CN1996990A - A scheduling method for VoIP service - Google Patents

Abstract

The invention discloses a VoIP service scheduling method, which is characterized in that the method includes the following steps: a. Judging whether there is a VoIP service that needs to be scheduled, if there is, performing step b, if not, returning to step a; b. judging Whether the current moment is the VoIP scheduling time, if yes, then execute step c, if not, then return to step a; c. judge whether there is a VoIP service whose scheduling waiting time is greater than the waiting time threshold, if yes, then execute step d, if not , then return to step a; d. add the VoIP service whose scheduling waiting time is greater than the waiting time threshold to the VoIP scheduling candidate set at the current scheduling moment; e. determine and send the data of the VoIP service that can be sent in the VoIP scheduling candidate set. By using the method disclosed by the invention, the VoIP service carried by high-speed downlink packet access HSDPA can be scheduled.

Description

A scheduling method for VoIP service

technical field

The invention relates to a scheduling technology in a mobile communication system, in particular to a scheduling method for voice over IP (VoIP, Voice over IP) services.

Background technique

The use of VoIP is a transmission technology that utilizes a router-based IP packet switching network to realize voice communication. One of the evolution trends of the mobile communication system is all-IP network, including service IP. The use of VoIP technology in mobile communication systems can save bandwidth, improve spectrum efficiency, and provide a unified interface and platform for voice and data. If there are dedicated channels and shared channels in the mobile communication system, the VoIP service can be supported by either the dedicated channels or the shared channels. The shared channel refers to multiple users occupying the same channel, which supports time division multiplexing and code division multiplexing. Scheduling of VoIP services.

For example, the VoIP in Universal Mobile Telecommunications System (UMTS, Universal Mobile Telecommunication System) realizes end-to-end voice IP transmission through UMTS. UMTS can use a dedicated channel (DCH, Dedicated Channel) to support VoIP, or use a shared channel that is high-speed Downlink packet access (HSDPA, High Speed Downlink Packet Access) channel to support VoIP. The DCH can support various services such as conversation, flow, background, and interaction, and can also support VoIP; the HSDPA channel has higher spectral efficiency than a dedicated channel, but the original intention of the HSDPA channel is to be used for non-real-time or delay-sensitive For insensitive services, if you want to support mobile VoIP services with low data rate and high delay requirements on the HSDPA channel, you need to consider the comprehensive impact of delay, spectrum efficiency, code resource utilization efficiency, power consumption and other factors.

The disadvantage of the prior art is that there is no solution in the prior art for scheduling the VoIP service carried by the HSDPA channel.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method for scheduling VoIP services, capable of scheduling VoIP services carried by HSDPA.

Technical scheme of the present invention is realized like this:

A method for dispatching voice over IP VoIP services, the method comprising the following steps:

a. Determine whether there is a VoIP service that needs to be dispatched, if yes, perform step b, if not, return to step a;

b. Judging whether the current moment is the VoIP scheduling moment, if yes, then perform step c, if not, then return to step a;

c. Judging whether there is a VoIP service whose scheduling waiting time is greater than the waiting time threshold, if there is, then perform step d, if not, then return to step a;

D. Add the VoIP service whose scheduling waiting time is greater than the waiting time threshold to the VoIP scheduling candidate set at the current scheduling moment;

e. Determine and send the data of the VoIP service that can be sent in the VoIP scheduling candidate set.

The following steps are included between said step a and step b:

a11, judging whether there is a new VoIP service in the VoIP service that needs to be dispatched, if there is, then perform step a12, if not, then perform step b;

a12, judging whether the VoIP services that need to be dispatched are all new VoIP services, if yes, then perform step a13, if not, then perform step a15;

a13, VoIP scheduling system timing is set to zero;

a14, determine the VoIP scheduling time according to the time set to zero in the step a13;

a15. Start the scheduling waiting time of the new VoIP service mentioned in step a11.

In the step a, if there is no VoIP service that needs to be scheduled, before returning to step a, further include: setting the timing of the VoIP scheduling system to zero.

After the VoIP dispatching system resets the timing to zero, it is judged whether there is a VoIP service with a retransmission request before returning to step a. If it exists, then step a22 is performed, and if it does not exist, then return to step a;

a22. Add the VoIP service with retransmission request to the current VoIP scheduling candidate set, and execute step e.

Further include before step e:

e1. All VoIP services collect their own data.

The VoIP service that determines the data that can be sent in step e is specifically:

