US 7,447,203 B2Grant

Broadband access for virtual private networks

Issue Date:2008-11-04

•20 Claims

•3 Drawing Sheets

Abstract

Broadband access is provided to a virtual private network (VPN), including multiple local area networks (LANs) configured to interface with an IPv6 service provider network. Data to be routed from an originating device in an originating LAN to a destination device in a destination LAN is received by an ingress line interface and encapsulated in an IPv6 packet. A unique identification number assigned to the VPN is added to the IPv6 packet. When the destination device's address is not mapped to a corresponding egress line interface, the IPv6 packet is broadcast to a multicast address associated with the VPN. When the destination device's address is mapped to the egress line interface, the IPv6 packet is unicast to the egress line interface. The data is ultimately received and decapsulated by the egress line interface. After the VPN identification number is verified, the data is transmitted to the destination device.

Metadata

Assignee

AT&T Intellectual Property I, L.P.

Inventors

Weijing Chen
Keith Joseph Allen

Application Information

Application Number:US 10/628,238

Filing Date:2003-07-29

Priority Date:2003-07-29

Art Unit:2619

Classifications

IPC:

H04L12/56

Patent Drawings (3 sheets)

Description

Background of the Invention

[0001] 1. Field of the Invention

[0002] The present invention relates to the field of telecommunications. More particularly, the present invention relates to using an Internet protocol (IP) network of a telecommunications service provider to provide virtual private network (VPN) functionality among local area networks (LANs).

[0003] 2. Acronyms

[0004] The written description provided herein contains acronyms which refer to various telecommunications services, components and techniques, as well as features relating to the present invention. Although some of these acronyms are known, use of these acronyms is not strictly standardized in the art. For purposes of the written description herein, the acronyms are defined as follows:

- [0005] Address Resolution Protocol (ARP)
- [0006] Asynchronous Transfer Mode (ATM)
- [0007] Digital Subscriber Line (DSL)
- [0008] Digital Subscriber Line Access Multiplexer (DSLAM)
- [0009] Internet Protocol (IP)
- [0010] Internet Protocol Version 4 (IPv4)
- [0011] Internet Protocol Version 6 (IPv6)
- [0012] Internet Service Provider (ISP)
- [0013] Local Area Network (LAN)
- [0014] Media Access Control (MAC)
- [0015] Multi-Protocol Label Switching (MPLS)
- [0016] Point-to-Point Protocol (PPP)
- [0017] Personal Digital Assistant (PDA)
- [0018] Request for Comment (RFC)
- [0019] Telecommunications Service Provider (TSP)
- [0020] Transmission Control Protocol (TCP)
- [0021] User Datagram Protocol (UDP)
- [0022] Virtual Local Area Network (VLAN)
- [0023] Virtual Private Network (VPN)
- [0024] Wide Area Network (WAN)

[0025] 3. Background and Material Information

[0026] A virtual private network (VPN) is a non-public network that runs over a shared network infrastructure, such as the public Internet. A VPN enables interconnection among distinct networks, including local area networks (LANs), and other end-systems over a wide area network (WAN). The VPN provides security to the extent that it recognizes and transports only data associated with end-systems that are part of the network.

[0027] A virtual local area network (VLAN) provides logical grouping and networking of various customer end-systems, such as work stations, user devices, private networks, and the like, as though they are grouped on the same physical LAN. In other words, the VLAN associates end-systems based on criteria other than the physical location of the end-systems. For example, the VLAN can provide network services to a customer having multiple geographic locations, or to a department within a customer organization remotely located throughout a campus environment.

[0028] A VLAN VPN implemented over a WAN is provided by a telecommunications service provider (TSP) to interconnect the LANs as if they were one. Typically, TSPs rely on network connections to provide customers VPN service, including multi-protocol label switching (MPLS) paths, asynchronous transfer mode (ATM) circuits and point-to-point protocol (PPP) connections. However, connection oriented implementations inhibit efficient execution of VPN services and have limited scalability, as well as flexibility.

[0029] The present invention overcomes the problems associated with the prior art, as described below.

Brief Description of the Drawings

[0030] The present invention is further described in the detailed description that follows, by reference to the noted drawings by way of non-limiting examples of embodiments of the present invention, in which like reference numerals represent similar parts throughout several views of the drawings, and in which:

[0031] FIG. 1 is a diagram showing an exemplary network architecture, according to an aspect of the present invention; and

[0032] FIG. 2 is a flow diagram illustrating IP broadband access from an originating LAN, according to an aspect of the present invention.

Detailed Description of Embodiments

[0033] The present invention incorporates an Internet protocol, version 6 (IPv6) network to provide a connectionless approach to implementing VLAN VPNs among various LANs. Generally, the invention enables broadband access to the IPv6 network of a telecommunications service provider (TSP) by emulating layer two (e.g., Ethernet) functionality while performing layer three (e.g., IP) routing through a WAN. For example, a user operating within an originating LAN of a VPN may access the IPv6 TSP network from either a IPv4 or an IPv6 originating device by encapsulating each frame in an IPv6 packet, together with a unique VPN identification number, at an ingress line interface of the TSP network. The LAN frames include, for example, Ethernet frames, media access control (MAC) frames, other layer two frames and the like. The IPv6 packet is routed through the TSP network to an egress line interface associated with the destination LAN within the same VPN. The egress line interface verifies the VPN identification number and, upon verification, decapsulates the IPv6 packet and transmits the LAN frame to the destination LAN. Use of the IPv6 TSP network is a scalable and more manageable alternative to current MPLS networks, for example.

