WO2019191883A1 - 调度请求触发方法和终端设备 - Google Patents

调度请求触发方法和终端设备 Download PDF

Info

Publication number
WO2019191883A1
WO2019191883A1 PCT/CN2018/081645 CN2018081645W WO2019191883A1 WO 2019191883 A1 WO2019191883 A1 WO 2019191883A1 CN 2018081645 W CN2018081645 W CN 2018081645W WO 2019191883 A1 WO2019191883 A1 WO 2019191883A1
Authority
WO
WIPO (PCT)
Prior art keywords
scheduling request
terminal device
condition
status report
logical channel
Prior art date
Application number
PCT/CN2018/081645
Other languages
English (en)
French (fr)
Inventor
石聪
Original Assignee
Oppo广东移动通信有限公司
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 Oppo广东移动通信有限公司 filed Critical Oppo广东移动通信有限公司
Priority to CN201880037053.7A priority Critical patent/CN110720244B/zh
Priority to PCT/CN2018/081645 priority patent/WO2019191883A1/zh
Publication of WO2019191883A1 publication Critical patent/WO2019191883A1/zh

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management

Definitions

  • the present application relates to the field of communications, and more particularly, to a scheduling request triggering method and a terminal device.
  • a new radio (NR) system after the terminal device triggers a normal Buffer Status Report (BSR), it may be necessary to trigger a Scheduling Request (SR) or cancel the SR.
  • BSR Buffer Status Report
  • SR Scheduling Request
  • the delay requirement is high, especially the Ultra-Reliable and Low Latency Communication (URLLC) service.
  • URLLC Ultra-Reliable and Low Latency Communication
  • the mechanism for triggering the SR and canceling the SR at this stage cannot meet the delay in the NR system. Requirements.
  • the embodiment of the present application provides a scheduling request triggering method and a terminal device, which can flexibly trigger an SR and cancel an SR.
  • the embodiment of the present application provides a scheduling request triggering method, including:
  • the terminal device After the terminal device triggers the normal buffer status report, the terminal device determines to trigger the scheduling request or cancel the scheduling request under the first condition.
  • the terminal device may trigger the scheduling request or cancel the scheduling request under the first condition, thereby implementing flexible triggering scheduling request or flexible. Cancel the scheduling request.
  • the first condition is: an available uplink resource currently exists, and determining whether the available uplink resource can carry a logical channel that triggers the normal buffer status report. ;
  • the terminal device determines to cancel the scheduling request under the first condition, including:
  • the terminal device cancels the scheduling request at a first moment;
  • the terminal device cancels the scheduling request at the second moment.
  • the second time is later than the first time.
  • the terminal device can cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission and reducing signaling overhead caused by sending the scheduling request. Further, when the available uplink resources are not able to carry the logical channel that triggers the normal buffer status report, the terminal device may delay the cancellation of the scheduling request, thereby ensuring that the network device can learn the cache information for the terminal device, and avoid the network device scheduling inappropriate. resource of.
  • the first time and/or the second time is a media access control protocol data unit (Media Access) when the terminal device receives an uplink resource authorization.
  • Control Protocol Data Unit (MAC PDU) One of the group packet and MAC PDU transmission.
  • the terminal device can flexibly cancel the scheduling request at multiple points in time.
  • the method before the terminal device determines that the scheduling request is canceled under the first condition, the method further includes:
  • the terminal device triggers the scheduling request under a second condition.
  • the second condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in an off state;
  • a logical channel that triggers the normal cache status report can trigger a scheduling request.
  • the first condition is: determining whether the scheduling request is triggered by a third condition
  • the terminal device determines to cancel the scheduling request under the first condition, including:
  • the terminal device cancels the scheduling request at a third moment
  • the terminal device cancels the scheduling request at the fourth moment.
  • the third condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in an off state;
  • a logical channel that triggers the normal cache status report can trigger a scheduling request.
  • the fourth moment is later than the third moment.
  • the terminal device may cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission, and reducing signaling overhead caused by sending the scheduling request. Further, when the scheduling request is not triggered by the third condition, the terminal device may delay the cancellation of the scheduling request, thereby ensuring that the network device can learn the cache information for the terminal device, and prevent the network device from scheduling the inappropriate resource.
  • the third time and/or the fourth time is when the terminal device receives the uplink resource authorization, the MAC PDU group packet, and the MAC PDU is sent.
  • the terminal device receives the uplink resource authorization, the MAC PDU group packet, and the MAC PDU is sent.
  • the terminal device receives the uplink resource authorization, the MAC PDU group packet, and the MAC PDU is sent.
  • the terminal device can flexibly cancel the scheduling request at multiple points in time.
  • the first condition is: the current available uplink resource is available, and the fourth condition for triggering the scheduling request is met, and determining whether the normal buffer status report is heavy The timer is triggered by a timeout;
  • the terminal device determines that the scheduling request is triggered under the first condition, and includes:
  • the current uplink resource is available, and the fourth condition for triggering the scheduling request is met. If the normal buffer status report is triggered by the retransmission timer, the terminal device determines that the scheduling request is not triggered; or
  • the current uplink resource is available, and the fourth condition for triggering the scheduling request is met. If the normal buffer status report is not triggered by the retransmission timer, and the available uplink resource cannot be triggered, the The logical channel of the normal buffer status report, the terminal device determines to trigger the scheduling request.
  • the terminal device may trigger the scheduling request, thereby ensuring that the network device can learn to target The cache information of the terminal device prevents the network device from scheduling inappropriate resources. Further, when the normal buffer status report is triggered by the retransmission timer timeout, the terminal device may not trigger the scheduling request, avoid unnecessary scheduling request transmission, and reduce signaling overhead caused by sending the scheduling request.
  • the fourth condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in an off state;
  • the available uplink resources are not statically configured uplink resources
  • a logical channel that triggers the normal cache status report can trigger a scheduling request.
  • the first condition is: an available uplink resource is currently available, and the fifth condition that triggers the scheduling request is met, and the logical channel that currently has data to be transmitted is determined. Whether at least one logical channel is included, and the available uplink resource cannot bear the at least one logical channel;
  • the terminal device determines that the scheduling request is triggered under the first condition, and includes:
  • the available uplink resource is present, and the fifth condition is met, if the at least one logical channel is included in a logical channel that currently has data to be transmitted, and the available uplink resource cannot bear the at least one logic.
  • the terminal device determines to trigger the scheduling request; or
  • the available uplink resource is currently present, and the fifth condition is met. If the available uplink resource can carry all the logical channels that currently have data to be transmitted, the terminal device determines that the scheduling request is not triggered.
  • the available uplink resources are currently available, and the fifth condition is met. If at least one logical channel is included in the logical channel that currently has data to be transmitted, and the available uplink resources cannot carry at least one logical channel, the terminal device may trigger scheduling. The request, thereby ensuring that the network device can learn the cache information for the terminal device, and avoid the network device scheduling the inappropriate resources. Further, the available uplink resource is currently available, and the fifth condition is met. If the available uplink resource can carry all the logical channels that currently have data to be transmitted, the terminal device may not trigger the scheduling request, thereby avoiding unnecessary The scheduling request is sent to reduce the signaling overhead caused by sending the scheduling request.
  • the fifth condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in an off state;
  • the available uplink resources are not statically configured uplink resources
  • a logical channel that triggers the normal buffer status report can trigger a scheduling request
  • the normal buffer status report is triggered by a retransmission timer timeout.
  • the embodiment of the present application provides a terminal device, which can execute the module or unit of the method in the first aspect or any optional implementation manner of the first aspect.
  • a terminal device comprising a processor, a memory, and a communication interface.
  • the processor is coupled to the memory and communication interface.
  • the memory is for storing instructions for the processor to execute, and the communication interface is for communicating with other network elements under the control of the processor.
  • the processor executes the instructions stored by the memory, the execution causes the processor to perform the method of the first aspect or any of the possible implementations of the first aspect.
  • a computer storage medium having stored therein program code for instructing a computer to execute instructions of the methods described in the above aspects.
  • a computer program product comprising instructions, when executed on a computer, causes the computer to perform the methods described in the various aspects above.
  • FIG. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
  • FIG. 2 is a schematic flowchart of a scheduling request triggering method according to an embodiment of the present application.
  • FIG. 3 is a schematic block diagram of a terminal device according to an embodiment of the present application.
  • FIG. 4 is a schematic block diagram of an apparatus for wireless communication provided by an embodiment of the present application.
  • FIG. 5 is a schematic structural diagram of a system chip according to an embodiment of the present application.
  • GSM Global System of Mobile communication
  • CDMA Code Division Multiple Access
  • Wideband Code Wideband Code Division Multiple Access
  • Division Multiple Access WCDMA
  • GPRS General Packet Radio Service
  • LTE Long Term Evolution
  • LTE-A Advanced Long Term Evolution
  • NR New Radio
  • NR Universal Mobile Telecommunication System
  • UMTS Universal Mobile Telecommunication System
  • WLAN Wireless Local Area Networks
  • WiFi Wireless Fidelity
  • D2D Device to Device
  • M2M Machine to Machine
  • MTC Machine Type Communication
  • V2V Vehicle to Vehicle
  • the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, or may be applied to a Dual Connectivity (DC) scenario, and may also be applied to a Standalone (SA) fabric. Net scene.
  • CA Carrier Aggregation
  • DC Dual Connectivity
  • SA Standalone
  • the embodiment of the present application does not limit the spectrum of the application.
  • the embodiment of the present application can be applied to an authorized spectrum, and can also be applied to an unlicensed spectrum.
  • the embodiments of the present application describe various embodiments in combination with a network device and a terminal device, where the terminal device may also be referred to as a user equipment (User Equipment, UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a mobile station, and a remote location.
  • UE User Equipment
  • Station remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device.
  • the terminal device can be a station in the WLAN (STAION, ST), which can be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, and a personal digital processing.
  • WLAN STAION, ST
  • SIP Session Initiation Protocol
  • WLL Wireless Local Loop
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • PDA Personal Digital Assistant
  • a handheld device with wireless communication capabilities a computing device or other processing device connected to a wireless modem, an in-vehicle device, a wearable device, and a next-generation communication system, such as a terminal device in an NR network or Terminal equipment in the future evolution of the Public Land Mobile Network (PLMN) network.
  • PLMN Public Land Mobile Network
  • the terminal device may also be a wearable device.
  • a wearable device which can also be called a wearable smart device, is a general term for applying wearable technology to intelligently design and wear wearable devices such as glasses, gloves, watches, clothing, and shoes.
  • a wearable device is a portable device that is worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are more than just a hardware device, but they also implement powerful functions through software support, data interaction, and cloud interaction.
  • Generalized wearable smart devices include full-featured, large-size, non-reliable smartphones for full or partial functions, such as smart watches or smart glasses, and focus on only one type of application, and need to work with other devices such as smartphones. Use, such as various smart bracelets for smart signs monitoring, smart jewelry, etc.
  • the network device may be a device for communicating with the mobile device, and the network device may be an Access Point (AP) in the WLAN, a Base Transceiver Station (BTS) in GSM or CDMA, or may be in WCDMA.
  • the base station (NodeB, NB) may also be an evolved base station (Evolutional Node B, eNB or eNodeB) in LTE, or a relay station or an access point, or an in-vehicle device, a wearable device, and a network device (gNB) in the NR network. Or a network device or the like in a future evolved PLMN network.
  • the network device provides a service for the cell
  • the terminal device communicates with the network device by using a transmission resource (for example, a frequency domain resource, or a spectrum resource) used by the cell
  • the cell may be a network device (for example, The corresponding cell of the base station, the cell may belong to the macro base station, or may belong to the base station corresponding to the small cell, where the small cell may include: a metro cell, a micro cell, and a pico cell. Cell, femto cell, etc. These small cells have the characteristics of small coverage and low transmission power, and are suitable for providing high-speed data transmission services.
  • FIG. 1 exemplarily shows one network device and two terminal devices.
  • the wireless communication system 100 may include a plurality of network devices and may include other numbers of terminal devices within the coverage of each network device. The application embodiment does not limit this.
  • the wireless communication system 100 may further include other network entities, such as a Mobility Management Entity (MME), an Access and Mobility Management Function (AMF), and the like. This is not limited.
  • MME Mobility Management Entity
  • AMF Access and Mobility Management Function
  • the term "article of manufacture” as used in this application encompasses a computer program accessible from any computer-readable device, carrier, or media.
  • the computer readable medium may include, but is not limited to, a magnetic storage device (eg, a hard disk, a floppy disk, or a magnetic tape, etc.), such as a compact disc (CD), a digital versatile disc (Digital Versatile Disc, DVD). Etc.), smart cards and flash memory devices (eg, Erasable Programmable Read-Only Memory (EPROM), cards, sticks or key drivers, etc.).
  • various storage media described herein can represent one or more devices and/or other machine-readable media for storing information.
  • the term "machine-readable medium” may include, but is not limited to, a variety of media capable of storing, containing, and/or carrying instructions and/or data.
  • system and “network” are used interchangeably herein.
  • the term “and/or” in this context is merely an association describing the associated object, indicating that there may be three relationships, for example, A and / or B, which may indicate that A exists separately, and both A and B exist, respectively. B these three situations.
  • the character "/" in this article generally indicates that the contextual object is an "or" relationship.
  • FIG. 2 is a schematic flowchart of a scheduling request triggering method 200 according to an embodiment of the present application.
  • the method 200 is optionally applicable to the system shown in FIG. 1, but is not limited thereto.
  • the method 200 includes at least some of the following.
  • the terminal device After the terminal device triggers a normal buffer status report, the terminal device determines to trigger the scheduling request or cancel the scheduling request under the first condition.
  • the BSR can be divided into a normal BSR (Regular BSR) and a filled BSR (Padding BSR).
  • a normal BSR can also be called a regular BSR.
  • the trigger condition of a normal BSR can be: (1) The UE buffer area is empty, but new data with a logical channel needs to be sent. In this case, the BSR needs to be triggered; The data of the logical channel of the UE needs to be transmitted.
  • the BSR will be triggered by the logical channel with higher priority; (3) The timer of retransmission of the BSR (retxBSR) -Timer) timeout, and there is uplink data on at least one logical channel in the logical channel group (LCG) to be transmitted.
  • the triggering condition for filling the BSR may be: for the uplink data sent this time, the allocated resources are relatively large, and some padding bits do not need to transmit data, and some of the transmitted BSRs may just use the padding data to transmit.
  • the terminal device when the terminal device needs to transmit the first data on the logical channel A and the second data is transmitted on the logical channel B, the logical channel A and the logical channel B trigger the normal buffer status report M, and the buffer status report M includes The amount of data to be transmitted by logical channel A and the amount of data to be transmitted by logical channel B.
  • the terminal device may determine to trigger the scheduling request or cancel the scheduling request under the first condition.
  • the terminal device may trigger the scheduling request or cancel the scheduling request under the first condition, thereby implementing a flexible trigger scheduling request or a flexible cancellation scheduling request.
  • the first condition is that there is currently available uplink resource, and it is determined whether the available uplink resource can carry a logical channel that triggers the normal buffer status report.
  • the terminal device cancels the scheduling request at the first moment;
  • the terminal device cancels the scheduling request at the second moment.
  • the terminal device when the terminal device needs to transmit the first data on the logical channel A and the second data is transmitted on the logical channel B, the logical channel A and the logical channel B trigger the normal buffer status report M, and the normal buffer status report M includes data amount information that logical channel A needs to transmit and data amount information that logical channel B needs to transmit.
  • the terminal device After the terminal device triggers the normal buffer status report M and triggers the scheduling request N, there are currently available uplink resources. If the available uplink resources can carry the logical channel A and the logical channel B, the terminal device cancels the scheduling request at time 1. If the available uplink resources cannot carry logical channel A and logical channel B, the terminal device cancels the scheduling request at time 2.
  • the second moment is later than the first moment.
  • the first time and/or the second time is one of when the terminal device receives the uplink resource authorization, the MAC PDU group packet, and the MAC PDU transmission time.
  • the second time may be when the terminal device receives the uplink resource authorization, or may be the MAC PDU group packet, or may be the MAC PDU when the MAC PDU is sent.
  • the second moment needs to be later than the first moment.
  • the second time when the first time is a MAC PDU group packet, the second time may be a MAC PDU group packet, or may be a MAC PDU transmission time. It should be noted that when the second moment is a MAC PDU group packet, the second moment needs to be later than the first moment.
  • the second time may be when the MAC PDU is sent. It should be noted that the second moment needs to be later than the first moment.
  • first time and/or the second time may be a specific time point, or may be any time point within a specific time length, for example, the first time and/or the second time may be It is any point in time between the MAC PDU group packet and the MAC PDU transmission.
  • the terminal device before the terminal device determines that the scheduling request is cancelled under the first condition, the terminal device may trigger the scheduling request under the second condition.
  • the second condition is at least one of the following:
  • the logical channel that triggers the normal buffer status report can trigger the scheduling request.
  • the normal buffer status report is a normal BSR (regular BSR)
  • SR logicalChannelSR-Mask
  • timer for suppressing the terminal device from triggering the scheduling request may be an SR suppression timer (SR-DelayTimer).
  • the terminal device can cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission, and reducing signaling overhead caused by sending the scheduling request. Further, when the available uplink resources are not able to carry the logical channel that triggers the buffer status report, the terminal device may delay the cancellation of the scheduling request, thereby ensuring that the network device can learn the cache information for the terminal device, and avoid the network device scheduling the inappropriate resources. .
  • the first condition is: determining whether the scheduling request is triggered by a third condition.
  • the terminal device cancels the scheduling request at a third moment
  • the terminal device cancels the scheduling request at the fourth moment.
  • the third condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in the off state, in other words, a normal BSR (the normal buffer status report) has been triggered. And the SR suppression timer is not running;
  • the logical channel that triggers the normal buffer status report can trigger the scheduling request.
  • the normal buffer status report is a regular BSR, and the logical channel triggering the normal BSR is not configured by the higher layer, the SR is not allowed to be triggered (logicalChannelSR- Mask).
  • the third condition may not include that the uplink resource used for transmitting the logical channel that triggers the normal buffer status report is not semi-statically configured. Upstream resources.
  • the third time and/or the fourth time is one of when the terminal device receives the uplink resource authorization, the MAC PDU group packet, and the MAC PDU transmission time.
  • the fourth time may be when the terminal device receives the uplink resource authorization, or may be the MAC PDU group packet, or may be the MAC PDU when the MAC PDU is sent. . It should be noted that, when the terminal device receives the uplink resource authorization, the fourth moment needs to be later than the third moment.
  • the fourth time may be a MAC PDU group packet, or may be a MAC PDU transmission time. It should be noted that when the fourth moment is a MAC PDU group packet, the fourth moment needs to be later than the third moment.
  • the fourth time may be when the MAC PDU is sent. It should be noted that the fourth moment needs to be later than the third moment.
  • the third moment and/or the fourth moment may be a specific time point, or may be any one time point within a specific duration, for example, the third moment and/or the fourth moment may be It is any point in time between the MAC PDU group packet and the MAC PDU transmission.
  • the terminal device may cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission, and reducing signaling overhead caused by sending the scheduling request. Further, when the scheduling request is not triggered by the third condition, the terminal device may delay the cancellation of the scheduling request, thereby ensuring that the network device can learn the cache information for the terminal device, and prevent the network device from scheduling the inappropriate resource.
  • the first condition is that the available uplink resource is currently available, and the fourth condition for triggering the scheduling request is met, and whether the normal buffer status report is triggered by the retransmission timer timeout is determined.
  • the terminal device determines that the scheduling request is not triggered; or
  • the current uplink resource is available, and the fourth condition for triggering the scheduling request is met. If the normal buffer status report is not triggered by the retransmission timer, the available uplink resource cannot be triggered to trigger the normal. The logical channel of the buffer status report, the terminal device determines to trigger the scheduling request.
  • the retransmission timer may be a timer (retxBSR-Timer) for BSR retransmission.
  • the fourth condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in the off state, in other words, a normal BSR (the normal buffer status report) has been triggered. And the SR suppression timer is not running;
  • the available uplink resources are not statically configured uplink resources
  • the logical channel that triggers the normal buffer status report can trigger the scheduling request.
  • the normal buffer status report is a regular BSR, and the logical channel triggering the normal BSR is not configured by the higher layer, the SR is not allowed to be triggered (logicalChannelSR- Mask).
  • the terminal device can trigger the scheduling request, thereby ensuring that the network device can The cache information for the terminal device is learned, and the network device is prevented from scheduling inappropriate resources. Further, when the normal buffer status report is triggered by the retransmission timer timeout, the terminal device may not trigger the scheduling request, avoid unnecessary scheduling request transmission, and reduce signaling overhead caused by sending the scheduling request.
  • the first condition is that the available uplink resource is currently available, and the fifth condition that triggers the scheduling request is met, determining whether at least one logical channel is included in the logical channel that currently has data to be transmitted, and the available The uplink resource cannot carry the at least one logical channel.
  • the available uplink resource is currently present, and the fifth condition is met. If the at least one logical channel is included in the logical channel that currently has data to be transmitted, and the available uplink resource cannot carry the at least one logical channel, Then the terminal device determines to trigger the scheduling request; or
  • the available uplink resource currently exists, and the fifth condition is met. If the available uplink resource can carry all logical channels that currently have data to be transmitted, the terminal device determines not to trigger the scheduling request.
  • the fifth condition is at least one of the following:
  • the terminal device After the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device triggering the scheduling request is in the off state, in other words, a normal BSR (the normal buffer status report) has been triggered. And the SR suppression timer is not running;
  • the available uplink resources are not statically configured uplink resources
  • the logical channel that triggers the normal buffer status report can trigger the scheduling request.
  • the normal buffer status report is a regular BSR, and the logical channel triggering the normal BSR is not configured by the higher layer, the SR is not allowed to be triggered (logicalChannelSR- Mask);
  • This normal cache status report is triggered by the retransmission timer timeout.
  • the available uplink resources are currently available, and the fifth condition is met. If at least one logical channel is included in the logical channel that currently has data to be transmitted, and the available uplink resources cannot carry at least one logical channel, the terminal device may trigger scheduling. The request, thereby ensuring that the network device can learn the cache information for the terminal device, and avoid the network device scheduling the inappropriate resources. Further, the available uplink resource is currently available, and the fifth condition is met. If the available uplink resource can carry all the logical channels that currently have data to be transmitted, the terminal device may not trigger the scheduling request, thereby avoiding unnecessary The scheduling request is sent to reduce the signaling overhead caused by sending the scheduling request.
  • FIG. 3 is a schematic block diagram of a terminal device 300 according to an embodiment of the present application.
  • the terminal device 300 includes:
  • the processing unit 310 is configured to determine, after the terminal device 300 triggers the normal buffer status report, to trigger the scheduling request or cancel the scheduling request under the first condition.
  • the first condition is: currently, an available uplink resource exists, and determining whether the available uplink resource can carry a logical channel that triggers the normal buffer status report;
  • the processing unit 310 is specifically configured to:
  • the available uplink resource is capable of carrying a logical channel that triggers the normal buffer status report, canceling the scheduling request at a first moment;
  • the scheduling request is cancelled at a second time.
  • the second moment is later than the first moment.
  • the first time and/or the second time is one of when the terminal device receives an uplink resource authorization, a MAC PDU group packet, and a MAC PDU transmission time.
  • the processing unit 310 before the processing unit 310 determines that the scheduling request is canceled under the first condition, the processing unit 310 is further configured to trigger the scheduling request under the second condition.
  • the second condition is at least one of the following:
  • the terminal device 300 After the terminal device 300 triggers the normal buffer status report, and the timer for suppressing the terminal device 300 triggering the scheduling request is in an off state;
  • a logical channel that triggers the normal cache status report can trigger a scheduling request.
  • the first condition is: determining whether the scheduling request is triggered by a third condition
  • the processing unit 310 is specifically configured to:
  • the scheduling request is cancelled at the fourth moment.
  • the third condition is at least one of the following:
  • the terminal device 300 After the terminal device 300 triggers the normal buffer status report, and the timer for suppressing the terminal device 300 triggering the scheduling request is in an off state;
  • a logical channel that triggers the normal cache status report can trigger a scheduling request.
  • the fourth moment is later than the third moment.
  • the third time and/or the fourth time is one of when the terminal device receives an uplink resource authorization, a MAC PDU group packet, and a MAC PDU transmission time.
  • the first condition is: the current available uplink resource, and the fourth condition that triggers the scheduling request is met, and determining whether the normal buffer status report is triggered by a retransmission timer timeout;
  • the processing unit 310 is specifically configured to:
  • the fourth condition for triggering the scheduling request is met. If the normal buffer status report is triggered by a retransmission timer, it is determined that the scheduling request is not triggered; or
  • the current uplink resource is available, and the fourth condition for triggering the scheduling request is met. If the normal buffer status report is not triggered by the retransmission timer, and the available uplink resource cannot be triggered, the The logical channel of the normal buffer status report determines that the scheduling request is triggered.
  • the fourth condition is at least one of the following:
  • the terminal device 300 After the terminal device 300 triggers the normal buffer status report, and the timer for suppressing the terminal device 300 triggering the scheduling request is in an off state;
  • the available uplink resources are not statically configured uplink resources
  • a logical channel that triggers the normal cache status report can trigger a scheduling request.
  • the first condition is that the available uplink resource is currently available, and the fifth condition that triggers the scheduling request is met, determining whether at least one logical channel is included in the logical channel that currently has data to be transmitted, and the available The uplink resource cannot bear the at least one logical channel;
  • the processing unit 310 is specifically configured to:
  • the available uplink resource is present, and the fifth condition is met, if the at least one logical channel is included in a logical channel that currently has data to be transmitted, and the available uplink resource cannot bear the at least one logic.
  • the terminal device determines to trigger the scheduling request; or
  • the available uplink resource is currently present, and the fifth condition is met. If the available uplink resource can carry all the logical channels that currently have data to be transmitted, the terminal device determines that the scheduling request is not triggered.
  • the fifth condition is at least one of the following:
  • the terminal device 300 After the terminal device 300 triggers the normal buffer status report, and the timer for suppressing the terminal device 300 triggering the scheduling request is in an off state;
  • the available uplink resources are not statically configured uplink resources
  • a logical channel that triggers the normal buffer status report can trigger a scheduling request
  • the normal buffer status report is triggered by a retransmission timer timeout.
  • terminal device 300 may correspond to the terminal device in the method 200, and the corresponding operations implemented by the terminal device in the method 200 may be implemented.
  • the terminal device 300 may correspond to the terminal device in the method 200, and the corresponding operations implemented by the terminal device in the method 200 may be implemented.
  • no further details are provided herein.
  • FIG. 4 is a schematic block diagram of a device 400 for wireless communication provided by an embodiment of the present application.
  • the device 400 includes:
  • the memory 410 is configured to store a program, where the program includes a code
  • the transceiver 420 is configured to communicate with other devices;
  • the processor 430 is configured to execute program code in the memory 410.
  • the transceiver 420 is configured to perform specific signal transceiving under the driving of the processor 430.
  • the processor 430 can implement various operations performed by the terminal device in the method 200 in FIG. 2, and details are not described herein for brevity.
  • the device 400 can be a terminal device, such as a mobile phone.
  • the processor 430 may be a central processing unit (CPU), and the processor 430 may also be other general-purpose processors, digital signal processors (DSPs), and application specific integrated circuits. (ASIC), off-the-shelf programmable gate array (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and more.
  • the general purpose processor may be a microprocessor or the processor or any conventional processor or the like.
  • the memory 410 can include read only memory and random access memory and provides instructions and data to the processor 430. A portion of the memory 410 may also include a non-volatile random access memory. For example, the memory 410 can also store information of the device type.
  • the transceiver 420 can be used to implement signal transmission and reception functions, such as frequency modulation and demodulation functions or upconversion and down conversion functions.
  • the device 400 for wireless communication can be a chip or chipset.
  • the steps of the method disclosed in the embodiments of the present application may be directly implemented as a hardware processor, or may be performed by a combination of hardware and software modules in the processor.
  • the software module can be located in a conventional storage medium such as random access memory, flash memory, read only memory, programmable read only memory or electrically erasable programmable memory, registers, and the like.
  • the storage medium is located in the memory, and the processor 430 reads the information in the memory and completes the steps of the above method in combination with the hardware thereof. To avoid repetition, it will not be described in detail here.
  • FIG. 5 is a schematic structural diagram of a system chip 500 according to an embodiment of the present application.
  • the system chip 500 of FIG. 5 includes an input interface 501, an output interface 502, a processor 503, and a memory 504 that can be connected by an internal communication connection line for executing code in the memory 504.
  • the processor 503 when the code is executed, the processor 503 implements a method performed by the terminal device in the method embodiment. For the sake of brevity, it will not be repeated here.
  • the computer program product includes one or more computer instructions.
  • the computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable device.
  • the computer instructions can be stored in a computer readable storage medium or transferred from one computer readable storage medium to another computer readable storage medium, for example, the computer instructions can be wired from a website site, computer, server or data center (for example, coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (eg infrared, wireless, microwave, etc.) to another website site, computer, server or data center.
  • the computer readable storage medium can be any available media that can be accessed by a computer or a data storage device such as a server, data center, or the like that includes one or more available media.
  • the usable medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a DVD), or a semiconductor medium (such as a solid state disk (SSD)).
  • the size of the sequence numbers of the foregoing processes does not mean the order of execution sequence, and the order of execution of each process should be determined by its function and internal logic, and should not be applied to the embodiment of the present application.
  • the implementation process constitutes any limitation.

Landscapes

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

Abstract

本申请实施例提供了一种调度请求触发方法和终端设备，能够灵活触发SR 与取消 SR。该方法包括：在终端设备触发正常的缓存状态报告之后，所述终端设备确定在第一条件下触发调度请求或者取消调度请求。

Description

调度请求触发方法和终端设备 技术领域
本申请涉及通信领域，并且更具体地，涉及一种调度请求触发方法和终端设备。
背景技术
在新无线(New Radio，NR)系统中，在终端设备触发正常的缓存状态报告(Buffer Status Report，BSR)之后，可能需要触发调度请求(Scheduling Request，SR)或者取消SR。NR系统中对时延要求较高，尤其是高可靠低时延通信(Ultra-Reliable and Low Latency Communication，URLLC)业务，然而，现阶段触发SR与取消SR的机制无法满足NR系统中对时延的要求。
发明内容
本申请实施例提供了一种调度请求触发方法和终端设备，能够灵活触发SR与取消SR。
第一方面，本申请实施例提供了一种调度请求触发方法，包括：
在终端设备触发正常的缓存状态报告之后，所述终端设备确定在第一条件下触发调度请求或者取消调度请求。
因此，在本申请实施例的调度请求触发方法中，在终端设备触发正常的缓存状态报告之后，终端设备可以在第一条件下触发调度请求或者取消调度请求，从而，实现灵活触发调度请求或者灵活取消调度请求。
可选地，在第一方面的一种实现方式中，所述第一条件为：当前存在可用的上行资源，判断所述可用的上行资源是否能够承载触发所述正常的缓存状态报告的逻辑信道；
所述终端设备确定在第一条件下取消调度请求，包括：
若所述可用的上行资源能够承载触发所述正常的缓存状态报告的逻辑信道，所述终端设备在第一时刻取消所述调度请求；或者
若所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，所述终端设备在第二时刻取消所述调度请求。
可选地，在第一方面的一种实现方式中，所述第二时刻晚于所述第一时刻。
因此，在可用的上行资源能够承载触发正常的缓存状态报告的逻辑信道时，终端设备可以提前取消调度请求，从而，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。进一步地，在可用的上行资源不能够承载触发正常的缓存状态报告的逻辑信道时，终端设备可以推迟取消调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。
可选地，在第一方面的一种实现方式中，所述第一时刻和/或所述第二时刻为所述终端设备收到上行资源授权时、媒体接入控制协议数据单元(Media Access Control Protocol Data Unit，MAC PDU)组包时、MAC PDU发送时中的一种。
因此，终端设备可以灵活的在多个时间点取消调度请求。
可选地，在第一方面的一种实现方式中，在所述终端设备确定在所述第一条件下取消所述调度请求之前，所述方法还包括：
所述终端设备在第二条件下触发所述调度请求。
可选地，在第一方面的一种实现方式中，所述第二条件为以下情况中的至少一种：
当前无可用的上行资源；
当前无半静态配置的上行资源；
在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
可选地，在第一方面的一种实现方式中，所述第一条件为：判断所述调度请求是否是第三条件触发的；
所述终端设备确定在第一条件下取消调度请求，包括：
若所述调度请求是所述第三条件触发的，所述终端设备在第三时刻取消所述调度请求；或者
若所述调度请求并非所述第三条件触发的，所述终端设备在第四时刻取消所述调度请求。
可选地，在第一方面的一种实现方式中，所述第三条件为以下情况中的至少一种：
当前无可用的上行资源；
当前无半静态配置的上行资源；
在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
可选地，在第一方面的一种实现方式中，所述第四时刻晚于所述第三时刻。
因此，在调度请求是第三条件触发的时，终端设备可以提前取消调度请求，从而，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。进一步地，在调度请求并非第三条件触发的时，终端设备可以推迟取消调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。
可选地，在第一方面的一种实现方式中，所述第三时刻和/或所述第四时刻为所述终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
因此，终端设备可以灵活的在多个时间点取消调度请求。
可选地，在第一方面的一种实现方式中，所述第一条件为：当前存在可用的上行资源，同时满足触发调度请求的第四条件，判断所述正常的缓存状态报告是否为重传定时器超时触发的；
所述终端设备确定在第一条件下触发调度请求，包括：
当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告是重传定时器超时触发的，则所述终端设备确定不触发所述调度请求；或者
当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告并非是重传定时器超时触发的，且所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，则所述终端设备确定触发所述调度请求。
因此，在缓存状态报告并非是重传定时器超时触发的，且可用的上行资源不能够承载触发正常的缓存状态报告的逻辑信道时，终端设备可以触发调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。进一步地，在正常的缓存状态报告是重传定时器超时触发的时，终端设备可以不触发调度请求，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。
可选地，在第一方面的一种实现方式中，所述第四条件为以下情况中的至少一种：
在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
所述可用的上行资源并非静态配置的上行资源；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
可选地，在第一方面的一种实现方式中，所述第一条件为：当前存在可用的上行资源，且满足触发调度请求的第五条件，判断在当前存在待传输数据的逻辑信道中是否包 括至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道；
所述终端设备确定在第一条件下触发调度请求，包括：
当前存在所述可用的上行资源，且满足所述第五条件，若在当前存在待传输数据的逻辑信道中包括所述至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道，则所述终端设备确定触发所述调度请求；或者
当前存在所述可用的上行资源，且满足所述第五条件，若所述可用的上行资源能够承载当前存在待传输数据的所有逻辑信道，则所述终端设备确定不触发所述调度请求。
因此，当前存在可用的上行资源，且满足第五条件，若在当前存在待传输数据的逻辑信道中包括至少一个逻辑信道，且可用的上行资源无法承载至少一个逻辑信道时，终端设备可以触发调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。进一步地，当前存在所述可用的上行资源，且满足所述第五条件，若可用的上行资源能够承载当前存在待传输数据的所有逻辑信道时，终端设备可以不触发调度请求，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。
可选地，在第一方面的一种实现方式中，所述第五条件为以下情况中的至少一种：
在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
所述可用的上行资源并非静态配置的上行资源；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求；
所述正常的缓存状态报告是由重传定时器超时触发的。
第二方面，本申请实施例提供了一种终端设备，可以执行第一方面或第一方面的任一可选的实现方式中的方法的模块或者单元。
第三方面，提供了一种终端设备，该终端设备包括处理器、存储器和通信接口。处理器与存储器和通信接口连接。存储器用于存储指令，处理器用于执行该指令，通信接口用于在处理器的控制下与其他网元进行通信。该处理器执行该存储器存储的指令时，该执行使得该处理器执行第一方面或第一方面的任意可能的实现方式中的方法。
第四方面，提供了一种计算机存储介质，该计算机存储介质中存储有程序代码，该程序代码用于指示计算机执行上述各方面所述的方法的指令。
第五方面，提供了一种包括指令的计算机程序产品，当其在计算机上运行时，使得计算机执行上述各方面所述的方法。
附图说明
图1是本申请实施例的应用场景的示意图。
图2是根据本申请实施例的一种调度请求触发方法的示意性流程图。
图3是根据本申请实施例的终端设备的示意性框图。
图4示出了本申请实施例提供的无线通信的设备的示意性框图。
图5是根据本申请实施例的系统芯片的示意性结构图。
具体实施方式
下面将结合本申请实施例中的附图，对本申请实施例中的技术方案进行清楚、完整地描述。
本申请实施例可以应用于各种通信系统，例如：全球移动通讯(Global System of Mobile communication，GSM)系统、码分多址(Code Division Multiple Access，CDMA)系统、宽带码分多址(Wideband Code Division Multiple Access，WCDMA)系统、通用分组无线业务(General Packet Radio Service，GPRS)、长期演进(Long Term Evolution， LTE)系统、先进的长期演进(Advanced long term evolution，LTE-A)系统、新无线(New Radio，NR)系统、NR系统的演进系统、免授权频谱上的LTE(LTE-based access to unlicensed spectrum，LTE-U)系统、免授权频谱上的NR(NR-based access to unlicensed spectrum，NR-U)系统、通用移动通信系统(Universal Mobile Telecommunication System，UMTS)、无线局域网(Wireless Local Area Networks，WLAN)、无线保真(Wireless Fidelity，WiFi)、下一代通信系统或其他通信系统等。
通常来说，传统的通信系统支持的连接数有限，也易于实现，然而，随着通信技术的发展，移动通信系统将不仅支持传统的通信，还将支持例如，设备到设备(Device to Device，D2D)通信，机器到机器(Machine to Machine，M2M)通信，机器类型通信(Machine Type Communication，MTC)，以及车辆间(Vehicle to Vehicle，V2V)通信等，本申请实施例也可以应用于这些通信系统。
可选地，本申请实施例中的通信系统可以应用于载波聚合(Carrier Aggregation，CA)场景，也可以应用于双连接(Dual Connectivity，DC)场景，还可以应用于独立(Standalone，SA)布网场景。
本申请实施例对应用的频谱并不限定。例如，本申请实施例可以应用于授权频谱，也可以应用于免授权频谱。
本申请实施例结合网络设备和终端设备描述了各个实施例，其中：终端设备也可以称为用户设备(User Equipment，UE)、接入终端、用户单元、用户站、移动站、移动台、远方站、远程终端、移动设备、用户终端、终端、无线通信设备、用户代理或用户装置等。终端设备可以是WLAN中的站点(STAION，ST)，可以是蜂窝电话、无绳电话、会话启动协议(Session Initiation Protocol，SIP)电话、无线本地环路(Wireless Local Loop，WLL)站、个人数字处理(Personal Digital Assistant，PDA)设备、具有无线通信功能的手持设备、计算设备或连接到无线调制解调器的其它处理设备、车载设备、可穿戴设备以及下一代通信系统，例如，NR网络中的终端设备或者未来演进的公共陆地移动网络(Public Land Mobile Network，PLMN)网络中的终端设备等。
作为示例而非限定，在本申请实施例中，该终端设备还可以是可穿戴设备。可穿戴设备也可以称为穿戴式智能设备，是应用穿戴式技术对日常穿戴进行智能化设计、开发出可以穿戴的设备的总称，如眼镜、手套、手表、服饰及鞋等。可穿戴设备即直接穿在身上，或是整合到用户的衣服或配件的一种便携式设备。可穿戴设备不仅仅是一种硬件设备，更是通过软件支持以及数据交互、云端交互来实现强大的功能。广义穿戴式智能设备包括功能全、尺寸大、可不依赖智能手机实现完整或者部分的功能，例如：智能手表或智能眼镜等，以及只专注于某一类应用功能，需要和其它设备如智能手机配合使用，如各类进行体征监测的智能手环、智能首饰等。
网络设备可以是用于与移动设备通信的设备，网络设备可以是WLAN中的接入点(Access Point，AP)，GSM或CDMA中的基站(Base Transceiver Station，BTS)，也可以是WCDMA中的基站(NodeB，NB)，还可以是LTE中的演进型基站(Evolutional Node B，eNB或eNodeB)，或者中继站或接入点，或者车载设备、可穿戴设备以及NR网络中的网络设备(gNB)或者未来演进的PLMN网络中的网络设备等。
在本申请实施例中，网络设备为小区提供服务，终端设备通过该小区使用的传输资源(例如，频域资源，或者说，频谱资源)与网络设备进行通信，该小区可以是网络设备(例如基站)对应的小区，小区可以属于宏基站，也可以属于小小区(Small cell)对应的基站，这里的小小区可以包括：城市小区(Metro cell)、微小区(Micro cell)、微微小区(Pico cell)、毫微微小区(Femto cell)等，这些小小区具有覆盖范围小、发射功率低的特点，适用于提供高速率的数据传输服务。
图1示例性地示出了一个网络设备和两个终端设备，可选地，该无线通信系统100可以包括多个网络设备并且每个网络设备的覆盖范围内可以包括其它数量的终端设备， 本申请实施例对此不做限定。
可选地，该无线通信系统100还可以包括移动性管理实体(Mobility Management Entity，MME)、接入与移动性管理功能(Access and Mobility Management Function，AMF)等其他网络实体，本申请实施例对此不作限定。
此外，本申请的各个方面或特征可以实现成方法、装置或使用标准编程和/或工程技术的制品。本申请中使用的术语“制品”涵盖可从任何计算机可读器件、载体或介质访问的计算机程序。例如，计算机可读介质可以包括，但不限于：磁存储器件(例如，硬盘、软盘或磁带等)，光盘(例如，压缩盘(Compact Disc，CD)、数字通用盘(Digital Versatile Disc，DVD)等)，智能卡和闪存器件(例如，可擦写可编程只读存储器(Erasable Programmable Read-Only Memory，EPROM)、卡、棒或钥匙驱动器等)。另外，本文描述的各种存储介质可代表用于存储信息的一个或多个设备和/或其它机器可读介质。术语“机器可读介质”可包括但不限于，能够存储、包含和/或承载指令和/或数据的各种介质。
应理解，本文中术语“系统”和“网络”在本文中常被可互换使用。本文中术语“和/或”，仅仅是一种描述关联对象的关联关系，表示可以存在三种关系，例如，A和/或B，可以表示：单独存在A，同时存在A和B，单独存在B这三种情况。另外，本文中字符“/”，一般表示前后关联对象是一种“或”的关系。
图2是根据本申请实施例的调度请求触发方法200的示意性流程图。该方法200可选地可以应用于图1所示的系统，但并不限于此。该方法200包括以下内容中的至少部分内容。
S210，在终端设备触发正常的缓存状态报告之后，该终端设备确定在第一条件下触发调度请求或者取消调度请求。
应理解，BSR可以分为正常的BSR(Regular BSR)、填充BSR(Padding BSR)。正常的BSR，也可以称为常规BSR，正常的BSR的触发条件可以是：(1)UE缓存区空了，但是有逻辑信道的新的数据来了需要发送，此时需要触发BSR；(2)UE有逻辑信道的数据需要发送，此时又来了优先级更高的逻辑信道的数据，则将以优先级更高的逻辑信道来触发BSR；(3)BSR重传的定时器(retxBSR-Timer)超时，且逻辑信道组(logical channel group，LCG)中存在至少一个逻辑信道上有上行数据需要发送。填充BSR的触发条件可以是：对于本次发送的上行数据，分配的资源比较大，一些填充位不需要传输数据，此时一些发送的BSR的正好可以使用这些填充数据来发送。
例如，在终端设备需要在逻辑信道A上传输第一数据，以及在逻辑信道B上传输第二数据时，逻辑信道A和逻辑信道B触发正常的缓存状态报告M，且缓存状态报告M中包括逻辑信道A需要传输的数据量信息和逻辑信道B需要传输的数据量信息。在终端设备触发缓存状态报告M之后，该终端设备可以确定在第一条件下触发调度请求或者取消调度请求。
因此，在终端设备触发正常的缓存状态报告之后，终端设备可以在第一条件下触发调度请求或者取消调度请求，从而，实现灵活触发调度请求或者灵活取消调度请求。
作为实施例1，该第一条件为：当前存在可用的上行资源，判断该可用的上行资源是否能够承载触发该正常的缓存状态报告的逻辑信道。
具体地，若该可用的上行资源能够承载触发该正常的缓存状态报告的逻辑信道，该终端设备在第一时刻取消该调度请求；或者
若该可用的上行资源不能够承载触发该正常的缓存状态报告的逻辑信道，该终端设备在第二时刻取消该调度请求。
例如，在终端设备需要在逻辑信道A上传输第一数据，以及在逻辑信道B上传输第二数据时，逻辑信道A和逻辑信道B触发正常的缓存状态报告M，且该正常的缓存状态报告M中包括逻辑信道A需要传输的数据量信息和逻辑信道B需要传输的数据量信息。在终端设备触发该正常的缓存状态报告M，以及触发调度请求N之后，当前存在可用的 上行资源，若是可用的上行资源能够承载逻辑信道A和逻辑信道B时，终端设备在时刻1取消调度请求；若是可用的上行资源不能够承载逻辑信道A和逻辑信道B时，终端设备在时刻2取消调度请求。
需要说明的是，该第二时刻晚于该第一时刻。
可选地，该第一时刻和/或该第二时刻为该终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
例如，在该第一时刻为该终端设备收到上行资源授权时，该第二时刻可以是该终端设备收到上行资源授权时，也可以是MAC PDU组包时，还可以是MAC PDU发送时。需要说明的是，该第二时刻是该终端设备收到上行资源授权时，该第二时刻需要晚于该第一时刻。
又例如，在该第一时刻为MAC PDU组包时，该第二时刻可以是MAC PDU组包时，也可以是MAC PDU发送时。需要说明的是，该第二时刻是MAC PDU组包时，该第二时刻需要晚于该第一时刻。
又例如，在该第一时刻为MAC PDU发送时，该第二时刻可以是MAC PDU发送时。需要说明的是，该第二时刻需要晚于该第一时刻。
应理解，该第一时刻和/或该第二时刻可以是一个具体地时间点，也可以是一个具体地时长内的任意一个时间点，例如，该第一时刻和/或该第二时刻可以是MAC PDU组包与MAC PDU发送之间的任意一个时间点。
可选地，在实施例1中，在该终端设备确定在该第一条件下取消该调度请求之前，该终端设备可以在第二条件下触发该调度请求。
具体地，该第二条件为以下情况中的至少一种：
当前无可用的上行资源，换句话说，当前无针对一个新传输的上行共享信道资源(Uplink Shared Channel，UL-SCH)；
当前无半静态配置的上行资源；
在该终端设备触发该正常的缓存状态报告之后，且用于抑制该终端设备触发调度请求的定时器处于关闭状态，换句话说，一个正常的BSR(regular BSR)已经被触发了并且SR抑制计时器没有在运行中；
触发该正常的缓存状态报告的逻辑信道能够触发调度请求，换句话说，若该正常的缓存状态报告为一个正常BSR(regular BSR)，并且触发该正常BSR的逻辑信道没有被高层配置不允许触发SR(logicalChannelSR-Mask)。
应理解，用于抑制该终端设备触发调度请求的定时器可以是SR抑制计时器(SR-DelayTimer)。
因此，在可用的上行资源能够承载触发缓存状态报告的逻辑信道时，终端设备可以提前取消调度请求，从而，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。进一步地，在可用的上行资源不能够承载触发缓存状态报告的逻辑信道时，终端设备可以推迟取消调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。
作为实施例2，该第一条件为：判断该调度请求是否是第三条件触发的。
具体地，若该调度请求是该第三条件触发的，该终端设备在第三时刻取消该调度请求；或者
若该调度请求并非该第三条件触发的，该终端设备在第四时刻取消该调度请求。
可选地，该第三条件为以下情况中的至少一种：
当前无可用的上行资源，换句话说，当前无针对一个新传输的上行共享信道资源；
当前无半静态配置的上行资源；
在该终端设备触发该正常的缓存状态报告之后，且用于抑制该终端设备触发调度请求的定时器处于关闭状态，换句话说，一个正常的BSR(该正常的缓存状态报告)已经 被触发了并且SR抑制计时器没有在运行中；
触发该正常的缓存状态报告的逻辑信道能够触发调度请求，换句话说，若该正常的缓存状态报告为一个regular BSR，并且触发该正常BSR的逻辑信道没有被高层配置不允许触发SR(logicalChannelSR-Mask)。
需要说明的是，该第四时刻晚于该第三时刻。
需要说明的是，若该第三条件包括当前无半静态配置的上行资源时，该第三条件不可以包括用于传输触发所述正常的缓存状态报告的逻辑信道的上行资源并非半静态配置的上行资源。
可选地，该第三时刻和/或该第四时刻为该终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
例如，在该第三时刻为该终端设备收到上行资源授权时，该第四时刻可以是该终端设备收到上行资源授权时，也可以是MAC PDU组包时，还可以是MAC PDU发送时。需要说明的是，该第四时刻是该终端设备收到上行资源授权时，该第四时刻需要晚于该第三时刻。
又例如，在该第三时刻为MAC PDU组包时，该第四时刻可以是MAC PDU组包时，也可以是MAC PDU发送时。需要说明的是，该第四时刻是MAC PDU组包时，该第四时刻需要晚于该第三时刻。
又例如，在该第三时刻为MAC PDU发送时，该第四时刻可以是MAC PDU发送时。需要说明的是，该第四时刻需要晚于该第三时刻。
应理解，该第三时刻和/或该第四时刻可以是一个具体地时间点，也可以是一个具体地时长内的任意一个时间点，例如，该第三时刻和/或该第四时刻可以是MAC PDU组包与MAC PDU发送之间的任意一个时间点。
因此，在调度请求是第三条件触发的时，终端设备可以提前取消调度请求，从而，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。进一步地，在调度请求并非第三条件触发的时，终端设备可以推迟取消调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。
作为实施例3，该第一条件为：当前存在可用的上行资源，同时满足触发调度请求的第四条件，判断该正常的缓存状态报告是否为重传定时器超时触发的。
具体地，当前存在可用的上行资源，同时满足触发调度请求的该第四条件，若该正常的缓存状态报告是重传定时器超时触发的，则该终端设备确定不触发该调度请求；或者
当前存在可用的上行资源，同时满足触发调度请求的该第四条件，若该正常的缓存状态报告并非是重传定时器超时触发的，且所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，则该终端设备确定触发该调度请求。
应理解，该重传定时器可以是针对BSR重传的定时器(retxBSR-Timer)。
可选地，该第四条件为以下情况中的至少一种：
在该终端设备触发该正常的缓存状态报告之后，且用于抑制该终端设备触发调度请求的定时器处于关闭状态，换句话说，一个正常的BSR(该正常的缓存状态报告)已经被触发了并且SR抑制计时器没有在运行中；
所述可用的上行资源并非静态配置的上行资源；
触发该正常的缓存状态报告的逻辑信道能够触发调度请求，换句话说，若该正常的缓存状态报告为一个regular BSR，并且触发该正常BSR的逻辑信道没有被高层配置不允许触发SR(logicalChannelSR-Mask)。
因此，在正常的缓存状态报告并非是重传定时器超时触发的，且可用的上行资源不能够承载触发正常的缓存状态报告的逻辑信道时，终端设备可以触发调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。进 一步地，在正常的缓存状态报告是重传定时器超时触发的时，终端设备可以不触发调度请求，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。
作为实施例4，该第一条件为：当前存在可用的上行资源，且满足触发调度请求的第五条件，判断在当前存在待传输数据的逻辑信道中是否包括至少一个逻辑信道，且该可用的上行资源无法承载该至少一个逻辑信道。
具体地，当前存在该可用的上行资源，且满足该第五条件，若在当前存在待传输数据的逻辑信道中包括该至少一个逻辑信道，且该可用的上行资源无法承载该至少一个逻辑信道，则该终端设备确定触发该调度请求；或者
当前存在该可用的上行资源，且满足该第五条件，若该可用的上行资源能够承载当前存在待传输数据的所有逻辑信道，则该终端设备确定不触发该调度请求。
可选地，该第五条件为以下情况中的至少一种：
在该终端设备触发该正常的缓存状态报告之后，且用于抑制该终端设备触发调度请求的定时器处于关闭状态，换句话说，一个正常的BSR(该正常的缓存状态报告)已经被触发了并且SR抑制计时器没有在运行中；
所述可用的上行资源并非静态配置的上行资源；
触发该正常的缓存状态报告的逻辑信道能够触发调度请求，换句话说，若该正常的缓存状态报告为一个regular BSR，并且触发该正常BSR的逻辑信道没有被高层配置不允许触发SR(logicalChannelSR-Mask)；
该正常的缓存状态报告是由重传定时器超时触发的。
因此，当前存在可用的上行资源，且满足第五条件，若在当前存在待传输数据的逻辑信道中包括至少一个逻辑信道，且可用的上行资源无法承载至少一个逻辑信道时，终端设备可以触发调度请求，从而，确保网络设备可以获知针对终端设备的缓存信息，避免网络设备调度不合适的资源。进一步地，当前存在所述可用的上行资源，且满足所述第五条件，若可用的上行资源能够承载当前存在待传输数据的所有逻辑信道时，终端设备可以不触发调度请求，避免没有必要的调度请求发送，减少因发送调度请求而造成的信令开销。
图3是根据本申请实施例的终端设备300的示意性框图。该终端设备300包括：
处理单元310，用于在该终端设备300触发正常的缓存状态报告之后，确定在第一条件下触发调度请求或者取消调度请求。
可选地，所述第一条件为：当前存在可用的上行资源，判断所述可用的上行资源是否能够承载触发所述正常的缓存状态报告的逻辑信道；
所述处理单元310具体用于：
若所述可用的上行资源能够承载触发所述正常的缓存状态报告的逻辑信道，在第一时刻取消所述调度请求；或者
若所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，在第二时刻取消所述调度请求。
可选地，所述第二时刻晚于所述第一时刻。
可选地，所述第一时刻和/或所述第二时刻为所述终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
可选地，在所述处理单元310确定在所述第一条件下取消所述调度请求之前，所述处理单元310还用于在第二条件下触发所述调度请求。
可选地，所述第二条件为以下情况中的至少一种：
当前无可用的上行资源；
当前无半静态配置的上行资源；
在所述终端设备300触发所述正常的缓存状态报告之后，且用于抑制所述终端设备300触发调度请求的定时器处于关闭状态；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
可选地，所述第一条件为：判断所述调度请求是否是第三条件触发的；
所述处理单元310具体用于：
若所述调度请求是所述第三条件触发的，在第三时刻取消所述调度请求；或者
若所述调度请求并非所述第三条件触发的，在第四时刻取消所述调度请求。
可选地，所述第三条件为以下情况中的至少一种：
当前无可用的上行资源；
当前无半静态配置的上行资源；
在所述终端设备300触发所述正常的缓存状态报告之后，且用于抑制所述终端设备300触发调度请求的定时器处于关闭状态；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
可选地，所述第四时刻晚于所述第三时刻。
可选地，所述第三时刻和/或所述第四时刻为所述终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
可选地，所述第一条件为：当前存在可用的上行资源，同时满足触发调度请求的第四条件，判断所述正常的缓存状态报告是否为重传定时器超时触发的；
所述处理单元310具体用于：
当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告是重传定时器超时触发的，确定不触发所述调度请求；或者
当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告并非是重传定时器超时触发的，且所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，确定触发所述调度请求。
可选地，所述第四条件为以下情况中的至少一种：
在所述终端设备300触发所述正常的缓存状态报告之后，且用于抑制所述终端设备300触发调度请求的定时器处于关闭状态；
所述可用的上行资源并非静态配置的上行资源；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
可选地，所述第一条件为：当前存在可用的上行资源，且满足触发调度请求的第五条件，判断在当前存在待传输数据的逻辑信道中是否包括至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道；
所述处理单元310具体用于：
当前存在所述可用的上行资源，且满足所述第五条件，若在当前存在待传输数据的逻辑信道中包括所述至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道，则所述终端设备确定触发所述调度请求；或者
当前存在所述可用的上行资源，且满足所述第五条件，若所述可用的上行资源能够承载当前存在待传输数据的所有逻辑信道，则所述终端设备确定不触发所述调度请求。
可选地，所述第五条件为以下情况中的至少一种：
在所述终端设备300触发所述正常的缓存状态报告之后，且用于抑制所述终端设备300触发调度请求的定时器处于关闭状态；
所述可用的上行资源并非静态配置的上行资源；
触发所述正常的缓存状态报告的逻辑信道能够触发调度请求；
所述正常的缓存状态报告是由重传定时器超时触发的。
应理解，该终端设备300可以对应于方法200中的终端设备，可以实现方法200中终端设备实现的相应操作，为了简洁，在此不再赘述。
图4示出了本申请实施例提供的无线通信的设备400的示意性框图，该设备400包括：
存储器410，用于存储程序，该程序包括代码；
收发器420，用于和其他设备进行通信；
处理器430，用于执行存储器410中的程序代码。
可选地，收发器420用于在处理器430的驱动下执行具体的信号收发。
可选地，当该代码被执行时，该处理器430可以实现图2中的方法200中终端设备执行的各个操作，为了简洁，在此不再赘述。此时，该设备400可以为终端设备，例如，手机。
应理解，在本申请实施例中，该处理器430可以是中央处理单元(Central Processing Unit，CPU)，该处理器430还可以是其他通用处理器、数字信号处理器(DSP)、专用集成电路(ASIC)、现成可编程门阵列(FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件等。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。
该存储器410可以包括只读存储器和随机存取存储器，并向处理器430提供指令和数据。存储器410的一部分还可以包括非易失性随机存取存储器。例如，存储器410还可以存储设备类型的信息。
收发器420可以是用于实现信号发送和接收功能，例如频率调制和解调功能或叫上变频和下变频功能。
在实现过程中，上述方法的至少一个步骤可以通过处理器430中的硬件的集成逻辑电路完成，或该集成逻辑电路可在软件形式的指令驱动下完成该至少一个步骤。因此，无线通信的设备400可以是个芯片或者芯片组。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成，或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器，闪存、只读存储器，可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器，处理器430读取存储器中的信息，结合其硬件完成上述方法的步骤。为避免重复，这里不再详细描述。
图5是根据本申请实施例的系统芯片500的示意性结构图。图5的系统芯片500包括输入接口501、输出接口502、处理器503以及存储器504之间可以通过内部通信连接线路相连，该处理器503用于执行该存储器504中的代码。
可选地，当该代码被执行时，该处理器503实现方法实施例中由终端设备执行的方法。为了简洁，在此不再赘述。
在上述实施例中，可以全部或部分地通过软件、硬件、固件或者其任意组合来实现。当使用软件实现时，可以全部或部分地以计算机程序产品的形式实现。该计算机程序产品包括一个或多个计算机指令。在计算机上加载和执行该计算机程序指令时，全部或部分地产生按照本申请实施例所述的流程或功能。该计算机可以是通用计算机、专用计算机、计算机网络、或者其他可编程装置。该计算机指令可以存储在计算机可读存储介质中，或者从一个计算机可读存储介质向另一个计算机可读存储介质传输，例如，该计算机指令可以从一个网站站点、计算机、服务器或数据中心通过有线(例如同轴电缆、光纤、数字用户线(DSL))或无线(例如红外、无线、微波等)方式向另一个网站站点、计算机、服务器或数据中心进行传输。该计算机可读存储介质可以是计算机能够存取的任何可用介质或者是包含一个或多个可用介质集成的服务器、数据中心等数据存储设备。该可用介质可以是磁性介质，(例如，软盘、硬盘、磁带)、光介质(例如，DVD)、或者半导体介质(例如固态硬盘Solid State Disk(SSD))等。
应理解，在本申请的各种实施例中，上述各过程的序号的大小并不意味着执行顺序的先后，各过程的执行顺序应以其功能和内在逻辑确定，而不应对本申请实施例的实施过程构成任何限定。
所属领的技术人员可以清楚地了解到，为描述的方便和简洁，上述描述的系统、装 置和单元的具体工作过程，可以参考前述方法实施例中的对应过程，在此不再赘述。
以上所述，仅为本申请的具体实施方式，但本申请的保护范围并不局限于此，任何熟悉本技术领的技术人员在本申请揭露的技术范围内，可轻易想到变化或替换，都应涵盖在本申请的保护范围之内。因此，本申请的保护范围应以该权利要求的保护范围为准。

Claims (28)

  1. 一种调度请求触发方法，其特征在于，包括：
    在终端设备触发正常的缓存状态报告之后，所述终端设备确定在第一条件下触发调度请求或者取消调度请求。
  2. 根据权利要求1所述的方法，其特征在于，所述第一条件为：当前存在可用的上行资源，判断所述可用的上行资源是否能够承载触发所述正常的缓存状态报告的逻辑信道；
    所述终端设备确定在第一条件下取消调度请求，包括：
    若所述可用的上行资源能够承载触发所述正常的缓存状态报告的逻辑信道，所述终端设备在第一时刻取消所述调度请求；或者
    若所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，所述终端设备在第二时刻取消所述调度请求。
  3. 根据权利要求2所述的方法，其特征在于，所述第二时刻晚于所述第一时刻。
  4. 根据权利要求2或3所述的方法，其特征在于，所述第一时刻和/或所述第二时刻为所述终端设备收到上行资源授权时、媒体接入控制协议数据单元MAC PDU组包时、MAC PDU发送时中的一种。
  5. 根据权利要求2至4中任一项所述的方法，其特征在于，在所述终端设备确定在所述第一条件下取消所述调度请求之前，所述方法还包括：
    所述终端设备在第二条件下触发所述调度请求。
  6. 根据权利要求5所述的方法，其特征在于，所述第二条件为以下情况中的至少一种：
    当前无可用的上行资源；
    当前无半静态配置的上行资源；
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
  7. 根据权利要求1所述的方法，其特征在于，所述第一条件为：判断所述调度请求是否是第三条件触发的；
    所述终端设备确定在第一条件下取消调度请求，包括：
    若所述调度请求是所述第三条件触发的，所述终端设备在第三时刻取消所述调度请求；或者
    若所述调度请求并非所述第三条件触发的，所述终端设备在第四时刻取消所述调度请求。
  8. 根据权利要求7所述的方法，其特征在于，所述第三条件为以下情况中的至少一种：
    当前无可用的上行资源；
    当前无半静态配置的上行资源；
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
  9. 根据权利要求7或8所述的方法，其特征在于，所述第四时刻晚于所述第三时刻。
  10. 根据权利要求7至9中任一项所述的方法，其特征在于，所述第三时刻和/或所述第四时刻为所述终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
  11. 根据权利要求1所述的方法，其特征在于，所述第一条件为：当前存在可用的 上行资源，同时满足触发调度请求的第四条件，判断所述正常的缓存状态报告是否为重传定时器超时触发的；
    所述终端设备确定在第一条件下触发调度请求，包括：
    当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告是重传定时器超时触发的，则所述终端设备确定不触发所述调度请求；或者
    当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告并非是重传定时器超时触发的，且所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，则所述终端设备确定触发所述调度请求。
  12. 根据权利要求11所述的方法，其特征在于，所述第四条件为以下情况中的至少一种：
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    所述可用的上行资源并非静态配置的上行资源；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
  13. 根据权利要求1所述的方法，其特征在于，所述第一条件为：当前存在可用的上行资源，且满足触发调度请求的第五条件，判断在当前存在待传输数据的逻辑信道中是否包括至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道；
    所述终端设备确定在第一条件下触发调度请求，包括：
    当前存在所述可用的上行资源，且满足所述第五条件，若在当前存在待传输数据的逻辑信道中包括所述至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道，则所述终端设备确定触发所述调度请求；或者
    当前存在所述可用的上行资源，且满足所述第五条件，若所述可用的上行资源能够承载当前存在待传输数据的所有逻辑信道，则所述终端设备确定不触发所述调度请求。
  14. 根据权利要求13所述的方法，其特征在于，所述第五条件为以下情况中的至少一种：
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    所述可用的上行资源并非静态配置的上行资源；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求；
    所述正常的缓存状态报告是由重传定时器超时触发的。
  15. 一种终端设备，其特征在于，包括：
    处理单元，用于在所述终端设备触发正常的缓存状态报告之后，确定在第一条件下触发调度请求或者取消调度请求。
  16. 根据权利要求15所述的终端设备，其特征在于，所述第一条件为：当前存在可用的上行资源，判断所述可用的上行资源是否能够承载触发所述正常的缓存状态报告的逻辑信道；
    所述处理单元具体用于：
    若所述可用的上行资源能够承载触发所述正常的缓存状态报告的逻辑信道，在第一时刻取消所述调度请求；或者
    若所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，在第二时刻取消所述调度请求。
  17. 根据权利要求16所述的终端设备，其特征在于，所述第二时刻晚于所述第一时刻。
  18. 根据权利要求16或17所述的终端设备，其特征在于，所述第一时刻和/或所述第二时刻为所述终端设备收到上行资源授权时、媒体接入控制协议数据单元MAC PDU 组包时、MAC PDU发送时中的一种。
  19. 根据权利要求16至18中任一项所述的终端设备，其特征在于，在所述处理单元确定在所述第一条件下取消所述调度请求之前，所述处理单元还用于在第二条件下触发所述调度请求。
  20. 根据权利要求19所述的终端设备，其特征在于，所述第二条件为以下情况中的至少一种：
    当前无可用的上行资源；
    当前无半静态配置的上行资源；
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
  21. 根据权利要求15所述的终端设备，其特征在于，所述第一条件为：判断所述调度请求是否是第三条件触发的；
    所述处理单元具体用于：
    若所述调度请求是所述第三条件触发的，在第三时刻取消所述调度请求；或者
    若所述调度请求并非所述第三条件触发的，在第四时刻取消所述调度请求。
  22. 根据权利要求21所述的终端设备，其特征在于，所述第三条件为以下情况中的至少一种：
    当前无可用的上行资源；
    当前无半静态配置的上行资源；
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
  23. 根据权利要求21或22所述的终端设备，其特征在于，所述第四时刻晚于所述第三时刻。
  24. 根据权利要求21至23中任一项所述的终端设备，其特征在于，所述第三时刻和/或所述第四时刻为所述终端设备收到上行资源授权时、MAC PDU组包时、MAC PDU发送时中的一种。
  25. 根据权利要求15所述的终端设备，其特征在于，所述第一条件为：当前存在可用的上行资源，同时满足触发调度请求的第四条件，判断所述正常的缓存状态报告是否为重传定时器超时触发的；
    所述处理单元具体用于：
    当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告是重传定时器超时触发的，确定不触发所述调度请求；或者
    当前存在可用的上行资源，同时满足触发调度请求的所述第四条件，若所述正常的缓存状态报告并非是重传定时器超时触发的，且所述可用的上行资源不能够承载触发所述正常的缓存状态报告的逻辑信道，确定触发所述调度请求。
  26. 根据权利要求25所述的终端设备，其特征在于，所述第四条件为以下情况中的至少一种：
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    所述可用的上行资源并非静态配置的上行资源；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求。
  27. 根据权利要求15所述的终端设备，其特征在于，所述第一条件为：当前存在可用的上行资源，且满足触发调度请求的第五条件，判断在当前存在待传输数据的逻辑信道中是否包括至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信 道；
    所述处理单元具体用于：
    当前存在所述可用的上行资源，且满足所述第五条件，若在当前存在待传输数据的逻辑信道中包括所述至少一个逻辑信道，且所述可用的上行资源无法承载所述至少一个逻辑信道，则所述终端设备确定触发所述调度请求；或者
    当前存在所述可用的上行资源，且满足所述第五条件，若所述可用的上行资源能够承载当前存在待传输数据的所有逻辑信道，则所述终端设备确定不触发所述调度请求。
  28. 根据权利要求27所述的终端设备，其特征在于，所述第五条件为以下情况中的至少一种：
    在所述终端设备触发所述正常的缓存状态报告之后，且用于抑制所述终端设备触发调度请求的定时器处于关闭状态；
    所述可用的上行资源并非静态配置的上行资源；
    触发所述正常的缓存状态报告的逻辑信道能够触发调度请求；
    所述正常的缓存状态报告是由重传定时器超时触发的。
PCT/CN2018/081645 2018-04-02 2018-04-02 调度请求触发方法和终端设备 WO2019191883A1 (zh)

Priority Applications (2)

Application Number Priority Date Filing Date Title
CN201880037053.7A CN110720244B (zh) 2018-04-02 2018-04-02 调度请求取消方法和终端设备
PCT/CN2018/081645 WO2019191883A1 (zh) 2018-04-02 2018-04-02 调度请求触发方法和终端设备

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/081645 WO2019191883A1 (zh) 2018-04-02 2018-04-02 调度请求触发方法和终端设备

Publications (1)

Publication Number Publication Date
WO2019191883A1 true WO2019191883A1 (zh) 2019-10-10

Family

ID=68099730

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2018/081645 WO2019191883A1 (zh) 2018-04-02 2018-04-02 调度请求触发方法和终端设备

Country Status (2)

Country Link
CN (1) CN110720244B (zh)
WO (1) WO2019191883A1 (zh)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN117377113A (zh) * 2021-04-01 2024-01-09 北京小米移动软件有限公司 调度请求触发方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101695194A (zh) * 2009-10-22 2010-04-14 普天信息技术研究院有限公司 一种lte系统半静态调度中上行逻辑信道的复用方法
CN102056332A (zh) * 2009-11-02 2011-05-11 中兴通讯股份有限公司 缓冲区状态报告处理流程的优化方法及系统
CN107592978A (zh) * 2015-05-12 2018-01-16 Lg 电子株式会社 无线通信系统中发送基于竞争的pusch的方法及其设备

Family Cites Families (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101772070B (zh) * 2009-01-05 2015-02-25 上海中兴软件有限责任公司 重传缓冲区状态报告定时器的处理方法及终端
CN101771521B (zh) * 2009-01-06 2013-11-06 中兴通讯股份有限公司 一种缓冲区状态报告重传定时器的管理方法
KR101623977B1 (ko) * 2009-10-09 2016-05-24 삼성전자주식회사 이동통신 시스템에서 스케줄링 요청 신호를 전송하는 방법 및 장치
JP2011155334A (ja) * 2010-01-26 2011-08-11 Sharp Corp 通信システム及び移動局装置及び基地局装置及び処理方法
KR101776873B1 (ko) * 2011-01-11 2017-09-11 삼성전자 주식회사 이동통신 시스템에서 역방향 전송 출력 결정 방법 및 장치
KR102268754B1 (ko) * 2014-11-05 2021-06-24 엘지전자 주식회사 D2d 통신 시스템에서 사이드링크 버퍼 상태 보고에 의해 트리거된 스케줄링 요청을 취소하는 방법 및 그 장치
EP3320715B1 (en) * 2015-07-06 2020-04-08 LG Electronics Inc. Method for cancelling a buffer status report or a scheduling request in dual connectivity and a device therefor
KR20170123236A (ko) * 2016-04-28 2017-11-07 엘지전자 주식회사 데이터 볼륨 정보를 전송하는 방법 및 사용자기기
KR102394123B1 (ko) * 2017-06-16 2022-05-04 삼성전자 주식회사 차세대 이동 통신 시스템에서 복수 개의 스케쥴링 요청을 전송하는 방법 및 장치
CN109561511A (zh) * 2017-09-27 2019-04-02 夏普株式会社 无线通信方法和设备
CN109587770A (zh) * 2017-09-29 2019-04-05 华为技术有限公司 调度请求的处理方法和终端设备

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101695194A (zh) * 2009-10-22 2010-04-14 普天信息技术研究院有限公司 一种lte系统半静态调度中上行逻辑信道的复用方法
CN102056332A (zh) * 2009-11-02 2011-05-11 中兴通讯股份有限公司 缓冲区状态报告处理流程的优化方法及系统
CN107592978A (zh) * 2015-05-12 2018-01-16 Lg 电子株式会社 无线通信系统中发送基于竞争的pusch的方法及其设备

Also Published As

Publication number Publication date
CN110720244A (zh) 2020-01-21
CN110720244B (zh) 2021-02-26

Similar Documents

Publication Publication Date Title
WO2019183848A1 (zh) 监听pdcch的方法、终端设备和网络设备
CN111586751B (zh) 一种缓存状态报告bsr的触发方法、通信装置
US11463194B2 (en) Information determination method, terminal apparatus, and network apparatus
CN112369094B (zh) 无线通信方法、终端设备和网络设备
WO2019024114A1 (zh) 数据传输的方法、终端设备和网络设备
WO2019024022A1 (zh) 上行传输的方法和终端设备
WO2019023851A1 (zh) 通信方法、通信装置和系统
WO2019076347A1 (zh) 通信方法和通信装置
WO2019148443A1 (zh) 确定竞争窗口的方法和设备
WO2020119615A1 (zh) 一种通信方法、装置及计算机可读存储介质
WO2019191987A1 (zh) 传输上行数据的方法、终端设备和网络设备
US20230397298A1 (en) Timer operating method, terminal device, and network device
WO2019157634A1 (zh) 一种harq信息的传输方法及装置、计算机存储介质
WO2020151585A1 (zh) 数据传输的方法和装置
WO2019191883A1 (zh) 调度请求触发方法和终端设备
WO2019218126A1 (zh) 控制网络拥塞的方法、终端设备和网络设备
GB2496221A (en) Mobile interference mitigation via autonomous denial and beacon frames
WO2022067611A1 (zh) 先侦听后传输失败上报的方法、终端设备和网络设备
WO2021164684A1 (zh) 上行反馈资源的确定方法和终端设备
WO2019178833A1 (zh) 资源授权的方法和设备
CN114731239B (zh) 冲突处理方法和终端设备
CN115211061B (zh) 信息传输的方法、终端设备和网络设备
WO2022205483A1 (zh) 传输方法、终端设备、网络设备及通信系统
US20220322424A1 (en) Method for processing random access procedure, and terminal device
CN115190628B (zh) 资源传输方法和终端设备

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

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

Country of ref document: EP

Kind code of ref document: A1