e11, according to the data collected in the step e1, respectively determine the required code word and the required power of the candidate VoIP service;

e12. Determine the VoIP service that can send data according to the result of comparing the required codeword sum and required power sum with the available codeword and available power respectively.

Step e further includes: arranging the VoIP services in the VoIP scheduling candidate set.

The arranging is: arranging the VoIP services according to the waiting time of each candidate VoIP service.

When the current moment in step b is the VoIP scheduling moment, the following steps are included before step c is performed:

b11, judging whether there is a VoIP service with a retransmission request, if it exists, then perform step b12, if it does not exist, then perform step c;

b12. Add the VoIP service with retransmission request to the VoIP scheduling candidate set.

When there is no VoIP service whose waiting time is greater than the waiting time threshold is scheduled in step c, it is judged whether the VoIP scheduling candidate set is empty before returning to step a, if yes, then return to step a, if not, then execute step e.

The following steps are further included between steps d and e:

d11, judging whether there is a VoIP service with a retransmission request, if it exists, then execute step d22, if it does not exist, then return to step a;

d22. Add the VoIP service with the retransmission request to the VoIP scheduling candidate set, and execute step e.

Correspondingly, if there is no VoIP service with a waiting time greater than the waiting time threshold scheduled in step c, step d11 is performed, wherein, if it is judged in step d11 that there is no VoIP service with a retransmission request, then return to step a.

In step d11, when there is no VoIP service with a retransmission request, it is judged whether the VoIP scheduling candidate set is empty before returning to step a, if yes, then return to step a, if not, then execute step e.

Step e further includes: arranging the VoIP services in the VoIP scheduling candidate set.

The arranging is: arranging the VoIP services according to whether each candidate VoIP service has a retransmission request and the length of the waiting time.

The sending data in step e is performed by code division multiplexing.

After step e, further include:

f. The scheduling waiting time of the sent VoIP service data is terminated, and return to step a.

The invention provides a VoIP scheduling method for adding VoIP services whose scheduling waiting time is greater than the waiting time threshold into the VoIP scheduling candidate set at the time of VoIP scheduling, and arranging and sending the VoIP services in the VoIP scheduling candidate set. The present invention has following beneficial effect:

Through uniform fixed or unfixed distribution of VoIP scheduling time, VoIP scheduling system timing, VoIP service scheduling waiting timing, etc., and comparing the required codeword sum, required power sum, and system available codewords and available power, and through code division multiplexing The transmission of VoIP data takes into account the number of VoIP transmission time intervals (TTIs), available codeword resources, available power resources and other system resources, and can complete the reasonable scheduling of VoIP services in the MAC-hs, so that the UMTS system can operate in spectrum efficiency. Under constraints such as , time delay, etc., it can support VoIP services more effectively.

Description of drawings

Fig. 1 is a schematic diagram of the process of VoIP scheduling in the embodiment of the present invention.

Detailed ways

The VoIP service scheduling method in the present invention is to add the VoIP services whose scheduling waiting time is greater than the waiting time threshold into the VoIP scheduling candidate set at the current scheduling time at the VoIP scheduling time, and arrange and send the VoIP services in the VoIP scheduling candidate set.

The present invention will be described in further detail below with reference to the accompanying drawings and examples.

Fig. 1 is the process schematic diagram that carries out VoIP scheduling in the present embodiment, and the process shown in Fig. 1 comprises the following steps:

Step 101: Judging whether there is a VoIP service that needs to be scheduled, if yes, execute step 103; if not, execute step 102.

Usually step 101 is executed at each scheduling moment. The scheduling time can be the same as the transmission time interval (TTI), or it can be a multiple of TTI.

Judging in step 101 whether there is a VoIP service that needs to be scheduled can be to judge whether there is a VoIP priority queue, such as the step described in step 101 can be in the UMTS system: judging the high-speed shared channel media access control (MAC-hs) scheduling unit Whether there is a VoIP priority queue in the priority queue, if yes, then perform step 103; if not, then perform step 102.

The priority queue (Priority Queue) of the scheduling unit is a data cache provided for each data flow from the upper layer according to its corresponding priority, and there can be priority queues of multiple services in the priority queue of the scheduling unit. The VoIP priority queue is a data cache provided in the dispatching unit for each VoIP service data flow from the upper layer according to its corresponding priority.

