CN1852581A - Method for transmitting data on downward link - Google Patents

Abstract

The invention discloses a method for transmitting data on the downlink, which includes: identifying the type information when a radio link control entity sends a control PDU, a retransmission data PDU, and a new data PDU to a MAC-d entity; According to the type information, the entity uses the retransmitted data PDU and control PDU to generate a data frame with a higher scheduling priority, and uses the newly sent data PDU to generate a data frame with a lower scheduling priority and sends it to the MAC-hs entity; the MAC-hs entity will The retransmitted data PDU and control PDU in the received higher scheduling priority data frame are distributed to the queue corresponding to the higher scheduling priority, and the newly sent data PDU in the lower scheduling priority data frame is distributed to the corresponding lower queue. Scheduling priority queue. The invention can shorten the waiting time of the control PDU and the retransmission data PDU in the queue, avoid terminal call drop, and greatly improve the downlink data transmission rate.

Description

A method of transmitting data on the downlink

technical field

The invention relates to mobile communication technology, in particular to a method for transmitting data on the downlink when the Wideband Code Division Multiple Access (WCDMA) system adopts the High Speed Downlink Packet Access (HSDPA) technology.

Background technique

HSDPA technology is a technology for high-speed data transmission on the downlink of a WCDMA system. HSDPA technology adopts hybrid automatic retransmission technology, adaptive modulation and coding technology and downlink 2ms short frame technology, and can achieve air interface peak rate up to 13.976Mbps. Therefore, it can greatly improve the throughput rate of downlink user data and improve the downlink capacity of WCDMA system.

When using the HSDPA technology, the downlink data in the WCDMA system can be carried on the high-speed downlink shared channel (HS-DSCH) and transmitted to the mobile terminal. FIG. 1 is a flow chart of the prior art in which downlink data is carried on the HS-DSCH in a WCDMA system and the downlink data is transmitted in an acknowledgment mode. Referring to FIG. 1 , in the prior art, the downlink data of the WCDMA system is carried on the HS-DSCH, and the process of transmitting in acknowledgment mode includes the following steps:

Step 101: A radio link control (RLC) entity in a radio network controller (RNC) sends a MAC-DATA request primitive carrying its own downlink data to a MAC-d entity in the RNC.

Here, the MAC-DATA request primitive is a command set by the protocol and used when sending downlink data between the RLC entity in the RNC and the MAC-d entity in the RNC.

In addition, in this step, the downlink data carried in the MAC-DATA request primitive may include two types of protocol data units (PDUs), namely data PDUs and control PDUs. Wherein, the data PDU includes two types of newly transmitted data PDU and retransmitted data PDU.

Step 102: The MAC-d entity acquires downlink data from the received MAC-DATA request primitive, and determines the scheduling priority of the downlink data.

Here, the MAC-d entity may determine the scheduling priority of the downlink data according to the pre-configured mapping relationship between the service type, service processing priority and scheduling priority, such as the mapping relationship shown in Table 1. Among them, the business processing priority of 1 has the highest priority, and so on, the business processing priority of 15 has the lowest priority; the scheduling priority of 14 has the highest priority, and so on, the scheduling priority of 0 has the highest priority lowest. business type business priority scheduling priority Interactive business 1 14 2 13 3 12 4 11 5 10 6 9 7 8 8 7 9 6 10 5 11 4 12 3 13 2 14 1 15 0 background business - 0

Table 1

Referring to Table 1, for example, in this step, the data received by the MAC-d entity is an interactive service type, and its corresponding service processing priority is 3, then the MAC-d entity can determine the scheduling priority of the acquired downlink data for 12.

Step 103: The MAC-d entity uses all the acquired downlink data to generate an HS-DSCH data frame, and carries the determined scheduling priority information in the HS-DSCH data frame and sends it to the MAC-hs in the base station entity.

Step 104: After receiving the HS-DSCH data frame, the MAC-hs entity distributes all data of the HS-DSCH data frame to a corresponding priority queue corresponding to the current receiver according to the scheduling priority information carried therein.

Here, each queue inside the MAC-hs entity corresponds to different recipients, and all queues corresponding to the same recipient have different scheduling priority levels. Therefore, in this step, the MAC-hs entity The carried scheduling priority information distributes the HS-DSCH data frame to a queue with a corresponding scheduling priority corresponding to the current receiver.

Step 105: When scheduling the queue corresponding to the corresponding scheduling priority of the current receiver, the MAC-hs entity sends all data in the queue to the terminal (UE) according to the principle of first in first out.

It can be seen from the above description that in the prior art, the downlink data of the RLC entity usually includes different types of PDUs, namely, newly transmitted data PDUs, retransmitted data PDUs and control PDUs, while the RLC entity is transmitting to the MAC-d entity When downlinking data, the newly sent data PDU, retransmitted data PDU and control PDU are not distinguished in the MAC-DATA request primitive, so that the MAC-d entity uses the combination of newly sent data PDU, retransmitted data PDU and control PDU to generate an HS -DSCH data frame. Since the MAC-d entity determines a scheduling priority for the combined HS-DSCH data frame, the newly transmitted data PDU, retransmitted data PDU and control PDU in the HS-DSCH data frame have the same scheduling priority. After that, when the MAC-hs entity in the base station receives the HS-DSCH data frame, it directly stores the newly sent data PDU, retransmitted data PDU and control PDU in the HS-DSCH data frame according to the same determined priority in the in the same queue. In this way, since the first-in-first-out principle must be followed in a queue, when there are many newly sent data PDUs in the queue before the retransmitted data PDUs and control PDUs, the retransmitted data PDUs and control PDUs in the queue must wait until the previous The newly sent data PDUs can only be scheduled and sent to the UE after all the PDUs are sent.

