Connection architecture for a mobile network

• US 7,139,565 B2
• Filed: 01/08/2003
• Issued: 11/21/2006
• Est. Priority Date: 01/08/2002
• Status: Expired due to Term

• Current Assignee: Seven Networks LLC (SoftBank Group Corp.)
• Original Assignee: Seven Networks Inc
• Inventors: Burke, Scott M., Gustafson, Brian D., Raj, Binu, Alvarado, William, Benitez, Juan, Duncan, Fred J., Fiatal, Trevor A., Boynton, Lee R.
• Primary Examiner(s): Kincaid, Lester G.
• Assistant Examiner(s): Casca, Fred A.
• Application Number:
  US10/339,368
• Publication Number:
  US 20030157947A1
• Time in Patent Office: 1,413 Days
• Field of Search: 455/550.1, 455/426
• US Class Current: 455/423
• 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 real-time communication architecture establishes a continuous connection between an enterprise network and a communication management system. The connection is continuously held open allowing mobile devices real-time access to enterprise email systems. The real-time communication architecture can support an entire enterprise email system or individual email users. The foregoing and other objects, features and advantages of the invention will become more readily apparent from the following detailed description of a preferred embodiment of the invention which proceeds with reference to the accompanying drawings.

Claims

1. A method for transferring data comprising:

establishing a first connection from a client operating in a local network to a server located in a publicly accessible network that is external and operates independently and outside of the local network, the local network accessible from the publicly accessible network only through one or more local network firewalls and the first connection being initiated outbound from the client in the local network through the one or more firewalls to the server in the publicly accessible network;

establishing a second connection from a mobile device to the server in the publicly accessible network through a mobile network, the mobile network also operating outside and independently of the local network;

sending transactions between the mobile device and the client using both the first connection established between the client in the local network and the server in the publicly accessible network and the second connection established between the mobile device in the mobile network and the server in the publicly accessible network, said transactions being exchanged over a transaction path that extends from the mobile device over both the mobile network and the publicly accessible network to the server and from the server over both the publicly addressable network and through the one or more firewalls over the local network to the client operating in the local network;

continuously maintaining the first connection between the server and the client over both the publicly accessible network and through the one or more firewalls over the local network after the second connection is terminated for maintaining communication accessibility from the publicly accessible network through the one of more firewalls to the local network for the same or other mobile devices that need to subsequently communicate with the client; and

establishing a new third connection from the same or another mobile device over both the mobile network and the publicly accessible network to the server after termination of the second connection and sending new transactions from the mobile device to the server in the publicly accessible network over the newly established third connection and also using the previously established and continuously maintained first connection to forward the new transactions from the server in the publicly accessible network through the one or more firewalls to the client in the local network without having to establish a new outbound connection from the client in the local network through the one or more firewalls to the server in the publicly accessible network;

wherein the first connection is a continuously maintained communicative logical connection.

2. A method according to claim 1 wherein the first connection is a Transmission Control Protocol (TCP) connection that is continuously maintained by the server independently of the termination of the second connection and independently of any other communications between the server and any other mobile device, wherein the second connection is terminated by the mobile device in response to completing the transactions between the mobile device and the client, and wherein the new transactions are automatically transferred over the first connection independently of an amount of time between when the second connection is terminated by the mobile device and when the third connection is established by the mobile device.

3. A method according to claim 1 including automatically reestablishing the first connection in response to a disconnection of the first connection and maintaining the first connection for forwarding transactions received from the same or another mobile device over the wireless network to the client through the one or more firewalls over the first connection independently of whether the wireless connection is established or terminated by the same or another mobile device over the wireless network.

4. A method according to claim 1 including:

sending a file query, email query, or other data query from the mobile device to the local network over the second connection and the first connection;

generating a file list or response at the local network according to the query; and

sending the file list or response back to the mobile device over the first connection and the second connection.

5. A method according to claim 4 including:

selecting a file name, email, or other data item from the file list or response displayed on the mobile device;

attaching a file or data identifier to an email message identifying the selected file or data item;

sending the email message from the mobile device to the local network; and

attaching a file or other data item associated with the file or data identifier to the email message after the email message is sent from the mobile device and sending out the email message over an Internet Protocol (IP) network.

6. A method according to claim 1 including:

storing a representation of data in the local network on the mobile device;

sending a synchronization request from the mobile device to the local network over the second connection and the first connection requesting an updated representation of the data; and

sending the updated representation of the data back to the mobile device over the first connection and the second connection according to the synchronization request.

7. A method according to claim 1 including:

storing filters in the local network that identify specific types of data;

sending a message identifier when any of the identified types of data associated with the filters are received;

using a Short Message Service or other notification protocol to relay the message identifier to the mobile device.

8. A method according to claim 7 wherein at least one of the filters identifies high priority data.

9. A method according to claim 1 including:

sending a first query transaction from the mobile device to the local network for a file list;

sending a first partial file list to the mobile device;

storing the first partial file list in the mobile device;

sending a second query transaction from the mobile device to the local network requesting a different portion of the file list;

sending a second partial file list to the mobile device; and

replacing the first partial file list in the mobile device with the second partial file list.

10. A method according to claim 1 including:

identifying an amount of charge in a mobile device battery; and

automatically synchronizing the mobile device with the local network at different time intervals according to the amount of charge in the battery.

11. The method according to claim 1 including:

sending an authentication token from the local network to the server and establishing the logical first connection when the authentication token is authenticated by the server before the mobile device first establishes the second connection with the server; and

maintaining the authenticated logical first connection between the server and the local network even after the mobile device terminates the second connection.

12. The method of claim 1 wherein the mobile device is provided real time access to the local network by not persistently storing data associated with the transactions in the server.

13. The method of claim 1 wherein the first connection is in a pre-negotiated logical communicative state regardless or whether any connections are established between the server and any mobile device.

14. The method of claim 1 wherein the first connection is a continuously maintained TCP connection.

15. The method of claim 14 further including:

receiving a plurality of independent transactions from a different mobile device; and

forwarding each of the plurality of independent transactions from the server to the local network over the continuously maintained TCP connection.

16. The method of claim 15 further including the local network serving files to the server in response to file requests from the server.

37. The method according to claim 1 including providing real time access to the local network by maintaining the logical first connection between the local network and the server after the second connection is terminated.

17. A method for transferring data between a mobile device and a local network, comprising:

initiating a primary connection from the local network to a management system;

establishing a mobile connection from the mobile device to the management system;

sending transactions between the mobile device and the local network over the primary connection and the mobile connection;

continuously maintaining the primary connection between the local network and the management system after the mobile connection is terminated; and

establishing a new mobile connection between the mobile device and the management system and sending transactions between the mobile device and the local network over the new mobile connection and the previously established primary connection;

wherein the primary connection is a continuously maintained communicative logical connection;

storing a representation of data in the local network on the mobile device;

sending a synchronization request from the mobile device to the local network over the mobile connection and the primary connection requesting an updated representation of the data;

sending the updated representation of the data back to the mobile device over the primary first connection and the mobile connection according to the synchronization request;

terminating the mobile connection between the mobile device and the management system;

monitoring the local network for new data associated with a mobile device user;

sending a synchronization trigger over the primary connection from the local network to the management system when the new data is detected;

forwarding the synchronization trigger from the management system to the mobile device; and

automatically reestablishing the mobile connection between the mobile device and the management system when the synchronization trigger is received by the mobile device; and

sending a synchronization request from the mobile device over the reestablished mobile connection and the primary connection to the local network.

18. A method according to claim 17 including using a notification protocol for forwarding the synchronization trigger to the mobile device.

19. A method according to claim 17 including using a Wireless Application Protocol (WAP) Push or other equivalent notification protocol for forwarding the synchronization trigger to the mobile device.

