EVENT TRIGGERING METHOD DURING SLEEP MODE AND RELATED MOBILE DEVICES

• US 20130036428A1
• Filed: 06/15/2012
• Published: 02/07/2013
• Est. Priority Date: 08/02/2011
• Status: Abandoned Application

• Current Assignee: HTC Corporation
• Original Assignee: HTC Corporation
• Inventors: Lei, Yu-Hsiang, Huang, Yen-Ying
• Application Number:
  US13/524,163
• Publication Number:
  US 20130036428A1
• Time in Patent Office: Days
• US Class Current: 719/318
• CPC Class Codes: G06F 1/3206 Monitoring of events, devices or parameters that trigger a change in power modality
• CPC Class Codes: G06F 1/329 by task scheduling
• CPC Class Codes: G06F 9/4825 Interrupt from clock, e.g. time of day
• CPC Class Codes: Y02D 10/00 Energy efficient computing, e.g. low power processors, power management or thermal management

Abstract

An event triggering method for triggering events during a sleep mode for use in a mobile device is provided, wherein events includes at least first and second type events. First, an event manager operated in the sleep mode is provided, wherein event manager includes a counter. Thereafter, second type event registers to event manager a periodical time period. Upon receiving a request for triggering the first type event, it is determined whether to trigger second type event together with triggered first event according to a counter value counted by the counter and time period registered by the second type event; wherein second type event is determined as not being triggered when counter value is less than time period registered by second type event and second type event is determined as being triggered when counter value is equal to or exceeds time period registered by second type event.

Claims

1. An event triggering method for triggering events during a sleep mode for use in a mobile device, wherein the events comprise at least one first type event and at least one second type event, comprising:

providing an event manager operated in the sleep mode, wherein the event manager comprises a counter;

registering to the event manager a periodical time period for the second type event; and

upon receiving a request for triggering the first type event, determining whether to trigger the second type event together with the triggered first type event according to a counter value counted by the counter and the time period registered by the second type event;

wherein the second type event is determined as not being triggered in response to the counter value being less than the time period registered by the second type event and the second type event is determined as being triggered in response to the counter value being equal to or exceeding the time period registered by the second type event.

2. The event triggering method of claim 1, wherein the first type event is timing-critical/real-time event and the second type event is non-timing critical/non-real-time event.

3. The event triggering method of claim 2, wherein the non-timing critical/non-real-time event is issued from a driver layer of the mobile device or from an application layer of the mobile device.

4. The event triggering method of claim 1, wherein the at least one second type event determined as being triggered comprise two or more events and the two or more events are sequentially triggered based on priority of the two or more events.

5. The event triggering method of claim 1, wherein the determining step further comprises:

in response to determining that the second type event is not being triggered, subtracting the counter value from the time period to obtain a subtracted time period; and

configuring the subtracted time period as the time period of the second type event for subsequent determination.

6. The event triggering method of claim 5, wherein the second type event further includes a tolerance period and the second type event is determined as being triggered together with a closest subsequent first type event in response to the triggering of the second type event has been delayed over the tolerance period.

7. The event triggering method of claim 5, wherein the periodical time period of the second type event is registered to the event manager during an initialization operation of the second type event.

8. A mobile device, comprising:

an event manager operated in a sleep mode and comprises a counter, for triggering events during the sleep mode, wherein the events comprise at least first type events and second type events,

wherein the event manager accepts a registration of a periodical time period from each second type event and upon receiving a request for triggering one of the first type events, determines whether to trigger any of the second type events together with the triggered first type event according to a counter value counted by the counter and the time period registered by each second type event, wherein the second type event is determined as not being triggered in response to the counter value being less than the time period registered by the second type event and the second type event is determined as being triggered in response to the counter value being equal to or exceeding the time period registered by the second type event.

9. The mobile device of claim 8, wherein the first type events are timing-critical/real-time events and the second type events are non-timing critical/non-real-time events.

10. The mobile device of claim 9, wherein the non-timing critical/non-real-time events comprise events issued from a driver layer of the mobile device and events issued from an application layer of the mobile device and the event manager is located on the driver layer of the mobile device for accepting the registration of the non-timing critical/non-real-time events.

11. The mobile device of claim 8, wherein the second type events that are determined as being triggered comprise at least two events and the event manager further sequentially triggers the at least two events based on priority of the at least two events or a predefined time order.

12. The mobile device of claim 8, wherein the second type event further includes a tolerance period and the event manager further determines to trigger the second type event together with a closest subsequent first type event when the triggering of the second type event has been delayed over the tolerance period.

13. The mobile device of claim 8, wherein the periodical time period of each second type event is registered to the event manager during an initialization operation of the second type event.

14. An event triggering method for triggering events during a sleep mode for use in a mobile device, comprising:

receiving an interrupt for triggering a first event;

determining whether to trigger a second event together with the first event according to a counter value from a time point the second event is previously triggered to a current time point; and

performing operation corresponding to the first event and the second event in response to the second event being determined to be triggered.

15. The method of claim 14, wherein the determining step further comprises determining whether the counter value is equal to or exceeds a predetermined time period corresponding to the second event.

16. The method of claim 15, further comprising not triggering the second event in response to the time period being less than the predetermined time period.

17. The method of claim 15, further comprising registering the predetermined time period to an event manager.

18. The method of claim 15, further comprising adjusting the time period corresponding to the second event in response to the completion of the operation of the second event.

19. The method of claim 14, further comprising triggering a third event together with the first event;

wherein the second event and the third event are registered to an event manager and have equal predetermined time period.

20. The method of claim 14, wherein the first event is a timing critical event and the second event is a non-timing critical event.