[0034] In view of the above, the present invention through one or more of its various aspects and/or embodiments is presented to accomplish one or more objectives and advantages, such as those noted below.

[0035] An aspect of the present invention provides a method for sending data through a provider network from an originating network to a destination network in a VPN. The method includes encapsulating data link layer data from the originating network in a network layer packet and determining whether a data link layer address of a destination device in the destination network is mapped to a network layer address of an egress line interface in the provider network. When the destination device address is not mapped to the egress line interface address, the network layer packet is broadcast to a multicast address associated with the VPN. When the destination device address is mapped to the egress line interface address, based on a previous transmission from the destination device, the network layer packet is unicast to the egress line interface address.

[0036] A VPN identification number corresponding to the VPN may be added to the network layer packet. The VPN identification number is verified after the egress line interface receives the network layer packet. The data layer link data is decapsulated from the network layer packet only when the VPN identification number is verified.

[0037] Another aspect of the present invention provides a method for providing broadband access to a VPN, which includes multiple LANs configured to interface with an IPv6 service provider network through broadband access links. The method includes encapsulating a LAN frame from an originating LAN of the VPN in an IPv6 packet of the service provider network; adding a VPN identification number corresponding to the VPN to the IPv6 packet; and routing the IPv6 packet through the service provider network. The LAN frame is decapsulated when the VPN identification number is verified. The decapsulated LAN frame is transmitted to the destination LAN. The IPv6 packet is discarded when the VPN identification number is not verified. The IPv6 packet includes an IPv6 address of an ingress line interface, which receives the LAN frame, as a source address and an IPv6 address of an egress line interface, to which the IPv6 packet is routed for verification, as a destination address.

[0038] The IPv6 packet may include the VPN identification number in an optional header extension. For example, the VPN identification number may be included in a multiple of four octets of the optional header extension. The optional header extension may further identify a destination option type, in which case the method further includes discarding the IPv6 packet when the egress line interface does not recognize the destination option type in the optional header extension. The optional header extension may further identify a VPN hop number, which indicates a number of line interfaces that transmit the IPv6 packet.

[0039] It is determined whether an address of a destination device in the destination LAN is mapped to the egress line interface. When the address is not mapped to the egress line interface, the IPv6 packet is broadcast to a multicast address associated with the VPN and the IPv6 packet is received at the egress line interface based on the multicast address. An address of the egress line interface is mapped to the address of the destination device, based on address information received by the ingress line interface in a transmission from the destination device. Subsequent IPv6 packets are then transmitted to the destination device using a unicast address of the egress line interface based on the mapping.

[0040] Another aspect of the present invention provides a system for providing broadband access to a VPN, which includes multiple LANs configured to interface with an IPv6 service provider network. The system includes multiple interface devices in the service provider network. Each interface device includes at least one line interface, each of which is connectable to at least one of the LANs through a broadband access link. A first interface device receives a LAN frame from a first LAN at an ingress line interface corresponding to the first LAN, encapsulates the LAN frame in an IPv6 packet, and adds a VPN identification number corresponding to the VPN to the IPv6 packet. The LAN frame is directed to a second LAN. A second interface device receives the IPv6 packet at an egress line interface corresponding to the second LAN, verifies the VPN identification number, decapsulates the LAN frame when the VPN identification number is verified, and transmits the LAN frame to the second LAN. The second interface device discards the IPv6 packet when it is not able to verify the VPN identification number.

[0041] The IPv6 packet includes the VPN identification number in an optional header extension. The first interface device may further include an ingress virtual bridge corresponding to the ingress line interface. When the ingress virtual bridge is not able to associate an address of a destination device in the second LAN with an address of the egress line interface of the second interface device, the first interface device broadcasts the IPv6 packet to a multicast address associated with the VPN. The second interface device receives the IPv6 packet at the egress line interface based on the multicast address. The second interface device may further include an egress virtual bridge corresponding to the egress line interface. The egress virtual bridge then maps an address of an originating device in the first LAN with the address of the ingress line interface after the second interface device receives the broadcast IPv6 packet. The second interface device is able to unicast subsequent IPv6 packets, directed to the originating device, to the address of the ingress line interface based on the mapping.

[0042] Yet another aspect of the present invention provides a method of providing broadband access for a customer in a VPN, including multiple LANs interfacing with at least one TSP network. Each TSP network includes multiple interfaces corresponding to the multiple LANs. The method includes assigning a unique VPN identification number to the customer and assigning a common multicast address to the interfaces and a unique unicast address to each of the interfaces. Data from an originating LAN is received, the data being directed to a destination device in a destination LAN. The originating LAN corresponds to an ingress interface of the interfaces and the destination LAN corresponds to an egress interface of the interfaces. When an address of the destination device address is not mapped to the destination LAN, the data is encapsulated in a multicast packet, having the unique address of the ingress interface as a source address and the multicast address as a destination address. The encapsulated data is transmitted to all interfaces corresponding to the LANs based on the multicast address. The frame is decapsulated only at the egress interface, which forwards the frame to the destination device.

[0043] The destination device address may be mapped to the IPv6 address of the egress interface based on address information previously received by the ingress interface from the destination device. When the destination device address is mapped to the egress interface, the data is encapsulated in a unicast packet having the unique IPv6 address of the ingress interface as the source address and the unique address of the egress interface as the destination address. The encapsulated frame is then transmitted only to the egress interface, based on the destination address in the unicast packet. The VPN identification number may be entered in the multicast packet and/or the unicast packet. The reading the VPN identification is read at the egress interface to verify that the received packet is associated with the VPN.

[0044] The various aspects and embodiments of the present invention are described in detail below.