The MAC-hs is a MAC entity supporting high-speed shared channel HSDPA located in the base station Node B, which contains a functional module scheduling unit for processing data scheduling. All data in the MAC-hs scheduling unit exists in the form of a priority queue.

In this embodiment, the Node B learns the VoIP service type from the upper radio network controller (RNC) through a message, and the MAC-hs can distinguish the streaming service from the VoIP service after obtaining the message.

Step 102: Set the timing of the VoIP scheduling system to zero, and return to Step 101.

Because the VoIP service may be scheduled and transmitted only at the specified VoIP scheduling time, the VoIP scheduling system needs a timing mechanism that can be called the timing of the VoIP scheduling system. In step 102, since there is no VoIP priority queue in the MAC-hs, the VoIP scheduling system sets the timing to zero and stops working, and is in a waiting state.

If the VoIP service that needs to be scheduled in step 101 does not include the VoIP service that has a retransmission request, for example: when judging whether there is a VoIP service that needs to be scheduled by judging whether there is a VoIP priority queue in the MAC-hs priority queue in step 101 , because the VoIP service with hybrid automatic repeat request (HARQ) retransmission request usually does not exist in the form of VoIP priority queue in MAC-hs priority queue, but is reserved in MAC-hs in the form of data backup, Therefore in the step 102, a judgment can be carried out before returning to the step 101 after the scheduling system timing of VoIP is set to zero, and the judgment is specifically:

Step 102a: Determine whether there is a VoIP service with a retransmission request, if not, return to step 101, and if yes, execute step 102b.

Step 102b: Add the VoIP service with retransmission request to the VoIP scheduling candidate set at the current VoIP scheduling moment, and execute step 116 .

The HARQ is a transmission mechanism that guarantees fast retransmission of data at layer 2 when data transmission fails. The HARQ retransmission request is the retransmission request of the HARQ unit in the MAC-hs, usually generated by the HARQ unit, and the VoIP service with the HARQ retransmission request is generally not in the priority queue of the MAC-hs, but in the form of data backup Retained in MAC-hs.

The retransmission request in this embodiment may be a HARQ retransmission request.

Step 103: Judging whether there is a new VoIP service among the VoIP services that need to be scheduled, if yes, perform step 104; if not, perform step 109.

The steps described in step 103 may be in the UMTS system: judging whether there is a new VoIP priority queue in the MAC-hs priority queue, if yes, then perform step 104; if not, then perform step 109. Judgment result in step 101 is when there is VoIP priority queue in the MAC-hs priority queue, some may be new in these VoIP priority queues, some may be old, can judge the VoIP that determines existence in step 101 by step 103 Whether there is a new VoIP priority queue in the priority queue.

Step 104: A new VoIP service accesses the shared channel.

There can be many VoIP services accessing the shared channel.

The shared channel may be HSDPA. Usually, the VoIP service is judged through HSDPA channel admission control, and the judgment result is admitted access to HSDPA. There are many kinds of decision algorithms for HSDPA channel admission control, such as the HSDPA channel admission control decision algorithm calculated according to the number of users or power, etc. Usually, the HSDPA channel admission control module on the network side uses the access request information of the VoIP service Make access control decisions.

Step 105: Judging whether the VoIP services that need to be scheduled are all new services, if yes, perform step 106; if not, perform step 108.

Step 106: The timing of the VoIP scheduling system is set to zero.

When the first VoIP service accesses the shared channel, or there is only one VoIP service in the shared channel, the timing reset operation of the VoIP dispatching system is executed, and the subsequent VoIP dispatching time takes this time zero as the time reference. In practical applications, there may also be situations where all the VoIP services that need to be scheduled are new and there are multiple ones. At this time, it is also necessary to perform the timing reset action of the VoIP scheduling system.

The shared channel in step 105 and step 106 may be HSDPA.

Step 107: Determine the VoIP scheduling time according to the timing zero of the scheduling system in step 106.

Through step 107, all VoIP scheduling times after the timing of the scheduling system is set to zero are determined. The VoIP scheduling time in step 107 is the time when VoIP services are scheduled, and only at the VoIP scheduling time can VoIP services be scheduled. In this embodiment, the VoIP scheduling time can be uniformly and fixedly distributed or evenly and not fixedly distributed.

