WO2007076636A1

WO2007076636A1 - A management system and management method of the timer in the software system

Info

Publication number: WO2007076636A1
Application number: PCT/CN2005/002425
Authority: WO
Inventors: Chuan Ye; Xinghua Li; Wu Luo
Original assignee: Zte Corporation
Priority date: 2005-12-31
Filing date: 2005-12-31
Publication date: 2007-07-12
Also published as: CN101361320B; HK1126907A1; CN101361320A

Abstract

A management system and management method of the timer in the software system, applying to the timer applied the task/process setting, at least comprises an absolute timer management module and a relative timer management module, in which the absolute timer management module includes an absolute timer queue and the relative timer management module includes a TICK queue and a long time length relative timer queue. The main method comprises: the timer resource of the software system is managed unifiedly; the timers applied the task/process setting are divided into two kinds of absolute timers and relative timers, and the different kind of timers are managed respectively by the different timer queues. Using the present invention, it reduces the burden related to the timing and clocking of the timer management in the software system, and prevents the confusedness of the timer use in the software system.

Description

Management system and management method of timer in software system

The present invention relates to a timing and timing technique in a software system, and more particularly to a management system and management method for a timer in a software system, which can be used in a mobile terminal and a network side switching device. Background technique

At present, the complexity of the software system of communication equipment is increasing, and the requirements for timer management and use are also rising. The current software system requires the use of timers to minimize the system load caused by timer management, reduce the timing error caused by timer updates, and make the timer management and use highly versatile and reduce the software system. Development difficulty and development cost, improve the efficiency and stability of the software system timer.

The Chinese patent application with the application number CN02110936 proposes a timing method for the timer in the embedded real-time operating system, which comprises the following steps: a. setting a timer description array of the required maximum number of timers; b, using an array of a certain length and The loop pointer variable constitutes a loop timing queue, and the loop pointer variable points to each array element in a circular manner; c. When the upper layer application needs a timer task, inserts a new timer into the loop timing queue; d. When the timing period comes, the loop pointer variable moves backward, and the queue list queue of the index group element is emptied. If it is empty, it waits for the next timing period to arrive; if it is not empty, it judges the list queue one by one. Whether the multiple value in the description structure of the timer is 0. If it is 0, it indicates that the timer has expired, and the corresponding timing operation and re-insertion timer operation are performed. At the same time, the timer description array is deleted from the linked list queue; if the multiple value is not 0, the multiple value is decremented by 1, and then the next timer is determined. The above technical solution of the patent application includes the following defects: 1. The number of times in the linked list queue is decremented, which increases the burden on the system; 2. It does not consider the problem of the ultra long time timer. Summary of the invention

In order to solve the above problems, an object of the present invention is to provide a simple and efficient management system and management method for a timer in a software system, which does not need to perform a decrementing operation on the timing duration of each timer, and not only considers a short duration timer. The management of the queue, and the management of the long-term timer queue is added. The basic idea of the present invention is: unified management of timer resources in a software system; the timers set by application tasks/processes are divided into two categories: absolute timers and relative timers, and different types of timers are respectively different. Timer queue management.

In order to achieve the above object, a timer management system in a software system of the present invention is applicable to a timer set by an application task/process, and the timer set by the application task/process includes an absolute timer and a relative timer, and the foregoing The management system includes at least one absolute timer management module and one relative timer management module, wherein:

The foregoing absolute timer management module includes at least: an absolute timer queue for managing the above absolute timer;

The foregoing relative timer management module includes at least: a TICK queue for managing a relative timer of a short duration, wherein each element in the TICK queue hangs a short duration relative timer queue; and a long duration relative timer Queue, a relative timer used to manage long periods of time. The above-mentioned absolute timer queue is a doubly linked list; the TICK queue is an array whose length is MAX-TMCB-NUM, where MAX_TMCB_NUM is the maximum number of timers allowed by the relative timer management module. The timing duration of the relative timer in each of the short-term relative timer queues is less than or equal to MAX_TMCB_NUM TIC:, where TICK is one unit time; and the relative timer in each of the short-term relative timer queues described above At the same time.