[0045] The present invention is directed to enabling TSPs to provide IP broadband network services over packet switched data networks having expanded capacity, such as IPv6 networks. IPv6 networks are capable of serving mass-market IP broadband access subscribers, as well as accommodating business customers to manage their data communication services in-house. VLAN VPN is one service that enables the broadband access and management control desired.

[0046] FIG. 1 is a diagram depicting an exemplary network infrastructure supporting the present invention. FIG. 1, in particular, depicts a VLAN VPN of a customer, which includes multiple LANs 10, 40 and 50. In an embodiment of the invention, each LAN is an Ethernet LAN having user end-systems 14, 44 and 54 that interface with a TSP core network 20 through customer edge devices 11, 41 and 51, respectively. However, each of the LANs 10, 40 and 50 may be an IP network or other data network without departing from the spirit and scope of the present invention. As discussed above, the TSP network 20 is an IPv6 network, which allows static allocation of IPv6 addresses to uniquely identify the customers, due to the large address space of the IPv6 format. The TSP IPv6 network 20 is essentially configured such that it appears to be a wide-area LAN to the VLAN VPN customer.

[0047] The LANs 10, 40 and 50, depicted in the exemplary embodiment of the invention, provide layer two (i.e., data link layer) network functionality. Layer two functionality generally includes handling physical and logical connections to the Ethernet or other LAN frame (or packet) destinations. The user devices, such as customer devices 14, 44 and 54, are addressed and identified using unique MAC addresses corresponding to each device. The data link layer protocol specifies the MAC address of each frame's source and destination.

[0048] The TSP network 20, depicted in the exemplary embodiment of the invention, provides layer three (ie., network layer) functionality. The network layer routes packets (or datagrams) from one network to another. Internet protocol, in particular, identifies each IP device with a unique IP address, including, for example, the edge devices 22, 23 and 24 and/or the various line interfaces 22a, 23a and 24a, discussed below. In the depicted embodiment of the present invention, each IP address is an IPv6 address allocated by the TSP network 20. The IP packets are routed through the TSP network 20 in accordance with IP (e.g., IPv6), while the layer four (i e., transport layer) protocols, such as transmission control protocol (TCP) and user datagram protocol (UDP) for transmission control, continue to be supported with no change.

[0049] The originating customer device 14 is depicted as part of the originating LAN 10. Each of the LANs 10, 40 and 50 may include any number and type of IP compatible networked devices, including, for example, a personal computer, a laptop computer, a personal digital assistant (PDA), a voice over IP telephone, or the like. The originating customer device 14 communicates through the LAN 10 with the customer edge device 11. The customer edge device 11 likewise is any interface device capable of communicating with the TSP network 20, such as an Ethernet switch or an IP router with an Ethernet interface, depending on the type of customer network.

[0050] The customer edge device 11 accesses an ingress router 22 of the TSP network 20 over a broadband access link 12. In an embodiment of the invention, the broadband access link 12 is a digital subscriber line (DSL), and therefore includes a DSL access multiplexer (DSLAM), an asynchronous transfer mode (ATM) edge switch and an interworking function device (not pictured), for example. Alternatively, the broadband access link 12 may include digital cable, T-1, digital signal-level 3 (DS-3) or optical carrier-level 3 (OC-3) interfaces, or an Ethernet. The broadband access links 12, 42 and 52 of the various LANs in the VPN do not need to be the same type.

[0051] The TSP network 20 includes multiple edge devices (i.e., gateways) 22, 23 and 24, which may be IPv6 routers or switches having Ethernet bridging functionality, for example. Each edge device 22, 23 and 24 has multiple line interfaces, which correspond to the various customer LANs and interface the edge devices with the customer LANs, including depicted line interfaces 22a, 23a and 24a. It is understood that each edge device 22, 23 and 24 is configured with multiple line interfaces, even though FIG. 1 depicts only one corresponding line interface 22a, 23a and 24a for each. The multiple line interfaces enable each edge device 22, 23 and 24 to simultaneously service multiple VPNs and LANs.

[0052] Typically, each customer device 14, 44 and 54 corresponds to a single line interface (e.g., line interfaces 22a, 23a and 24a), although alternative embodiments of the invention include multiple interfaces for a single customer device 14, 44 and 54. As discussed below, each line interface 22a, 23a and 24a is associated with a virtual learning bridge, which learns and caches mapping of customer devices 14, 44 and 54 with their associated line interfaces 22a, 23a and 24a. The TSP network 20 is thus able to more efficiently route communications among the LANs in the VPN over time.

[0053] The exemplary network architecture of FIG. 1 depicts an ingress edge device 22, which interfaces with the broadband access link 12 of the originating LAN 10 through an ingress line interface 22a. In addition to the ingress edge device 22, FIG. 1 depicts two egress edge devices 23 and 24. Egress edge device 23 interfaces with the broadband access link 42 of the destination LAN 40 through an egress line interface 23a, and the egress edge device 24 interfaces with the broadband access link 52 of the destination LAN 50 through an egress line interface 24a. Each of the LANs 40 and 50 respectively include at least one destination device 44 and 54 of the customer, which may be any of the types of devices described above with respect to the originating customer device 14 of LAN 10. It is understood that all of the exemplary customer devices and corresponding edge devices depicted in FIG. 1 are capable of sending and receiving data through the VPN, and are described as originating or destination devices only to facilitate description of the various embodiments of the invention.