In this case, if the UE is in a wireless environment with poor channel conditions, the rate at which the MAC-hs entity in the base station sends data to the UE will be very small, which will cause the control PDU to wait in the queue for a long time Only then can it be scheduled and sent to the UE, which makes the UE wait for a long time before receiving the control PDU. Since the status report information is carried in the control PDU, when the UE fails to receive the control PDU for a long time, it will actively disconnect from the network side, which will cause the UE to drop calls. At the same time, since the retransmission data PDU is not sent out in the queue, the retransmission data PDU will always occupy the sending resources of the RLC entity, so if the retransmission data PDU waits in the queue for a long time, it will make the RLC entity The sending window cannot slide forward for a long time, which greatly affects the downlink data transmission rate.

It can be seen that if any one of the control PDU or the retransmission data PDU cannot be sent out in time, the downlink transmission quality will deteriorate, thereby reducing user satisfaction.

Contents of the invention

In view of this, the main purpose of the present invention is to provide a method for transmitting data on the downlink, so as to improve the quality of downlink transmission.

In order to achieve the above object, the technical solution of the present invention is achieved in that:

A method of transmitting data on a downlink, comprising the steps of:

A. Setting the scheduling priority of the non-new data protocol data unit is higher than the scheduling priority of the new data protocol data unit;

B. The radio link control entity sends the non-new data PDU and the new data PDU to the MAC-d entity, and identifies its type information at the same time;

C. The MAC-d entity uses the received non-new data protocol data unit to generate a data frame with higher scheduling priority according to the identified type information and the set scheduling priority, and uses the received new data protocol The data unit generates a data frame with a lower scheduling priority, and then sends the generated data frame to the MAC-hs entity;

D. The MAC-hs entity distributes the non-new data protocol data units in the received higher scheduling priority data frames to the higher scheduling priority queue, and distributes the received lower scheduling priority data frames. The newly sent data PDUs are distributed to queues with lower scheduling priorities.

The non-new data PDU includes: a control PDU and a retransmission data PDU.

The step A includes: according to the business type and business processing priority, setting the new data protocol data unit to correspond to the third scheduling priority, and setting the control protocol data unit and the retransmission data protocol data unit to correspond to the first scheduling priority and The second scheduling priority, wherein, the first scheduling priority and the second scheduling priority are any scheduling priority higher than the third scheduling priority.

In step A, the first scheduling priority is higher than the second scheduling priority.

In step A, the first scheduling priority is equal to the second scheduling priority.

The method further includes: pre-adding a type bit for identifying the type of the protocol data unit in the sending request primitive, and setting the control protocol data unit and the retransmission data protocol data unit to correspond to the first type value and the second type value respectively;

In step B, the step of identifying the type information when the RLC entity sends the control PDU and the retransmission data PDU to the MAC-d entity includes: the RLC entity transmits the first request primitive Write the first type value on the type bit of the original language, and carry the control protocol data unit in the first send request primitive, and write the second type value on the type bit of the second send request primitive, and retransmit the data The protocol data unit is carried in the second send request primitive, and then the first send request primitive and the second send request primitive are sent to the MAC-d entity;

In step C, the step of the MAC-d entity generating a data frame with a higher scheduling priority includes: the MAC-d entity extracts from the first send request primitive according to the first type value carried in the first send request primitive Obtain the control protocol data unit, and then according to the set control protocol data unit corresponding to the first scheduling priority, use the acquired control protocol data unit to generate the first data frame corresponding to the first scheduling priority, and the MAC-d entity according to The second type value carried in the second sending request primitive obtains the retransmission data protocol data unit from the second sending request primitive, and then according to the set retransmission data protocol data unit corresponding to the second scheduling priority, uses the acquired The retransmission data PDU generates a second data frame corresponding to the second scheduling priority;

In step D, the step of the MAC-hs entity distributing the retransmission data PDU and the control PDU in the higher scheduling priority data frame to the higher scheduling priority queue includes: the MAC-hs entity will The control protocol data unit carried in the first data frame corresponding to the first scheduling priority is distributed to the queue corresponding to the first scheduling priority in itself, and the retransmission data carried in the second data frame corresponding to the second scheduling priority The protocol data unit is distributed to the queue corresponding to the second scheduling priority in itself.

The first scheduling priority is the highest scheduling priority; the second scheduling priority is the second highest scheduling priority.

The method further includes: pre-adding a type bit for identifying the type of the protocol data unit in the sending request primitive, and setting the control protocol data unit and the retransmission data protocol data unit to correspond to the first type value and the second type value respectively;

In step B, the step of identifying the type information when the RLC entity sends the control PDU and the retransmission data PDU to the MAC-d entity includes: the RLC entity transmits the first request primitive Write the first type value or the second type value on the type bit of the , and send the control protocol data unit and the retransmission data protocol data unit to the MAC-d entity in the first sending request primitive;

