IP Library › Granted Patent US 9,565,218
Granted Patent B2
US 9,565,218 · App. 14/603,980 · Granted Feb 7, 2017

Resource management for WebRTC

Inventors: Binod Pankajakshy Gangadharan (Bangalore, IN); Terje Strand (San Francisco, CA); Andreas E. Jansson (San Francisco, CA); Sharath Rajasekar (San Francisco, CA)
Assignee: Oracle International Corporation
H04L65/1069H04L65/608H04L67/145H04L67/26
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 9,565,218
App. No.
14/603,980
Granted
Feb 7, 2017
Kind
B2
Abstract

A system performs client wake up for real-time communications (“RTC”). The system closes a connection between a gateway and an RTC application of a device. The RTC application enters a sleeping mode when the connection to the gateway is closed. After closing the connection, the system receives a message intended for the RTC application. The system requests a push notification server to wake up the RTC application, reconnects the gateway with the RTC application, and delivers the message to the RTC application.

Claims (67)

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

closing a connection between a gateway and an RTC application of a device, wherein the RTC application enters a sleeping mode when the connection to the gateway is closed;

after the closing of the connection, receiving a message intended for the RTC application;

requesting a push notification server to wake up the RTC application, comprising the gateway sending a JavaScript Object Notation (JSON) message to the push notification server, the JSON message including a JSON for RTC (JsonRTC) session ID of the RTC, identifying information, and a token;

reconnecting the gateway with the RTC application; and

delivering the message to the RTC application.

2. The non-transitory computer-readable medium of claim 1 , wherein, prior to closing the connection, the performing further comprises:

creating an account for the device at the push notification server; and

obtaining identification information of the device from the push notification server, wherein the identification information comprises a key or an identifier (ID) corresponding to the device.

3. The non-transitory computer-readable medium of claim 2 , wherein the performing further comprises:

registering the RTC application with the push notification server; and

obtaining the token from the push notification server, wherein the token identifies the device and the RTC application.

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

wherein the RTC application provides the token to the gateway,

wherein the gateway stores the identification information and the token.

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

wherein the closing of the connection between the gateway and the RTC application is performed upon receiving a corresponding message by the gateway from the RTC application indicating that the RTC application is entering the sleeping mode,

wherein, upon receiving the corresponding message, the gateway stores data pertaining to the connection in a distributed storage and starts a timer thread to keep connections with one or more network entities open on behalf of the RTC application.

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

wherein the message that is intended for the RTC application is received from a user agent,

wherein the gateway stores the message at a fabric component.

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

wherein the RTC application is a WebRTC application,

wherein the connection is a WebSocket connection,

wherein the gateway is a WebRTC session controller.

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

closing a connection between a gateway and an RTC application of a device, wherein the RTC application enters a sleeping mode when the connection to the gateway is closed;

after the closing of the connection, receiving a message intended for the RTC application;

requesting a push notification server to wake up the RTC application, comprising the gateway sending a JavaScript Object Notation (JSON) message to the push notification server, the JSON message including a JSON for RTC (JsonRTC) session ID of the RTC, identifying information, and a token;

reconnecting the gateway with the RTC application; and

delivering the message to the RTC application.

9. The method of claim 8 further comprising:

prior to closing the connection,

creating an account for the device at the push notification server; and

obtaining identification information of the device from the push notification server, wherein the identification information comprises a key or an identifier (ID) corresponding to the device.

10. The method of claim 9 further comprising:

registering the RTC application with the push notification server; and

obtaining the token from the push notification server, wherein the token identifies the device and the RTC application.

11. The method of claim 10 ,

wherein the RTC application provides the token to the gateway,

wherein the gateway stores the identification information and the token.

12. The method of claim 8 ,

wherein the closing of the connection between the gateway and the RTC application is performed upon receiving a corresponding message by the gateway from the RTC application indicating that the RTC application is entering the sleeping mode,

wherein, upon receiving the corresponding message, the gateway stores data pertaining to the connection in a distributed storage and starts a timer thread to keep connections with one or more network entities open on behalf of the RTC application.

13. The method of claim 8 ,

wherein the message that is intended for the RTC application is received from a user agent,

wherein the gateway stores the message at a fabric component.

14. The method of claim 8 ,

wherein the RTC application is a WebRTC application,

wherein the connection is a WebSocket connection,

wherein the gateway is a WebRTC session controller.

15. A system for client wake up for real-time communications (RTC) comprising:

a closing module that closes a connection between a gateway and an RTC application of a device, wherein the RTC application enters a sleeping mode when the connection to the gateway is closed;

a receiving module that, after the closing of the connection, receives a message intended for the RTC application;

a requesting module that requests a push notification server to wake up the RTC application, wherein the gateway sends a JavaScript Object Notation (JSON) message to the push notification server, the JSON message including a JSON for RTC (JsonRTC) session ID of the RTC, identifying information, and a token;

a reconnecting module that reconnects the gateway with the RTC application; and

a delivering module that delivers the message to the RTC application.

16. The system of claim 15 , further comprising:

a creating module that, prior to closing the connection,

creates an account for the device at the push notification server, and

obtains identification information of the device from the push notification server, wherein the identification information comprises a key or an identifier (ID) corresponding to the device.

17. The system of claim 16 , further comprising:

a registering module that registers the RTC application with the push notification server; and

an obtaining module that obtains the token from the push notification server, wherein the token identifies the device and the RTC application.

18. The system of claim 17 ,

wherein the RTC application provides the token to the gateway,

wherein the gateway stores the identification information and the token.

Assignments (1)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 26, 2015
From: GANGADHARAN, BINOD PANKAJAKSHY; STRAND, TERJE; JANSSON, ANDREAS E.; RAJASEKAR, SHARATH
To: ORACLE INTERNATIONAL CORPORATION
Reel/Frame 034812/0246 →
Continuity (1)
Related Publication 20160219083A1 · Jul 28, 2016