[0054] IPv6 packets are routed through the TSP network 20 to one of the egress edge devices 23 or 24, depending on the destination address of each IPv6 packet sent from the ingress edge device 22. For example, an Ethernet frame from the customer device 14 destined for the destination device 44 in LAN 40 is encapsulated in an IPv6 packet having the IP address of the egress line interface 23a as the destination address. As described in detail with respect to FIG. 2, when the egress line interface associated with the destination device and/or the destination LAN is not known, the ingress edge device 22 multicasts the IPv6 packet to the other edge devices serving the VLAN VPN so that all potential egress edge devices, including the egress edge devices 23 and 24, receive the packet. Only the egress edge device having the egress line interface that services the destination LAN (e.g., the egress edge device 23 and associated egress line interface 23a) responds to the broadcast IPv6 packet, enabling unicast transmission of subsequent packets from the ingress edge device 22. In alternative embodiments of the invention, the broadcast comprises a modified address resolution protocol (ARP) message and the encapsulation and decapsulation is performed by the customer edge devices 11 and 41. The addressing and transmitting processes is described in detail with respect to FIG. 2, below.

[0055] In an embodiment of the invention, the customer subscribes to a VLAN VPN service having IP broadband connectivity with the TSP network 20 from multiple sites or locations. The customer's VLAN VPN is assigned a unique VPN identification number, which is four or more bytes, for example. In alternative embodiments of the invention, the unique VPN identification number is an IPv6 address prefix under control of the TSP or an identification number allocated from a dedicated, separate address space of the TSP network 20. The VPN identification number assigned to the customer is included with the VPN interface configuration. The VPN identification number distinguishes data packets associated with the customer's VLAN VPN from other VLAN VPNs supported by the TSP network 20.

[0056] Each of the line interfaces 22a, 23a and 24a depicted in the TSP network 20 is allocated unique IPv6 address (TSP-IPv6) from an IPv6 address block of the TSP network 20. As explained above, the line interfaces 22a, 23a and 24a and associated TSP-IPv6 addresses correspond to particular LANs of the customer's VPN. The line interfaces 22a, 23a and 24a are also assigned a VLAN VPN specific IPv6 multicast address (TSP-MIPv6) from the TSP's IPv6 address block, associated with the customer's VPN. A single multicast address may be used to multicast a packet to all of the interfaces serving a VLAN VPN. In an embodiment of the invention, the TSP-IPv6 and TSP-MIPv6 addresses are allocated or assigned to the line interfaces 22a, 23a and 24a manually, although any effective form of allocation or assignment may be incorporated without departing from the spirit and scope of the present invention. Generally, using the IPv6 and the MIPv6 addresses, the TSP network 20 is able to effectively provide layer two (e.g., Ethernet) capabilities to link customer edge devices 11, 41 and 51, while the customer performs its own layer three (e.g., IP) network administration.

[0057] As stated above, the ingress edge device 22 has virtual learning bridges corresponding to the line interfaces associated with every VLAN VPN that it serves, including the line interface 22a. When the virtual learning bridge receives an Ethernet frame from the originating VLAN 10, for example, it learns and caches identification information, such as an Ethernet MAC address and/or the LAN identification number (e.g., the 802.1q tag) of the originating customer device 14 from which the frame is sent. Therefore, the line interface 22a knows precisely where to forward frames that it subsequently receives, e.g., from the other line interfaces 23a and 24a, destined for the MAC address and/or the VLAN identification number of the originating customer device 14.

[0058] Similarly, the virtual learning bridge learns information that enables the line interface 22a to efficiently forward LAN frames that it receives from the originating customer device 14 to various destination devices, such as the destination customer devices 44 and 54. For example, referring to FIG. 2, the ingress line interface 22a

- [0059] receives a LAN frame from the originating customer device 14 over the broadband access link 12 at step s210. At step s212, the ingress line interface 22a determines whether the destination address (e.g., the address of the destination customer device 44) is already mapped to an egress line interface.

[0060] When mapping of the destination address to an egress line interface does not exist, for example, when the ingress line interface 22a has no record of transmitting a packet from the originating customer device 14 to the destination customer device 44 (or from the originating LAN 10 to the destination LAN 40), the ingress line interface 22a encapsulates the LAN frame in a multicast IPv6 packet at step s214. The multicast IPv6 packet includes the TSP IPv6 address of the ingress line interface 22a as the source address and the TSP-MIPv6 multicast address of the customer's VLAN VPN as the destination multicast address.

[0061] At step s216, the previously assigned VPN identification number is added to the header of the IPv6 packet in order to provide security for the VPN. Use of the VPN identification number prevents unsecured or unauthorized LAN frames from being delivered to VPN customers at the egress line interfaces 23a and 24a. Use of the VPN identification number is an improvement over security measures implemented in conventional VPNs, which typically require layered connections internal to the network, and a control plane consisting of virtual routers configured to exchange routing information. In an alternative embodiment, the customer edge device 11 adds the VPN identification number to the IPv6 packet header, and the ingress line interface 22a confirms it. The IPv6 packet, including the VPN identification number is transmitted through the TSP network 20 to the egress line interface 23a in the egress device 23 at step s220.

[0062] In an embodiment of the invention, an extension of the current IPv6 optional header is used to encapsulate the VPN identification number. The IPv6 header is implemented, for example, in accordance with RFC 2460, “Internet Protocol, Version 6 (IPv6) Specification” (December 1998), the content of which is expressly incorporated by reference herein in its entirety. The VPN identification number marks an IPv6 packet as belonging to a particular VLAN VPN. The VPN identification number header is a specific option of the more generic destination options header (e.g., header type 60) of the IPv6 protocol. An exemplary format of the optional header extension, including the VPN identification number header is as follows:

[0063]

