Mobile device power management in data synchronization over a mobile network with or without a trigger notification
DC CAFC
First Claim
Patent Images
1. A system for synchronizing a mobile device with a client over a network, the system, comprising:
- a server in communication with the client over a first connection;
a mobile device in communication with the server over a second connection;
wherein, in operation, the server routes data between the mobile device and the client over the first and second connections;
wherein, in operation, the mobile device automatically sends synchronization requests on a periodic basis for delivery to the client for updated data, andwherein, the periodicity occurs at a frequency determined 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 Assignments
Litigations
3 Petitions
Accused Products
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.
1737 Citations
30 Claims
-
1. A system for synchronizing a mobile device with a client over a network, the system, comprising:
-
a server in communication with the client over a first connection; a mobile device in communication with the server over a second connection; wherein, in operation, the server routes data between the mobile device and the client over the first and second connections; wherein, in operation, the mobile device automatically sends synchronization requests on a periodic basis for delivery to the client for updated data, and wherein, the periodicity occurs at a frequency determined 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. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20)
-
-
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 first connection between the client and a system and a mobile connection between the mobile device and the 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 data when the new data 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; wherein, the mobile device automatically sends synchronization requests on a periodic basis for delivery to the client for updated data, and wherein, the periodicity occurs at a frequency determined according to remaining battery power on the mobile device; sending transactions between the mobile device and the client over a new mobile connection and the first connection. - View Dependent Claims (22, 23, 24, 25)
-
-
26. A mobile device located in a mobile network, comprising:
a processor configured to; exchange transactions with a client operating in a network through a connection provided through a server coupled to the client; automatically send synchronization requests from the mobile device to the network on a periodic basis; wherein, the periodicity of the synchronization requests occur at a frequency determined according to remaining battery power on the mobile device; and exchange synchronization communications with the client over the connection after sending each synchronization request. - View Dependent Claims (27, 28, 29, 30)
Specification
-
- Resources
Litigation Campaign Assessment
Thank you for your request. You will receive a custom alert email when the Litigation Campaign Assessment is available.
×
Litigation Data
-
Current AssigneeSeven Networks LLC (SoftBank Group Corp.)
-
Original AssigneeSeven Networks Inc
-
InventorsFiatal, Trevor A., Boynton, Lee R., Burke, Scott M., Gustafson, Brian D., Raj, Binu, Alvarado, William, Benitez, Juan, Duncan, Fred J.
-
Primary Examiner(s)Edouard, Patrick
-
Assistant Examiner(s)CASCA, FRED A
-
Application NumberUS13/101,775Publication NumberTime in Patent Office1,202 DaysField of Search709/248, 709/224, 709/249, 709/203, 455/70, 455/412.1, 455/522.1, 455/418, 455/414.1, 455/375, 370/350, 370/507, 707/610, 707/621US Class Current455/412.2CPC Class CodesH04B 7/04 using two or more spaced in...H04B 7/0417 Feedback systemsH04B 7/0617 for beam formingH04L 2209/80 Wireless network architectu...H04L 51/58 Message adaptation for wire...H04L 63/0272 Virtual private networksH04L 63/0281 ProxiesH04L 63/029 Firewall traversal, e.g. tu...H04L 63/0428 wherein the data content is...H04L 63/0464 using hop-by-hop encryption...H04L 63/0471 applying encryption by an i...H04L 63/08 for authentication of entit...H04L 63/0807 using tickets, e.g. Kerbero...H04L 67/04 specially adapted for termi...H04L 67/1095 Replication or mirroring of...H04L 67/14 Session management for real...H04L 69/329 in the application layer [O...H04L 9/3226 using a predetermined code,...H04W 12/03 Protecting confidentiality,...H04W 12/04 Key management, e.g. using ...View All