For example, the VoIP scheduling time can be evenly and fixedly distributed, and the VoIP service can be scheduled only at the evenly and fixedly distributed VoIP scheduling time. The evenly and fixedly distributed VoIP scheduling times refer to: when the system allocates N/M system resources for VoIP, N scheduling times are uniformly and fixedly used to schedule VoIP services in every M scheduling times, and all VoIP service data are only in these The scheduling time is scheduled for transmission, and N and M are natural numbers. Here, the system resource is the number of TTIs per second. For example: if N/M=1/2, the VoIP service is scheduled once in the second TTI every two TTIs; if N/M=2/5, the VoIP service is scheduled twice every five TTIs, at this time, First, schedule a VoIP service in the second TTI every two TTIs, then schedule a VoIP service in the third TTI every three TTIs, or schedule a VoIP service in the third TTI every three TTIs, and then schedule a VoIP service in the third TTI every A VoIP service is scheduled in the second TTI for each TTI.

The uniform unfixed distribution is relative to the uniform fixed distribution, that is, the scheduling time can be unfixed. For example: when the system allocates N/M system resources for VoIP, in every M scheduling time, N scheduling times can be randomly and evenly used to schedule VoIP services, but these N randomly and evenly distributed scheduling times are not suitable for all VoIP services is the same.

Step 108: start the scheduling waiting time of the new VoIP service.

The scheduling waiting timing refers to: before the data is scheduled to be sent out, counting the waiting time length. If there are multiple new VoIP services, all new VoIP services in step 108 start scheduling and waiting timing. Usually, there are multiple data in one service, and at this time start the scheduling and waiting timing of each data respectively.

Step 109: the existing VoIP services collect their respective data.

In the UMTS system, step 109 may be that the VoIP priority queue in the MAC-hs scheduling unit collects respective data. The collected data is usually data whose minimum unit is a dedicated channel medium access control (MAC-d) protocol data unit (PDU). The MAC-d is a MAC module for processing dedicated channel data, and the MAC-d PDU is a group of data with a fixed format used when forwarding data from higher layers. Usually, the MAC-hs uses the flow control mechanism in the flow control unit to receive data from the RNC regularly or irregularly. The increase in the amount of data brought about by data collection depends on the flow control mechanism and whether there is data generated by data sources such as the RNC.

In the UMTS system, between step 108 and step 109, it may include: judging whether there is a VoIP service satisfying the switching condition of the HSDPA channel to the DCH, if not, performing step 109; if there is, switching the VoIP service meeting the switching condition to After the DCH, it is judged whether there is a VoIP priority queue in the MAC-hs priority queue, if yes, then execute step 109, if not, then return to step 101, if yes, then execute step 109.

In the life cycle of the VoIP service, as the corresponding user tends to move towards the base station, the channel condition of the user may become better and better. If the HSDPA channel is to meet the delay requirements of the VoIP service, the spectrum efficiency will gradually decrease. When the user tends to move towards the edge of the cell, due to the gradual deterioration of channel conditions, HSDPA will also show the problem of reduced spectrum efficiency or the inability to guarantee VoIP service delay. If these situations occur, the VoIP service that meets the switching conditions from the HSDPA channel to the DCH should be switched to the DCH in time.

Step 110: According to the VoIP scheduling time determined in step 107, judge whether the current scheduling time is the VoIP scheduling time, if yes, execute step 111; if not, return to step 101.

Step 111: Judging whether there is a VoIP service with a retransmission request, if yes, go to step 112; if not, go to step 113.

The VoIP service with a retransmission request is usually selected to be sent at the VoIP scheduling time before this time, but the VoIP service that fails to be sent, the VoIP service with a retransmission request is usually reserved in the MAC-hs in the form of data backup.

In the UMTS system, in step 111, it may be determined whether there is a VoIP service with a HARQ retransmission request among the existing HSDPA VoIP services.

Step 112: Add the VoIP service with retransmission request into the VoIP scheduling candidate set.

The VoIP scheduling candidate set is the VoIP scheduling candidate set at the current VoIP scheduling time and only belongs to the current VoIP scheduling time. Therefore, the VoIP scheduling candidate set at the next VoIP scheduling time can only be generated at the next VoIP scheduling time.

The VoIP scheduling candidate set stores some VoIP services in all VoIP services. In this embodiment, VoIP services may be scheduled at the current VoIP scheduling time only if they first enter the VoIP scheduling candidate set, and VoIP services that do not enter the VoIP scheduling candidate set cannot be scheduled at the current VoIP scheduling time.

Step 113: Determine whether there is a VoIP service whose VoIP scheduling waiting time is greater than the waiting time threshold, if yes, go to step 114; if not, go to step 115.

