Efficient tunneled streams for real-time communications

• US 10,015,287 B2
• Filed: 03/04/2015
• Issued: 07/03/2018
• Est. Priority Date: 03/04/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Herrero, Rolando, Katz, Henry
• Primary Examiner(s): Rashid, Harunur
• Application Number:
  US14/638,434
• Publication Number:
  US 20160261559A1
• Time in Patent Office: 1,217 Days
• CPC Class Codes: H04L 12/4633 Interconnection of networks using encapsulation techniques, e.g. tunneling
• CPC Class Codes: H04L 65/60 Network streaming of media packets
• CPC Class Codes: H04L 67/01 Protocols
• CPC Class Codes: H04L 69/10 Streamlined, light-weight or high-speed protocols, e.g. express transfer protocol [XTP] or byte stream
• CPC Class Codes: H04L 69/16 Implementation or adaptation of Internet protocol [IP], of transmission control protocol [TCP] or of user datagram protocol [UDP]
• CPC Class Codes: H04L 69/163 In-band adaptation of TCP data exchange; In-band control procedures

Abstract

A system tunnels real-time communications (“RTC”). The system creates a connection between a tunneling client and a signaling server. The connection includes a stream-based tunnel between the tunneling client and a tunneling server and a stream connection between the tunneling server and the signaling server. The system then receives, from the tunneling client, stream traffic encapsulated as datagram traffic within the stream-based tunnel. The system translates the datagram traffic into the stream traffic, and forwards the stream traffic to the signaling server over the stream connection.

Claims

1. A non-transitory computer-readable medium having instructions stored thereon that, when executed by a processor, cause the processor to perform tunneling for real-time communications (RTC), the performing comprising:

creating a connection between a tunneling client on a user equipment configured to execute an application and a signaling server configured to receive signaling traffic within a service provider network , the creating including

opening a stream-based tunnel between the tunneling client and a tunneling server interposed between the user equipment and the signaling server; and

subsequently to the opening the stream-based tunnel, opening a stream connection between the tunneling server and the signaling server;

encapsulating a plurality of inner streams from the user equipment as datagram traffic;

receiving at the tunneling server, from the tunneling client, the datagram traffic including the encapsulated plurality of inner streams within the stream-based tunnel, wherein the datagram traffic behaves as a connectionless transmission;

translating the datagram traffic at the tunneling server into stream traffic using a socket application programming interface (API), wherein an inner transmission control protocol (TCP) layer of the application is modified to behave as the datagram traffic while preserving a same software interface with TCP sockets; and

transmitting the stream traffic from the tunneling server to the signaling server over the stream connection.

2. The non-transitory computer-readable medium of claim 1,

wherein the connection is initiated by the tunneling client by sending a service request control message according to a tunneled services control function (TSCF) standard;

wherein the tunneling server translates the service request control message to a first TCP packet for initiating the connection;

wherein the tunneling server forwards the first TCP packet to the signaling server; and

wherein the encapsulating and the translating avoids creating a double stream stack.

3. The non-transitory computer-readable medium of claim 2,

wherein the service request control message includes a first TSCF Type Length Value (TLV) indicating source and destination information corresponding to the connection.

4. The non-transitory computer-readable medium of claim 3,

wherein, in response to the first TCP packet, the tunneling server receives a second TCP packet from the signaling server;

wherein the tunneling server translates the second TCP packet into a service response control message according to TSCF; and

wherein the tunneling server forwards the service response control message to the tunneling client.

5. The non-transitory computer-readable medium of claim 4,

wherein the service response control message includes a second TSCF TLV indicating a connection identifier corresponding to the connection.

6. The non-transitory computer-readable medium of claim 1,

wherein the connection is terminated by the tunneling client by sending a service request control message according to a tunneled services control function (TSCF) standard;

wherein the tunneling server translates the service request control message to a transmission control protocol (TCP) packet for terminating the connection; and

wherein the tunneling server forwards the TCP packet to the signaling server.

7. The non-transitory computer-readable medium of claim 1,

wherein the connection is initiated by the signaling server by sending a transmission control protocol (TCP) packet to tunneling server for initiating the connection;

wherein the tunneling server translates the TCP packet into a service request control message for initiating the connection according to a tunneled services control function (TSCF) standard; and

wherein the tunneling server forwards the service request control message to the tunneling client.

8. A method of tunneling for real-time communications (RTC), comprising:

creating a connection between a tunneling client on a user equipment configured to execute an application and a signaling server configured to receive signaling traffic within a service provider network, the creating including

