WO2007112646A1 - Procédé d'ordonnancement mac-e pour canal spécifique amélioré et système associé - Google Patents

Procédé d'ordonnancement mac-e pour canal spécifique amélioré et système associé Download PDF

Info

Publication number
WO2007112646A1
WO2007112646A1 PCT/CN2007/000531 CN2007000531W WO2007112646A1 WO 2007112646 A1 WO2007112646 A1 WO 2007112646A1 CN 2007000531 W CN2007000531 W CN 2007000531W WO 2007112646 A1 WO2007112646 A1 WO 2007112646A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling
mac
transmission
unit
user
Prior art date
Application number
PCT/CN2007/000531
Other languages
English (en)
French (fr)
Inventor
Caijun Zhu
Weidong Zhu
Original Assignee
Huawei Technologies Co., Ltd.
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Huawei Technologies Co., Ltd. filed Critical Huawei Technologies Co., Ltd.
Publication of WO2007112646A1 publication Critical patent/WO2007112646A1/zh

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L47/00—Traffic control in data switching networks
    • H04L47/10—Flow control; Congestion control

Definitions

  • the present invention relates to a scheduling technique in a communication system, and more particularly to a medium access control (MAC-e) scheduling method and system for enhancing a dedicated channel.
  • MAC-e medium access control
  • the 3GPP R6 version introduces High Speed Uplink Packet Access (HSUPA).
  • HSUPA an Enhanced Dedicated Channel (E-DCH) is added, and the User Equipment (UE) transmits uplink data to the base station NodeB through the E-DCH.
  • E-DCH Enhanced Dedicated Channel
  • UE User Equipment
  • MAC Medium Access Control
  • a MAC-e entity and a MAC-es entity are added to each UE that uses the E-DCH, and each NodeB corresponding to the UE is configured with a MAC-e entity in the radio network controller.
  • the Service RNC (SRNC) of the (RNC) is configured with a MAC-es entity.
  • the MAC-e entity located in the NodeB controls the access of the E-DCH, and the MAC-e entity in the NodeB is connected to the MAC-es entity located in the SRNC.
  • the MAC-es entity in the UE and SRNC is further connected to its own dedicated channel media access control (MAC-d) entity.
  • MAC-d media access control
  • the MAC-e entity of the NodeB allocates MAC-e data belonging to one user to one according to the binding relationship.
  • each MAC-d flow establishes an Iub transport bearer.
  • the NodeB sends the data to the RNC:.
  • the data is restored to the MAC-es data according to the binding relationship.
  • the functions related to HSUP A in the NodeB are performed by the MAC-e entity, such as MAC-e scheduling, MAC-e scheduling control, demultiplexing, and hybrid automatic repeat request (HARQ).
  • the MAC-e scheduling function is mainly for allocating E-DCH cell resources to different UEs according to the scheduling request of the UE to perform specific scheduling and allocation; the MAC-e scheduling control function is responsible for receiving scheduling requests and sending and distributing to the E-DCH. Scheduling of each UE.
  • the MAC-e scheduling is controlled by the NodeB and is based on uplink and downlink control signaling and rules that the UE needs to follow according to these control commands. In practical applications, the MAC-e scheduling may be performed for only one user or for multiple users.
  • the system includes: UE11 and NodeB 12.
  • the NodeB 12 includes: an air interface information unit 12a and a MAC-e scheduling unit 12b.
  • the UE 11 sends a scheduling request to the air interface information unit 12a in the NodeB 12, and receives the scheduling command information sent by the MAC-e scheduling unit 12b.
  • the air interface information unit 12a in the NodeB 12 receives the scheduling request sent by the UE 11, and transmits the air interface information to the MAC-e scheduling unit 12b.
  • the MAC-e scheduling unit 12b in the NodeB 12 receives the air interface information transmitted by the air interface information unit 12a, and transmits scheduling command information to the UE 11.
  • the system shown in FIG. 1 may be directed to one user or multiple users, wherein, if for one user, the UE 11 refers to a certain user, the air interface information unit 12a, and the MAC-e scheduling unit 12b. For the user, if for a plurality of users, the UE 11 refers to a plurality of users, and the air interface information unit 12a and the MAC-e scheduling unit 12b are also for a plurality of users.
  • 2 is a schematic diagram of a process of performing MAC-e scheduling in the prior art, where the process includes: Step 201: MAC-e scheduling starts.
  • the MAC-e scheduling may be for one user or for multiple users.
  • Step 202 Perform MAC-e scheduling on the user according to the air interface resource information.
  • the step of performing MAC-e scheduling on the user according to the air interface resource information is as follows:
  • the MAC-e scheduling schedules the HSUPA user according to the information of the air interface resource, the uplink signaling of the user, and the quality of service (QoS) requirement, specifically:
  • the NodeB estimates the margin of the air interface load according to the difference between the received total bandwidth power (RTWP) value obtained by the self measurement and the RTWP target value configured by the SRNC, and then according to the scheduling request from the UE, the QoS-related information obtained from the SRNC, the service
  • the priority and other information allocates load margin to the UE, and implements the scheduling behavior based on the air interface load.
  • the RTWP value is a measurement value specified by the 3GPP, and can be used to measure the load status of the uplink cell, where the RTWP target value is an RTWP value configured by the SRNC.
  • the best scheduling result is that the measured RTWP measurement value of the cell is consistent with the RTWP target value.
  • step 202 the user is subjected to MAC-e scheduling. If the MAC-e scheduling in step 201 is for multiple users, then step 202 is Perform MAC-e scheduling for each user separately.
  • Step 203 End MAC-e scheduling according to the constraint of the air interface load.
  • the scheduling authorization includes two types, one is an absolute grant (AG), the AG provides an upper limit of the uplink maximum power resources available to the UE, and the other is a relative grant (RG), which is used to indicate the power resources used by the UE in the previous scheduling. Increase or decrease a relative value based on the basis.
  • the UE sends data to the NodeB according to the AG or RG received from the NodeB and according to the information of the cached data, the maximum transmit power limitation of the UE, and the like.
  • the 3GPP R6 has developed the following mechanism:
  • the SRNC detects the uplink data transmission frame sent by the NodeB. If an uplink is found on a certain FP bearer, If the data is lost or the delay is too large, a congestion indication is sent to the NodeB, and the NodeB is instructed to control the transmission of the uplink data on the FP bearer.
  • the FP bearer is an Iub bearer resource allocated to a certain user between the NodeB and the SRNC.
  • FIG. 3 is a schematic diagram of a system in which an RNC sends a transmission congestion indication to a NodeB in the prior art.
  • the system includes: an odeB3 RNC32, where the NodeB 31 includes: a congestion indication receiving unit 31c.
  • the congestion indication receiving unit 31c in the NodeB 31 receives the transmission congestion indication transmitted by the RNC 32.
  • the RNC 32 transmits a transmission congestion indication to the congestion indication receiving unit 31c.
  • the congestion indication receiving unit 31c shown in Fig. 3 may be for one user or for a plurality of users.
  • the congestion indication receiving unit included in the NodeB shown in FIG. 3 is independent of the air interface information unit and the MAC-e scheduling unit included in the NodeB shown in FIG.
  • the MAC-e scheduling algorithm based on the air interface load only considers the air interface load resources in the NodeB cell, but the maximum traffic of the single user in the uplink direction of the HSUPA user can be as high as 5.76 Mbps, showing a strong burst, in actual system applications.
  • the bandwidth of the Iub interface transmission bandwidth is limited. If the NodeB does not consider the allocation and control of the Iub transmission bandwidth resources during MAC-e scheduling, in the case of limited transmission bandwidth configuration, uplink transmission congestion is likely to occur and data loss is caused. If the delay is too large, the transmission quality is affected, and the QoS of the transmission cannot be guaranteed.
  • the RNC feeds back a congestion indication to the Node, instructing the NodeB to control the transmission of the uplink data on the FP bearer.
  • the result of the scheduling may be that the user is required to continue to speed up or slow down or maintain. If the result of the scheduling is the speed increase, the uplink data received by the NodeB will be more. However, it is necessary to reduce the data sent to the RNC, which may easily cause the NodeB to be overburdened.
  • the main purpose of the embodiments of the present invention is to provide a MAC-e scheduling method, which can reduce data loss, reduce transmission delay, and improve transmission quality.
  • Another main object of the embodiments of the present invention is to provide a MAC-e scheduling system, which can reduce data loss, reduce transmission delay, and improve transmission quality.
  • a medium access control MAC-e scheduling method for enhancing a dedicated channel includes the following steps when performing MAC-e scheduling:
  • step B degree command.
  • the occurrence of the abnormal condition is: transmission congestion occurs;
  • step A The judgment in step A is: determining whether there is a transmission congestion of the user, and if so, an abnormal condition occurs in the uplink transmission; otherwise, the uplink transmission does not have an abnormal condition;
  • the step B is: sending a deceleration MAC-e scheduling command to a user who has experienced transmission congestion;
  • Step B further includes the step CI 1 :
  • Step B and step CI 1 further include: determining whether a user receives the congestion release indication, and if not, executing the step Cl l, otherwise stopping sending the speed reduction scheduling command to the user having the transmission congestion, performing step C1 .
  • the occurrence of the abnormal condition is: the data cache is too large;
  • step A The judgment in step A is: determining whether the user data buffer is too large, and if so, the uplink transmission has an abnormal condition; otherwise, the uplink transmission does not have an abnormal condition;
  • the step B is: sending a MAC-e scheduling command for slowing down the user on the transmission port where the data buffer is too large;
  • Step B further includes: performing MAC-e scheduling on users that are not part of the data cache excessive transmission port.
  • Step A includes: Presetting the data cache threshold
  • step A The judgment in step A is performed based on the result of comparing the comparison data buffer value with the cache threshold.
  • the occurrence of the abnormal condition is: a transmission port in which the uplink traffic exceeds the configured Iub transmission port bandwidth after scheduling;
  • Step A further includes: performing MAC-e scheduling on the user, and calculating uplink traffic of the scheduled transmission port;
  • the determination in step A is: determining whether there is a transmission port whose uplink traffic exceeds the bandwidth of the configured Iub transmission port after scheduling, and if yes, the uplink transmission has an abnormal condition; otherwise, the uplink transmission does not have an abnormal condition;
  • the step B is: determining whether the uplink traffic exceeds the bandwidth of the configured Iub transmission port, and if there is a user whose scheduling result is the acceleration rate, if yes, the scheduling result of the scheduling user is modified to the speed reduction MAC- e scheduling command or maintaining speed MAC-e scheduling command; otherwise, ending the MAC-e scheduling process.
  • Step C11 further includes: Cl ll, determine whether the user data cache is too large, if yes, proceed to step C112, otherwise perform step C113;
  • step CI 1 is specifically step C113:
  • Step C113 further includes:
  • step C22 Determine whether there is a transmission port whose uplink traffic exceeds the configured Iub transmission port bandwidth after scheduling, if yes, execute step C23; otherwise, terminate the MAC-e scheduling process;
  • step C23 Determine whether there is a user whose scheduling result is a speed increase on the transmission port whose uplink traffic exceeds the configured Iub transmission port bandwidth. If yes, execute step C24; otherwise, terminate the MAC-e scheduling process;
  • the method further includes: performing MAC-e scheduling on the user.
  • a MAC-e scheduling system includes: a user equipment UE, an air interface information unit, and a NodeB of a MAC-e scheduling unit, where the UE sends a scheduling request to the air interface information unit; the air interface information unit sends the air interface information to the MAC-e scheduling unit, NodeB Further comprising: an uplink transmission detecting unit;
  • the uplink transmission detecting unit is configured to send uplink transmission information to the MAC-e scheduling unit, and the MAC-e scheduling unit is configured to send a MAC-e scheduling command for slowing down or maintaining the speed to the UE according to the received uplink transmission information.
  • the uplink transmission detecting unit is composed of a congestion indication receiving unit and/or a lub information unit
  • the system further comprises: a radio network controller RNC;
  • the congestion indication receiving unit receives the transmission congestion information sent by the RNC, and sends the transmission congestion information to the MAC-e scheduling unit; the MAC-e scheduling unit sends the deceleration MAC-e scheduling command to the UE according to the received transmission congestion information;
  • the lub information unit receives the lub transmission port information sent by the RNC, and sends the lub transmission port information to the MAC-e scheduling unit; the MAC-e scheduling unit sends the MAC-e of the deceleration or the maintenance speed to the UE according to the received lub transmission port information. Schedule commands.
  • the uplink transmission detecting unit includes: a cache unit;
  • the buffer unit receives the user data sent by the air interface information unit, and sends the data buffer excessive information to the MAC-e scheduling unit.
  • the MAC-e scheduling unit sends the slowdown MAC-e scheduling command to the UE according to the received data buffer excessive information.
  • the uplink traffic may be controlled in advance by using the lub transmission port with the uplink traffic exceeding the configuration, thereby avoiding data loss or delay caused by single user congestion or excessive data buffering of the lub interface. Large, which in turn improves transmission quality and guarantees QoS for lub transmission.
  • the user who experiences the transmission congestion is decelerated by the MAC-e scheduling, and the transmission congestion state of the corresponding user can be effectively and quickly cancelled, thereby avoiding data loss or excessive delay, thereby improving the transmission quality.
  • the user who has an excessive cache is slowed down by MAC-e scheduling, and the cached state of the corresponding user can be quickly and effectively cancelled, thereby avoiding data loss or excessive delay, thereby improving transmission quality.
  • the MAC-e scheduling of the NodeB can limit the transmission power of the user, and the available transmit power of the user directly affects the data transmission thereof, that is, the NodeB can limit the data transmission traffic of the UE through the MAC-e scheduling of the NodeB.
  • the NodeB by utilizing this feature of the HSUPA, combined with the information such as the transmission bandwidth and the traffic of the Iub transmission port detected by the NodeB, the NodeB can perform scheduling on the user according to the available Iub transmission bandwidth resources, and can fully utilize the transmission bandwidth.
  • FIG. 1 is a schematic diagram of a system for performing MAC-e scheduling in the prior art
  • FIG. 2 is a schematic diagram of a process of performing MAC-e scheduling in the prior art
  • FIG. 3 is a schematic diagram of a system in which an RNC sends a transmission congestion indication to a NodeB in the prior art
  • FIG. 4 is a schematic diagram of a system for MAC-e scheduling in Embodiment 1 of the present invention.
  • FIG. 5 is a schematic diagram of a process of MAC-e scheduling according to Embodiment 1 of the present invention.
  • FIG. 6 is a schematic diagram of a system for MAC-e scheduling in Embodiment 2 of the present invention.
  • FIG. 7 is a schematic diagram of a process of MAC-e scheduling in Embodiment 2 of the present invention.
  • FIG. 8 is a schematic diagram of a system for MAC-e scheduling in Embodiment 3 of the present invention.
  • FIG. 9 is a schematic diagram of a process of MAC-e scheduling in Embodiment 3 of the present invention.
  • FIG. 10 is a schematic diagram of a system for MAC-e scheduling in Embodiment 4 of the present invention.
  • FIG. 11 is a schematic diagram of a process of MAC-e scheduling in Embodiment 4 of the present invention. Mode for carrying out the invention
  • the MAC-e scheduling when performing MAC-e scheduling, it is determined whether an abnormal condition occurs in the uplink transmission, and if it occurs, a MAC-e scheduling command for slowing down or maintaining the speed is sent to the user according to the abnormal situation that occurs.
  • the MAC-e scheduling may be for one user or for multiple users, where, if for one user, the user that is sent to the user refers to a certain user, and if for multiple users, The user who is speaking to the user is one user or multiple users, as is the case in the following text.
  • the occurrence of the abnormal condition refers to a situation in which data loss or excessive delay may occur, such as a transmission congestion, an excessive data buffer, and a transmission port whose uplink traffic exceeds the configured Iub transmission port bandwidth after scheduling. One or more of them.
  • the MAC-e scheduling system in the embodiment of the present invention further includes: an uplink transmission detecting unit, where the uplink transmission detecting unit sends uplink transmission information to the MAC-e scheduling unit, and the MAC-e scheduling unit receives the uplink transmission information according to the unit.
  • the uplink transmission information sends a scheduling command for slowing down or maintaining the speed to the UE.
  • the uplink transmission detecting unit is: a unit for detecting an uplink transmission state, for example, one or more of a congestion indication receiving unit, a buffer unit, and an Iub information unit; and the uplink transmission information is: information related to an uplink transmission status, For example: one or more of transmission congestion information, data cache oversized information, and Iub transmission port information.
  • the UE, the uplink transmission detecting unit, the MAC-e scheduling unit, the congestion indication receiving unit, the buffer unit, the Iub information unit, and the air interface information unit described in the following herein may be for one user or for multiple users. .
  • the uplink transmission detecting unit is: a congestion indication receiving unit; and the uplink transmission information is: transmitting congestion information.
  • the occurrence of an abnormal condition in the embodiment means that: transmission congestion occurs.
  • FIG. 4 is a schematic diagram of a system for MAC-e scheduling in the embodiment, where the system includes: UE41,
  • NodeB42 RNC43 wherein the NodeB 42 includes: an air interface information unit 42a, a MAC-e scheduling unit 42b, and a congestion indication receiving unit 42c.
  • the UE 41 sends a scheduling request to the air interface information unit 42a in the NodeB 42 to receive the scheduling command information sent by the MAC-e scheduling unit 42b.
  • the air interface information unit 42a in the NodeB 42 receives the scheduling request sent by the UE 41, and transmits the air interface information to the MAC-e scheduling unit 42b.
  • the MAC-e scheduling unit 42b in the NodeB 42 receives the air interface information transmitted by the air interface information unit 42a, receives the transmission congestion information transmitted by the congestion indication receiving unit 42c, and transmits the scheduling command information to the UE 41.
  • the congestion indication receiving unit 42c in the NodeB 42 receives the transmission congestion information transmitted by the RNC 43 and transmits the transmission congestion information to the MAC-e scheduling unit 42b.
  • the RNC 43 transmits transmission congestion information to the congestion indication receiving unit 31c.
  • FIG. 5 is a schematic diagram of a process of MAC-e scheduling in the embodiment, where the process includes the following steps:
  • Step 501 The same as step 201.
  • Step 502 The MAC-e scheduling unit determines whether a user has transmission congestion. If yes, step 503 is performed; otherwise, step 504 is performed.
  • the determining in step 502 may be performed according to the congestion indication information sent by the congestion indication receiving unit to the MAC-e scheduling unit, and the MAC-e scheduling unit may determine, according to the received information, which user has transmission congestion.
  • the congestion indication receiving unit usually receives the transmission congestion indication from the SRNC in the RNC.
  • the uplink transmission is performed.
  • the SRNC in the RNC can send a transmission congestion indication to the NodeB, such as a TNL CONGESTION INDICATION control frame.
  • the frame structure of the TNL CONGESTION INDICATION can be as described in the 3GPP TS 25.427 V6.4.0 (2005-09) protocol. TNL CONGESTION in the agreement
  • the INDICATION control frame can use the Congestion Status parameter to indicate the transmission congestion status on the corresponding transmission bearer, for example: 0 means no congestion; 1 means reservation; 2 means congestion caused by transmission delay; 3 means lost Congestion caused by frames.
  • the RNC after detecting the transmission congestion, the RNC sends the TNL CONGESTION INDICATION control frame to the NodeB to indicate that the RNC detects the transmission congestion.
  • the Congestion Status parameter can be 1 or 2; after the congestion is removed, the RNC also sends the NodeB to the NodeB.
  • the TNL CONGESTION INDICATION control frame is sent to indicate that the congestion is released.
  • the Congestion Status parameter can be 0.
  • Step 503 The MAC-e scheduling sends a scheduled command for slowing down the user who has experienced transmission congestion.
  • MAC-e scheduling can reduce the uplink data transmission rate of the user, thereby reducing or eliminating uplink transmission congestion.
  • step 504 may be directly performed, or the MAC-e scheduling unit may first determine whether the user receives the congestion release indication sent by the RNC. If not, execute step 504, otherwise stop the user from receiving the congestion cancellation indication. After the sent spin-down scheduling command is sent, step 504 is performed. For example, if the NodeB receives the TNL CONGESTION INDICATION control frame of each user and indicates that congestion is generated, the NodeB forcibly sends a scheduling command for deceleration to such users during the MAC-e scheduling from the current time until receiving the RNC. The issued TNL CONGESTION INDICATION control frame and indicates that the congestion is released.
  • Step 504 Perform MAC-e scheduling on the user that does not have transmission congestion according to the air interface resource information.
  • Step 504 is substantially the same as step 202, except that if step 503 is performed before step 504, only the user who does not experience transmission congestion is scheduled for MAC-e scheduling in step 504.
  • Step 505 The same as step 203.
  • Example 2 The same as step 203.
  • the uplink transmission detecting unit is: a buffer unit; and the uplink transmission information is: the data buffer is too large.
  • the abnormal condition described in this embodiment refers to: The data cache is too large.
  • FIG. 6 is a schematic diagram of a system for MAC-e scheduling in the embodiment, where the system includes: a UE 41 and a NodeB 42.
  • the NodeB 42 includes an air interface information unit 42a, a MAC-e scheduling unit 42b, and a buffer unit 42d.
  • UE41 is the same as described in FIG.
  • the air interface information unit 42a receives the scheduling request sent by the UE 41, transmits the air interface information to the MAC-e scheduling unit 42b, and receives the user data transmitted by the UE 41, and transmits the data to the buffer unit 42d.
  • the MAC-e scheduling unit 42b receives the air interface information sent by the air interface information unit 42a, receives the data buffer oversized information sent by the buffer unit 42d, and transmits the scheduling command information to the UE 41.
  • the buffer unit 42d receives the user data transmitted by the air interface information unit 42a, and transmits the data buffer oversized information to the MAC-e scheduling unit 42b.
  • FIG. 7 is a schematic diagram of a process of MAC-e scheduling in the embodiment, where the process includes the following steps:
  • Step 701 The same as step 501.
  • Step 702 The MAC-e scheduling unit determines whether the user data cache is too large. If yes, step 703 is performed; otherwise, step 704 is performed.
  • the determining in step 702 may be performed according to the data cached by the cache unit to the MAC-e scheduling unit, and the MAC-e may determine that the data cache is too large according to the received information and the Iub transmission port information used by the user.
  • the user corresponding to the data carried in the Iub transport port.
  • NodeB usually It will provide a certain amount of uplink data buffering capability of the lub transmission port.
  • the NodeB buffers the data that cannot be sent out in time to the buffer, that is, the buffer unit, so as to be effective. Avoid data loss when bursting with peak data.
  • the uplink data buffer of the NodeB can be implemented by providing a data buffer on each lub transmission port or by other means. In actual application, the NodeB can periodically detect the buffer of the uplink lub transmission port. As for the lub transmission port information used by the user, when the HSUPA user accesses the NodeB, the RNC notifies the NodeB to establish the transmission bearer information used by the user, including the lub transmission port used by the service.
  • the cache value may be compared with a preset threshold.
  • the size of the threshold may be set according to the delay size and buffer size that the integrated transmission service can accept. The size of the specific threshold does not affect the implementation of the process described in this embodiment.
  • Step 703 The MAC-e schedule sends a scheduling command to the user on the excessively large lub transmission port.
  • step 704 may be directly performed, or the MAC-e scheduling unit may first determine whether the data in the buffer is sent. If not, execute step 704. Otherwise, cancel the slow-down scheduling of the user with too large data cache. After the command, step 704 is performed.
  • the NodeB can always maintain the monitoring of the transmission buffer. If it finds that there is too much data buffer in the buffer corresponding to a certain lub transmission port, such as exceeding a set threshold, it means that the NodeB transmits the transmission capability of the lub transmission port. The request for the data transmission cannot be met. After the cache exception occurs, the MAC-e entity sends a deceleration command to the HSUPA user using the transmission port when the scheduling is performed, and controls the UE to reduce the uplink data transmission rate.
  • Step 704 Perform MAC-e scheduling on the user that does not belong to the data cache oversized lub transmission port according to the air interface resource information.
  • Step 704 is substantially the same as step 202, except that if step 703 is performed before step 704, then only MAC-e scheduling for users that do not have excessive data buffering is performed in step 704.
  • Step 705 Same as step 505.
  • the uplink transmission detecting unit is: a lub information unit, and the uplink transmission information is: lub transmission port information.
  • the occurrence of the abnormal condition in the embodiment refers to: a transmission port in which the uplink traffic exceeds the configured lub transmission port bandwidth after scheduling.
  • FIG. 8 is a schematic diagram of a system for MAC-e scheduling in the embodiment.
  • the system includes: UE41, NodeB42, and RNC43.
  • the NodeB42 includes: an air interface information unit 42a, a MAC-e scheduling unit 42b, and a lub information unit 42e.
  • the UE 41 and the air interface information unit 42a are the same as those described in FIG.
  • the MAC-e scheduling unit 42b receives the air interface information transmitted by the air interface information unit 42a, receives the lub transmission port information transmitted by the lub information unit 42e, and transmits scheduling command information to the UE 41.
  • the lub information unit 42e receives the lub transmission port information transmitted by the RNC, and transmits the lub transmission port information to the MAC-e scheduling unit 42b.
  • the RNC 43 transmits lub transmission port information to the lub information unit 42e.
  • FIG. 9 is a schematic diagram of a process of MAC-e scheduling in the embodiment, where the process includes the following steps:
  • Step 901 The same as step 501.
  • Step 902 Perform MAC-e scheduling on the user according to the air interface resource information, and calculate uplink traffic of the transmission port after scheduling.
  • Step 902 Perform VIAC-e scheduling on the user according to the air interface resource information, which is the same as step 202.
  • the NodeB can predict the maximum uplink sending data rate of the UE being scheduled by the NodeB according to the scheduling result, and combine each user with the scheduling command of the HSUPA user that is already in the NodeB.
  • the Iub transport port configuration used can calculate the upstream traffic on all Iub transport ports configured by the NodeB.
  • the RNC notifies the NodeB to establish the transmission bearer information used by the user, including the Iub transmission port and bandwidth used by the service.
  • step 902 after scheduling a user, the uplink traffic after scheduling by the user is calculated, and according to the uplink traffic of each user, the total uplink traffic of all users in each Iub transmission port can be calculated.
  • Step 903 The MAC-e scheduling unit determines whether there is a transmission port whose scheduled uplink traffic exceeds the configured Iub transmission port bandwidth. If yes, step 904 is performed; otherwise, step 906 is performed.
  • the determining in step 903 may be performed according to the Iub transmission port information sent by the Iub information unit to the MAC-e scheduling unit, and the MAC-e scheduling unit may determine, according to the received information, whether the maximum uplink traffic of each Iub transmission port will exceed The maximum bandwidth of the configured Iub transport port.
  • the Iub transport port information includes: The maximum bandwidth allowed by the Iub transport port. The maximum allowed bandwidth is usually configured when the base station is established.
  • the configured information includes: an Iub transmission port used between the NodeB and the RNC, and a bandwidth resource configured by each Iub transmission port, and configured. The information is relatively fixed and will not change unless the Iub transport port bandwidth configuration is modified.
  • Step 904 The MAC-e scheduling unit determines whether the excess transmission port in step 903 has a user whose scheduling result is a speed increase. If yes, step 905 is performed, otherwise step 906 is performed.
  • Step 905 Modify the scheduling result to be a scheduling command of the speed increasing user.
  • the scheduling command for modifying the speed increase in step 905 may be to modify the scheduling command to maintain speed or slow down.
  • the target of modifying the scheduling command in step 905 may be: The uplink traffic of the lub transmission port after scheduling does not exceed the configured lub transmission port bandwidth.
  • Step 4 ⁇ 906 Same as step 505.
  • the abnormal condition of the uplink transmission may be: one or more of a situation that the transmission congestion occurs, the data buffer is too large, and the uplink traffic exceeds the configured transmission bandwidth of the lub transmission port after scheduling.
  • This embodiment is a combination of the three schemes described in each of Embodiments 1 to 3, and the combined system is as shown in FIG.
  • the system includes: UE41, NodeB42, and RNC43.
  • the NodeB42 includes: an air interface information unit 42a, a MAC-e scheduling unit 42b, a congestion indication receiving unit 42c, and a buffer unit 42d. , lub information unit 42e.
  • the UE 41 sends a scheduling request to the air interface information unit 42a in the NodeB 42 to receive the scheduling command information sent by the MAC-e scheduling unit 42b.
  • the air interface information unit 42a in the NodeB 42 receives the scheduling request sent by the UE 41, receives the user data sent by the UE 41, and transmits the data to the buffer unit 42d, and sends the air interface information to the MAC-e scheduling unit 42b.
  • the MAC-e scheduling unit 42b in the NodeB 42 receives the air interface information sent by the air interface information unit 42a, receives the transmission congestion indication sent by the congestion indication receiving unit 42c, and receives the data buffer oversized information sent by the buffer unit 42d, and transmits the received lub information unit 42e.
  • the lub transmits the port information, and sends scheduling command information to the UE41.
  • the congestion indication receiving unit 42c in the NodeB 42 receives the transmission congestion indication transmitted by the RNC 43 and transmits a transmission congestion indication to the MAC-e scheduling unit 42b.
  • the buffer unit 42d receives the user data transmitted by the air interface information unit 42a, and transmits the data buffer excessive information to the MAC-e scheduling unit 42b.
  • the lub information unit 42e receives the lub transmission port information transmitted by the RNC, and transmits the lub transmission port information to the MAC-e scheduling unit 42b.
  • the RNC 43 transmits a transmission congestion indication to the congestion indication receiving unit 31c, and transmits lub transmission port information to the lub information unit 42e.
  • FIG. 11 is a combination thereof.
  • the process shown in FIG. 11 includes the following steps:
  • Steps 1101 to 1103 are the same as steps 501 to 503. After step 503, MAC-e scheduling is performed on other users according to the air interface resource information. After step 1103 is performed, step 1104 is performed.
  • Steps 1104 to 1105 are the same as steps 702 to 703. After step 703, MAC-e scheduling is performed on other users according to the air interface resource information. After step 1105 is performed, step 1106 is performed.
  • Steps 1106 to 1110 The same as step 902 to step 906, except that in step 1106, MAC-e scheduling is performed on users that do not have transmission congestion and are not in the cached excessive transmission port, and the uplink of each transmission port after scheduling is calculated. flow.
  • Embodiments 1 to 3 can perform a reasonable combination of two or three, for example, one scheme after the combination of the three schemes provided in Embodiment 4, and others Reasonable combinations are all within the scope of the present invention and will not be described in detail herein.
  • the uplink transmission detecting unit may be one or more of the congestion indication receiving unit, the buffer unit, and the lub information unit, and may also be other units for detecting the uplink transmission status.
  • the uplink transmission information may be: transmitting congestion information, number Other information may be used in addition to one or more of the cached oversized information and the lub transmission port information.
  • the occurrence of the abnormal condition may be: one or more of a situation in which transmission congestion occurs, the data buffer is too large, and the uplink traffic exceeds the configured transmission bandwidth of the lub transmission port after the scheduling, It can also be a situation where other data may be lost or the delay is too large.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)
  • Small-Scale Networks (AREA)

Description

一种增强专用信道的媒体接入控制调度方法和系统 相关申请的交叉引用
本申请要求申请号为 200610067077.6, 申请曰为 2006.3.31的中国 申请的优先权， 该中国申请作为参考被并入到本申请中。 技术领域
本发明涉及一种通信系统中的调度技术，特别涉及一种增强专用 信道的媒体接入控制 （ MAC-e )调度方法和系统。 发明背景
3GPP R6版本引入了高速上行分组接入（HSUPA ) , HSUPA中， 新增了增强专用信道 （E-DCH ) ， 用户设备（UE ) 通过 E-DCH向基 站 NodeB发送上行数据。 为了支持 HSUPA, 在媒体接入控制 （MAC ) 层增加了一个新的 MAC-e实体和一个新的 MAC-es实体。 具体地说： 给每一个使用 E-DCH的 UE中都增加了 MAC-e实体和 MAC-es实体， 该 UE对应的每个 NodeB配置了一个 MAC-e实体， 在无线网络控制器
( RNC ) 的服务 RNC(SRNC)配置了一个 MAC-es实体。 位于 NodeB中 的 MAC-e实体控制 E-DCH的接入， NodeB中的 MAC-e实体连接到位于 SRNC中的 MAC-es实体。 UE和 SRNC中的 MAC-es实体进一步连接到 自身的专用信道媒体访问控制（MAC-d )实体。 MAC-e实体和 MAC-es 实体之间执行数据传送时，把用户中的多个逻辑信道的数据绑定在一 个 MAC-d 流上进行传送， 具体的绑定关系由 SRNC决定， 并通知 NodeB。 例如： 在 UTRAN侧， NodeB的 MAC-e实体接收到发自 UE的 数据后，根据绑定关系把属于一个用户的 MAC-e数据分配在一个或者 几个 MAC-d流上， 每个 MAC-d 流会建立一个 Iub传输承载， 通过建立 好的传输承载， NodeB把数据发送给 RNC：。 RNC接收后再根据绑定关 系把数据恢复为 MAC-es的数据。
NodeB中与 HSUP A相关的功能由 MAC- e实体执行， 比如： MAC-e 调度、 MAC- e调度控制、 解复用、 混合自动重传请求 （HARQ )等功 能。 其中， MAC-e调度功能主要是根据 UE的调度请求， 为不同 UE分 配 E-DCH小区资源来进行具体的调度分配； MAC-e调度控制功能负责 接收对 E-DCH的调度请求和发送分配给各 UE的调度。 所述 MAC-e调 度由 NodeB控制，并基于上下行控制信令以及 UE根据这些控制命令需 要遵循的规则。 实际应用时， 所述 MAC-e调度可以是只针对一个用户 进行， 也可以针对多个用户进行。
图 1为现有技术中进行 MAC-e调度的系统示意图， 该系统包含： UE11、 NodeB 12, 其中 NodeB 12包含： 空口信息单元 12a、 MAC-e调 度单元 12b。
UE11 , 向 NodeB12中的空口信息单元 12a发送调度请求， 接收 MAC- e调度单元 12b发送的调度命令信息。
NodeB12中的空口信息单元 12a, 接收 UE11发送的调度请求， 向 MAC-e调度单元 12b发送空口信息。
NodeB 12中的 MAC-e调度单元 12b, 接收空口信息单元 12a发送的 空口信息， 向 UE11发送调度命令信息。
图 1中所示系统可以指针对一个用户， 也可以针对多个用户， 其 中， 如果针对一个用户时， 则所述 UE11是指某个用户、 所述空口信 息单元 12a、 MAC-e调度单元 12b是针对该用户而言， 如果针对多个用 户， 则所述 UE11是指多个用户、 所述空口信息单元 12a、 MAC-e调度 单元 12b也是针对多个用户而言。 图 2为现有技术中进行 MAC-e调度的过程示意图， 该过程包含： 步驟 201 : MAC-e调度开始。
所述 MAC-e调度，可以是针对一个用户 ,也可以是针对多个用户。 步骤 202: 根据空口资源信息对用户进行 MAC-e调度。
步骤 202所述根据空口资源信息对用户进行 MAC-e调度是指： MAC-e调度根据空口资源、 用户的上行信令、 服务质量（QoS )要求 等信息对 HSUPA用户进行调度， 具体地说： NodeB根据自身测量获得 的接收总带宽功率（ RTWP )值和 SRNC配置的 RTWP目标值的差值估 计空口负载的余量， 然后根据来自 UE的调度请求、 从 SRNC获得的与 QoS有关的信息、 业务优先级等信息给 UE分配负载余量， 实现基于空 口负载的调度行为。 所述 RTWP值是 3GPP规定的一种测量值， 能够用 来衡量上行小区的负载状况， 所述 RTWP目标值是 SRNC配置的一个 RTWP值。 NodeB 执行上行 MAC-e调度时， 最佳的调度结果是调度后 的小区 RTWP测量值与 RTWP目标值保持一致。
如果步骤 201中所述 MAC-e调度是针对一个用户，则步驟 202中就 是对该用户进行 MAC-e调度， 如果步骤 201中所述 MAC-e调度是针对 多个用户， 则步骤 202中就是对分别对每个用户进行 MAC-e调度。
步骤 203: 根据空口负载的约束结束 MAC-e调度。
在 NodeB中， MAC-e实体进行具体的调度分配后， 通过调度授权 将 UE最大可用的上行资源通知给该 UE。 调度授权包括两种类型， 一 个是绝对授权（ AG )， AG提供了 UE可用的上行最大功率资源的上限； 另一个是相对授权（RG ) , RG用以表示 UE在前一调度使用的功率资 源基础上增加或减少一个相对值。 UE根据从 NodeB接收的 AG或 RG, 并根据自身緩存数据状况， UE的最大发射功率限制等信息向 NodeB 发送数据。 为了避免连接 NodeB和 RNC的 Iub传输端口频繁出现拥塞导致数 据包丟失或者时延过大， 3GPP R6制订了以下机制： SRNC检测 NodeB 发送的上行数据传输帧，如果在某个 FP承载上发现有上行数据丟失或 者时延过大， 则向 NodeB发传输拥塞指示， 指示 NodeB控制该 FP承载 上上行数据的发送。 所述 FP承载是 NodeB和 SRNC之间给某一用户分 配的 Iub承载资源。
图 3为现有技术中 RNC向 NodeB发送传输拥塞指示的系统示意 图， 该系统包含： odeB3 RNC32, 其中， NodeB31包含： 拥塞指 示接收单元 31c。
NodeB 31中的拥塞指示接收单元 31 c， 接收 RNC32发送的传输拥 塞指示。
RNC32, 向拥塞指示接收单元 31c发送传输拥塞指示。
图 3所示拥塞指示接收单元 31c可以是针对一个用户而言，也可以 是针对多个用户而言。
现有技术中， 图 3所示 NodeB包含的拥塞指示接收单元， 与图 1所 示 NodeB包含的空口信息单元、 MAC-e调度单元之间相互独立， 没有 关联。
现有技术的缺点是：
1 ) 基于空口负载的 MAC-e调度算法只考虑了 NodeB小区内的空 口负载资源， 但是 HSUPA用户的上行方向的单用户最大流量可高达 5.76Mbps, 呈现出很强的突发，实际系统应用中 Iub口传输带宽的资源 是有限的，如果 NodeB在 MAC-e调度时不考虑 Iub传输带宽资源的分配 和控制，在传输带宽配置有限的情况下，很有可能出现上行传输拥塞， 并导致数据丢失、 时延过大等问题， 影响传输质量， 传输的 QoS无法 得到保证。 2 ) 如果在某个 FP承载上发现有上行数据丟失或者时延过大， RNC向 Node反馈传输拥塞指示 ,指示 NodeB控制该 FP承载上上行数据 的发送。 此时如果没有针对此拥塞状况的特殊 MAC-e调度， 那么调度 的结果有可能是要求该用户继续升速或降速或保持，如果调度的结果 是升速， NodeB接收的上行数据会更多， 但又需要减少向 RNC发送的 数据， 容易导致 NodeB负担过重。 发明内容
有鉴于此，本发明实施例的主要目的在于提供一种 MAC-e调度方 法， 能够减少数据丟失， 降低传输时延， 进而提高传输质量。
本发明实施例的另一主要目的在于提供一种 MAC-e调度系统，能 够减少数据丢失， 降低传输时延， 进而提高传输质量。
本发明实施例中的技术方案是这样实现的：
一种增强专用信道的媒体接入控制 MAC-e调度方法， 在执行 MAC- e调度时， 该方法包含以下步骤：
A、 判断上行传输是否出现异常状况， 如果出现， 则执行步驟 B; 度命令。
所述出现异常状况为： 出现传输拥塞；
步驟 A所述判断为： 判断是否有用户出现传输拥塞， 如果是， 则 上行传输出现异常状况； 否则， 上行传输未出现异常状况；
所述步骤 B为： 对出现传输拥塞的用户发送降速的 MAC-e调度命 令；
步骤 B之后进一步包含步骤 CI 1 :
Cl l、 对未出现传输拥塞的用户进行 MAC-e调度。 步骤 B和步骤 CI 1之间进一步包含： 判断是否有用户收到拥塞解 除指示， 如果没有， 则执行步據 Cl l， 否则停止对出现传输拥塞的用 户发送降速调度命令后， 执行步骤 Cl l。
所述出现异常状况为： 出现数据緩存过大；
步骤 A所述判断为： 判断是否出现用户数据緩存过大， 如果是， 则 上行传输出现异常状况； 否则， 上行传输未出现异常状况；
所迷步骤 B为： 对出现数据緩存过大传输端口上的用户发送降速 的 MAC-e调度命令；
步骤 B之后进一步包含： 对不属于数据緩存过大传输端口的用户 进行 MAC-e调度。
步驟 A之前包含： 预先设置数据緩存门限值；
步骤 A所述判断根据比较数据緩存值与緩存门限值比较的结果进 行。
所述出现异常状况为： 存在调度后上行流量超过配置的 Iub传输 端口带宽的传输端口；
步驟 A之前进一步包含： 对用户进行 MAC-e调度， 并计算调度后 传输端口的上行流量；
步骤 A所述判断为：判断是否存在调度后上行流量超过配置的 Iub 传输端口带宽的传输端口， 如果存在， 则上行传输出现异常状况； 否 则， 上行传输未出现异常状况；
所述步骤 B为： 判断上行流量超过配置的 Iub传输端口带宽的传输 端口上是否存在调度结果为升速的用户， 如果存在， 则将调度结果为 升速用户的调度命令修改为降速 MAC-e调度命令或保持速度 MAC-e 调度命令； 否则结束 MAC- e调度流程。
步驟 C11之前进一步包含： Cl l l、 判断是否出现用户数据緩存过大， 如果是， 则执行步骤 C112, 否则执行步骤 C113;
C112、对出现数据緩存过大传输端口上的用户发送降速的 MAC-e 调度命令；
所述步驟 CI 1具体为步骤 C113:
C 113、对未出现传输拥塞且不属于数据緩存过大传输端口的用户 进行 MAC-e调度。
步驟 C113之后进一步包含：
C21、 计算 MAC-e调度后传输端口的上行流量；
C22、判断是否存在调度后上行流量超过配置的 Iub传输端口带宽 的传输端口， 如果存在， 则执行步骤 C23; 否则结束 MAC-e调度流程；
C23、判断上行流量超过配置的 Iub传输端口带宽的传输端口上是 否存在调度结果为升速的用户， 如果存在， 则执行步骤 C24; 否则结 束 MAC-e调度流程；
C24、 将调度结果为升速用户的 MAC- e调度命令修改为降速或保 持速度 MAC-e调度命令。
步骤 A中判断为未出现异常状况后进一步包含： 对用户进行 MAC-e调度。
一种 MAC-e调度系统， 包含： 用户设备 UE, 包含空口信息单元、 MAC-e调度单元的 NodeB , UE向空口信息单元发送调度请求； 空口信 息单元向 MAC-e调度单元发送空口信息， NodeB进一步包含： 上行传 输检测单元；
上行传输检测单元， 用于向 MAC- e调度单元发送上行传输信息； MAC-e调度单元， 用于根据收到的上行传输信息向 UE发送降速 或保持速度的 MAC-e调度命令。 所述上行传输检测单元由拥塞指示接收单元和 /或 lub信息单元组 成
该系统进一步包含： 无线网络控制器 RNC;
拥塞指示接收单元， 接收 RNC发送的传输拥塞信息， 向 MAC-e 调度单元发送传输拥塞信息； MAC-e调度单元根据收到的传输拥塞信 息向 UE发送降速 MAC-e调度命令；
lub信息单元， 接收 RNC发送的 lub传输端口信息， 向 MAC-e调度 单元发送 lub传输端口信息； MAC-e调度单元根据收到的 lub传输端口 信息向 UE发送降速或保持速度的 MAC-e调度命令。
所述上行传输检测单元包含： 緩存单元；
緩存单元， 接收空口信息单元发送的用户数据， 向 MAC-e调度单 元发送数据緩存过大信息； MAC-e调度单元根据收到的数据緩存过大 信息向 UE发送降速 MAC-e调度命令。
本发明实施例有以下有益效果：
1 )本方明实施例中通过对于上行流量超过配置的 lub传输端口带 令， 可以预先控制上行流量， 由此尽量避免 lub口的单用户拥塞或数 据緩存过大导致的数据丢失或时延过大， 进而能够提高传输质量， 保 证 lub传输的 QoS。
2 ) 本方明实施例中对出现传输拥塞的用户通过 MAC-e调度进行 降速， 能够有效快速地解除对应用户的传输拥塞状态， 避免数据丢失 或时延过大， 进而提高传输质量。
3 ) 本方明实施例中对出现緩存过大的用户通过 MAC-e调度进行 降速， 能够有效快速地解除对应用户的緩存过大状态， 避免数据丢失 或时延过大， 进而提高传输质量。 4 ) HSUPA中， NodeB的 MAC-e调度能够限制用户的发射功率， 用户的可用发射功率直接影响到其数据发送， 即通过 NodeB的 MAC-e 调度， NodeB可以限制 UE的数据发送流量。 本发明实施例中利用 HSUPA的此特性， 结合 NodeB检测的 Iub传输端口的传输带宽、 流量 等信息， NodeB可以根据可用的 Iub传输带宽资源执行对用户的调度， 能够充分利用传输带宽。 附图简要说明
图 1为现有技术中进行 MAC- e调度的系统示意图；
图 2为现有技术中进行 MAC-e调度的过程示意图；
图 3为现有技术中 RNC向 NodeB发送传输拥塞指示的系统示意 图；
图 4为本发明实施例 1中 MAC-e调度的系统示意图；
图 5为本发明实施例 1中 MAC-e调度的过程示意图；
图 6为本发明实施例 2中 MAC-e调度的系统示意图；
图 7为本发明实施例 2中 MAC-e调度的过程示意图；
图 8为本发明实施例 3中 MAC-e调度的系统示意图；
图 9为本发明实施例 3中 MAC- e调度的过程示意图；
图 10为本发明实施例 4中 MAC - e调度的系统示意图；
图 11为本发明实施例 4中 MAC-e调度的过程示意图。 实施本发明的方式
本发明实施例中： 在执行 MAC-e调度时， 判断上行传输是否出现 异常状况， 如果出现， 则根据出现的异常状况向用户发送降速或保持 速度的 MAC-e调度命令。 所述 MAC-e调度可以是针对一个用户， 也可以是针对多个用户， 其中，如果针对一个用户，则所述向用户发送中的用户是指某个用户， 如果针对多个用户，则所述向用户发送中的用户是一个用户或多个用 户， 以下本文中均如此。
所述出现异常状况是指：出现有可能会导致数据丢失或时延过大 的状况， 比如出现传输拥塞、 数据緩存过大、 存在调度后上行流量超 过配置的 Iub传输端口带宽的传输端口等状况中的一个或多个。
本发明实施例中所述 MAC-e调度系统除了图 1所述单元， 进一步 包含： 上行传输检测单元， 上行传输检测单元向 MAC-e调度单元发送 上行传输信息， MAC-e调度单元根据收到的上行传输信息， 向 UE发 送降速或保持速度的调度命令。 所述上行传输检测单元为： 检测上行 传输状态的单元， 比如： 拥塞指示接收单元、 緩存单元、 Iub信息单 元中的一个或多个； 所述上行传输信息为： 与上行传输状态有关的信 息， 比如： 传输拥塞信息、 数据緩存过大信息、 Iub传输端口信息中 的一个或多个。
以下本文中所述 UE、 上行传输检测单元、 MAC-e调度单元、 拥 塞指示接收单元、 緩存单元、 Iub信息单元， 以及空口信息单元， 可 以针对一个用户而言， 也可以针对多个用户而言。
实施例 1 :
本实施例中， 上行传输检测单元为： 拥塞指示接收单元； 上行传 输信息为： 传输拥塞信息。
本实施例中所述出现异常状况是指： 出现传输拥塞。
图 4为本实施例中 MAC-e调度的系统示意图，该系统包含： UE41、
NodeB42 RNC43 , 其中 NodeB42包含： 空口信息单元 42a、 MAC-e 调度单元 42b、 拥塞指示接收单元 42c。 UE41 , 向 NodeB42中的空口信息单元 42a发送调度请求， 接收 MAC-e调度单元 42b发送的调度命令信息。
NodeB42中的空口信息单元 42a， 接收 UE41发送的调度请求， 向 MAC-e调度单元 42b发送空口信息。
NodeB42中的 MAC-e调度单元 42b, 接收空口信息单元 42a发送的 空口信息， 接收拥塞指示接收单元 42c发送的传输拥塞信息， 向 UE41 发送调度命令信息。
NodeB42中的拥塞指示接收单元 42c， 接收 RNC43发送的传输拥 塞信息 , 向 MAC-e调度单元 42b发送传输拥塞信息。
RNC43， 向拥塞指示接收单元 31 c发送传输拥塞信息。
图 5为本实施例中 MAC-e调度的过程示意图， 该过程包含以下步 驟：
步骤 501 : 与步骤 201相同。
步骤 502: MAC-e调度单元判断是否有用户出现传输拥塞， 如果 是， 则执行步骤 503 , 否则执行步骤 504。
步骤 502所述判断， 可以根据拥塞指示接收单元给 MAC-e调度单 元发送的传输拥塞信息进行， MAC-e调度单元根据收到的信息， 即可 判断哪个用户出现传输拥塞。 拥塞指示接收单元通常是从 RNC中的 SRNC接收传输拥塞指示，这里，由于 HSUPA的突发性特点以及 NodeB MAC-e调度的准确性、 空口误码导致的上下行信息失真等原因， 上行 传输中通常存在传输拥塞。 根据 3GPP的 R6版本协议， 出现传输拥塞 后， RNC中的 SRNC可以向 NodeB发送传输拥塞指示， 比如发送传输 拥塞指示 （ TNL CONGESTION INDICATION ) 控制帧。 TNL CONGESTION INDICATION的帧结构可以根据 3GPP TS 25.427 V6.4.0 (2005-09)协议中 的描述。 协议中 TNL CONGESTION INDICATION控制帧可以使用拥塞状态（ Congestion Status )参数表示 对应的传输承载上的传输拥塞状态， 比如： 由 0表示不拥塞； 由 1表示 保留； 由 2表示传输延时导致的拥塞； 由 3表示丢帧导致的拥塞。 根据 协议的规定， RNC在检测到传输拥塞后， 向 NodeB发送上述的 TNL CONGESTION INDICATION控制帧指示 RNC检测到了传输拥塞， 此 时 Congestion Status参数可以为 1或 2;拥塞解除后， RNC也会向 NodeB 发送 TNL CONGESTION INDICATION控制帧， 指示拥塞解除， 此时 Congestion Status参数可以为 0。
步骤 503: MAC-e调度对出现传输拥塞的用户发送降速的调度命 令。
通过步骤 503， MAC-e调度可以减少所述用户的上行数据发送速 率， 进而可以减轻或者消除上行传输拥塞。
本步骤之后， 可以直接执行步骤 504, 也可以由 MAC-e调度单元 先判断是否有用户收到 RNC下发的拥塞解除指示， 如果没有， 则执行 步骤 504,否则停止对收到拥塞解除指示用户发送的降速调度命令后， 执行步骤 504。 比如： NodeB如果接收到每个用 户 的 TNL CONGESTION INDICATION控制帧且指示为拥塞产生， 则 NodeB从 当前时刻起在 MAC-e调度时对此类用户强制发送降速的调度命令，一 直到接收到 RNC下发的 TNL CONGESTION INDICATION 控制帧且 指示拥塞解除。
步骤 504 : 根据空口资源信息对没出现传输拥塞的用户进行 MAC-e调度。
步骤 504与步骤 202基本相同， 只是如果步骤 504之前执行了步骤 503， 则步骤 504中只对没出现传输拥塞的用户进行 MAC-e调度。
步驟 505: 与步骤 203相同。 实施例 2:
本实施例中，上行传输检测单元为：緩存单元；上行传输信息为： 数据緩存过大信息。
本实施例中所述出现异常状况是指： 出现数据緩存过大。
图 6为本实施例中 MAC-e调度的系统示意图，该系统包含： UE41、 NodeB42 ,其中 NodeB42包含：空口信息单元 42a、 MAC-e调度单元 42b、 緩存单元 42d。
UE41 , 与图 4中所述相同。
空口信息单元 42a， 接收 UE41发送的调度请求， 向 MAC-e调度单 元 42b发送空口信息， 接收 UE41发送的用户数据， 向緩存单元 42d发 送。
MAC-e调度单元 42b， 接收空口信息单元 42a发送的空口信息， 接 收緩存单元 42d发送的数据緩存过大信息， 向 UE41发送调度命令信 息。
緩存单元 42d, 接收空口信息单元 42a发送的用户数据， 向 MAC- e 调度单元 42b发送数据緩存过大信息。
图 7为本实施例中 MAC-e调度的过程示意图， 该过程包含以下步 骤：
步骤 701 : 与步骤 501相同。
步骤 702: MAC-e调度单元判断是否出现用户数据緩存过大， 如 果是， 则执行步骤 703 , 否则执行步骤 704。
步骤 702所述判断， 可以根据緩存单元给 MAC-e调度单元发送的 数据緩存过大信息进行， MAC-e根据收到的信息，结合用户使用的 Iub 传输端口信息， 即可判断数据緩存过大 Iub传输端口中承载的数据对 应的用户。 这里， 针对 HSUP A上行数据突发较大的特点， NodeB通常 会提供一定的 lub传输端口上行数据緩存能力 , 当上行传输提供的发 送能力比上行需要发送的数据量小时， NodeB把无法及时发送出去的 数据緩存到緩冲区， 即緩存单元中， 以便能够有效避免峰值数据突发 时数据的丟失。 NodeB的上行数据緩存可以采用在每个 lub传输发送端 口提供数据緩冲区的方式或其他方式实现。 实际应用时， NodeB可以 周期性检测上行 lub传输端口的緩存。 至于用户使用的 lub传输端口信 息， 通常是 HSUPA用户接入 NodeB时， RNC通过高层信令的方式通知 NodeB建立该用户使用的传输承载信息，包括业务使用的 lub传输端口 等。
步骤 702中， 判断数据緩存是否过大时， 可以将緩存值与预先设 置的门限值进行比较。所迷门限值的大小可以根据综合传输业务所能 接受的时延大小， 緩冲区大小进行设置， 具体门限值的大小不影响本 实施例所述过程的实现。
步骤 703: MAC-e调度对出现数据緩存过大 lub传输端口上的用户 发送降速的调度命令。
本步骤之后， 可以直接执行步骤 704， 也可以 MAC- e调度单元先 判断缓冲区中的数据是否发送完毕， 如果不是， 则执行步骤 704, 否 则取消对出现数据緩存过大用户发的降速调度命令后，执行步骤 704。
实际应用时， NodeB可以一直保持对传输緩存的监测， 如果发现 某个 lub传输端口对应的緩冲区出现数据緩存过多比如超过一个设定 的门限，则意味着 NodeB此 lub传输端口的发送能力无法满足数据发送 的要求； 出现緩存异常后， MAC- e实体执行调度时对使用本传输端口 的 HSUPA用户发送降速命令， 控制 UE降低上行数据发送速率。
步骤 704: 根据空口资源信息对不属于数据緩存过大 lub传输端口 的用户进行 MAC-e调度。 步骤 704与步骤 202基本相同， 只是如果步驟 704之前执行了步骤 703 , 则步骤 704中只对没出现数据緩存过大的用户进行 MAC-e调度。
步骤 705: 与步驟 505相同。
实施例 3:
本实施例中， 上行传输检测单元为： lub信息单元， 上行传输信 息为： lub传输端口信息。
本实施例中所述出现异常状况是指：存在调度后上行流量超过配 置的 lub传输端口带宽的传输端口。
图 8为本实施例中 MAC-e调度的系统示意图，该系统包含： UE41、 NodeB42、 RNC43 , 其中 NodeB42包含： 空口信息单元 42a、 MAC-e 调度单元 42b、 lub信息单元 42e。
UE41、 空口信息单元 42a, 与图 4中所述相同。
MAC-e调度单元 42b, 接收空口信息单元 42a发送的空口信息， 接 收 lub信息单元 42e发送的 lub传输端口信息， 向 UE41发送调度命令信 息。
lub信息单元 42e , 接收 RNC发送的 lub传输端口信息， 向 MAC-e 调度单元 42b发送 lub传输端口信息。
RNC43 , 向 lub信息单元 42e发送 lub传输端口信息。
图 9为本实施例中 MAC-e调度的过程示意图， 该过程包含以下步 骤：
步驟 901 : 与步骤 501相同。
步骤 902: 根据空口资源信息对用户进行 MAC-e调度， 并计算出 调度后传输端口的上行流量。
步驟 902所述根据空口资源信息对用户进行] VIAC-e调度， 与步骤 202相同。 通常， MAC-e实体根据协议提供的框架执行 MAC-e调度时， 对 NodeB中已经存在的 HSUPA用户发升速、或降速、 或保持的调度命 令， 产生调度命令后， NodeB根据调度结果能够预测 UE被 NodeB调度 后的最大上行发送数据速率， 并结合每个用户使用的 Iub传输端口配 置， 可以计算出 NodeB配置的所有 Iub传输端口上的上行传输流量。 至 于用户使用的 Iub传输端口信息， 通常是 HSUPA用户接入 NodeB时， RNC通过高层信令的方式通知 NodeB建立该用户使用的传输承载信 息， 包括业务使用的 Iub传输端口和带宽等。
步骤 902中， 通常是调度一个用户后就算出该用户调度后的上行 流量， 并根据各个用户的上行流量， 能够计算出各个 Iub传输端口中 所有用户总的上行流量。
步骤 903: MAC-e调度单元判断是否存在调度后上行流量超过配 置的 Iub传输端口带宽的传输端口， 如果存在， 则执行步骤 904， 否则 执行步骤 906。
步驟 903所述判断，可以根据 Iub信息单元给 MAC-e调度单元发送 的 Iub传输端口信息进行， MAC-e调度单元根据收到的信息， 即可判 断各个 Iub传输端口的最大上行流量是否将超过配置的 Iub传输端口最 大带宽。 所述 Iub传输端口信息包含： Iub传输端口允许的最大带宽。 所述允许的最大带宽通常在基站建立时配置， 这里， 基站建立时， 配 置的信息包含： NodeB与 RNC之间使用的 Iub传输端口、 每个 Iub传输 端口配置的带宽等传输资源信息， 所配置的信息相对固定， 除非修改 Iub传输端口带宽配置， 否则不会变。
步骤 904: MAC-e调度单元判断步骤 903中所述超过的传输端口是 否存在调度结果为升速的用户， 如果存在， 则执行步骤 905， 否则执 行步驟 906。
步骤 905: 修改调度结果为升速用户的调度命令。 步骤 905所述修改升速的调度命令可以为将调度命令修改为保持 速度或者降速。 步骤 905中修改调度命令的目标可以为： 调度后 lub传 输端口的上行流量不超过配置的 lub传输端口带宽。
步 4^906: 与步骤 505相同。
实施例 4:
本实施例中， 上行传输出现异常状况可以为： 出现传输拥塞、 出 现数据緩存过大、 存在调度后上行流量超过配置的 lub传输端口带宽 的传输端口等状况中的一个或多个。
本实施例为实施例 1〜实施例 3中分别所述的 3个方案的組合,组合 后的系统如图 10所示。
图 10为本实施例中 MAC-e调度的系统示意图， 该系统包含： UE41、 NodeB42、 RNC43 , 其中 NodeB42包含： 空口信息单元 42a、 MAC-e调度单元 42b、 拥塞指示接收单元 42c、 緩存单元 42d、 lub信息 单元 42e。
UE41 , 向 NodeB42中的空口信息单元 42a发送调度请求， 接收 MAC-e调度单元 42b发送的调度命令信息。
NodeB42中的空口信息单元 42a， 接收 UE41发送的调度请求， 接 收 UE41发送的用户数据，向緩存单元 42d发送，向 MAC-e调度单元 42b 发送空口信息。
NodeB42中的 MAC-e调度单元 42b， 接收空口信息单元 42a发送的 空口信息， 接收拥塞指示接收单元 42c发送的传输拥塞指示， 接收緩 存单元 42d发送的数据緩存过大信息， 接收 lub信息单元 42e发送的 lub 传输端口信息， 向 UE41发送调度命令信息。
NodeB42中的拥塞指示接收单元 42c, 接收 RNC43发送的传输拥 塞指示， 向 MAC-e调度单元 42b发送传输拥塞指示。 緩存单元 42d， 接收空口信息单元 42a发送的用户数据， 向 MAC-e 调度单元 42b发送数据緩存过大信息。
lub信息单元 42e， 接收 RNC发送的 lub传输端口信息， 向 MAC-e 调度单元 42b发送 lub传输端口信息。
RNC43 , 向拥塞指示接收单元 31c发送传输拥塞指示， 向 lub信息 单元 42e发送 lub传输端口信息。
实施例 1〜实施例 3中分别所述的 3个方案进行组合时可以按不同 的先后顺序进行组合， 图 11为其中的一种组合方式， 图 11所示过程包 含以下步骤：
步骤 1101〜步驟 1103: 与步骤 501〜步骤 503相同， 只是步骤 503之 后根据空口资源信息对其他用户进行 MAC-e调度， 而执行步驟 1103 之后， 执行步骤 1104。
步骤 1104〜步驟 1105: 与步骤 702〜步骤 703相同， 只是步驟 703之 后根据空口资源信息对其他用户进行 MAC-e调度， 而执行步骤 1105 之后， 执行步骤 1106。
步驟 1106〜步骤 1110: 与步骤 902〜步骤 906相同， 只是步骤 1106 中对没有出现传输拥塞、且不属于出现緩存过大传输端口的用户进行 MAC-e调度， 并计算调度后各传输端口的上行流量。
实际应用时， 实施例 1〜实施例 3中分别所述的 3个方案， 可以进行 两个或三个的合理组合， 比如： 实施例 4中提供的 3个方案組合之后的 一种方案， 其他合理組合均在本发明保护范围之内， 在此不再详述。
本发明实施例中， 上行传输检测单元为除了可以为： 拥塞指示接 收单元、 緩存单元、 lub信息单元中的一个或多个， 也可以为其他检 测上行传输状态的单元。
本发明实施例中， 上行传输信息除了可以为： 传输拥塞信息、 数 据緩存过大信息、 lub传输端口信息中的一个或多个之外， 也可以为 其他信息。
本发明实施例中，所述出现异常状况除了可以为：出现传输拥塞、 数据緩存过大、 存在调度后上行流量超过配置的 lub传输端口带宽的 传输端口等状况中的一个或多个之外，也可以为出现其他可能会导致 数据丟失或时延过大的状况。
以上所述仅为本发明的较佳实施例，并非用以限定本发明的保护 范围。