In addition, the long-term relative timer queue is an array whose length is MAX_TMCB_UM, where MAX_TMCB_NUM is the maximum number of timers allowed by the relative timer management module; the relative duration of the long duration The relative timers in the queue have a timing greater than MAXJTMCB—NUM TICKs, where TICK is one unit time.

To achieve the above objective, a method for managing a timer in a software system of the present invention is applicable to a timer set by an application task/process, and includes at least the following steps:

Step 1: The management system divides the timer set by the application task/process into an absolute timer and a relative timer; 'Step 2: The management system determines whether the timer to be managed is an absolute timer or a relative timer, if Absolute timer, step 3 is performed; if it is a relative timer, step 4 is performed;

Step 3: The absolute timer management module forms the above absolute timer into an absolute timer queue, and the absolute timer queue manages the above absolute timer.

Step 4: The management system determines whether the timing duration of the relative timer is greater than MAX TMCB NUM TICK, and if not, step 5 is performed; Step 5: The relative timer management module forms a relative timer queue of a short duration, which is a relative timer that is less than or equal to MAX_TMCB JNiUM TICKs at the same time, and the relative timer management module is short. The relative timer queue of the duration is hung to an element in the TICK queue, and the TICK queue manages the relative timers whose timing duration is less than or equal to MAX_TMCB_NUM TICKs; wherein the array length of the TICK queue is MAX_TMCB— NUM, and MAX__TMCB__NUM is the maximum number of timers allowed by the above relative timer management module;

Step 6: The relative timer management module forms a relative timer queue with a duration longer than MAX_TMCB__NUM TICKs, and the relative duration of the long timer is greater than MAX_TMCB_UM. The relative timer of the TICK is managed; wherein the length of the long-term relative timer queue is MAX-TMCB-UM, and MAX_TMCB-NUM is the maximum number of timers allowed by the relative timer management module; Each element in the long-term relative timer queue indicates whether the TMCB with the same index number is set.

For example, if the 10th element in the long-term relative timer queue is true (TRUE), it means that TMCB[10] has been used by a certain timer.

Wherein, the above step 3 includes the following steps:

Step 301: The absolute timer management module configures the absolute timer according to the length of the set time to form the absolute timer queue, and the absolute timer of the earliest arrival time is arranged in the first part of the absolute timer queue, and the latest arrival time The absolute timer is listed at the end of the above absolute timer queue;

Step 302: The timer scan task scans in the above absolute period in one scan period Absolute timer of the queue header;

Step 303: The timer scanning task determines whether the absolute timer ranked in the first timer queue is expired, and if not, the timer scanning task continues to scan the absolute timer in the next scanning period; if Perform step 304;

Step 304: The timer scanning task removes the foregoing absolute timer from the absolute timer queue header, and sends a timeout message to the task that sets the absolute timer; and then performs step 305;

Step 305: The timer scanning task scans an absolute timer that is ranked at the head of the absolute timer queue in the next scanning period.

Step 306: Steps 303 to 305 are repeatedly executed until the absolute timer of the first timer queue is not reached or the absolute timer queue is empty.

In the above step 5, the relative timer queue that constitutes the short duration includes the following steps: Step 501: The relative timer management module sets a system cursor, where the system cursor indicates the current system time, and the value ranges from 0 to 0. (MAX_TMCB_NUM-1); Step 502: The relative timer management module converts the timing duration of each of the relative timers whose timing duration is less than or equal to MAX_TMCB-NUM TICK to TICK relative to the system cursor The offset of the unit;

Step 503: The relative timer management module forms a short-term relative timer queue of all the relative timers having the same offset position as the system cursor, and hangs it down to an element in the TICK queue.

Wherein, in the above step 5, managing the relative timer in which one of the timing durations is less than or equal to MAX TMCB NUM TICKs includes the following steps - Step 504: The timer scan task scans the relative timer in one scan period, and the system cursor is increased by 1;

Step 505: The timer scan task determines whether the system cursor overlaps with the relative timer. If not, the timer scan task continues to scan the relative timer in the next scan period, and the system cursor increases by 1; otherwise, Go to step 506;

Step 506: The timer scanning task removes the relative timer queue of the short duration of the relative timer from the TICK queue, and sends a timeout message to the task that sets the relative timer.

