WO2009132557A1 - 缓冲区状态报告的处理方法及装置 - Google Patents

缓冲区状态报告的处理方法及装置 Download PDF

Info

Publication number
WO2009132557A1
WO2009132557A1 PCT/CN2009/071387 CN2009071387W WO2009132557A1 WO 2009132557 A1 WO2009132557 A1 WO 2009132557A1 CN 2009071387 W CN2009071387 W CN 2009071387W WO 2009132557 A1 WO2009132557 A1 WO 2009132557A1
Authority
WO
WIPO (PCT)
Prior art keywords
status report
service data
buffer status
service
buffer
Prior art date
Application number
PCT/CN2009/071387
Other languages
English (en)
French (fr)
Inventor
章校东
Original Assignee
华为技术有限公司
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 华为技术有限公司 filed Critical 华为技术有限公司
Publication of WO2009132557A1 publication Critical patent/WO2009132557A1/zh
Priority to US12/914,627 priority Critical patent/US8335169B2/en

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/12—Wireless traffic scheduling
    • H04W72/1221—Wireless traffic scheduling based on age of data to be sent
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/50—Allocation or scheduling criteria for wireless resources
    • H04W72/56—Allocation or scheduling criteria for wireless resources based on priority criteria
    • H04W72/566—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient
    • H04W72/569—Allocation or scheduling criteria for wireless resources based on priority criteria of the information or information source or recipient of the traffic information