Claims

权利要求书
1、 一种增强专用信道的媒体接入控制 MAC-e调度方法， 在执行 MAC-e调度时， 其特征在于， 该方法包含以下步骤：
A、 判断上行传输是否出现异常状况， 如果出现， 则执行步驟 B; 度命令。
2、 根据权利要求 1所述的方法， 其特征在于， 所述出现异常状况 为： 出现传输拥塞；
步驟 A所述判断为： 判断是否有用户出现传输拥塞， 如果是， 则 上行传输出现异常状况； 否则， 上行传输未出现异常状况；
所述步骤 B为： 对出现传输拥塞的用户发送降速的 MAC-e调度命 令；
步骤 B之后进一步包含步骤 CI 1：
Cl l、 对未出现传输拥塞的用户进行 MAC-e调度。
3、 根据权利要求 2所述的方法， 其特征在于， 步骤 B和步骤 C11 之间进一步包含： 判断是否有用户收到拥塞解除指示， 如果没有， 则 执行步骤 C11 ,否则停止对出现传输拥塞的用户发送降速调度命令后， 执行步骤 Cl l。
4、 根据权利要求 1所述的方法， 其特征在于， 所述出现异常状况 为： 出现数据缓存过大；
步骤 A所述判断为： 判断是否出现用户数据緩存过大， 如果是， 则 上行传输出现异常状况； 否则， 上行传输未出现异常状况；
所述步骤 B为： 对出现数据缓存过大传输端口上的用户发送降速 的 MAC-e调度命令； 步骤 B之后进一步包含： 对不属于数据緩存过大传输端口的用户 进行 MAC-e调度。
5、 根据权利要求 4所述的方法， 其特征在于， 步骤 A之前包含： 预先设置数据缓存门限值；
步骤 A所述判断根据比较数据緩存值与緩存门限值比较的结果进 行。
6、 根据权利要求 1所述的方法， 其特征在于， 所述出现异常状况 为： 存在调度后上行流量超过配置的 Iub传输端口带宽的传输端口； 步骤 A之前进一步包含： 对用户进行 MAC-e调度， 并计算调度后 传输端口的上行流量；
步骤 A所述判断为： 判断是否存在调度后上行流量超过配置的 Iub 传输端口带宽的传输端口， 如果存在， 则上行传输出现异常状况； 否 则， 上行传输未出现异常状况；
所述步骤 B为： 判断上行流量超过配置的 Iub传输端口带宽的传输 端口上是否存在调度结果为升速的用户， 如果存在， 则将调度结果为 升速用户的调度命令修改为降速 MAC-e调度命令或保持速度 MAC-e 调度命令； 否则结束 MAC-e调度流程。
7、 根据权利要求 2所述的方法， 其特征在于， 步骤 C11之前进一 步包含：
Cl l l、 判断是否出现用户数据緩存过大， 如果是， 则执行步驟 cm, 否则执行步骤 cii3;
C 112、对出现数据緩存过大传输端口上的用户发送降速的 MAC-e 调度命令；
所述步骤 CI 1具体为步骤 C113:
C113、对未出现传输拥塞且不属于数据緩存过大传输端口的用户 进行 MAC-e调度。
8、 根据权利要求 7所述的方法， 其特征在于， 步骤 C113之后进一 步包含：
C21、 计算 MAC-e调度后传输端口的上行流量；
021、判断是否存在调度后上行流量超过配置的 lub传输端口带宽 的传输端口， 如果存在， 则执行步骤 C23; 否则结束 MAC-e调度流程；
C23、判断上行流量超过配置的 lub传输端口带宽的传输端口上是 否存在调度结果为升速的用户， 如果存在， 则执行步骤 C24; 否则结 束 MAC-e调度流程；
C24、 将调度结果为升速用户的 MAC-e调度命令修改为降速或保 持速度 MAC-e调度命令。
9、 根据权利要求 2、 3、 4、 5、 7或 8所述的方法， 其特征在于， 步骤 A中判断为未出现异常状况后进一步包含： 对用户进行 MAC-e调 度。
10、 一种 MAC-e调度系统， 包含： 用户设备 UE, 包含空口信息 单元、 MAC-e调度单元的 NodeB, UE向空口信息单元发送调度请求； 空口信息单元向 MAC-e调度单元发送空口信息， 其特征在于， NodeB 进一步包含： 上行传输检测单元；
上行传输检测单元， 用于向 MAC-e调度单元发送上行传输信息； MAC-e调度单元， 用于根据收到的上行传输信息向 UE发送降速 或保持速度的 MAC-e调度命令。
11、 根据权利要求 10所述的系统， 其特征在于， 所述上行传输检 测单元由拥塞指示接收单元和 /或 lub信息单元组成；
该系统进一步包含： 无线网络控制器 RNC;
拥塞指示接收单元， 接收 RNC发送的传输拥塞信息， 向 MAC-e 调度单元发送传输拥塞信息； MAC-e调度单元根据收到的传输拥塞信 息向 UE发送降速 MAC-e调度命令；
Iub信息单元， 接收 RNC发送的 Iub传输端口信息， 向 MAC-e调度 单元发送 Iub传输端口信息； MAC-e调度单元 #居收到的 Iub传输端口 信息向 UE发送降速或保持速度的 MAC-e调度命令。
12、 根据权利要求 10或 11所述的系统， 其特征在于， 所述上行传 输检测单元包含： 緩存单元；
缓存单元， 接收空口信息单元发送的用户数据， 向 MAC-e调度单 元发送数据緩存过大信息； MAC-e调度单元根据收到的数据緩存过大 信息向 UE发送降速 MAC-e调度命令。
PCT/CN2007/000531 2006-03-31 2007-02-14 Procédé d'ordonnancement mac-e pour canal spécifique amélioré et système associé WO2007112646A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN200610067077A CN101047425B (zh) 2006-03-31 2006-03-31 一种增强专用信道的媒体接入控制调度方法和系统
CN200610067077.6 2006-03-31