In the above step 503, regardless of whether all the relative timers in the short-term relative timer queue are set at the same time, all the relative timers in the short-term relative timer queue arrive at the same time, because all of the above The relative timer and the above system cursor have the same TICK offset position; any relative timer with a timing duration less than or equal to MAX_TMCB_NUM TICK is placed in the above TICK queue as: position = (system cursor current position) Value + TICK number relative to the timer's timing duration) mod (MAX - TMCB - NUM).

The step 6 includes the following steps: Step 601: The foregoing relative timer management module sets a system cursor, where the relative timer of the long-term relative timer queue is greater than MAX_TMCB_NUM TICK. The system cursor indicates the current system time, and the value ranges from 0 to (: MAX - TMCB - UM - 1); Step 602: The relative timer management module gives a compensation value to the relative timer, and the relative timer The final timing is the sum of the above compensation value and the number of TICKs of the relative timers to be set, that is, the final timing of the relative timer = compensation value + The number of TICKs of the relative duration of the relative timer to be set;

Step 603: The timer scan task scans the relative timer in one scan period, and the system cursor is increased by 1;

Step 604: The timer scanning task subtracts the duration of the MAXJTMCB-NUM TICKs from the final timing duration of the corresponding relative timer at the location of the system cursor; Step 605: The foregoing relative timer management module determines the above step 604. Whether the timing duration of the relative timer subtraction is less than or equal to MAX_TMCB_UM TICK, if yes, step 606 is performed; otherwise, step 607 is performed;

Step 606: The relative timer management module removes the relative timer in the foregoing step 604 from the long-term relative timer queue, and then puts it into the TICK queue for a short duration under one of the elements. The tail of the relative timer queue;

Step 607: Repeat steps 603 to 605.

In addition, since the time taken by the system cursor from the start position to the original position and then back to the original position is exactly the time of the MAX_TMCB_UM TICK, the timer scan task in the above step 604 can be considered as the above. The corresponding relative timer at the location of the system cursor has passed the MAXJTMCB_NUM TICK time.

In addition, in the above step 602, the method for calculating the compensation value by the relative timer management module is:

Step 611: The relative timer management module determines whether the index number (tid) of the TMCB used by the relative timer is greater than the current position value of the system cursor, and if yes, step 612 is performed; otherwise, step 613 is performed;

Step 612: Compensation value = MAX_TMCB - NUM - (TMCB relative to the timer used) Index number (tid) - the current position value of the system cursor:);

