IP Library Granted Patent US 9,525,588
Granted Patent B2
US 9,525,588 · App. 13/810,496 · Granted Dec 20, 2016

Push content to a currently utilized device among client devices

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,525,588
App. No.
13/810,496
Granted
Dec 20, 2016
Kind
B2
Abstract

In one example, a system includes an authentication server that is configured to receive an authentication request for a primary application, provide time-based authentication credentials for the primary application, receive an updated authentication request for the primary application, wherein the updated authentication request includes a client device identifier (ID) corresponding to a client device from which the authentication request is received, and transmit the client device ID; the system may further include a push server that is configured to receive the transmitted client device ID, and push an update to the client device having the client device ID.

Claims (39)

1. A system, comprising:

an authentication server comprising at least one computer processor, the authentication server configured to:

receive an authentication request from a client device for an authentication service,

provide time-limited authentication credentials for a user of a primary application of the authentication service,

receive, from a client device other than the client device from which the authentication request is received, an updated authentication request for the authentication service when the primary application for which the time-limited authentication credentials were given or one or more dependent applications is utilized on the client device other than the client device from which the authentication request is received, wherein the updated authentication request includes a client device identifier (ID) corresponding to the client device from which the updated authentication request is received,

provide the client device ID corresponding to the client device from which the updated authentication request is received to a push server corresponding to the authentication service, and

provide a client device ID corresponding to the client device from which the authentication request has been received within a predetermined amount of time to the push server; and

the push server configured to:

receive the client device ID corresponding to the client device from which the updated authentication request is received and the client device ID corresponding to the client device from which the authentication request has been received,

push content, formatted in one format, to the client device having the client device ID corresponding to the client device from which the updated authentication request is received, and

push the content, formatted in another format, to the client device having the client device ID corresponding to the client device from which the authentication request has been received within a predetermined amount of time.

2. The system of claim 1 , wherein the one or more dependent applications utilize the time-limited authentication credentials provided for the user.

3. The system of claim 2 ,

wherein the user is authenticated for the authentication service and the one or more dependent applications on multiple client devices, and

wherein the authentication server is further configured to:

store a client device ID for at least one client device from which the updated authentication request has most recently been received, and

provide the client device ID of the client device from which the updated authentication request has most recently been received to the push server.

4. The system of claim 3 , wherein the push server is further configured to:

push the content, formatted in one format, to the client device having the client device ID of the client device from which the updated authentication request has most recently been received; and

push the content, formatted in another format, to the client device having the client device ID of the client device from others.

5. The system of claim 2 , wherein the authentication server is further configured to provide the client device ID corresponding to the client device from which the updated authentication request is received to a push server corresponding to the one or more dependent applications that are to receive content on a push basis.

6. The system of claim 2 , wherein the authentication server is further configured to provide the client device ID corresponding to the client device from which the authentication request has been received within a predetermined amount of time to a push server corresponding to the one or more dependent applications on a predetermined frequency.

7. The system of claim 2 , wherein the user is authenticated for the authentication service and the one or more dependent applications on multiple client devices.

8. The system of claim 2 ,

wherein the authentication server is further configured to:

store a client device ID for at least a subset of all client devices from which the user has requested authorization on the primary application, and

provide the client device ID corresponding to those of the subset of all client devices from which updated authentication requests have been received within a predetermined amount of time to the push server; and

wherein the push server is further configured to:

push the content for the user on the primary application to those of the subset of client devices from which the updated authentication requests have been received within the predetermined amount of time.

9. The system of claim 2 , wherein the push server is further configured to request a client ID via an API.

10. The system of claim 1 , wherein the authentication service is a cloud-based authentication service and the primary application or one or more dependent applications is a cloud-based application.

11. The system of claim 10 , wherein the cloud-based application is a widget that runs on the device.

12. The system of claim 1 , wherein the authentication server is an OAuth server.

13. A non-transitory computer-readable medium storing one or more computer-executable instructions that, when executed, cause one or more processors to:

responsive to receipt of an authentication request from a client device, provide credentials that enable multisite authorization for a user on a cloud-based service and one or more dependent cloud-based services;

receive a renewed authorization request from another client device having a corresponding device identifier (ID); and

provide the device ID to a push server corresponding to at least one of the cloud-based service or one or more of the dependent cloud-based services to facilitate a push service to the another client device having the corresponding device ID and to facilitate the push service to a subset of client devices for which the multisite authorization has been provided,

wherein the push service to the another client device transmits content, formatted in one format, and the push service to the subset of client devices transmits the content, formatted in another format.

14. The non-transitory computer-readable medium of claim 13 , wherein the push service to the subset of client devices transmits an indication that corresponding updates have been read elsewhere.

Assignments (3)
SECURITY INTEREST Recorded Jan 29, 2019
From: EMPIRE TECHNOLOGY DEVELOPMENT LLC
To: CRESTLINE DIRECT FINANCE, L.P.
Reel/Frame 048373/0217 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2013
From: KRUGLICK, EZEKIEL
To: ARDENT RESEARCH CORPORATION
Reel/Frame 029718/0262 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2013
From: ARDENT RESEARCH CORPORATION
To: EMPIRE TECHNOLOGY DEVELOPMENT LLC
Reel/Frame 029718/0281 →