In step C, the step of the MAC-d entity generating a data frame with a higher scheduling priority includes: the MAC-d entity selects from the first type value or the second type value carried in the first sending request primitive Get the control protocol data unit and the retransmission data protocol data unit in the sending request primitive, and then use The acquired control protocol data unit and the retransmission data protocol data unit generate a first data frame corresponding to the first scheduling priority or the second scheduling priority;

In step D, the step of the MAC-hs entity distributing the retransmission data PDU and the control PDU in the higher scheduling priority data frame to the corresponding higher priority queue includes: the MAC-hs entity will The control protocol data unit and the retransmission data protocol data unit carried in the first data frame corresponding to the first scheduling priority or the second scheduling priority are distributed to the queue corresponding to the first scheduling priority or the second scheduling priority in itself .

Both the first scheduling priority and the second scheduling priority are the highest scheduling priority.

The method further includes: setting the newly sent data protocol data unit to correspond to the third type value;

In step B, the step of identifying the type information when the radio link control entity sends the new data protocol data unit to the MAC-d entity includes: the radio link control entity writes on the type bit of the third sending request primitive Enter the third type value, and send the newly sent data protocol data unit to the MAC-d entity in the third sending request primitive;

In step C, the step of the MAC-d entity generating a lower scheduling priority data frame using the received new data PDU includes: the MAC-d entity according to the third type carried in the third sending request primitive Obtain the new data PDU from the third sending request primitive, and then according to the set new data PDU corresponding to the third scheduling priority, use the acquired new data PDU to generate the third scheduling priority The third data frame of level;

In step D, the step of the MAC-hs entity distributing the newly sent data protocol data unit in the lower scheduling priority data frame to the corresponding lower scheduling priority queue includes: the MAC-hs entity will receive the first The newly sent data PDU carried in the third data frame of the third scheduling priority is distributed to the queue corresponding to the third scheduling priority in itself.

The method further includes: pre-adding a type bit for identifying the type of the protocol data unit in the sending request primitive, and setting the non-new data protocol data unit and the new data protocol data unit to correspond to different type values;

The step B includes: the radio link control entity writes the type value corresponding to the non-new data protocol data unit on the type bit of a sending request primitive, and carries the non-new data protocol data unit in the sending request primitive In addition, the radio link control entity writes the type value corresponding to the new data protocol data unit in the type bit of another transmission request primitive, and carries the new data transmission protocol data unit in the another transmission request primitive language, and then send the two send request primitives to the MAC-d entity;

In step C, the type information based on the MAC-d entity includes: the type value corresponding to the non-new data protocol data unit written on the type bits in the two sending request primitives and the new data protocol data The type value corresponding to the unit;

Wherein, the non-new data PDU is a control PDU or a retransmission data PDU.

The sending request primitive is a MAC-DATA request primitive or a self-defined request primitive.

The control PDU, the retransmission data PDU and the new data PDU belong to the same service or different services.

Visible, the method that the present invention proposes has the following advantages:

In the present invention, the RLC entity in the RNC identifies the type information when sending new data PDUs, retransmission data PDUs and control PDUs, and accordingly, the MAC-d entity in the RNC generates HS-DSCH data according to the type information frame, the scheduling priority of the HS-DSCH data frame corresponding to the retransmission data PDU and control PDU is higher than that of the HS-DSCH data frame corresponding to the newly transmitted data PDU. Therefore, the MAC-hs entity in the base station Scheduling priority of DSCH data frames, distribute retransmission data PDUs and control PDUs to queues with higher scheduling priority, and distribute new data PDUs to queues with lower scheduling priority, so that MAC-hs entities can prioritize Scheduling and sending retransmission data PDUs and control PDUs, thereby reducing the waiting time for retransmission data PDUs and control PDUs in the MAC-hs entity to be scheduled, avoiding UE call drop and greatly improving the downlink data transmission rate, thereby improving User satisfaction with the operator.

Description of drawings

FIG. 1 is a flow chart of the prior art in which downlink data is carried on the HS-DSCH in a WCDMA system and the downlink data is transmitted in an acknowledgment mode.

Fig. 2 is a flow chart of downlink data being carried on the HS-DSCH in the WCDMA system in Embodiment 1 of the present invention and using an acknowledgment mode to transmit the downlink data.

Fig. 3 is a flow chart of downlink data being carried on the HS-DSCH in the WCDMA system in Embodiment 2 of the present invention and using an acknowledgment mode to transmit the downlink data.

Detailed ways

The core idea of the present invention is: set the scheduling priority of the non-new data PDU to be higher than the scheduling priority of the new data PDU; the RLC entity sends the non-new data PDU and the new data PDU to the MAC-d entity, and identifies its Type information; the MAC-d entity uses the received non-new data PDU to generate a data frame with a higher scheduling priority according to the identified type information and the set scheduling priority, and uses the received new data PDU to generate The data frame of lower scheduling priority, and then the generated data frame is sent to the MAC-hs entity; the MAC-hs entity distributes the non-new data PDU in the received higher scheduling priority data frame to the higher scheduling In the priority queue, distribute the newly sent data PDU in the lower scheduling priority data frame received to the lower scheduling priority queue.

Wherein, the non-new data PDU may be: a control PDU; or, a retransmission data PDU; or, a control PDU and a retransmission data PDU.

