Connection architecture for a mobile network

• US 10,110,534 B2
• Filed: 10/28/2016
• Issued: 10/23/2018
• Est. Priority Date: 01/08/2002
• Status: Expired due to Term

• Current Assignee: Seven Networks Inc
• Original Assignee: Seven Networks LLC (SoftBank Group Corp.)
• 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 A
• Application Number:
  US15/338,238
• Publication Number:
  US 20170048182A1
• Time in Patent Office: 725 Days
• Field of Search: 709206, 709238, 709217, 4554121, 4554122, 4554566, 4554141, 455418, 455420, 4554221, 455574, 455572, 455573, 455522, 455 411, 4553431, 4551271, 4555521, 4553435, 455 111, 455 134
• 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 network architectures or network communication protocols for wireless network security H04W12/00
• 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 includes a processor configured to direct the mobile device to send a request directing a management server to initiate a transaction.

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 associated with a first device;

receive a first message from the first device over the first connection;

generate a second message for a second device based on the first message from the first device;

send the second message to the second device;

receive a second connection associated with the second device, wherein the first connection includes a connection that is initiated by the first device, wherein the second connection includes a connection that is initiated by the second device;

receive a third message from the second device, wherein the third message is generated by the second device in response to receipt of the second message, wherein the third message contains a latest version of data stored at the second device and wherein the first message comprises a data query that is transmitted from the first device for the latest version of the data stored at the second device;

generate a fourth message, wherein the fourth message includes data from the third message; and

send the fourth message to the first device over the first connection.

2. The server of claim 1, wherein the first message is received in response to instructions from a user of the first device.

3. The server of claim 1, wherein the second connection is a TCP/IP connection.

4. The server of claim 1, wherein a version of the data is stored at the first device.

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

manage a transaction between the first device and second device using the second connection.

6. The server of claim 1, wherein the second message includes data from the first message.

7. The server of claim 1, wherein the server is operable to maintain the second connection regardless of whether the first connection is terminated.

8. The server of claim 1, wherein the server is operable to receive a third connection associated with the second device.

9. The server of claim 8, wherein the server is operable to manage transactions between the first device and the second device over the first and third connection.

10. The server of claim 1, wherein the first message is in response to a request from a user.

11. A method of operating a server, the method comprising:

receiving a first connection associated with a first device;

receiving a first message from the first device over the first connection;

generating a second message for a second device based on the first message from the first device;

sending the second message to the second device; and

receiving a second connection associated with the second device,

wherein the first connection includes a connection that is initiated by the first device,

wherein the second connection includes a connection that is initiated by the second device;

receiving a third message from the second device,

wherein the third message is generated by the second device in response to receipt of the second message, wherein the third message contains a latest version of data stored at the second device and wherein the first message comprises a data query that is transmitted from the first device for the latest version of the data stored at the second device;

generating a fourth message,

wherein the fourth message includes data from the third message; and

sending the fourth message to the first device over the first connection.

12. The method of claim 11, wherein the first message is received in response to instructions from a user of the first device.

13. The method of claim 11, wherein the second connection is a TCP/IP connection.

14. The method of claim 11, wherein a version of the data is stored at the first device.

15. The method of claim 11, further comprising:

managing a transaction between the first device and second device using the second connection.

16. The method of claim 11, wherein the second message includes data from the first message.

17. The method of claim 11, wherein the second connection is maintained regardless of whether the first connection is terminated.

18. The method of claim 11, further comprising receiving a third connection associated with the second device.

19. The method of claim 18, further comprising managing transactions between the first device and the second device over the first and third connection.

20. The method of claim 11, wherein the first message is in response to a request from a user.