WO2006136915A2 - System and method for establishing peer to peer connections between pcs and smart phones using networks with obstacles - Google Patents
System and method for establishing peer to peer connections between pcs and smart phones using networks with obstacles Download PDFInfo
- Publication number
- WO2006136915A2 WO2006136915A2 PCT/IB2006/001660 IB2006001660W WO2006136915A2 WO 2006136915 A2 WO2006136915 A2 WO 2006136915A2 IB 2006001660 W IB2006001660 W IB 2006001660W WO 2006136915 A2 WO2006136915 A2 WO 2006136915A2
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- peer
- peer device
- relay
- communication channel
- http
- Prior art date
Links
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/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/104—Peer-to-peer [P2P] networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L65/00—Network arrangements, protocols or services for supporting real-time applications in data packet communication
- H04L65/40—Support for services or applications
-
- 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/25—Mapping addresses of the same type
- H04L61/2503—Translation of Internet protocol [IP] addresses
- H04L61/256—NAT traversal
- H04L61/2578—NAT traversal without involvement of the NAT server
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/02—Network architectures or network communication protocols for network security for separating internal from external traffic, e.g. firewalls
- H04L63/029—Firewall traversal, e.g. tunnelling or, creating pinholes
-
- 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/01—Protocols
- H04L67/02—Protocols based on web technology, e.g. hypertext transfer protocol [HTTP]
-
- 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/50—Network services
- H04L67/56—Provisioning of proxy services
Definitions
- the present invention relates generally to firewalls and peer to peer connections. More specifically, the present invention relates to a system and method for establishing peer to peer (P2P) connections between PCS and smart phones or other devices, including personal computers, over a network that obstructs the straightforward establishment of such P2P connections using means such as firewalls and network address translation (NAT) servers.
- P2P peer to peer
- P2P peer-to-peer
- the user may directly share with other users the content he or she possesses.
- Each P2P protocol (Napster, Gnutella, Chord, FastTrack, etc) comes with a content location service, centralized or distributed, which permits the location of the peer(s) that contain a specified content.
- a location service Using such a location service, a user looking for some specific content may connect to the device of another user who offers the content in question and retrieve it from there.
- Firewalls are used to control the data traffic that goes through them.
- the great majority of such firewalls allow only solicited HTTP traffic to reach a smart phone or a PC, while plain IP traffic (over TCP or UDP) is blocked.
- plain IP traffic over TCP or UDP
- NAT servers also create obstacles to a P2P connection, especially for the case where one peer is a smart phone that roams across different CNOs while connected to the Internet. In that case, while the smart phone would be connected to a P2P overlay network, it will change its IP address and consequently it will lose all socket connections that have been established to its previous IP address.
- firewalls that implement the strict security policy of allowing only solicited HTTP traffic to reach a PC connected in the corporate network.
- CNO cellular network operator
- a number of solutions to P2P connections despite the presence of CNO firewalls have been proposed in the context of SIP deployment, since SIP traffic faces the same constraints from the firewalls as any other, unsolicited HTTP traffic. These solutions rely on the dynamic allocation of pinholes on the firewalls to allow SIP traffic to go through. Such solutions create another case of specific traffic, similar to the solicited HTTP traffic. They are not a generic solution to the establishment of P2P connections.
- exemplary embodiments described herein establish peer to peer connections between personal computers (PCs) and smart phones despite the obstacles imposed by firewalls, which allow only solicited HTTP traffic to go through, and by network address translation (NAT) servers, which change the IP address of roaming smart phones.
- exemplary embodiments utilize an HTTP-based protocol that does message relaying. The purpose of the protocol is to enable a socket connection between two terminals despite firewalls between them. The protocol uses HTTP requests and responses to relay the messages between the peers without expecting any favorable behavior from the firewalls (e.g., opening "pinholes" for specific TCP (transmission control protocol) or UDP (user datagram protocol) traffic).
- TCP transmission control protocol
- UDP user datagram protocol
- One exemplary embodiment relates to a method of circumventing network obstacles to provide a peer-to-peer communication channel between peers utilizing hypertext transfer protocol (HTTP).
- This method can include communicating a HTTP request from a peer device to a relay through a network including an obstacle where the HTTP request contains data intended for another peer device.
- the method further includes communicating data in a HTTP response from the relay to the peer device and establishing a communication channel between the two peer devices via the relay. The communication channel permits the peer device and the another peer device to send and receive data.
- HTTP hypertext transfer protocol
- Another exemplary embodiment relates to a system for circumventing network obstacles to provide a peer-to-peer communication channel between peers.
- the system can include a first peer device communicating with a relay via a network including an obstacle, a second peer device communicating with the same relay via a network including another device , and a server coupled to the first and second peer devices and including programmed instructions to carry out functions of relaying the communication from the first peer device to the second and vise versa .
- the server receives a HTTP request from the first peer device. This HTTP request includes data intended for another peer device.
- the server further relays the aforementioned data to the intended peer device establishing thus a virtual communication channel between the first peer device and the second peer device to enable sending and receiving of data.
- FIG. 1 Another exemplary embodiment relates to a computer program product to circumvent network obstacles and provide a peer-to-peer communication channel between peers utilizing hypertext transfer protocol (HTTP).
- the computer program product can include computer code that communicates a HTTP request from a peer device to a relay through a network including an obstacle and on to another peer device, computer code that communicates a HTTP response from the relay to the peer device, and computer code that establishes a communication channel between the peer device and the another peer device via the relay.
- the communication channel permits the peer device and the another peer device to send and receive data.
- FIG. 1 is a general diagram of a peer-to-peer system in accordance with an exemplary embodiment.
- FIG. 2 is a diagram depicting a sequence diagram of interactions between two peers and a relay in the peer-to-peer system of Fig. 1 in accordance with an exemplary embodiment.
- Fig. 1 illustrates a peer-to-peer system 10.
- the peer-to-peer system 10 includes a peer device 12, a cellular network operator (CNO) 14, a firewall 16, a network 18, a server 20, middlepoint software 22, a CNO 24, a firewall 26, and a peer device 28. Additional, fewer, or different devices can also be included in the peer-to-peer system 10 depending on the implementation or embodiment.
- the peer device 12 and peer device 28 include software identified in Fig. 1 as peer software 121 and peer software 281, such as a midlet that enables an application programming interface (API) for peer-to-peer communication with other peer devices.
- the network 18 can be the Internet or another similar network of devices.
- the server 20 is coupled to the network 18 and communicates using HTTP (hypertext transfer protocol) messages.
- the middlepoint software 22 is resident in the server 20 and provides instructions for facilitating peer- to-peer communication between peer devices.
- the middlepoint software 22 and server 20 function as a relay in the peer-to-peer communication between peer devices.
- Peer-to-peer communication in the peer-to-peer system 10 is carried out using a communication channel established between peers. From the viewpoint of an application 122 on peer device 12 and an application 282 on peer device 28, the communication channel operates as a socket connection. One peer listens for connections, another peer establishes a connection with the first one, and then both sides of the communication channel can send and receive data on that channel. Applications 122 and 282 on peer devices 12 and 28, respectively, can listen for connections, establish a connection, and send / receive data on an established connection. When a peer wants to allow other peers to connect to it and create a communication channel, the peer communicates to the server 20 the fact that this peer is listening for connections and the endpoint where the given peer listens for connections.
- a peer When a peer attempts to establish a connection with a remote peer, which presumably listens for connections, it must communicate to the server 20 the fact that this peer attempts to establish a connection to a remote peer and the endpoint of the remote peer, to which the given peer attempts to establish a connection.
- the server 20 does not buffer data.
- the server 20 keeps information about the established communication channels and forwards data sent by a peer to the intended recipient.
- the receiving peer buffers receives data until the received data is consumed by its associated application. Since the receiving buffer of a peer is of finite size, it is possible that it overflows (e.g., if the associated application consumes data slower than the corresponding peer receives data). In the occasion of such event, the receiving peer may notify the server 20 about the overflow. If the server 20 receives such a receiving-buffer overflow notification, the server 20 informs the peer that sent the data that caused the overflow about the event.
- the choice of whether a receiving peer notifies the server about the overflow of its receiving buffer depends on the properties of the established communication channel. If the communication channel is established as a non- reliable connection (e.g., a UDP datagram connection), then no notification need be sent by the peer that experiences the buffer overflow. If the communication channel is established as a reliable stream (e.g., a TCP session) then notification is produced by the peer that experiences the buffer overflow.
- a non- reliable connection e.g., a UDP datagram connection
- a reliable stream e.g., a TCP session
- Fig. 2 illustrates a sequence diagram of interactions between two peers and a relay in which a communication channel is established and data is exchanged over it.
- Peer A is listening for connections
- peer B establishes a connection to peer A
- peer A sends a message
- peer B sends a message.
- the interactions between a peer and the relay are defined as synchronous messages, associated with a response.
- a peer that wishes to listen for connections from other peers informs the relay about this intention by sending a LISTEN_REQ message to the relay that indicates the peer's intention to listen for connections.
- the relay sends a LISTEN_RSP message to the peer, indicating the success or the reason of failure of the attempted operation.
- the socket- server accepts connections on it.
- the given peer sends to the relay an ACCEPT_REQ message.
- the relay responds to the ACCEPTJREQ message with an ACCEPT_RSP message.
- the client-side of a socket that wants to establish a connection with a well-known server-side endpoint must attempt to connect to it.
- a peer sends to the relay a CONNECT_REQ message that indicates the peer's intention to connect to a given endpoint.
- the relay sends a CONNECT_RSP message to the peer, indicating the success or the reasons of failure of the attempted connection.
- each of the peers can send data to the other one and receive data from it.
- the act of sending data is taken by a peer when it has data to send.
- the data are sent to the relay, which forwards them to the other end of the established connection without buffering them.
- the sent data must be delivered to the receiving end of a connection immediately.
- the act of receiving data is possible at all times at each end of an established connection.
- the fact that sent data are delivered at the receiving end without buffering at the relay does not mean that the application, which uses sockets for remote communication, must consume the received data immediately. Rather, it is the responsibility of the code at the receiving end to buffer the received data until the application attempts to read them. Then, the application at the receiving end must perform a local operation of retrieving data from its incoming buffer. The local operation blocks if the incoming buffer is empty.
- a peer sends to the relay a RECEIVE_REQ message, which indicates the readiness of the peer to receive data.
- the relay answers the RECEIVE_REQ message with a RECEIVE_RSP message which contains the data sent to the peer in question.
- a peer has data to send over an established connection, it sends them to the relay with a SENDJREQ message.
- the relay forwards the received data to the intended recipient and sends back a SEND_RSP message to the sending peer.
- the techniques described with reference to Figs. 1 and 2 have several advantages.
- the approach described does not require any changes in the existing infrastructure, neither does it conflict with current firewall policies. It delivers peer-to-peer connection while using standard HTTP and obeying the strictest firewall policies.
- it is easy to use, allowing the developers to use the technique as an alternative to TCP/IP sockets without having to invest any effort in learning a new protocol.
- the approach has small impact on the peers.
- the only thing a peer needs to have in order to be able to use the protocol is the midlet that implements the API. This API code does not represent a significant amount of code; neither does it represent a significant execution overhead on the peer.
- 1 and 2 provides a robust peer-to-peer communication protocol despite a number of firewalls that may be placed between two peers.
- the reliability of the approach stems from the fact that it does not attempt to take advantage of holes in the security policies realized by the firewalls. Neither does it rely on special features implemented by few current firewalls or expected to be implemented by future firewalls. Rather, the approach builds on the minimum set of rules that are followed by the majority of the firewalls today, such as allowing solicited HTTP traffic to reach terminals inside the firewall- protected network.
- the approach described herein is different than existing peer-to-peer socket implementations, such as the JXTA peer-to-peer sockets (described in the article "Introduction to Peer-to-Peer Sockets," which is available at the web address http://www.codinginparadise.Org/p2psockets/l.html ).
- the JXTA P2P socket approach requires the entire JXTA infrastructure to work, whereas the approach of the exemplary embodiments requires only HTTP communications.
- the JXTA P2P sockets cannot circumvent firewalls that are not part of the JXTA framework.
- the exemplary embodiments can circumvent any firewall that allows as little as only solicited HTTP traffic. .
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computer Security & Cryptography (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Multimedia (AREA)
- Computer And Data Communications (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
- Information Transfer Between Computers (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
Description
Claims
Priority Applications (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
JP2008517620A JP2008544386A (en) | 2005-06-22 | 2006-06-20 | System and method for establishing a peer-to-peer connection between a PC and a smartphone using a faulty network |
EP06779738.1A EP1897336B1 (en) | 2005-06-22 | 2006-06-20 | System and method for establishing peer to peer connections between pcs and smart phones using networks with obstacles |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/158,710 | 2005-06-22 | ||
US11/158,710 US8874691B2 (en) | 2005-06-22 | 2005-06-22 | System and method for establishing peer to peer connections between PCS and smart phones using networks with obstacles |
Publications (2)
Publication Number | Publication Date |
---|---|
WO2006136915A2 true WO2006136915A2 (en) | 2006-12-28 |
WO2006136915A3 WO2006136915A3 (en) | 2007-03-08 |
Family
ID=37568899
Family Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
PCT/IB2006/001660 WO2006136915A2 (en) | 2005-06-22 | 2006-06-20 | System and method for establishing peer to peer connections between pcs and smart phones using networks with obstacles |
Country Status (6)
Country | Link |
---|---|
US (2) | US8874691B2 (en) |
EP (1) | EP1897336B1 (en) |
JP (1) | JP2008544386A (en) |
KR (1) | KR101004385B1 (en) |
CN (1) | CN101233739A (en) |
WO (1) | WO2006136915A2 (en) |
Families Citing this family (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
KR100810759B1 (en) * | 2006-02-17 | 2008-03-07 | 엔에이치엔(주) | P2P File Transmission System and Method |
US8082363B2 (en) * | 2006-05-12 | 2011-12-20 | Hewlett-Packard Development Company, L.P. | Multiplexed communication between host computer and smartphone used as wireless modem |
US8798075B2 (en) * | 2006-06-30 | 2014-08-05 | Sony Corporation | Peer to peer connection |
CN101425958A (en) * | 2007-10-29 | 2009-05-06 | 华为技术有限公司 | Request answering method, apparatus and system in P2P overlapping network |
EP2071809A1 (en) * | 2007-12-13 | 2009-06-17 | Alcatel Lucent | Method of establishing a connection in a peer-to-peer network with network address translation (NAT) |
JP5304555B2 (en) * | 2009-09-11 | 2013-10-02 | ブラザー工業株式会社 | Terminal device, communication method, and communication program |
CN102271144A (en) * | 2010-06-01 | 2011-12-07 | 中兴通讯股份有限公司 | P2P (point to point) overlay network, data resource operating method and new node adding method |
CN107347110A (en) * | 2016-05-06 | 2017-11-14 | 杭州云沣科技有限公司 | Intelligent terminal tele-control system |
US10097670B2 (en) * | 2016-05-19 | 2018-10-09 | Adobe Systems Incorporated | Facilitating personalized video messages using peer-to-peer communications |
CN106790494A (en) * | 2016-12-14 | 2017-05-31 | 北京佰才邦技术有限公司 | The update method and buffer memory device of a kind of address information |
US11238428B1 (en) * | 2018-04-25 | 2022-02-01 | Marvell Asia Pte, Ltd. | System and method for secure transactions to transmit cryptocurrency |
CN109600449A (en) * | 2018-12-24 | 2019-04-09 | 深圳市网心科技有限公司 | A kind of P2P penetrating method, device, system and storage medium |
US10972450B1 (en) | 2019-04-15 | 2021-04-06 | Wells Fargo Bank, N.A. | Systems and methods for securely migrating data between devices |
WO2021056069A1 (en) * | 2019-09-25 | 2021-04-01 | Commonwealth Scientific And Industrial Research Organisation | Cryptographic services for browser applications |
Family Cites Families (23)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7003463B1 (en) * | 1998-10-02 | 2006-02-21 | International Business Machines Corporation | System and method for providing network coordinated conversational services |
US6789119B1 (en) * | 1999-11-24 | 2004-09-07 | Webex Communication, Inc. | Emulating a persistent connection using http |
US7814208B2 (en) * | 2000-04-11 | 2010-10-12 | Science Applications International Corporation | System and method for projecting content beyond firewalls |
US7028091B1 (en) * | 2000-08-31 | 2006-04-11 | Sun Microsystems, Inc. | Web server in-kernel interface to data transport system and cache manager |
US6685093B2 (en) * | 2001-09-25 | 2004-02-03 | Ecrio, Inc. | System, method and apparatus for communicating information between a mobile communications device and a bar code reader |
WO2002057917A2 (en) * | 2001-01-22 | 2002-07-25 | Sun Microsystems, Inc. | Peer-to-peer network computing platform |
EP1388073B1 (en) * | 2001-03-01 | 2018-01-10 | Akamai Technologies, Inc. | Optimal route selection in a content delivery network |
US7222306B2 (en) * | 2001-05-02 | 2007-05-22 | Bitstream Inc. | Methods, systems, and programming for computer display of images, text, and/or digital content |
US20030105812A1 (en) * | 2001-08-09 | 2003-06-05 | Gigamedia Access Corporation | Hybrid system architecture for secure peer-to-peer-communications |
CA2410172A1 (en) * | 2001-10-29 | 2003-04-29 | Jose Alejandro Rueda | Content routing architecture for enhanced internet services |
US20030131258A1 (en) * | 2002-01-04 | 2003-07-10 | Kadri Seemab Aslam | Peer-to-peer communication across firewall using internal contact point |
US7200668B2 (en) * | 2002-03-05 | 2007-04-03 | Sun Microsystems, Inc. | Document conversion with merging |
JP2003273937A (en) | 2002-03-19 | 2003-09-26 | Hitachi Ltd | Service gateway device |
JP4315696B2 (en) * | 2002-03-29 | 2009-08-19 | 富士通株式会社 | Host terminal emulation program, relay program, and host terminal emulation method |
US7318073B2 (en) * | 2002-05-31 | 2008-01-08 | Microsoft Corporation | System and method for downloading information to a mobile device |
US7296288B1 (en) * | 2002-11-15 | 2007-11-13 | Packeteer, Inc. | Methods, apparatuses, and systems allowing for bandwidth management schemes responsive to utilization characteristics associated with individual users |
US7769881B2 (en) * | 2003-01-24 | 2010-08-03 | Hitachi, Ltd. | Method and apparatus for peer-to peer access |
US7774495B2 (en) * | 2003-02-13 | 2010-08-10 | Oracle America, Inc, | Infrastructure for accessing a peer-to-peer network environment |
US7257837B2 (en) * | 2003-07-26 | 2007-08-14 | Innomedia Pte | Firewall penetration system and method for real time media communications |
JP4269226B2 (en) * | 2003-11-14 | 2009-05-27 | ソニー株式会社 | Information communication system and method, information processing apparatus and method, program, and recording medium |
US7346925B2 (en) * | 2003-12-11 | 2008-03-18 | Microsoft Corporation | Firewall tunneling and security service |
US7716339B2 (en) * | 2004-09-11 | 2010-05-11 | Oracle International Corporation | System and method for discretization of client-server interactions |
US7646775B2 (en) * | 2005-03-08 | 2010-01-12 | Leaf Networks, Llc | Protocol and system for firewall and NAT traversal for TCP connections |
-
2005
- 2005-06-22 US US11/158,710 patent/US8874691B2/en not_active Expired - Fee Related
-
2006
- 2006-06-20 CN CNA2006800282980A patent/CN101233739A/en active Pending
- 2006-06-20 KR KR1020087001593A patent/KR101004385B1/en not_active IP Right Cessation
- 2006-06-20 JP JP2008517620A patent/JP2008544386A/en active Pending
- 2006-06-20 EP EP06779738.1A patent/EP1897336B1/en not_active Not-in-force
- 2006-06-20 WO PCT/IB2006/001660 patent/WO2006136915A2/en active Application Filing
-
2014
- 2014-09-12 US US14/484,510 patent/US9258362B2/en not_active Expired - Fee Related
Non-Patent Citations (1)
Title |
---|
See references of EP1897336A4 * |
Also Published As
Publication number | Publication date |
---|---|
JP2008544386A (en) | 2008-12-04 |
EP1897336A2 (en) | 2008-03-12 |
US8874691B2 (en) | 2014-10-28 |
KR101004385B1 (en) | 2010-12-28 |
EP1897336A4 (en) | 2012-12-12 |
US9258362B2 (en) | 2016-02-09 |
US20060294213A1 (en) | 2006-12-28 |
EP1897336B1 (en) | 2015-08-12 |
KR20080019717A (en) | 2008-03-04 |
US20140379875A1 (en) | 2014-12-25 |
CN101233739A (en) | 2008-07-30 |
WO2006136915A3 (en) | 2007-03-08 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
EP1897336B1 (en) | System and method for establishing peer to peer connections between pcs and smart phones using networks with obstacles | |
RU2660620C1 (en) | Communication device and method of bypassing gateway firewall of application layer in setting rts communication connection between rts-client and rts-server | |
US7769871B2 (en) | Technique for sending bi-directional messages through uni-directional systems | |
EP1892887B1 (en) | Communication method between communication devices and communication apparatus | |
US8868757B1 (en) | Two-way web service router gateway | |
JP5378494B2 (en) | Data transmission system and method using relay server | |
US20070136413A1 (en) | Sip server sharing module and sip message relay system | |
US20070233844A1 (en) | Relay device and communication system | |
EP1735941A2 (en) | Method and system for providing web browsing through a firewall in a peer to peer network | |
US8788682B2 (en) | Communication device, and method, in an internet protocol network, of controlling a communication device | |
CA2408766A1 (en) | Content delivery network bypass system | |
CN105743852B (en) | Method and system for realizing Socket connection maintaining communication across network gate through http | |
EP3468152B1 (en) | Two-way transparent proxy method and system | |
Takasugi et al. | Seamless service platform for following a user's movement in a dynamic network environment | |
AU2004300728B2 (en) | Communication system, computer comprising a peer-to-peer message filter and method for processing a peer-to-peer message | |
US20090028110A1 (en) | Seamless Establishment and Maintenance of Network Connections for Mobile Applications | |
US11716222B2 (en) | Communications bridge | |
JP2009055418A (en) | Communicating system, relay device, terminal, relay processing method, and its program | |
Bhagwat et al. | MSOCKS+: an architecture for transport layer mobility | |
CN116708381B (en) | Cross-network data transmission method and device, storage medium and electronic equipment | |
KR100463221B1 (en) | File Transfer System Through A Gateway Server | |
Cassagnes et al. | An overlay architecture for achieving total flexibility in internet communications | |
Arnes et al. | Cloudless Friend-to-Friend Middleware for Smartphones | |
KR20170111305A (en) | A network bridging method and computer network system thereof seamlessly supporting UDP protocols between the separated networks | |
Fairhurst | Datagram congestion control protocol (DCCP) simultaneous-open technique to facilitate NAT/middlebox traversal |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
121 | Ep: the epo has been informed by wipo that ep was designated in this application | ||
NENP | Non-entry into the national phase |
Ref country code: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2008517620 Country of ref document: JP |
|
WWW | Wipo information: withdrawn in national office |
Ref document number: DE |
|
WWE | Wipo information: entry into national phase |
Ref document number: 2006779738 Country of ref document: EP |
|
WWE | Wipo information: entry into national phase |
Ref document number: 1020087001593 Country of ref document: KR |
|
WWE | Wipo information: entry into national phase |
Ref document number: 200680028298.0 Country of ref document: CN |
|
WWP | Wipo information: published in national office |
Ref document number: 2006779738 Country of ref document: EP |