[0064] The first three bits of the first octet are 011, as shown above. The remaining five bits comprise the destination option type number. The value of 011 indicates that nodes not recognizing this option type should discard the packet and that the option data (i.e., the VPN hop count) may change en route. Discarding the packet ensures that any packet delivered to a node not capable of processing VPN headers will not be inadvertently delivered to a site outside of the VPN. The VPN hop count is an eight bit unsigned integer, which is incremented by one by each peering edge device in the TSP network 20 that forwards the packet. The VPN identification number is a four (or multiple of four) octet identifier associated with each VPN.

[0065] At step s218, the multicast IPv6 packet, including the encapsulated LAN frame and the VPN identification number, is then broadcast through the TSP network 20, resulting in the IPv6 packet being received by every potential egress line interface associated with a broadband access of the customer's VLAN VPN, including, for example, line interfaces 23a and 24a, at step s220. Only the line interface 23a which corresponds to the destination LAN 40 and/or the destination customer device 44 proceeds with the remaining steps of FIG. 2, for example, based on the MAC address of the destination customer device 44 to which the LAN frame was initially addressed.

[0066] When the mapping exists, as determined at step s212, the ingress line interface 22a encapsulates the LAN frame in a unicast IPv6 packet at step s232. The IPv6 packet has the TSP IPv6 address of the egress line interface (e.g., the line interface 23a) as the destination address and the TSP IPv6 address of the ingress line interface 22a as the source address. At step s234, the previously assigned VPN identification number is added to the header of the IPv6 packet in order to provide security for the VPN, as described above with respect to multicasting IPv6 packets. The unicast IPv6 packet, including the encapsulated LAN frame and the VPN identification number, is then transmitted through the TSP network 20 using the TSP IPv6 address of the egress line interface 23a, which receives the unicast IPv6 packet at step s220.

[0067] At step s222, the virtual learning bridge of the egress line interface 23a authenticates the IPv6 packet. For example, the egress line interface 23a first determines whether the VPN identification number of the received IPv6 packet matches the assigned customer VPN identification number. Any IPv6 packets that do not include a matching VPN identification number are discarded at step s238. In an embodiment of the invention, the destination customer edge device 41 determines whether the VPN identification number of the received IPv6 packet matches the assigned VPN identification number and discards unauthorized packets, accordingly. In another embodiment, authorization of the VPN identification numbers can be disabled in the TSP network 20 and/or the LAN 40 to enable interworking among a greater number of VPNs.

[0068] When the VPN identification number of the IPv6 packet matches the customer VPN identification number, the virtual learning bridge of the egress line interface 23a decapsulates the IPv6 packet and extracts the LAN frame at step s224. The LAN frame is forwarded to the destination LAN 40, through the broadband access link 42 at step s226.

[0069] Meanwhile, at step s228, the virtual learning bridge of the egress line interface 23a learns and caches the mapping of identification information, such as an Ethernet MAC address and/or the VLAN identification number of the originating customer device 14, to the TSP-IPv6 address of the ingress line interface 22a, from which the frame was sent. Therefore, when the egress line interface 23a receives subsequent LAN frames from the customer device 44 and/or the LAN 40, destined for the customer device 14 and/or the LAN 10, the egress line interface 23a merely encapsulates the LAN frame in an IPv6 packet and unicasts the IPv6 packet to the ingress line interface 22a, using the mapping.

[0070] Because the majority of Ethernet data traffic, for example, is bi-directional, eventually all of the line interfaces 22a, 23a and 24a will learn and cache the mapping of the identification information of all active customer devices 14, 44 and 54 in all of the LANs 10, 40 and 50 to the TSP IPv6 addresses of the corresponding line interfaces 22a, 23a and 24a. Accordingly, the line interfaces will be able to encapsulate the LAN frames in unicast IPv6 packets containing the specific TSP-IPv6 address of the desired line interface as the destination address, instead of a multicast IPv6 packet having the customer IPv6 multicast address as the destination address. In other words, as the mapping among line interfaces 22a, 23a and 24a and customer devices 14, 44 and 54 is learned and cached, the process increasingly follows the unicast steps s232, s234 and s236 of FIG. 2, as opposed to the multicast steps s214, s216 and s218, significantly increasing the efficiency of the TSP network 20.

[0071] An alternative embodiment of the present invention enables interworking among different VLAN VPNs (i.e., extra-net VPNs). The line interfaces 22a, 23a and 24a are configured to recognize and authenticate multiple, previously assigned VPN identification numbers, corresponding to the interworking VPNs, instead of a single VPN identification number corresponding to one customer. Accordingly, any IPv6 packet that arrives at the line interfaces 22a, 23a and 24a having a VPN identification number matching any of the VPN identification numbers on the list is authenticated and forwarded to the appropriate LAN 10, 40 and 50 and/or customer device 14, 44 and 54. For example, the allowed VPN identification number list may include all of the VPN identification numbers of pre-arranged peering business customers.

[0072] Although the invention has been described with reference to several exemplary embodiments, it is understood that the words that have been used are words of description and illustration, rather than words of limitation. Changes may be made within the purview of the appended claims, as presently stated and as amended, without departing from the scope and spirit of the invention in its aspects. Although the invention has been described with reference to particular means, materials and embodiments, the invention is not intended to be limited to the particulars disclosed; rather, the invention extends to all functionally equivalent structures, methods, and uses such as are within the scope of the appended claims.

[0073] In accordance with various embodiments of the present invention, the methods described herein are intended for operation as software programs running on a computer processor. Dedicated hardware implementations including, but not limited to, application specific integrated circuits, programmable logic arrays and other hardware devices can likewise be constructed to implement the methods described herein. Furthermore, alternative software implementations including, but not limited to, distributed processing or component/object distributed processing, parallel processing, or virtual machine processing can also be constructed to implement the methods described herein.

