US20130227156A1 - Ipv6 address generation to trigger a virtual leased line service - Google Patents
Ipv6 address generation to trigger a virtual leased line service Download PDFInfo
- Publication number
- US20130227156A1 US20130227156A1 US13/859,856 US201313859856A US2013227156A1 US 20130227156 A1 US20130227156 A1 US 20130227156A1 US 201313859856 A US201313859856 A US 201313859856A US 2013227156 A1 US2013227156 A1 US 2013227156A1
- Authority
- US
- United States
- Prior art keywords
- address
- sap
- session
- service
- network device
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/14—Session management
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/50—Routing or path finding of packets in data switching networks using label swapping, e.g. multi-protocol label switch [MPLS]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/09—Mapping addresses
- H04L61/10—Mapping addresses of different types
- H04L61/103—Mapping addresses of different types across network layers, e.g. resolution of network layer into physical layer addresses or address resolution protocol [ARP]
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/50—Address allocation
- H04L61/5007—Internet protocol [IP] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L61/00—Network arrangements, protocols or services for addressing or naming
- H04L61/59—Network arrangements, protocols or services for addressing or naming using proxies for addressing
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/622—Layer-2 addresses, e.g. medium access control [MAC] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2101/00—Indexing scheme associated with group H04L61/00
- H04L2101/60—Types of network addresses
- H04L2101/618—Details of network addresses
- H04L2101/659—Internet protocol version 6 [IPv6] addresses
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L45/00—Routing or path finding of packets in data switching networks
- H04L45/68—Pseudowire emulation, e.g. IETF WG PWE3
Definitions
- Various exemplary embodiments disclosed herein relate generally to communications devices, specifically connectivity in a packet data network.
- a packet data network such as an Internet Protocol (IP) or Multiprotocol Label Switching (MPLS) network.
- IP Internet Protocol
- MPLS Multiprotocol Label Switching
- a pseudo-local area network may be established between one or more devices through the packet data network with the use of various devices and techniques.
- One of the methods for creating such a pseudo-LAN may be the use of one or more pseudowires within the packet data network to connect devices on the edge of the network.
- P2P Layer 2 point-to-point
- two devices connected through a packet-switching network may operate in a similar manner to, for example, devices sharing a common provider edge (PE) device.
- PE provider edge
- Configuration of a pseudo-LAN regularly involves the management of devices connected within the pseudo-LAN, including, for example, the resolution of addresses for the devices once the service is established. While the pseudo-LAN may be able to support a variety of services, such as Asynchronous Transfer Mode (ATM), Frame Relay (FR), Ethernet, High-Level Data Link Control (HLDC), MPLS, IPv4 and IPv6 Internet Protocol, some form of address resolution between services of the same layer may be necessary. However, address resolution between devices using different services may not be possible in certain instances, such as during the initial setup through the pseudo-LAN or when an intermediate service is not active.
- ATM Asynchronous Transfer Mode
- FR Frame Relay
- Ethernet High-Level Data Link Control
- HLDC High-Level Data Link Control
- MPLS IPv4 and IPv6 Internet Protocol
- Various embodiments may relate to a method of a provider service access point (SAP) determining an address of a customer SAP.
- the method may include the provider SAP determining that a virtual leased line (VLL) service connecting a second customer SAP and the first customer SAP is not active and using its media access control (MAC) address to create a substitute IPv6 link local address, wherein the substitute IPv6 link local address acts as the IPv6 link local address for the second customer SAP.
- the method may also include the provider SAP establishing an IPv6CP session with the first customer SAP using the substitute IPv6 link local address.
- VLL virtual leased line
- MAC media access control
- the provider SAP may receive a Neighbor Solicitation packet or Neighbor Advertisement packet over the VLL service, wherein the established IPv6CP session triggered the VLL service to become active, extract from the Neighbor Solicitation packet or Neighbor Advertisement packet a true IPv6 link local address for the second customer SAP; and renegotiate the IPv6CP session, wherein the true IPv6 link local address replaces the substitute IPv6 link local address.
- Various embodiments may also relate to a system of determining an address of a customer service access point (SAP).
- SAP customer service access point
- the system may include a first customer SAP connected to a packet data network that includes a true IPv6 link local address.
- the system may also include a second customer SAP that solicits the true IPv6 link local address when a virtual leased line (VLL) service between the first and second customer SAPs is not active.
- VLL virtual leased line
- the system may also include a provider SAP connected to the second customer SAP and the packet data network that determines when the VLL service connecting a first and second customer SAP is not active, uses its media access control (MAC) address to create a substitute IPv6 link local address, wherein the substitute IPv6 link local address acts as the IPv6 link local address for the first customer SAP, establishes an IPv6CP session with the second customer SAP using the substitute IPv6 link local address, receives a Neighbor Solicitation packet or Neighbor Advertisement packet over the VLL service, wherein the established IPv6CP session triggered the VLL service to become active, and extracts, from the Neighbor Solicitation packet or Neighbor Advertisement packet, a true IPv6 address for the first customer SAP, and reestablishes the IPv6CP session, wherein the true IPv6 link local address replaces the substitute IPv6 link local address.
- MAC media access control
- various exemplary embodiments enable the management of addresses when establishing a service.
- the system may enable consistent, reliable service that may react properly when a provider SAP does not have the far-end customer address stored.
- FIG. 1 illustrates an exemplary embodiment of the pseudo-local area network (LAN) through a packet data network
- FIG. 2 illustrates an exemplary datapath for a Point-to-Point Protocol (PPP) customer edge service access point (SAP);
- PPP Point-to-Point Protocol
- SAP customer edge service access point
- FIG. 3 illustrates an exemplary datapath for a Frame Relay (FR) customer edge SAP
- FIG. 4 illustrates an exemplary flowchart for determining an address for a far-end customer edge SAP through the packet data network.
- FIG. 1 illustrates an exemplary embodiment of the pseudo-local area network (LAN) through a packet data network.
- communications system 100 includes a packet data network 101 , customer edge (CE) service access providers (SAPs) 111 - 114 , provider edge (PE) SAPs 121 - 122 , pseudowire 130 , and local connections 131 - 134 .
- CE customer edge
- SAPs service access providers
- PE provider edge
- Pseudowire 130 may be established through packet data network 101 to connect PE SAPs 121 , 122 , which may, in turn, establish a pseudo-local area network (pseudo-LAN), Internet Protocol LAN service (IPLS), virtual private wire service (VPWS), or virtual private network (VPN) that includes CE SAPs 111 - 114 and PE SAPs 121 , 122 .
- communications system 100 may include a VPWS that includes the SAPs 111 - 114 .
- the communications network 100 may be a network incorporating hardware dedicated to a customer entity.
- the devices in the communications network 100 may be configured such that the devices 111 - 114 , 121 - 122 in the communications network 100 occupy the same address space. This may include devices that connect directly to each other at the same site and may also include devices located at two different sites that communicate with each other through the packet data network 101 .
- the devices may be located behind the same security boundary, which may isolate devices within the boundary from outside devices, with some control of communications at the border between such devices.
- Packet data network 101 may be a packet-switched network operating in accordance with a packet-based protocol, such as Transmission Control Protocol/Internet Protocol (TCP/IP), Multiprotocol Label Switching (MPLS), Asynchronous Transfer Mode (ATM), Frame Relay (FR), Ethernet, Provider Backbone Transport (PBT), High-Level Data Link Control (HDLC), or any other suitable packet-based protocol that will be apparent to one of skill in the art. More specifically, data packet network 101 may communicate using Layer 2 or Layer 3 protocols, such as MPLS or IPv4 and IPv6 Internet protocol.
- TCP/IP Transmission Control Protocol/Internet Protocol
- MPLS Multiprotocol Label Switching
- ATM Asynchronous Transfer Mode
- FR Frame Relay
- Ethernet Ethernet
- PBT Provider Backbone Transport
- HDLC High-Level Data Link Control
- Layer 2 or Layer 3 protocols such as MPLS or IPv4 and IPv6 Internet protocol.
- CE service access points 111 - 114 may be devices or nodes in the communications network 100 .
- CE SAPs 111 - 114 may be network nodes or devices, such as routers or switches, that may be configured to transmit packets to other devices, such as other CE SAPs in the pseudo-LAN or provider edge SAPs.
- CE SAPs 111 - 114 may be capable of communications with other devices within and outside of the pseudo-LAN, using multiple layers of the OSI reference model, such as, for example, Layer 3 communications using MPLS (L3 MPLS) or Layer 2 communications using Ethernet and Virtual Private LAN Service (VPLS).
- L3 MPLS MPLS
- VPLS Virtual Private LAN Service
- Each of the CE SAPs may include a similar address space.
- CE SAPs 111 - 114 may share common portion of an IPv6 prefix, such as “2001:fc3:85a7::812e:e70:,” with specific addresses within the address space.
- CE SAP 111 may have, for example, “7334/128” as the remaining portion of the IPv6 address, while CE SAP 112 may have “7335/128” as its remaining portion.
- PE SAP 121 - 122 may be a node or device in the communications network 100 , such as a router, switch, or similar hardware device located on the edge of the packet data network 101 .
- PE SAPs 121 - 122 may be configured to receive packets from the CE SAPs 111 - 114 and transmit these packets to other devices through direct connections, such as 131 - 134 , or through the packet data network 101 to other devices through intermediaries, such as other PE SAPs 121 - 122 .
- Pseudowire 130 may be an embodiment of a service that transmits a packet over a packet-switching network.
- Pseudowire 130 may be, for example, a pseudowire end-to-end (PWE3) that transports customer data packets over an MPLS network.
- PWE3 pseudowire end-to-end
- the pseudowire 130 may only transport packets between devices of the same type or using the same service.
- the pseudowire 130 may also transport packets between devices of a different type or using a different service. This may occur, for example, when the packets' payload consists solely of IP datagrams.
- Local connections 131 - 134 may be wired or wireless connections or attachment circuits that enable the transfer of packets from the CE SAPs 111 - 114 to the PE SAPs 121 - 122 , respectively. Local connections 131 - 134 may be configured to support one or more services that support the transfer of packets between devices, such as, for example, TCP/IP, MPLS, ATM, FR, Ethernet, PBT, and HDLC.
- the PE SAP 121 may include one or more services to connect to the CE SAPs 111 , 113 , 114 .
- the local connection between the CE SAP 111 and the PE SAP 121 may be a Frame Relay (FR) link.
- FR Frame Relay
- the PE SAP 121 may connect with the CE SAPs 111 , 113 , and 114 . When connected, the PE SAP 121 may obtain the addresses of each CE SAP 111 , 113 , 114 . PE SAP 121 may obtain at least one address associated with the CE SAP 111 , for example, upon receipt of an Inverse Neighbor Solicitation message originating from the CE SAP 111 .
- the Inverse Neighbor Solicitation message may be a request for another device from which the CE SAP 111 does not already have an address, such as, for example CE SAP 112 .
- the addresses of the CE SAPs 111 , 113 , 114 may include, for example, the IPv6 address, the data link connection identifier (DLCI), and/or the MAC address.
- the PE SAP 121 may store each of the obtained addresses.
- PE SAP 121 may, for example, store an obtained IPv6 address for the CE SAP 111 in an Address Resolution Protocol (ARP) Cache that may be included with the PE SAP 121 .
- ARP Address Resolution Protocol
- the PE SAP 121 may then include at least one of the stored addresses associated with the CE SAP 112 in an Inverse Neighbor Advertisement sent back to the CE SAP 111 .
- PE SAP 121 may have already stored at least one address associated with CE SAP 112 as a result of receiving a Neighbor Solicitation message from the CE SAP 112 .
- PE SAP 121 may have received the Neighbor Solicitation originating from CE SAP 112 when the pseudowire between the PE SAP 121 and the PE SAP 122 has been established in response to the establishment of a service.
- service establishment may include, for example, establishing a Virtual Leased Line (VLL) for the CE SAPs 111 - 114 within the communications network 100 .
- VLL Virtual Leased Line
- the pseudowire may not already be established for the PE SAP 121 to receive Neighbor Solicitation messages. This may occur, for example, during the initialization of a service, which may be in response or associated with an Inverse Neighbor Solicitation message originating from the CE SAP 111 .
- the PE SAP 121 has no address for the target device CE SAP 112 stored and will not reply to the Inverse Neighbor Solicitation.
- the PE SAP 121 may, in such instances, generate an address for the target device using known values, such as its own MAC address, and may thereafter modify the target address to the “true” address acquired once the service is properly established.
- the generated rule may enable a service to become established and may therefore allow a PE SAP 121 , 122 to receive Neighbor Solicitation messages from far-end devices and thus enables the PE SAPs 121 , 122 to store these values and return valid addresses upon further queries.
- FIG. 2 illustrates an exemplary datapath for a Point-to-Point Protocol (PPP) customer edge service access point (SAP).
- PE SAP 201 and PE SAP 202 may be similar to the PEs SAP 121 - 122 of the communications system 100 in FIG. 1 .
- PE SAPs 201 , 202 may receive and transmit messages to and from other devices (not shown), such as Neighbor Solicitation messages 211 and Neighbor Advertisement messages 212 , 213 .
- the PE SAPs 201 , 202 may perform ARP mediation, which may resolve Layer 2 addresses when different resolution protocols are used in the attachment circuits.
- a CE such as CE SAP 112 in the communications system 100 in FIG. 1
- no addresses for the constituent devices in the communications system are pre-configured, so the devices may perform address discovery at various stages in order to acquire the addresses (including the IPv6 address, link local address, and/or MAC address) of other devices in the communications system 200 .
- the PE SAP 202 may extract a MAC address and IP address (e.g., IPv6 address) of the source of the message, and may store the values of these addresses in memory, such as an Address Resolution Protocol (ARP) cache included with the PE SAP 202 .
- ARP Address Resolution Protocol
- PE SAP 202 may then send the Neighbor Solicitation message through the pseudowire 130 to the PE SAP 201 , which may also extract and store the addresses of the source device in its memory.
- the PE SAP 201 may use IPv6 Control Protocol (IPv6CP) negotiation 251 to bring up the PPP local connection 133 with the CE SAP 113 . This may trigger the PE SAP 201 to generate a Neighbor Advertisement 212 message and forward the Neighbor Advertisement message 212 through the pseudowire to the PE SAP 202 .
- IPv6CP IPv6 Control Protocol
- the PE 201 may copy a number of values from the Neighbor Solicitation message 211 .
- the PE SAP 201 may copy the link local address of the CE SAP 113 that was learned through the IPv6CP negotiation to use as the source address in the Neighbor Advertisement message 212 .
- PE SAP 201 may also add a Layer 2 address in the Neighbor Advertisement message (in the illustrative embodiment, a PPP Layer 2 address) and may copy the source IP address of the Neighbor Solicitation message as the destination IP address of the Neighbor Advertisement message.
- the PE SAP 201 may send the Neighbor Advertisement message 212 through the pseudowire to the PE SAP 202 .
- the PE SAP 201 may also bounce the IPv6CP SAP (in the illustrative example, CE SAP 113 ), using the IP address of the source CE SAP (e.g., CE SAP 112 ) to set a new link local address for the CE SAP 113 .
- the PE SAP 202 may replace the Layer 2 address of the Neighbor Advertisement message 212 with its own MAC address. In some embodiments, the PE SAP 202 may also extract the addresses of the source CE SAP 213 that triggered the generation of the Neighbor Advertisement message 212 and store the address values in its memory. After replacing this value, the PE SAP 202 may then forward the modified Neighbor Advertisement message 213 to the CE SAP 112 .
- the PE SAP 201 and/or the PE SAP 202 may not reply to the Neighbor Solicitation message 211 . This may occur, for example, when the service is not active, as the PE SAPs 201 , 202 would drop such messages. In such instances, the PE SAPs 201 , 202 may not acquire and store the addresses of far-end CE SAPs, as it would not receive either Neighbor Solicitation or Neighbor Advertisement messages 211 - 212 due to the pseudowire not being established. This action may occur in some embodiments, as it is desirable to refrain from establishing the pseudowire before the IPv6CP negotiation has completed.
- the needed far-end link local address for the proper negotiation is not known by the PE SAP 201 .
- the PE SAP 201 may therefore use its own MAC address to generate a temporary link local address in order to perform a proper IPv6CP negotiation 252 with the CE SAP 213 .
- the PE SAP 201 may subsequently receive Neighbor Solicitation and Advertisement messages 211 - 212 over the now-established pseudowire.
- PE SAP may then extract the actual link local address of the far-end CE SAP 112 .
- the PE SAP 201 may then use the actual link local address in an IPv6CP renegotiation 251 with the CE SAP 113 .
- the PE SAP 201 may need to add values due to the differing lengths of the MAC address and the IPv6 address, for example.
- the PE SAP 201 may insert two octets, such as 0xFF and 0xFE in the middle of the MAC address. This insertion may be between the company id and the vendor-supplied id of the MAC address, which should be known to a person of skill in the art.
- FIG. 3 illustrates an exemplary datapath for a Frame Relay (FR) customer edge SAP.
- the datapath for the communications system 300 is similar to the datapath for communications system 200 in FIG. 2 , except that the PE SAP 301 responds to an Inverse Neighbor Solicitation message 315 instead of PE SAP 201 initiating the IPv6CP negotiation, as the PE SAP 201 in Frame Relay does not initiate the address discovery process.
- FR Frame Relay
- the PE SAP 301 receives the Neighbor Solicitation message 311 over the pseudowire 130 originating from the CE SAP 112 . Meanwhile, the CE SAP 111 independently sends an Inverse Neighbor Solicitation message 315 to the PE SAP 301 .
- the Inverse Neighbor Solicitation message 315 may contain the address of the CE SAP 111 , including, for example, its IPv6 address, and its data link connection identifier (DLCI).
- DLCI data link connection identifier
- the PE SAP 301 may store the IPv6 address for the CE SAP 111 .
- the PE SAP 301 may reply to the Inverse Neighbor Solicitation message 315 with an Inverse Neighbor Advertisement message 316 .
- the Inverse Neighbor Advertisement message 316 may contain the IP address of the source of the Neighbor Solicitation message 311 and the local DLCI of the CE SAP 111 .
- the PE SAP 301 may not reply to the Inverse Neighbor Solicitation message 311 . This may occur, for example, when the PE SAP 301 has not received a Neighbor Solicitation message 311 due to, for example, the service not yet being established or active.
- the PE SAP 301 may generate an Inverse Neighbor Advertisement message 317 using a temporary IP address generated from its own MAC address in lieu of the IP address of the source of the Neighbor Solicitation message 311 . In such instances, the PE SAP 301 may, upon receipt of the Neighbor Solicitation message 311 , replace the temporary IP address in its storage and generate a subsequent Inverse Neighbor Advertisement message 316 with the actual IP source address.
- FIG. 4 illustrates an exemplary flowchart for determining an address for a far-end customer edge SAP through the packet data network.
- PE SAP 201 may perform method 400 , for example, when initiating an IPv6CP negotiation 252 with a CE SAP 113 over a PPP attachment circuit 133 or generating an Inverse Neighbor Advertisement message 317 through an FR attachment circuit 131 with a CE SAP 111 .
- Method 400 begins at step 401 and continues to step 403 , where the PE SAP 201 determines whether the service is active.
- the PE SAP 201 may receive and process Neighbor Solicitation messages 211 and may therefore acquire and store the actual local link address of the far-end CE SAP 112 upon receipt of the Neighbor Solicitation message 211 .
- the PE SAP 201 may proceed to step 409 ; otherwise, the PE SAP 201 in step 403 determines that the service is not active and proceeds to step 405 .
- the PE SAP 201 may generate a substitute link local address for the far-end CE SAP 112 .
- the PE SAP 201 may generate the substitute link local address from its own MAC address, adding octets to the middle of the MAC address to convert the value from a MAC address value to an IPv6 address value.
- the PE SAP 201 may generate the substitute link local address from other values, such as, for example, an unallocated IPv6 address in the address space of the pseudo-LAN.
- the PE SAP 201 may store the value of the substitute link local address in its memory, which may be, for example, and ARP cache.
- PE SAP 201 may then proceed to step 407 , where the PE SAP 201 initiates an IPv6CP negotiation with the local CE SAP 113 over an attachment circuit 113 using the generated substitute address.
- the PE SAP 201 may conduct similar ARP mediation techniques using the generated temporary address.
- Other ARP mediation techniques may include, for example generating an Inverse Neighbor Advertisement message 317 using the substitute address.
- the IPv6CP negotiation may cause an IPv6CP session to be up, which may cause the service to become active.
- the service once active, may also trigger the pseudowire to be established in some embodiments.
- the active service allows the PE SAP 201 in step 409 to receive and process Neighbor Solicitation or Advertisement messages 211 - 212 from the far-end CE SAP 112 .
- the PE SAP 201 may in step 411 determine whether the PE SAP 201 stored a substitute link local address for the CE SAP 112 that initiated the Neighbor Solicitation message 211 or Neighbor Advertisement message 212 .
- the PE SAP 201 in step 413 may replace the substitute link local address with the actual link local address extracted from the Neighbor Solicitation message 211 or the Neighbor Advertisement message 212 .
- the PE SAP 201 may initiate an IPv6CP negotiation with the local CE SAP 113 over the local attachment circuit 113 using the actual link local address.
- the IPv6CP negotiation may be similar to that step 407 .
- PE SAP 201 may perform other ARP mediations in a similar manner to the ARP mediations described in relation to step 407 , with the PE SAP 201 using the actual link local address.
- the PE SAP 201 may end the process 400 at step 417 .
- the illustrative embodiments therefore disclose a system and related method of bringing up an IPv6CP session between a pseudowire SAP and a CE SAP when the service is not active.
- the service By generating a substitute link local address for IPv6CP negotiation, the service enables proper ARP mediation even before the receipt of Neighbor Solicitation or Neighbor Advertisement messages, which may require a service to be active before a pseudowire SAP receives and/or extracts relevant information from them.
- various exemplary embodiments of the invention may be implemented in hardware and/or firmware. Furthermore, various exemplary embodiments may be implemented as instructions stored on a machine-readable storage medium, which may be read and executed by at least one processor to perform the operations described in detail herein.
- a machine-readable storage medium may include any mechanism for storing information in a form readable by a machine, such as a personal or laptop computer, a server, or other computing device.
- a machine-readable storage medium may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and similar storage media.
- any block diagrams herein represent conceptual views of illustrative circuitry embodying the principals of the invention.
- any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in machine readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
Abstract
Description
- This application is a continuation of application Ser. No. 12/843,492, filed on Jul. 26, 2010, the entire disclosure of which is hereby incorporated herein by reference for all purposes.
- Various exemplary embodiments disclosed herein relate generally to communications devices, specifically connectivity in a packet data network.
- In modern communications systems, various local devices and local networks may be attached to each other through a packet data network, such as an Internet Protocol (IP) or Multiprotocol Label Switching (MPLS) network. In some instances, a pseudo-local area network (pseudo-LAN) may be established between one or more devices through the packet data network with the use of various devices and techniques. One of the methods for creating such a pseudo-LAN may be the use of one or more pseudowires within the packet data network to connect devices on the edge of the network. Through such emulation of a
Layer 2 point-to-point (P2P) connection-oriented service, two devices connected through a packet-switching network may operate in a similar manner to, for example, devices sharing a common provider edge (PE) device. - Configuration of a pseudo-LAN regularly involves the management of devices connected within the pseudo-LAN, including, for example, the resolution of addresses for the devices once the service is established. While the pseudo-LAN may be able to support a variety of services, such as Asynchronous Transfer Mode (ATM), Frame Relay (FR), Ethernet, High-Level Data Link Control (HLDC), MPLS, IPv4 and IPv6 Internet Protocol, some form of address resolution between services of the same layer may be necessary. However, address resolution between devices using different services may not be possible in certain instances, such as during the initial setup through the pseudo-LAN or when an intermediate service is not active.
- In view of the foregoing, it would be desirable to have a communications system that enables address resolution between devices. In particular, it would be desirable to have a system capable of resolving addresses of applicable devices during initiation of a service through at least one pseudowire.
- In light of the present need for address resolution in a pseudo-local area network, a brief summary of various exemplary embodiments is presented. Some simplifications and omissions may be made in the following summary, which is intended to highlight and introduce some aspects of the various exemplary embodiments, but not to limit the scope of the invention. Detailed descriptions of a preferred exemplary embodiment adequate to allow those of ordinary skill in the art to make and use the inventive concepts will follow in the later sections.
- Various embodiments may relate to a method of a provider service access point (SAP) determining an address of a customer SAP. The method may include the provider SAP determining that a virtual leased line (VLL) service connecting a second customer SAP and the first customer SAP is not active and using its media access control (MAC) address to create a substitute IPv6 link local address, wherein the substitute IPv6 link local address acts as the IPv6 link local address for the second customer SAP. The method may also include the provider SAP establishing an IPv6CP session with the first customer SAP using the substitute IPv6 link local address. The provider SAP may receive a Neighbor Solicitation packet or Neighbor Advertisement packet over the VLL service, wherein the established IPv6CP session triggered the VLL service to become active, extract from the Neighbor Solicitation packet or Neighbor Advertisement packet a true IPv6 link local address for the second customer SAP; and renegotiate the IPv6CP session, wherein the true IPv6 link local address replaces the substitute IPv6 link local address.
- Various embodiments may also relate to a system of determining an address of a customer service access point (SAP). The system may include a first customer SAP connected to a packet data network that includes a true IPv6 link local address. The system may also include a second customer SAP that solicits the true IPv6 link local address when a virtual leased line (VLL) service between the first and second customer SAPs is not active. The system may also include a provider SAP connected to the second customer SAP and the packet data network that determines when the VLL service connecting a first and second customer SAP is not active, uses its media access control (MAC) address to create a substitute IPv6 link local address, wherein the substitute IPv6 link local address acts as the IPv6 link local address for the first customer SAP, establishes an IPv6CP session with the second customer SAP using the substitute IPv6 link local address, receives a Neighbor Solicitation packet or Neighbor Advertisement packet over the VLL service, wherein the established IPv6CP session triggered the VLL service to become active, and extracts, from the Neighbor Solicitation packet or Neighbor Advertisement packet, a true IPv6 address for the first customer SAP, and reestablishes the IPv6CP session, wherein the true IPv6 link local address replaces the substitute IPv6 link local address.
- It should be apparent that, in this manner, various exemplary embodiments enable the management of addresses when establishing a service. Particularly, by generating and subsequently modifying an address for a far-end device, the system may enable consistent, reliable service that may react properly when a provider SAP does not have the far-end customer address stored.
- In order to better understand various exemplary embodiments, reference is made to the accompanying drawings wherein:
-
FIG. 1 illustrates an exemplary embodiment of the pseudo-local area network (LAN) through a packet data network; -
FIG. 2 illustrates an exemplary datapath for a Point-to-Point Protocol (PPP) customer edge service access point (SAP); -
FIG. 3 illustrates an exemplary datapath for a Frame Relay (FR) customer edge SAP; and -
FIG. 4 illustrates an exemplary flowchart for determining an address for a far-end customer edge SAP through the packet data network. - Referring now to the drawings, in which like numerals refer to like components or steps, there are disclosed broad aspects of various exemplary embodiments.
-
FIG. 1 illustrates an exemplary embodiment of the pseudo-local area network (LAN) through a packet data network. In various exemplary embodiments,communications system 100 includes apacket data network 101, customer edge (CE) service access providers (SAPs) 111-114, provider edge (PE) SAPs 121-122,pseudowire 130, and local connections 131-134. Pseudowire 130 may be established throughpacket data network 101 to connect PESAPs PE SAPs communications system 100 may include a VPWS that includes the SAPs 111-114. - In some embodiments, the
communications network 100 may be a network incorporating hardware dedicated to a customer entity. In such embodiments, the devices in thecommunications network 100 may be configured such that the devices 111-114, 121-122 in thecommunications network 100 occupy the same address space. This may include devices that connect directly to each other at the same site and may also include devices located at two different sites that communicate with each other through thepacket data network 101. In some embodiments, the devices may be located behind the same security boundary, which may isolate devices within the boundary from outside devices, with some control of communications at the border between such devices. -
Packet data network 101 may be a packet-switched network operating in accordance with a packet-based protocol, such as Transmission Control Protocol/Internet Protocol (TCP/IP), Multiprotocol Label Switching (MPLS), Asynchronous Transfer Mode (ATM), Frame Relay (FR), Ethernet, Provider Backbone Transport (PBT), High-Level Data Link Control (HDLC), or any other suitable packet-based protocol that will be apparent to one of skill in the art. More specifically,data packet network 101 may communicate usingLayer 2 or Layer 3 protocols, such as MPLS or IPv4 and IPv6 Internet protocol. - Customer edge (CE) service access points (SAPs) 111-114 may be devices or nodes in the
communications network 100. CE SAPs 111-114 may be network nodes or devices, such as routers or switches, that may be configured to transmit packets to other devices, such as other CE SAPs in the pseudo-LAN or provider edge SAPs. CE SAPs 111-114 may be capable of communications with other devices within and outside of the pseudo-LAN, using multiple layers of the OSI reference model, such as, for example, Layer 3 communications using MPLS (L3 MPLS) orLayer 2 communications using Ethernet and Virtual Private LAN Service (VPLS). Each of the CE SAPs may include a similar address space. For example, CE SAPs 111-114 may share common portion of an IPv6 prefix, such as “2001:fc3:85a7::812e:e70:,” with specific addresses within the address space. CESAP 111 may have, for example, “7334/128” as the remaining portion of the IPv6 address, while CE SAP 112 may have “7335/128” as its remaining portion. - Provider edge (PE) SAP 121-122 may be a node or device in the
communications network 100, such as a router, switch, or similar hardware device located on the edge of thepacket data network 101. PE SAPs 121-122 may be configured to receive packets from the CE SAPs 111-114 and transmit these packets to other devices through direct connections, such as 131-134, or through thepacket data network 101 to other devices through intermediaries, such as other PE SAPs 121-122. - Pseudowire 130 may be an embodiment of a service that transmits a packet over a packet-switching network. Pseudowire 130 may be, for example, a pseudowire end-to-end (PWE3) that transports customer data packets over an MPLS network. In some embodiments, the
pseudowire 130 may only transport packets between devices of the same type or using the same service. In other embodiments, thepseudowire 130 may also transport packets between devices of a different type or using a different service. This may occur, for example, when the packets' payload consists solely of IP datagrams. - Local connections 131-134 may be wired or wireless connections or attachment circuits that enable the transfer of packets from the CE SAPs 111-114 to the PE SAPs 121-122, respectively. Local connections 131-134 may be configured to support one or more services that support the transfer of packets between devices, such as, for example, TCP/IP, MPLS, ATM, FR, Ethernet, PBT, and HDLC. In the illustrative embodiment, the
PE SAP 121 may include one or more services to connect to theCE SAPs PE SAP 121 may be a Frame Relay (FR) link. - Having described the components of the
communications network 100, a brief summary of the operation of thecommunications network 100 will be provided. It should be apparent that the following description is intended to provide an overview of the operation of the communications network and is therefore a simplification in some respects. The detailed operation of thecommunications network 100 will be described in further detail below in relation to, for exampleFIGS. 2-4 . - According to various exemplary embodiments, the
PE SAP 121 may connect with theCE SAPs PE SAP 121 may obtain the addresses of eachCE SAP PE SAP 121 may obtain at least one address associated with theCE SAP 111, for example, upon receipt of an Inverse Neighbor Solicitation message originating from theCE SAP 111. The Inverse Neighbor Solicitation message may be a request for another device from which theCE SAP 111 does not already have an address, such as, forexample CE SAP 112. - The addresses of the
CE SAPs PE SAP 121 may store each of the obtained addresses.PE SAP 121 may, for example, store an obtained IPv6 address for theCE SAP 111 in an Address Resolution Protocol (ARP) Cache that may be included with thePE SAP 121. When thePE SAP 121 already has the address forCE SAP 112 stored, thePE SAP 121 may then include at least one of the stored addresses associated with theCE SAP 112 in an Inverse Neighbor Advertisement sent back to theCE SAP 111.PE SAP 121 may have already stored at least one address associated withCE SAP 112 as a result of receiving a Neighbor Solicitation message from theCE SAP 112.PE SAP 121 may have received the Neighbor Solicitation originating fromCE SAP 112 when the pseudowire between thePE SAP 121 and thePE SAP 122 has been established in response to the establishment of a service. Such service establishment may include, for example, establishing a Virtual Leased Line (VLL) for the CE SAPs 111-114 within thecommunications network 100. - In some instances, however, the pseudowire may not already be established for the
PE SAP 121 to receive Neighbor Solicitation messages. This may occur, for example, during the initialization of a service, which may be in response or associated with an Inverse Neighbor Solicitation message originating from theCE SAP 111. In such instances, thePE SAP 121 has no address for the targetdevice CE SAP 112 stored and will not reply to the Inverse Neighbor Solicitation. As will be discussed in further detail below, thePE SAP 121 may, in such instances, generate an address for the target device using known values, such as its own MAC address, and may thereafter modify the target address to the “true” address acquired once the service is properly established. In such embodiments, the generated rule may enable a service to become established and may therefore allow aPE SAP PE SAPs -
FIG. 2 illustrates an exemplary datapath for a Point-to-Point Protocol (PPP) customer edge service access point (SAP).PE SAP 201 andPE SAP 202 may be similar to the PEs SAP 121-122 of thecommunications system 100 inFIG. 1 .PE SAPs Neighbor Solicitation messages 211 andNeighbor Advertisement messages PE SAPs Layer 2 addresses when different resolution protocols are used in the attachment circuits. - When a service is active, a CE, such as
CE SAP 112 in thecommunications system 100 inFIG. 1 , may send aNeighbor Solicitation message 211 to thePE SAP 202 in order to perform address discovery. In some embodiments, no addresses for the constituent devices in the communications system are pre-configured, so the devices may perform address discovery at various stages in order to acquire the addresses (including the IPv6 address, link local address, and/or MAC address) of other devices in thecommunications system 200. Upon receipt of theNeighbor Solicitation message 211, thePE SAP 202 may extract a MAC address and IP address (e.g., IPv6 address) of the source of the message, and may store the values of these addresses in memory, such as an Address Resolution Protocol (ARP) cache included with thePE SAP 202. -
PE SAP 202 may then send the Neighbor Solicitation message through thepseudowire 130 to thePE SAP 201, which may also extract and store the addresses of the source device in its memory. In some embodiments, thePE SAP 201 may use IPv6 Control Protocol (IPv6CP)negotiation 251 to bring up the PPPlocal connection 133 with theCE SAP 113. This may trigger thePE SAP 201 to generate aNeighbor Advertisement 212 message and forward theNeighbor Advertisement message 212 through the pseudowire to thePE SAP 202. - When generating the
Neighbor Advertisement message 212, thePE 201 may copy a number of values from theNeighbor Solicitation message 211. For example, thePE SAP 201 may copy the link local address of theCE SAP 113 that was learned through the IPv6CP negotiation to use as the source address in theNeighbor Advertisement message 212.PE SAP 201 may also add aLayer 2 address in the Neighbor Advertisement message (in the illustrative embodiment, aPPP Layer 2 address) and may copy the source IP address of the Neighbor Solicitation message as the destination IP address of the Neighbor Advertisement message. Once theNeighbor Advertisement message 212 is created, thePE SAP 201 may send theNeighbor Advertisement message 212 through the pseudowire to thePE SAP 202. In some embodiments, thePE SAP 201 may also bounce the IPv6CP SAP (in the illustrative example, CE SAP 113), using the IP address of the source CE SAP (e.g., CE SAP 112) to set a new link local address for theCE SAP 113. - Upon receipt of the
Neighbor Advertisement message 212, thePE SAP 202 may replace theLayer 2 address of theNeighbor Advertisement message 212 with its own MAC address. In some embodiments, thePE SAP 202 may also extract the addresses of thesource CE SAP 213 that triggered the generation of theNeighbor Advertisement message 212 and store the address values in its memory. After replacing this value, thePE SAP 202 may then forward the modifiedNeighbor Advertisement message 213 to theCE SAP 112. - In some embodiments, the
PE SAP 201 and/or thePE SAP 202 may not reply to theNeighbor Solicitation message 211. This may occur, for example, when the service is not active, as thePE SAPs PE SAPs CE SAP 213, the needed far-end link local address for the proper negotiation is not known by thePE SAP 201. - In some embodiments, the
PE SAP 201 may therefore use its own MAC address to generate a temporary link local address in order to perform aproper IPv6CP negotiation 252 with theCE SAP 213. As theIPv6CP negotiation 252 may trigger the service to become active, thePE SAP 201 may subsequently receive Neighbor Solicitation and Advertisement messages 211-212 over the now-established pseudowire. PE SAP may then extract the actual link local address of the far-end CE SAP 112. Once the actual link local address of the far-end CE SAP 112 is known, thePE SAP 201 may then use the actual link local address in anIPv6CP renegotiation 251 with theCE SAP 113. - When generating the temporary link local address from its MAC address, the
PE SAP 201 may need to add values due to the differing lengths of the MAC address and the IPv6 address, for example. For example, thePE SAP 201 may insert two octets, such as 0xFF and 0xFE in the middle of the MAC address. This insertion may be between the company id and the vendor-supplied id of the MAC address, which should be known to a person of skill in the art. -
FIG. 3 illustrates an exemplary datapath for a Frame Relay (FR) customer edge SAP. The datapath for thecommunications system 300 is similar to the datapath forcommunications system 200 inFIG. 2 , except that thePE SAP 301 responds to an InverseNeighbor Solicitation message 315 instead ofPE SAP 201 initiating the IPv6CP negotiation, as thePE SAP 201 in Frame Relay does not initiate the address discovery process. - In the illustrative embodiment, the
PE SAP 301 receives theNeighbor Solicitation message 311 over thepseudowire 130 originating from theCE SAP 112. Meanwhile, theCE SAP 111 independently sends an InverseNeighbor Solicitation message 315 to thePE SAP 301. The InverseNeighbor Solicitation message 315 may contain the address of theCE SAP 111, including, for example, its IPv6 address, and its data link connection identifier (DLCI). Upon receipt of the InverseNeighbor Solicitation message 315, thePE SAP 301 may store the IPv6 address for theCE SAP 111. - When the
PE SAP 301 has a previously stored address for the source of theNeighbor Solicitation message 311, thePE SAP 301 may reply to the InverseNeighbor Solicitation message 315 with an InverseNeighbor Advertisement message 316. The InverseNeighbor Advertisement message 316 may contain the IP address of the source of theNeighbor Solicitation message 311 and the local DLCI of theCE SAP 111. - In some embodiments, when the
PE SAP 301 does not have the address of the source of theNeighbor Solicitation message 311 previously stored, it may not reply to the InverseNeighbor Solicitation message 311. This may occur, for example, when thePE SAP 301 has not received aNeighbor Solicitation message 311 due to, for example, the service not yet being established or active. In some embodiments, thePE SAP 301 may generate an InverseNeighbor Advertisement message 317 using a temporary IP address generated from its own MAC address in lieu of the IP address of the source of theNeighbor Solicitation message 311. In such instances, thePE SAP 301 may, upon receipt of theNeighbor Solicitation message 311, replace the temporary IP address in its storage and generate a subsequent InverseNeighbor Advertisement message 316 with the actual IP source address. -
FIG. 4 illustrates an exemplary flowchart for determining an address for a far-end customer edge SAP through the packet data network.PE SAP 201 may perform method 400, for example, when initiating anIPv6CP negotiation 252 with aCE SAP 113 over aPPP attachment circuit 133 or generating an InverseNeighbor Advertisement message 317 through anFR attachment circuit 131 with aCE SAP 111. - Method 400 begins at
step 401 and continues to step 403, where thePE SAP 201 determines whether the service is active. When the service is active, thePE SAP 201 may receive and processNeighbor Solicitation messages 211 and may therefore acquire and store the actual local link address of the far-end CE SAP 112 upon receipt of theNeighbor Solicitation message 211. In such instances, thePE SAP 201 may proceed to step 409; otherwise, thePE SAP 201 instep 403 determines that the service is not active and proceeds to step 405. - In
step 405, thePE SAP 201 may generate a substitute link local address for the far-end CE SAP 112. In some embodiments, thePE SAP 201 may generate the substitute link local address from its own MAC address, adding octets to the middle of the MAC address to convert the value from a MAC address value to an IPv6 address value. In other embodiments, thePE SAP 201 may generate the substitute link local address from other values, such as, for example, an unallocated IPv6 address in the address space of the pseudo-LAN. In some embodiments, thePE SAP 201 may store the value of the substitute link local address in its memory, which may be, for example, and ARP cache. -
PE SAP 201 may then proceed to step 407, where thePE SAP 201 initiates an IPv6CP negotiation with thelocal CE SAP 113 over anattachment circuit 113 using the generated substitute address. In other embodiments, thePE SAP 201 may conduct similar ARP mediation techniques using the generated temporary address. Other ARP mediation techniques may include, for example generating an InverseNeighbor Advertisement message 317 using the substitute address. - After
step 407, the IPv6CP negotiation may cause an IPv6CP session to be up, which may cause the service to become active. The service, once active, may also trigger the pseudowire to be established in some embodiments. In some embodiments, the active service allows thePE SAP 201 instep 409 to receive and process Neighbor Solicitation or Advertisement messages 211-212 from the far-end CE SAP 112. - Upon receipt of the
Neighbor Solicitation message 211 orNeighbor Advertisement message 212 instep 409, thePE SAP 201 may instep 411 determine whether thePE SAP 201 stored a substitute link local address for theCE SAP 112 that initiated theNeighbor Solicitation message 211 orNeighbor Advertisement message 212. When the substitute link local address is stored in thePE SAP 201, thePE SAP 201 instep 413 may replace the substitute link local address with the actual link local address extracted from theNeighbor Solicitation message 211 or theNeighbor Advertisement message 212. - In
step 415, thePE SAP 201 may initiate an IPv6CP negotiation with thelocal CE SAP 113 over thelocal attachment circuit 113 using the actual link local address. The IPv6CP negotiation may be similar to thatstep 407. Similarly,PE SAP 201 may perform other ARP mediations in a similar manner to the ARP mediations described in relation to step 407, with thePE SAP 201 using the actual link local address. After the IPv6CP negotiation or renegotiation, thePE SAP 201 may end the process 400 atstep 417. - The illustrative embodiments therefore disclose a system and related method of bringing up an IPv6CP session between a pseudowire SAP and a CE SAP when the service is not active. By generating a substitute link local address for IPv6CP negotiation, the service enables proper ARP mediation even before the receipt of Neighbor Solicitation or Neighbor Advertisement messages, which may require a service to be active before a pseudowire SAP receives and/or extracts relevant information from them.
- It should be apparent from the foregoing description that various exemplary embodiments of the invention may be implemented in hardware and/or firmware. Furthermore, various exemplary embodiments may be implemented as instructions stored on a machine-readable storage medium, which may be read and executed by at least one processor to perform the operations described in detail herein. A machine-readable storage medium may include any mechanism for storing information in a form readable by a machine, such as a personal or laptop computer, a server, or other computing device. Thus, a machine-readable storage medium may include read-only memory (ROM), random-access memory (RAM), magnetic disk storage media, optical storage media, flash-memory devices, and similar storage media.
- It should be appreciated by those skilled in the art that any block diagrams herein represent conceptual views of illustrative circuitry embodying the principals of the invention. Similarly, it will be appreciated that any flow charts, flow diagrams, state transition diagrams, pseudo code, and the like represent various processes which may be substantially represented in machine readable media and so executed by a computer or processor, whether or not such computer or processor is explicitly shown.
- Although the various exemplary embodiments have been described in detail with particular reference to certain exemplary aspects thereof, it should be understood that the invention is capable of other embodiments and its details are capable of modifications in various obvious respects. As is readily apparent to those skilled in the art, variations and modifications can be affected while remaining within the spirit and scope of the invention. Accordingly, the foregoing disclosure, description, and figures are for illustrative purposes only and do not in any way limit the invention, which is defined only by the claims.
Claims (20)
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US13/859,856 US20130227156A1 (en) | 2010-07-26 | 2013-04-10 | Ipv6 address generation to trigger a virtual leased line service |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US12/843,492 US8468258B2 (en) | 2010-07-26 | 2010-07-26 | IPv6 generation to trigger a virtual leased line service |
US13/859,856 US20130227156A1 (en) | 2010-07-26 | 2013-04-10 | Ipv6 address generation to trigger a virtual leased line service |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/843,492 Continuation US8468258B2 (en) | 2010-07-26 | 2010-07-26 | IPv6 generation to trigger a virtual leased line service |
Publications (1)
Publication Number | Publication Date |
---|---|
US20130227156A1 true US20130227156A1 (en) | 2013-08-29 |
Family
ID=44925575
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/843,492 Active 2031-12-09 US8468258B2 (en) | 2010-07-26 | 2010-07-26 | IPv6 generation to trigger a virtual leased line service |
US13/859,856 Abandoned US20130227156A1 (en) | 2010-07-26 | 2013-04-10 | Ipv6 address generation to trigger a virtual leased line service |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US12/843,492 Active 2031-12-09 US8468258B2 (en) | 2010-07-26 | 2010-07-26 | IPv6 generation to trigger a virtual leased line service |
Country Status (6)
Country | Link |
---|---|
US (2) | US8468258B2 (en) |
EP (1) | EP2599286B1 (en) |
JP (1) | JP5602946B2 (en) |
KR (1) | KR20130032902A (en) |
CN (1) | CN103026692B (en) |
WO (1) | WO2012014067A2 (en) |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10027589B1 (en) * | 2016-06-30 | 2018-07-17 | Juniper Network, Inc. | Apparatus, system, and method for achieving redundancy and load-balancing across communication layers within networks |
US10412019B2 (en) | 2015-07-06 | 2019-09-10 | Futurewei Technologies, Inc. | Path computation element central controllers (PCECCs) for network services |
CN112398731A (en) * | 2019-08-15 | 2021-02-23 | 华为技术有限公司 | Method for processing message and first network equipment |
Families Citing this family (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US8824678B2 (en) * | 2011-04-05 | 2014-09-02 | Broadcom Corporation | MAC address anonymizer |
TWI532353B (en) * | 2013-07-26 | 2016-05-01 | 正文科技股份有限公司 | Method for establishing connection of community virtual network and network communication system thereof |
US9860169B1 (en) * | 2015-09-29 | 2018-01-02 | Juniper Networks, Inc. | Neighbor resolution for remote EVPN hosts in IPV6 EVPN environment |
US10361951B2 (en) * | 2016-03-31 | 2019-07-23 | Telefonaktiebolaget Lm Ericsson (Publ) | Pseudo-wire signaling framework using interior gateway protocols |
US11063899B1 (en) * | 2021-01-12 | 2021-07-13 | CYBERTOKA Ltd. | Methods and systems for discovering media access control (MAC) addresses |
Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060052099A1 (en) * | 2004-09-09 | 2006-03-09 | Parker Jeffrey L | Wireless protocol converter |
US20080212569A1 (en) * | 2005-07-19 | 2008-09-04 | Stephen Terrill | Method and Apparatus for Allocating Application Servers in an Ims |
US7525965B1 (en) * | 2005-06-30 | 2009-04-28 | Sun Microsystems, Inc. | Trick play for multicast streams |
US20100220714A1 (en) * | 2006-12-21 | 2010-09-02 | Bce Inc. | Method and system for managing internal and external calls for a group of communication clients sharing a common customer identifier |
US20110055362A1 (en) * | 2009-09-01 | 2011-03-03 | Konica Minolta Systems Laboratory, Inc. | Method and system for modifying and/or changing a mac id utilizing an ipv6 network connection |
US20110320619A1 (en) * | 2009-03-02 | 2011-12-29 | Nec Europe Ltd | Method for operating a network and a network |
Family Cites Families (7)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5884297A (en) * | 1996-01-30 | 1999-03-16 | Telefonaktiebolaget L M Ericsson (Publ.) | System and method for maintaining a table in content addressable memory using hole algorithms |
US7305481B2 (en) * | 2003-01-07 | 2007-12-04 | Hexago Inc. | Connecting IPv6 devices through IPv4 network and network address translator (NAT) using tunnel setup protocol |
US8175078B2 (en) * | 2005-07-11 | 2012-05-08 | Cisco Technology, Inc. | Redundant pseudowires between Ethernet access domains |
US7673061B2 (en) | 2006-03-28 | 2010-03-02 | Tellabs San Jose, Inc. | Method and apparatus for neighborhood discovery across disparate point-to-point networks |
US7953097B2 (en) * | 2009-01-09 | 2011-05-31 | Alcatel Lucent | Neighbour discovery protocol mediation |
US8503329B2 (en) * | 2009-08-05 | 2013-08-06 | Cisco Technology, Inc. | Signaling of attachment circuit status and automatic discovery of inter-chassis communication peers |
CN101662511B (en) * | 2009-10-10 | 2012-07-04 | 中国电信股份有限公司 | Network address distributing method, DHCP server, access system and method thereof |
-
2010
- 2010-07-26 US US12/843,492 patent/US8468258B2/en active Active
-
2011
- 2011-07-20 JP JP2013521245A patent/JP5602946B2/en not_active Expired - Fee Related
- 2011-07-20 WO PCT/IB2011/001872 patent/WO2012014067A2/en active Application Filing
- 2011-07-20 EP EP11781591.0A patent/EP2599286B1/en not_active Not-in-force
- 2011-07-20 KR KR1020137001980A patent/KR20130032902A/en not_active Application Discontinuation
- 2011-07-20 CN CN201180036501.XA patent/CN103026692B/en not_active Expired - Fee Related
-
2013
- 2013-04-10 US US13/859,856 patent/US20130227156A1/en not_active Abandoned
Patent Citations (6)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20060052099A1 (en) * | 2004-09-09 | 2006-03-09 | Parker Jeffrey L | Wireless protocol converter |
US7525965B1 (en) * | 2005-06-30 | 2009-04-28 | Sun Microsystems, Inc. | Trick play for multicast streams |
US20080212569A1 (en) * | 2005-07-19 | 2008-09-04 | Stephen Terrill | Method and Apparatus for Allocating Application Servers in an Ims |
US20100220714A1 (en) * | 2006-12-21 | 2010-09-02 | Bce Inc. | Method and system for managing internal and external calls for a group of communication clients sharing a common customer identifier |
US20110320619A1 (en) * | 2009-03-02 | 2011-12-29 | Nec Europe Ltd | Method for operating a network and a network |
US20110055362A1 (en) * | 2009-09-01 | 2011-03-03 | Konica Minolta Systems Laboratory, Inc. | Method and system for modifying and/or changing a mac id utilizing an ipv6 network connection |
Cited By (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US10412019B2 (en) | 2015-07-06 | 2019-09-10 | Futurewei Technologies, Inc. | Path computation element central controllers (PCECCs) for network services |
US10027589B1 (en) * | 2016-06-30 | 2018-07-17 | Juniper Network, Inc. | Apparatus, system, and method for achieving redundancy and load-balancing across communication layers within networks |
CN112398731A (en) * | 2019-08-15 | 2021-02-23 | 华为技术有限公司 | Method for processing message and first network equipment |
US11811900B2 (en) | 2019-08-15 | 2023-11-07 | Huawei Technologies Co., Ltd. | Packet processing method and first network device |
Also Published As
Publication number | Publication date |
---|---|
JP2013535909A (en) | 2013-09-12 |
EP2599286B1 (en) | 2015-04-22 |
JP5602946B2 (en) | 2014-10-08 |
EP2599286A2 (en) | 2013-06-05 |
KR20130032902A (en) | 2013-04-02 |
WO2012014067A2 (en) | 2012-02-02 |
WO2012014067A3 (en) | 2012-03-22 |
US8468258B2 (en) | 2013-06-18 |
CN103026692A (en) | 2013-04-03 |
CN103026692B (en) | 2016-01-13 |
US20120023242A1 (en) | 2012-01-26 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US20130227156A1 (en) | Ipv6 address generation to trigger a virtual leased line service | |
EP1648134B1 (en) | Network service selection and authentication and stateless auto-configuration in an IPv6 access network | |
JP5607617B2 (en) | Method for receiving data packets in IPv6 domain, and associated device and residential gateway | |
US8451844B2 (en) | Method of receiving a data packet coming from an IPv4 domain in an IPv6 domain, an associated device, and associated access equipment | |
EP2364543B1 (en) | Broadband network access | |
EP1693996B1 (en) | Automatic discovery of psuedo-wire peer addresses in ethernet-based networks | |
JP5362032B2 (en) | Neighbor discovery protocol mediation | |
US7653745B1 (en) | Method and apparatus for distributed network address translation processing | |
US9774530B2 (en) | Mapping of address and port (MAP) provisioning | |
US7707277B2 (en) | Method and system for configuring pseudowires using dynamic host configuration protocol (DHCP) messages | |
WO2001099354A1 (en) | Communication device including vpn accomodation function | |
WO2012083657A1 (en) | Packet processing method, system and customer premises equipment | |
WO2022068436A1 (en) | Service processing method and related device | |
US11552926B2 (en) | Method related to sending management IP address and system | |
TWI532353B (en) | Method for establishing connection of community virtual network and network communication system thereof | |
EP4030698A1 (en) | Packet processing method, device, system and apparatus as well as storage medium | |
WO2004100499A1 (en) | A communication network, a network element and communication protocol and method of address auto-configuration therefor | |
Hu et al. | RFC 8772 The China Mobile, Huawei, and ZTE Broadband Network Gateway (BNG) Simple Control and User Plane Separation Protocol (S-CUSP) | |
Shah et al. | Address Resolution Protocol (ARP) Mediation for IP Interworking of Layer 2 VPNs | |
Kompella | Internet Engineering Task Force (IETF) H. Shah, Ed. Request for Comments: 6575 Ciena Category: Standards Track E. Rosen, Ed. | |
Headquarters | Implementing IPv6 Addressing and Basic Connectivity |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: ALCATEL-LUCENT CANADA INC., CANADA Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:PIRBHAI, SHAFIQ;HART, NEIL D.;REEL/FRAME:030185/0689 Effective date: 20100810 Owner name: ALCATEL-LUCENT, FRANCE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNOR:ALCATEL-LUCENT CANADA INC.;REEL/FRAME:030185/0969 Effective date: 20110527 |
|
AS | Assignment |
Owner name: CREDIT SUISSE AG, NEW YORK Free format text: SECURITY AGREEMENT;ASSIGNOR:ALCATEL LUCENT;REEL/FRAME:030851/0345 Effective date: 20130719 |
|
AS | Assignment |
Owner name: ALCATEL LUCENT, FRANCE Free format text: RELEASE OF SECURITY INTEREST;ASSIGNOR:CREDIT SUISSE AG;REEL/FRAME:033677/0419 Effective date: 20140819 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |