MOBILE DEVICE POWER MANAGEMENT IN DATA SYNCHRONIZATION OVER A MOBILE NETWORK WITH OR WITHOUT A TRIGGER NOTIFICATION

• US 20110213898A1
• Filed: 05/05/2011
• Published: 09/01/2011
• Est. Priority Date: 01/08/2002
• Status: Active Grant

• Current Assignee: Seven Networks Inc
• Original Assignee: Seven Networks Inc
• Inventors: Raj, Binu, Duncan, Fred J., Benitez, Juan, Gustafson, Brian D., Fiatal, Trevor A., Alvarado, William, Boynton, Lee R., Burke, Scott M.
• GRANTED PATENT: US 8,811,952 B2
• Time in patent office: 0 Days
• US Class Current: 709/248
• 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/38 in combination with wireless systems mobile application service signalling using messaging, e.g. SMS, H04W4/12
• 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 supporting authentication of entities communicating through a packet data network 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 adapted for terminals or networks with limited resources or for terminal portability, e.g. wireless application protocol [WAP] services or facilities specially adapted for wireless communication networks H04W4/00
• CPC Class Codes: H04L 67/1095 for supporting replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes or user terminals or syncML synchronisation in information retrieval in file systems G06F16/10; synchronisation in structured data stores G06F16/27; mass storage redundancy by mirroring for error detection or correction of data G06F11/2056
• CPC Class Codes: H04L 67/14 for session management session control for real-time communications H04L65/1066; session initiation protocol H04L65/1006; negotiation of communication capabilities H04L69/24; computer conference arrangements H04L12/1813; connection management in wireless networks H04W76/00; session management for telephonic communication and services H04M7/00; intertask communications in multiprogramming arrangements G06F9/54
• CPC Class Codes: H04L 69/329 in the application layer, i.e. layer seven network arrangements or network communication protocols for networked applications H04L67/00; data processing systems and methods specially adapted for administrative, commercial, financial or managerial purposes G06Q
• 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/001 Protecting confidentiality, e.g. by encryption or ciphering
• 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 system for synchronizing a mobile device with a client over a network, the system, comprising:

a server in the network that communicates with a client over a first connection;

a mobile device that communicates with the server over a second connection;

wherein, in operation, the server to route data between the mobile device and the client over the first and second connections;

wherein, in operation, the mobile device to send synchronization requests to the client for updated data, wherein, a frequency of the synchronization requests is sent according to remaining battery power on the mobile device;

wherein, the first connection is maintained independently of the connectivity status of the second connection with the mobile device.

2. The system of claim 1, wherein, the mobile device synchronizes more frequently when a larger amount of battery power is remaining compared to when a smaller amount of battery power is remaining.

3. The system of claim 1, wherein, the mobile device uses different charge gradient levels for varying the frequency of synchronization.

4. The system of claim 1, wherein, the frequency is varied according to a day of the week.

5. The system of claim 4, wherein, the mobile device synchronizes less often on weekends than on weekdays.

6. The system of claim 1, wherein, the mobile device identifies its remaining battery power.

7. The system of claim 1, wherein, the first connection is maintained so that a communication path between the mobile device and the client is established whenever new connections are made between the mobile device and the server.

8. The system of claim 1, wherein, the first connection is maintained regardless of transaction inactivity between any of the client, the mobile device and the server.

9. The system of claim 1, wherein, a trigger is sent to the mobile device through the server when new data is available at the client for synchronization.

10. The system of claim 9, wherein, the client sends the trigger.

11. The system of claim 9, wherein, the trigger includes a notification of new activity without including payload data.

12. The system of claim 9, wherein, the trigger causes the mobile device to request synchronization with the client.

13. The system of claim 12, wherein, the mobile device establishes a connection with the server to request the synchronization with the client.

14. The system of claim 9, wherein, the server is coupled to a Short message service controller (SMSC);

further wherein, Short Message Service (SMS) is used to trigger the mobile device.

15. The system of claim 9, wherein, wireless application protocol (WAP) push operation is used to trigger the mobile device.

16. The system of claim 9, wherein, the client generates a trigger message which causes the server to send an SMS message through an SMSC to the mobile device to notify the mobile device of the new data.

17. The system of claim 9, wherein, the trigger is sent to the mobile device when the new data meets criteria defined by a filter which identifies types of events that a trigger should be sent for.

18. The system of claim 17, wherein, the filter is configured at the client.

19. The system of claim 17, wherein, the filter is configured at the client to specify content of higher priority.

20. The system of claim 9, wherein, the trigger includes a notification of new content and at least some of new content when identified as higher priority.

21. A method for transferring data between a mobile device and a client, comprising:

sending transactions between the mobile device and the client over a connection between the client and a management system and a mobile connection between the mobile device and the management system;

determining that new data for the mobile device is available at the client;

sending a trigger to notify the mobile device of the new content when the new content meets criteria defined by a filter which identifies types of events for which a trigger is to be sent;

forwarding a synchronization request sent from the mobile device to the client responsive to the trigger; and

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

22. The method of claim 21, wherein, a frequency of synchronization requests are sent according to remaining battery power on the mobile device.

23. The method of claim 21, further comprising, maintaining the connection between the client and the management system after the mobile connection is terminated.

24. The method of claim 21, wherein, the filter identifies the types of events as having higher priority then others.

25. The method of claim 21, wherein, the trigger is sent via SMS or WAP.

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

a processor configured to exchange transactions with a client through a connection provided through a server coupled to the client;

the processor to send synchronization requests from the mobile device to the local network;

wherein, a frequency of the synchronization requests is sent according to remaining battery power on the mobile device;

the processor to exchange synchronization communications with the client over the connection after sending the synchronization request.

27. The mobile device of claim 26, wherein, the synchronization request from the mobile device to the local network in response to a received synchronization trigger.

28. The mobile device of claim 26, wherein, the mobile device synchronizes more frequently when a larger amount of battery power is remaining compared to when a smaller amount of battery power is remaining.

29. The mobile device of claim 26, wherein, the frequency is varied according to a day of the week.

30. The mobile device of claim 26, wherein, the mobile device identifies its remaining battery power.