In addition, the control PDU, the retransmitted data PDU and the newly transmitted data PDU may belong to the same service, or may belong to different services. That is to say, the present invention can differentiate the scheduling priority for the control PDU and/or retransmission data PDU and new data PDU of the same service, so that the scheduling of the control PDU and/or retransmission data PDU of the same service is prioritized It can also be based on different service types, so that the scheduling priority of control PDUs and/or retransmission data PDUs of any service type is higher than that of new data PDUs of any service type.

In addition, the method for the RLC entity to identify type information is as follows: the RLC entity carries type information of different PDUs in different sending request primitives sent to the MAC-d entity to identify them. Here, the sending request primitive may be an existing MAC-DATA request primitive of the protocol or a self-defined request primitive.

In addition, it should be noted that in the present invention, different service types or the same service type but different service processing priorities correspond to different services described in the present invention.

In order to make the purpose, technical solution and advantages of the present invention clearer, the present invention will be further described in detail below in conjunction with the accompanying drawings and specific embodiments.

In the following embodiments, the non-newly transmitted data PDUs include control PDUs and retransmission data PDUs.

Moreover, in the following embodiments, the present invention reduces the number of retransmitted data PDUs and control PDUs in the MAC- The time spent waiting to be scheduled in the hs entity. For the control PDU and the retransmission data PDU, the present invention can distinguish the scheduling priority between the two, or not distinguish the scheduling priority between the two, that is to say, the control PDU and the retransmission data can be set The scheduling priorities of the PDUs are not equal, and the scheduling priorities of the control PDU and the retransmission data PDU can also be set to be equal.

Example 1:

In this embodiment, the existing MAC-DATA request primitive of the protocol is used as the sending request primitive, and the scheduling priorities of the control PDU and the retransmission data PDU are set to be unequal as an example to illustrate the present invention specific implementation process.

Fig. 2 is a flow chart of downlink data being carried on the HS-DSCH in the WCDMA system in Embodiment 1 of the present invention and using an acknowledgment mode to transmit the downlink data. Referring to Fig. 2, in the present invention, on the HS-DSCH of WCDMA system, the process of adopting confirmation mode to transmit data specifically comprises the following steps:

Step 201: Preset the scheduling priority from high to low of the control PDU, the retransmitted data PDU and the newly transmitted data PDU.

The specific setting process of this step includes:

Firstly, according to the existing method for determining the downlink data scheduling priority of a service, the scheduling priority of the newly sent data PDU of a service is determined.

For example, as shown in Table 1, the scheduling priorities of the new data PDUs of different services with service processing priorities of 6, 7, and 8 in the interactive service are set to the scheduling priorities 9, 9, and 8 from high to low. 8 and 7.

Secondly, the scheduling priority of the retransmission data PDU of a service is set to be higher than that of the new data PDU, and the scheduling priority of the control PDU is higher than the scheduling priority of the retransmission data PDU.

Here, under the condition that the scheduling priority of the control PDU is higher than the scheduling priority of the retransmitted data PDU, the scheduling priority of both can be any scheduling priority higher than the scheduling priority of the newly transmitted data PDU. For example, for a service with a service processing priority of 6 in the interactive service, the scheduling priority of its newly transmitted data PDU is 9, then the scheduling priority of the retransmitted data PDU of this type of service can be set to any of 14 to 10 One, and the scheduling priority of the control PDU of this type of service can be set to any one of 15 to 11, and the scheduling priority of the control PDU is higher than that of the retransmission data PDU. For another example, for a service with a service processing priority of 8 in the interactive service, the scheduling priority of its newly transmitted data PDU is 7, then the scheduling priority of the retransmitted data PDU of this type of service can be set from 14 to 8 Any one, and the scheduling priority of the control PDU of this type of service can be set to any one of 15 to 9, and the scheduling priority of the control PDU is higher than the scheduling priority of the retransmission data PDU.

The specific service implementation process is described below by setting the scheduling priority of the control PDU of any kind of service as 15, and setting the scheduling priority of the retransmission data PDU of any kind of service as 14 as an example. At this time, the scheduling priorities of the newly transmitted data PDU, the retransmitted data PDU and the control PDU set in this step can be shown in Table 2.

business type   Business processing priority Types of RLC PDUs scheduling priority Interactive business 1 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 14 2 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 13 3 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 12 4 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 11 5 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 10 6 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 9 7 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 8 8 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 7 9 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 6 10 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 5 11 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 4 12 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 3 13 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 2 14 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 1 15 control PDU 15 PDU of retransmitted data 14 PDU of newly sent data 0 background business - control PDU 15 - PDU of retransmitted data 14 - PDU of newly sent data 0

Table 2

In Table 2, the business processing priority of 1 has the highest priority, and so on, the business processing priority of 15 has the lowest priority; the scheduling priority of 15 has the highest priority, and so on, the scheduling priority of 0 has the lowest priority.

Step 202: Add a type bit used to indicate the PDU type in the MAC-DATA request primitive in advance, and set the control PDU, retransmission data PDU and new data PDU to correspond to the first type value, the second type value and the first type value respectively. Three types of values.

Here, a type bit for indicating the PDU type is added to the MAC-DATA request primitive, and different types of values corresponding to the newly sent data PDU, retransmitted data PDU, and control PDU are set, so that the subsequent process can use The MAC-d entity distinguishes different types of PDUs according to the type value on the type bit in the MAC-DATA request primitive.

