Terminal and application synchronization method therefor

• US 10,075,409 B2
• Filed: 06/13/2014
• Issued: 09/11/2018
• Est. Priority Date: 06/14/2013
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: Hong, Youngki, Lee, Gunuk, Kim, Jinhyoung, Park, Yongseok
• Primary Examiner(s): Vostal, O. C.
• Application Number:
  US14/304,288
• Publication Number:
  US 20140368332A1
• Time in Patent Office: 1,551 Days
• Field of Search: 709248
• CPC Class Codes: H04L 51/58 Message adaptation for wireless communication

Abstract

A method and apparatus for application synchronization are provided. The method for application synchronization in a terminal includes receiving a first alarm registration request, determining whether a data transmission and reception action of an application corresponding to the first alarm registration request is detected within a preset time after a trigger time of the first alarm registration request, and estimating, when a data transmission and reception action of the application corresponding to the first alarm registration request is detected within the preset time after the trigger time of the first alarm registration request, the period of a repetitive synchronization activity associated with the first alarm registration request, and adjusting the execution time of the repetitive synchronization activity according to the period estimation result.

Claims

1. A method for application synchronization by a terminal, the method comprising:

receiving a first alarm registration request for an application;

determining whether a first alarm corresponding to the first alarm registration request is triggered;

determining whether data associated with the application corresponding to the first alarm registration request is transmitted or received within a predetermined time interval since the first alarm is triggered, if the first alarm corresponding to the first alarm registration request is triggered; and

estimating a period of the application corresponding to the first alarm registration request, if the data is transmitted or received within the predetermined time interval since the first alarm is triggered,

wherein an execution time of a synchronization operation is determined based on whether a synchronization operation identifier associated with the first alarm registration request is on a first list, and

wherein the synchronization operation identifier is added to a second list, if the data is not transmitted or received within the predetermined time interval since the first alarm is triggered.

2. The method of claim 1, further comprising:

determining whether the synchronization operation identifier associated with the first alarm registration request is on the first list; and

adjusting, if the synchronization operation identifier associated with the first alarm registration request is on the first list, an execution time of a repetitive synchronization operation, which is associated with the first alarm registration request, according to period information corresponding to the synchronization operation identifier.

3. The method of claim 2, further comprising:

determining, if the synchronization operation identifier associated with the first alarm registration request is not on the first list, whether a second alarm registration request and a third alarm registration request corresponding to the first alarm registration request are received before the first alarm registration request is received;

determining, if the second alarm registration request and the third alarm registration request corresponding to the first alarm registration request are received before the first alarm registration request is received, a periodicity of the first alarm registration request based on gaps between trigger times of the first alarm registration request, the second alarm registration request and the third alarm registration request;

generating, if the first alarm registration request is determined as having the periodicity, period information based on the gaps between the trigger times; and

adding the synchronization operation identifier related to the first alarm registration request and the period information to the first list.

4. The method of claim 3, further comprising:

adding the synchronization operation identifier related to the first alarm registration request to a second list, when the first alarm registration request is determined as not having the periodicity.

5. The method of claim 4, further comprising:

adding, if at least two alarm registration requests corresponding to the first alarm registration request are not received before the first alarm registration request is received, the synchronization operation identifier related to the first alarm registration request to a third list so that the synchronization operation identifier is associated with the trigger time of the first alarm registration request.

6. The method of claim 5, further comprising:

deleting the synchronization operation identifier related to the first alarm registration request from the first list, the second list and the third list, if the application corresponding to the first alarm registration request is updated.

7. A terminal supporting application synchronization, the terminal comprising:

at least one processor configured to;

receive a first alarm registration request for an application,

determine whether a first alarm corresponding to the first alarm registration request is triggered,

determine whether data associated with the application corresponding to the first alarm registration request is transmitted or received within a predetermined time interval since the first alarm is triggered, if the first alarm corresponding to the first alarm registration request is triggered, and

estimate a period of the application corresponding to the first alarm registration request, if the data is transmitted or received within the predetermined time interval since the first alarm is triggered; and

a communication unit configured to send and receive data under control of the at least one processor,

wherein an execution time of a synchronization operation is determined based on whether a synchronization operation identifier associated with the first alarm registration request is on a first list, and

wherein the synchronization operation identifier is added to a second list, if the data is not transmitted or received within the predetermined time interval since the first alarm is triggered.

8. The terminal of claim 7, wherein the at least one processor is further configured to:

determine whether the synchronization operation identifier associated with the first alarm registration request is on a first list, and

adjust, if the synchronization operation identifier associated with the first alarm registration request is on the first list, the execution time of a repetitive synchronization operation associated with the first alarm registration request according to period information corresponding to the synchronization operation identifier.

9. The terminal of claim 8, wherein the at least one processor is further configured to:

determine, if the synchronization operation identifier associated with the first alarm registration request is not on the first list, whether a second alarm registration request and a third alarm registration request corresponding to the first alarm registration request are received before the first alarm registration request is received,

determine, if the second alarm registration request and the third alarm registration request corresponding to the first alarm registration request are received before the first alarm registration request is received, a periodicity of the first alarm registration request based on gaps between trigger times of the first alarm registration request the second alarm registration request and the third alarm registration request,

generate, if the first alarm registration request is determined as having the periodicity, period information based on the gaps between the trigger times, and

add the synchronization operation identifier related to the first alarm registration request and the period information to the first list.

10. The terminal of claim 9, wherein the at least one processor is further configured to add the synchronization operation identifier related to the first alarm registration request to a second list, when the first alarm registration request is determined as not having the periodicity.

11. The terminal of claim 10, wherein the at least one processor is further configured to add, when at least two alarm registration requests corresponding to the first alarm registration request are not issued before the first alarm registration request is issued, the synchronization operation identifier related to the first alarm registration request to a third list so that the synchronization operation identifier is associated with the trigger time of the first alarm registration request.

12. The terminal of claim 11, wherein the at least one processor is further configured to delete the synchronization operation identifier related to the first alarm registration request from the first list, the second list and the third list, if the application corresponding to the first alarm registration request is updated.