TERMINAL AND APPLICATION SYNCHRONIZATION METHOD THEREFOR

• US 20140368332A1
• Filed: 06/13/2014
• Published: 12/18/2014
• Est. Priority Date: 06/14/2013
• Status: Active Grant

• Current Assignee: Samsung Electronics Co. Ltd.
• Original Assignee: Samsung Electronics Co. Ltd.
• Inventors: HONG, Youngki, PARK, Yongseok, LEE, Gunuk, KIM, Jinhyoung
• Granted Patent: US 10,075,409 B2
• Time in Patent Office: Days
• US Class Current: 340/501
• 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 in a terminal, the method comprising:

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

performing, when the 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, adjustment by estimating a period of a repetitive synchronization activity associated with the first alarm registration request and adjusting an execution time of the repetitive synchronization activity according to the estimated period.

2. The method of claim 1, wherein the performing of the adjustment comprises:

determining, 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, whether a synchronization activity identifier associated with the first alarm registration request is on a whitelist; and

adjusting, when the synchronization activity identifier associated with the first alarm registration request is on the whitelist, the execution time of the repetitive synchronization activity, which is associated with the first alarm registration request, according to period information related to the synchronization activity identifier.

3. The method of claim 2, wherein the performing of the adjustment further comprises:

determining, when the synchronization activity identifier associated with the first alarm registration request is not on the whitelist, whether a second alarm registration request and a third alarm registration request corresponding to the first alarm registration request are issued before the first alarm registration request is issued;

determining, when the second alarm registration request and the third alarm registration request corresponding to the first alarm registration request are issued before the first alarm registration request is issued, periodicity of the first alarm registration request on the basis of intervals between trigger times of the first alarm registration request through the third alarm registration request;

estimating, when the first alarm registration request is determined as having periodicity, period information on the basis of intervals between the trigger times;

adding the synchronization activity identifier related to the first alarm registration request and the period information to the whitelist;

adding, when the first alarm registration request is determined as not having periodicity, the synchronization activity identifier related to the first alarm registration request to an ignore list; and

adding, 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 activity identifier related to the first alarm registration request to a watch list so that the synchronization activity identifier is associated with the trigger time of the first alarm registration request.

4. The method of claim 1, wherein the performing of the adjustment further comprises preventing, when the synchronization activity identifier associated with the first alarm registration request is on the ignore list, adjustment of the execution time of the repetitive synchronization activity associated with the first alarm registration request.

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

a controller configured to receive a first alarm registration request, to determine 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, to perform, 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, adjustment by estimating the period of a repetitive synchronization activity associated with the first alarm registration request, and to adjust the execution time of the repetitive synchronization activity according to the period estimation result; and

a communication unit configured to send and receive data under control of the controller.

6. The terminal of claim 5, wherein the controller is further configured to determine, when the 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, whether a synchronization activity identifier associated with the first alarm registration request is on a whitelist, and to adjust, when the synchronization activity identifier associated with the first alarm registration request is on the whitelist, the execution time of the repetitive synchronization activity associated with the first alarm registration request according to period information related to the synchronization activity identifier.

7. The terminal of claim 6, wherein the controller is further configured to determine, when the synchronization activity identifier associated with the first alarm registration request is not on the whitelist, whether a second alarm registration request and a third alarm registration request corresponding to the first alarm registration request are issued before the first alarm registration request is issued, to determine, when the second alarm registration request and the third alarm registration request corresponding to the first alarm registration request are issued before the first alarm registration request is issued, periodicity of the first alarm registration request on the basis of intervals between trigger times of the first alarm registration request through the third alarm registration request, to estimate, when the first alarm registration request is determined as having periodicity, period information on the basis of intervals between the trigger times, to add the synchronization activity identifier related to the first alarm registration request and the period information to the whitelist, to add, when the first alarm registration request is determined as not having periodicity, the synchronization activity identifier related to the first alarm registration request to an ignore list, and 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 activity identifier related to the first alarm registration request to a watch list so that the synchronization activity identifier is associated with the trigger time of the first alarm registration request.

8. The terminal of claim 5, wherein the controller is further configured to prevent, when the synchronization activity identifier associated with the first alarm registration request is on the ignore list, adjustment of the execution time of the repetitive synchronization activity associated with the first alarm registration request.

9. A terminal comprising:

a storage unit configured to store an ignore list; and

a controller configured to determine whether an alarm trigger signal is generated, to determine, when an alarm trigger signal is generated, whether an alarm triggered by the alarm trigger signal is a target for application synchronization management, to determine, when the alarm is the target for application synchronization management, whether the alarm is a User Interface (UI) alarm or an abnormal action alarm, and to add, when the alarm is the UI alarm or the abnormal action alarm, information on the alarm to the ignore list.

10. The terminal of claim 9, wherein the storage unit is further configured to store at least one of a whitelist and a watch list, and

wherein the controller is further configured to determine that the alarm is a target for application synchronization management when information on a repetitive synchronization activity associated with the alarm is contained in at least one of the whitelist and the watch list.

11. The terminal of claim 9, wherein the information related to the alarm comprises information indicating a repetitive synchronization activity related to the alarm, and

wherein the information indicating the repetitive synchronization activity comprises at least one of an application identifier, period information, and information associated with the application identifier or period information.

12. The terminal of claim 9, wherein the controller is further configured to determine whether the alarm is the UI alarm according to generation of a foreground signal within a preset time and turning-on of the screen.

13. The terminal of claim 9, wherein the controller is further configured to determine whether the alarm is the abnormal action alarm according to cycle patterns of a repetitive synchronization activity associated with the alarm.

14. The terminal of claim 9, wherein the controller is further configured to determine, when the alarm is the abnormal action alarm, whether a next alarm is registered by the application having registered the alarm, and to perform, when the next alarm is not registered, a rollback function.

15. A method for application synchronization management, the method comprising:

determining whether an alarm trigger signal is generated;

determining, when the alarm trigger signal is generated, whether an alarm triggered by the alarm trigger signal is a target for application synchronization management;

determining, when the alarm is the target for application synchronization management, whether the alarm is a User Interface (UI) alarm or an abnormal action alarm; and

adding, when the alarm is the UI alarm or the abnormal action alarm, information on the alarm to an ignore list.

16. The method of claim 15, wherein the determining of whether the alarm is a target for application synchronization management comprises determining that the alarm is the target for application synchronization management when information on a repetitive synchronization activity associated with the alarm is contained in at least one of a whitelist and a watch list.

17. The method of claim 15, wherein the information related to the alarm comprises at least one of information indicating the repetitive synchronization activity related to the alarm, information indicating the repetitive synchronization activity comprises at least one of an application identifier and period information, and information associated with the application identifier or period information.

18. The method of claim 15, wherein the alarm is determined to be the UI alarm according to generation of a foreground signal within a preset time and turning-on of the screen.

19. The method of claim 15, wherein the alarm is determined to be the abnormal action alarm according to cycle patterns of a repetitive synchronization activity associated with the alarm.

20. The method of claim 15, further comprising determining, when the alarm is the abnormal action alarm, whether a next alarm is registered by the application having registered the alarm;

and

performing, when the next alarm is not registered, a rollback function.