Step 203: When sending downlink data, the RLC entity in the RNC uses three MAC-DATA request primitives, writes the first type value on the type bit of MAC-DATA request primitive 1, and carries the control PDU in the MAC - In the DATA request primitive 1, and write the second type value on the type bit of the MAC-DATA request primitive 2, and carry the retransmission data PDU in the MAC-DATA request primitive 2, and, in the MAC - Write a third type value in the type bit of the DATA request primitive 3, and carry the newly sent data PDU in the MAC-DATA request primitive 3.

Step 204: The RLC entity in the RNC sends each MAC-DATA request primitive carrying the newly transmitted data PDU, the retransmitted data PDU and the control PDU to the MAC-d entity in the RNC.

Step 205: After the MAC-d entity in the RNC receives each MAC-DATA request primitive sent by the RLC entity, obtain each MAC-DATA request primitive according to the type value on the type bit in each MAC-DATA request primitive The control PDU, retransmission data PDU and new data PDU carried in the

Here, since the type bit in the MAC-DATA request primitive 1 is the first type value, such as 01, and the type bit in the MAC-DATA request primitive 2 is the second type value, such as 10, the MAC-DATA request primitive In language 3, the type bit is the third type value, such as 11. Since the control PDU, retransmission data PDU and new data PDU have been preset to correspond to the first type value, the second type value and the third type value respectively, then , the MAC-d entity in the RNC can obtain the control PDU from the MAC-DATA request primitive 1, obtain the retransmission data PDU from the MAC-DATA request primitive 2, and obtain the new transmission PDU from the MAC-DATA request primitive 3 Data PDUs.

Step 206: The MAC-d entity in the RNC determines the scheduling priority of the newly acquired data PDU, retransmitted data PDU and control PDU according to the preset scheduling priorities of the newly transmitted data PDU, retransmitted data PDU and control PDU class.

Here, the MAC-d entity in the RNC determines the scheduling priority of the obtained retransmission data PDU and control PDU as the second highest and the highest, and according to the business type of the newly transmitted data PDU obtained and the newly transmitted data The service processing priority corresponding to the RLC entity of the PDU determines the scheduling priority of the newly sent data PDU.

For example, the MAC-d entity in the RNC obtains the control PDU, retransmission data PDU and newly transmitted PDU from the received MAC-DATA request primitive 1, MAC-DATA request primitive 2 and MAC-DATA request The service types of the data PDU are all interactive services, and the service processing priority corresponding to the RLC entity that sends the new data PDU is 5, then according to the above table 2, the scheduling priority of the currently acquired new data PDU can be determined is 10, the scheduling priority of the currently acquired retransmission data PDU is 14, and the scheduling priority of the currently acquired control PDU is 15.

Step 207: The MAC-d entity generates the first HS-DSCH data frame, the second HS-DSCH data frame and the third HS-DSCH data frame respectively by using the obtained control PDU, retransmission data PDU and new data PDU, and Corresponding scheduling priority information is carried in each HS-DSCH data frame.

Here, the MAC-d entity carries the determined highest scheduling priority information of the control PDU in the first HS-DSCH data frame, such as information with a scheduling priority of 15, and carries the determined information in the second HS-DSCH data frame The second highest scheduling priority information of the retransmitted data PDU, such as information with a scheduling priority of 14, carries the determined scheduling priority information of the newly transmitted data PDU in the third HS-DSCH data frame, such as a scheduling priority of 10 Information.

Step 208: The MAC-d entity sends the first HS-DSCH data frame, the second HS-DSCH data frame and the third HS-DSCH data frame to the MAC-hs entity in the base station.

Step 209: According to the scheduling priority information carried in the received first HS-DSCH data frame, second HS-DSCH data frame and third HS-DSCH data frame, the MAC-hs entity in the base station allocates The control PDU, retransmitted data PDU and newly sent data PDU data in the data frame are distributed to the queue corresponding to the corresponding scheduling priority of the current receiver.

Here, since the scheduling priority carried in the first HS-DSCH data frame is the highest, such as 15, the scheduling priority carried in the second HS-DSCH data frame is the second highest, such as 14, and the scheduling priority carried in the third HS-DSCH data frame The carried scheduling priority is relatively the lowest, such as 10, then the MAC-hs entity in the base station distributes the data in the first HS-DSCH data frame, that is, the control PDU, to itself, and the scheduling priority corresponding to the current receiver is the highest In the queue, such as queue 1, the data in the second HS-DSCH data frame, that is, the retransmission data PDU, is distributed to the queue with the second highest scheduling priority corresponding to the current receiver, such as queue 2 , distributing the data in the third HS-DSCH data frame, that is, the newly transmitted data PDU, to the queue corresponding to the scheduling priority 10 corresponding to the current receiver.

Since then, due to the first HS-DSCH data frame, the control PDU, retransmission data PDU and new transmission data PDU in the second HS-DSCH data frame and the third HS-DSCH data frame have been sequentially distributed to the scheduling priority from high to high Therefore, when the MAC-hs entity in the subsequent base station schedules each queue corresponding to the current receiver, it will sequentially schedule the queue where the control PDU is located, the queue where the retransmission data PDU is located, and the new sender The data PDU is in the queue, so that the retransmission data PDU and control PDU can be sent to the UE first, reducing the time for the retransmission data PDU and control PDU to be scheduled in the MAC-hs entity, avoiding UE drop and greatly improving the downlink data Transmission rate.

