CONNECTION ARCHITECTURE FOR A MOBILE NETWORK

• US 20170048182A1
• Filed: 10/28/2016
• Published: 02/16/2017
• Est. Priority Date: 01/08/2002
• Status: Active Grant

• Current Assignee: Seven Networks Inc
• 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.
• Granted Patent: US 10,110,534 B2
• Time in Patent Office: Days
• 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 includes a processor configured to direct the mobile device to send a request directing a management server to initiate a transaction.

Claims

1. (canceled)

2. 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;

receive a first trigger from the first device, wherein the first connection is maintained independently of the first trigger;

generate a second trigger for a second device based on the first trigger from the first device; and

receive a second connection from the second device.

3. The server of claim 2, wherein the server is further operable to:

send the second trigger to the second device; and

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

4. The server of claim 2, wherein the first trigger includes data selected from the group comprising:

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

5. The server of claim 2, wherein the second trigger notifies the second device of new data available on the first device.

6. The server of claim 2, wherein the server is further operable to:

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

receive a third connection from the third device.

7. The server of claim 6, wherein the third trigger notifies the third device of new data available on the first device.

8. The server of claim 2, wherein the first and second triggers are substantially the same.

9. The server of claim 6, wherein the second and third triggers are substantially the same.

10. The server of claim 2, wherein maintaining the first connection with the first device independently of the first trigger comprises automatically reestablishing the first connection with the first device if the first connection is disconnected for any reason.

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

terminate the first connection.

12. 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;

receiving a first trigger from the first device, wherein the first connection is maintained independently of the first trigger;

generating a second trigger for a second device based on the first trigger from the first device; and

receiving a second connection from the second device.

13. The method of claim 12, the method further comprising:

sending the second trigger to the second device; and

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

14. The method of claim 12, wherein the first trigger includes data selected from the group comprising:

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

15. The method of claim 12, wherein the second trigger notifies the second device of new data available on the first device.

16. The method of claim 12, the method further comprising:

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

receiving a third connection from the third device.

17. The method of claim 16, wherein the third trigger notifies the third device of new data available on the first device.

18. The method of claim 12, wherein the first and second triggers are substantially the same.

19. The method of claim 16, wherein the second and third triggers are substantially the same.

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

21. The method of claim 12, the method further comprising:

terminating the first connection.