WO2008024226A1 - Procédé et système d'interfonctionnement d'une liaison point à point et d'un système local - Google Patents

Procédé et système d'interfonctionnement d'une liaison point à point et d'un système local Download PDF

Info

Publication number
WO2008024226A1
WO2008024226A1 PCT/US2007/017928 US2007017928W WO2008024226A1 WO 2008024226 A1 WO2008024226 A1 WO 2008024226A1 US 2007017928 W US2007017928 W US 2007017928W WO 2008024226 A1 WO2008024226 A1 WO 2008024226A1
Authority
WO
WIPO (PCT)
Prior art keywords
lan
address
environment
host
frame
Prior art date
Application number
PCT/US2007/017928
Other languages
English (en)
Other versions
WO2008024226B1 (fr
Inventor
Jonathan Sadler
Original Assignee
Tellabs Operations, Inc.
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Tellabs Operations, Inc. filed Critical Tellabs Operations, Inc.
Publication of WO2008024226A1 publication Critical patent/WO2008024226A1/fr
Publication of WO2008024226B1 publication Critical patent/WO2008024226B1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L69/00—Network arrangements, protocols or services independent of the application payload and not provided for in the other groups of this subclass
    • H04L69/08—Protocols for interworking; Protocol conversion

Definitions

  • the present invention relates generally to interworking functions between different networks, and more particularly to methods and systems for interworking a point-to-point network and a local access network service.
  • LAN local area network
  • Ethernet a local area network
  • the company may provide an Ethernet service within the main office, but separately connect remote network equipment through routers that maintain point-to-point (P2P) links with the main office.
  • P2P links may be supported by a Digital Subscriber Loop (DSL) connection or leased lines such as Tl facilities to a router at the main office.
  • DSL Digital Subscriber Loop
  • PPP Point-to-Point Protocol
  • IP Internet Protocol
  • the PPP hosts may establish a PPP session by tunneling across a regional aggregation network using a Layer 2 Tunneling Protocol (L2TP) for delivery to a service network.
  • L2TP Layer 2 Tunneling Protocol
  • the service network at one or both ends of the PPP session is typically maintained by a different service provider than the service provider maintaining all or a portion of the regional aggregate network through which the PPP session is established.
  • an interworking device affords an interface between a point-to-point (P2P) environment and a local access network (LAN) environment.
  • the interworking device comprises a P2P frame transceiver adapted to communicate with an attached device utilizing frames formatted in accordance with a P2P protocol such as PPP.
  • a LAN frame transceiver is adapted to communicate, over a LAN environment, with LAN attached devices utilizing LAN frames formatted in accordance with a LAN protocol.
  • the P2P and LAN frames include network layer (NL) information associated with a common predefined network layer protocol.
  • a data forwarding module utilizes the NL information to map the client traffic from i) the P2P frames into the LAN environment and ii) the LAN frames into the P2P environment.
  • the NL information may include NL addresses.
  • the P2P and LAN frames may include at least one of automatic network layer address assignment information, fault handling information, P2P node identification information, local LAN traffic destination information and remote LAN traffic destination information.
  • the device may further include a P2P-to-network layer (P2P/NL) Address Assignment function that determines when the P2P frame includes a control protocol to request a network layer address.
  • P2P/NL P2P-to-network layer
  • IPCP Internet Protocol Control Protocol
  • the device may further comprise memory storing a table assisting the mapping of P2P endpoints into LAN addresses (e.g. MAC addresses).
  • This assist table would contain a LAN address and an NL address associated with a host on the P2P environment.
  • the data forwarding module utilizes the LAN and NL addresses to convey the NL traffic to and from the LAN environment.
  • a NL address analysis function may be provided that determines whether an NL address in the client traffic corresponds to a local LAN.
  • a control module may be included that assigns a LAN address to a physical link between the P2P interface and a host in the P2P environment.
  • a method for interfacing between a point-to-point (P2P) environment and a local area access network environment.
  • the method includes communicating with a P2P host utilizing P2P frames formatted in accordance with a P2P protocol and communicating, over a LAN environment, with a LAN host utilizing LAN frames formatted in accordance with a LAN protocol.
  • the P2P and LAN frames include client traffic having network layer information associated with a common predefined client level network layer protocol.
  • the method further includes utilizing the NL information to map the client traffic from at least one of i) the P2P frames into the LAN environment and ii) the LAN frames into the P2P environment.
  • the method may further comprise obtaining, from a LAN network layer address assignment server (e.g. a Dynamic Host Configuration Protocol (DHCP) server for LANs supporting an IP network layer) on the LAN environment, an NL address to be allocated for the P2P host.
  • a LAN network layer address assignment server e.g. a Dynamic Host Configuration Protocol (DHCP) server for LANs supporting an IP network layer
  • DHCP Dynamic Host Configuration Protocol
  • a P2P address request (e.g. as conveyed by IPCP in PPP when supporting an IP network layer) from the P2P host is received and, in response thereto, the method includes transmitting an NL address request over the LAN environment.
  • Figure 1 illustrates a block diagram of a network implementing methods and systems in accordance with exemplary embodiments of the present invention.
  • Figure 2 illustrates a block diagram of the modules, tables and functions within the interworking device in accordance with an exemplary embodiment of the present invention.
  • Figure 3 illustrates a block diagram of the control module and PPP and LAN frame transceivers in accordance with an exemplary embodiment of the present invention.
  • Figure 4 illustrates a flow sequence of the operations carried out to establish a physical link between a P2P host and the interworking device in accordance with an exemplary embodiment of the present invention.
  • Figure 5 illustrates a block diagram of the portion of the interworking device utilized to forward data from the P2P environment to the LAN environment in accordance with an exemplary embodiment of the present invention.
  • Figures 6a and 6b illustrate the flow sequence performed in connection with forwarding client traffic from the P2P environment to the local LAN service in the LAN environment in accordance with an exemplary embodiment of the present invention.
  • Figures 7a and 7b illustrate the flow sequence performed when forwarding client traffic from the P2P environment to a remote LAN service in accordance with an exemplary embodiment of the present invention.
  • Figure 8 illustrates a flow sequence in connection with the conveyance of client traffic from the LAN host to the P2P host in accordance with exemplary embodiment of the present invention.
  • Figure 9 illustrates a flow sequence carried out to shutdown a network layer in accordance with an exemplary embodiment of the present invention.
  • Figure 10 illustrates a flow sequence carried out to shutdown all communications across the P2P link in accordance with an exemplary embodiment of the present invention.
  • FIG. 1 illustrates a block diagram of a network implementing certain methods and systems in accordance with exemplary embodiments of the present invention.
  • the network is generally apportioned into a point-to-point (P2P) environment 112 and a local access network (LAN) environment 114 that interface with one another through an interworking device 116.
  • the P2P environment 112 includes one or more P2P hosts 118 that are separately joined to the interworking device 1 16 by individual dedicated links 120.
  • the LAN environment 114 includes one or more LAN services 122 and 124 that are joined to one another through a router 126.
  • the LAN service 122 represents a local LAN service as the interworking device 1 16 is provided directly connected to the LAN service 122.
  • the LAN service 124 represents a remote service in that the interworking device 116 is not directly connected to the LAN service 124, but instead must communicate through router 126.
  • the local LAN service 122 includes the interworking device 116, one or more LAN hosts 130, a LAN Network Layer Address Server 132 and optionally the router 126.
  • the LAN Network Layer Address Server 132 can be placed anywhere in the network, including incorporation into the interworking device 1 16 or on a network behind router 126. When arranged in this way, router 126 will provide a proxy function that allows the LAN Network Layer Address Server 132 to be reached as if it were directly connected to LAN service 122.
  • the interworking device 116 provides an interface between the P2P environment 112 and the LAN environment 114.
  • the P2P protocol of the P2P environment 112 represents one layer 2 (or server layer or data link layer of the Open Systems Interconnection (OSI) seven-layer model) protocol, while the LAN protocol of the LAN environment 114 represents another layer 2 protocol.
  • Common examples of P2P and LAN protocols are the Point-to-Point Protocol (PPP) defined in IETF RFC 1661 and Ethernet defined in IEEE 802.3.
  • PPP Point-to-Point Protocol
  • the P2P and LAN hosts 118 and 130 separately encapsulate client traffic within the layer 2 P2P and LAN frames, respectively.
  • the client traffic includes data packets formatted in accordance with a layer 3 (or client layer or network layer of the OSI seven -layer model) protocol, such as Internet Protocol (IP).
  • IP Internet Protocol
  • the interworking device 116 can provide a seamless client level interface between the respective P2P and LAN environments 112 and 114 utilizing the corresponding layer 2 protocols.
  • the interworking device 116 can be adapted to perform at least one of the functions of disassembling, analyzing and rebuilding the PPP and LAN frames based on the content of the client level traffic.
  • the interworking device 1 16 can be adapted to support control operations for establishing and terminating links within the P2P environment 112 and within the LAlS environment 114.
  • the interworking device 116 can be adapted to maintain the links while forwarding client traffic from LAN hosts 130 and client-layer routers 126 that attach the local LAN service 122 to the P2P hosts 118, and forwarding data from the P2P hosts 118 to the LAN hosts 130 attached to the local LAN service 122 or to the client-layer router 126, thereby facilitating access to remote LAN service 124.
  • the interworking device 116 communicates with the P2P environment 112 based on the PPP protocol, and communicates with the LAN environment 114 based on the Ethernet protocol.
  • the P2P host 1 18 and interworking device 116 can be adapted to encapsulate client traffic that includes control and data packets formatted in accordance with the client-level network layer (NL) protocol, within P2P frames for conveyance within P2P environment 112.
  • the interworking device 116 can also be adapted to operate with the LAN environment 114 to encapsulate the client traffic within LAN frames for conveyance within the LAN environment 1 14.
  • the interworking device 116 can also be adapted to map the client control and data packets between P2P and LAN frame structures in order to afford a seamless interface between the P2P environment 1 12 and the LAN environment 114.
  • FIG. 2 illustrates a block diagram of the modules, tables and functional blocks within an interworking device (such as interworking device 116 of Figure 1), in accordance with an exemplary embodiment of the present invention.
  • the interworking device includes a P2P frame transceiver 250 that is joined to links (such as links 120 of Figure 1), to send/receive P2P frames to/from P2P hosts (such as the P2P hosts 118 of Figure I) formatted in accordance with the applicable P2P protocol.
  • the P2P protocol represents an encapsulation protocol that is used to transport client traffic, defined in accordance with a client-layer protocol, over point-to-point serial links.
  • the client traffic may be encapsulated utilizing the IETF'S Point-to-Point Protocol (PPP).
  • PPP Point-to-Point Protocol
  • LCP Link Control Protocol
  • NCP Network Control Protocol
  • the Internet Protocol Control Protocol is the NCP for use with IP client traffic.
  • packets from each client-level network layer may be sent over the PPP link.
  • the PPP link will remain configured for communications until LCP or NCP frames close the PPP link or until some external event occurs such as, but not limited to, the failure of the P2P host, the PPP link, or the interworking function.
  • the interworking device can also include a LAN frame transceiver 252 that is adapted to communicate, over a LAN environment (such as the LAN environment 1 14 of Figure 1), with various nodes, including at least one of a LAN host (such as the LAN host 130 of Figure 1), a router (such as the router 126 of Figure 1), a LAN Network Layer Address Assignment server (such as the LAN Network Layer Address Assignment server 132 of Figure 1) and other interconnecting media.
  • a LAN host such as the LAN host 130 of Figure 1
  • a router such as the router 126 of Figure 1
  • a LAN Network Layer Address Assignment server such as the LAN Network Layer Address Assignment server 132 of Figure 1
  • Each of the LAN host, router, LAN/NL Address Assignment server and interworking device have a unique LAN address.
  • the LAN protocol in use may be Ethernet, which uses Media Access Control (MAC) address for LAN addresses.
  • MAC Media Access Control
  • the LAN Network Layer Address Assignment server may be a Dynamic Host Configuration Protocol (DHCP) server.
  • DHCP Dynamic Host Configuration Protocol
  • other types of nodes may be joined to a LAN service (such as the LAN service 122 of Figure 1), such as Data Terminal Equipment (DTE) that represent sources or destinations of data frames and Data Communication Equipment (DCE) that represent intermediate network devices that receive and forward frames across the LAN service.
  • DTE Data Terminal Equipment
  • DCE Data Communication Equipment
  • the DTE may represent PCs, workstations, file servers, print servers and the like
  • the DCE may represent repeaters, network switches, routers, interface cards, modems and the like.
  • a control module 254 manages and conducts the control operations for establishing, maintaining and terminating links within a P2P environment (such as the P2P environment 112 of Figure 1) and within a LAN environment (such as the LAN environment 114 of Figure 1) based on client-level NL information that is defined in accordance with a common predefined client-level network layer protocol.
  • the predefined client-level network layer protocol extends across both of the P2P and LAN environments.
  • the NL information may include, among other things, source and destination Network Layer addresses (such as IP addresses), address assignment information, fault handling information, P2P node identification information, local LAN traffic destination information and remote LAN traffic destination information.
  • Figure 2 illustrates separate modules for exemplary data forwarding operations.
  • Data forwarding module 256 supports conveyance of client traffic from the LAN environment 114 to the P2P environment 112.
  • Data forwarding module 258 supports conveyance of client traffic from the P2P environment to a local LAN service (such as the LAN service 122 of Figure 1) and to a remote LAN service (such as the LAN service 124 of Figure 1).
  • the interworking device can also include a Network Layer address to LAN address table 262 and furthermore a P2P endpoint assist (P2P/NL/MAC) table 264.
  • the Network Layer address to LAN address table 262 can include a LAN address field 266 and a Network Layer address field 268 that store LAN and Network Layer addresses in a one-to-one relation with one another.
  • the P2P Endpoint Assist table 264 can include a P2P link physical port field 270, a P2P host NL address field 272, an NL subnet field 274, a LAN address field 276, and a LAN Default Router field 278 that store corresponding information also in a one to one relation to one another.
  • the fields 266 -278, Network Layer address to LAN address table 262 and P2P Endpoint Assist table 264 are described below in more detail.
  • the control module 254 can communicates with P2P hosts (such as the P2P hosts 1 18 of Figure 1), LAN hosts (such as the LAN hosts 130 of Figure 1), a router (such as the router 126 of Figure 1) and a DHCP server (such as the DHCP server 132 of Figure 1) in order to build and maintain the Network Layer address to LAN address and P2P Endpoint Assist tables 262 and 264.
  • P2P hosts such as the P2P hosts 1 18 of Figure 1
  • LAN hosts such as the LAN hosts 130 of Figure 1
  • a router such as the router 126 of Figure 1
  • a DHCP server such as the DHCP server 132 of Figure 1
  • the data forwarding modules 256 and 258 access and update the Network Layer address to LAN address and P2P Endpoint Assist tables 262 and 264 in order to map client traffic packets between the P2P and LAN environments.
  • the interworking device can also maintain a LAN address pool 248 and a pending traffic queue 246.
  • FIG. 3 illustrates a block diagram of a control module (such as control module 254 of Figure 2) and P2P and LAN frame transceivers (such as the P2P and LAN frame transceivers 250 and 252 of Figure 2), in accordance with an exemplary embodiment of the present invention.
  • the P2P frame transceiver 250 receives the P2P frames and extracts NL information from the P2P frames.
  • the P2P frame transceiver 250 loads client traffic and NL information into a P2P frame and sends the P2P frame over the corresponding link.
  • the LAN frame transceiver 252 receives LAN frames and extracts client traffic and NL information therefrom.
  • the control module (such as control module 254 of Figure 2) includes a P2P/NL Address Assignment function 282 that communicates with a P2P host (such as each of the P2P hosts 1 18 of Figure 1) in accordance with an applicable P2P Protocol to coordinate configuration of Network Layer addresses on the P2P host.
  • a P2P host such as each of the P2P hosts 1 18 of Figure 1
  • IPCP IP Control Protocol
  • the control module also includes a LAN/NL Address Assignment function 284.
  • the P2P/NL Address Assignment function 282 communicates with the LAN/NL Address Assignment function 284 that in turn communicates with a LAN/NL Address assignment server (such as the LAN/NL Address assignment server 132 of Figure 1) to obtain a Network Layer address to be allocated to the requesting P2P host.
  • a LAN/NL Address assignment server such as the LAN/NL Address assignment server 132 of Figure 1
  • DHCP Dynamic Host Configuration Protocol
  • Figures 4, 6a through 10 are flow sequences illustrating methods according to exemplary embodiments of the present invention.
  • the techniques illustrated in these figures may be performed sequentially, in parallel or in an order other than that which is described. It should be appreciated that not all of the techniques described are required to be performed, that additional techniques may be added, and that some of the illustrated techniques may be substituted with other techniques.
  • Figure 4 illustrates a flow sequence of the operations carried out by a control module (such as control module 254 of Figure 2) in connection with establishing a physical link between a P2P host (such as P2P host 118 of Figure 1) and an interworking device (such as interworking device 1 16 of Figure 1), as well as the allocation of an NL address to be used in connection with client traffic sent/received to/from the P2P host, in accordance with an exemplary embodiment of the present invention.
  • the flow sequence is organized into four columns for operations carried out by the P2P host, the interworking device,, a LAN/NL Address Assignment server (such as the LAN/NL Address Assignment server 132 of Figure 1) and a LAN host (such as the LAN host 130 of Figure 1).
  • the P2P host establishes a link (such as link 120 of Figure 1) with the interworking device.
  • the interworking device stores a unique identifier for the physical port to which the link is joined to the interworking device.
  • the unique physical port ID is saved in a P2P link physical port field (such as the P2P link physical port field 270 of Figure 2) of an P2P Endpoint Assist table (such as the P2P Endpoint Assist table 264 of Figure 2).
  • the control module also allocates a unique LAN address from a LAN Address Pool (such as the LAN Address Pool 248 of Figure 2) for use by hosts on a LAN service (such as the LAN service 122 of Figure 1) when contacting the P2P host and records the LAN address in a LAN address field (such as LAN address field 276 of Figure 2) of the P2P Endpoint assist table in a one-to-one relation with the unique physical port ID saved in the P2P link physical port field.
  • a unique LAN address from a LAN Address Pool such as the LAN Address Pool 248 of Figure 248
  • a LAN service such as the LAN service 122 of Figure 1
  • the P2P host starts to configure its network layer and requests that an NL address be assigned thereto for use in connection with client traffic.
  • the NL address request is sent by the P2P host (e.g. as an IPCP address request when the client layer is an IP network layer and the P2P protocol is the PPP protocol).
  • a P2P/NL Address Assignment function (such as the P2P/NL Address Assignment function 282 of Figure 3) receives the NL address request and, in response thereto, directs a LAN/NL Address Assignment function (such as the LAN/NL Address Assignment function 284 of Figure 3) to obtain an NL address from the LAN service to be allocated for use by the P2P host.
  • the LAN/NL Address Assignment function transmits a request over the LAN service requesting one or more LAN/NL Address Assignment server to provide an available NL address.
  • the LAN/NL Address Assignment server responds with an available NL addresses.
  • the LAN/NL Address Assignment function selects one of the available NL addresses and provides it to the P2P/NL Address Assignment function.
  • the P2P/NL Address Assignment function builds an NL address assignment reply including the selected NL address. The reply is built in accordance with the P2P protocol in use on the link and passed to a P2P frame transceiver (such as the P2P frame transceiver 250 of Figure 2) to be sent to the P2P host.
  • the P2P host reviews the NL address offer and approves the address provided by the interworking device and stores the selected NL address for use as the source NL address in connection with subsequent client traffic sent from the P2P host. The approval is communicated back via an acknowledgement to the interworking device, and the Network Layer is considered up, as indicated at 422.
  • the P2P/NL Address Assignment function informs the LAN/NL Address Assignment function of the acceptance of the NL address by the P2P host.
  • the LAN/NL Address Assignment function informs the LAN/NL Address Assignment server of the selected NL address.
  • the LAN/NL Address Assignment server removes the selected NL address from the list of available NL addresses.
  • an acknowledgement is sent by the LAN/NL Address Assignment server back to the interworking device along with the LAN/NL prefix mask and the NL address of the Default Router (such as router 126 of Figure 1).
  • the LAN/NL Address Assignment function then stores the selected NL address, its prefix mask and the NL address of the Default Router, in the P2P Endpoint Assist table (in fields such as the NL address field 272, the NL SubNet field 274 and the LAN Default Router field 278 of Figure 2) in a one-to-one relation with the corresponding LAN address stored in the LAN address field and P2P physical port ID stored in the P2P link physical port field.
  • NL/LAN Addr table (such as the NL/LAN Addr table 262 of Figure 2) for the Default Router NL address containing the provided LAN address.
  • the interworking device provides a control operation for establishing an NL address to be used by a P2P host in connection with a LAN service (such as LAN service 122 of Figure 1), where the request for the NL address originates utilizing the P2P/NL Address Assignment protocol yet is assigned utilizing the LAN/NL Address Assignment protocol.
  • a LAN service such as LAN service 122 of Figure 1
  • an IP address (a 32-bit address typically written in the format xxx.xx.xx.xxx) prefix is associated with a LAN service (such as the LAN service 122 of Figure 1).
  • the prefix may be 101.11.01.0 with a mask length of 24-bits.
  • any destination IP address that begins with the 24-bit prefix 101.1 1.01.0 would correspond to a device on the LAN service.
  • a DHCP server acting as a LAN/NL Address Assignment Server (such as the LAN/NL Address Assignment Server 132 of Figure 1), would indicate that the mask for the local LAN service was 24-bits in length (from the most significant, or left end of the IP address).
  • any client traffic with a destination IP address having the IP address prefix 101.11.01 would be directed to a destination device on the LAN service.
  • Any client traffic with a destination IP address differing from the IP address prefix 101.11.01 would not lie on the LAN service. Instead, the client traffic would need to be routed, through a default router (such as router 126 of Figure 1) to reach other IP subnetworks, including a remote LAN service (such as remote LAN service 124 of Figure 1).
  • a default router such as router 126 of Figure 1
  • remote LAN service such as remote LAN service 124 of Figure 1
  • Figure 5 illustrates a block diagram of a portion of an interworking device (such as interworking device in Figure 2) utilized to forward data from a P2P environment (such as the P2P environment 112 of Figure 1) to a LAN environment (such as LAN environment 114 of Figure I) (e.g. from P2P host 1 18 of Figure 1 to Ethernet host 130 of Figure 1), namely a data forwarding module 558.
  • the P2P transceiver 550 receives incoming P2P frames and passes the client traffic to the client traffic manager 586.
  • the client traffic manager 586 retains the client traffic for subsequent routing over the LAN environment.
  • the P2P transceiver 550 passes the source and destination IP addresses from the client traffic to a subnet address analysis (SAA) function 588.
  • the SAA function 588 accesses a P2P Endpoint Assist table (such as the P2P Endpoint Assist table 264 of Figure 2) to obtain the NL subnet information associated with the NL address that has been allocated to the P2P host sending the client traffic.
  • the SAA function 588 compares the destination NL address from the client traffic with the subnet mask and stored NL address to determine whether the destination NL address lies within the local LAN service (such as LAN service 122 of Figure 1).
  • An NL/LAN Addr map manager 590 accesses and updates the NL/LAN Addr table 562.
  • An NL/LAN address resolution (NL/LAN AR) Request Function 592 sends requests over a LAN service (such the LAN service 122 of Figure 1) for a LAN address associated with a particular destination NL address.
  • the NL to LAN AR function 592 receives from the LAN service replies to the NL to LAN addr requests sent and a LAN frame reconstruction function 596 builds LAN frames, each of which contains a LAN header (with LAN address) and the client traffic held by the client traffic manager 586 to be conveyed over the LAN service.
  • Figures 6a, 6b, 7a and 7b illustrates the flow sequence performed by a data forwarding module (such as data forwarding module 558 of Figure 5) in connection with forwarding client traffic from a P2P environment (such as the P2P environment 112 of Figure 1) to a local LAN service (such as the LAN service 122 of Figure 1) in a LAN environment (such as the LAN environment 114 of Figure 1).
  • Figure 6a is implemented when a destination NL address is already stored in an NL/LAN address table (such as NL/LAN address table 262 of Figure 2).
  • Figure 6b is implemented when a destination NL address is not already stored in an NL/LAN address table and the destination NL address is on the LAN service.
  • Figure 7a is implemented when a destination NL address is not already stored in an NL/LAN address table, the destination NL address is not on the LAN service and the default router LAN address is known.
  • Figure 7a is implemented when a destination NL address is not already stored in an NL/LAN address table, the destination NL address is not on the LAN service and the default router LAN address is unknown.
  • a P2P host (such as the P2P host 118 of Figure 1) sends a P2P frame over a link (such as link 120 of Figure 1).
  • the P2P frame includes the appropriate P2P header and the encapsulated client-layer (e.g. Network Layer) traffic.
  • a P2P frame transceiver receives the P2P frame, removes the client traffic and provides the client traffic to a client traffic manager (such as the client traffic manager 586 of Figure 5).
  • the client traffic manager retrieves an entry in a P2P Endpoint Assist Table (such as the P2P Endpoint Assist Table 264 of Figure 2) for the P2P interface where the P2P frame was received.
  • the client traffic manager retrieves the destination NL address from the client traffic and consults an NL/LAN addr map manager (such as the NL/LAN addr map manager 590 of Figure 5) to determine if an entry already exists in an NL/LAN Addr table for the destination NL address.
  • the client traffic manager provides a LAN frame transceiver (such as the LAN frame transceiver 252 of Figure 2) with LAN address in the P2P Endpoint Assist Table as the source LAN address, the LAN 1 address in the NL/LAN Addr table as the destination LAN address, and the client traffic for transmission.
  • a LAN frame transceiver such as the LAN frame transceiver 252 of Figure 2
  • the client traffic manager provides the NL subnet mask and the NL address from the P2P Endpoint Assist Table along with the destination NL address retrieved from the client traffic to an SAA function (such as the SAA function 588 of Figure 5) to determine whether the destination NL address is in the local LAN service.
  • SAA function such as the SAA function 588 of Figure 5
  • the destination NL address as well as the NL address assigned to the P2P endpoint are each logically AND'ed with the NL subnet mask. The result is then compared, and if it is the same, the endpoint is in the local LAN service. If the results are not the same, then the endpoint is not in the local LAN service. This result is then returned to the client traffic manager.
  • the client traffic manager provides the LAN address in the P2P Endpoint Assist table, the NL address to be resolved, and the client traffic to an NL/LAN AR Request Function (such as the NL/LAN AR Request Function 592 of Figure 5).
  • the NL/LAN AR Request Function places the client traffic on its pending traffic queue (such as the pending traffic queue 246 of Figure 2).
  • the pending traffic queue associates, with the client traffic, the NL address to be resolved and the source LAN address. Once the LAN address has been resolved, the client traffic may then be transmitted.
  • the NL/LAN AR Request Function transmits an NL to LAN Addr Resolution request over the LAN service.
  • the destination device within the LAN environment having the destination NL address in the request, sends an NL to LAN Addr Resolution response that includes the NL address being resolved, and the corresponding LAN address of the destination device.
  • the NL/LAN AR Request Function receives this response and requests the NL/LAN addr table manager to create an entry for the NL address and the corresponding LAN address in associated fields (such as fields 268 and 266 in Figure 2) in the NL/LAN addr table.
  • the NL/LAN Addr Resolution Request Function evaluates, in order, the entries on the pending traffic queue to identify entries that matched the NL address resolved. For each matching entry, the LAN frame transceiver is provided the source LAN address associated with the entry. For each matching entry, the LAN frame transceiver is also provided with the LAN address corresponding to the resolved NL address as the destination LAN address, and the client traffic for transmission.
  • the client traffic manager consults the NL/LAN addr table manager to determine if an entry already exists in the NL/LAN Addr table for the NL Default Router (such as router 126 of Figure 1) using an NL address stored in a NL Default Router field (such as the NL Default Router field 278 of Figure 2) of the P2P Endpoint Assist Table. If an entry exists in the NL/LAN addr table, at 666, the client traffic manager will request the NL/LAN Addr table manager to create an entry in the NL/LAN Addr table for the destination NL address.
  • the entry in the NL/LAN Addr table is created using the LAN address of the NL Default Router as the LAN address.
  • the client traffic manager will then provide i) the LAN frame transceiver with LAN address in the P2P Endpoint Assist Table as the source LAN address, ii) the LAN address of the NL Default Router as the destination LAN address, and iii) the client traffic for transmission.
  • the client traffic manager provides i) the LAN address in the P2P Endpoint Assist table, ii) the NL address of the NL Default Router to be resolved, and iii) the client traffic to the NL/LAN Addr Resolution Request Function.
  • the NL/LAN Addr Resolution Request Function places the client traffic on its pending traffic queue.
  • the pending traffic queue associates, with the client traffic, the NL address to be resolved and the source LAN address. Once the NL address has been resolved, the client traffic may then be transmitted.
  • the NL/LAN Addr Resolution Request Function then transmits an NL to LAN Addr Resolution request over the LAN service.
  • the destination device within the LAN environment having the destination NL address in the request, sends an NL to LAN Addr Resolution response that includes the NL address being resolved, and the corresponding LAN address of the destination device.
  • the NL/LAN AR Request Function receives this response and requests the NL/LAN addr map manager to create an entry for the NL address and the corresponding LAN address in associated fields (such as fields 268 and 266 of Figure 2) in the NL/LAN addr table.
  • the NL/LAN AR Request Function evaluates, in order, the entries on the pending traffic queue to identify entries that matched the NL address resolved. For each matching entry, the LAN frame transceiver is provided the source LAN address associated with the entry. For each matching entry; the LAN frame transceiver is also provided with the LAN address corresponding to the resolved NL address as the destination LAN address, and the client traffic for transmission.
  • Figure 8 illustrates a flow sequence performed by a data forwarding module (such as data forwarding module 558 as in Figure 5) in connection with the conveyance of client traffic from a LAN host (such as LAN host 130 of Figure 1) to a P2P host (such as P2P host 118 of Figure 1).
  • a data forwarding module such as data forwarding module 558 as in Figure 5
  • the LAN host or an NL router such as NL router 126 of Figure 1
  • a check is made to determine if the NL address of the P2P host is in a NL/LAN addr table stored on the LAN host or LN router.
  • the LAN host or NL router will resolve the NL address of the P2P host into a LAN address.
  • the LAN host broadcasts an NL to LAN Addr Resolution request message containing a destination NL address.
  • a NL/LAN Addr Resolution responder (such as NL/LAN. Addr Resolution responder 594 of Figure 5) compares the destination NL address within the NL to LAN Addr Resolution request message with NL addresses stored in a P2P Endpoint Assist table (such as P2P Endpoint Assist table 264 of Figure 2).
  • the NL/LAN Addr Resolution Responder replies with the corresponding LAN address from the P2P Endpoint Assist table that has been reserved for the P2P host associated with the NL address.
  • the LAN host updates a NL/LAN addr table (such as NL/LAN addr table 262 of Figure 2).
  • the LAN host begins sending LAN frames to the P2P host, utilizing a LAN header and the corresponding client traffic.
  • the LAN header includes the LAN address associated with the P2P host.
  • a LAN frame transceiver receives the LAN frames and removes the LAN header, keeping track of the LAN address they were sent to. An entry is retrieved from the P2P Endpoint Assist table that is associated with the LAN address, to which the LAN frames were sent.
  • the P2P frame transceiver 250 is provided with the P2P Port, and the client traffic.
  • a P2P frame transceiver (such as P2P frame transceiver 250 of Figure 2) constructs a P2P frame including an appropriate P2P protocol header and the client traffic.
  • the P2P frame is then transmitted at 810 on the specified P2P Port, across a link (such as link 120 of Figure 1) connected to the P2P host.
  • the P2P frame is received by the P2P host.
  • client traffic is routed through the interworking device from the LAN host to the P2P host.
  • FIG. 9 illustrates a flow sequence carried out to shutdown a network layer in accordance with an exemplary embodiment of the present invention.
  • a P2P host such as P2P host 1 18 of Figure 1
  • the P2P host issues a Network Layer Stop message.
  • a P2P frame transceiver (such as P2P frame transceiver 250 of Figure 2) receives the Network Layer Stop message, and generates a Network Layer down event.
  • an interworking device (such as interworking device 116 of Figure 1) sends a message directing a LAN/NL Address Assignment Server (such as LAN/NL Address Assignment Server 132 of Figure 1) to release the NL address assigned to the P2P host. Since the NL address is no longer assigned to the P2P host, the values in NL Subnet and LAN Default Router fields of a P2P Endpoint Assist Table (such as fields 274 and 278 of P2P Endpoint Assist Table 264 of Figure 2) are no longer valid. Therefore, at 902, the values in the NL Subnet field and LAN Default Router field are removed from the P2P Endpoint Assist Table. At 904, the LAN/NL Address Assignment Server receives the NL address release message and places the NL address onto a list of available addresses. At 906, the P2P host receives the Network Layer Stop acknowledgement and places the network layer in a down state.
  • a LAN/NL Address Assignment Server such as LAN/NL Address Assignment Server 132 of Figure 1
  • FIG 10 illustrates a flow sequence carried out to shutdown all communications across a P2P link (such as the P2P link 120 of Figure 1) in accordance with an exemplary embodiment of the present invention.
  • the P2P host (such as the P2P host 118 of Figure 1) determines to cease the use of the P2P link for P2P communications, and issues a Link Stop message.
  • a P2P frame transceiver (such as the P2P frame transceiver 250 of Figure 2) receives the Link Stop message, and returns the LAN Address that has been associated with the P2P host to be returned to a LAN Addr Pool (such as the LAN Addr Pool 248 of Figure 2).
  • the P2P frame transceiver sends a Link Stop acknowledgement to the P2P host.
  • the P2P host receives the Link Stop acknowledgement and places the link in a down state.
  • the LAN service may utilize a different layer 2 protocol other than Ethernet.
  • the P2P environment such as the P2P environment 112 of Figure 1
  • LAN environment such as the LAN environment 122 of Figure 1
  • interworking device such as the interworking device 116 of Figure 1
  • IP Internet protocol
  • the client traffic is defined based on the Internet protocol (IP), although optionally other protocols may be used, for example Novell's Internetwork Packet exchange (IPX), DECnet and the like.
  • the P2P link (such as the P2P link 120 of Figure 1) may represent a DSL link over a phone line, a DSl link, a DS3 link and the like.
  • more than one router (such as the router 126 of Figure 1) may be provided for connection to different remote LAN services (such as the remote LAN services 124 of Figure I).
  • the local LAN service (such as the local LAN service 122 of Figure 1) may be joined to a non-LAN service through another router.
  • more than one LAN/NL Address Assignment server (such as the LAN/NL Address Assignment server 132 of Figure 1) may be utilized.
  • Software embodiments of the present invention may include an article of manufacture on a machine accessible or machine readable medium having instructions.
  • the instructions on the machine accessible or machine readable medium may be used to program a computer system or other electronic device.
  • the machine- readable medium may include, but is not limited to, floppy diskettes, optical disks, CD-ROMs, and magneto-optical disks or other type of media/machine readable medium suitable for storing or transmitting electronic instructions.
  • the techniques described herein are not limited to any particular software configuration. They may find applicability in any computing or processing environment.
  • machine accessible medium or “machine readable medium” used herein shall include any medium that is capable of storing, encoding, or transmitting a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methods described herein.
  • machine readable medium e.g., any medium that is capable of storing, encoding, or transmitting a sequence of instructions for execution by the machine and that cause the machine to perform any one of the methods described herein.
  • software in one form or another (e.g., program, procedure, process, application, module, unit, logic, and so on) as taking an action or causing a result. Such expressions are merely a shorthand way of stating that the execution of the software by a processing system causes the processor to perform an action to produce a result.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Data Exchanges In Wide-Area Networks (AREA)
  • Small-Scale Networks (AREA)

