IP Library Granted Patent US 10,805,307
Granted Patent B1
US 10,805,307 · App. 16/902,334 · Granted Oct 13, 2020

Multiple data store authentication

Inventors: Jay Sutaria (Mountain View, CA); Brian Daniel Gustafson (Montara, CA); Robert Paul van Gent (Redwood City, CA); Ruth Lin (Santa Clara, CA); David Merriwether (Menlo Park, CA); Parvinder Sawhney (Fremont, CA)
Assignee: Seven Networks, LLC
H04L63/102H04L63/0876H04W12/06H04W12/08
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 10,805,307
App. No.
16/902,334
Granted
Oct 13, 2020
Kind
B1
Abstract

Systems and methods for authenticating access to multiple data stores substantially in real-time are disclosed. The system may include a server coupled to a network, a client device in communication with the server via the network and a plurality of data stores. The server may authenticate access to the data stores and forward information from those stores to the client device. An exemplary authentication method may include receipt of a request for access to data. Information concerning access to that data is stored and associated with an identifier assigned to a client device. If the identifier is found to correspond to the stored information during a future request for access to the store, access to that store is granted.

Claims (35)

1. A server for providing access to one or more data stores, comprising:

a memory and a processor, the server communicatively coupled to a network and the one or more data stores, wherein the server is configured to:

send a first identifier for a client device upon the client device communicating with the server for the client device to present the first identifier in a subsequent connection with the server;

receive registration information for a data store from the client device,

wherein a second identifier is generated based on device information received from the client device, and

wherein the second identifier is associated with the data store and the registration information;

receive, from the client device via the subsequent connection with the client device, a request for the client device to receive information from the data store via the server,

wherein the subsequent connection includes the first identifier;

configure a service to receive data from the data store on behalf of the client device,

wherein the service receives data from the data store based on the second identifier;

receive a first message indicative of new information at the data store;

transmit a second message to the client device in response to receipt of the first message;

wherein additional information associated with the first message is sent from the data store to the client device upon receipt of the second message by the client device.

2. The server of claim 1 , wherein the first identifier is generated by the server.

3. The server of claim 1 , wherein the second identifier is generated by the server.

4. The server of claim 1 , wherein a third identifier is generated for another data store.

5. The server of claim 4 , wherein the third identifier is generated by the server.

6. The server of claim 1 , wherein the first message is received when the first message matches a predefined characteristic set by the data store.

7. A non-transitory computer-readable storage medium, the non-transitory computer-readable storage medium storing instructions to be implemented on at least one server including at least one processor, the instructions when executed by the at least one processor cause the at least one server to perform a method for providing access to one or more data stores that are communicatively coupled to the at least one server over a network, the method comprising:

sending a first identifier for a client device upon the client device communicating with the server for the client device to present the first identifier in a subsequent connection with the server;

receiving registration information for a data store from the client device,

wherein a second identifier is generated based on device information received from the client device, and

wherein the second identifier is associated with the data store and the registration information;

receiving, from the client device via the subsequent connection with the client device, a request for the client device to receive information from the data store via the server,

wherein the subsequent connection includes the first identifier;

configuring a service to receive data from the data store on behalf of the client device,

wherein the service receives data from the data store based on the second identifier;

receiving a first message indicative of new information at the data store;

transmitting a second message to the client device in response to receipt of the first message;

wherein additional information associated with the first message is sent from the data store to the client device upon receipt of the second message by the client device.

8. The non-transitory computer-readable storage medium of claim 7 , wherein the first identifier is generated by the server.

9. The non-transitory computer-readable storage medium of claim 7 , wherein the second identifier is generated by the server.

10. The non-transitory computer-readable storage medium of claim 7 , wherein a third identifier is generated for another data store.

11. The non-transitory computer-readable storage medium of claim 10 , wherein the third identifier is generated by the server.

12. The non-transitory computer-readable storage medium of claim 7 , wherein the first message is received when the first message matches a predefined characteristic set by the data store.

Assignments (2)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 17, 2020
From: GUSTAFSON, BRIAN DANIEL; VAN GENT, ROBERT PAUL; SUTARIA, JAY; LIN, RUTH; MERRIWETHER, DAVID; SAWHNEY, PARVINDER
To: SEVEN NETWORKS, INC.
Reel/Frame 052963/0388 →
ENTITY CONVERSION Recorded Jun 17, 2020
From: SEVEN NETWORKS, INC.
To: SEVEN NETWORKS, LLC
Reel/Frame 052966/0530 →