Connection architecture for a mobile network

• US 9,608,968 B2
• Filed: 02/17/2015
• Issued: 03/28/2017
• Est. Priority Date: 01/08/2002
• Status: Expired due to Term

• Current Assignee: Seven Networks LLC (FIG LLC (d/b/a Fortress Investment Group LLC))
• Original Assignee: Seven Networks LLC (FIG LLC (d/b/a Fortress Investment Group LLC))
• Inventors: Fiatal, Trevor A., Boynton, Lee R., Burke, Scott M, Gustafson, Brian D., Raj, Binu, Alvarado, William, Benitez, Juan, Duncan, Fred J.
• Primary Examiner(s): Casca, Fred
• Application Number:
  US14/623,514
• Publication Number:
  US 20150163180A1
• Time in Patent Office: 770 Days
• Field of Search: 455/412.1, 455/412.2, 455/456.6, 455/414.1, 455/418, 455/420, 455/422.1, 455/419, 709/206, 709/238, 709/217
• US Class Current: 1/1
• CPC Class Codes: H04B 7/04 using two or more spaced independent antennas
• CPC Class Codes: H04B 7/0417 Feedback systems
• CPC Class Codes: H04B 7/0617 for beam forming
• CPC Class Codes: H04L 2209/80 Wireless
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/0428 wherein the data content is protected, e.g. by encrypting or encapsulating the payload
• CPC Class Codes: H04L 63/0464 using hop-by-hop encryption, i.e. wherein an intermediate entity decrypts the information and re-encrypts it before forwarding it
• CPC Class Codes: H04L 63/0471 applying encryption by an intermediary, e.g. receiving clear information at the intermediary and encrypting the received information at the intermediary before forwarding
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0807 using tickets, e.g. Kerberos cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213
• CPC Class Codes: H04L 67/04 specially adapted for terminals or networks with limited capabilities; specially adapted for terminal portability
• CPC Class Codes: H04L 67/1095 Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066
• CPC Class Codes: H04L 69/329 in the application layer [OSI layer 7]
• CPC Class Codes: H04L 9/3226 using a predetermined code, e.g. password, passphrase or PIN network architectures or network communication protocols for supporting authentication of entities using passwords in a packet data network H04L63/083
• CPC Class Codes: H04W 12/03 Protecting confidentiality, e.g. by encryption
• CPC Class Codes: H04W 12/04 Key management, e.g. using generic bootstrapping architecture [GBA]
• CPC Class Codes: H04W 4/12 : Messaging; Mailboxes; Announcements
• CPC Class Codes: H04W 52/0261 : managing power supply demand, e.g. depending on battery level
• CPC Class Codes: H04W 76/10 : Connection setup
• CPC Class Codes: H04W 88/06 : adapted for operation in multiple networks or having at least two operational modes, e.g. multi-mode terminals
• CPC Class Codes: Y02D 10/00 : Energy efficient computing, e.g. low power processors, power management or thermal management
• CPC Class Codes: Y02D 30/70 : in wireless communication networks

Abstract

A mobile device for accessing content stored on a remote server over a mobile network is provided. The mobile device includes a processor configured to direct the mobile device to receive at least a portion of a list initiated by the remote server, the list identifying folders or files stored on the remote server, process a selection to identify one of the folders or files on the list having the content on the remote server, and send a request directing a management server to initiate a transaction including an identifier indicating the one of the folders or files having the content on the remote server that is to be sent as the attachment to the destination.

Claims

1. A server that manages transactions between first and second devices, the server comprising:

a communication interface;

a processor communicatively coupled to the communication interface; and

a memory communicatively coupled to the processor, the memory containing instructions executable by the processor whereby the server is operable to;

receive a first connection from a first device;

authenticate the first device over the first connection;

receive a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction;

generate a trigger for a second device based on the first transaction from the first device, wherein the trigger is pushed to the second device;

after the generation of the trigger for the second device, receive a second connection from the second device while the first connection is maintained;

authenticate the second device over the second connection,

wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user; and

send a second transaction to the second device using the second connection, wherein the second transaction contains the new data,

wherein the trigger is pushed over a connection different from the second connection,

wherein a third transaction is received by the server in response to user input at the second device.

2. The server of claim 1, wherein the first device is in a private network that contains a firewall.