Abstract

Dispositif d'inter fonctionnement permettant d'établir une interface entre un environnement point-à-point (P2P) et un environnement de réseau local (LAN). Le dispositif d'interfonctionnement comprend un émetteur-récepteur de trames P2P conçu pour communiquer avec un hôte P2P au moyen de trames P2P formatées selon un protocole P2P. Un émetteur-récepteur de trames LAN est conçu pour communiquer, au sein d'un environnement LAN, avec un hôte LAN utilisant des trames LAN formatées selon un protocole LAN. Les trames P2P et LAN incluent un trafic client avec des informations à couche de réseau (NL) de niveau client associées à un protocole à couche de réseau de niveau client prédéfini. Un module de transmission de données utilise les informations NL pour reporter le trafic client depuis au moins soit (1) les trames P2P dans l'environnement LAN, soit les trames LAN dans l'environnement P2P.
PCT/US2007/017928 2006-08-24 2007-08-13 Procédé et système d'interfonctionnement d'une liaison point à point et d'un système local WO2008024226A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
US11/509,345 US20080049765A1 (en) 2006-08-24 2006-08-24 Method and system for inter working a point-to-point link and a LAN service
US11/509,345 2006-08-24

Publications (2)

Publication Number Publication Date
WO2008024226A1 true WO2008024226A1 (fr) 2008-02-28
WO2008024226B1 WO2008024226B1 (fr) 2008-05-22