Step 613: The compensation value of the second system cursor current position value is relative to the TMCB index number used by the timer (tic.

The management system and the management method according to the present invention have the following advantages: 1. The burden on the timing and timing of the timer management in the software system is alleviated; 2. The timer in the software system is prevented from being used. The chaos on it.

The above and other objects, features, and advantages of the present invention will become more apparent and understood by the appended claims appended claims DRAWINGS

1 is a schematic diagram of main processes of the management method according to the present invention;

Figure 2 is a schematic diagram of a TICK queue consisting of 2000 array elements of the present invention. detailed description

An embodiment is now proposed based on the present invention, but the invention is not limited to this specific embodiment.

FIG. 1 is a schematic diagram of main processes of the management method according to the present invention. As shown in Figure 1, it includes at least the following steps:

Step 1: The management system divides the timer set by the above application task/process into an absolute timer and a relative timer;

Step 2: The management system determines whether the timer to be managed is an absolute timer or a relative timer. If it is an absolute timer, step 3 is performed; if it is a relative timer, step 4 is performed; Step 3: The absolute timer management module forms the above absolute timer into an absolute timer queue, and the absolute timer queue manages the above absolute timer.

Step 4: The management system determines whether the timing duration of the relative timer is greater than MAX_TMCBJNTUM TICK, if not, execute step 5; otherwise, perform step 6; Step 5: The relative timer management module will arrive at the same time The relative timers whose timing duration is less than or equal to MAX_TMCB_NUM TICKs constitute a short-term relative timer queue, and the relative timer management module hangs the short-term relative timer queue to the TICK queue. Under one element, the TICK queue manages the relative timers whose timing duration is less than or equal to MAX_TMCB_NUM TICKs; wherein the array length of the TICK queue is MAXJTMCB_NUM, and MAX_TMCB_UM is the relative timer management module The maximum number of timers allowed to be set;

Step 6: The relative timer management module forms a relative timer queue TidArray [MAX_TMCB_NUM] whose timing duration is greater than MAX_TMCB_NUM TICK, and the relative timer queue of the long duration is opposite to the timing. The relative timers whose duration is greater than MAXJTMCB-NUM TICKs are managed; wherein the length of the long-term relative timer queue array is MAXJTMCB_NUM, and the MAXJTMCB-NUM is the maximum number of timers allowed by the relative timer management module. Each of the above-mentioned long-term relative timer queues indicates whether or not the TMCB having the same index number is set.

For the management of the absolute timer, the timing precision set by the above-mentioned absolute timer management module is a second level, and the management method of the above absolute timer management module includes the following steps:

Step 301: The above absolute timer management module sets the above absolute timer according to the set time. The length of the above-mentioned absolute timer queue, the absolute timer of the earliest arrival time is ranked in the first part of the above absolute timer queue, and the latest absolute timer is arranged at the end of the above absolute timer queue;

Step 302: The timer scan task scans an absolute timer ranked in the header of the absolute timer queue in one scan period;

Step 303: The timer scanning task determines whether the absolute timer listed in the header of the absolute timer queue is up, if not, the timer scanning task continues to scan the absolute timer in the next scanning period; if Perform step 304;

Step 304: The timer scanning task removes the absolute timer from the absolute timer queue header, and sends a timeout message to the task that sets the absolute timer; then step 305 is performed;

2 is a schematic diagram of a TICK queue consisting of 2000 array elements according to the present invention. The system cursor indicates the current system time, and the system cursor has a value ranging from 0 to 1999. The management of the relative timer of the present invention will be described below with reference to Figs. 1 and 2.

For a relative timer whose timing duration is less than or equal to 2000 TICK, the relative timer queue constituting the short duration includes the following steps: Step 501: The relative timer management module sets a system cursor, where the system cursor represents the current system At the moment, its value ranges from 0 to 1999 _; Step 502: The relative timer management module converts a timing duration of each of the relative timers whose timing duration is less than or equal to 2000 TICKs into an offset in units of TICK with respect to the system cursor.

The foregoing relative timer management module is less than or equal to one of the foregoing timing durations.

The method for managing the relative timers of 2000 TICKs includes the following steps: Step 504: The timer scan task scans the relative timers in one scan period, and the system cursor increases by 1; indicating the short duration of the relative timers The relative lifetime of all relative timers in the relative timer queue is reduced by one TICK;

Step 505: The timer scan task determines whether the system cursor overlaps with the relative timer, and if not, the timer scan task continues to scan the relative timer in the next scan period, and the system cursor increases. 1; otherwise , performing step 506;

For example: Set a relative timer with a duration of 800 TICKs, which is offset from the system cursor by 800. During each scan cycle, the system cursor is incremented by 1. After the timer scan task scans 800 times, the system cursor coincides with the relative timer, that is, the duration of the relative timer of 800 TICK is over.

For a relative timer with a timing duration greater than 2000 TICK, the above relative timer tube The method for managing the relative timer of one of the long-term relative timer queues TidArray[2000] with a timing duration greater than 2000 TICKs includes the following steps: Step 601: The foregoing relative timer management module sets a system a cursor; wherein the system cursor indicates a current system time, and the range of the cursor is 0 to 1999;

Step 602: The relative timer management module gives a compensation value to the relative timer, and the final timing duration of the relative timer is the sum of the compensation value and the TICK number of the timing duration of the relative timer to be set, that is, the relative timing. The final timing of the device = the compensation value + the number of TICKs of the relative duration of the relative timer to be set;

Step 604: The timer scan task subtracts the duration of the corresponding timing of the corresponding relative timer at the position of the system cursor by 2000 TICK; since the system cursor rotates from the starting position and then returns to the circle The time taken to the original location is exactly 2000 TICK time, so the timer scan task in step 604 can assume that the corresponding relative timer at the location of the system cursor has passed 2000 TICK time; Step 605 The relative timer management module determines whether the timing duration of the relative timer subtraction in the above step 604 is less than or equal to 2000 TICKs, and if yes, executing step 606; otherwise, executing step 607;

Step 606: The relative timer management module removes the relative timer in the foregoing step 604 from the long-term relative timer queue TidArmy[2000], and then puts it into one of the elements in the TICK queue. The tail of the relative timer queue for a short duration; Step 607: Steps 603 to 605 are repeatedly performed.

Step 612: Compensation value = 2000 - (relative to the TMCB index number (tid) used by the timer) The current position value of a system cursor;

Step 613: Compensation value = the current position value of the system cursor is the index number (tid) of the TMCB used by the timer.

For example, suppose the current position value of the system cursor is 1500, the TICK number of the relative timer of the relative timer to be set is 3000, and the index number (tid) of the TMCB used by the relative timer is 1000, then the relative timer management module The compensation value for the relative timer is: 1500 - 1000 = 500, then the final timing of the relative timer is: 500+3000=3500. The timer scanning process is as follows: The system cursor needs to pass 1500 TICK durations before moving to the relative timer position, that is, moving to TidArray[1000] _; at this time, the timer scanning task reduces the final timing of the relative timer. Go to 2000 TICK, leaving 1500 TICK; Since the relative timer duration of the relative timer is less than 2000 TICK, the relative timer management module will compare the timer TidArray[1000] from the long-term relative timer queue TidArray [ It is taken out in 2000] and then placed in the tail of the short-term relative timer queue hanging under one of the elements in the above TICK queue.

The working principle of the present invention has been described in detail above, but this is only for ease of understanding. The visualized examples of N2005/002425 should not be construed as limiting the scope of the invention. Also, various possible equivalents and modifications may be made without departing from the scope of the invention as defined by the appended claims.

Claims

Rights request

A timer management system for a software system, which is applicable to a timer set by an application task/process, wherein the timer set by the application task/process includes an absolute timer and a relative timer, and the foregoing management system is at least It includes an absolute timer management module and a relative timer management module, where:

The foregoing relative timer management module includes at least:

a TICK queue for managing a relative timer of a short duration, wherein each element in the TICK queue hangs a short duration relative timer queue;

A long-term relative timer queue for managing long-term relative timers.

2. The management system of claim 1 wherein

The above absolute timer queue is a doubly linked list;

The above TICK queue is an array whose array length is MAX_TMCB_NUM, where MAX_TMCB_NUM is the maximum number of timers allowed by the above relative timer management module;

The timing duration of the relative timer in each of the short-term relative timer queues is less than or equal to MAX_TMCB_NUM TICK, where TICK is one unit time; and the relative timer in each of the short-term relative timer queues described above At the same time.

3. A management system according to claim 2, characterized in that The above long-term relative timer queue is an array whose array length is

MAX_TMCB_NUM, where MAX_TMCB_NUM is the maximum number of timers allowed for the relative timer management module described above;

The relative duration of the relative timers in the long-term relative timer queue is greater than MAX_TMCB_NUM TICK, where TICK is one unit time.

4. A method for managing a timer in a software system, which is applicable to a timer set by an application task/process, and is characterized by at least the following steps:

Step 2: The management system determines whether the timer to be managed is an absolute timer or a relative timer, if it is an absolute timer, step 3 is performed; if it is a relative timer, step 4 is performed;

Step 4: The management system determines whether the timing duration of the relative timer is greater than MAX_TMCB_NUM TIC:, if not, execute step 5; otherwise, perform step 6; Step 5: The relative timer management module will arrive at the same time The relative timers whose timing duration is less than or equal to MAX_TMCB_NUM TICKs constitute a short-term relative timer queue, and the relative timer management module hangs the short-term relative timer queue to the TICK queue. Under one element, the TICK queue manages the relative timers whose timing duration is less than or equal to MAX_TMCB-NUM TICKs; wherein the array length of the TICK queue is MAX-TMCB-NUM, and MAX-TMCB-NUM For the above relative The maximum number of timers allowed by the timer management module;

Step 6: The relative timer management module forms a relative timer queue whose timing duration is greater than MAX_TMCB_UM TICKs, and the relative timer queue of the long duration is longer than the MAX_TMCB_NUM TICK. The relative timer is managed; wherein the length of the long-term relative timer queue is MAX_TMCB_NUM, and MAX_TMCB_NUM is the maximum number of timers allowed by the relative timer management module; the relative duration of the long duration Each element in the queue indicates whether a TMCB with the same index number is set.

5. The management method according to claim 4, wherein the step 3 comprises the following steps:

Step 301: The absolute timer tube module forms the absolute timer according to the length of the set time to form the absolute timer queue, and the absolute timer of the earliest arrival time is arranged in the first part of the absolute timer queue, and the latest arrival time The absolute timer is listed at the end of the above absolute timer queue;

Step 304: The timer scanning task removes the absolute timer from the absolute timer queue header, and sends a timeout message to the task that sets the absolute timer; then step 305 is performed; Step 305: The timer scanning task scans an absolute timer that is ranked at the head of the absolute timer queue in the next scanning period.

Step 306: Repeat steps 303 to 305 until the absolute timer of the first timer queue is not reached or the absolute timer queue is empty.

The management method according to claim 4, wherein the forming the relative timer queue of the short duration in the above step 5 comprises the following steps:

Step 501: The relative timer management module sets a system cursor, where the system cursor represents a current system time, and the value ranges from 0 to (MAX - TMCB - NUM - 1); Step 502: The above relative timer management The module converts each of the above-mentioned timing durations of the relative timers whose timing duration is less than or equal to MAX_TMCB-NUM TICKs into an offset of TICK with respect to the above system cursors;

7. The management method according to claim 6, wherein managing the relative timer of one of the long-term relative timer queues having a timing duration less than or equal to MAX_TMCB_NUM TICKs in the step 5 includes the following steps. :

Step 504: The timer scan task scans the relative timer in one scan period, and the system cursor is increased by 1;

Step 505: The timer scan task determines whether the system cursor overlaps with the relative timer. If not, the timer scan task continues to scan the relative timer in the next scan period, and the system cursor increases by 1; otherwise, Go to step 506; Step 506: The timer scanning task removes the short timer duration relative timer queue in which the relative timer is located from the TICK queue, and sends a timeout message to the task that sets the relative timer.

8. The management method according to claim 7, characterized in that

In the foregoing step 503, regardless of whether all the relative timers in the relative timer queue of the short duration are set at the same time, all the relative timers in the relative timer queue of the fe duration are at the same time;

The calculation method for placing any relative timer whose timing duration is less than or equal to MAXJTMCB-NUM TICK into the above TICK queue is: position = (the current position value of the system cursor + the number of TICKs relative to the timer duration) mod (MAX - TMCB - NUM).

The management method according to claim 4, characterized in that, for the relative timer in which one of the timing durations is greater than MAX_TMCB-NUM TICKs, the above step 6 includes the following steps:

Step 601: The foregoing relative timer management module sets a system cursor; wherein the system cursor represents a current system time, and the value ranges from 0 to (MAX - TMCB - UM - 1); Step 602: The foregoing relative timer management The module gives a compensation value to the relative timer, and the final timing duration of the relative timer is the sum of the compensation value and the TICK number of the relative timer of the relative timer to be set, that is, the final timing duration of the relative timer = the compensation value. + the number of TICKs of the relative duration of the relative timer that needs to be set;

Step 604: The above timer scanning task corresponds to the location of the system cursor Comparing the final timing of the timer with the duration of the MAX-TMCB-NUM TICK; Step 605: The relative timer management module determines whether the timing duration of the relative timer subtraction in the above step 604 is less than or equal to. MAX_TMCB_NUM TICK If yes, go to step 606; otherwise, go to step 607;

Step 607: Repeat steps 603 to 605.

The management method according to claim 9, wherein in the step 602, the method for calculating the compensation value by the relative timer management module is:

Step 611: The relative timer management module determines whether the index number of the TMCB used by the relative timer is greater than the current position value of the system cursor, and if yes, step 612 is performed; otherwise, step 613 is performed;

Step 612: Compensation value -MAX_TMCB_NUM- (relative to the TMCB index number used by the timer, the current position value of the system cursor);

Step 613: Compensation value = The current position value of the system cursor is relative to the index number of the TMCB used by the timer.