Step 114: Add the VoIP service whose scheduling waiting time exceeds the VoIP scheduling candidate set.

Each VoIP service, such as the VoIP priority queue, will count its scheduling waiting time for this part of the data every time it receives its own data, so as to count the retention time of its oldest data in MAC-hs, and at the same time provide sufficient Using the spectrum of HSDPA, each MAC-hs needs to collect as much data as possible to make full use of the channel conditions. However, this data collection process cannot last for too long. Therefore, the scheduling waiting timer can be used to monitor the scheduling waiting time to monitor the waiting process. If the scheduling waiting timer expires, the VoIP service is added to the VoIP scheduling candidate set as a scheduling candidate.

Usually at each scheduling time, all VoIP services can be screened according to certain principles, and qualified VoIP services can be added to the VoIP scheduling candidate set.

In this embodiment, the scheduling candidate set at a certain VoIP scheduling time may be: a set of VoIP priority queues with HARQ retransmission requests or scheduling waiting time timeouts at this VoIP scheduling time.

In step 110 to step 114 of this embodiment, when the current scheduling time is the VoIP scheduling time, first determine whether there is a VoIP service with a retransmission request, and then determine whether there is a VoIP service whose VoIP scheduling waiting time is greater than the waiting time threshold.

During actual application, if the current scheduling time is the VoIP scheduling time, it can be judged first whether there is a VoIP service whose scheduling waiting time of VoIP is greater than the waiting time threshold, and then judge whether there is a VoIP service having a retransmission request, that is, step 110 during actual application ~Step 114 can be Step 110a~Step 114a:

Step 110a: According to the VoIP scheduling time determined in step 107, judge whether the current scheduling time is the VoIP scheduling time, if yes, then perform step 111a; if not, then return to step 101;

Step 111a: determine whether there is a VoIP service with a VoIP scheduling waiting time greater than the waiting time threshold, if there is, then perform step 112a; if not, then perform step 113a;

Step 112a: adding the VoIP priority queue whose scheduling waiting time has expired to the VoIP scheduling candidate set;

Step 113a: judging whether there is a VoIP service with a retransmission request, if yes, then execute step 114a; if not, then execute step 115;

Step 114a: Add the VoIP service with retransmission request into the VoIP scheduling candidate set.

Step 115: Judging whether the VoIP scheduling candidate set is empty, if yes, return to step 101; if not, execute step 116.

In step 115, if the VoIP scheduling candidate set is empty, it usually waits for the next scheduling moment, and returns to step 101 when the next scheduling moment comes.

Step 116: In the VoIP scheduling candidate set, arrange the scheduling objects at the current moment in order according to whether each candidate VoIP service is retransmitted and the length of waiting time, and determine the required data for each user according to the amount of data collected by each of the top candidate VoIP services. codeword and power.

In this embodiment, VoIP services with retransmission requests are usually added to the VoIP scheduling candidate set. In actual application, if the VoIP scheduling candidate set does not consider whether there are VoIP services with retransmission requests, in step 116, according to each candidate The waiting time of the VoIP service is arranged in order of the VoIP service in the VoIP scheduling candidate set at the current moment, that is, the scheduling object.

When a plurality of VoIP business code division multiplexing scheduling time, there is an upper limit on the number of code division multiplexing users, and a restriction condition can be applied in step 116, that is, the number of the first few candidate VoIP services selected should not exceed the number of code division multiplexing users. Maximum number of users. The upper limit of the number of code division multiplexing users can be set according to the actual situation of the system.

Determining the codeword and power required by each user can be done in the Transport Format Resource Combination (TFRC) unit in MAC-hs, usually using a specific algorithm, and determined according to its channel quality indicator (CQI) report, the specific codeword Algorithms, power allocation schemes, etc. can be implemented using many different methods in the prior art. In step 116, the transport block size (TBS), modulation mode, etc. may also be determined.

There are many ways to arrange the current scheduling objects in the VoIP scheduling candidate set; for multiple candidate VoIP services with the same waiting time for scheduling, they can be arranged randomly.

Step 117: According to the results of comparing the required codeword sum and required power sum with available codewords and available power respectively, determine the VoIP service that can send data and send the data.

