PUSH CONTENT TO A CURRENTLY UTILIZED DEVICE AMONG CLIENT DEVICES

• US 20170078274A1
• Filed: 11/28/2016
• Published: 03/16/2017
• Est. Priority Date: 08/14/2012
• Status: Active Grant

• Current Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Original Assignee: Empire Technology Development LLC (Allied Inventors Management, LLC)
• Inventors: KRUGLICK, Ezekiel
• Granted Patent: US 10,154,022 B2
• Time in Patent Office: Days
• US Class Current: 1/1
• CPC Class Codes: H04L 41/00 Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
• CPC Class Codes: H04L 63/068 using time-dependent keys, e.g. periodically changing keys cryptographic mechanisms or cryptographic arrangements for controlling usage of secret information H04L9/088
• CPC Class Codes: H04L 63/0815 providing single-sign-on or federations
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 67/55 Push-based network services

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

1. An authentication server, comprising:

at least one computer processor configured to;

responsive to receipt of an authorization 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 that depend from the cloud-based service, wherein the authorization request comprises a device identifier (ID) associated with the client device;

receive a renewed authorization request from another client device, wherein the another client device is associated with another device identifier (ID) and wherein the renewed authorization request comprises the another device ID; and

provide the device ID and the another device ID to a push server corresponding to at least one of the cloud-based service or the one or more of the dependent cloud-based services, wherein the another device ID facilitates a push service to the another client device associated with the another device ID, and the device ID facilitates the push service to the client device,

wherein the push service to the another client device transmits content, formatted in one format suitable for the cloud-based service and the one or more dependent cloud-based services for which the user is authorized using the another client device, and the push service to the client device transmits the content, formatted in another format.

2. The authentication server of claim 1, wherein the push service to the client device transmits an indication that corresponding updates have been read elsewhere.

3. The authentication server of claim 1, wherein the credentials are tokens including parameters indicating expiration time for the tokens.

4. The authentication server of claim 1, wherein the content includes message, notification, or update.

5. The authentication server of claim 1, further comprising:

a buffer configured to store the device ID and the another device ID.

6. The authentication server of claim 1, wherein the device ID includes IP address associated with the client device and the another device ID includes IP address associated with the another client device.

7. An authentication server comprising:

at least one computer processor configured to;

receive an authentication request from a client device for an authentication service, wherein the authentication request includes a client device identifier (ID) associated with the client device;

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

receive, from another device, 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 that depend from the primary application of the authentication service is utilized on the another client device, wherein the updated authentication request includes a different client device identifier (ID) associated with the another client device;

provide the different client device ID associated with the another client device to a push server corresponding to the authentication service; and

provide the client device ID associated with the client device from which the authentication request has been received to the push server,

wherein the push server pushes content, formatted in one format, to the another client device, and pushes the content, formatted in another format to the client device.

8. The authentication server of claim 7, wherein the authentication server is an OAuth server.

9. The authentication server of claim 7, wherein the one or more dependent applications utilize the time-limited authentication credentials provided for the user.

10. The authentication server of claim 9, wherein the at least one computer processor is further configured to provide the different client device ID associated with the another client device to a push server corresponding to the one or more dependent applications that are to receive content on a push basis.

11. The authentication server of claim 9, wherein the at least one computer processor is further configured to provide the different client device ID associated with the another client device to a push server corresponding to the one or more dependent applications on a predetermined frequency.

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

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

wherein the at least one computer processor 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 for the at least one client device from which the updated authentication request has most recently been received to the push server.

14. The authentication server of claim 9, wherein the user is authenticated for the authentication service and the one or more dependent applications on multiple client devices, and

wherein the at least one computer processor is further configured to:

store respective client device IDs associated with at least a subset of the multiple client devices from which the user has requested authorization on the primary application, and

provide the respective client device IDs associated with those of the subset of the multiple 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 pushes 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.

15. The authentication server of claim 9, wherein the push server requests a client ID via an API.

16. The authentication server of claim 7, 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.

17. The authentication server of claim 13, 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.

18. The authentication server of claim 16, wherein the cloud-based application is a widget that runs on the client device or the another client device.

19. The authentication server of claim 9, wherein the user is authenticated for the authentication service and the one or more dependent applications on multiple client devices, and

wherein the at least one computer processor is further configured to:

store respective client device IDs associated with at least a subset of the multiple client devices from which the user has requested authorization on the primary application, and

provide the respective client device IDs associated with those of the subset of client devices from which updated authentication requests have been received within a predefined quantity of devices among the multiple devices to the push server; and

wherein the push server pushes the content for the user on the primary application to those of the subset of client devices from which updated authentication requests have been received within a predefined quantity of devices among the multiple devices to the push server.

20. A method comprising:

responsive to receipt of an authorization request from a client device, providing, by an authentication server, credentials that enable multisite authorization for a user on a cloud-based service and one or more dependent cloud-based services that depend from the cloud-based service, wherein the authorization request comprises a device identifier (ID) associated with the client device;

receiving, by the authentication server, a renewed authorization request from another client device, wherein the another client device is associated with a another device identifier (ID), and wherein the renewed authorization request comprises the another device ID; and

providing, by the authentication server, the device ID and the another device ID to a push server corresponding to at least one of the cloud-based service or the one or more of the dependent cloud-based services, wherein the another device ID facilitates a push service to the another client device associated with the another device ID, and the device ID facilitates the push service to the client device,

wherein the push service to the another client device transmits content, formatted in one format suitable for the cloud-based service and the one or more dependent cloud-based services for which the user is authorized using the another client device, and the push service to the client device transmits the content, formatted in another format.