IP Library Granted Patent US 7,275,073
Granted Patent B2
US 7,275,073 · App. 10/430,943 · Granted Sep 25, 2007

System and method for notifying mobile devices based on device type and network capabilities

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,275,073
App. No.
10/430,943
Granted
Sep 25, 2007
Kind
B2
Abstract

A system, method and computer architecture for synchronizing data between one or more enterprise databases and one or more mobile devices is disclosed. The architecture comprises: one or more synchronization agents in communication with a plurality of enterprise databases, one or more monitoring agents in communication with the one or more enterprise databases where the monitoring agents are configured to monitor changes in the plurality of databases according to predetermined criteria, an events database accessible to the one or more monitoring agents for storing information relating to the changes, a synchronization database for storing information relating to synchronization events, a synchronization server in communication with a plurality of synchronization agents and the synchronization database where the synchronization server is adapted to receive communications from the mobile devices, and a notification server in communication with the events database and the synchronization database where the notification server is adapted to determine when to send notifications to the one or more mobile devices.

Claims (53)

1. A system comprising:

one or more synchronization agents in communication with one or more enterprise databases;

one or more monitoring agents in communication with the one or more enterprise databases, to monitor changes in the one or more enterprise databases according to a predetermined criteria;

an events database accessible to the one or more monitoring agents to store information relating to the changes;

a synchronization server in communication with the one or more synchronization agents to receive communications from one or more mobile devices;

a synchronization database in communication with the synchronization server to store information relating to synchronization events; and

a notification server in communication with the events database and the synchronization database to compare a last synchronization time for a mobile device with a last notification time for the mobile device, to increase a notification period for which the mobile device is notified of changes upon determining that the last synchronization time is older than the last notification time, and in response to the increased notification period, to delay sending notifications to the mobile devices.

2. The system of claim 1 further comprising: a device database in communication with the device database to store information relating to the one or more mobile devices.

3. The system of claim 2 wherein the notification server is further to scan the events database for a record relating to the changes.

4. The system of claim 2 wherein the notification server is further to determine if the one or more mobile devices is responding, if not, then to set a longer notification period.

5. The system of claim 2 wherein the notification server is further to determine if the network is overloaded, if yes, then to wait for a predetermined amount of time before notifying the one or more mobile devices, if not, then to send the notification to the one or more mobile devices.

6. The system of claim 2 wherein the notification server is further to determine a device type for the one or more mobile devices from the device database; and to determine a notification protocol for the device type from the device database.

7. The method of claim 6 wherein the determining of the notification protocol comprises determining a most suitable network channel protocol.

8. The method of claim 7 wherein the most suitable network channel protocol is selected from a group consisting of short message service, hypertext transfer protocol, and Mobitex.

9. A method comprising:

determining if the network is overloaded, if yes, then waiting for a predetermined amount of time before notifying a mobile device of an amendment event, if not, then sending the notification to the mobile device;

comparing a last synchronization time for a mobile device with a last notification time for the mobile device;

increasing a notification period for which the mobile device is notified of the amendment event upon determining that the last synchronization time is older than the last notification time; and

in response to the increased notification period, delaying sending the notification to the mobile device.

10. The method of claim 9 further comprising:

determining a device type for the mobile device; and

determining a notification protocol for the device type.

11. The method of claim 10 further comprising determining a most suitable network channel protocol.

12. The method of claim 11 wherein the most suitable network channel protocol is selected from a group consisting of short message service, hypertext transfer protocol, and Mobitex.

13. A method comprising:

monitoring a database for changes to an enterprise database according to a predetermined criteria;

determining whether to notify a mobile device of a monitored modification, if not waiting before notifying;

notifying the mobile device of a monitored modification;

determining whether a response to the notifying was received, if not, then repeating the above monitoring, determining, and notifying;

sending the monitored modification such that the mobile device and the enterprise database are synchronized;

comparing a last synchronization time for a mobile device with a last notification time for the mobile device;

increasing a notification period for which the mobile device is notified of the monitored modification upon determining that the last synchronization time is older than the last notification time; and

in response to the increased notification period, delaying sending a notification to the mobile device.

14. The method of claim 13 wherein the determining whether to notify the mobile device further comprises:

determining if the network is overloaded, if yes, then waiting for a predetermined amount of time before notifying the mobile device, if no, then sending the notification to the mobile device.

15. The method of claim 14 further comprising:

determining a device type for the mobile device;

determining a notification protocol for the device type; and

sending the notification according to the notification protocol.

16. The method of claim 13 further comprising:

setting up the mobile device; and

initially synchronizing with the mobile device.

17. A method comprising:

scanning a database for a record relating to an amendment event according to a predetermined criteria;

determining if the network is overloaded, if yes, then waiting for a predetermined amount of time before notifying the mobile device, if not, then sending the notification to the mobile device;

comparing a last synchronization time with a last notification time;

increasing a notification duration upon determining that the last synchronization time is older than the last notification time; and

in response to the increased notification duration, delaying sending the notification to the mobile device.

18. The method of claim 17 further comprising:

determining a device type for the mobile device; and

determining a notification method for the device type.

19. The method of claim 18 further comprising determining a most suitable network channel protocol.

20. The method of claim 19 wherein the most suitable network channel protocol is selected from a group consisting of short message service, hypertext transfer protocol, and Mobitex.

Assignments (11)
NUNC PRO TUNC ASSIGNMENT Recorded Jun 19, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064271/0199 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 16, 2023
From: BLACKBERRY LIMITED
To: MALIKIE INNOVATIONS LIMITED
Reel/Frame 064104/0103 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 30, 2018
From: GOOD TECHNOLOGY HOLDINGS LIMITED
To: BLACKBERRY LIMITED
Reel/Frame 045196/0255 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 28, 2017
From: GOOD TECHNOLOGY SOFTWARE, INC.
To: GOOD TECHNOLOGY HOLDINGS LIMITED
Reel/Frame 044038/0262 →
CHANGE OF NAME Recorded Dec 4, 2012
From: GOOD TECHNOLOGY ACQUISITION, INC.
To: GOOD TECHNOLOGY SOFTWARE, INC.
Reel/Frame 029405/0351 →
CHANGE OF NAME Recorded Dec 4, 2012
From: GOOD TECHNOLOGY, INC.
To: GOOD TECHNOLOGY ACQUISITION, INC.
Reel/Frame 029405/0271 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 2, 2010
From: TX TECHNOLOGY ACQUISITION CORPORATION
To: GOOD TECHNOLOGY, INC.
Reel/Frame 023882/0633 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 12, 2007
From: TX TECHNOLOGY CORPORATION
To: GOOD TECHNOLOGY, INC.
Reel/Frame 019820/0250 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 17, 2005
From: JP MOBILE OPERATING, L.P.
To: TX TECHNOLOGY ACQUISITION CORP.
Reel/Frame 016645/0669 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2003
From: GANJI, KIRAN; BOINAPALLI, RAGHUVEER
To: JP MOBILE OPERATING, L.P.
Reel/Frame 014392/0493 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2003
From: GANJI, KIRAN; BOINAPALLI, RAGHUVEER
To: JP MOBILE OPERATING, L.P.
Reel/Frame 014405/0488 →