In step 117, add up the required codewords and required powers of the candidate VoIP services in the scheduling candidate set respectively, and limit the available codewords and available power of the system to determine whether the sum of required codewords and the sum of required powers can be less than or equal to the available codewords and available power of the system the first several candidate VoIP services, and send the data of the first few candidate VoIP services in a code division multiplexing manner. For example: in step 116, the upper limit of the number of code division multiplexing users is 4, and the demand codewords and requirements of the VoIP service P1, VoIP service P2, VoIP service P3, and VoIP service P4 arranged in the first to fourth places are determined. If the required codeword sum and required power sum of VoIP service P1 and VoIP service P2 are less than the available codeword and available power of the system respectively, and the required codeword sum and required power sum of VoIP service P1, VoIP service P2 and VoIP service P3 Respectively greater than the available codewords and available power of the system, then only the data of VoIP service P1 and VoIP service P2 are sent in step 117, wherein VoIP service P1 and VoIP service P2 will send all or part of the data according to other conditions of the system.

In a UMTS system, the available power may be a High Speed Physical Downlink Shared Channel (HS-PDSCH) power constant. The HS-PDSCH power is the upper limit of the available power for VoIP service scheduling. Dynamic power management can be used to adjust this power value. At this time, all design principles based on this power remain unchanged, and only its value changes.

The available codewords and available power can be set in advance by the system.

In this embodiment, code division multiplexing is generally not performed with other services that may be allocated to the shared channel. In actual application, code division multiplexing can also be performed with other services that may be allocated to the shared channel. For example: in step 116, all candidate services in the VoIP scheduling candidate set and other service candidate sets are considered at the same time, and the candidate VoIP services may be ranked at the top when performing arranging.

Step 118: The scheduling waiting time of the sent VoIP service data is terminated, and the process returns to Step 101.

If the data of the VoIP service P1 and the VoIP service P2 are sent in step 117, after the data is sent, the scheduling waiting time for the sent data of the VoIP service P1 and VoIP service P2 is terminated. In step 117, the VoIP service that does not get a scheduling opportunity, or the VoIP service that has a scheduling opportunity but has no data to send, will enter the scheduling candidate set at the next scheduling time, and strive for the scheduling opportunity again.

In the UMTS system, if the data is sent but failed in step 117, the failed VoIP service is sent. If it is the data in the VoIP priority queue, scheduling is performed in step 118 to wait for timing termination and data backup. If there is HARQ The data requested for retransmission can continue to be retained in the MAC-hs in the form of data backup until it is scheduled and sent successfully, or the number of retransmissions exceeds the limit times specified by the system.

In this embodiment, the step of collecting respective data of the VoIP service is placed in step 109. In fact, as long as there is a VoIP service, each VoIP service will collect its own data, and will not be affected by other steps in FIG. 1 .

In this embodiment, for the UMTS system, the VoIP service with the HARQ retransmission request can be automatically added to the scheduling candidate set at the time of VoIP scheduling, and has the highest priority, that is, it is automatically listed first in the queuing of candidate VoIP services. In actual application, the VoIP service with the HARQ retransmission request may be given the highest priority, or its priority may not be considered. Such as: in step 118, the scheduling waiting timing of the VoIP service data that has been sent is not terminated earlier, if the message that has been successfully sent is received, the scheduling waiting timing of the VoIP service data that has been sent can be terminated, and if the message that fails to be sent is received, the sent message can be retained The scheduling of VoIP service data waits timing; Now, the VoIP service that has sent but fails to send in step 117 also can judge whether to enter the VoIP scheduling candidate set according to its waiting time length; Correspondingly, in step 116 of the present embodiment, only need according to The waiting time of each candidate VoIP service can be used to arrange the scheduling objects at the current moment.

The specific process of the scheduling method in the example of the present invention has nothing to do with the specific admission control algorithm for the VoIP request to access HSDPA. And the following treatments do not affect the method to be protected in the present invention:

Different schemes of uniform and fixed distribution of VoIP scheduling time; design scheme of uniform but not fixed VoIP scheduling time; different values of scheduling waiting timer; different queuing methods of scheduling candidate sets; different upper limit of code division multiplexing users value; whether to perform code division multiplexing with other services that may be allocated to HSDPA; different ways for VoIP priority queues with HARQ retransmission requests to join the scheduling candidate set.

In addition to the UMTS system, the present invention can also be applied to other wireless communication systems like UMTS in which dedicated channels and shared channels coexist.

The above descriptions are only preferred embodiments of the present invention, and are not intended to limit the application scope of the present invention.

Claims (16)