Publications (1)

Publication Number Publication Date
WO2007112646A1 true WO2007112646A1 (fr) 2007-10-11

Family

ID=38563089

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2007/000531 WO2007112646A1 (fr) 2006-03-31 2007-02-14 Procédé d'ordonnancement mac-e pour canal spécifique amélioré et système associé

Country Status (2)

Country Link
CN (1) CN101047425B (zh)
WO (1) WO2007112646A1 (zh)

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP5168066B2 (ja) * 2008-10-01 2013-03-21 日本電気株式会社 移動通信システム、無線基地局、送信レート割当方法
WO2020223919A1 (en) * 2019-05-08 2020-11-12 Lenovo (Beijing) Limited Method and apparatus for radio link flow control

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1575026A (zh) * 2003-06-16 2005-02-02 三菱电机株式会社 具有停等式自动重发请求处理的时间调度
CN1627845A (zh) * 2003-12-11 2005-06-15 北京三星通信技术研究有限公司 移动通信系统中上行共享信道增强的基站控制的调度方法
WO2005078967A1 (en) * 2004-02-14 2005-08-25 Samsung Electronics Co., Ltd. Method of transmitting scheduling information on an enhanced uplink dedicated channel in a mobile communication system

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1575026A (zh) * 2003-06-16 2005-02-02 三菱电机株式会社 具有停等式自动重发请求处理的时间调度
CN1627845A (zh) * 2003-12-11 2005-06-15 北京三星通信技术研究有限公司 移动通信系统中上行共享信道增强的基站控制的调度方法
WO2005078967A1 (en) * 2004-02-14 2005-08-25 Samsung Electronics Co., Ltd. Method of transmitting scheduling information on an enhanced uplink dedicated channel in a mobile communication system

