WO2008101366A1 - A packet dispatching method in wireless communication system - Google Patents
A packet dispatching method in wireless communication system Download PDFInfo
- Publication number
- WO2008101366A1 WO2008101366A1 PCT/CN2007/000590 CN2007000590W WO2008101366A1 WO 2008101366 A1 WO2008101366 A1 WO 2008101366A1 CN 2007000590 W CN2007000590 W CN 2007000590W WO 2008101366 A1 WO2008101366 A1 WO 2008101366A1
- Authority
- WO
- WIPO (PCT)
- Prior art keywords
- service
- rate
- threshold
- soft
- resource
- Prior art date
Links
- 238000000034 method Methods 0.000 title claims abstract description 97
- 238000004891 communication Methods 0.000 title claims abstract description 21
- 230000001133 acceleration Effects 0.000 claims description 19
- 238000012545 processing Methods 0.000 claims description 16
- 238000011084 recovery Methods 0.000 claims description 15
- 238000005259 measurement Methods 0.000 claims description 14
- 238000013468 resource allocation Methods 0.000 claims description 13
- 230000001105 regulatory effect Effects 0.000 claims description 8
- 230000003827 upregulation Effects 0.000 claims description 6
- 238000012544 monitoring process Methods 0.000 claims description 3
- 230000001960 triggered effect Effects 0.000 description 7
- 238000010586 diagram Methods 0.000 description 5
- 238000012423 maintenance Methods 0.000 description 4
- 108010003272 Hyaluronate lyase Proteins 0.000 description 1
- 230000007423 decrease Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 239000002699 waste material Substances 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W28/00—Network traffic management; Network resource management
- H04W28/16—Central resource management; Negotiation of resources or communication parameters, e.g. negotiating bandwidth or QoS [Quality of Service]
- H04W28/24—Negotiating SLA [Service Level Agreement]; Negotiating QoS [Quality of Service]
Definitions
- the present invention relates to a wireless communication system supporting multi-user packet data services.
- the rate scalability of packet services is very large. If the system data load is too light, the packet data service rate is too small, which will reduce the system throughput and waste system resources. If the packet data service rate is too large when the system load is heavy, the system resources will be exhausted and new users cannot access.
- QoS Quality of Service
- the system is generally considered to be congested when the user initiates a call but the system resources are insufficient to cause the call to fail, thereby triggering the packet data service rate to be lowered to release part of the resources.
- Such a scheme can make full use of system resources, but the disadvantage is that a large amount of call loss occurs when the system is under heavy load, because the failure of resource allocation means that the call has failed, and the system congestion is considered to be late.
- the technical problem to be solved by the present invention is to provide a packet scheduling method in a wireless communication system.
- a wireless communication system carrying a multi-user packet data service when the system capacity is insufficient, the new user can still access the system.
- the present invention provides a packet scheduling method in a wireless communication system, which includes the following steps: (a) when the system allocates resources to the target cell or increases the resource allocation of the service with the hard resource requirement of the service, if the resource allocation is successful, the next step is performed;
- step (b) determining whether the system resource is sufficient according to a preset system resource threshold is performed by any one of the following three determinations:
- the minimum hard resource requirement threshold is determined according to the type of the system bearer service, and is the maximum value of the minimum hard resource requirement of various services supported by the system.
- the above method may further have the following features:
- the system performs resource allocation with a minimum hard resource requirement of the service after receiving a service establishment request or a handover request.
- the foregoing method may further have the following features:
- the service performs resource preemption, and the resource preemption includes the following steps:
- the new user does not wait for a timeout, the new user is reassigned resources.
- the foregoing method may further have the following features: In the step-1), whether the user with a lower priority of the service quality of the service and can be preempted in the determining system is prioritized by the service quality in the system. The user with the lowest level starts to judge whether the user can be preempted according to the core network parameters carried by the radio access bearer when the service is established. If not, the user with the lower priority of the service quality is judged.
- the packet scheduling and speed reduction processing of the service in the system includes the following steps:
- (b-1) determining whether there is a rate-downtable service in the system, and if so, sorting the services in the system according to the size of the falling rate of the service rate, where the falling rate of the service rate refers to the current rate of the service The difference in the minimum rate of service, otherwise, the end;
- step (b-2) preferentially reduce the service rate of the service with a large drop in service rate, and return to step (b-1) o
- the foregoing method may further have the following features: after the service rate is lowered in the step (b-2), it is first determined whether the system resource is sufficient, and if so, the packet scheduling deceleration processing ends, otherwise the step returns to the step (b- 1), the determining whether the system resource is sufficient is to perform any one of the following three judgments:
- the foregoing method may also have the following features: During the process of the packet data service, periodically monitor the traffic volume and perform the following steps:
- step (i) when the packet scheduling and speed-up processing is performed on the service in the system, the following steps are included:
- the foregoing method may further have the following feature: the difference between the soft congestion control threshold and the soft congestion control recovery threshold is greater than or equal to an increase in soft capacity that may be caused by a level of increase in various service rates.
- Another technical problem to be solved by the present invention is to provide a packet scheduling method in a wireless communication system.
- a wireless communication system carrying a multi-user packet data service when the system resources are dynamically adjusted according to the traffic demand, the original user can be guaranteed. Under the premise of business service quality, system resources are occupied at a low level.
- the foregoing method may further have the following features:
- the determining whether there is insufficient system resources after the service rate is adjusted one level and the service quality priority in the system is not slowed down is higher.
- a low business is one of the following three judgments:
- the foregoing method may further have the following features: In the step (C), after the current service rate is adjusted, determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource requirement threshold or system soft Whether the capacity load is greater than the system soft capacity congestion control threshold, and if so, the packet scheduling and speed reduction processing is performed on the services in the system; otherwise, the packet scheduling acceleration process ends.
- the above method may further have the following features: In the step (A), performing Before step (B), or in the step (C), it is judged whether the current service rate can be up-regulated, and if so, the execution continues, otherwise, it ends. Further, the foregoing method may further have the following feature: the difference between the soft congestion control threshold and the soft congestion control recovery threshold is greater than or equal to an increase in soft capacity that may be caused by a level of increase in various service rates.
- the invention can basically solve the problem that the new service call loss is caused by the packet service rate in the system is too high through the five packet service related processing flows. Since the present invention comprehensively considers the characteristics of the packet data service, the performance of the wireless communication system, and the QoS of the packet data service carried in the wireless communication system, the packet access can be maximized under the premise of ensuring system performance and user QoS. The capacity of the system.
- FIG. 1 is a diagram showing an example of a hard resource allocation process when an initial service is accessed
- FIG. 2 is a diagram showing an example of a resource preemption process when a service is established
- 3 is a diagram showing an example of a packet scheduling slowdown process triggered by congestion control
- FIG. 4 is an exemplary diagram of a traffic triggering packet scheduling process
- FIG. 5 is a diagram showing an example of a packet scheduling acceleration process in a service maintenance process.
- the minimum hard resource requirement (Requirement- Hard) is also called the minimum hard resource demand threshold, which is determined according to the type of the system bearer service, and is generally the maximum value of the system supporting the minimum hard resource requirement of various services, or may be other settings. value.
- the minimum hard resource requirement for guaranteeing a CS12.2k (circuit switched) service call is a code resource with a Spreading Factor (hereinafter referred to as SF) of 128; assuming I/B type PS services
- SF Spreading Factor
- the rate of the service requirement is 32K, which is equivalent to the minimum hard resource requirement is a code resource with an SF of 64.
- the S-type PS service generally guarantees a rate of 64K, which is equivalent to a minimum hard resource requirement of a code resource with an SF of 32.
- the code resource with the SF of 32 is equivalent to four code resources with an SF of 128. Therefore, the minimum hard resource requirement (Requirement- Hard) for ensuring QoS during initial service access can be configured as a code resource with an SF of 32.
- the CongestionThreshold (Soft) threshold is mainly used to prevent the system soft capacity load from exceeding the maximum system soft capacity and affect the stable operation of the system. It can be determined according to system performance.
- the soft capacity refers to downlink power and uplink interference.
- the soft-capacity congestion control recovery threshold (NoraialThreshold_Soft) is mainly used to prevent the rate ping-pong lifting problem in the packet switching (Packet Switch, hereinafter referred to as PS) service acceleration process, which is generally smaller than the congestion control threshold, the congestion control threshold and the congestion control recovery threshold.
- PS Packet Switch
- the difference is greater than or equal to the increase in soft capacity that may result from a level of increase in various service rates.
- the maximum downlink transmit power of the downlink TCP is 41 dBm
- the congestion control threshold of the downlink is set to 40 dBm. If the TCP increment caused by the PS traffic rate increase is less than ldB, the congestion control recovery threshold of the downlink downlink can be set to 39 dBm. If the TCP increment caused by the PS rate up one level may be between 2 and 3 dB, the recovery threshold should be set to 37 dBm or lower.
- the basic principle of the present invention is: The system load is lowered in advance to avoid accepting the call loss caused by the rejection (call failure). After each service hard resource application is completed, it is determined whether the remaining amount of system hard resources is less than Requirement- Hard or whether the system soft-capacity load is greater than the system soft-capacity congestion control gate. CongestionThreshold—Soft, if yes, triggers the system packet scheduling process until the system hard resource remaining amount is greater than Requirement—hard or the system soft capacity load is less than CongestionThreshold—Soft, reducing system load and ensuring that new users can access the system. In addition, when the user performs packet data service, the system performance parameters are periodically monitored and packet scheduling is performed to ensure the original user's QoS.
- the congestion control process (such as PS service rate reduction) is triggered to release part of the resources to reduce the system load; when other factors trigger
- the congestion control recovery threshold 39 dBm or 37 dBm. If yes, the rate-up process is not performed.
- FIG. 1 is a resource allocation process of a service initial access cell, and the detailed implementation steps are as follows: Step 101: The system receives a service establishment request or a handover request.
- Step 102 The system allocates resources in the target cell with the minimum hard resource requirement of the service; when the hard resources are relatively abundant, the system does not limit the resource allocation by using the minimum hard resource requirement of the service, but Multiple acceptance attempts and load shedding processes.
- Step 103 If the resource allocation is successful, go to step 105, otherwise go to step 104; Step 104, invoke the resource preemption process when the service is established, as shown in Figure 2;
- Step 105 Determine whether the remaining amount of the system hard resource is smaller than the minimum hard resource requirement threshold Requirement Jiard or the system soft capacity load that guarantees the QoS when the service is initially accessed. If the system is not greater than the system soft congestion control threshold CongestionThreshold_Soft, if yes, go to step 106. Otherwise, the business distribution process ends;
- Step 106 Call the packet scheduling slowdown process triggered by the congestion control, as shown in FIG. 3.
- Figure 2 shows the resource preemption process when the service is established. The detailed implementation steps are as follows:
- Step 201 The system invokes a resource preemption process when the service is established
- Step 202 Determine whether the new user has the preemption capability. If yes, perform the next step, otherwise the current resource preemption process ends.
- Step 203 Determine whether there is a user with a lower service QoS priority and can be preempted in the system, for example, perform the next step; otherwise, the current resource preemption process ends;
- Step 204 Release the user with the lowest service QoS priority in the system and can be preempted.
- Step 205 Determine whether the new user waits for a timeout. If yes, the current resource preemption process ends. Otherwise, perform the next step;
- Step 206 Re-allocate resources to the new user. If the user is accepted when the resource is re-allocated, the current resource preemption succeeds. If the user is rejected, the current call is terminated, and the current resource preemption process ends.
- the present invention may also employ other various resource preemption processes.
- 3 is an example of a packet scheduling slowdown process triggered by congestion control
- Step 301 The congestion control triggers a packet scheduling slowdown process
- Step 302 Determine whether there is a service whose rate can be continuously adjusted in the system, and if yes, perform the next step, otherwise, the packet scheduling slowdown process ends;
- the criterion for determining whether the rate can continue to be down-regulated is related to the service type. For example, for the CS service, the rate cannot be lowered. For the stream service, the rate reduction should be no lower than the guaranteed rate (the CN parameter brought in the AB assignment); For interactive class background services, the rate can be reduced to zero. Step 303: Perform rate reduction priority ordering on services in the system.
- the larger the margin the higher the priority of the drop rate, and the same margin is sorted according to the service QoS priority.
- Step 304 Downgrade the service rate with the highest rate of descending rate first;
- Step 305 Determine whether the remaining amount of the system hard resource is less than a minimum hard resource requirement threshold (Requirement- Hard) or whether the system soft capacity load is greater than a system soft congestion control threshold (CongestionThreshold_Sofl), and if yes, return to step 302, otherwise the packet scheduling slowdown The process ends.
- a minimum hard resource requirement threshold Requirement- Hard
- CongestionThreshold_Sofl system soft congestion control threshold
- the packet service rate in the system is downgraded step by step according to the derating rate priority until all packet service rates in the system are reduced to no longer fall.
- Figure 4 is an example of a traffic triggering packet scheduling process
- Step 401 the traffic measurement report decision
- Step 4 02 whether the traffic measurement triggers the service rate up-regulation, if yes, step 403 is performed, otherwise, step 404 is performed;
- Step 403 Determine whether the current service rate is up-regulated, and if yes, perform the next step, otherwise, end;
- Step 404 perform packet scheduling acceleration processing on the service (call the packet service acceleration process, see Figure 5); The purpose is to determine whether the current service has the maximum rate and whether it can be adjusted upwards. In another embodiment, the current service rate may not be up-regulated at this time, and the determination is performed in the packet scheduling acceleration process.
- Step 405 Whether the traffic measurement triggers the service rate reduction, if yes, step 405 is performed; step 406, determining whether the current service rate can be down-regulated, and if yes, performing step 406, otherwise, ending;
- step 407 the current service rate is lowered by one level or several levels.
- the current service refers to the corresponding service carried by the user that reports the traffic measurement report (triggered rate reduction); reports a measurement report, and the service decreases the rate.
- FIG. 5 is an example of a packet scheduling acceleration process in a service maintenance process
- Step 501 triggering a packet scheduling acceleration process
- Step 502 If the current service rate is increased by one level, whether the remaining amount of the system hard resource is less than the Requirement- Hard and the QoS priority of the system that is not decelerated is lower than the current service, if yes, the packet scheduling acceleration process End, otherwise, perform the next step;
- the system soft capacity load may also be used as a judgment condition, that is, whether the current service rate increases by one level, whether the system soft load is greater than CongestionThreshold_Soft, and the system has no deceleration QoS priority lower than the current
- the service of the service, or the system resource remaining amount and the system soft capacity load are simultaneously used as the judgment conditions, that is, whether the current system traffic rate rises one level later, the system hard resource remaining amount is less than the Requirement-Hard and the system soft capacity load is greater than the CongestionThreshold-Soft. There is no service in the system where the QoS priority can be lower than that of the current service.
- Step 503 Determine whether the remaining amount of the hard resource in the system is less than Requirement_Hard, and if yes, the packet scheduling acceleration process ends; otherwise, perform the next step;
- Step 504 Determine whether the soft load in the system is greater than NomialThreshold_Soft. If yes, the packet scheduling acceleration process ends; otherwise, perform the next step;
- Step 505 the current service rate is adjusted by one level or several levels;
- Step 506 Determine whether the remaining amount of the system hard resource is smaller than the minimum hard resource requirement threshold of the guaranteed QoS when the service is initially accessed, or whether the system soft load is greater than the system soft congestion control threshold CongestionThreshold_Soft, and if yes, step 508 is performed. Otherwise, the packet scheduling acceleration process ends;
- Step 507 the packet scheduling slowdown process triggered by the congestion control is invoked, as shown in FIG. 3.
- the packet scheduling slowdown process can also be triggered when the resource allocation of the service is increased.
- the current user will be rate-up. If the remaining amount of the hard resource is less than the Requirement-Hard after the up-regulation, the Qos can be lower through the congestion control rate-down process. The user's rate drops. For example: A 32Kbps user requests an increase rate, but the current load of the system is greater than the congestion control recovery threshold. If there is a 384Kbps service in the system, the service rate of 32Kbps can be raised to 128Kbps, and then the service rate of 384Kbps will be To 256Kbps.
- the method comprehensively considers the characteristics of the packet data service, the performance of the wireless communication system, the QoS of the packet data service carried in the wireless communication system, and the like, and can maximize the packet access system under the premise of ensuring system performance and user QoS. Capacity.
Landscapes
- Engineering & Computer Science (AREA)
- Quality & Reliability (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
- Data Exchanges In Wide-Area Networks (AREA)
Abstract
A packet dispatching method in the wireless communication system which bears the multi-user packet data service, can make a new user access the system when the system capacity is not sufficient. The method includes the following steps: the system distributes the resources (102) or increases the resources distribution of the service in a destination cell according to the hard resources demand amount of the service, if the resources distribution succeeds, the next step is performed (103); the system resources are determined whether to be sufficient or not according to the preset system resources threshold (105), if the system resources are notsufficient, the down adjusting rate process of the packet dispatching on the service in the system is performed (106).
Description
一种无线通讯系统中的分组调度方法 Packet scheduling method in wireless communication system
技术领域 Technical field
本发明涉及支持多用户分组数据业务的无线通讯系统。 The present invention relates to a wireless communication system supporting multi-user packet data services.
背景技术 Background technique
在支持分组数据业务的无线通讯系统中,分组业务的速率可伸缩性是很 大的。 如果系统负荷较轻时分组数据业务速率过小, 会减小系统吞吐量, 浪 费系统资源; 如果系统负荷较重时分组数据业务速率过大, 会导致系统资源 耗尽, 新用户无法接入, 系统中不同用户业务服务质量(Quality of Service, 以下筒称 QoS ) 不均衡等问题。 一般情况下, 在系统负荷低的时候, 单用 户分组数据业务的实际速率可以较大, 以便有效利用系统资源, 为用户提供 更好的 QoS; 在系统负荷高的时候, 单用户分组数据业务的实际速率可能较 小, 以便保证所有用户的正常通讯及系统性能。 在现有的相关技术方案中, 一般在用户发起呼叫但系统资源不足导致呼叫失败时才认为系统拥塞,从而 触发分组数据业务速率下调以释放部分资源。此类方案可以充分利用系统资 源,但缺点是在系统高负荷时会出现大量呼损, 因为资源分配失败就意味着 此次呼叫已经失败了, 此时认为系统拥塞已经迟了。 In a wireless communication system supporting packet data services, the rate scalability of packet services is very large. If the system data load is too light, the packet data service rate is too small, which will reduce the system throughput and waste system resources. If the packet data service rate is too large when the system load is heavy, the system resources will be exhausted and new users cannot access. The problem that the quality of service (Quality of Service, hereinafter referred to as QoS) of different users in the system is unbalanced. Under normal circumstances, when the system load is low, the actual rate of single-user packet data services can be large, so as to effectively utilize system resources and provide better QoS for users; when the system load is high, single-user packet data services The actual rate may be small to ensure proper communication and system performance for all users. In the related related technical solutions, the system is generally considered to be congested when the user initiates a call but the system resources are insufficient to cause the call to fail, thereby triggering the packet data service rate to be lowered to release part of the resources. Such a scheme can make full use of system resources, but the disadvantage is that a large amount of call loss occurs when the system is under heavy load, because the failure of resource allocation means that the call has failed, and the system congestion is considered to be late.
如何根据系统负荷合理控制分组数据业务的实际速率以保证新用户可 正常接入、 原用户 QoS得以保证并最大化地利用系统资源是现有技术尚未 解决的问题。 How to properly control the actual rate of packet data services according to system load to ensure that new users can access normally, the original user QoS can be guaranteed and the system resources are maximized is an unsolved problem in the prior art.
发明内容 Summary of the invention
本发明所要解决的技术问题是提供一种无线通讯系统中的分组调度方 法, 在承载多用户分组数据业务的无线通讯系统中, 当系统容量不足时, 使 新用户仍能接入系统。 The technical problem to be solved by the present invention is to provide a packet scheduling method in a wireless communication system. In a wireless communication system carrying a multi-user packet data service, when the system capacity is insufficient, the new user can still access the system.
为了解决上述技术问题,本发明提供了一种无线通讯系统中的分组调度 方法, 包括以下步骤:
( a ) 系统以所述业务的硬资源需求量在目标小区进行资源分配或增加 业务的资源分配时, 如果资源分配成功, 则执行下一步; In order to solve the above technical problem, the present invention provides a packet scheduling method in a wireless communication system, which includes the following steps: (a) when the system allocates resources to the target cell or increases the resource allocation of the service with the hard resource requirement of the service, if the resource allocation is successful, the next step is performed;
( b )根据预先设定的系统资源门限判断系统资源是否足够, 如果系统 资源不足, 则对系统中的业务进行分组调度降速处理。 (b) judging whether the system resources are sufficient according to the preset system resource threshold, and if the system resources are insufficient, performing packet scheduling and speed reduction processing on the services in the system.
进一步地, 上述方法还可具有以下特点: 在所述步骤(b ) 中, 所述根 据预先设定的系统资源门限判断系统资源是否足够,是进行以下三种判断中 的任意一种: , Further, the above method may further have the following features: In the step (b), determining whether the system resource is sufficient according to a preset system resource threshold is performed by any one of the following three determinations:
判断系统硬资源剩余量是否小于预先设定的最小硬资源需求门限; 判断系统软容量负荷是否大于预先设定的系统软容量拥塞控制门限; 判断是否满足以下两个条件中的任意一个: 系统硬资源剩余量是否小于 预先设定的最小硬资源需求门限,系统软容量负荷是否大于预先设定的系统 软容量拥塞控制门限; Determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource requirement threshold; determining whether the system soft capacity load is greater than a preset system soft capacity congestion control threshold; determining whether one of the following two conditions is met: Whether the remaining amount of resources is less than a preset minimum hard resource demand threshold, and whether the system soft capacity load is greater than a preset system soft capacity congestion control threshold;
如果以上判断结果为是, 则系统资源足够, 否则, 系统资 '源不足。 If the above judgment result is yes, the system resources are sufficient, otherwise, the system resource 'source is insufficient.
进一步地, 上述方法还可具有以下特点: 所述最小硬资源需求门限根据 系统承载业务的类型确定, 为系统支持的各种业务最小硬资源需求的最大 值。 Further, the foregoing method may also have the following features: The minimum hard resource requirement threshold is determined according to the type of the system bearer service, and is the maximum value of the minimum hard resource requirement of various services supported by the system.
进一步地, 上述方法还可具有以下特点: 在所述步驟(a ) 中, 系统是 在收到业务建立请求或切换请求后以所述业务的最小硬资源需求量进行资 源分配。 Further, the above method may further have the following features: In the step (a), the system performs resource allocation with a minimum hard resource requirement of the service after receiving a service establishment request or a handover request.
进一步地, 上述方法还可具有以下特点: 在所述步骤(a ) 中, 如果资 源分配失败, 则所述业务进行资源抢占, 所述资源抢占包括以下步骤: Further, the foregoing method may further have the following features: In the step (a), if the resource allocation fails, the service performs resource preemption, and the resource preemption includes the following steps:
( a-1 )若新用户具有抢占能力, 判断系统中是否存在业务服务质量优 先级较低且可以被抢占的用户, 如果是, 则将系统中业务服务质量优先级最 低且可以被抢占的用户释放掉, 否则, 结束; (a-1) If the new user has the preemption capability, determine whether there is a user with a lower priority of the service quality and can be preempted. If yes, the user with the lowest priority of the service quality in the system and can be preempted Released, otherwise, ended;
( a-2 )若所述新用户未等待超时, 则给该新用户重新分配资源。
进一步地, 上述方法还可具有以下特点: 在所述步骤 -1 ) 中, 所述 判断系统中是否存在业务服务质量优先级较低且可以被抢占的用户,是先从 系统中业务服务质量优先级最低的用户开始判断,根据业务建立时无线接入 承载携带的核心网络参数, 判断该用户是否可被抢占, 如果不是, 则查找服 务质量优先级次低的用户进行判断。 (a-2) If the new user does not wait for a timeout, the new user is reassigned resources. Further, the foregoing method may further have the following features: In the step-1), whether the user with a lower priority of the service quality of the service and can be preempted in the determining system is prioritized by the service quality in the system. The user with the lowest level starts to judge whether the user can be preempted according to the core network parameters carried by the radio access bearer when the service is established. If not, the user with the lower priority of the service quality is judged.
进一步地, 上述方法还可具有以下特点: 所述步骤(b ) 中, 所述对系 统中的业务进行分组调度降速处理, 包括以下步驟: Further, the foregoing method may further have the following features: In the step (b), the packet scheduling and speed reduction processing of the service in the system includes the following steps:
( b-1 ) 判断系统中是否存在速率可下调的业务, 如果是, 则对系统中 的业务按照业务速率的下降余量大小进行排序,所述业务速率的下降余量是 指业务当前速率与业务最小速率之差, 否则, 结束; (b-1) determining whether there is a rate-downtable service in the system, and if so, sorting the services in the system according to the size of the falling rate of the service rate, where the falling rate of the service rate refers to the current rate of the service The difference in the minimum rate of service, otherwise, the end;
( b-2 )优先下调业务速率下降余量较大的业务的业务速率, 返回步骤 ( b-1 ) o (b-2) preferentially reduce the service rate of the service with a large drop in service rate, and return to step (b-1) o
进一步地, 上述方法还可具有以下特点: 在所述步骤(b-2 ) 中下调业 务速率之后, 先判断系统资源是否足够, 如果是, 分組调度降速处理结束, 否则再返回步骤(b-1 ) , 所述判断系统资源是否足够, 是进行以下三种判 断中的任意一种: Further, the foregoing method may further have the following features: after the service rate is lowered in the step (b-2), it is first determined whether the system resource is sufficient, and if so, the packet scheduling deceleration processing ends, otherwise the step returns to the step (b- 1), the determining whether the system resource is sufficient is to perform any one of the following three judgments:
判断系统硬资源剩余量是否小于预先设定的最小硬资源需求门限; Determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource requirement threshold;
判断系统软容量负荷是否大于预先设定的系统软容量拥塞控制门限; 判断是否满足以下两个条件中的任意一个: 系统硬资源剩余量是否小于 预先设定的最小硬资源需求门限,系统软容量负荷是否大于预先设定的系统 软容量拥塞控制门限; Determine whether the system soft load is greater than a preset system soft space congestion control threshold; determine whether one of the following two conditions is met: whether the system hard resource remaining amount is less than a preset minimum hard resource demand threshold, and the system soft capacity Whether the load is greater than a preset system soft capacity congestion control threshold;
如果以上判断结果为是, 则系统资源足够, 否则, 系统资源不足。 If the above judgment result is yes, the system resources are sufficient, otherwise, the system resources are insufficient.
进一步地, 上述方法还可具有以下特点: 在分组数据业务进行过程中, 定期对业务量进行监测, 并执行以下步骤: Further, the foregoing method may also have the following features: During the process of the packet data service, periodically monitor the traffic volume and perform the following steps:
( i )判断业务量测量是否触发业务速率上调, 如果是, 判断当前业务 速率如果可上调, 则对系统中的业务进行分组调度升速处理, 否则, 执行下 一步;
( ii )判断业务量测量触发业务速率下调且当前业务速率可下调时, 则 将当前业务速率下调一级或几级。 (i) determining whether the traffic measurement triggers the service rate up-regulation, and if yes, determining that the current service rate can be up-regulated, then performing packet scheduling acceleration processing on the services in the system; otherwise, performing the next step; (ii) When the traffic measurement trigger service rate is down-regulated and the current service rate is down, the current service rate is lowered by one or several levels.
进一步地, 上述方法还可具有以下特点: 在所述步骤(i ) 中, 所述对 系统中的业务进行分组调度升速处理时, 包括以下步骤: Further, the foregoing method may further have the following features: In the step (i), when the packet scheduling and speed-up processing is performed on the service in the system, the following steps are included:
( i-1 )判断如果速率上调一级后是否会出现系统硬资源剩余量小于最小 硬资源需求门限且系统中没有可降速的服务质量优先级较低的业务;或者判 断如果速率上调一级后是否会出现系统软容量负荷大于系统软容量拥塞控 制门限且系统中没有可降速的服务质量优先级较低的业务;或者判断如果速 率上调一级后是否会出现系统软容量负荷大于系统软容量拥塞控制门限和 系统硬资源剩余量小于最小硬资源需求门限中的任一种,且系统中没有可降 速的服务质量优先级较低的业务; 如果以上判断结果为是, 则结束, 否则, 执行下一步; (i-1) judging whether the system hard resource remaining amount is less than the minimum hard resource demand threshold and there is no service quality lower priority service in the system after the rate is adjusted one level; or if the rate is increased by one level After the system soft load is greater than the system soft capacity congestion control threshold and there is no service quality lower priority in the system; or if the system soft load is greater than the system soft if the rate is increased by one level The capacity congestion control threshold and the system hard resource residual amount are less than any of the minimum hard resource requirement thresholds, and there is no service with a lower priority for the service quality that can be decelerated in the system; if the above judgment result is yes, the process ends; otherwise, , perform the next step;
( ii-2 )如判断出系统中硬资源剩余量大于最小硬资源需求门限, 且系 统中软容量负荷小于软容量拥塞控制恢复门限,则将所述当前业务速率上调 一级或几级, 执行下一步, 否则分组调度升速流程结束; (ii-2) If it is determined that the remaining amount of the hard resource in the system is greater than the minimum hard resource demand threshold, and the soft load in the system is less than the soft congestion control recovery threshold, the current service rate is adjusted by one or more levels, and the execution is performed. One step, otherwise the packet scheduling acceleration process ends;
( ii-3 )判断系统硬资源剩余量是否小于预先设定的最小硬资源需求门 限或系统软容量负荷是否大于系统软容量拥塞控制门限, 如果是, 则对系统 中的业务进行分组调度降速处理, 否则, 分组调度升速流程结束。 (ii-3) determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource demand threshold or whether the system soft capacity load is greater than a system soft capacity congestion control threshold, and if so, performing packet scheduling slowdown on the service in the system Processing, otherwise, the packet scheduling acceleration process ends.
进一步地, 上述方法还可具有以下特点: 所述软容量拥塞控制门限与软 容量拥塞控制恢复门限之差大于等于各种业务速率上升一级可能带来的软 容量的增量。 Further, the foregoing method may further have the following feature: the difference between the soft congestion control threshold and the soft congestion control recovery threshold is greater than or equal to an increase in soft capacity that may be caused by a level of increase in various service rates.
本发明所要解决的另一技术问题是提供一种无线通讯系统中的分组调 度方法, 在承载多用户分组数据业务的无线通讯系统中,根据业务量需求动 态调整系统资源时,可以在保证原用户业务服务质量的前提下使系统资源占 用量较低。 Another technical problem to be solved by the present invention is to provide a packet scheduling method in a wireless communication system. In a wireless communication system carrying a multi-user packet data service, when the system resources are dynamically adjusted according to the traffic demand, the original user can be guaranteed. Under the premise of business service quality, system resources are occupied at a low level.
为了解决上述技术问题,本发明提供了一种无线通讯系统中对业务量监 测引起的分组调度方法, 包括以下步骤:
( A )判断业务量测量是否触发业务速率上调,如果是,则执行步骤( B ), 否则执行步骤(D ) ; In order to solve the above technical problem, the present invention provides a packet scheduling method caused by traffic volume monitoring in a wireless communication system, including the following steps: (A) determining whether the traffic measurement triggers the traffic rate up-regulation, and if so, performing step (B), otherwise performing step (D);
( B )判断如果该业务速率上调一级后是否会出现系统资源不足且系统 中没有可降速的服务质量优先级较低的业务, 如果是, 则结束, 否则执行下 一步', (B) judging whether there will be insufficient system resources after the service rate is upgraded by one level and there is no service with lower priority for the service quality in the system, if yes, then the process ends, otherwise the next step is performed,
( C )如判断出系统中硬资源剩余量大于最小硬资源需求门限, 且系统 中软容量负荷小于软容量拥塞控制恢复门限,则将所述当前业务速率上调一 级或几级, Μ于下一步, 否则, 结束; (C) If it is determined that the remaining amount of the hard resource in the system is greater than the minimum hard resource demand threshold, and the soft load in the system is less than the soft congestion control recovery threshold, the current service rate is adjusted by one or several levels, next to the next step. , otherwise, end;
( D )判断业务量测量触发业务速率下调且当前业务速率可下调, 则将 当前业务速率下调一级或几级。 (D) If the traffic measurement trigger service rate is lowered and the current service rate is down, the current service rate is lowered by one or several levels.
进一步地, 上述方法还可具有以下特点: 在所述步骤(B ) 中, 所述判 断如果该业务速率上调一级后是否会出现系统资源不足且系统中没有可降 速的服务质量优先级较低的业务, 是进行以下三种判断中的任意一种: Further, the foregoing method may further have the following features: In the step (B), the determining whether there is insufficient system resources after the service rate is adjusted one level and the service quality priority in the system is not slowed down is higher. A low business is one of the following three judgments:
判断如果速率上调一级后是否会出现系统硬资源剩余量小于最小硬资 源需求门限且系统中没有可降速的服务质量优先级较低的业务; Determining whether the system hard resource remaining amount is less than the minimum hard resource demand threshold and there is no service quality lower priority service in the system if the rate is increased by one level;
或者判断如果速率上调一级后是否会出现系统软容量负荷大于系统软 容量拥塞控制门限且系统中没有可降速的服务质量优先级较低的业务; Or determining whether the system soft capacity load is greater than the system soft space congestion control threshold and the service quality with lower priority is not available in the system if the rate is increased by one level;
或者判断如果速率上调一级后是否会出现系统软容量负荷大于系统软 容量拥塞控制门限和系统硬资源剩余量小于最小硬资源需求门限中的任一 种, 且系统中没有可降速的服务盾量优先级较低的业务。 Or determine whether there is any one of the system soft capacity load greater than the system soft capacity congestion control threshold and the system hard resource residual amount is less than the minimum hard resource demand threshold if the rate is adjusted one level, and there is no service shield that can be slowed down in the system. A business with a lower priority.
进一步地, 上述方法还可具有以下特点: 在所述步骤(C ) 中, 对所述 当前业务速率进行上调后,判断系统硬资源剩余量是否小于预先设定的最小 硬资源需求门限或系统软容量负荷是否大于系统软容量拥塞控制门限,如果 是, 则对系统中的业务进行分组调度降速处理, 否则, 分组调度升速流程结 束。 Further, the foregoing method may further have the following features: In the step (C), after the current service rate is adjusted, determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource requirement threshold or system soft Whether the capacity load is greater than the system soft capacity congestion control threshold, and if so, the packet scheduling and speed reduction processing is performed on the services in the system; otherwise, the packet scheduling acceleration process ends.
进一步地, 上述方法还可具有以下特点: 在所述步骤(A ) 中, 在执行
步驟(B )之前, 或者在所述步骤(C ) 中, 判断当前业务速率是否可上调, 如果是, 继续执行, 否则, 结束。 - 进一步地, 上述方法还可具有以下特点: 所述软容量拥塞控制门限与软 容量拥塞控制恢复门限之差大于等于各种业务速率上升一级可能带来的软 容量的增量。 Further, the above method may further have the following features: In the step (A), performing Before step (B), or in the step (C), it is judged whether the current service rate can be up-regulated, and if so, the execution continues, otherwise, it ends. Further, the foregoing method may further have the following feature: the difference between the soft congestion control threshold and the soft congestion control recovery threshold is greater than or equal to an increase in soft capacity that may be caused by a level of increase in various service rates.
本发明通过五个分组业务相关处理流程基本可以解决这种由于系统中 分组业务速率太高而导致新业务呼损等问题。由于本发明综合考虑了分组数 据业务的特性、无线通讯系统的性能、承载于无线通讯系统中分组数据业务 的 QoS等因素, 可以在保证系统性能和用户 QoS的前提下最大限度地提高 分组接入系统的容量。 The invention can basically solve the problem that the new service call loss is caused by the packet service rate in the system is too high through the five packet service related processing flows. Since the present invention comprehensively considers the characteristics of the packet data service, the performance of the wireless communication system, and the QoS of the packet data service carried in the wireless communication system, the packet access can be maximized under the premise of ensuring system performance and user QoS. The capacity of the system.
附图概述 BRIEF abstract
图 1是业务初始接入时硬资源分配流程示例图; FIG. 1 is a diagram showing an example of a hard resource allocation process when an initial service is accessed;
图 2是业务建立时的资源抢占流程示例图; 2 is a diagram showing an example of a resource preemption process when a service is established;
图 3是拥塞控制触发的分组调度降速流程示例图; 3 is a diagram showing an example of a packet scheduling slowdown process triggered by congestion control;
图 4是业务量触发分组调度流程示例图; 4 is an exemplary diagram of a traffic triggering packet scheduling process;
图 5是业务保持过程中分组调度升速流程示例图。 FIG. 5 is a diagram showing an example of a packet scheduling acceleration process in a service maintenance process.
本发明的较佳实施方式 Preferred embodiment of the invention
本发明针对承载多用户分组数据业务的无线通讯系统中系统容量不足 可能导致新用户无法接入系统、 系统中原用户业务 QoS无法保证等问题提 出一种有效解决方法。 无线通讯系统中容量不足可能是由硬资源(比如码资源、 时隙资源)受 限导致的, 也可能是由于软资源(比如功率资源、 干扰)受限导致的。 因此, 本发明对系统性能参数监测引起的分组调度方法分为新用户接入系统时的 资源请求阶段处理流程和系统资源不足时原有用户调度阶段处理流程。硬资 源受限问题主要放在资源请求阶段解决,软资源受限问题主要放在业务保持
过程中的原有用户的调度阶段解决。 为此, 需要预先设定几个参数, 包括: 业务初始接入时保证 QoS的最小硬资源需求(Requirement—Hard )、 系统软 容量拥塞控制门限(CongestionThreshold_Soft ) 、 系统软容量拥塞控制恢复 门限( NomialThreshold一 Soft ) 。 这些参数可以通过无线通讯系统操作维护 平台静态配置。 其中: . The invention provides an effective solution for the problem that the system capacity of the wireless communication system carrying the multi-user packet data service is insufficient, the new user cannot access the system, and the original user service QoS cannot be guaranteed in the system. Insufficient capacity in a wireless communication system may be caused by limited resources such as code resources and time slot resources, or may be caused by limited soft resources (such as power resources and interference). Therefore, the packet scheduling method caused by the system performance parameter monitoring is divided into a resource request phase processing flow when a new user accesses the system and an original user scheduling phase processing flow when the system resource is insufficient. The hard resource limitation problem is mainly solved in the resource request phase, and the soft resource limitation problem is mainly placed on the business maintenance. The scheduling phase of the original user in the process is resolved. To this end, several parameters need to be preset, including: minimum hard resource requirement (Requirement-Hard) for guaranteeing QoS during initial service access, system soft congestion control threshold (CongestionThreshold_Soft), system soft congestion control recovery threshold (NomialThreshold) A Soft). These parameters can be statically configured through the wireless communication system operation and maintenance platform. among them: .
所述最小硬资源需求 (Requirement— Hard) 也称最小硬资源需求门限, 根 据系统承载业务的类型确定,一般为系统支持各种业务最小硬资源需求的最 大值,或者也可以是设定的其他值。例如,在 WCDMA系统中,保证 CS12.2k (电路交换)业务呼叫的最小硬资源需求是一个扩频因子( Spreading Factor, 以下筒称 SF )为 128的码资源; 假设 I/B类 PS业务的保证业务需求的速率 为 32K, 相当于最小硬资源需求是一个 SF为 64的码资源; S类 PS业务一 般保证速率签约为 64K, 相当于最小硬资源需求是一个 SF为 32的码资源。 而 SF为 32的码资源相当于 4个 SF为 128的码资源, 于是, 可以配置业务 初始接入时保证 QoS的最小硬资源需求 (Requirement— Hard)为一个 SF为 32 的码资源。 The minimum hard resource requirement (Requirement- Hard) is also called the minimum hard resource demand threshold, which is determined according to the type of the system bearer service, and is generally the maximum value of the system supporting the minimum hard resource requirement of various services, or may be other settings. value. For example, in a WCDMA system, the minimum hard resource requirement for guaranteeing a CS12.2k (circuit switched) service call is a code resource with a Spreading Factor (hereinafter referred to as SF) of 128; assuming I/B type PS services The rate of the service requirement is 32K, which is equivalent to the minimum hard resource requirement is a code resource with an SF of 64. The S-type PS service generally guarantees a rate of 64K, which is equivalent to a minimum hard resource requirement of a code resource with an SF of 32. The code resource with the SF of 32 is equivalent to four code resources with an SF of 128. Therefore, the minimum hard resource requirement (Requirement- Hard) for ensuring QoS during initial service access can be configured as a code resource with an SF of 32.
所述软容量拥塞控制门限( CongestionThreshold— Soft )主要为了防止系 统软容量负荷超过系统软容量最大值时影响系统的稳定运行,可根据系统性 能确定。 这里软容量指下行功率, 上行干扰。 The CongestionThreshold (Soft) threshold is mainly used to prevent the system soft capacity load from exceeding the maximum system soft capacity and affect the stable operation of the system. It can be determined according to system performance. Here, the soft capacity refers to downlink power and uplink interference.
所述软容量拥塞控制恢复门限(NoraialThreshold_Soft ) 主要为了防止 分组交换(Packet Switch, 以下简称 PS )业务升速过程中出现速率乒乓升降 问题, 其一般小于拥塞控制门限,拥塞控制门限与拥塞控制恢复门限之差大 于等于各种业务速率上升一級可能带来的软容量的增量。 例如: 小区下行 TCP最大发射功率为 41dBm, 设置小区下行的拥塞控制门限为 40dBm, 如 果 PS业务速率上调一级带来的 TCP增量小于 ldB, 则可以设置小区下行的 拥塞控制恢复门限为 39dBm,如果 PS速率上调一级带来的 TCP增量可能在 2 ~ 3dB之间, 则恢复门限应设置为 37dBm或更低。 The soft-capacity congestion control recovery threshold (NoraialThreshold_Soft) is mainly used to prevent the rate ping-pong lifting problem in the packet switching (Packet Switch, hereinafter referred to as PS) service acceleration process, which is generally smaller than the congestion control threshold, the congestion control threshold and the congestion control recovery threshold. The difference is greater than or equal to the increase in soft capacity that may result from a level of increase in various service rates. For example, the maximum downlink transmit power of the downlink TCP is 41 dBm, and the congestion control threshold of the downlink is set to 40 dBm. If the TCP increment caused by the PS traffic rate increase is less than ldB, the congestion control recovery threshold of the downlink downlink can be set to 39 dBm. If the TCP increment caused by the PS rate up one level may be between 2 and 3 dB, the recovery threshold should be set to 37 dBm or lower.
本发明的基本原理是: 提前将系统负荷降下来, 避免接纳拒绝(呼叫失 败)导致的呼损。 在每次业务硬资源申请结束后判断系统硬资源剩余量是否 小于 Requirement— Hard 或系统软容量负荷是否大于系统软容量拥塞控制门
限 CongestionThreshold—Soft, 如果是, 触发系统分組调度流程, 直到系统硬 资源 剩 余量 大于 Requirement— Hard 或 系 统软容量 负 荷 小 于 CongestionThreshold—Soft为止, 降低系统负荷, 保证新用户可以接入系统。 另外, 在用户进行分组数据业务时, 周期性地对系统性能参数进行监测, 并 进行分组调度, 以保证原用户的 Qos。 仍采用刚才的例子进行说明, 例如, 当小区当前的负荷大于拥塞控制门限( 40dBm )时,则触发拥塞控制流程(如 PS 业务降速率) , 以便释放部分资源来降低系统负荷; 当其他因素触发系 统升负荷(如业务量测量触发 PS业务速率上调)时,需要判断小区当前 TCP 的值是否大于拥塞控制恢复门限(39dBm或 37dBm ) , 如果是, 则不执行 升速率流程。 The basic principle of the present invention is: The system load is lowered in advance to avoid accepting the call loss caused by the rejection (call failure). After each service hard resource application is completed, it is determined whether the remaining amount of system hard resources is less than Requirement- Hard or whether the system soft-capacity load is greater than the system soft-capacity congestion control gate. CongestionThreshold—Soft, if yes, triggers the system packet scheduling process until the system hard resource remaining amount is greater than Requirement—hard or the system soft capacity load is less than CongestionThreshold—Soft, reducing system load and ensuring that new users can access the system. In addition, when the user performs packet data service, the system performance parameters are periodically monitored and packet scheduling is performed to ensure the original user's QoS. Still using the example just described, for example, when the current load of the cell is greater than the congestion control threshold (40dBm), the congestion control process (such as PS service rate reduction) is triggered to release part of the resources to reduce the system load; when other factors trigger When the system is overloaded (such as the traffic measurement triggers the PS service rate increase), it is necessary to determine whether the current TCP value of the cell is greater than the congestion control recovery threshold (39 dBm or 37 dBm). If yes, the rate-up process is not performed.
下面结合附图对技术方案的实施作进一步的详细描述: The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings:
图 1为业务初始接入小区的资源分配流程, 详细实施步骤如下: . 步骤 101, 系统收到业务建立请求或切换请求; FIG. 1 is a resource allocation process of a service initial access cell, and the detailed implementation steps are as follows: Step 101: The system receives a service establishment request or a handover request.
步驟 102, 系统以该业务最小硬资源需求量在目标小区进行资源分配; 在硬资源比较充裕时,并不局限于以该业务最小硬资源需求量进行资源 分配, 不过这样做实现筒单, 避免多次接纳尝试和降负荷流程。 Step 102: The system allocates resources in the target cell with the minimum hard resource requirement of the service; when the hard resources are relatively abundant, the system does not limit the resource allocation by using the minimum hard resource requirement of the service, but Multiple acceptance attempts and load shedding processes.
步骤 103, 如果资源分配成功, 执行步骤 105, 否则执行步骤 104; 步骤 104, 调用业务建立时的资源抢占流程, 见图 2; Step 103: If the resource allocation is successful, go to step 105, otherwise go to step 104; Step 104, invoke the resource preemption process when the service is established, as shown in Figure 2;
步骤 105,判断系统硬资源剩余量是否小于业务初始接入时保证 QoS的 最小硬资源需求门限 Requirement Jiard或系统软容量负荷是否大于系统软 容量拥塞控制门限 CongestionThreshold—Soft, 如果是, 则执行步骤 106, 否 则, 业务分配流程结束; Step 105: Determine whether the remaining amount of the system hard resource is smaller than the minimum hard resource requirement threshold Requirement Jiard or the system soft capacity load that guarantees the QoS when the service is initially accessed. If the system is not greater than the system soft congestion control threshold CongestionThreshold_Soft, if yes, go to step 106. Otherwise, the business distribution process ends;
在另一实施例中,也可以只判断系统硬资源剩余量是否小于最小硬资源 需求门限, 或只判断系统软容量负荷是否大于系统软容量拥塞控制门限。 In another embodiment, it may also be determined whether the remaining amount of the system hard resource is less than the minimum hard resource requirement threshold, or only whether the system soft capacity load is greater than the system soft capacity congestion control threshold.
步骤 106, 调用拥塞控制触发的分组调度降速流程, 见图 3。
图 2是业务建立时的资源抢占流程, 详细实施步骤如下: Step 106: Call the packet scheduling slowdown process triggered by the congestion control, as shown in FIG. 3. Figure 2 shows the resource preemption process when the service is established. The detailed implementation steps are as follows:
步骤 201 , 系统调用业务建立时的资源抢占流程; Step 201: The system invokes a resource preemption process when the service is established;
步骤 202, 判断新用户是否具有抢占能力, 如果是, 执行下一步, 否则' 本次资源抢占流程结束; Step 202: Determine whether the new user has the preemption capability. If yes, perform the next step, otherwise the current resource preemption process ends.
步骤 203,判断系统中是否存在业务 QoS优先级较低且可以被抢占的用 户, 如杲是, 执行下一步, 否则, 本次资源抢占流程结束; Step 203: Determine whether there is a user with a lower service QoS priority and can be preempted in the system, for example, perform the next step; otherwise, the current resource preemption process ends;
从系统中业务 Qos优先级最低的用户开始判断, 根据业务建立时 RAB (无线接入承载)指派里带过来的 CN (核心网络)参数, 判断该用户可以 抢占还是不可以抢占, 若该用户可以被抢占, 则释放该用户' 否则查找 Qos 优先级其次低的用户进行判断, 直到不存在业务 QoS低于所述新用户业务 且可被抢占的用户。 Judging from the user with the lowest service QoS priority in the system, according to the CN (Core Network) parameter brought in the RAB (Radio Access Bearer) assignment, it is determined whether the user can preempt or not preempt, if the user can be If the preemption is released, the user is released. Otherwise, the user whose second QoS priority is found is judged until there is no user whose service QoS is lower than the new user service and can be preempted.
步骤 204 , 将系统中业务 QoS优先级最低且可以被抢占的用户释放掉; 步驟 205 , 判断新用户是否等待超时, 如果是, 本次资源抢占流程结束, 否则, 执行下一步; Step 204: Release the user with the lowest service QoS priority in the system and can be preempted. Step 205: Determine whether the new user waits for a timeout. If yes, the current resource preemption process ends. Otherwise, perform the next step;
步骤 206, 给新用户重新分配资源, 如果重新分配资源时接纳该用户, 则本次资源抢占成功, 如果该用户被拒绝, 则释 ^此次呼叫, 本次资源抢占 流程结束。 Step 206: Re-allocate resources to the new user. If the user is accepted when the resource is re-allocated, the current resource preemption succeeds. If the user is rejected, the current call is terminated, and the current resource preemption process ends.
除本流程外, 本发明也可采用其他的各种资源抢占流程。 In addition to this process, the present invention may also employ other various resource preemption processes.
图 3是拥塞控制触发的分组调度降速流程示例; 3 is an example of a packet scheduling slowdown process triggered by congestion control;
步骤 301 , 拥塞控制触发分组调度降速流程; Step 301: The congestion control triggers a packet scheduling slowdown process;
步骤 302, 判断系统中是否存在速率可继续下调的业务, 如果是, 执行 下一步, 否则, 分组调度降速流程结束; Step 302: Determine whether there is a service whose rate can be continuously adjusted in the system, and if yes, perform the next step, otherwise, the packet scheduling slowdown process ends;
判断是否存在速率可继续下调的业务的标准具体与业务类型相关,比如 对于 CS业务, 速率不可下调; 对于流类业务, 速率下调应该不低于保证速 率 ( AB指派里带过来的 CN参数) ; 对于交互类背景类业务, 速率可降 为 0。
步驟 303 , 对系统中的业务进行降速率优先级排序; The criterion for determining whether the rate can continue to be down-regulated is related to the service type. For example, for the CS service, the rate cannot be lowered. For the stream service, the rate reduction should be no lower than the guaranteed rate (the CN parameter brought in the AB assignment); For interactive class background services, the rate can be reduced to zero. Step 303: Perform rate reduction priority ordering on services in the system.
按照业务速率的下降余量(业务当前速率与业务最小速率之差)大小进 行排序, 余量越大降速率优先级越高, 相同余量按照业务 QoS优先级进行 排序, QoS优先级越低降速率优先级越高。 According to the falling margin of the service rate (the difference between the current service rate and the service minimum rate), the larger the margin, the higher the priority of the drop rate, and the same margin is sorted according to the service QoS priority. The lower the QoS priority is. The higher the rate priority.
步骤 304, 将降速率优先级最高的业务速率下调一级; Step 304: Downgrade the service rate with the highest rate of descending rate first;
步骤 305 , 判断系统硬资源剩余量是否小于最小硬资源需求门限 (Requirement— Hard)或系统软容量负荷是否大于系统软容量拥塞控制门限 ( CongestionThreshold_Sofl ) , 如果是, 返回步驟 302, 否则分组调度降速 流程结束。 Step 305: Determine whether the remaining amount of the system hard resource is less than a minimum hard resource requirement threshold (Requirement- Hard) or whether the system soft capacity load is greater than a system soft congestion control threshold (CongestionThreshold_Sofl), and if yes, return to step 302, otherwise the packet scheduling slowdown The process ends.
按照降速率优先级对系统中分组业务速率进行逐级下调,直到系统中所 有分组业务速率都降到不可再降为止。 The packet service rate in the system is downgraded step by step according to the derating rate priority until all packet service rates in the system are reduced to no longer fall.
在另一实施例中,也可以只判断系统硬资源剩余量是否小于最小硬资源 需求门限, 或只判断系统软容量负荷是否大于系统软容量拥塞控制门限。 由于下调一个业务的一级速率后可能负荷还很高, 因此需要循环降速, 但是为了不会在每次循环降速都把所有业务速率降到最小,增加了对系统资 源的判断步骤,保证下调时只要能够满足接入的最低要求即可, 而不会将所 有业务调到最小。在另一个实施例中, 也可以在步骤 304将降速率优先级高 的业务速率下调后即返回步骤 302, 即一次将所有可以降速率的业务全部降 速。 In another embodiment, it may also be determined whether the remaining amount of the system hard resource is less than the minimum hard resource requirement threshold, or only whether the system soft capacity load is greater than the system soft capacity congestion control threshold. Since the first-level rate of a service is lowered, the load may be high, so the cycle speed reduction is required, but in order not to reduce all service rates to a minimum in each cycle, the judgment steps of the system resources are added to ensure that As long as you can meet the minimum requirements for access, you will not be able to minimize all services. In another embodiment, the service rate with a lower rate of priority is also lowered in step 304, and then the process returns to step 302, that is, all services that can be down-rate are decelerated at a time.
图 4是业务量触发分组调度流程示例; Figure 4 is an example of a traffic triggering packet scheduling process;
步骤 401, 业务量测量报告判决; Step 401, the traffic measurement report decision;
步骤 402, 业务量测量是否触发业务速率上调, 如果是, 执行步骤 403, 否则, 执行步骤 404; Step 4 02, whether the traffic measurement triggers the service rate up-regulation, if yes, step 403 is performed, otherwise, step 404 is performed;
步骤 403, 判断当前业务的速率是否可上调, 如果是, 则执行下一步, 否则, 结束; 步骤 404, 对该业务进行分组调度升速处理 (调用分组业务升速流程, 见图 5 ) ;
目的在于判断当前业务是否最大速率,是否还可上调。在另一实施例中, 也可此时不对当前业务速率是否可上调进行判断,而在分组调度升速流程中 进行判断。 Step 403: Determine whether the current service rate is up-regulated, and if yes, perform the next step, otherwise, end; Step 404, perform packet scheduling acceleration processing on the service (call the packet service acceleration process, see Figure 5); The purpose is to determine whether the current service has the maximum rate and whether it can be adjusted upwards. In another embodiment, the current service rate may not be up-regulated at this time, and the determination is performed in the packet scheduling acceleration process.
步骤 405, 业务量测量是否触发业务速率下调, 如果是, 执行步驟 405; 步骤 406, 判断当前业务速率是否可下调, 如果是, 执行步骤 406, 否 则, 结束; Step 405: Whether the traffic measurement triggers the service rate reduction, if yes, step 405 is performed; step 406, determining whether the current service rate can be down-regulated, and if yes, performing step 406, otherwise, ending;
步骤 407, 将当前业务速率下调一级或几级。 In step 407, the current service rate is lowered by one level or several levels.
这里当前业务是指上报业务量测量报告 (触发降速率)的用户承载的对 应业务; 上报一次测量报告, 该业务降一次速率。 The current service refers to the corresponding service carried by the user that reports the traffic measurement report (triggered rate reduction); reports a measurement report, and the service decreases the rate.
图 5是业务保持过程中分组调度升速流程示例; FIG. 5 is an example of a packet scheduling acceleration process in a service maintenance process;
步骤 501, 分组调度升速流程触发; Step 501: triggering a packet scheduling acceleration process;
步骤 502, 判断如果当前业务速率上调一级后是否会出现系统硬资源剩 余量小于 Requirement— Hard且系统中没有可降速的 QoS优先级低于当前业 务的业务, 如果是, 分组调度升速流程结束, 否则, 执行下一步; Step 502: If the current service rate is increased by one level, whether the remaining amount of the system hard resource is less than the Requirement- Hard and the QoS priority of the system that is not decelerated is lower than the current service, if yes, the packet scheduling acceleration process End, otherwise, perform the next step;
在其他实施例中, 也可将系统软容量负荷作为判断条件, 即判断当前业 务速率上升一级 以 后 的是否会出 现 系 统软容量 负 荷 大于 CongestionThreshold_Soft且系统中没有可降速的 QoS优先级低于当前业务 的业务,或者将系统资源剩余量和系统软容量负荷同时作为判断条件, 即判 断当前业务速率上升一级以后是否会出现系统硬资源剩余量小于 Requirement一 Hard且系统软容量负荷大于 CongestionThreshold—Soft且系统 中没有可降速的 QoS优先级低于当前业务的业务。 In other embodiments, the system soft capacity load may also be used as a judgment condition, that is, whether the current service rate increases by one level, whether the system soft load is greater than CongestionThreshold_Soft, and the system has no deceleration QoS priority lower than the current The service of the service, or the system resource remaining amount and the system soft capacity load are simultaneously used as the judgment conditions, that is, whether the current system traffic rate rises one level later, the system hard resource remaining amount is less than the Requirement-Hard and the system soft capacity load is greater than the CongestionThreshold-Soft. There is no service in the system where the QoS priority can be lower than that of the current service.
步骤 503 , 判断系统中硬资源剩余量是否小于 Requirement_Hard, 如果 是, 分组调度升速流程结束, 否则, 执行下一步; Step 503: Determine whether the remaining amount of the hard resource in the system is less than Requirement_Hard, and if yes, the packet scheduling acceleration process ends; otherwise, perform the next step;
步骤 504, 判断系统中软容量负荷是否大于 NomialThreshold— Soft, 如 果是, 分组调度升速流程结束, 否则, 执行下一步; Step 504: Determine whether the soft load in the system is greater than NomialThreshold_Soft. If yes, the packet scheduling acceleration process ends; otherwise, perform the next step;
步骤 505, 将当前业务速率上调一级或几级;
步骤 506,判断系统硬资源剩余量是否小于业务初始接入时保证 QoS的 最小硬资源需求门限 Requirement—Hard或系统软容量负荷是否大于系统软 容量拥塞控制门限 CongestionThreshold_Soft, 如果是, 则执行步骤 508, 否 则, 分组调度升速流程结束; Step 505, the current service rate is adjusted by one level or several levels; Step 506: Determine whether the remaining amount of the system hard resource is smaller than the minimum hard resource requirement threshold of the guaranteed QoS when the service is initially accessed, or whether the system soft load is greater than the system soft congestion control threshold CongestionThreshold_Soft, and if yes, step 508 is performed. Otherwise, the packet scheduling acceleration process ends;
步骤 507, 调用拥塞控制触发的分组调度降速流程, 见图 3。 Step 507, the packet scheduling slowdown process triggered by the congestion control is invoked, as shown in FIG. 3.
可见, 增加业务的资源分配时也可触发分組调度降速流程。 It can be seen that the packet scheduling slowdown process can also be triggered when the resource allocation of the service is increased.
系统中如果存在 Qos比较低且速率可降的业务,就会对当前用户进行速 率上调, 上调后如杲硬资源剩余量小于 Requirement—Hard, 则可再通过拥塞 控制降速率流程将 Qos比较低的用户的速率降下来。 比如: 一个 32Kbps的 用户请求升速率,但系统当前负荷大于拥塞控制恢复门限, 如果此时系统中 存在一个 384Kbps的业务, 则可以先把 32Kbps的业务速率升到 128Kbps, 然后把 384Kbps的业务速率将到 256Kbps。 If there is a service with a lower Qos and a lower rate, the current user will be rate-up. If the remaining amount of the hard resource is less than the Requirement-Hard after the up-regulation, the Qos can be lower through the congestion control rate-down process. The user's rate drops. For example: A 32Kbps user requests an increase rate, but the current load of the system is greater than the congestion control recovery threshold. If there is a 384Kbps service in the system, the service rate of 32Kbps can be raised to 128Kbps, and then the service rate of 384Kbps will be To 256Kbps.
工业实用性 Industrial applicability
本方法综合考虑了分组数据业务的特性、无线通讯系统的性能、承载于 无线通讯系统中分组数据业务的 QoS等因素, 可以在保证系统性能和用户 QoS的前提下最大限度地提高分组接入系统的容量。
The method comprehensively considers the characteristics of the packet data service, the performance of the wireless communication system, the QoS of the packet data service carried in the wireless communication system, and the like, and can maximize the packet access system under the premise of ensuring system performance and user QoS. Capacity.
Claims
1、 一种无线通讯系统中的分组调度方法, 包括以下步驟: A packet scheduling method in a wireless communication system, comprising the following steps:
( a ) 系统以所述业务的硬资源需求量在目标小区进行资源分配或增加 业务的资源分配时, 如果资源分配成功, 则执行下一步; (a) When the system allocates resources to the target cell or increases the resource allocation of the service with the hard resource requirement of the service, if the resource allocation is successful, the next step is performed;
资源不足, 则对系统中的业务进行分组调度降速处理。 If the resources are insufficient, the services in the system are scheduled and slowed down.
2、 如权利要求 1所述的方法, 其特征在于, 在所述步骤(b ) 中, 所述 根据预先设定的系统资源门限判断系统资源是否足够,是进行以下三种判断 中的任意一种: 2. The method according to claim 1, wherein in the step (b), determining whether the system resource is sufficient according to a preset system resource threshold is performing any one of the following three determinations. Kind:
判断系统硬资源剩余量是否小于预先 i殳定的最小硬资源需求门限; 判断系统软容量负荷是否大于预先设定的系统软容量拥塞控制门限; 判断是否满足以下两个条件中的任意一个: 系统硬资源剩余量是否小于 预先设定的最小硬资源需求门限,系统软容量负荷是否大于预先设定的系统 软容量拥塞控制门限; Determining whether the remaining amount of the system hard resource is less than the minimum hard resource demand threshold determined in advance; determining whether the system soft capacity load is greater than a preset system soft capacity congestion control threshold; determining whether one of the following two conditions is met: Whether the remaining amount of the hard resource is less than a preset minimum hard resource requirement threshold, and whether the system soft capacity load is greater than a preset system soft capacity congestion control threshold;
如果以上判断结果为是, 则系统资源足够, 否则, 系统资源不足。 If the above judgment result is yes, the system resources are sufficient, otherwise, the system resources are insufficient.
3、 如权利要求 2所述的方法, 其特征在于, 所述最小硬资源需求门限 根据系统承载业务的类型确定,为系统支持的各种业务最小硬资源需求的最 大值。 3. The method according to claim 2, wherein the minimum hard resource requirement threshold is determined according to a type of the system bearer service, and is a maximum value of a minimum hard resource requirement of various services supported by the system.
4、 如权利要求 2所述的方法, 其特征在于, 在所述步骤(a ) 中, 系统 是在收到业务建立请求或切换请求后以所述业务的最小硬资源需求量进行 资源分配。 , 4. The method according to claim 2, wherein in the step (a), the system allocates resources with a minimum hard resource requirement of the service after receiving a service establishment request or a handover request. ,
5、 如权利要求 2所述的方法, 其特征在于, 在所述步驟(a ) 中, 如果 资源分配失败, 则所述业务进行资源抢占, 所述资源抢占包括以下步骤: The method according to claim 2, wherein in the step (a), if the resource allocation fails, the service performs resource preemption, and the resource preemption includes the following steps:
( a-1 ) 若新用户具有抢占能力, 判断系统中是否存在业务服务盾量优 先级较低且可以被抢占的用户, 如果是, 则将系统中业务服务质量优先级最 低且可以被抢占的用户释放掉, 否则, 结束; (a-1) If the new user has the preemption capability, determine whether there is a user with a lower priority and can be preempted in the system. If yes, the service quality of the system has the lowest priority and can be preempted. The user releases it, otherwise, it ends;
( a-2 )若所述新用户未等待超时, 则给该新用户重新分配资源。
(a-2) If the new user does not wait for a timeout, the new user is reassigned resources.
6、 如权利要求 5所述的方法, 其特征在于, 在所述步骤(a-1 ) 中, 所 述判断系统中是否存在业务服务质量优先级较低且可以被抢占的用户,是先 从系统中业务服务质量优先级最低的用户开始判断,根据业务建立时无线接 入承载携带的核心网络参数, 判断该用户是否可被抢占, 如果不是, 则查找 服务质量优先级次低的用户进行判断。 The method according to claim 5, wherein in the step (a-1), whether the user with a lower priority of the service quality of the service and can be preempted is determined in the system. The user with the lowest priority of the service quality in the system starts to judge whether the user can be preempted according to the core network parameters carried in the radio access bearer when the service is established. If not, the user with the lower priority of the service quality is judged. .
7、 如权利要求 2所述的方法, 其特征在于, 所述步骤(b ) 中, 所述对 系统中的业务进行分组调度降速处理, 包括以下步骤: The method according to claim 2, wherein in the step (b), the packet scheduling and speed reduction processing of the service in the system includes the following steps:
( b-1 ) 判断系统中是否存在速率可下调的业务, 如果是, 则对系统中 的业务按照业务速率的下降余量大小进行排序,所述业务速率的下降余量是 指业务当前速率与业务最小速率之差, 否则, 结束; (b-1) determining whether there is a rate-downtable service in the system, and if so, sorting the services in the system according to the size of the falling rate of the service rate, where the falling rate of the service rate refers to the current rate of the service The difference in the minimum rate of service, otherwise, the end;
( b-2 )优先下调业务速率下降余量较大的业务的业务速率, 返回步骤 ( b-1 ) 0 (B-2) priority traffic rate drops down greater traffic service margin rate returns to the step (b-1) 0
8、 如权利要求 7所述的方法, 其特征在于, 在所述步骤(b-2 ) 中下调 业务速率之后,先判断系统资源是否足够,如果是,分组调度降速处理结束, 否则再返回步骤(b-1 ) , 所述判断系统资源是否足够, 是进行以下三种判 断中的任意一种: The method according to claim 7, wherein after the service rate is lowered in the step (b-2), it is first determined whether the system resource is sufficient, and if so, the packet scheduling deceleration processing ends, otherwise, the process returns. Step (b-1), wherein determining whether the system resource is sufficient is performing any one of the following three determinations:
判断系统硬资源剩余量是否小于预先设定的最小硬资源需求门限; 判断系统软容量负荷是否大于预先设定的系统软容量拥塞控制门限; 判断是否满足以下两个条件中的任意一个:系统硬资源剩余量是否小于 预先设定的最小硬资源需求门限,系统软容量负荷是否大于预先设定的系统 软容量拥塞控制门限; Determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource requirement threshold; determining whether the system soft capacity load is greater than a preset system soft capacity congestion control threshold; determining whether one of the following two conditions is met: the system is hard Whether the remaining amount of resources is less than a preset minimum hard resource demand threshold, and whether the system soft capacity load is greater than a preset system soft capacity congestion control threshold;
如果以上判断结果为是, 则系统资源足够, 否则, 系統资源不足。 ' If the above judgment result is yes, the system resources are sufficient, otherwise, the system resources are insufficient. '
9、 如权利要求 1所述的方法, 其特征在于, 在分组数据业务进行过程 中, 定期对业务量进行监测, 并执行以下步骤: 9. The method according to claim 1, wherein during the progress of the packet data service, the traffic volume is periodically monitored, and the following steps are performed:
( i ) 判断业务量测量是否触发业务速率上调, 如果是, 判断当前业务 速率如果可上调, 则对系统中的业务进行分组调度升速处理, 否则, 执行下 一步; (i) determining whether the traffic measurement triggers the service rate up-regulation, and if yes, determining that the current service rate can be up-regulated, then performing packet scheduling acceleration processing on the services in the system; otherwise, performing the next step;
( ii )判断业务量测量触发业务速率下调且当前业务速率可下调时, 则
将当前业务速率下调一级或几级。 (ii) when it is determined that the traffic measurement triggers the service rate downgrade and the current service rate can be lowered, Lower the current service rate by one or several levels.
10、 如权利要求 9所述的方法, 其特征在于, 在所述步骤(i ) 中, 所 述对系统中的业务进行分组调度升速处理时, 包括以下步骤: The method according to claim 9, wherein in the step (i), when the packet scheduling and speed-up processing is performed on the service in the system, the following steps are included:
( i-1 )判断如果速率上调一级后是否会出现系统硬资源剩余量小于最小 硬资源需求门限且系统中没有可降速的服务质量优先级较低的业务; (i-1) determining whether the system hard resource remaining amount is less than the minimum hard resource demand threshold and there is no service quality lower priority service in the system if the rate is increased by one level;
或者判断如果速率上调一级后是否会出现系统软容量负荷大于系统软 容量拥塞控制门限且系统中没有可降速的服务质量优先级较低的业务; Or determining whether the system soft capacity load is greater than the system soft space congestion control threshold and the service quality with lower priority is not available in the system if the rate is increased by one level;
或者判断如果速率上调一级后是否会出现系统软容量负荷大于系统软 容量拥塞控制门限和系统硬资源剩余量小于最小硬资源需求门限中的任一 种, 且系统中没有可降速的服务质量优先级较低的业务; Or determining whether the system soft capacity load is greater than the system soft capacity congestion control threshold and the system hard resource residual amount is less than the minimum hard resource demand threshold after the rate is adjusted one level, and there is no service quality that can be decelerated in the system. a lower priority business;
如果以上判断结果为是, 则结束, 否则, 执行下一步; If the above judgment result is yes, the process ends; otherwise, the next step is performed;
( ii-2 )如判断出系统中硬资源剩余量大于最小硬资源需求门限, 且系 统中软容量负荷小于软容量拥塞控制恢复门限,则将所述当前业务速率上调 一级或几级, 执行下一步, 否则分组调度升速流程结束; (ii-2) If it is determined that the remaining amount of the hard resource in the system is greater than the minimum hard resource demand threshold, and the soft load in the system is less than the soft congestion control recovery threshold, the current service rate is adjusted by one or more levels, and the execution is performed. One step, otherwise the packet scheduling acceleration process ends;
( ii-3 ) 判断系统硬资源剩余量是否小于预先设定的最小硬资源需求门 限或系统软容量负荷是否大于系统软容量拥塞控制门限, 如果是, 则对系统' 中的业务进行分组调度降速处理, 否则, 分组调度升速流程结束。 (ii-3) determining whether the remaining amount of the system hard resource is less than a preset minimum hard resource demand threshold or whether the system soft capacity load is greater than a system soft capacity congestion control threshold, and if so, performing packet scheduling on the service in the system Speed processing, otherwise, the packet scheduling acceleration process ends.
11、 如权利要求 1所述的方法,其特征在于,所述软容量拥塞控制门限 与软容量拥塞控制恢复门限之差大于等于各种业务速率上升一级可能带来 的软容量的增量。 The method according to claim 1, wherein the difference between the soft congestion control threshold and the soft congestion control recovery threshold is greater than or equal to an increase in soft capacity that may be caused by a level of increase in various service rates.
12、 一种无线通讯系统中对业务量监测引起的分组调度方法,包括以下 步骤: 12. A method for packet scheduling caused by traffic volume monitoring in a wireless communication system, comprising the following steps:
( A )判断业务量测量是否触发业务速率上调,如果是,则执行步骤( B ), 否则执行步骤(D ) ; (A) determining whether the traffic measurement triggers the traffic rate up-regulation, and if so, performing step (B), otherwise performing step (D);
( B )判断如果该业务速率上调一级后是否会出现系统资源不足且系统 中没有可降速的服务质量优先级较低的业务, 如果是, 则结束, 否则执行下 步; (B) judging whether there will be insufficient system resources after the service rate is upgraded by one level and there is no service with lower priority of service quality in the system, if yes, then the process ends; otherwise, the next step is performed;
( C )如判断出系统中硬资源剩余量大于最小硬资源需求门限, 且系统
中软容量负荷小于软容量拥塞控制恢复门限,则将所述当前业务速率上调一 级或几级, 执行下一步, 否则, 结束; (C) if it is determined that the remaining amount of hard resources in the system is greater than the minimum hard resource demand threshold, and the system If the medium-capacity load is less than the soft-capacity congestion control recovery threshold, the current service rate is adjusted by one or more levels, and the next step is performed; otherwise, the process ends;
( D )判断业务量测量触发业务速率下调且当前业务速率可下调, 则将 当前业务速率下调一级或几级。 (D) If the traffic measurement trigger service rate is lowered and the current service rate is down, the current service rate is lowered by one or several levels.
13、 如权利要求 12所述的方法, 其特征在于, 在所述步骤(B ) 中, 所述判断如果该业务速率上调一级后是否会出现系统资源不足且系统中没 有可降速的服务质量优先级较低的业务, 是进行以下三种判断中的任意一 种: The method according to claim 12, wherein in the step (B), the determining whether there is insufficient system resources after the service rate is adjusted one level and there is no service in the system that can be decelerated A business with a lower quality priority is one of the following three judgments:
判断如果速率上调一级后是否会出现系统硬资源剩余量小于最小硬资 源需求门限且系统中没有可降速的服务质量优先级较低的业务; Determining whether the system hard resource remaining amount is less than the minimum hard resource demand threshold and there is no service quality lower priority service in the system if the rate is increased by one level;
或者判断如果速率上调一级后是否会出现系统软容量负荷大于系统软 容量拥塞控制门限且系统中没有可降速的服务质量优先级较低的业务; 或者判断如果速率上调一级后是否会出现系统软容量负荷大于系统软 容量拥塞控制门限和系统硬资源剩余量小于最小硬资源需求门限中的任一 种, 且系统中没有可降速的服务质量优先级较低的业务。 Or determine whether the system soft capacity load is greater than the system soft capacity congestion control threshold and there is no service quality lower priority service in the system if the rate is increased by one level; or whether the rate will appear if the rate is increased by one level. The system soft capacity load is greater than any one of the system soft capacity congestion control threshold and the system hard resource residual amount is less than the minimum hard resource requirement threshold, and there is no service with a lower priority for the service quality that can be decelerated in the system.
14、 如权利要求 12所述的方法, 其特征在于, 在所述步骤(C ) 中, 对所述当前业务速率进行上调后,判断系统硬资源剩余量是否小于预先设定 的最小硬资源需求门限或系统软容量负荷是否大于系统软容量拥塞控制门 限, 如果是, 则对系统中的业务进行分组调度降速处理, 否则, 分组调度升 速流程结束。 The method according to claim 12, wherein in the step (C), after the current service rate is adjusted, it is determined whether the remaining amount of the system hard resource is less than a preset minimum hard resource requirement. Whether the threshold or system soft capacity load is greater than the system soft capacity congestion control threshold. If yes, the service in the system is scheduled to be slowed down. Otherwise, the packet scheduling acceleration process ends.
15、 如权利要求 12所述的方法, 其特征在于, 在所述步骤(A ) 中, 在执行步骤(B )之前, 或者在所述步骤(C ) 中, 判断当前业务速率是否 可上调, 如果是, 继续执行, 否则, 结束。 The method according to claim 12, wherein in the step (A), before performing step (B), or in the step (C), determining whether the current service rate is up, If yes, continue execution, otherwise, end.
16、 如权利要求 12所述的方法, 其特征在于, .所述软容量拥塞控制门 限与软容量拥塞控制恢复门限之差大于等于各种业务速率上升一级可能带 来的软容量的增量。
The method according to claim 12, wherein the difference between the soft congestion control threshold and the soft congestion control recovery threshold is greater than or equal to an increase in soft capacity that may be caused by a level of increase in various service rates. .
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2007/000590 WO2008101366A1 (en) | 2007-02-17 | 2007-02-17 | A packet dispatching method in wireless communication system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| PCT/CN2007/000590 WO2008101366A1 (en) | 2007-02-17 | 2007-02-17 | A packet dispatching method in wireless communication system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| WO2008101366A1 true WO2008101366A1 (en) | 2008-08-28 |
Family
ID=39709604
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| PCT/CN2007/000590 WO2008101366A1 (en) | 2007-02-17 | 2007-02-17 | A packet dispatching method in wireless communication system |
Country Status (1)
| Country | Link |
|---|---|
| WO (1) | WO2008101366A1 (en) |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110825520A (en) * | 2019-10-18 | 2020-02-21 | 山东省计算中心(国家超级计算济南中心) | Cluster top-speed elastic expansion method for realizing efficient resource utilization |
| CN118170107A (en) * | 2024-05-16 | 2024-06-11 | 青岛国创智能家电研究院有限公司 | Operating system scheduling method, device and system based on abstractable equipment function |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1520653A (en) * | 2001-06-25 | 2004-08-11 | ����ɭ�绰�ɷ�����˾ | Triggering Packet Data Rate Changes in Communication Systems |
| CN1671233A (en) * | 2004-03-15 | 2005-09-21 | 大唐移动通信设备有限公司 | Method for resource distribution and scheduling of non real-time service in mobile communication system |
| CN1681348A (en) * | 2004-04-08 | 2005-10-12 | 大唐移动通信设备有限公司 | Method for controlling non-realtime service data transmission of mobile terminal |
-
2007
- 2007-02-17 WO PCT/CN2007/000590 patent/WO2008101366A1/en active Application Filing
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN1520653A (en) * | 2001-06-25 | 2004-08-11 | ����ɭ�绰�ɷ�����˾ | Triggering Packet Data Rate Changes in Communication Systems |
| CN1671233A (en) * | 2004-03-15 | 2005-09-21 | 大唐移动通信设备有限公司 | Method for resource distribution and scheduling of non real-time service in mobile communication system |
| CN1681348A (en) * | 2004-04-08 | 2005-10-12 | 大唐移动通信设备有限公司 | Method for controlling non-realtime service data transmission of mobile terminal |
Cited By (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110825520A (en) * | 2019-10-18 | 2020-02-21 | 山东省计算中心(国家超级计算济南中心) | Cluster top-speed elastic expansion method for realizing efficient resource utilization |
| CN110825520B (en) * | 2019-10-18 | 2023-08-29 | 山东省计算中心(国家超级计算济南中心) | A cluster ultra-fast elastic scaling method to achieve efficient resource utilization |
| CN118170107A (en) * | 2024-05-16 | 2024-06-11 | 青岛国创智能家电研究院有限公司 | Operating system scheduling method, device and system based on abstractable equipment function |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US9414255B2 (en) | Packet flow control in a wireless communications network based on an indication contained in a packet | |
| US7453801B2 (en) | Admission control and resource allocation in a communication system supporting application flows having quality of service requirements | |
| KR100426357B1 (en) | Scheduling Method for QoS and Resource Management in Mobile Communication System | |
| CN100454903C (en) | A method of flow control on IUB interface | |
| US9743314B2 (en) | Communication network congestion control using allocation and retention priority | |
| RU2460120C2 (en) | Method and apparatus for managing resources in wireless communication device | |
| KR20070095905A (en) | Method and apparatus for flow control in cell change for high speed downlink packet access | |
| EP2854446B1 (en) | Access control method and device | |
| CN101572918B (en) | Method, device and system for allocating radio resources | |
| WO2005053329A1 (en) | Method of wireless channel resource allocation and rate control in a cdma communication system | |
| CN1761356A (en) | Method for converting types from public channel to dedicated channel in CDMA system | |
| WO2011032454A1 (en) | Method and equipment for allocating resource of shared network | |
| CN100421530C (en) | Access Method of Forward Compatible Terminal in Wireless Network | |
| EP1326463A1 (en) | Method and apparatus for packet transmission scheduling by performing load control functionality | |
| CN101626598A (en) | Method and system for managing transmission resource | |
| CN100514938C (en) | Method and system for controlling Iub interface band width resource in wireless network | |
| CN100369524C (en) | CDMA system up-bag dispatching method | |
| CN100581167C (en) | Resource access method and device thereof | |
| JP5410296B2 (en) | Power overload control method useful for high speed downlink packet access | |
| JP4348367B2 (en) | Communication system, communication unit, and capability preserving method inside | |
| CN102223668A (en) | Resource seizing method for long term evolution (LTE) system during service congestion | |
| US8116204B2 (en) | Scheduler | |
| WO2008101366A1 (en) | A packet dispatching method in wireless communication system | |
| CN100417290C (en) | A Congestion Control Method in the Third Generation Mobile Communication System | |
| Imbeni et al. | Quality of service management for mixed services in WCDMA |
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: 07711006 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: 07711006 Country of ref document: EP Kind code of ref document: A1 |