1, a kind of dispatching method of IP voice-over VoIP business is characterized in that the method includes the steps of:

A, judge whether to need the VoIP business of scheduling, if having, execution in step b if do not have, returns step a;

B, judge current time whether be the VoIP scheduling constantly, if, execution in step c then, if not, then return step a;

C, judge whether the scheduling stand-by period greater than the VoIP business of stand-by period thresholding, if having, then execution in step d if do not have, then returns step a;

D, will dispatch the stand-by period greater than the professional current scheduling VoIP scheduling Candidate Set constantly that adds of the VoIP of stand-by period thresholding;

E, determine and send the data of the VoIP business that can send in the VoIP scheduling Candidate Set.

2, method according to claim 1 is characterized in that, comprises following steps between described step a and the step b:

A11, judge to need in the VoIP business of scheduling whether new VoIP business is arranged, if having, execution in step a12 then, if do not have, execution in step b then;

A12, judge to need whether the VoIP business of scheduling all is new VoIP business, if, execution in step a13 then, if not, execution in step a15 then;

A13, VoIP dispatching patcher timing zero setting;

A14, determine that according to the time of zero setting among the step a13 VoIP scheduling constantly;

Timing is waited in the scheduling of new VoIP business described in a15, the setting up procedure a11.

3, method according to claim 2 is characterized in that, among the described step a, if do not need the VoIP business of dispatching, further comprises before returning step a: VoIP dispatching patcher timing zero setting.

4, method according to claim 3 is characterized in that, returns the VoIP business that step a judges whether to have before repeat requests after the described VoIP dispatching patcher timing zero setting, if exist, then execution in step a22 if there is no, then returns step a;

A22, professional current VoIP scheduling Candidate Set, the execution in step e of adding of VoIP of repeat requests will be arranged.

5, method according to claim 1 is characterized in that, further comprises before the step e:

E1, all VoIP business are collected the data of oneself separately.

6, method according to claim 5 is characterized in that, step e is described to determine that the VoIP business that can send data is specially:

E11, determine demand code word, the demand power of candidate VoIP business respectively according to the data of collecting among the step e1;

E12, according to demand code word and, demand power and determine to send the VoIP business of data respectively with the result of available codeword, available horsepower comparison.

7, method according to claim 1 is characterized in that, further comprises among the step e: the VoIP business in the VoIP scheduling Candidate Set is arranged.

8, method according to claim 7 is characterized in that, described being arranged as: the stand-by period length according to each candidate VoIP business is arranged the VoIP business.

9, method according to claim 1 is characterized in that, current time is VoIP scheduling constantly the time among the step b, comprises following steps before the execution in step c:

B11, judge whether to have the VoIP business of repeat requests, if exist, execution in step b12 then, if there is no, execution in step c then;

B12, the professional VoIP of the adding scheduling of the VoIP Candidate Set of repeat requests will be arranged.

10, method according to claim 9 is characterized in that, does not dispatch the stand-by period among the step c greater than the VoIP of stand-by period thresholding when professional, judge whether VoIP scheduling Candidate Set is empty before returning step a, if then return step a, if not, execution in step e then.

11, method according to claim 1 is characterized in that, further comprises following steps between steps d and the e:

D11, judge whether to have the VoIP business of repeat requests, if exist, then execution in step d22 if there is no, then returns step a;

D22, the professional VoIP of the adding scheduling of the VoIP Candidate Set of repeat requests will be arranged, execution in step e.

Correspondingly, do not dispatch the stand-by period among the step c greater than the VoIP of stand-by period thresholding when professional, execution in step d11 wherein, is judged as the VoIP business that does not have repeat requests in the steps d 11, then return step a.

12, method according to claim 11 is characterized in that, in the steps d 11, when not having the VoIP business of repeat requests, return step a and judge whether VoIP scheduling Candidate Set is empty before, if, then return step a, if not, execution in step e then.

13, each described method in 11 according to Claim 8 is characterized in that step e further comprises: the VoIP business in the VoIP scheduling Candidate Set is arranged.

14, method according to claim 13 is characterized in that, described being arranged as: whether have repeat requests, stand-by period length according to each candidate VoIP business arrange the VoIP business.

15, method according to claim 1 is characterized in that, the described transmission data of step e are to be undertaken by the code division multiplexing mode.

16, method according to claim 1 is characterized in that, further comprises after the step e:

F, the scheduling that has sent the VoIP business datum wait for that timing stops, and returns step a.

Images