[0074] It should also be noted that the software implementations of the present invention as described herein are optionally stored on a tangible storage medium, such as: a magnetic medium such as a disk or tape; a magneto-optical or optical medium such as a disk; or a solid state medium such as a memory card or other package that houses one or more read-only (non-volatile) memories, random access memories, or other re-writable (volatile) memories. A digital file attachment to email or other self-contained information archive or set of archives is considered a distribution medium equivalent to a tangible storage medium. Accordingly, the invention is considered to include a tangible storage medium or distribution medium, as listed herein and including art-recognized equivalents and successor media, in which the software implementations herein are stored.

[0075] Although the present specification describes components and functions implemented in the embodiments with reference to particular standards and protocols, the invention is not limited to such standards and protocols. Each of the standards for Internet and other packet-switched network transmission (e.g., IPv4, IPv6, TCP, UDP, MPLS) and public telephone networks (ATM, DSL) represent examples of the state of the art. Such standards are periodically superseded by faster or more efficient equivalents having essentially the same functions. Accordingly, replacement standards and protocols having the same functions are considered equivalents.

Claims

What is claimed:

1. A method for providing a virtual private network, by receiving from a customer originating device of a first local area network, a local area network frame for transmission to a customer destination device in a second local area network over broadband access links that include customer local area network edge devices of at least one customer and an ingress edge device and an egress edge device of a service provider network, the method comprising:

assigning to each edge device of the service provider a unicast IPv6 address, from an IPv6 address block of the service provider, that corresponds to a particular local area network of the customer;

assigning to each edge device of the service provider a virtual private network specific multicast IPv6 address, from the IPv6 address block of the service provider, using the virtual private network specific multicasting IPv6 address for multicasting packets to all of the edge devices of the service provider serving the virtual private network;

determining whether an IPv6 packet includes a destination address of a customer destination device, and whether the destination address is mapped to an egress edge device of the service provider,

when mapping of the destination address to an egress edge device does not exist, encapsulating the local area network frame in a multicast IPv6 packet, the multicast IPv6 packet including the IPv6 address of the ingress edge device of the service provider as the source address and the multicast IPv6 address of the virtual private network as the destination multicast address;

when mapping of the destination address to an egress edge device does exist, encapsulating the local area network frame in a unicast IPv6 packet, including the unicast IPv6 address of the egress edge device of the service provider;

adding a virtual private network identification header to a header of the IPv6 packet, the virtual private network identification header including a destination option, a virtual private network hop count and an identification number identifying the virtual private network of the customer;

broadcasting the IPv6 packets having multicast addresses through the service provider network to all of the edge devices serving the virtual private network;

transmitting the IPv6 packets having the unicast IPv6 address, through the service provider network to a particular egress device;

authenticating the IPv6 packets at the egress device of the service provider using the virtual private network identification;

discarding any IPv6 packets that cannot be authenticated;

decapsulating and extracting the local area network frame of authenticated IPv6 packets at the egress device of the service provider;

forwarding the decapsulated local area network frame to the destination local area network; and

transmitting the decapsulated customer local area network frame to the customer destination device.

2. The method according to claim 1 wherein the ingress edge device of the service provider adds the virtual private network identification number to the IPv6 packet header.

3. The method according to claim 1 wherein the customer local area network edge device adds the virtual private network identification number to the IPv6 packet header, and the ingress edge device confirms the virtual private network identification number.

4. The method according to claim 1, in which the IPv6 packet is discarded when the egress edge device does not recognize the destination option type in the header.

5. The method according to claim 1, in which the virtual private network hop number is incremented every time the IPv6 packet is forwarded by an edge device of the service provider network.

6. The method according to claim 1, in which the egress edge device includes a virtual learning bridge for authenticating the IPv6 packet, the egress edge device determines whether the virtual private network identification number of the received IPv6 packet matches the assigned customer virtual private network identification number, and any IPv6 packets that do not include a matching virtual private network identification number are discarded.

7. The method according to claim 1, in which destination local area network edge device of the customer determines whether the virtual private network identification number of the received IPv6 packet matches the assigned virtual private network identification number and discards unauthorized packets.

8. The method according to claim 1, wherein the authentication of the virtual private network identification numbers can be disabled in the service provider network or the destination local area network to enable interworking among a plurality of virtual private networks.

9. The method according to claim 1, in which the egress edge device includes a virtual learning bridge for learning and caching a mapping of identification information, including an Ethernet MAC address or an identification number of the originating customer device, to the IPv6 address of the ingress edge device, from which the local area network frame was sent, such that when the egress edge device receives subsequent local area network frames from the customer destination device destined for the customer originating device, the egress edge device encapsulates the local area network frame in a unicast IPv6 packet and unicasts the IPv6 packet to the ingress edge device using the cached mapping.

10. The method according to claim 1, in which edge devices of the service provider are configured to recognize and authenticate multiple, previously assigned virtual private network identification numbers, corresponding to interworking virtual private networks, instead of a single virtual private network identification number corresponding to one customer.

11. A service provider network for providing a virtual private network, for receiving from a customer originating device of a first local area network, a local area network frame for transmission to a customer destination device in a second local area network over broadband access links that include local area network edge devices of the customer coupled to the service provider network, the service provider network comprising:

a plurality of ingress edge devices and egress edge devices;

each edge device being assigned a unicast IPv6 address, from an IPv6 address block of the service provider, that corresponds to a particular local area network of the customer;