Family

ID=38823618

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2007/017928 WO2008024226A1 (fr) 2006-08-24 2007-08-13 Procédé et système d'interfonctionnement d'une liaison point à point et d'un système local

Country Status (2)

Country Link
US (1) US20080049765A1 (fr)
WO (1) WO2008024226A1 (fr)

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100959074B1 (ko) * 2007-12-12 2010-05-20 한국전자통신연구원 Ｐ２ｐ 네트워크 상에서의 보안 그룹 생성 방법, 생성장치, 인증 방법, 인증 장치
US20100138650A1 (en) * 2008-12-01 2010-06-03 Shin Yuk Kang Secure communication system, gateway apparatus and its operating method
CN101841573B (zh) * 2010-01-20 2013-08-07 中国科学院计算机网络信息中心 互联网地址信息处理方法、装置以及互联网系统
US9124647B2 (en) * 2011-10-31 2015-09-01 Microsoft Technology Licensing, Llc Communication protocol abstraction
KR102098239B1 (ko) * 2012-12-04 2020-04-08 삼성전자주식회사 무선 통신 시스템에서 인터넷 프로토콜 어드레스를 설정하는 방법 및 장치
JP5838380B2 (ja) * 2013-03-28 2016-01-06 パナソニックＩｐマネジメント株式会社 通信システム、携帯型情報端末、通信アダプタ、及び通信方法

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2361394A (en) * 2000-04-14 2001-10-17 3Com Corp Conversion of point-to-point data packets to Ethernet data packets
US20040017800A1 (en) * 2000-09-29 2004-01-29 Alfred Lupper Method for connection of data terminal devices to a data network
US20040252717A1 (en) * 2003-06-13 2004-12-16 Corrigent Systems Ltd. Multiprotocol media conversion