opening a stream-based tunnel between the tunneling client and a tunneling server interposed between the user equipment and the signaling server; and

subsequently to the opening the stream-based tunnel, opening a stream connection between the tunneling server and the signaling server;

encapsulating a plurality of inner streams from the user equipment as datagram traffic;

receiving at the tunneling server, from the tunneling client, the datagram traffic including the encapsulated plurality of inner streams within the stream-based tunnel, wherein the datagram traffic behaves as a connectionless transmission;

translating the datagram traffic at the tunneling server into stream traffic using a socket application programming interface (API), wherein an inner transmission control protocol (TCP) layer of the application is modified to behave as the datagram traffic while preserving a same software interface with TCP sockets; and

transmitting the stream traffic from the tunneling server to the signaling server over the stream connection.

9. The method of claim 8,

wherein the connection is initiated by the tunneling client by sending a service request control message according to a tunneled services control function (TSCF) standard;

wherein the tunneling server translates the service request control message to a first TCP packet for initiating the connection;

wherein the tunneling server forwards the first TCP packet to the signaling server; and

wherein the encapsulating and the translating avoids creating a double stream stack.

10. The method of claim 9,

wherein the service request control message includes a first TSCF Type Length Value (TLV) indicating source and destination information corresponding to the connection.

11. The method of claim 10,

wherein, in response to the first TCP packet, the tunneling server receives a second TCP packet from the signaling server;

wherein the tunneling server translates the second TCP packet into a service response control message according to TSCF; and

wherein the tunneling server forwards the service response control message to the tunneling client.

12. The method of claim 11,

wherein the service response control message includes a second TSCF TLV indicating a connection identifier corresponding to the connection.

13. The method of claim 8,

wherein the connection is terminated by the tunneling client by sending a service request control message according to a tunneled services control function (TSCF) standard;

wherein the tunneling server translates the service request control message to a transmission control protocol (TCP) packet for terminating the connection; and

wherein the tunneling server forwards the TCP packet to the signaling server.

14. The method of claim 8,

wherein the connection is initiated by the signaling server by sending a transmission control protocol (TCP) packet to tunneling server for initiating the connection;

wherein the tunneling server translates the TCP packet into a service request control message for initiating the connection according to a tunneled services control function (TSCF) standard; and

wherein the tunneling server forwards the service request control message to the tunneling client.

15. A system for tunneling of real-time communications (RTC), comprising:

a hardware processor configured to;

create a connection between a tunneling client on a user equipment configured to execute an application and a signaling server configured to receive signaling traffic within a service provider network, the creation of the connection including

opening a stream-based tunnel between the tunneling client and a tunneling server interposed between the user equipment and the signaling server; and

subsequently to the opening the stream-based tunnel, opening a stream connection between the tunneling server and the signaling server

encapsulate a plurality of inner streams from the user equipment as datagram traffic;

receive at the tunneling server, from the tunneling client, the datagram traffic including the encapsulated plurality of inner streams within the stream-based tunnel, wherein the datagram traffic behaves as a connectionless transmission;

translate the datagram traffic at the tunneling server into stream traffic using a socket application programming interface (API), wherein an inner transmission control protocol (TCP) layer of the application is modified to behave as the datagram traffic while preserving a same software interface with TCP sockets; and

transmit the stream traffic from the tunneling server to the signaling server over the stream connection.

16. The system of claim 15,

wherein the connection is initiated by the tunneling client by sending a service request control message according to a tunneled services control function (TSCF) standard;

wherein the tunneling server translates the service request control message to a first TCP packet for initiating the connection;

wherein the tunneling server forwards the first TCP packet to the signaling server; and

wherein the encapsulation and the translation avoids creating a double stream stack.

17. The system of claim 16,

wherein the service request control message includes a first TSCF Type Length Value (TLV) indicating source and destination information corresponding to the connection.

18. The system of claim 17,

wherein, in response to the first TCP packet, the tunneling server receives a second TCP packet from the signaling server;

wherein the tunneling server translates the second TCP packet into a service response control message according to TSCF; and

wherein the tunneling server forwards the service response control message to the tunneling client.

19. The system of claim 18,

wherein the service response control message includes a second TSCF TLV indicating a connection identifier corresponding to the connection.

20. The system of claim 15,

wherein the connection is terminated by the tunneling client by sending a service request control message according to a tunneled services control function (TSCF) standard;

wherein the tunneling server translates the service request control message to a TCP packet for terminating the connection; and

wherein the tunneling server forwards the TCP packet to the signaling server.