Multiple data store authentication

• US 10,243,962 B1
• Filed: 02/20/2018
• Issued: 03/26/2019
• Est. Priority Date: 04/21/2005
• Status: Active Grant

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Inventors: Backholm, Ari, Sawhney, Parvinder
• Primary Examiner(s): Mehedi, Morshed
• Application Number:
  US15/899,947
• Time in Patent Office: 399 Days
• CPC Class Codes: G06F 21/44 Program or device authentication
• CPC Class Codes: G06Q 30/06 Buying, selling or leasing transactions
• CPC Class Codes: H04L 63/083 using passwords cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/102 Entity profiles
• CPC Class Codes: H04W 12/06 Authentication
• CPC Class Codes: H04W 12/069 using certificates or pre-shared keys
• CPC Class Codes: H04W 12/08 Access security

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

1. A server, comprising:

a memory and a processor, the server communicatively coupled to a network and a plurality of data stores, wherein the server is configured to;

send a first identifier to a client device upon the client device communicating with the server over a connection;

receive registration information from the client device;

send a second identifier to the client device in response to the received registration information;

configure a service to receive data from a first data store on behalf of the client device, wherein the service is based on the second identifier;

receive a communication from the client device to receive data from the plurality of data stores,

wherein the communication includes the first identifier;

receive a first message from the first data store, wherein the first message is indicative of new data at the first data store;

transmit a second message to the client device in response to receipt of the first message and authentication of the client device, wherein the second message is transmitted over a subsequent connection, and wherein the authentication of the client device is based on the first identifier,

wherein the subsequent connection is an IP connection between the client device and the server; and

receive a keep-alive message from the client device for maintenance of the subsequent connection,

wherein additional information associated with the first message is sent from the first 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 data store comprises an application server.

3. The server of claim 1, wherein the client device is one of a cellular telephone or personal digital assistant.

4. The server of claim 1, wherein the first identifier is a token, wherein the token comprises a unique string of data.

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

6. The server of claim 1, wherein the first identifier is specific to the client device, wherein the subsequent connection is established after the first identifier is sent to the client device.

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

8. The server of claim 1, wherein the first data store is communicatively coupled to the client device and can transmit to the client device using a connection that is independent of the server.

9. The server of claim 1, wherein the server is configured to direct the client device to delete content thereon in response to an indication that the client device is misappropriated.

10. The server of claim 1, wherein the additional information is sent over a subsequently established connection that is independent of the server.

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

12. The server of claim 1, wherein an IP connection is established between the client device and the first data store in response to transmission of the second message to the client device by the server for sending of the additional information.

13. The server of claim 1, wherein the second message is encrypted.

14. The server of claim 1, wherein an additional message indicative of new data at the first data store is transmitted over the subsequent connection.

15. The server of claim 1, wherein the server is further configured to receive a third message from a second data store, wherein the third message from the second data store is indicative of new data at the second data store, wherein a fourth message associated with the second data store is transmitted over the subsequent connection.

16. The server of claim 1, wherein the subsequent connection is established over a different network than the network over which the first message is received.

17. The server of claim 1, wherein the subsequent connection is established over a different network than a network over which another subsequent connection is established.

18. The server of claim 1, wherein another subsequent connection is established over a different wireless network than the wireless network over which the subsequent connection is established.

19. The server of claim 1, further configured to monitor active connections established with the client device, wherein transmitting the second message is based on the monitoring.

20. The server of claim 1, wherein the first identifier authenticates the client device to receive data from the first data store and a second data store over the subsequent connection.

21. The server of claim 1, wherein the request from the client device for data from the plurality of data stores is received over a connection that is different than the subsequent connection.

22. The server of claim 1, further configured to transmit the second message in substantially real time.

23. A method comprising:

sending a first identifier to a client device upon the client device communicating with a server over a connection, wherein the server is communicatively coupled to a network and a plurality of data stores;

receiving registration information from the client device;

sending a second identifier to the client device in response to the received registration information;

configuring a service to receive data from a first data store on behalf of the client device, wherein the service is based on the second identifier;

receiving a communication from the client device to receive data from the plurality of data stores,

wherein the communication includes the first identifier;

receiving a first message from the first data store, wherein the first message is indicative of new data at the first data store;

transmitting a second message to the client device in response to receipt of the first message and authentication of the client device, wherein the second message is transmitted over a subsequent connection, and wherein the authentication of the client device is based on the first identifier,

wherein the subsequent connection is an IP connection between the client device and the server; and

receiving a keep-alive message from the client device for maintenance of the subsequent connection,

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

24. The method of claim 23, wherein the first data store comprises an application server.

25. The method of claim 23, wherein the client device is one of a cellular telephone or personal digital assistant.

26. The method of claim 23, wherein the first identifier is a token, wherein the token comprises a unique string of data.

27. The method of claim 23, wherein a third identifier is generated for a second data store.

28. The method of claim 23, wherein the first identifier is specific to the client device, wherein the subsequent connection is established after the first identifier is sent to the client device.

29. The method of claim 23, wherein the first message is received when the first message matches a predefined characteristic set by the first data store.

30. The method of claim 23, wherein the first data store is communicatively coupled to the client device and can transmit to the client device using a connection that is independent of the server.

31. The method of claim 23, further comprising directing the client device to delete content thereon in response to an indication that the client device is misappropriated.

32. The method of claim 23, wherein the additional information is sent over a subsequently established connection that is independent of the server.

33. The method of claim 23, wherein the first identifier is generated by the server.

34. The method of claim 23, wherein an IP connection is established between the client device and the first data store in response to transmission of the second message to the client device by the server for sending of the additional information.

35. The method of claim 23, wherein the second message is encrypted.

36. The method of claim 23, wherein an additional message indicative of new data at the first data store is transmitted over the subsequent connection.

37. The method of claim 23, further comprising receiving a third message from a second data store, wherein the third message from the second data store is indicative of new data at the second data store, wherein a fourth message associated with the second data store is transmitted over the subsequent connection.

38. The method of claim 23, wherein the subsequent connection is established over a different network than the network over which the first message is received.

39. The method of claim 23, wherein the subsequent connection is established over a different network than a network over which another subsequent connection is established.

40. The method of claim 23, wherein another subsequent connection is established over a different wireless network than the wireless network over which the subsequent connection is established.

41. The method of claim 23, further comprising monitoring active connections established with the client device, wherein transmitting the second message is based on the monitoring.

42. The method of claim 23, wherein the first identifier authenticates the client device to receive data from the first data store and a second data store over the subsequent connection.

43. The method of claim 23, wherein the request from the client device for data from the plurality of data stores is received over a connection that is different than the subsequent connection.

44. The method of claim 23, transmitting the second message in substantially real timer.