Example 2:

In this embodiment, the existing MAC-DATA request primitive of the protocol is used as the sending request primitive, and the scheduling priority of the control PDU and the retransmission data PDU are set as an example to illustrate the present invention The specific implementation process.

Fig. 3 is a flow chart of downlink data being carried on the HS-DSCH in the WCDMA system in Embodiment 2 of the present invention and using an acknowledgment mode to transmit the downlink data. Referring to Fig. 3, in the present invention, the process of adopting the confirmation mode to transmit data on the HS-DSCH of the WCDMA system specifically includes the following steps:

Step 301: Preset the scheduling priority of the retransmitted data PDU and the control PDU to be equal and higher than the scheduling priority of the newly transmitted data PDU.

The specific setting process of this step includes:

Firstly, according to an existing method for determining a service downlink data scheduling priority, that is, according to a service type and a service processing priority of a service, the scheduling priority of a newly sent data PDU of this service is determined.

For example, as shown in Table 1, the scheduling priorities of the new data PDUs of different services with service processing priorities of 6, 7, and 8 in the interactive service are set to the scheduling priorities 9, 9, and 8 from high to low. 8 and 7.

Secondly, set the scheduling priority of the control PDU and the retransmission data PDU of a service to be equal, and be any scheduling priority higher than the scheduling priority of the new data PDU.

For example, for a service with a service processing priority of 6 in the interactive service, the scheduling priority of its new data PDU is 9, then the scheduling priority of the control PDU and retransmission data PDU of this service can be set to be equal, as Any one of scheduling priorities 15 to 10. For another example, for a service with a service processing priority of 8 in the interactive service, the scheduling priority of its new data PDU is 7, then the scheduling priority of the control PDU and the retransmission data PDU of this type of service can be set to be equal. Any one of 15 to 8.

The specific service implementation process is described below by setting the scheduling priorities of the control PDU and the retransmission data PDU of any service to be equal to the highest scheduling priority of 15 as an example.

Step 302: Add a type bit used to indicate the PDU type in the MAC-DATA request primitive in advance, and set the control PDU, retransmission data PDU and new data PDU to correspond to the first type value, the second type value and the first type value respectively. Three types of values.

Step 303: When sending downlink data, the RLC entity in the RNC uses two MAC-DATA request primitives, writes the first or second type value on the type bit of MAC-DATA request primitive 1, and retransmits The data PDU and the control PDU are carried in the MAC-DATA request primitive 1, and the third type value is written in the type bit of the MAC-DATA request primitive 2, and the newly sent data PDU is carried in the MAC-DATA request primitive Language 2.

Here, since the scheduling priority of the retransmission data PDU and the control PDU have been preset to be the same, they correspond to the highest scheduling priority of 15, that is, the retransmission data PDU and the control PDU may not distinguish the scheduling priority in the subsequent sending process, Therefore, the RLC entity in the RNC can write the type value of any one of the retransmission data PDU and the control PDU on the type bit of the MAC-DATA request primitive 1, that is, write the first type value or the second type Any value can be used.

Step 304: the RLC entity in the RNC sends each MAC-DATA request primitive to the MAC-d entity in the RNC.

Step 305: After receiving the MAC-DATA request primitives sent by the RLC entity, the MAC-d entity in the RNC obtains the MAC-DATA request primitive 1 according to the type value on the type bit in each MAC-DATA request primitive The retransmission data PDU and control PDU carried in the MAC-DATA request primitive 2, and obtain the newly sent data PDU carried in the MAC-DATA request primitive 2.

Here, since the type bit of the MAC-DATA request primitive 1 is the first type value or the second type value, the MAC-d entity can know that the MAC-DATA request primitive 1 carries the retransmission data PDU and the control PDUs. Since the type bit of the MAC-DATA request primitive 2 is a third-type value, the MAC-d entity can know that the MAC-DATA request primitive 2 carries a new data PDU.

Step 306: The MAC-d entity in the RNC determines the scheduling priority of the currently acquired new data PDU according to the preset scheduling priorities of the new data PDU, retransmission data PDU and control PDU, and the retransmission data PDU and Controls the scheduling priority of PDUs.

Here, the MAC-d entity in the RNC determines the scheduling priority of the obtained retransmission data PDU and control PDU as the highest, and according to the service type of the obtained new data PDU and the RLC that sent the new data PDU The business processing priority corresponding to the entity determines the scheduling priority of the newly sent data PDU.

Step 307: The MAC-d entity uses the obtained retransmission data PDU and control PDU to generate the first HS-DSCH data frame, and uses the obtained newly transmitted data PDU to generate the second HS-DSCH data, and transmits data on each HS-DSCH The corresponding scheduling priority information is carried in the data frame.

Here, the MAC-d entity carries the determined highest scheduling priority information of retransmitted data PDUs and control PDUs in the first HS-DSCH data frame, and carries the determined newly transmitted data PDUs in the second HS-DSCH data frame Scheduling priority information.

Step 308: The MAC-d entity sends the first HS-DSCH data frame and the second HS-DSCH data frame to the MAC-hs entity in the base station.