each edge device also being assigned a virtual private network specific multicast IPv6 address, from the IPv6 address block of the service provider, which is used for multicasting packets to all of the edge devices of the service provider serving the virtual private network;

each edge device determining whether an IPv6 packet includes a destination address of a customer destination device, and whether the destination address is mapped to an egress edge device of the service provider,

wherein a virtual private network identification header is added to a header of the IPv6 packet, the virtual private network identification header including a destination option, a virtual private network hop count and an identification number identifying the virtual private network of the customer;

wherein the IPv6 packets having multicast addresses are broadcast through the service provider network to all of the edge devices serving the virtual private network;

wherein the IPv6 packets having the unicast IPv6 address are transmitted through the service provider network to a particular egress device;

wherein the IPv6 packets are authenticated at the egress devices of the service provider;

wherein any IPv6 packets that cannot be authenticated are discarded;

wherein the local area network frame of authenticated IPv6 packets are decapsulated and extracted at the egress device of the service provider;

wherein the decapsulated local area network frames are forwarded to the destination local area network; and

wherein the decapsulated local area network frames are transmitted to the customer destination device.

12. The network according to claim 11 wherein the ingress edge device of the service provider adds the virtual private network identification number to the IPv6 packet header.

13. The network according to claim 11 wherein the customer edge device adds the virtual private network identification number to the IPv6 packet header, and the ingress edge device confirms the virtual private network identification number.

14. The network according to claim 11, in which the IPv6 packet is discarded when the egress edge device does not recognize the destination option type in the header.

15. The network according to claim 11, in which the virtual private network hop number is incremented every time the IPv6 packet is forwarded by an edge device of the service provider network.

16. The network according to claim 11, in which the egress edge device includes a virtual learning bridge for authenticating the IPv6 packet, the egress edge device determines whether the virtual private network identification number of the received IPv6 packet matches the assigned customer virtual private network identification number, and any IPv6 packets that do not include a matching virtual private network identification number are discarded.

17. The network according to claim 11, in which destination local area network edge device of the customer determines whether the virtual private network identification number of the received IPv6 packet matches the assigned virtual private network identification number and discards unauthorized packets.

18. The network according to claim 11, wherein the authentication of the virtual private network identification numbers can be disabled in the service provider network or the destination local area network to enable interworking among a plurality of virtual private networks.

19. The network according to claim 11, in which the egress edge device includes a virtual learning bridge for learning and caching a mapping of identification information, including an Ethernet MAC address or an identification number of the originating customer device, to the IPv6 address of the ingress edge device, from which the local area network frame was sent, such that when the egress edge device receives subsequent local area network frames from the customer destination device destined for the customer originating device, the egress edge device encapsulates the local area network frame in a unicast IPv6 packet and unicasts the IPv6 packet to the ingress edge device using the cached mapping.

20. The network according to claim 11, in which edge devices of the service provider are configured to recognize and authenticate multiple, previously assigned virtual private network identification numbers, corresponding to interworking virtual private networks, instead of a single virtual private network identification number corresponding to one customer.

Patent Citations (63)

Patent	Date	Inventor	Cited By
US5600644(A)	1997-02-01	Chang et al.	Applicant
US5633869(A)	1997-05-01	Burnett et al.	Applicant
US5737333(A)	1998-04-01	Civanlar et al.	Applicant
US5757796(A)	1998-05-01	Hebb	Applicant
US5781529(A)	1998-07-01	Liang et al.	Applicant
US5809025(A)	1998-09-01	Timbs	Applicant
US5828844(A)	1998-10-01	Civanlar et al.	Applicant
US5835710(A)	1998-11-01	Nagami et al.	Applicant
US5892763(A)	1999-04-01	Laraqui et al.	Applicant
US5903559(A)	1999-05-01	Acharya et al.	Applicant
US5930477(A)	1999-07-01	Uchida	Applicant
US5936959(A)	1999-08-01	Joffe	Applicant
US5940394(A)	1999-08-01	Killian	Examiner
US5940396(A)	1999-08-01	Rochberger	Applicant
US5946313(A)	1999-08-01	Allan et al.	Applicant
US5949782(A)	1999-09-01	Wells	Applicant
US5958018(A)	1999-09-01	Eng et al.	Applicant
US5983332(A)	1999-11-01	Watkins	Applicant
US5991854(A)	1999-11-01	Watkings	Applicant
US6016319(A)	2000-01-01	Kshirsagar et al.	Applicant
US6021263(A)	2000-02-01	Kujoory et al.	Applicant
US6034958(A)	2000-03-01	Wicklung	Applicant
US6055236(A)	2000-04-01	Nessett et al.	Examiner
US6078586(A)	2000-06-01	Dugan et al.	Applicant
US6081836(A)	2000-06-01	Karapetkov et al.	Applicant
US6111881(A)	2000-08-01	Soncodi	Applicant
US6122670(A)	2000-09-01	Bennett et al.	Applicant
US6138144(A)	2000-10-01	DeSimone et al.	Applicant
US6195364(B1)	2001-02-01	Brodigan	Applicant
US6222842(B1)	2001-04-01	Sasyan et al.	Applicant
US6252857(B1)	2001-06-01	Fendick et al.	Applicant
US6314098(B1)	2001-11-01	Masuda et al.	Applicant
US6343322(B2)	2002-01-01	Nagami et al.	Applicant
US6343326(B2)	2002-01-01	Acharya et al.	Applicant
US6345051(B1)	2002-02-01	Gupta et al.	Applicant
US6385170(B1)	2002-05-01	Chiu et al.	Applicant
US6456962(B1)	2002-09-01	Allingham et al.	Applicant
US6470389(B1)	2002-10-01	Chung et al.	Applicant
US6496479(B1)	2002-12-01	Shionozaki	Applicant
US6516417(B1)	2003-02-01	Pegrum et al.	Applicant
US6523068(B1)	2003-02-01	Beser et al.	Applicant
US6538416(B1)	2003-03-01	Hahne et al.	Applicant
US6563794(B1)	2003-05-01	Takashima et al.	Applicant
US6598080(B1)	2003-07-01	Nagami et al.	Applicant
US6625124(B1)	2003-09-01	Fan et al.	Applicant
US6751218(B1)	2004-06-01	Hagirahim et al.	Applicant
US6788681(B1)	2004-09-01	Hurren et al.	Examiner
US6798782(B1)	2004-09-01	Caronni et al.	Applicant
US7110375(B2)	2006-09-01	Khalil et al.	Examiner
US2002/0038419(A1)	2002-03-01	Garrett et al.	Applicant
US2002/0061011(A1)	2002-05-01	Wan	Applicant
US2002/0141369(A1)	2002-10-01	Perras	Applicant
US2002/0196793(A1)	2002-12-01	Samba et al.	Applicant
US2003/0028671(A1)	2003-02-01	Mehta et al.	Applicant
US2003/0076854(A1)	2003-04-01	Mudhar et al.	Applicant
US2003/0088696(A1)	2003-05-01	McCanne	Applicant
US2003/0115480(A1)	2003-06-01	McDysan	Examiner
US2004/0013130(A1)	2004-01-01	Blanchet et al.	Examiner
WO99/29137	1999-06-01		Applicant
WO/57296	2000-09-01		Applicant
WO/76122	2000-12-01		Applicant
WO1/11837	2001-02-01		Applicant
WO1/31829	2001-05-01		Applicant