Definitions

  • the present invention relates to wireless communication technologies, and in particular, to a processing technique of a Buffer Status Report (BSR).
  • BSR Buffer Status Report
  • the Long Term Evolution (LTE) project is a mobile communication architecture that the 3GPP, 3rd Generation Partnership Project is preparing to promote.
  • the base station performs unified scheduling on uplink data transmissions of different user equipments (UE, User Equipment), thereby improving channel utilization.
  • UE User Equipment
  • the user equipment needs to send an uplink scheduling information report to the base station, so that the base station can schedule the user equipment according to the uplink scheduling information report sent by the user equipment.
  • the triggering condition of the sending process of the buffer status report proposed by 3GPP LTE is that the service data with higher priority than all the data that has been waiting in the sending buffer of the user equipment arrives at the sending buffer of the user equipment. .
  • Embodiments of the present invention provide a method and apparatus for processing a buffer status report to save air interface resources.
  • a method for processing a buffer status report comprising: obtaining service data having a higher priority than all service data that has been waiting to be sent in a transmission buffer; and if a scheduling resource is available, prohibiting triggering a buffer status The sending process of the report.
  • a processing device for a buffer status report comprising: an obtaining unit, configured to obtain a ratio that is already being sent a service data of a high priority in the buffer waiting for all the service data to be sent; a buffer status report processing unit, configured to obtain, at the obtaining unit, all the service data that is waiting to be sent in the sending buffer After the high priority service data, if there is a scheduling resource available, the process of triggering the buffer status report is prohibited.
  • the buffer state may not be triggered.
  • the sending process of the report In the prior art, the user equipment triggers the transmission process of the buffer status report as long as it obtains the service data with higher priority than all the service data that has been waiting to be sent in the transmission buffer. Therefore, the embodiment of the present invention does not occupy the air interface resource frequently because the user equipment frequently triggers the transmission process of the buffer status report. Therefore, the embodiment of the present invention can save air interface with respect to the prior art. Resources.
  • FIG. 1 is a flowchart of a method for processing a buffer status report according to an embodiment of the present invention
  • FIG. 2 is a schematic view of Embodiment 1 of the present invention.
  • FIG. 3 is a schematic structural diagram of a device for processing a buffer status report according to an embodiment of the present invention.
  • S101 Obtaining business data having a higher priority than all service data that has been waiting to be transmitted in the transmission buffer.
  • the send buffer can be the send buffer of the Media Access Control (MAC) layer.
  • the sending buffer can temporarily store the service data waiting to be sent. Further, the service data of the same service waiting to be sent can be temporarily stored, or the service data of different services waiting to be sent can be temporarily stored.
  • MAC Media Access Control
  • Each service can be associated with a priority, and the priority of the service data is related to the priority of the service.
  • the priority of the service 1 is higher than the priority of the service 2, and the priority of the service 2 is higher than the priority of the service 3.
  • the priority of the service data of the service 1 is higher than the priority of the service data of the service 2
  • the priority of the service data of the service 2 is higher than the priority of the service data of the service 3.
  • the service data with the highest priority is sent first, even if the service data with low priority is temporarily stored in the transmission buffer for a long time, but if there is service data with high priority Arrival send buffer Areas, which are generally sent first, are also high priority business data.
  • the service type of the service data temporarily stored in the transmission buffer may be different, for example, a static scheduling service, a semi-static scheduling service, or a dynamic scheduling service.
  • the static scheduling means that the scheduling resources configured by the base station for the service are continuously valid, and the user equipment always uses the scheduling resources to send the service data of the service.
  • the semi-persistent scheduling means that the scheduling resources configured by the base station for the service can be continuously valid. However, when there are special cases, for example, when the configured scheduling resources cannot meet the actual requirements, the base station can configure new scheduling resources for the service again.
  • the dynamic scheduling means that the base station can configure scheduling resources for the service at any time, and does not need to configure a fixed scheduling resource for the service.
  • the scheduling resource herein may be a scheduling resource configured by the base station for the service corresponding to the service data with high priority mentioned in S101, or may be all the waiting for transmission in the sending buffer mentioned by the base station in S101. All or part of the scheduling resources configured by the service corresponding to the service data may also be the scheduling resources configured by the service corresponding to the service data with the higher priority mentioned by the base station in S101, and the base station is mentioned in S101. All or part of the scheduling resources configured by the service corresponding to all service data waiting to be sent in the buffer.
  • the transmission process of the buffer status report can be triggered.
  • the base station is obtained as S101.
  • the sending process of the zone status report Of course, if the service data of the service is received next time, and the scheduled resource configured by the base station is unavailable, the process of sending the buffer status report needs to be triggered.
  • the above buffer status report here can refer to the regular buffer status report (Regular BSR).
  • the service data with high priority mentioned in S101 may be semi-persistent scheduling service data.
  • the scheduling resource may be a semi-static scheduling resource.
  • the service corresponding to the high priority service data is a Voice over Internet Protocol (VoIP) service.
  • VoIP Voice over Internet Protocol
  • Embodiment 1 It is assumed that semi-persistent scheduling is applied to the uplink VoIP service, and the semi-persistent scheduling resource interval is configured to be 20 ms.
  • the base station allocates semi-static resources for the uplink VoIP service in the talking state. When the uplink VoIP service enters the Silence state, the base station releases the semi-static resources allocated to it. As shown in Figure 2, the upstream VoIP service is first muted, starting to enter the call state in subframe #5 and arriving at the first VoIP packet, after which a VoIP packet arrives every 20 ms. After determining that the uplink VoIP service enters the call state, the base station allocates a semi-static resource with an interval of 20 ms for the uplink VoIP service by using the uplink grant signaling in the subframe #13.
  • the user equipment After receiving the uplink authorization signaling, the user equipment saves the allocated semi-persistent scheduling resource, and considers that the semi-persistent scheduling resource is available every 20 ms thereafter. In this way, the data of the uplink VoIP service that arrives later will be prohibited from triggering the transmission process of the buffer status report.
  • the uplink VoIP service enters the mute state in subframe #1145.
  • the base station After detecting that the uplink VoIP service enters the mute state, the base station sends a signal for releasing the semi-static scheduling resource to the user equipment in subframe #1180. After receiving the signaling, the user equipment deletes the saved semi-persistent scheduling resource allocation information.
  • the uplink VoIP service enters the call state again, the transmission process of the buffer status report is triggered.
  • Embodiment 2 This embodiment is basically the same as Embodiment 1. The difference between the two embodiments is that After the user equipment deletes the saved semi-persistent scheduling resource allocation information, when the uplink VoIP service enters the call state again, if the scheduling resource allocated by the base station for other services is available, the transmission process of triggering the buffer status report may be prohibited, or The user equipment may use the scheduling resource allocated by the base station for other services to send the service data of the uplink VoIP service, that is, to preempt the scheduling resources of other services; if the scheduling resource allocated by the base station for other services is not available, the buffer status report is triggered. The sending process.
  • the scheduling resource allocated by the base station for other services may be a static scheduling resource, a semi-static scheduling resource, or a dynamic scheduling resource. Since the static scheduling resource and the semi-static scheduling resource are the sustainable scheduling resources allocated by the base station for the service, even if the uplink VoIP service preempts the static scheduling resource or the semi-static scheduling resource of other services, the data of other services can also be used. The subsequent resource configuration period is sent out, so that the impact on the data transmission of other services is not large. Therefore, when the user equipment needs to send the service data of the uplink VoIP service, but there is no available scheduling resource configured for the uplink VoIP service, the static scheduling resource or the semi-static scheduling resource for preempting other services for the uplink VoIP service is a preferred technical means.
  • the scheduling resource of the other service may be a scheduling resource of another service, or may be a scheduling resource of multiple other services.
  • the scheduling resource of one service may be randomly selected, or may be according to a certain A rule selects a scheduling resource, for example, a scheduling resource preemption of a service with the lowest priority.
  • the embodiment 2 is taken as an example. It is assumed that the priority of service 1 is higher than the priority of service 2, the priority of service 2 is higher than the priority of service 3, and the scheduling resources of services 1, 2, and 3 can be used for sending.
  • the scheduling resource of the priority 3 is selected for preemption.
  • each scheduling resource cannot satisfy the sending condition of the service data that needs to be sent currently, for example, the service that needs to be sent currently.
  • the data packets are relatively large, and each resource cannot be used independently to send service data packets.
  • some or all of these resources may be integrated, so that the integrated scheduling resources may satisfy the transmission conditions of the service data that needs to be sent currently.
  • the scheduling resources of Service 2 and Service 2 and Service 3 can be preempted, but each scheduling resource cannot be used independently for transmitting the service data packets of the uplink VoIP service.
  • the resources After the resources are integrated, they can be used to send service packets of the uplink VoIP service.
  • the scheduling resources of the services 1, 2, and 3 are preempted, and the scheduling resources are integrated, and the integrated scheduling resource is used to send the service data packet of the uplink VoIP service.
  • the trigger buffer status report specified by the existing protocol is also satisfied.
  • the other conditions of the transmission process may trigger the transmission process of the buffer status report according to the provisions of the protocol. For example, when the service data packet of the uplink VoIP service is obtained, if the base station has configured the semi-scheduled resource for the uplink VoIP service, but the size of the service data packet exceeds a preset threshold, the buffer status report may be triggered. process.
  • this technical means is optional.
  • the S101, the S102, and the execution body of the step of determining whether there is an available scheduling resource may be a user equipment, and specifically may be some or some functional modules of the MAC layer.
  • the base station may allocate scheduling resources to the user equipment according to a certain policy according to the scheduling resource situation and the buffer status report reported by all user equipments. Specifically, the base station generates The user equipment is notified to schedule the authorization information of the resource information, and then the authorization information is sent to the user equipment. After receiving the authorization information, the user equipment sends the service data by using the scheduling resources allocated by the base station.
  • the embodiment of the present invention provides a processing device for a buffer status report.
  • the method includes: an obtaining unit 301, configured to obtain service data with higher priority than all service data that has been waiting to be sent in a sending buffer; and a buffer status report processing unit 302, configured to obtain After the unit 301 obtains the service data with higher priority than all the service data that has been waiting to be sent in the transmission buffer, if there is available scheduling resource, the transmission process of triggering the buffer status report is prohibited.
  • the sending buffer can temporarily store the service data waiting to be sent. Further, the service data of the same service waiting to be sent can be temporarily stored, or the service data of different services waiting to be sent can be temporarily stored.
  • Each service can correspond to a priority.
  • the service data with the highest priority is sent first, even if the service data with low priority is temporarily stored in the send buffer for a long time.
  • the service data that is sent first is generally also the priority.
  • the type of service corresponding to the service data temporarily stored in the send buffer may be different, for example, It is a static scheduling service, or it can be a semi-static scheduling service, or it can be a dynamic scheduling service.
  • the static scheduling means that the scheduling resources configured by the base station for the service are continuously valid, and the user equipment always uses the scheduling resources to send the service data of the service.
  • the semi-persistent scheduling means that the scheduling resources configured by the base station for the service can be continuously valid. However, when there are special cases, for example, when the configured scheduling resources cannot meet the actual requirements, the base station can configure new scheduling resources for the service again.
  • the dynamic scheduling means that the base station can configure scheduling resources for the service at any time, and does not need to configure a fixed scheduling resource for the service.
  • the scheduling resource herein may be a scheduling resource configured by the base station for the service corresponding to the service data with the highest priority, or may be configured by the base station for the service corresponding to all the service data waiting to be sent in the sending buffer. All or part of the scheduling resources may be configured to include a scheduling resource configured by the base station for the service corresponding to the service data with the highest priority, and the base station configured for the service corresponding to all the service data waiting to be sent in the sending buffer. All or part of the scheduling resources.
  • the buffer status report processing unit 302 may trigger the buffering. The sending process of the punch status report.
  • the foregoing apparatus may further include: a determining unit 303, configured to determine, after the obtaining unit 301 obtains the service data with a higher priority than all the service data that has been waiting to be sent in the sending buffer, whether the available scheduling resource is available. And the judgment result is supplied to the buffer status report processing unit 302. Specifically, the determining unit 303 can determine whether there is a scheduling resource configured by the base station for the service corresponding to the service data with the high priority or whether the scheduling resource is available. If yes, the buffer status report processing unit 302 prohibits the triggering. The transmission process of the rush zone status report, otherwise, the buffer status report processing unit 302 triggers the transmission process of the buffer status report.
  • a determining unit 303 configured to determine, after the obtaining unit 301 obtains the service data with a higher priority than all the service data that has been waiting to be sent in the sending buffer, whether the available scheduling resource is available. And the judgment result is supplied to the buffer status report processing unit 302. Specifically, the determining unit 303 can determine whether there is
  • the determining unit 303 may determine whether there is all or part of the scheduling resources configured by the base station for the service corresponding to all the service data waiting to be sent in the sending buffer, or whether the scheduling resource is available, and if yes, buffering The zone status report processing unit 302 prohibits the transmission process of triggering the buffer status report. Otherwise, the buffer status report processing unit 302 triggers the transmission process of the buffer status report.
  • the determining unit 303 may determine whether there is a scheduling resource available for any one of the two scheduling resources, and if yes, the buffer status report processing unit 302 prohibits the sending of the buffer status report. Process, otherwise, buffer status report processing unit 302 triggers the transmission process of the buffer status report.
  • the obtaining unit 301 can obtain the scheduling resource configured by the base station for the service corresponding to the service data with the higher priority. If the obtaining unit 301 subsequently receives the service data of the service corresponding to the service data with the higher priority, and the base station provides the scheduling resource configured by the service corresponding to the service data with the higher priority, the buffer status report processing unit is available. 302 can still disable the transmission process of triggering the buffer status report.
  • the processing device of the buffer status report needs to request scheduling resources for the base station for a certain service at a certain time, if the obtaining unit 301 receives the service data of the service next time, the buffer zone is The processing device of the status report can use the scheduling resources that have been previously configured by the base station, and the buffer status report processing unit 302 does not have to trigger the transmission process of the buffer status report.
  • the acquisition unit 301 receives the service data of the service next time, and the scheduled resource configured by the base station is unavailable, the buffer status report processing unit 302 also needs to trigger the transmission process of the buffer status report.
  • each functional unit in the processing device of the buffer status report may be set or applied in the user equipment.
  • the obtaining unit 301 may be an antenna device of the user equipment, or the MAC layer may be responsible for receiving the upper layer sending.
  • the receiving means of the data, the operating means of the user equipment in the processing means of the buffer status report are the same as the working mode of the user equipment, and will not be described herein.
  • the user equipment after the user equipment receives the service data with higher priority than all the service data that has been waiting to be sent in the sending buffer, the user equipment does not simply trigger the sending of the buffer status report. Instead, it is necessary to determine if there are available scheduling resources, and if so, it is not necessary to trigger the transmission of the buffer status report. Compared with the prior art, in the embodiment of the present invention, the user equipment does not need to frequently trigger the sending process of the buffer status report, so that air interface resources can be saved.
  • the storage medium may be a magnetic disk, an optical disk, a read-only memory (ROM), or a random access memory (RAM).