20. A computer system, comprising:

a server located in a first publicly accessible Internet network that communicates with a local client over a persistent permanent stateful connection initiated by the local client from a second private enterprise network through a firewall that separates the second private enterprise network from the first publicly accessible Internet network;

the server further communicating over a first stateful connection initiated from a mobile device located outside the second private enterprise network over a mobile network and the first publicly accessible Internet network;

the mobile device prevented from directly accessing the second private enterprise network by the firewall and thereby using the server to route transactions between the mobile device and the local client over the first stateful connection and through the firewall using the established persistent permanent stateful connection stateful connection;

the server continuously maintaining the persistent permanent stateful connection independently of the connectivity status of the first stateful connection with the mobile device and regardless of file transaction inactivity between any of the local client, the mobile device and the server so that a connection oriented and stateful communication path between the mobile device and the local client is completed whenever new stateful connections are established between the mobile device and the server.

21. A computer system according to claim 20 including a user database containing user configuration information for a user in the second private enterprise network, the server receiving an authentication token or other identifier from the local client and establishing the persistent permanent stateful connection when the authentication token or other identifier is verified with the user configuration information.

22. A management computer system according to claim 21 wherein the server receives an authentication token or other identifier from the mobile device and establishes the first stateful connection with the mobile device when the authentication token or other identifier is verified with the user configuration information.

23. A management computer system according to claim 20 wherein the server receives a data list from the local client and sends out portions of the data list to the mobile device according to a type of platform used by the mobile device and according to query requests received from the mobile device.

24. A management computer system according to claim 20 wherein the server receives a trigger from the local client and then notifies the mobile device of the trigger.

25. A computer system according to claim 20 including receiving a high priority message from the local client and notifying the mobile device of the high priority message.

26. The computer system of claim 20 wherein the substantially permanent stateful connection is a continuously maintained Transmission Control Protocol (TCP) connection.

27. The computer system of claim 20 wherein the transactions are not persistently stored on the server.

28. The computer system of claim 20 wherein the persistent permanent stateful connection is a layer four connection that sits on top of the Internet Protocol (IP).

29. The computer system of claim 20 wherein state information for the persistent permanent stateful connection is included in packets communicated between the server and the local client.

30. The computer system of claim 20 wherein the first stateful connection is released according to a timeout and the persistent permanent stateful connection is maintained independently of any timeouts.

31. A mobile device located in a mobile network, comprising:

a processor configured to exchange file access transactions with a local client through a constant stateful connection that provides access to an internet that is separated from a publicly addressable network by one or more firewalls, constant stateful connection remaining stateful regardless of whether the processor is actively connected to the mobile network, regardless of how much time passes between any communications amongst any mobile device and any network devices located on the intranet, and regardless of any timeouts so that repetitively established temporary stateful connections between the processor and a server repetitively couple with the constant stateful connection to repetitively complete temporary stateful communication paths between the processor and the local client;

the processor to send a synchronization request from the mobile device over one of the temporary stateful connections and the constant stateful connection to the local network in response to a received synchronization trigger; and

the processor to exchange synchronization communications with the local network over the temporary stateful connection and the substantially permanent stateful connection after sending the synchronization request.

32. A mobile device according to claim 31 including memory for storing data received from the local client, the processor sending a synchronization transaction to the local client that enables the local client to send updates to the stored data.

33. A mobile device according to claim 32 wherein the processor automatically connects to the mobile network and sends the synchronization transaction upon receiving a notification.

34. A mobile device according to claim 32 including a battery, the processor sending out the synchronization transaction at different time intervals according to an amount of charge remaining in the battery.

35. A mobile device according to claim 31 wherein the processor receives a first file list from the local client identifying a portion of local files, the processor sending a transaction causing the local client to send a second file list identifying another portion of the local files.

36. A mobile device according to claim 35 wherein the processor automatically stores the first file list in memory and then replaces the first file list in memory with the second file list.