Non-Patent Literature (25)

English Language Abstract of EP 1 036 450, published Sep. 20, 2000.Applicant
WAN, “ASP Bi-level Addressing & ANS Requirements” (99-0534), dated Sep. 26-Oct. 1, 1999.Applicant
WAN, “ASP Bi-level Addressing Architecture” (99-0649), dated Nov. 28-Dec. 4, 1999.Applicant
ATM Forum Addressing: Reference Guide (AF-RA-0106.000), The ATM Forum Technical Committee, dated Feb. 1999.Applicant
“ATM Forum Addressing: User Guide version 1.0” (AF-RA-0105.000), The ATM Forum Technical Committee, dated Jan. 1999.Applicant
“PNNI Transported Address Stack version 1.0” (AF-CS-0115.000), The ATM Forum Technical Committee, dated May 1999.Applicant
“New Capabilities ATM Addressing Document (Draft)” (BTD-RA-ADDR-02.03), The ATM Forum Technical Committee, dated Oct. 1998.Applicant
“ATM Name System V2.0 Baseline Text” (BTD-SAA-ANS-02.01), The ATM Forum Technical Committee, dated Jul. 1999.Applicant
“ATM Bi-Level Addressing Document, Version 1.0” (STR-RA-ADDR-01.00), The ATM Forum Technical Committee, dated Jul. 2000.Applicant
“ATM Bi-Level Addressing Document, Version 1.0 (Draft)” (STR-RA-ADDR-01.00), The ATM Forum Technical Committee, dated Jul. 2000.Applicant
Specification for RFC 1034, entitled: “Domain Names-Concepts and Facilities”, Nov. 1987.Applicant
Specification for RFC 1035, entitled: “Domain Names-Implementation and Specification”, Nov. 1987.Applicant
Specification for RFC 1995, entitled: “Incremental Zone Transfer in DNS” Aug. 1996.Applicant
Specification for RFC 1996, entitled: “A Mechanism for Prompt Notification of Zone Changes (DNS Notify),” Aug. 1996.Applicant
Specification for RFC 2065, entitled: “Domain Name System Security Extensions” Jan. 1997.Applicant
Specification for RFC 2136, entitled: “Dynamic Updates in the Domain Name System (DNS Update),” Apr. 1997.Applicant
Specification for RFC 2137, entitled: “Secure Domain Name System Dynamic Update”, Apr. 1997.Applicant
“The Internet Multimedia Conferencing Architecture”, by Handley et al., INET '96, Jun. 1996, pp. 1-13, http://www.isoc.org/inet96/proceedings/,>.Applicant
“RSVP-ATM QoS Interworking”, Cisco IOS Release 12.0 (3), 2001, pp. 1-34.Applicant
“RSVP Over ATM Implementation Requirements”, by Berger, FORE Systems, Aug. 1998, <ftp://ftp.isi.edu/in-notes/rfc2380.txt>.Applicant
“An Overview of ATM”, <http://www.rware.demon.co.uk/atm.htm>, 1999.Applicant
“QoS Trials on SuperJANET in the Context of HICID and Other BT/JISC Project”, by Crowcroft et al., Nov. 14, 1997, <http://www.cs.ucl.ac.uk/research/hicid/jisc-anc.html>.Applicant
“Extensions to RSVP for QoS IP Over Signaled QoS Network”, by Chen et al., SBC Communications, Inc., Apr. 2002, <http://www.ietf.org/internt-drafts/draft-weijing-rsvp-sqn-00.tex>.Applicant
“Resource Reservation Protocol”, Cisco Systems, Inc., published on Feb. 20, 2002, http://www.cisco.com/univercd/cc/td/doc/cisintwk/ito—doc/rsvp.htm>.Applicant
K. Allen, et al., “IPv6 for Large Access Providers” (Oct. 2002).Applicant