Landscapes

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

Description

緩冲区状态报告的处理方法及装置
本申请要求于 2008 年 4 月 28 日提交中国专利局、 申请号为 200810095058.3、 发明名称为"緩冲区状态报告的处理方法及装置 "的中国专利 申请的优先权， 其全部内容通过引用结合在本申请中。
技术领域
本发明涉及无线通信技术， 尤其涉及緩冲区状态报告（BSR, Buffer Status Report ) 的处理技术。
背景技术
长期演进（ LTE, Long Term Evolution )项目是第三代合作伙伴计划（ 3GPP, 3rd Generation Partnership Project )组织准备推动的移动通信体系架构。 在现有 的 LTE系统中， 基站对不同用户设备 ( UE, User Equipment )的上行数据传输 进行统一调度，从而提高信道的利用率。在基站对用户设备进行调度的过程中 , 用户设备需要向基站发送上行调度信息报告， 这样，基站可以根据用户设备发 送的上行调度信息报告， 对用户设备进行调度。
在上行调度信息报告中， 最重要的是緩冲区状态报告。 目前， 3GPP LTE 提出的一种緩冲区状态报告的发送过程的触发条件是，比已在用户设备发送緩 冲区中等待的所有数据具有更高优先级的业务数据到达用户设备发送緩冲区。
但发明人在仔细研究现有技术后发现， 在某些场景下， 某个或某些业务的 数据会频繁的到达用户设备发送緩冲区。如果这些业务数据比已在用户设备发 送緩冲区中等待的所有数据的优先级都高，则根据上述的緩冲区状态报告的发 送过程的触发条件， 用户设备需要频繁的触发緩冲区状态报告的发送过程， 这 样就会导致用户设备因发送緩冲区状态报告而频繁的占用空口资源。
发明内容
本发明实施例提供緩冲区状态报告的处理方法及装置， 用以节省空口资 源。
一种緩冲区状态报告的处理方法， 包括： 获得比已在发送緩冲区中等待发 送的所有业务数据的优先级高的业务数据； 如果有可用的调度资源， 则禁止触 发緩冲区状态报告的发送过程。
一种緩冲区状态报告的处理装置， 包括： 获得单元， 用于获得比已在发送 緩冲区中等待发送的所有业务数据的优先级高的业务数据；緩冲区状态报告处 理单元，用于在所述获得单元获得所述比已在发送緩冲区中等待发送的所有业 务数据的优先级高的业务数据后，如果有可用的调度资源， 则禁止触发緩冲区 状态报告的发送过程。
在本发明的实施例中，用户设备在获得比已在发送緩冲区中等待发送的所 有业务数据的优先级高的业务数据后， 如果有可用的调度资源， 则可以不必触 发緩冲区状态报告的发送过程。 而在现有技术中， 用户设备只要获得比已在发 送緩冲区中等待发送的所有业务数据的优先级高的业务数据后，就触发緩冲区 状态报告的发送过程。 所以， 本发明实施例不会如现有技术那样， 即， 用户设 备因频繁触发緩冲区状态报告的发送过程而频繁的占用空口资源， 因此， 本发 明实施例相对于现有技术可以节省空口资源。
附图说明
图 1为本发明实施例的緩冲区状态报告的处理方法的流程图；
图 2为本发明的实施例 1的示意图；
图 3为本发明实施例的緩冲区状态报告的处理装置的结构示意图。
具体实施方式
首先对緩冲区状态报告的处理方法进行说明。 如图 1所示， 包括：
S101 :获得比已在发送緩冲区中等待发送的所有业务数据的优先级高的业 务数据。
发送緩冲区可以是指媒体接入控制 （MAC, Media Access Control )层的 发送緩冲区。 发送緩冲区中可以暂存等待发送的业务数据， 进一步来说， 可以 暂存等待发送的相同业务的业务数据，也可以暂存等待发送的不同业务的业务 数据。
每个业务都可以对应一个优先级， 业务数据的优先级与业务的优先级相 关， H没业务 1 的优先级高于业务 2的优先级， 业务 2的优先级高于业务 3 的优先级， 那么业务 1的业务数据的优先级高于业务 2的业务数据的优先级， 业务 2的业务数据的优先级高于业务 3的业务数据的优先级。一般来说， 在发 送緩冲区中，优先级最高的业务数据先被发送出去， 即使优先级低的业务数据 在发送緩冲区中暂存很长时间，但是如果有优先级高的业务数据到达发送緩冲 区， 则先被发送出去的一般也是优先级高的业务数据。
在发送緩冲区中暂存的业务数据对应的业务的类型可以不同， 例如， 可以 是静态调度业务， 也可以是半静态调度业务， 还可以是动态调度业务。
这里的静态调度是指，基站为业务配置的调度资源持续有效， 用户设备总 是使用上述调度资源发送上述业务的业务数据。
这里的半静态调度是指，基站为业务配置的调度资源可以持续有效，但有 特殊情况时， 例如配置的调度资源不能满足实际需要时，基站可以再次为业务 配置新的调度资源。
这里的动态调度是指，基站可以随时为业务配置调度资源， 不需为业务配 置固定的调度资源。
S102: 如果有可用的调度资源， 则禁止触发緩冲区状态报告的发送过程。 这里的调度资源可以是指基站为 S101中提到的优先级高的业务数据对应 的业务所配置的调度资源， 也可以是指基站为 S101中提到的在发送緩冲区中 等待发送的所有业务数据对应的业务所配置的所有或部分的调度资源，还可以 是指包括基站为 S101中提到的优先级高的业务数据对应的业务所配置的调度 资源和基站为 S101中提到的在发送緩冲区中等待发送的所有业务数据对应的 业务所配置的所有或部分的调度资源。
另夕卜，如果没有可用的调度资源，则可以触发緩冲区状态报告的发送过程。 在 S102之前， 还可以先执行这样一个步骤， 即， 判断是否存在可用的调 度资源。 例如， 可以判断是否存在基站为 S101中提到的优先级高的业务数据 对应的业务所配置的调度资源或者上述调度资源是否可用，如果是， 则禁止触 发緩冲区状态报告的发送过程， 否则， 触发緩冲区状态报告的发送过程。 再例 如， 可以判断是否存在基站为 S101中提到的在发送緩冲区中等待发送的所有 业务数据对应的业务所配置的所有或部分的调度资源或者上述调度资源是否 可用， 如果是， 则禁止触发緩冲区状态报告的发送过程， 否则， 触发緩冲区状 态报告的发送过程。再例如， 可以判断是否存在上述两种调度资源中任意一种 可用的调度资源， 如果是， 则禁止触发緩冲区状态报告的发送过程， 否则， 触 发緩冲区状态报告的发送过程。
进一步的， 触发緩冲区状态报告的发送过程之后， 可以获得基站为 S101 中提到的优先级高的业务数据对应的业务所配置的调度资源。如果后续还收到 S101中提到的优先级高的业务数据对应的业务的业务数据，且基站为 S101中 提到的优先级高的业务数据对应的业务所配置的调度资源可用，则仍然可以禁 止触发緩冲区状态报告的发送过程。也就是说，如果在某一次需要为某种业务 向基站请求调度资源， 那么如果下一次收到这种业务的业务数据时， 则可以使 用基站之前已配置的调度资源， 而不必再触发緩冲区状态报告的发送过程。 当 然，如果下一次收到这种业务的业务数据时，基站之前已配置的调度资源不可 用， 则还需要触发緩冲区状态报告的发送过程。这里上述的緩冲区状态报告可 以是指正规緩冲区状态报告（ Regular BSR )。
可选的， S101中提到的优先级高的业务数据可以是半静态调度业务数据， 相应的， 调度资源可以是半静态调度资源。 更具体的， 优先级高的业务数据对 应的业务为网络电话 ( VoIP, Voice over Internet Protocol )业务。
为使本领域技术人员更加清楚的理解本发明的实施例， 下面再以 VoIP业 务为例进行说明。
实施例 1 : 假定对上行 VoIP业务釆用半静态调度， 半静态调度资源间隔 配置为 20ms。 基站为通话（Talking )状态的上行 VoIP业务分配半静态资源。 当上行 VoIP业务进入静音（Silence )状态时， 则基站释放为其分配的半静态 资源。 如图 2所示， 上行 VoIP业务首先处于静音状态， 在子帧 #5开始进入通 话状态并到达第一个 VoIP分组， 此后， 每 20ms到达一个 VoIP分组。 基站在 确定上行 VoIP业务进入通话状态后， 通过上行授权信令在子帧 #13开始为上 行 VoIP业务分配间隔为 20ms的半静态资源。 用户设备在接收到该上行授权 信令后， 保存分配的半静态调度资源， 并认为此后每 20ms半静态调度资源可 用。 这样， 对于后续到达的上行 VoIP业务的数据都将被禁止触发緩冲区状态 报告的发送过程。
再假设上行 VoIP业务在子帧 #1145进入静音状态。基站在检测到上行 VoIP 业务进入静音状态后， 在子帧 #1180向用户设备发送释放半静态调度资源的信 令。 用户设备收到该信令后， 删除保存的半静态调度资源分配信息。 当上行 VoIP业务再次进入通话状态时， 则触发緩冲区状态报告的发送过程。
实施例 2:这个实施例与实施例 1基本相同。两个实施例的不同之处在于， 用户设备删除保存的半静态调度资源分配信息后， 当上行 VoIP业务再次进入 通话状态时，如果有基站为其他业务分配的调度资源可用， 则可以禁止触发緩 冲区状态报告的发送过程， 或者说， 用户设备可以使用基站为其他业务分配的 调度资源发送上行 VoIP业务的业务数据， 即， 抢占其他业务的调度资源； 如 果基站为其他业务分配的调度资源也不可用，则触发緩冲区状态报告的发送过 程。
在实际应用中，基站为其他业务分配的调度资源可以是静态调度资源， 也 可以是半静态调度资源，还可以是动态调度资源。 由于静态调度资源及半静态 调度资源都是基站为业务分配的可持续使用的调度资源， 所以， 即使为上行 VoIP 业务抢占了其他业务的静态调度资源或半静态调度资源， 其他业务的数 据也可以在后续的资源配置周期被发送出去， 这样，对其他业务的数据发送影 响并不大。 因此， 当用户设备需要发送上行 VoIP业务的业务数据、 但没有可 用的为上行 VoIP业务配置的调度资源时，为上行 VoIP业务抢占其他业务的静 态调度资源或半静态调度资源是优选的技术手段。
另外， 上述的其他业务的调度资源可以是指其他一个业务的调度资源， 也 可以是指其他多个业务的调度资源，在抢占调度资源时， 可以随机选择一个业 务的调度资源，也可以按照某种规则选择调度资源， 例如选择优先级最低的业 务的调度资源抢占。 还是以实施例 2为例， 假设业务 1 的优先级高于业务 2 的优先级， 业务 2的优先级高于业务 3的优先级， 且业务 1、 2及 3的调度资 源都可以用于发送上行 VoIP业务的业务数据， 当需要抢占业务 1、 2及 3的调 度资源时， 选择优先级 3的调度资源抢占。
在实现本发明实施例的过程中，虽然可能其他多个业务的调度资源可以被 抢占， 但也可能每个调度资源都不能满足当前需要发送的业务数据的发送条 件， 例如， 当前需要发送的业务数据包比较大， 每个资源都不能独立的用于发 送业务数据包。这种情况下，可以将这些资源中的一部分资源或全部资源整合， 这样， 整合后的调度资源就有可能满足当前需要发送的业务数据的发送条件。 还是以实施例 2为例， 4艮设业务 1的、 业务 2及业务 3的调度资源都可以被抢 占， 但每个调度资源都不能独立用于发送上行 VoIP业务的业务数据包， 而这 些调度资源整合后， 就可以用于发送上行 VoIP业务的业务数据包， 当需要发 送上行 VoIP业务的业务数据包时， 首先抢占业务 1、 2及 3的调度资源， 再将 这些调度资源整合，使用整合后的调度资源发送上行 VoIP业务的业务数据包。
需要说明的是， 在上述方法中， 当获得优先级高的业务数据时， 如果满足 了有对应于上述业务的调度资源的条件，但同时还满足了现有协议规定的触发 緩冲区状态报告的发送过程的其他条件， 则可以按照协议的规定， 触发緩冲区 状态报告的发送过程。 例如， 当获得上行 VoIP业务的业务数据包时， 如果基 站已经为上行 VoIP业务配置了半调度资源， 但上述业务数据包的大小超过了 预先设置的门限， 则可以触发緩冲区状态报告的发送过程。 当然， 这个技术手 段是可选的。
还需要说明的是， S101、 S102 及判断是否存在可用的调度资源的步骤的 执行主体可以是用户设备，具体来说，可以是 MAC层的某个或某些功能模块。
此外，基站获得用户设备触发的緩冲区状态报告后， 可以根据调度资源情 况和所有用户设备上报的緩冲区状态报告，按一定策略为用户设备分配调度资 源， 具体来说， 基站生成用于通知用户设备调度资源信息的授权信息， 再将授 权信息发送给用户设备。用户设备收到授权信息后，使用基站分配的调度资源， 发送业务数据。
上述方法可以由多种形式的装置来实现，对此， 本发明实施例提供了一种 緩冲区状态报告的处理装置。 如图 3所示， 包括： 获得单元 301 , 用于获得比 已在发送緩冲区中等待发送的所有业务数据的优先级高的业务数据；緩冲区状 态报告处理单元 302, 用于在获得单元 301获得上述比已在发送緩冲区中等待 发送的所有业务数据的优先级高的业务数据后，如果有可用的调度资源， 则禁 止触发緩冲区状态报告的发送过程。
发送緩冲区中可以暂存等待发送的业务数据， 进一步来说， 可以暂存等待 发送的相同业务的业务数据， 也可以暂存等待发送的不同业务的业务数据。
每个业务都可以对应一个优先级， 一般来说， 在发送緩冲区中， 优先级最 高的业务数据先被发送出去，即使优先级低的业务数据在发送緩冲区中暂存很 长时间，但是如果有优先级高的业务数据到达发送緩冲区， 则先被发送出去的 一般也是优先级高的业务数据。
在发送緩冲区中暂存的业务数据对应的业务的类型可以不同， 例如， 可以 是静态调度业务， 也可以是半静态调度业务， 还可以是动态调度业务。
这里的静态调度是指，基站为业务配置的调度资源持续有效， 用户设备总 是使用上述调度资源发送上述业务的业务数据。
这里的半静态调度是指，基站为业务配置的调度资源可以持续有效，但有 特殊情况时， 例如配置的调度资源不能满足实际需要时，基站可以再次为业务 配置新的调度资源。
这里的动态调度是指，基站可以随时为业务配置调度资源， 不需为业务配 置固定的调度资源。
这里的调度资源可以是指基站为上述优先级高的业务数据对应的业务所 配置的调度资源，也可以是指基站为上述在发送緩冲区中等待发送的所有业务 数据对应的业务所配置的所有或部分的调度资源，还可以是指包括基站为上述 优先级高的业务数据对应的业务所配置的调度资源和基站为上述在发送緩冲 区中等待发送的所有业务数据对应的业务所配置的所有或部分的调度资源。
另外，在获得单元 301获得上述比已在发送緩冲区中等待发送的所有业务 数据的优先级高的业务数据后， 如果没有可用的调度资源， 则緩冲区状态报告 处理单元 302可以触发緩冲区状态报告的发送过程。
此外， 上述装置还可以包括： 判断单元 303 , 用于在获得单元 301获得上 述比已在发送緩冲区中等待发送的所有业务数据的优先级高的业务数据后，判 断是否有可用的调度资源， 并将判断结果提供给緩冲区状态报告处理单元 302。 具体来说， 判断单元 303可以判断是否存在基站为上述优先级高的业务 数据对应的业务所配置的调度资源或者上述调度资源是否可用， 如果是， 则緩 冲区状态报告处理单元 302禁止触发緩冲区状态报告的发送过程， 否则，緩冲 区状态报告处理单元 302触发緩冲区状态报告的发送过程。再例如， 判断单元 303 可以判断是否存在基站为上述在发送緩冲区中等待发送的所有业务数据 对应的业务所配置的所有或部分的调度资源或者上述调度资源是否可用 ,如果 是， 则緩冲区状态报告处理单元 302禁止触发緩冲区状态报告的发送过程， 否 则， 緩冲区状态报告处理单元 302触发緩冲区状态报告的发送过程。 再例如， 判断单元 303 可以判断是否存在上述两种调度资源中任意一种可用的调度资 源，如果是， 则緩冲区状态报告处理单元 302禁止触发緩冲区状态报告的发送 过程， 否则， 緩冲区状态报告处理单元 302触发緩冲区状态报告的发送过程。 緩冲区状态报告处理单元 302触发緩冲区状态报告的发送过程之后，获得 单元 301 可以获得基站为上述优先级高的业务数据对应的业务所配置的调度 资源。如果获得单元 301后续还收到上述优先级高的业务数据对应的业务的业 务数据， 且基站为上述优先级高的业务数据对应的业务所配置的调度资源可 用，则緩冲区状态报告处理单元 302仍然可以禁止触发緩冲区状态报告的发送 过程。也就是说，如果上述緩冲区状态报告的处理装置在某一次需要为某种业 务向基站请求调度资源，那么如果获得单元 301下一次收到这种业务的业务数 据时， 则上述緩冲区状态报告的处理装置可以使用基站之前已配置的调度资 源， 而緩冲区状态报告处理单元 302不必再触发緩冲区状态报告的发送过程。 当然，如果获得单元 301下一次收到这种业务的业务数据时，基站之前已配置 的调度资源不可用，则緩冲区状态报告处理单元 302还需要触发緩冲区状态报 告的发送过程。
需要说明的是，上述緩冲区状态报告的处理装置中的各个功能单元可以设 置或应用在用户设备中， 例如， 获得单元 301可以是用户设备的天线装置， 也 可以是 MAC层负责接收高层发送的数据的接收装置， 上述緩冲区状态报告的 处理装置中的各个功能单元在用户设备的工作方式与在上述装置中的工作方 式相同， 这里不再赘述。
在本发明所有的实施例中，用户设备在收到比已在发送緩冲区中等待发送 的所有业务数据的优先级高的业务数据后，不是简单的触发緩冲区状态报告的 发送过程， 而是需要确定是否有可用的调度资源， 如果有， 则不必触发緩冲区 状态报告的发送过程。 相对于现有技术来说， 在本发明实施例中， 用户设备不 必频繁的触发緩冲区状态报告的发送过程， 因此可以节省空口资源。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程 , 是可以通过计算机程序来指令相关的硬件来完成，上述的程序可存储于一计算 机可读取存储介质中，该程序在执行时，可包括如上述各方法的实施例的流程。 其中，上述的存储介质可为磁碟、光盘、只读存储记忆体（Read-Only Memory, ROM )或随机存储记忆体（Random Access Memory, RAM )等。
上述仅是本发明的优选实施方式，应当指出，对于本技术领域的普通技术 人员来说， 在不脱离本发明原理的前提下， 还可以作出若干改进和润饰， 这些 改进和润饰也应视为本发明的保护范围。