38. The mobile device of claim 31 wherein the constant stateful connection is a continuously maintained TCP connection that is established through the one or more firewalls.

39. The mobile device of claim 31 wherein the file access transactions are persistently stored only in the mobile device and at network the intranet where the local client is located.

40. A method for transferring data between a mobile device and a local network, comprising:

initiating a primary connection from the local network to a management system;

establishing a mobile connection from the mobile device to the management system;

sending transactions between the mobile device and the local network over the primary connection and the mobile connection;

maintaining the primary connection between the local network and the management system after the mobile connection is terminated;

sending a synchronization request from the mobile device over a new mobile connection and the previously established primary connection to the local network after receiving a synchronization trigger; and

sending transactions between the mobile device and the local network over the new mobile connection and the previously established primary connection.

41. A computer system, comprising:

a computer located in a first local network operating a local client that conducts transactions with a mobile device through a server located in a second publicly accessible network external to the first local network and through a wireless network also operating outside the first local network that connects the mobile device to the server, the local client initiating a logical first connection out through the first local network and through the second publicly accessible network to the server that configures both the computer in the first local network and the server in the publicly accessible network for exchanging transactions between the mobile device and the local client over the logical first connection; and

the logical first connection between the computer in the first local network and the server in the second publicly accessible network being continuously held open after the mobile device has terminated all connectivity with the server over the wireless network and providing re-connectivity of the mobile device with the computer in the first local network through the already established logical first connection thereby providing continuous pre-negotiated logical re-connectivity from the mobile device to the computer in the first local network through the logical first connection previously established between the server and the computer in the first local network independently of the mobile device terminating all communications with both the server and the computer in the first local network.

42. A computer system according to claim 41 wherein the local client receives a view transaction from the mobile device over the logical first connection, the local client accessing a user directory and sending a list of data items contained in the user directory back over the logical first connection to the mobile device responsive to the view transaction.

43. A computer system according to claim 41 wherein the local client receives a send transaction from the mobile device over the logical first connection, the local client accessing a local network and creating new message data according to the send transaction.

44. A computer system according to claim 41 wherein the local client receives an update transaction from the mobile device over the logical first connection, the local client accessing a user directory and modifying the identified data item according to the update transaction.

45. A computer system according to claim 41 wherein the local client sends a first list to the mobile device identifying a first portion of the user directory to the mobile device ad sends a second list to the mobile device identifying a second portion of the user directory when another view transaction is received from the mobile device.

46. A computer system according to claim 45 wherein the user directory contains, user document files, user emails, subdirectories, or other data items.

47. A computer system according to claim 42 wherein the local client receives a email transaction from the mobile device containing email message information ad identifying at least one of the data items from the list previously sent to the mobile device, local client attaching the identified data item from the user directory to the email message information and transmitting the email message information to a email address contained in the email message information.

48. The computer system according to claim 41 wherein the local client contains filters that identify events, the local client monitoring one or more user directories for the identified events and sending a trigger to the mobile device when the events are detected in the user directories, the trigger causing the mobile device to establish a mobile connection with the server and initiate a synchronization transaction with the local client.

49. The computer system according to claim 41 including an email server coupled to the computer, the email server containing user directories accessed by the local client according to the transactions received from the mobile device.

50. A computer system according to claim 49 wherein the local client operates on a desktop computer, a mobile computer, the email server, a separate server, or an embedded computing node.

51. The computer system according to claim 41 wherein the continuously held open logical first connection provides continuous synchronization of content between the local network and the mobile device.

52. The computer system according to claim 41 wherein the continuously held open logical first connection provides real time access to the local network by the mobile device.

53. The computer system of claim 41 wherein the continuously held open logical first connection is established over the publicly addressable network through one or more firewalls.

54. The management computer system of claim 41 wherein the continuously held open logical first connection is a Transmission Control Protocol (TCP) connection.

55. The management computer system of claim 41 wherein the transactions are not persistently stored on the server.