Real-time communications gateway

• US 9,648,052 B2
• Filed: 01/23/2015
• Issued: 05/09/2017
• Est. Priority Date: 01/23/2015
• Status: Active Grant

• Current Assignee: Oracle International Corporation (Oracle Corporation)
• Original Assignee: Oracle International Corporation (Oracle Corporation)
• Inventors: Gangadharan, Binod Pankajakshy, Sang, Yumin, Zhang, Shuquan, Li, Yuwei, Wang, Robby, Melo, Michael D.
• Primary Examiner(s): Cheema, Umar
• Assistant Examiner(s): Wang, Hannah S
• Application Number:
  US14/604,086
• Publication Number:
  US 20160219093A1
• Time in Patent Office: 837 Days
• Field of Search: 709215
• CPC Class Codes: H04L 65/1059 End-user terminal functionalities specially adapted for real-time communication
• CPC Class Codes: H04L 65/1069 Session establishment or de-establishment
• CPC Class Codes: H04L 65/1104 Session initiation protocol [SIP]
• CPC Class Codes: H04L 67/303 Terminal profiles
• CPC Class Codes: H04L 69/24 Negotiation of communication capabilities
• CPC Class Codes: H04N 21/00 Selective content distribution, e.g. interactive television or video on demand [VOD] real-time bi-directional transmission of motion video data H04N7/14 ; broadcast or conference over packet switching networks H04L12/18
• CPC Class Codes: H04N 21/6437 Real-time Transport Protocol [RTP]

Abstract

A system performs Real-Time Communications (“RTC”). The system establishes a signaling channel between a browser application and a rich communications services (“RCS”) endpoint. The system then queries RCS capabilities of the RCS endpoint via the signaling channel, and initiates the RTC between the browser application and the RCS endpoint via the signaling channel.

Claims

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

establishing a signaling channel between a browser application and a rich communications services (RCS) endpoint, wherein the browser application is a WebRTC application and the signaling channel supports Message Session Relay Protocol (MSRP) communications over WebSockets, wherein the WebRTC application establishes the signaling channel with a signaling engine within a WebRTC Session Controller (WSC) according to a JavaScript Object Notation (JSON) protocol for RTC (JsonRTC);

querying RCS capabilities of the RCS endpoint via the signaling channel via an application programming interface (API) in a JavaScript software development kit (SDK) implemented at the browser application;

initiating the RTC between the browser application and the RCS endpoint via the signaling channel; and

creating a WebSocket listener by a media engine of the WSC for the MSRP communications, wherein the WebSocket listener is created based on parameters received by the signaling engine over a Session Initiation Protocol (SIP) from the RCS endpoint.

2. The non-transitory computer-readable medium of claim 1, wherein the WSC is configured to translate the JsonRTC protocol to the SIP in conformance with RCS.

3. The non-transitory computer-readable medium of claim 1, wherein the

parameters comprise Session Description Protocol (SDP) communications.

4. The non-transitory computer-readable medium of claim 1, wherein the WebSocket listener has a complete uniform resource identifier (URI) comprising an ephemeral port and a unique context root.

5. The non-transitory computer-readable medium of claim 1, wherein the RTC is an RCS compliant RTC with the RCS endpoint via the application programming interface (API) in the JavaScript software development kit (SDK).

6. The non-transitory computer-readable medium of claim 5, wherein the RCS compliant RTC comprises at least one of standalone messaging, 1-1 chat, group chat, file transfer, image sharing, or video sharing.

7. The non-transitory computer-readable medium of claim 1, wherein the querying of the RCS capabilities of the RCS endpoint is implemented by Groovy scripts executed in the signaling engine within the WebRTC Session Controller (WSC).

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

establishing a signaling channel between a browser application and a rich communications services (RCS) endpoint, wherein the browser application is a WebRTC application and the signaling channel supports Message Session Relay Protocol (MSRP) communications over WebSockets, wherein the WebRTC application establishes the signaling channel with a signaling engine within a WebRTC Session Controller (WSC) according to a JavaScript Object Notation (JSON) protocol for RTC (JsonRTC);

querying RCS capabilities of the RCS endpoint via the signaling channel via an application programming interface (API) in a JavaScript software development kit (SDK) implemented at the browser application;

initiating the RTC between the browser application and the RCS endpoint via the signaling channel; and

creating a WebSocket listener by a media engine of the WSC for the MSRP communications, wherein the WebSocket listener is created based on parameters received by the signaling engine over a Session Initiation Protocol (SIP) from the RCS endpoint.

9. The method claim 8, wherein the WSC is configured to translate the JsonRTC protocol to the SIP in conformance with RCS.

10. The method of claim 8, wherein the parameters comprise Session Description Protocol (SDP) communications.

11. The method of claim 8, wherein the WebSocket listener has a complete uniform resource identifier (URI) comprising an ephemeral port and a unique context root.

12. The method claim 8, wherein the RTC is an RCS compliant RTC with the RCS endpoint via the API in the JavaScript SDK.

13. The method claim 12, wherein the RCS compliant RTC comprises at least one of standalone messaging, 1-1 chat, group chat, file transfer, image sharing, or video sharing.

14. The method claim 8, wherein the querying of the RCS capabilities of the RCS endpoint is implemented by Groovy scripts executed in the signaling engine within the WSC.

15. A real-time communications (RTC) system comprising:

a processor executing instructions stored in memory to implement a plurality of modules comprising;

an establishing module that establishes a signaling channel between a browser application and a rich communications services (RCS) endpoint, wherein the browser application is a WebRTC application and the signaling channel supports Message Session Relay Protocol (MSRP) communications over WebSockets, wherein the WebRTC application establishes the signaling channel with a signaling engine within a WebRTC Session Controller (WSC) according to a JavaScript Object Notation (JSON) protocol for RTC (JsonRTC);

a querying module that queries RCS capabilities of the RCS endpoint via the signaling channel via an application programming interface (API) in a JavaScript software development kit (SDK) implemented at the browser application;

an initiating module that initiates the RTC between the browser application and the RCS endpoint via the signaling channel; and

a creating module that creates a WebSocket listener by a media engine of the WSC for the MSRP communications, wherein the WebSocket listener is created based on parameters received by the signaling engine over a Session Initiation Protocol (SIP) from the RCS endpoint.

16. The system of claim 15, wherein the WSC is configured to translate the JsonRTC protocol to the SIP in conformance with RCS.

17. The system of claim 15, wherein the parameters comprise Session Description Protocol (SDP) communications.

18. The system of claim 15, wherein the RTC is an RCS compliant RTC with the RCS endpoint via the API in the JavaScript SDK.

19. The system of claim 18, wherein the RCS compliant RTC comprises at least one of standalone messaging, 1-1 chat, group chat, file transfer, image sharing, or video sharing.

20. The system of claim 15, wherein the querying of the RCS capabilities of the RCS endpoint is implemented by Groovy scripts executed in the signaling engine within the WSC.