WO1996000468A1 - Procede d'utilisation d'un protocole point a point au-dessus d'un reseau a mailles imparfaites - Google Patents
Procede d'utilisation d'un protocole point a point au-dessus d'un reseau a mailles imparfaites Download PDFInfo
- Publication number
- WO1996000468A1 WO1996000468A1 PCT/US1995/007442 US9507442W WO9600468A1 WO 1996000468 A1 WO1996000468 A1 WO 1996000468A1 US 9507442 W US9507442 W US 9507442W WO 9600468 A1 WO9600468 A1 WO 9600468A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- imn
- ppp
- source node
- packet
- network interface
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims description 14
- 238000004891 communication Methods 0.000 claims abstract description 34
- 230000008878 coupling Effects 0.000 claims abstract description 9
- 238000010168 coupling process Methods 0.000 claims abstract description 9
- 238000005859 coupling reaction Methods 0.000 claims abstract description 9
- 238000012790 confirmation Methods 0.000 claims 2
- 239000000284 extract Substances 0.000 description 7
- 230000005540 biological transmission Effects 0.000 description 5
- 238000012795 verification Methods 0.000 description 3
- 238000005538 encapsulation Methods 0.000 description 2
- 230000005641 tunneling Effects 0.000 description 2
- 230000009286 beneficial effect Effects 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 239000000835 fiber Substances 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 238000013507 mapping Methods 0.000 description 1
- 239000000463 material Substances 0.000 description 1
- 230000008450 motivation Effects 0.000 description 1
- 238000012545 processing Methods 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L9/00—Cryptographic mechanisms or cryptographic arrangements for secret or secure communications; Network security protocols
- H04L9/40—Network security protocols
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L2212/00—Encapsulation of packets
Definitions
- a point-to-point data communication link serves to connect two nodes or stations directly over a single two-way link.
- the two nodes are each connected together by a common transmission medium such as a twisted pair transmission line, fiber optic channel, or a radio communications channel.
- the two nodes cooperate to transmit data aetween themselves using a common data communication protocol.
- PPP Point-to-Point Protocol
- RFC 1548 Internet Request for Comments, no. 1548, December 1993, the contents of which are herein incorporated by reference.
- data to be communicated over a point-to-point link is included in an information field of a special PPP frame or packet which further includes other fields used for link operation.
- the data included in the information field may be a packet formatted in accordance with some other protocol such as Internet Protocol (IP) .
- IP Internet Protocol
- An imperfect mesh network is a network with an interconnected set of nodes in which the nodes typically do not have knowledge of all other nodes in the network and which do not share a common transmission medium.
- a source node with data to transmit to an arbitrary target node does not normally know of the intermediate path to the target node, nor is there a direct link between the source node and its ultimate target node.
- Data transmitted from the source node to the target node is instead routed through a path comprising a series of intermediate nodes belonging to the IMN with each node in the path having a direct link to a successor in its route to the ultimate target node, but generally not being able to communicate directly or to even be aware of the source node and/or the target node.
- a sequence of packets is transmitted from the source node to target node, they may follow disparate paths and thus may arrive out of order. Furthermore, a fault at an intermediate node in any one of the paths followed may terminate transport of a packet and thus disrupt the sequence.
- heavyweight transport protocols For each set of one or more data packets successfully transported from a source node to a target node, an acknowledgement packet is returned from the target node to the source node. If reliable ordered delivery is not required, a so-called lightweight transport protocol may be employed.
- a lightweight transport protocol does not provide reliable ordered delivery but offers increased network efficiency by operating without the use of acknowledgement packets. Because of the widespread availability of software that implements PPP at a node such as a personal computer or workstation, it is desirable to emulate a PPP data communication link over an IMN.
- the node which operates PPP forwards a PPP packet to a source node connected in the IMN.
- the PPP packet is encapsulated at the source node within an IMN forwarding packet for transport across the IMN to a target node connected in the IMN.
- the encapsulation process appends an address of the target node and any other header information required for transport across the IMN.
- the PPP packet is extracted from the IMN forwarding packet by stripping away information particular to IMN operation. The extracted PPP packet may then be forwarded to another node equipped with PPP software.
- a lightweight transport protocol i.e. a transport protocol that does not provide reliable ordered delivery of packets and thus does not require the exchange of acknowledgement packets
- PPP Point-to-Point Protocol
- INN imperfect mesh network
- the gateway node may be configured either as a single device operative to internally map between physical IMN ports and logical ports, or as a combination of a conventional communications server and one or more special network interfaces for coupling to the IMN.
- the invention stems from recognition of a problem posed by the use of a heavyweight transport protocol to tunnel PPP packets through an IMN from a source node to a gateway node connected in a network employing Internet Protocol (IP) , e.g. the Internet, namely that use of a heavyweight transport protocol often results in the excessive generation of acknowledgement packets which degrade performance.
- IP Internet Protocol
- acknowledgment packets specific to IMN operation become
- a source node network interface includes means for encapsulating PPP packets received from a source node within IMN forwarding packets and means for forwarding the IMN forwarding packets to a gateway node via the IMN by
- logical ports at a gateway node corresponding to potential active PPP sessions are decoupled from physical ports for interfacing to the IMN. Decoupling logical ports from physical ports provides a significant advantage in that a packet to be forwarded or received during the course of an active PPP session may make use of any currently available physical port. Thus, the number of active PPP sessions that the gateway node can support is not limited by the number of physical ports. The ability to make efficient use of available physical ports at the gateway node is particularly beneficial when the IMN is a wireless network and each physical port includes an expensive radio transceiver.
- the gateway node includes a single device that couples directly to the IMN and internally maps between physical ports and logical ports.
- the gateway node includes a conventional communications server with serial ports directly coupled to logical ports and a special interface which includes physical ports to the IMN and performs the necessary mapping between the physical ports and communications server serial ports.
- devices substantially similar to the source node network interface of the first aspect of the invention couple individual serial ports of the communications server to the IMN.
- Fig. 1 depicts a data communication system in accordance with the invention, wherein PPP packets are transported across an imperfect mesh network (IMN) encapsulated within IMN forwarding packets.
- Fig. 2 is a flowchart describing the steps of establishing and employing an emulated PPP link over an IMN in accordance with the invention.
- INN imperfect mesh network
- Fig. 3 depicts a representation of a gateway node of the invention, wherein physical ports coupled to an IMN are decoupled from logical ports employed to operate individual virtual PPP sessions.
- Fig. 4 depicts a gateway node of the invention configured as a combination of a communications server having multiple serial ports directly linked to internal logical ports and a special network interface for coupling to an IMN.
- Fig. 5 depicts a gateway node of the invention configured as a combination of a communications server having multiple serial ports directly linked to internal logical ports and a plurality of special network : rfaces, each one for coupling a given serial port to an IM DESCRIPTION OF SPECIFIC EMBODIMENTS
- Fig. 1 depicts a data communication system 10 in accordance with the invention, wherein PPP packets are transported across an imperfect mesh network (IMN) 12 encapsulated within IMN forwarding packets.
- Data communication system 10 includes a representative source node 14, an associated source node network interface 16, IMN 12, and a gateway node 18. Gateway node 18 acts as an interface between IMN 12 and an Internet Protocol network 20.
- ISN imperfect mesh network
- IMN 12 consists of repeater nodes labelled R 0 through R 9 interconnected by paths representing allowable communication links between nodes. Data transmitted between the source node and gateway node is routed through a path comprising a series of the repeater nodes belonging to the IMN with each node in the path having a direct link to a successor in its route to the ultimate target node (gateway or source) but generally no direct link to the ultimate target node itself.
- source node 14 is a computer equipped with a conventional modem port and standard PPP software for transmitting and receiving PPP packets.
- the modem port is coupled to source node network interface 16 by a serial link.
- source node network interface 16 incorporates a radio transceiver.
- PPP packets are exchanged between source node 14 and source node network interface 16 through the modem port and serial link.
- Source node network interface 16 encapsulates PPP packets and modem commands received from source node 14 within IMN forwarding packets, packets specially formatted for transport across IMN 12.
- Source node network interface 16 also extracts PPP packets and modem commands from IMN forwarding packets received via IMN 12. Fig.
- source node 14 requests the establishment of an emulated PPP data link.
- source node 14 issues a conventional connection request to source node network interface 16.
- Source node network interface 16 then encapsulates the connection request within an IMN forwarding packet.
- the IMN forwarding packet includes an IMN-specific address of gateway node 18 and any other information required for transport across IMN 12.
- This IMN forwarding packet is forwarded across IMN 12 to gateway node 18 which responds to the encapsulated connection request by registering an active PPP connection to source node 14 and returning a connection verification indication encapsulated within another IMN forwarding packet which includes an IMN-specific address of source node network interface 16. If gateway node 18 cannot in fact support a new PPP connection, a connection busy indication will be sent instead.
- Source node network interface 16 extracts this information from the IMN forwarding packet and forwards it to source node 14.
- Source node 14 thus establishes the link by employing a conventional connection request which may be an "AT" modem command and without awareness of the operation of IMN 12.
- gateway node 18 may request the establishment of an emulated PPP link to source node 14 at step 110. Such a callout request may come about due to the operation of Internet Protocol network 20 in which gateway node 18 is connected or for some other reason.
- Gateway node 18 sends the connection request encapsulated within an IMN forwarding packet addressed to source node network interface 16 via IMN 12.
- source node network interface 16 extracts the connection request and forwards it to source node 14.
- Source node 14 responds by registering an active PPP connection to gateway node 18 and forwarding a connection verification indication to source node network interface 16 which encapsulates it within another IMN forwarding packet addressed for transport to gateway node 18.
- the connection request and connection verification indication may be conventional "AT" modem commands and source node 14 need not be aware of IMN 12.
- An emulated PPP data link established as described in connection with steps 100 and 110 may be employed to forward a PPP packet from source node 14 to gateway node 18 at step 120 or to forward a PPP packet from gateway node 18 to source node 14 at step 130.
- gateway node 18 is connected in Internet Protocol network 20 and source node 14 operates software which implements Internet Protocol
- the information fields of PPP packets exchanged via IMN 12 may include
- Source node 14 may then exchange Internet Protocol packets with any node accessible via Internet Protocol network 20, enabling a broad range of applications imp emented by protocols overlying Internet Pro .%col includir; electronic mail and remote data access.
- a PPP packet is to be forwarded from source node 14 to gateway node 18, the PPP packet is sent to source node network interface 16 for encapsulation within an IMN forwarding packet for transport to gateway node 18 across IMN 12.
- Gateway node 18 responds by extract:;r.g the PPP packet and processing it appropriately. If an Internet Protocol packet (IP packet) generated by source node 14 is encapsulated within an information field of the PPP packet, the IP packet is extracted and forwarded to its destination in Internet Protocol network 20 in accordance with an address field of the IP packet. Again, the operation of IMN 12 is transparent to source node 14 which need only generate the PPP packets.
- IP packet Internet Protocol packet
- a PPP packet is to be forwarded from gateway node 18 to source node 14, it is similarly encapsulated within an IMN forwarding packet for transport across IMN 12 to source node network interface 16.
- Source node network interface 16 extracts the PPP packet and sends it to source node 14.
- the motivation for generating the PPP packet at gateway node 18 may be receipt from Internet Protocol network 20 of an IP packet addressed to source node 14. Again, the operation of IMN 12 is transparent to source node 14. Protocols overlying Internet Protocol typically employ acknowledgement packets to assure reliable ordered delivery of data transport packets. For each set of data transport packets forwarded, an acknowledgement packet is returned.
- a heavyweight protocol were employed to transport IMN forwarding packets across IMN 12, the heavyweight protocol would similarly generate and exchange acknowledgement packets, including IMN-specific acknowledgement packets which themselves encapsulate the acknowledgement packets generated by overlying protocols.
- the protocols overlying Internet Protocol assure reliable ordered delivery between source node 14 and the ultimate destination in Internet Protocol network 20, there is no need to provide reliable ordered delivery across IMN 12.
- a lightweight transport protocol that does not itself generate acknowledgement packets is employed to transport the IMN forwarding packets which encapsulate the PPP packets.
- An emulated PPP link established in accordance with the invention is discontinued at the request of source node 16, at step 140, or at the request of gateway node 18, at step 150.
- Gateway node 18 may request disconnection of a link to source node 14 if a predetermined interval passes with no link activity. To avoid a timed disconnection, source node 14 may periodically encapsulate and forward so-called "keep- alive" messages to gateway node 18.
- Fig. 3 depicts a representation of one configuration of gateway node 18 in accordance with the invention, wherein physical ports to IMN 12 are decoupled from logical ports employed to operate virtual PPP sessions.
- gateway node 18 incorporates physical ports PI through PN for coupling to IMN 12. If IMN 12 is a wireless network, physical ports P through P N each incorporate a radio transceiver.
- Gateway node 14 may operate a plurality of emulated PPP links over IMN 12. Each link is operated by one of logical ports L ⁇ through 1 ⁇ which generates PPP packets for transmission and processes received PPP packets. A free logical port is selected to operate a given PPP link when the link is established.
- PPP packets associated with a given link may be received (in encapsulated form) by any available physical port.
- a lightweight transport/switching system 200 extracts PPP packets from IMN forwarding packets. Lightweight transport/switching system 200 directs the extracted PPP packet to the logical port which operates the given link.
- a PPP packet generated by a logical port and intended for transport across IMN 12 may employ any available physical port.
- Lightweight transport/switching system 200 encapsulates the PPP packet within an IMN forwarding packet and directs the IMN forwarding packet to the physical port with the shortest queue of packets awaiting transmission. Typical PPP sessions are not continuously active.
- the gateway node configuration depicted in Fig. 3 takes advantage of these idle periods to support a number of logical ports greater than the number of available physical ports. This decoupling is particularly advantageous when IMN 12 is a wireless network and each physical port necessarily incorporates an expensive radio transceiver.
- An IP router 202 interfaces the logical ports to Internet Protocol network 20. If a PPP packet received by a logical port encapsulates an IP packet, the logical port forwards the IP packet to IP router 202. The IP router then forwards the IP packet to its ultimate destination in Internet Protocol network 20. Alternatively, if IP router 202 receives an IP packet addressed to a node in IMN 12, the IP packet is forwarded to a logical port in communication with that node. If no PPP link with the node is currently active, the call-out procedure described in reference to Fig. 2 is followed to create a link.
- Fig. 4 depicts gateway node 18 configured as a combination of a communications server 300 having multiple serial ports directly linked to logical ports and a special network interface 302 for coupling to IMN 12.
- Communications server 300 is a conventional communications server, incorporating serial ports S through S M which are individually assigned to logical ports L through 1 ⁇ for operating PPP sessions.
- Network interface 302 incorporates physical ports P through P N for connecting to IMN 12 and is also connected to serial ports S x through S M .
- network interface 302 incorporates lightweight transport/switching system 200.
- Fig. 5 depicts gateway node 18 configured as a combination of conventional communications server 300 and a plurality of special network interfaces 400 for coupling to IMN 12.
- Each network interface 400 directly couples a serial port of communications server 300 to a physical port of IMN 12.
- each network interface extracts PPP packets from IMN forwarding packets received over IMN 12 and encapsulates PPP packets received from communications server 300 within IMN forwarding packets for transport across IMN 12.
- the network interfaces 400 are each functionally equivalent to source node network interface 16 of Fig. 1, only they are coupled to gateway node 18 rather than source node 14.
- the gateway node configuration of Fig. 5 does not provide the decoupling of physical ports and logical ports provided by the configurations of Fig. 3 and Fig. 4.
- the attached appendix contains a source-code listing containing one operational embodiment of selected elements of the claimed invention.
- the source-code instantiates elements of network interface 400 depicted in Fig. 5 which is equivalent to network interface 16 depicted in Fig. 1.
- the machine-readable form of the listing can be compiled using a C language compiler.
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
Un protocole de transport léger (c'est-à-dire un protocole de transport n'assurant pas la livraison fiable et ordonnée de paquets et par conséquent ne nécessitant pas l'échange de paquets d'accusés de réception) est utilisé pour acheminer des paquets de protocoles point à point (PPP) entre un ou plusieurs noeuds émetteurs (14) et un noeud de transit (18) à travers un réseau à mailles imparfaites (IMN)(12). Le noeud de transit (18) peut être configuré soit en tant que dispositif unique permettant d'établir une correspondance interne entre des accès physiques IMN et des accès logiques, soit sous forme de combinaison de serveur de communication traditionnel et d'une ou plusieurs interfaces spéciales de réseau afin de coupler le réseau de protocole Internet (20) à l'IMN.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
AU29020/95A AU2902095A (en) | 1994-06-24 | 1995-06-08 | Method for using point-to-point protocol over an imperfect mesh network |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US26537094A | 1994-06-24 | 1994-06-24 | |
US08/265,370 | 1994-06-24 |
Publications (1)
Publication Number | Publication Date |
---|---|
WO1996000468A1 true WO1996000468A1 (fr) | 1996-01-04 |
Family
ID=23010155
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/US1995/007442 WO1996000468A1 (fr) | 1994-06-24 | 1995-06-08 | Procede d'utilisation d'un protocole point a point au-dessus d'un reseau a mailles imparfaites |
Country Status (2)
Country | Link |
---|---|
AU (1) | AU2902095A (fr) |
WO (1) | WO1996000468A1 (fr) |
Cited By (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
WO1996021984A3 (fr) * | 1995-01-10 | 1996-09-12 | Nokia Telecommunications Oy | Systeme radio a transmission par paquets et equipement terminal y relatif |
GB2326568A (en) * | 1997-06-17 | 1998-12-23 | Advanced Micro Devices Inc | Interconnecting different networks using packet encapsulation |
GB2329550A (en) * | 1997-09-22 | 1999-03-24 | Northern Telecom Ltd | Transporting multi-protocol datagrams over an asynchronous virtual channel |
WO1999029124A1 (fr) * | 1997-12-01 | 1999-06-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Fonction de mappage et procede de transmission de messages de telecommunication du systeme ss7 sur des reseaux de donnees |
WO1999035798A1 (fr) * | 1998-01-12 | 1999-07-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Procede et dispositif pour configurer une liaison |
US6553020B1 (en) | 1996-12-18 | 2003-04-22 | Radiant Networks Plc | Communications system and method |
US7015809B1 (en) | 2002-08-14 | 2006-03-21 | Skipper Wireless Inc. | Method and system for providing an active routing antenna |
US7042394B2 (en) | 2002-08-14 | 2006-05-09 | Skipper Wireless Inc. | Method and system for determining direction of transmission using multi-facet antenna |
US7515544B2 (en) | 2005-07-14 | 2009-04-07 | Tadaaki Chigusa | Method and system for providing location-based addressing |
US7610050B2 (en) | 2002-08-14 | 2009-10-27 | Tadaaki Chigusa | System for mobile broadband networking using dynamic quality of service provisioning |
US7778149B1 (en) | 2006-07-27 | 2010-08-17 | Tadaaki Chigusa | Method and system to providing fast access channel |
US8160096B1 (en) | 2006-12-06 | 2012-04-17 | Tadaaki Chigusa | Method and system for reserving bandwidth in time-division multiplexed networks |
US8194654B1 (en) * | 1996-07-29 | 2012-06-05 | Cisco Technology, Inc. | Virtual dial-up protocol for network communication |
WO2016210017A1 (fr) * | 2015-06-26 | 2016-12-29 | Microsoft Technology Licensing, Llc | Protocole de transport léger |
Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5079765A (en) * | 1989-01-09 | 1992-01-07 | Canon Kabushiki Kaisha | Network system having a gateway apparatus for momitoring a local area network |
US5159592A (en) * | 1990-10-29 | 1992-10-27 | International Business Machines Corporation | Network address management for a wired network supporting wireless communication to a plurality of mobile users |
US5251205A (en) * | 1990-09-04 | 1993-10-05 | Digital Equipment Corporation | Multiple protocol routing |
US5323388A (en) * | 1991-09-20 | 1994-06-21 | Extension Technology Corp. | Local area network transmission emulator |
US5371852A (en) * | 1992-10-14 | 1994-12-06 | International Business Machines Corporation | Method and apparatus for making a cluster of computers appear as a single host on a network |
-
1995
- 1995-06-08 AU AU29020/95A patent/AU2902095A/en not_active Abandoned
- 1995-06-08 WO PCT/US1995/007442 patent/WO1996000468A1/fr active Application Filing
Patent Citations (5)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5079765A (en) * | 1989-01-09 | 1992-01-07 | Canon Kabushiki Kaisha | Network system having a gateway apparatus for momitoring a local area network |
US5251205A (en) * | 1990-09-04 | 1993-10-05 | Digital Equipment Corporation | Multiple protocol routing |
US5159592A (en) * | 1990-10-29 | 1992-10-27 | International Business Machines Corporation | Network address management for a wired network supporting wireless communication to a plurality of mobile users |
US5323388A (en) * | 1991-09-20 | 1994-06-21 | Extension Technology Corp. | Local area network transmission emulator |
US5371852A (en) * | 1992-10-14 | 1994-12-06 | International Business Machines Corporation | Method and apparatus for making a cluster of computers appear as a single host on a network |
Cited By (30)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5978386A (en) * | 1995-01-10 | 1999-11-02 | Nokia Telecommunications Oy | Packet radio system, and a terminal equipment for a packet radio system |
WO1996021984A3 (fr) * | 1995-01-10 | 1996-09-12 | Nokia Telecommunications Oy | Systeme radio a transmission par paquets et equipement terminal y relatif |
US8194654B1 (en) * | 1996-07-29 | 2012-06-05 | Cisco Technology, Inc. | Virtual dial-up protocol for network communication |
US6553020B1 (en) | 1996-12-18 | 2003-04-22 | Radiant Networks Plc | Communications system and method |
US7082112B2 (en) | 1996-12-18 | 2006-07-25 | Radiant Networks Plc | Communications system and method |
US7061883B2 (en) | 1996-12-18 | 2006-06-13 | Radiant Networks Plc | Communications system and method |
US7099297B2 (en) | 1996-12-18 | 2006-08-29 | Radiant Networks Pc | Communications system and method |
GB2326568A (en) * | 1997-06-17 | 1998-12-23 | Advanced Micro Devices Inc | Interconnecting different networks using packet encapsulation |
GB2326568B (en) * | 1997-06-17 | 1999-11-10 | Advanced Micro Devices Inc | Method and system for effective network communication of an unsupported media standard |
US6694372B1 (en) | 1997-06-17 | 2004-02-17 | Advanced Micro Devices, Inc. | Method and system for effective network communication of an unsupported media standard by encapsulated packet tagging |
GB2329550A (en) * | 1997-09-22 | 1999-03-24 | Northern Telecom Ltd | Transporting multi-protocol datagrams over an asynchronous virtual channel |
US6178181B1 (en) | 1997-12-01 | 2001-01-23 | Telefonaktiebolaget L M Ericsson (Publ) | Mapping function and method of transmitting signaling system 7(SS7) telecommunications messages over data networks |
GB2347047B (en) * | 1997-12-01 | 2002-11-20 | Ericsson Telefon Ab L M | Mapping function and method of transmitting signaling system 7 (SS7) telecommunications messages over data networks |
GB2347047A (en) * | 1997-12-01 | 2000-08-23 | Ericsson Telefon Ab L M | Mapping function and method of transmitting signaling system 7 (SS7) telecommunications messages over data networks |
WO1999029124A1 (fr) * | 1997-12-01 | 1999-06-10 | Telefonaktiebolaget Lm Ericsson (Publ) | Fonction de mappage et procede de transmission de messages de telecommunication du systeme ss7 sur des reseaux de donnees |
US6487218B1 (en) | 1998-01-12 | 2002-11-26 | Telefonaktiebolaget Lm Ericsson | Method and device for configuring a link |
AU753693B2 (en) * | 1998-01-12 | 2002-10-24 | Telefonaktiebolaget Lm Ericsson (Publ) | Method and device for configuring a link |
WO1999035798A1 (fr) * | 1998-01-12 | 1999-07-15 | Telefonaktiebolaget Lm Ericsson (Publ) | Procede et dispositif pour configurer une liaison |
US7015809B1 (en) | 2002-08-14 | 2006-03-21 | Skipper Wireless Inc. | Method and system for providing an active routing antenna |
US7610050B2 (en) | 2002-08-14 | 2009-10-27 | Tadaaki Chigusa | System for mobile broadband networking using dynamic quality of service provisioning |
US7042394B2 (en) | 2002-08-14 | 2006-05-09 | Skipper Wireless Inc. | Method and system for determining direction of transmission using multi-facet antenna |
US7515544B2 (en) | 2005-07-14 | 2009-04-07 | Tadaaki Chigusa | Method and system for providing location-based addressing |
US7778149B1 (en) | 2006-07-27 | 2010-08-17 | Tadaaki Chigusa | Method and system to providing fast access channel |
US8160096B1 (en) | 2006-12-06 | 2012-04-17 | Tadaaki Chigusa | Method and system for reserving bandwidth in time-division multiplexed networks |
WO2016210017A1 (fr) * | 2015-06-26 | 2016-12-29 | Microsoft Technology Licensing, Llc | Protocole de transport léger |
US9888095B2 (en) | 2015-06-26 | 2018-02-06 | Microsoft Technology Licensing, Llc | Lightweight transport protocol |
CN107787570A (zh) * | 2015-06-26 | 2018-03-09 | 微软技术许可有限责任公司 | 轻量传送协议 |
US20180139310A1 (en) * | 2015-06-26 | 2018-05-17 | Microsoft Technology Licensing, Llc | Lightweight transport protocol |
US10455061B2 (en) * | 2015-06-26 | 2019-10-22 | Microsoft Technology Licensing, Llc | Lightweight transport protocol |
CN112769718A (zh) * | 2015-06-26 | 2021-05-07 | 微软技术许可有限责任公司 | 网络接口卡 |
Also Published As
Publication number | Publication date |
---|---|
AU2902095A (en) | 1996-01-19 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US6178181B1 (en) | Mapping function and method of transmitting signaling system 7(SS7) telecommunications messages over data networks | |
US5918022A (en) | Protocol for transporting reservation system data over a TCP/IP network | |
US6917600B1 (en) | Mobile point-to-point protocol | |
US6154743A (en) | Technique for accessing heterogeneous directory services in an APPN environment | |
CN102098296B (zh) | 一种实现远程调用的方法和系统 | |
JP3478200B2 (ja) | サーバ・クライアント間双方向通信システム | |
WO1996000468A1 (fr) | Procede d'utilisation d'un protocole point a point au-dessus d'un reseau a mailles imparfaites | |
US5805818A (en) | System for acknowledging availability of neighbor node using data packet containing data that is ordinarily fowarded to neighbor node | |
CN110086689B (zh) | 一种双栈bfd检测方法以及系统 | |
US6389453B1 (en) | Method and system for routing undirectional multicast data | |
CN101350760B (zh) | 虚拟专网的数据报文转发方法 | |
CN110474830B (zh) | 一种基于端口转发的p2p隧道通信方法 | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
JP2003069615A (ja) | 通信制御装置および通信制御方法 | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments | |
Cisco | Configuring Serial Tunneling in SDLC and HDLC Environments |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AK | Designated states |
Kind code of ref document: A1 Designated state(s): AM AT AU BB BG BR BY CA CH CN CZ DE DK EE ES FI GB GE HU IS JP KE KG KP KR KZ LK LR LT LU LV MD MG MN MW MX NO NZ PL PT RO RU SD SE SG SI SK TJ TM TT UA UZ VN |
|
AL | Designated countries for regional patents |
Kind code of ref document: A1 Designated state(s): KE MW SD SZ UG AT BE CH DE DK ES FR GB GR IE IT LU MC NL PT SE BF BJ CF CG CI CM GA GN ML MR NE SN TD TG |
|
DFPE | Request for preliminary examination filed prior to expiration of 19th month from priority date (pct application filed before 20040101) | ||
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
REG | Reference to national code |
Ref country code: DE Ref legal event code: 8642 |
|
122 | Ep: pct application non-entry in european phase | ||
NENP | Non-entry into the national phase |
Ref country code: CA |