System and method for signaling and data tunneling in a peer-to-peer environment

• US 10,027,745 B2
• Filed: 09/09/2014
• Issued: 07/17/2018
• Est. Priority Date: 02/15/2010
• Status: Active Grant

• Current Assignee: Damaka, Inc.
• Original Assignee: Damaka, Inc.
• Inventors: Chaturvedi, Sivakumar R., Gundabathula, Satish
• Primary Examiner(s): Survillo, Oleg
• Application Number:
  US14/480,699
• Publication Number:
  US 20140379791A1
• Time in Patent Office: 1,407 Days
• Field of Search: 709227, 709229, 709238, 709249
• CPC Class Codes: H04L 45/26 Route discovery packet
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 51/043 using or handling presence information
• CPC Class Codes: H04L 61/2564 for a higher-layer protocol, e.g. for session initiation protocol [SIP]
• CPC Class Codes: H04L 61/2567 for reachability, e.g. inquiring the address of a correspondent behind a NAT server
• CPC Class Codes: H04L 61/2575 using address mapping retrieval, e.g. simple traversal of user datagram protocol through session traversal utilities for NAT [STUN]
• CPC Class Codes: H04L 61/2589 over a relay server, e.g. traversal using relay for network address translation [TURN]
• CPC Class Codes: H04L 67/104 Peer-to-peer [P2P] networks
• CPC Class Codes: H04L 67/54 Presence management, e.g. monitoring or registration for receipt of user log-on information, or the connection status of the users
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]

Abstract

An improved system and method are disclosed for peer-to-peer communications. In one example, the method enables an endpoint to use a tunneling server to bypass a network address translation (NAT) device that is blocking messages to an endpoint on the other side of the NAT device.

Claims

1. A method for use by a tunneling server in a peer-to-peer hybrid network comprising:

establishing, by the tunneling server, a connection with a first endpoint in response to a connection request from the first endpoint;

receiving, by the tunneling server, a request from the first endpoint for a plurality of shadow ports on the tunneling server;

creating, by the tunneling server, the plurality of shadow ports;

sending, by the tunneling server, a shadow network address and the shadow ports to the first endpoint;

receiving, by the tunneling server, a message from the first endpoint;

extracting, by the tunneling server, a destination network address and a destination port from the message;

determining, by the tunneling server, whether the destination network address matches a network address of the tunneling server, wherein a match indicates that the destination port is a shadow port on the tunneling server; and

sending, by the tunneling server, the message out of the tunneling server to a second endpoint corresponding to the destination network address only if the destination network address does not match the network address of the tunneling server.

2. The method of claim 1 further comprising:

determining, by the tunneling server, whether the shadow port is associated with a third endpoint if the destination network address matches the network address of the tunneling server; and

moving, by the tunneling server, the message to a buffer internal to the tunneling server if the shadow port is associated with the third endpoint, wherein the buffer corresponds to an endpoint associated with the destination port and the message is not sent out of the tunneling server.

3. The method of claim 2 further comprising sending, by the tunneling server, a notification message to the first endpoint that the message cannot be delivered if the destination network address matches the network address of the tunneling server and the shadow port is not associated with an endpoint.

4. The method of claim 3 further comprising dropping, by the tunneling server, the message if the destination network address matches the network address of the tunneling server and the shadow port is not associated with an endpoint.

5. The method of claim 2 further comprising:

determining, by the tunneling server, that the third endpoint associated with the shadow port is communicating with the first endpoint via a tunnel between the third endpoint and the tunneling server; and

releasing, by the tunneling server, the shadow ports created for the first endpoint.

6. The method of claim 1 further comprising sending, by the tunneling server, a notification message to the first endpoint identifying another tunneling server available for use by the first endpoint.