Claims

权 利 要 求
1.一种緩冲区状态报告的处理方法， 其特征在于， 所述方法包括： 获得比已在发送緩冲区中等待发送的所有业务数据的优先级高的业务数 据；
如果有可用的调度资源， 禁止触发緩冲区状态报告的发送过程。
2.如权利要求 1所述的緩冲区状态报告的处理方法， 其特征在于， 所述获 得比已在发送緩冲区中等待发送的所有业务数据的优先级高的业务数据之后， 所述方法还包括：如果没有可用的调度资源，触发緩冲区状态报告的发送过程。
3.如权利要求 2所述的緩冲区状态报告的处理方法， 其特征在于， 所述触 发緩冲区状态报告的发送过程之后， 所述方法还包括：
获得基站为所述优先级高的业务数据对应的业务所配置的调度资源； 如果后续还收到所述优先级高的业务数据对应的业务的业务数据 ,且基站 为所述优先级高的业务数据对应的业务所配置的调度资源可用，禁止触发緩冲 区状态报告的发送过程。
4.如权利要求 1或 2所述的緩冲区状态报告的处理方法， 其特征在于， 所 述调度资源包括：
基站为所述优先级高的业务数据对应的业务所配置的调度资源； 和 /或， 基站为所述在发送緩冲区中等待发送的所有业务数据对应的业务所配置 的全部或部分的调度资源。
5.如权利要求 1至 4任一项所述的緩冲区状态报告的处理方法， 其特征在 于， 所述优先级高的业务数据为半静态调度业务数据， 所述调度资源为半静态 调度资源。
6.如权利要求 1至 4任一项所述的緩冲区状态报告的处理方法， 其特征在 于， 所述优先级高的业务数据对应的业务为网络电话 VoIP业务， 所述调度资 源为半静态调度资源。
7.—种緩冲区状态报告的处理装置， 其特征在于， 所述装置包括： 获得单元，用于获得比已在发送緩冲区中等待发送的所有业务数据的优先 级高的业务数据； 及，
緩冲区状态报告处理单元，用于在所述获得单元获得所述比已在发送緩冲 区中等待发送的所有业务数据的优先级高的业务数据后，如果有可用的调度资 源， 则禁止触发緩冲区状态报告的发送过程。
8.如权利要求 7所述的緩冲区状态报告的处理装置， 其特征在于， 所述緩 冲区状态报告处理单元还用于，在所述获得单元获得所述比已在发送緩冲区中 等待发送的所有业务数据的优先级高的业务数据后， 如果没有可用的调度资 源， 则触发緩冲区状态报告的发送过程。
9.如权利要求 7或 8所述的緩冲区状态报告的处理装置， 其特征在于， 所 述装置还包括：
判断单元，用于在所述获得单元获得所述比已在发送緩冲区中等待发送的 所有业务数据的优先级高的业务数据后， 判断是否有可用的调度资源， 并将判 断结果提供给所述緩冲区状态报告处理单元。
10.如权利要求 7或 8所述的緩冲区状态报告的处理装置， 其特征在于， 所述装置为用户设备。
PCT/CN2009/071387 2008-04-28 2009-04-21 缓冲区状态报告的处理方法及装置 WO2009132557A1 (zh)