Also Published As

Publication number Publication date
CN101047425B (zh) 2010-05-12
CN101047425A (zh) 2007-10-03

Similar Documents

Publication Publication Date Title
JP4014615B2 (ja) 測定報告方法、基地局、測定の受信方法、およびコントローリング無線ネットワーク制御装置
US8755270B2 (en) Congestion/load indication for high speed packet access
EP2965558B1 (en) Sending data rate information to a wireless access network node
JP4643650B2 (ja) 無線アクセスネットワーク内での輻輳制御
EP1836866B1 (en) Uplink congestion detection and control between nodes in a radio access network
WO2008022588A1 (fr) Procédé permettant de réguler le flux pour une interface iub, appareil et station de base
US7801550B2 (en) Radio communication system and method where a radio terminal transmits uplink user data to a base station through an enhanced deticated physical data channel
US20110235528A1 (en) Fair congestion detection for transport network layer wcdma communications
US20060209686A1 (en) Flow control with dynamic priority allocation for handover calls
JP2010502056A (ja) 無線ネットワーク内でアップリンクスケジューリング要求および緊急状態を報告するための方法およびデバイス
JP2008515301A (ja) 上り回線送信の遅延推定
EP2437445B1 (en) Dynamic control of air interface throughput
JP5055431B2 (ja) 基地局、無線通信システム及び無線通信方法
WO2009097820A1 (zh) 解调资源分配方法、基站和系统
WO2010021338A1 (ja) 基地局、上位局、無線通信システム及び無線通信方法
WO2007112646A1 (fr) Procédé d'ordonnancement mac-e pour canal spécifique amélioré et système associé
WO2006097805A1 (en) Flow control with dynamic priority allocation for handover calls
EP1928196A1 (en) A method for radio flow control in a mobile communication system
KR20070053370A (ko) 무선 액세스 네트워크 내의 정체 제어

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 07710952

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 07710952

Country of ref document: EP

Kind code of ref document: A1