SYNCHRONIZATION METHOD AND ASSOCIATED APPARATUS

• US 20130097116A1
• Filed: 03/07/2012
• Published: 04/18/2013
• Est. Priority Date: 10/17/2011
• Status: Abandoned Application

• Current Assignee: Malikie Innovations Limited (Key Patent Innovations Limited)
• Original Assignee: Blackberry Limited
• Inventors: Ewanchuk, Andrew John, May, Darrell Reginald, Cherry, Carl Lloyd
• Application Number:
  US13/414,477
• Publication Number:
  US 20130097116A1
• Time in Patent Office: Days
• US Class Current: 707/610
• CPC Class Codes: G06F 16/273 Asynchronous replication or reconciliation

Abstract

An apparatus, and an associated method, facilitates synchronization of a database, such as a message database of a portable device. Synchronization is initiated at the device by the generating and transmitting of a plurality of synchronization requests, with each synchronization request requesting synchronization data of an increased synchronization depth. Synchronization operations are carried out using synchronization data returned responsive to the synchronization requests.

Claims

1. An apparatus for facilitating synchronization of a device database, said apparatus comprising:

a request generator configured to generate a synchronization request, the synchronization request including a first stage-length value;

a detector configured to detect synchronization data provided responsive to the synchronization request, the synchronization data being provided in a first stage of a first stage-length responsive to the first stage-length value and at least a second stage of a second stage-length.

2. The apparatus of claim 1 wherein said request generator is configured to generate a first synchronization request and at least a second synchronization request, wherein the first stage of the synchronization data detected by said detector is provided responsive to the first synchronization request, and wherein the second stage of the synchronization data detected by said detector is provided responsive to the second synchronization request.

3. The apparatus of claim 2 wherein the second synchronization request is generated automatically subsequent to generation of the first synchronization request.

4. The apparatus of claim 1 wherein the second stage-length is greater than the first stage-length.

5. The apparatus of claim 1 wherein the second stage of the synchronization data encompasses the first stage of the synchronization data.

6. The apparatus of claim 1 further comprising a reconciler configured to remove redundant synchronization data contained in the first stage of the synchronization data and in the second stage of the synchronization data.

7. The apparatus of claim 1 wherein the synchronization data provided in the first stage comprises both identifying parts and informational parts.

8. The apparatus of claim 1 wherein the synchronization data provided in the second stage comprises identifying parts.

9. The apparatus of claim 8 further comprising a reconciler configured to compare the identifying parts of the synchronization data provided in the first stage with identifying parts of the synchronization data provided in the second stage and to remove redundant synchronization data indicated responsive to the comparisons made by said reconciler.

10. The apparatus of claim 9 wherein said request generator is further configured to generate an information request, the information request for informational parts of non-redundant synchronization data of the second stage.

11. The apparatus of claim 10 further comprising a synchronizer configured to synchronize the device database with the synchronization data of the first stage and the non-redundant synchronization data of the second stage.

12. A device having a database, said device comprising:

a processor configured to;

generate a synchronization request that includes a first stage-length value;

detect synchronization data provided responsive to the synchronization request, the synchronization data being provided in a first stage of a first stage-length responsive to the first stage-length value and at least a second stage of a second stage-length.

13. The device of claim 12 wherein the synchronization request comprises a first synchronization request and at least a second synchronization request, wherein the detected synchronization data is provided in a first stage of a first stage-length and at least a second stage of a second stage-length, and wherein said processor is further configured to reconcile the detected synchronization data to remove redundancies of the synchronization data of the first stage and of the second stage.

14. The device of claim 12 wherein said processor is further configured to synchronize database data using the synchronization data.

15. A method for facilitating synchronization of a device database, said method comprising:

generating a synchronization request that includes a first stage-length value; and

detecting synchronization data provided responsive to the synchronization request, the synchronization data being provided in a first stage of a first stage-length responsive to the first stage-length value and at least a second stage of a second stage-length.

16. The method of claim 15 wherein said generating comprises generating a first synchronization request and at least a second synchronization request, wherein the first stage of the synchronization data detected during said detecting is provided responsive to the first synchronization request, and wherein the second stage of the synchronization data detected during said detecting is provided responsive to the second synchronization request.

17. The method of claim 16 further comprising receiving selection to generate the synchronization request, wherein said generating the first synchronization request is responsive to receiving the selection, and wherein said generating the second synchronization request is performed automatically subsequent to generation of the first synchronization request.

18. The method of claim 17 further comprising reconciling the synchronization data of the first stage and the synchronization data of the second stage to remove redundancies therefrom.

19. The method of claim 18 wherein the synchronization data provided in the first stage comprises both identifying parts and informational parts and wherein the synchronization data provided in the second stage comprises identifying parts.

20. The method of claim 19 further comprising generating an informational request for informational parts of non-redundant synchronization data of the second stage.

21. The method of claim 15 wherein the synchronization request is generated responsive to a trigger.

22. The method of claim 15 wherein the synchronization request includes routing information that permits routing of the synchronization request to a location.

23. The method of claim 15 wherein the synchronization request includes an identification of a part of a database that is to be synchronized.

24. The method of claim 16 further comprising reconciling the second stage of the synchronization data with the first stage of the synchronization data.

25. The method of claim 24 wherein the reconciling includes removing redundant data records of the second stage of the synchronization data.

26. A non-transitory computer-accessible medium having a sequence of instructions which, when executed by a processing entity, effectuate facilitation of synchronization of a device database, the non-transitory computer-accessible medium comprising:

a code portion for generating a synchronization request that includes a first stage-length value; and

a code portion for detecting synchronization data provided responsive to the synchronization request, the synchronization data being provided in a first stage of a first stage-length responsive to the first stage-length value and at least a second stage of a second stage-length.

27. A method for synchronizing data records of a device database, said method comprising:

iteratively generating a plurality of synchronization requests, each synchronization request of a synchronization depth, wherein each iteration is of a greater depth; and

synchronizing data records of the device database with synchronization data returned responsive to a synchronization request generated during said iteratively generating.

28. The method of claim 27 wherein said iteratively generating comprises generating one synchronization request of a one-day depth and generating a subsequent synchronization request of a three-day depth.

29. The method of claim 27 further comprising removing data redundancies from synchronization data returned responsive to a subsequent synchronization request, which contains synchronization data that is redundant to synchronization data returned responsive to an earlier synchronization request.