Priority Applications (1)

Application Number Priority Date Filing Date Title
US12/914,627 US8335169B2 (en) 2008-04-28 2010-10-28 Method and apparatus for processing buffer status report

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CNA2008100950583A CN101572913A (zh) 2008-04-28 2008-04-28 缓冲区状态报告的处理方法及装置
CN200810095058.3 2008-04-28

Related Child Applications (1)

Application Number Title Priority Date Filing Date
US12/914,627 Continuation US8335169B2 (en) 2008-04-28 2010-10-28 Method and apparatus for processing buffer status report

Publications (1)

Publication Number Publication Date
WO2009132557A1 true WO2009132557A1 (zh) 2009-11-05

Family

ID=41232116

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2009/071387 WO2009132557A1 (zh) 2008-04-28 2009-04-21 缓冲区状态报告的处理方法及装置

Country Status (3)

Country Link
US (1) US8335169B2 (zh)
CN (1) CN101572913A (zh)
WO (1) WO2009132557A1 (zh)

Families Citing this family (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8873474B2 (en) * 2008-10-17 2014-10-28 Telefonaktiebolaget L M Ericsson (Publ) Method and mobile terminal providing priority-based uplink scheduling information
CN102264098B (zh) * 2010-05-31 2015-12-16 中兴通讯股份有限公司 一种缓冲区状态报告处理的方法和装置
US10349439B2 (en) * 2014-01-23 2019-07-09 Telefonaktiebolaget Lm Ericsson (Publ) Release of semi-persistent scheduling
CN106031224B (zh) 2014-03-19 2019-10-01 Lg电子株式会社 在无线通信系统中取消用于设备对设备传输的触发的缓冲器状态报告的方法和装置
CN105101428A (zh) * 2014-05-22 2015-11-25 中兴通讯股份有限公司 调度方法及系统、终端、发送方法、基站及其调度方法
CN108289065B (zh) * 2017-01-10 2022-01-14 华为技术有限公司 数据处理方法、装置和系统
CN111491329B (zh) * 2019-01-25 2023-08-01 华硕电脑股份有限公司 无线通信中触发上行链路缓冲区状态报告的方法和设备
CN112469078A (zh) * 2019-09-06 2021-03-09 财团法人工业技术研究院 在多跳无线网络中传输缓冲区状态报告的方法和网络设备
CN114449537A (zh) * 2020-10-30 2022-05-06 上海朗帛通信技术有限公司 一种被用于中继无线通信中的方法和装置
WO2023087254A1 (en) * 2021-11-19 2023-05-25 Lenovo (Beijing) Limited Method and apparatus for wireless communication

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1604685A (zh) * 2003-08-26 2005-04-06 三星电子株式会社 用于上行链路分组传输的调度分配的装置和方法
KR20080015693A (ko) * 2006-08-16 2008-02-20 삼성전자주식회사 이동통신시스템에서 단말의 버퍼 상태 보고 방법 및 장치

Family Cites Families (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR100571791B1 (ko) * 2003-02-21 2006-04-18 삼성전자주식회사 무선통신시스템 및 그 무선통신방법
EP1509011A3 (en) * 2003-08-16 2011-01-19 Samsung Electronics Co., Ltd. Method and apparatus for assigning scheduling for uplink packet transmission in a mobile communication system
DE602004012862T2 (de) * 2004-10-01 2009-04-09 Matsushita Electric Industrial Co., Ltd., Kadoma-shi Dienstgüte-bewusste Ablaufsteuerung für Aufwärtsübertragungen über zugeordneten Kanälen
JP4657178B2 (ja) * 2006-08-30 2011-03-23 富士通株式会社 規制端末管理装置
US20100254321A1 (en) * 2006-11-15 2010-10-07 Soeng-Hun Kim Method and appratus for buffer status report in mobile communication system
WO2008108143A1 (ja) * 2007-03-06 2008-09-12 Ntt Docomo, Inc. 移動局、基地局装置、無線通信システム及び通信制御方法
GB2452013A (en) * 2007-06-19 2009-02-25 Nec Corp Buffer status reporting from a mobile communications device
EP2028890B1 (en) * 2007-08-12 2019-01-02 LG Electronics Inc. Handover method with link failure recovery, wireless device and base station for implementing such method
CN101843157B (zh) * 2007-11-01 2013-10-30 爱立信电话股份有限公司 基于无线电承载配置的缓冲器状态报告
US8165066B2 (en) * 2008-01-03 2012-04-24 Innovative Sonic Limited Method and apparatus for performing buffer status reporting
EP2079202A1 (en) * 2008-01-08 2009-07-15 NEC Corporation Method for optimizing the triggering of the transmission of buffer status reporting (BSR) information
EP2245793B1 (en) * 2008-02-19 2015-05-27 Telefonaktiebolaget L M Ericsson (PUBL) Uplink scheduling in wireless networks
US8223708B2 (en) * 2008-06-10 2012-07-17 Innovative Sonic Limited Method and apparatus for handling scheduling information report
US8254333B2 (en) * 2008-09-22 2012-08-28 Htc Corporation Method for improving buffer status triggering mechanism in wireless communications system and related communication device
US20100271990A1 (en) * 2009-04-24 2010-10-28 Motorola, Inc. Method and apparatus for triggering buffer status reports with packet discarding
US8331394B2 (en) * 2010-02-16 2012-12-11 Motorola Mobility Llc Increasing scheduling request efficiency in a wireless communication system

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1604685A (zh) * 2003-08-26 2005-04-06 三星电子株式会社 用于上行链路分组传输的调度分配的装置和方法
KR20080015693A (ko) * 2006-08-16 2008-02-20 삼성전자주식회사 이동통신시스템에서 단말의 버퍼 상태 보고 방법 및 장치

Also Published As

Publication number Publication date
CN101572913A (zh) 2009-11-04
US20110038339A1 (en) 2011-02-17
US8335169B2 (en) 2012-12-18

Similar Documents

Publication Publication Date Title
WO2009132557A1 (zh) 缓冲区状态报告的处理方法及装置
JP6726355B2 (ja) Ｖ２ｘ送信のための改良された無線リソース選択およびセンシング
US11051275B2 (en) Semi-persistent resource allocation behavior for V2X transmissions
RU2700181C2 (ru) Принудительное высвобождение и управление доступом по типу устройство-устройство (d2d)
US8861474B2 (en) Prohibiting unnecessary scheduling requests for uplink grants
JP6207837B2 (ja) スケジューリングを制御するための方法及び装置
RU2432698C2 (ru) Способ и устройство для обеспечения предотвращения истощения восходящей линии связи в системе долговременного развития
TWI482523B (zh) 處理觸發暫存器狀態報告之計時器的方法及通訊裝置
KR101110186B1 (ko) 반-지속 스케줄링의 ｈａｒｑ 프로세스를 핸들링하는 방법 및 장치
WO2019228214A1 (zh) 一种无线承载建立、业务流的监测方法及装置
TWI424776B (zh) 暫存器狀態回報方法及通訊裝置
JP5297317B2 (ja) 無線リソース割当装置および無線リソース割当方法
WO2013170712A1 (zh) 一种数据调度方法及装置
WO2011020444A1 (zh) 一种缓存状态报告上报方法、中继节点、基站和系统
KR20130023263A (ko) 무선 네트워크에서 통신을 개시하기 위한 기법
WO2015100680A1 (zh) 一种控制数据传输的方法、装置以及系统
JP7493077B2 (ja) Ｓｌ ｓｒ／ｂｓｒ処理のための方法
TWI468061B (zh) 用以通信的方法及其無線電台
WO2012136087A1 (zh) 一种资源调度的方法及系统及一种终端
WO2020125573A1 (zh) 通信方法、装置、终端、网络设备及存储介质
WO2012083890A1 (zh) 一种数据发送方法和用户设备
WO2020088400A1 (zh) 资源调度方法、装置及设备
JP5480236B2 (ja) 通信方法及びそのための無線局
WO2011120469A2 (zh) 业务调度方法和基站
WO2017101121A1 (zh) 传输信令、传输数据和建立gtp隧道的方法及设备

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: 09737667

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: 09737667

Country of ref document: EP

Kind code of ref document: A1