Step 309: The MAC-hs entity in the base station transmits the retransmission data in the first HS-DSCH data frame according to the scheduling priority information carried in the received first HS-DSCH data frame and the second HS-DSCH data frame Distribute the PDU and control PDU to the queue with the highest scheduling priority corresponding to the current receiver, and distribute the newly sent data PDU in the second HS-DSCH data frame to the queue with the corresponding scheduling priority corresponding to the current receiver middle.

Afterwards, when the MAC-hs entity in the base station schedules each queue corresponding to the current receiver, it will send the retransmission data PDU and control PDU to the UE at the same time according to the scheduling priority, reducing the number of retransmission data PDUs and control PDUs in the MAC. - The time for waiting to be scheduled in the hs entity, avoiding UE call drop and greatly improving the downlink data transmission rate.

In the above-mentioned embodiment 2, since the set scheduling priorities of the retransmitted data PDU and the control PDU are equal to the highest scheduling priority, no distinction is made between the retransmitted data PDU and the control PDU, that is, the retransmitted data PDU and the control PDU are The control PDU is carried in a MAC-DATA request primitive, and an HS-DSCH data frame is generated by using the retransmission data PDU and the control PDU, so that the retransmission data PDU and the control PDU do not distinguish the priority order of transmission, only for The newly sent data PDU can be sent first.

The specific implementation process of the present invention adopting a self-defined request primitive to carry the retransmission data PDU and the control PDU is the same as the principle of the process described in the above-mentioned embodiment 1 and embodiment 2.

In each of the above embodiments, the control PDU, the retransmission data PDU and the new data PDU belong to the same service, that is to say, the above embodiments describe the control PDU, the retransmission data PDU and the new data PDU for the same service. The scheduling priority of the retransmitted data PDU is higher than that of the newly transmitted data PDU, so that the control PDU and the retransmitted data PDU of the same service are sent out first relative to the newly transmitted data PDU. According to different service types, the present invention makes the scheduling priority of the control PDU and retransmission data PDU of any service type higher than that of the new data PDU of any service type, so that the control PDU and the retransmission data PDU of any service type The process in which the retransmitted data PDU is sent out preferentially relative to the newly transmitted data PDU of any service type is the same as the principle of the process in the foregoing embodiment.

In the above embodiments, the non-newly transmitted data PDUs include control PDUs and retransmission data PDUs. In other embodiments of the present invention, the non-new data PDU may only include one of the control PDU and the retransmission data PDU. It is described as: pre-setting the scheduling priority of non-new data PDUs, that is, control PDUs or retransmission data PDUs, is higher than that of new data PDUs, and adding a type bit used to identify the PDU type in the sending request primitive in advance, setting the control The PDU or retransmission data PDU, and the newly transmitted data PDU correspond to different types of values; when performing the transmission, the RLC entity writes the type value corresponding to the control PDU or the retransmission data PDU on the type bit of a transmission request primitive , and correspondingly carry the control PDU or retransmission data PDU in the send request primitive, and write the type value corresponding to the newly sent data PDU on the type bit of another send request primitive, and carry the newly sent data PDU In this another sending request primitive, then the two sending request primitives are sent to the MAC-d entity; Or the type value corresponding to the retransmission data PDU, and the type value corresponding to the newly sent data PDU, to identify the PDU corresponding to the two sending request primitives, so as to generate different data frames according to the type information and the set scheduling priority , and the process by which the MAC-hs entity distributes PDUs in different data frames to different scheduling priority queues.

In a word, the above descriptions are only preferred embodiments of the present invention, and are not intended to limit the protection scope of the present invention. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present invention shall be included within the protection scope of the present invention.

Claims (13)