Family Cites Families (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6795438B1 (en) * 1998-10-28 2004-09-21 Intel Corporation Method and apparatus for extending point-to-point/asynchronous transfer mode services to client computer systems
US6751216B2 (en) * 2001-09-05 2004-06-15 Sprint Communications Company L.P. Providing end-user communication services over peer-to-peer internet protocol connections between service providers
US6793088B2 (en) * 2002-02-08 2004-09-21 Rieke Corporation Container and method for preventing leakage therefrom through isolating deformation in the container
US7400647B1 (en) * 2003-01-13 2008-07-15 Extreme Networks Look up table (LUT) for point-to-point protocol identification (PPP ID)
US7430614B2 (en) * 2003-10-31 2008-09-30 Redback Networks, Inc. Use of IP address blocks with default interfaces in a router
US20050111352A1 (en) * 2003-11-21 2005-05-26 Boon Ho Method and system for monitoring a network containing routers using a backup routing protocol
US7333508B2 (en) * 2004-01-20 2008-02-19 Nortel Networks Limited Method and system for Ethernet and frame relay network interworking
US20060165121A1 (en) * 2005-01-27 2006-07-27 Alcatel Communication protocol interface systems and methods

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2361394A (en) * 2000-04-14 2001-10-17 3Com Corp Conversion of point-to-point data packets to Ethernet data packets
US20040017800A1 (en) * 2000-09-29 2004-01-29 Alfred Lupper Method for connection of data terminal devices to a data network
US20040252717A1 (en) * 2003-06-13 2004-12-16 Corrigent Systems Ltd. Multiprotocol media conversion

Also Published As

Publication number Publication date
WO2008024226B1 (fr) 2008-05-22
US20080049765A1 (en) 2008-02-28

Similar Documents

Publication Publication Date Title
US7733859B2 (en) Apparatus and method for packet forwarding in layer 2 network
EP1693996B1 (fr) Découverte automatique des adresses d'homologues pseudo-wire dans des réseaux Ethernet
US8782288B2 (en) Multicast-enabled address resolution protocol (ME-ARP)
US7568040B2 (en) Techniques for establishing subscriber sessions on an access network using DHCP
JP3953955B2 (ja) アクセス・ネットワーク
US7016353B2 (en) Method and system for dynamically assigning IP addresses in wireless networks
US6614809B1 (en) Method and apparatus for tunneling across multiple network of different types
CN100566334C (zh) 提供动态服务选择和最终用户配置的以太网数字用户线接入复用器和方法
JP4692258B2 (ja) ルータ装置及び通信システム
US6542935B1 (en) Method for obtaining a second address free from association with multiple devices
US20020165972A1 (en) Methods and apparatus for use in reducing traffic over a communication link used by a computer network
KR20080003436A (ko) Ｉｐ-기반 인터페이스를 이용하여 ｔｅ2 장치를 통한 무선데이터 서비스들을 지원하기 위한 방법 및 장치
US6618398B1 (en) Address resolution for internet protocol sub-networks in asymmetric wireless networks
US8706908B2 (en) System, method and apparatus for media access control (MAC) address proxying
US8321550B2 (en) Media access control address based service selection
CN103227787B (zh) 一种基于ARP代理的4over6隧道自动建立方法
US20080049765A1 (en) Method and system for inter working a point-to-point link and a LAN service
WO2014056412A1 (fr) Procédé d'envoi de message, système et pont de routage
USH2065H1 (en) Proxy server
JP4029930B2 (ja) 中継装置および接続方法
JP5608870B2 (ja) パケット転送装置、パケット転送方法、およびプログラム
CN101437013A (zh) 一种层二控制代理方法、装置和系统
JPH11355345A (ja) Ｌａｎ間接続装置及びｌａｎ間接続システム

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07836786

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

NENP Non-entry into the national phase

Ref country code: RU

122 Ep: pct application non-entry in european phase

Ref document number: 07836786

Country of ref document: EP

Kind code of ref document: A1