Subscriber-based ticking model for platforms

• US 8,832,700 B2
• Filed: 09/29/2010
• Issued: 09/09/2014
• Est. Priority Date: 09/29/2010
• Status: Active Grant

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Amin, Nimesh, Liu, Alan Chun Tung
• Primary Examiner(s): Bullock, Jr., Lewis A
• Assistant Examiner(s): Lu, Kevin X
• Application Number:
  US12/893,097
• Publication Number:
  US 20120079487A1
• Time in Patent Office: 1,441 Days
• Field of Search: 718/102
• US Class Current: 718/102
• CPC Class Codes: G06F 13/24 using interrupt G06F13/32 takes precedence
• CPC Class Codes: G06F 13/26 with priority control
• CPC Class Codes: G06F 9/4812 by interrupt, e.g. masked
• CPC Class Codes: G06F 9/4825 Interrupt from clock, e.g. time of day
• CPC Class Codes: G06F 9/4887 involving deadlines, e.g. rate based, periodic
• CPC Class Codes: G06F 9/542 Event management; Broadcasting; Multicasting; Notifications

Abstract

A central manager receives tick subscription requests from subscribers, including a requested period and an allowable variance. The manager selects a group period for a group of requests, based on requested period(s) and allowable variance(s). In some cases, the group period is not a divisor of every requested period but nonetheless provides at least one tick within the allowable variance of each requested period. Ticks may be issued by invoking a callback function. Ticks may be issued in a priority order based on the subscriber'"'"'s category, e.g., whether it is a user-interface process. An application platform may send a tick subscription request on behalf of an application process, e.g., a mobile device platform may submit subscription requests for processes which execute on a mobile computing device. Tick subscription requests may be sent during application execution, e.g., while the application'"'"'s user interface is being built or modified.

Claims

1. A computer-readable storage medium configured with data and with instructions that when executed by at least one processor causes the processor(s) to perform a method for subscriber-based ticking with allowable variances, the method comprising the steps of:

receiving, at a central ticking manager, a plurality of tick subscription requests from tick subscriber(s) via a platform, wherein the tick subscriber(s) are application process(es) and the receiving occurs while user interface code of the application process is being built or modified during execution of an application which owns the application process, each said subscription request being generated by the platform and including a request that a tick be issued within specified repeating intervals which are defined by a requested period and an allowable variance; and

selecting a group period for the tick subscription requests based at least on the requested period(s) and the allowable variance(s), such that a sequence of ticks issued periodically at the group period would provide at least one tick for each interval of each said subscription request.

2. The configured medium of claim 1, wherein the receiving step comprises receiving from a particular subscriber multiple subscription requests which specify different repeating intervals for ticks.

3. The configured medium of claim 1, wherein the selecting step comprises calculating a greatest common divisor of the requested periods.

4. The configured medium of claim 1, wherein the selecting step selects a group period which is not a divisor of at least one requested period but nonetheless provides for at least one tick within the allowable variance of each interval of the requested period.

5. The configured medium of claim 1, wherein the method further comprises checking each group period for any unsatisfied tick requests and issuing tick(s) to satisfy any such requests.

6. The configured medium of claim 1, wherein the method further comprises issuing ticks by repeatedly invoking a callback function which was provided to the central ticking manager by one of the subscriber(s).

7. The configured medium of claim 1, wherein the method further comprises categorizing subscribers and issuing ticks in a priority order which depends at least in part on subscriber categories.

8. A method for subscriber-based ticking with allowable variances, the method comprising the steps of:

a platform locating application processes, each of which requires periodic servicing at an interval; and

the platform sending a central ticking manager of the platform a plurality of tick subscription requests on behalf of the located application processes acting as tick subscribers, each of the plurality of tick subscription requests received at the central ticking manager specifying a service interval as a requested period and an allowable variance from the service interval, and wherein the sending and/or receiving of said subscription requests occurs while user interface code of the application process is being built or modified during execution of an application which owns the application process; and

the central ticking manager selecting a group period for the tick subscription requests based at least on the requested period(s) and the allowable variance(s), such that a sequence of ticks issued periodically at the group period would provide at least one tick for each interval of each said subscription request.

9. The method of claim 8, further comprising sending the central ticking manager a second tick subscription request on behalf of an application process, wherein the subscription requests for that application process specify different service intervals based on differences in expected activity by the application process in response to the ticks.

10. The method of claim 8, further comprising sending the central ticking manager a callback function to be invoked on behalf of an application process each service interval.

11. The method of claim 8, wherein the sending step occurs while a visual tree of the application which owns the application process is being modified on the platform.

12. The method of claim 8, further comprising sending the central ticking manager an indication of an application process'"'"'s priority relative to other processes.

19. The method of claim 8, wherein the method further comprises checking for unsatisfied tick requests and issuing tick(s) to satisfy any such requests.

20. The method of claim 8, wherein the method further comprises categorizing subscribers and issuing ticks in a priority order which depends at least in part on subscriber categories.

13. A computing system comprising:

a logical processor which includes hardware;

a memory in operable communication with the logical processor;

a platform having code residing in the memory, the code configured to locate application processes, each of which requires periodic servicing at an interval, and send a group of tick subscription requests to a central ticking manager of the platform, wherein each request of the group of tick subscription requests specifies a subscriber service interval as a requested period and an allowable variance from the service interval, wherein each request in the group of application process tick subscription requests is from an application process acting as a tick subscriber, each said application process is owned by an application in a set of one or more applications, and wherein the sending occurs while user interface code of the respective application process is being built or modified during execution of the application; and

the central ticking manager of the platform residing in the memory and having code configured to select a group period for the group of tick subscription requests based at least on the requested periods and the allowable variances, such that a sequence of ticks issued periodically at the group period will provide at least one tick for each interval of each said subscription request.

14. The system of claim 13, wherein the system comprises a mobile computing device platform, and the tick subscription requests identify processes which reside in the memory and are configured to execute on the mobile computing device platform.

15. The system of claim 13, wherein the tick subscription requests comprise a first request to receive ticks at a first requested period to service network I/O, and a second request to receive ticks at a second requested period to service a CPU-bound process.

16. The system of claim 13, wherein the system further comprises a user interface having threads and also comprises non-user-interface threads, and the central ticking manager is configured to give higher priority to user interface threads than non-user-interface threads.

17. The system of claim 13, wherein the system is configured to utilize at least one of the following mechanisms to provide ticks:

a software signal, an interrupt, a software event, a software message.

18. The system of claim 13, wherein the central ticking manager is configured to select a group period which is not a divisor of at least one requested period but nonetheless provides for at least one tick within the allowable variance of each interval of the requested period.