1. A method for transmitting data on a downlink, characterized in that the method comprises the following steps: A. Setting the scheduling priority of the non-new data protocol data unit is higher than the scheduling priority of the new data protocol data unit; B. The radio link control entity sends the non-new data PDU and the new data PDU to the MAC-d entity, and identifies its type information at the same time; C. The MAC-d entity uses the received non-new data protocol data unit to generate a data frame with higher scheduling priority according to the identified type information and the set scheduling priority, and uses the received new data protocol The data unit generates a data frame with a lower scheduling priority, and then sends the generated data frame to the MAC-hs entity; D. The MAC-hs entity distributes the non-new data protocol data units in the received higher scheduling priority data frames to the higher scheduling priority queue, and distributes the received lower scheduling priority data frames. The newly sent data PDUs are distributed to queues with lower scheduling priorities. 2. The method according to claim 1, wherein the non-new data PDU comprises: a control PDU and a retransmission data PDU. 3. The method according to claim 2, wherein the step A comprises: according to the business type and business processing priority, setting the newly sent data protocol data unit to correspond to the third scheduling priority, and setting the control protocol data unit The PDU and the retransmission data protocol data unit respectively correspond to a first scheduling priority and a second scheduling priority, wherein the first scheduling priority and the second scheduling priority are any scheduling priority higher than the third scheduling priority. 4. The method according to claim 3, wherein in step A, the first scheduling priority is higher than the second scheduling priority. 5. The method according to claim 3, wherein in step A, the first scheduling priority is equal to the second scheduling priority. 6. The method according to claim 4, further comprising: adding a type bit used to identify the type of the protocol data unit in the sending request primitive in advance, and setting the control protocol data unit and the retransmission data The protocol data units respectively correspond to the first type value and the second type value; In step B, the step of identifying the type information when the RLC entity sends the control PDU and the retransmission data PDU to the MAC-d entity includes: the RLC entity transmits the first request primitive Write the first type value on the type bit of the original language, and carry the control protocol data unit in the first send request primitive, and write the second type value on the type bit of the second send request primitive, and retransmit the data The protocol data unit is carried in the second send request primitive, and then the first send request primitive and the second send request primitive are sent to the MAC-d entity; In step C, the step of the MAC-d entity generating a data frame with a higher scheduling priority includes: the MAC-d entity extracts from the first send request primitive according to the first type value carried in the first send request primitive Obtain the control protocol data unit, and then according to the set control protocol data unit corresponding to the first scheduling priority, use the acquired control protocol data unit to generate the first data frame corresponding to the first scheduling priority, and the MAC-d entity according to The second type value carried in the second sending request primitive obtains the retransmission data protocol data unit from the second sending request primitive, and then according to the set retransmission data protocol data unit corresponding to the second scheduling priority, uses the acquired The retransmission data PDU generates a second data frame corresponding to the second scheduling priority; In step D, the step of the MAC-hs entity distributing the retransmission data PDU and the control PDU in the higher scheduling priority data frame to the higher scheduling priority queue includes: the MAC-hs entity will The control protocol data unit carried in the first data frame corresponding to the first scheduling priority is distributed to the queue corresponding to the first scheduling priority in itself, and the retransmission data carried in the second data frame corresponding to the second scheduling priority The protocol data unit is distributed to the queue corresponding to the second scheduling priority in itself. 7. The method according to claim 4 or 6, wherein the first scheduling priority is the highest scheduling priority; the second scheduling priority is the second highest scheduling priority. 8. The method according to claim 5, further comprising: adding a type bit used to identify the type of the protocol data unit in the sending request primitive in advance, and setting the control protocol data unit and the retransmission data The protocol data units respectively correspond to the first type value and the second type value; In step B, the step of identifying the type information when the RLC entity sends the control PDU and the retransmission data PDU to the MAC-d entity includes: the RLC entity transmits the first request primitive Write the first type value or the second type value on the type bit of the , and send the control protocol data unit and the retransmission data protocol data unit to the MAC-d entity in the first sending request primitive; In step C, the step of the MAC-d entity generating a data frame with higher scheduling priority includes: the MAC-d entity transmits the first type value or the second type value carried in the first sending request primitive from the first Get the control protocol data unit and the retransmission data protocol data unit in the sending request primitive, and then use The acquired control protocol data unit and the retransmission data protocol data unit generate a first data frame corresponding to the first scheduling priority or the second scheduling priority; In step D, the step of the MAC-hs entity distributing the retransmission data PDU and the control PDU in the higher scheduling priority data frame to the corresponding higher priority queue includes: the MAC-hs entity will The control protocol data unit and the retransmission data protocol data unit carried in the first data frame corresponding to the first scheduling priority or the second scheduling priority are distributed to the queue corresponding to the first scheduling priority or the second scheduling priority in itself . 9. The method according to claim 5 or 8, wherein both the first scheduling priority and the second scheduling priority are the highest scheduling priority. 10. The method according to claim 6 or 8, characterized in that the method further comprises: setting the newly sent data protocol data unit to correspond to the third type value; In step B, the step of identifying the type information when the radio link control entity sends the new data protocol data unit to the MAC-d entity includes: the radio link control entity writes on the type bit of the third sending request primitive Enter the third type value, and send the newly sent data protocol data unit to the MAC-d entity in the third sending request primitive; In step C, the step of the MAC-d entity generating a lower scheduling priority data frame using the received new data PDU includes: the MAC-d entity according to the third type carried in the third sending request primitive Obtain the new data PDU from the third sending request primitive, and then according to the set new data PDU corresponding to the third scheduling priority, use the acquired new data PDU to generate the third scheduling priority The third data frame of level; In step D, the step of the MAC-hs entity distributing the newly sent data protocol data unit in the lower scheduling priority data frame to the corresponding lower scheduling priority queue includes: the MAC-hs entity will receive the first The newly sent data PDU carried in the third data frame of the third scheduling priority is distributed to the queue corresponding to the third scheduling priority in itself. 11. The method according to claim 1, further comprising: adding a type bit used to identify the type of the protocol data unit in the sending request primitive in advance, and setting the non-new data protocol data unit and The newly sent data protocol data units correspond to different types of values; The step B includes: the radio link control entity writes the type value corresponding to the non-new data protocol data unit on the type bit of a sending request primitive, and carries the non-new data protocol data unit in the sending request primitive In addition, the radio link control entity writes the type value corresponding to the new data protocol data unit in the type bit of another transmission request primitive, and carries the new data transmission protocol data unit in the another transmission request primitive language, and then send the two send request primitives to the MAC-d entity; In step C, the type information based on the MAC-d entity includes: the type value corresponding to the non-new data protocol data unit written on the type bits in the two sending request primitives and the new data protocol data The type value corresponding to the unit; Wherein, the non-new data PDU is a control PDU or a retransmission data PDU. 12. The method according to claim 6, 8 or 11, wherein the sending request primitive is a MAC-DATA request primitive or a self-defined request primitive. 13. The method according to claim 2, 3, 4, 5, 6, 8 or 11, wherein the control PDU, retransmission data PDU and new data PDU belong to the same type business or a different kind of business.