3. The server of claim 2, wherein the server is in a publicly accessible network.

4. The server of claim 1, wherein the second device is in a wireless network.

5. The server of claim 1, wherein the server is further operable to:

receive configuration information from the first device, wherein the configuration information comprises login data associated with a user of the first device.

6. The server of claim 1, wherein the first transaction includes data selected from the group comprising:

electronic messages, calendar data, contact information data, task data, note data, documents, and files.

7. The server of claim 6, wherein the electronic messages comprise electronic mail (email) data.

8. The server of claim 1, wherein the trigger contains information that causes the second connection to be received by the server.

9. The server of claim 1, wherein the second connection is received in response to user input received at the second device.

10. The server of claim 1, wherein the server is further configure to:

send the trigger to the second device via a Short Message Service Center.

11. The server of claim 1, wherein the server is further operable to:

generate a third trigger for a third device based on the first transaction; and

receive a third connection from the third device.

12. The server of claim 11 wherein the server is further operable to:

send a third transaction to the third device using the third connection.

13. The server of claim 12, wherein the third transaction contains data from the first transaction.

14. The server of claim 1, wherein the second transaction contains data from the first transaction.

15. The server of claim 1, wherein maintaining the first connection with the first device independently of the first transaction comprises automatically reestablishing the first connection with the first device if the first connection is disconnected for any reason.

16. The server of claim 1, wherein the server is further operable to:

terminate the first connection.

17. The server of claim 1, wherein the server is operable to:

receive a message from the first device, wherein receipt of the message terminates the first connection.

18. The server of claim 1, wherein the server is further operable to:

terminate the second connection.

19. The server of claim 1, wherein the server is further operable to:

receive a message from the second device terminating the second connection.

20. A method of operating a server to manage transactions between first and second devices, the method comprising:

receiving a first connection from a first device;

authenticating the first device over the first connection;

receiving a first transaction from the first device in response to user input at the first device, wherein the first connection is maintained independently of the first transaction;

generating a trigger for a second device based on the first transaction from the first device, wherein the trigger notifies the second device of new data from the first transaction to be received by the second device from the server for display to a user, wherein the trigger is pushed to the second device;

after the generation of the trigger for the second device, receiving a second connection from the second device while the first connection is maintained;

authenticating the second device over the second connection; and

sending a second transaction to the second device using the second connection, wherein the second transaction contains the new data,

wherein the trigger is pushed over a connection different from the second connection,

wherein a third transaction is received by the server in response to user input at the second device.

21. The method of claim 20, wherein the first device is in a private network that contains a firewall.

22. The method of claim 21, wherein the server is in a publicly accessible network.

23. The method of claim 20, wherein the second device is in a wireless network.

24. The method of claim 20, the method further comprising:

receiving configuration information from the first device, wherein the configuration information comprises login data associated with a user of the first device.

25. The method of claim 20, wherein the first transaction includes data selected from the group comprising:

electronic messages, calendar data, contact information data, task data, note data, documents, and files.

26. The method of claim 25, wherein the electronic messages comprise electronic mail (email) data.

27. The method of claim 20, wherein the trigger notifies the second device of new data to be received by the second device from the server.

28. The method of claim 20, wherein the trigger contains information that causes the second connection to be received by the server.

29. The method of claim 20, wherein the second connection is received in response to user input received at the second device.

30. The method of claim 20, the method further comprising:

sending the trigger to the second device via a Short Message Service Center.

31. The method of claim 20, the method further comprising:

generating a third trigger for a third device based on the first transaction;

receiving a third connection from the third device.

32. The method of claim 31, the method further comprising:

Sending a fourth transaction to the third device using the third transaction.

33. The method of claim 20, wherein the second transaction contains data from the first transaction.

34. The method of claim 20, wherein maintaining the first connection with the first device independently of the first transaction comprises automatically reestablishing the first connection with the first device if the first connection is disconnected for any reason.

35. The method of claim 20, the method further comprising:

terminating the first connection.

36. The method of claim 20, the method further comprising:

Receiving a message from the first device, wherein the receipt of the message terminates the first transaction.

37. The method of claim 20, the method further comprising:

terminating the second connection.

38. The method of claim 20, the method further comprising:

receiving a message from the second device terminating the second connection.