CN110720244A - Scheduling request triggering method and terminal equipment - Google Patents

Scheduling request triggering method and terminal equipment Download PDF

Info

Publication number
CN110720244A
CN110720244A CN201880037053.7A CN201880037053A CN110720244A CN 110720244 A CN110720244 A CN 110720244A CN 201880037053 A CN201880037053 A CN 201880037053A CN 110720244 A CN110720244 A CN 110720244A
Authority
CN
China
Prior art keywords
scheduling request
condition
terminal device
status report
buffer status
Prior art date
Legal status (The legal status 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 status listed.)
Granted
Application number
CN201880037053.7A
Other languages
Chinese (zh)
Other versions
CN110720244B (en
Inventor
石聪
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Guangdong Oppo Mobile Telecommunications Corp Ltd
Original Assignee
Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Guangdong Oppo Mobile Telecommunications Corp Ltd filed Critical Guangdong Oppo Mobile Telecommunications Corp Ltd
Publication of CN110720244A publication Critical patent/CN110720244A/en
Application granted granted Critical
Publication of CN110720244B publication Critical patent/CN110720244B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

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

Landscapes

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

Abstract

The embodiment of the application provides a scheduling request triggering method and terminal equipment, which can flexibly trigger and cancel an SR. The method comprises the following steps: after the terminal equipment triggers a normal buffer status report, the terminal equipment determines to trigger a scheduling request or cancel the scheduling request under a first condition.

Description

Scheduling request triggering method and terminal equipment Technical Field
The present application relates to the field of communications, and in particular, to a scheduling request triggering method and a terminal device.
Background
In a New Radio (NR) system, after a terminal device triggers a normal Buffer Status Report (BSR), a Scheduling Request (SR) may need to be triggered or the SR may need to be cancelled. In the NR system, the requirement for delay is high, especially for high-reliability Low-delay Communication (URLLC) service, however, at present, the mechanism for triggering SR and canceling SR cannot meet the requirement for delay in the NR system.
Disclosure of Invention
The embodiment of the application provides a scheduling request triggering method and terminal equipment, which can flexibly trigger and cancel an SR.
In a first aspect, an embodiment of the present application provides a scheduling request triggering method, including:
after the terminal equipment triggers a normal buffer status report, the terminal equipment determines to trigger a scheduling request or cancel the scheduling request under a first condition.
Therefore, in the scheduling request triggering method of the embodiment of the present application, after the terminal device triggers the normal buffer status report, the terminal device may trigger the scheduling request or cancel the scheduling request under the first condition, thereby implementing flexible triggering of the scheduling request or flexible cancellation of the scheduling request.
Optionally, in an implementation manner of the first aspect, the first condition is that: judging whether the available uplink resources can bear a logic channel triggering the normal buffer status report or not when the available uplink resources currently exist;
the terminal equipment determines to cancel the scheduling request under a first condition, and the method comprises the following steps:
if the available uplink resources can carry the logical channel triggering the normal buffer status report, the terminal equipment cancels the scheduling request at a first moment; or
And if the available uplink resources cannot bear the logical channel triggering the normal buffer status report, the terminal equipment cancels the scheduling request at a second moment.
Optionally, in an implementation manner of the first aspect, the second time is later than the first time.
Therefore, when the available uplink resources can carry the logical channel triggering the normal buffer status report, the terminal device can cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission and reducing the signaling overhead caused by the transmission of the scheduling request. Further, when the available uplink resource cannot carry the logical channel triggering the normal buffer status report, the terminal device may defer canceling the scheduling request, thereby ensuring that the network device may acquire the buffer information for the terminal device, and avoiding the network device from scheduling unsuitable resources.
Optionally, in an implementation manner of the first aspect, the first time and/or the second time is one of when the terminal device receives an uplink resource grant, when the terminal device packages a Media Access Control Protocol Data Unit (MAC PDU), and when the MAC PDU is sent.
Therefore, the terminal device can flexibly cancel the scheduling request at a plurality of time points.
Optionally, in an implementation manner of the first aspect, before the terminal device determines to cancel the scheduling request under the first condition, the method further includes:
and the terminal equipment triggers the scheduling request under a second condition.
Optionally, in an implementation manner of the first aspect, the second condition is at least one of the following:
currently, there is no available uplink resource;
currently, there is no semi-statically configured uplink resource;
after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
the logical channel that triggers the normal buffer status report can trigger a scheduling request.
Optionally, in an implementation manner of the first aspect, the first condition is that: judging whether the scheduling request is triggered by a third condition;
the terminal equipment determines to cancel the scheduling request under a first condition, and the method comprises the following steps:
if the scheduling request is triggered by the third condition, the terminal equipment cancels the scheduling request at a third moment; or
And if the scheduling request is not triggered by the third condition, the terminal equipment cancels the scheduling request at a fourth time.
Optionally, in an implementation manner of the first aspect, the third condition is at least one of the following:
currently, there is no available uplink resource;
currently, there is no semi-statically configured uplink resource;
after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
the logical channel that triggers the normal buffer status report can trigger a scheduling request.
Optionally, in an implementation manner of the first aspect, the fourth time is later than the third time.
Therefore, when the scheduling request is triggered by the third condition, the terminal device can cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission and reducing signaling overhead caused by transmitting the scheduling request. Further, when the scheduling request is not triggered by the third condition, the terminal device may postpone canceling the scheduling request, thereby ensuring that the network device may acquire the cache information for the terminal device, and avoiding the network device from scheduling inappropriate resources.
Optionally, in an implementation manner of the first aspect, the third time and/or the fourth time is one of when the terminal device receives an uplink resource grant, when the terminal device packages a MAC PDU, and when the terminal device sends a MAC PDU.
Therefore, the terminal device can flexibly cancel the scheduling request at a plurality of time points.
Optionally, in an implementation manner of the first aspect, the first condition is that: currently, available uplink resources exist, and meanwhile, a fourth condition for triggering a scheduling request is met, and whether the normal cache state report is triggered by the overtime of a retransmission timer is judged;
the terminal device determines that a scheduling request is triggered under a first condition, and the method comprises the following steps:
if the normal buffer status report is triggered by the timeout of the retransmission timer, the terminal device determines not to trigger the scheduling request; or
If the normal buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resource cannot carry the logical channel triggering the normal buffer status report, the terminal device determines to trigger the scheduling request.
Therefore, when the buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resource cannot carry the logical channel triggering the normal buffer status report, the terminal device may trigger the scheduling request, thereby ensuring that the network device can acquire the buffer information for the terminal device and avoiding the network device from scheduling the unsuitable resource. Further, when the normal buffer status report is triggered by the timeout of the retransmission timer, the terminal device may not trigger the scheduling request, thereby avoiding unnecessary transmission of the scheduling request and reducing signaling overhead caused by transmission of the scheduling request.
Optionally, in an implementation manner of the first aspect, the fourth condition is at least one of the following:
after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
the available uplink resources are not statically configured uplink resources;
the logical channel that triggers the normal buffer status report can trigger a scheduling request.
Optionally, in an implementation manner of the first aspect, the first condition is that: the method comprises the steps that available uplink resources exist currently, a fifth condition for triggering a scheduling request is met, whether at least one logic channel is included in the logic channels where data to be transmitted exist currently is judged, and the available uplink resources cannot bear the at least one logic channel;
the terminal device determines that a scheduling request is triggered under a first condition, and the method comprises the following steps:
if the available uplink resources currently exist and meet the fifth condition, and if the logical channel where the data to be transmitted currently exists includes the at least one logical channel and the available uplink resources cannot bear the at least one logical channel, the terminal device determines to trigger the scheduling request; or
And if the available uplink resources can bear all the logic channels of the data to be transmitted, the terminal equipment determines not to trigger the scheduling request.
Therefore, available uplink resources exist currently, and the fifth condition is satisfied, if at least one logical channel is included in the logical channels where data to be transmitted currently exists, and the available uplink resources cannot bear the at least one logical channel, the terminal device may trigger the scheduling request, thereby ensuring that the network device can acquire the cache information for the terminal device, and avoiding that the network device schedules inappropriate resources. Further, the available uplink resources currently exist and the fifth condition is satisfied, and if the available uplink resources can carry all the logical channels currently having data to be transmitted, the terminal device may not trigger the scheduling request, thereby avoiding unnecessary scheduling request transmission and reducing signaling overhead caused by transmitting the scheduling request.
Optionally, in an implementation manner of the first aspect, the fifth condition is at least one of the following:
after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
the available uplink resources are not statically configured uplink resources;
the logic channel triggering the normal buffer status report can trigger a scheduling request;
the normal buffer status report is triggered by a retransmission timer timeout.
In a second aspect, an embodiment of the present application provides a terminal device, which may execute the modules or units of the method in the first aspect or any optional implementation manner of the first aspect.
In a third aspect, a terminal device is provided that includes a processor, a memory, and a communication interface. The processor is coupled to the memory and the communication interface. The memory is for storing instructions, the processor is for executing the instructions, and the communication interface is for communicating with other network elements under control of the processor. The processor, when executing the instructions stored by the memory, causes the processor to perform the method of the first aspect or any possible implementation of the first aspect.
In a fourth aspect, a computer storage medium is provided having program code stored therein for instructing a computer to execute the instructions of the method of the above aspects.
In a fifth aspect, there is provided a computer program product comprising instructions which, when run on a computer, cause the computer to perform the method of the above aspects.
Drawings
Fig. 1 is a schematic diagram of an application scenario of an embodiment of the present application.
Fig. 2 is a schematic flow chart 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 shows a schematic block diagram of a device 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.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application.
The embodiment of the application can be applied to various communication systems, such as: global System for Mobile communications (GSM) System, Code Division Multiple Access (CDMA) System, Wideband Code Division Multiple Access (WCDMA) System, General Packet Radio Service (GPRS), Long Term Evolution (Long Term Evolution, LTE) System, LTE-a System, New Radio (NR) System, Evolution System of NR System, LTE-a System over unlicensed spectrum, NR (NR-b) System, UMTS (Universal Mobile telecommunications System), UMTS (UMTS) System, WLAN-b System over unlicensed spectrum, WiFi-b System, Wireless Local Area Network (WLAN) System, Wireless Local Area network (WiFi) System, GPRS (General Packet Radio Service, GPRS) System, GPRS (GPRS) System, LTE-b System, LTE-a System, NR System, LTE-b System over unlicensed spectrum, and LTE-b System over unlicensed spectrum, Next generation communication systems or other communication systems, etc.
Generally, conventional Communication systems support a limited number of connections and are easy to implement, however, with the development of Communication technology, mobile Communication systems will support not only conventional Communication, but also, for example, Device-to-Device (D2D) Communication, Machine-to-Machine (M2M) Communication, Machine Type Communication (MTC), and Vehicle-to-Vehicle (V2V) Communication, and the embodiments of the present application can also be applied to these Communication systems.
Optionally, the communication system in the embodiment of the present application may be applied to a Carrier Aggregation (CA) scenario, may also be applied to a Dual Connectivity (DC) scenario, and may also be applied to an independent (SA) networking scenario.
The frequency spectrum of the application is not limited in the embodiment of the present application. For example, the embodiments of the present application may be applied to a licensed spectrum and may also be applied to an unlicensed spectrum.
The embodiments of the present application are described in conjunction with a network device and a terminal device, where: a terminal device may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a User terminal, a wireless communication device, a User agent, or a User Equipment, etc. The terminal device may be a Station (ST) in a WLAN, and may be a cellular phone, a cordless phone, a Session Initiation Protocol (SIP) phone, a Wireless Local Loop (WLL) station, a Personal Digital Assistant (PDA) device, a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, and a next generation communication system, for example, a terminal device in an NR Network or a terminal device in a future evolved Public Land Mobile Network (PLMN) Network, and the like.
By way of example and not limitation, in the embodiments of the present application, the terminal device may also be a wearable device. Wearable equipment can also be called wearable intelligent equipment, is the general term of applying wearable technique to carry out intelligent design, develop the equipment that can dress to daily wearing, like glasses, gloves, wrist-watch, dress and shoes etc.. A wearable device is a portable device that is worn directly on the body or integrated into the clothing or accessories of the user. The wearable device is not only a hardware device, but also realizes powerful functions through software support, data interaction and cloud interaction. The generalized wearable smart device includes full functionality, large size, and can implement full or partial functionality without relying on a smart phone, such as: smart watches or smart glasses and the like, and only focus on a certain type of application functions, and need to be used in cooperation with other devices such as smart phones, such as various smart bracelets for physical sign monitoring, smart jewelry and the like.
The network device may be a device for communicating with a mobile device, and the network device may be an Access Point (AP) in a WLAN, a Base Station (BTS) in GSM or CDMA, a Base Station (NodeB, NB) in WCDMA, an evolved Node B (eNB, eNodeB) in LTE, a relay Station or an Access Point, or a vehicle-mounted device, a wearable device, a network device (gNB) in an NR network, or a network device in a PLMN network that is evolved in the future.
In this embodiment of the present application, a network device provides a service for a cell, and a terminal device communicates with the network device through a transmission resource (for example, a frequency domain resource or a spectrum resource) used by the cell, where the cell may be a cell corresponding to the network device (for example, a base station), and the cell may belong to a macro base station or a base station corresponding to a Small cell (Small cell), where the Small cell may include: urban cells (Metro cells), Micro cells (Micro cells), Pico cells (Pico cells), Femto cells (Femto cells), and the like, and the small cells have the characteristics of small coverage area and low transmission power, and are suitable for providing high-rate data transmission services.
Fig. 1 exemplarily shows one network device and two terminal devices, and optionally, 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, which is not limited in this embodiment of the present application.
Optionally, 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), which is not limited in this embodiment.
Moreover, various aspects or features of the present application may be implemented as a method, apparatus, or article of manufacture using standard programming and/or engineering techniques. The term "article of manufacture" as used herein is intended to encompass a computer program accessible from any computer-readable device, carrier, or media. For example, computer-readable media may include, but are not limited to: magnetic storage devices (e.g., hard disk, floppy disk, or magnetic tape), optical disks (e.g., Compact Disk (CD), Digital Versatile Disk (DVD), etc.), smart cards, and flash Memory devices (e.g., Erasable Programmable Read-Only Memory (EPROM), card, stick, or key drive, etc.). In addition, 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" can include, without being limited to, various media capable of storing, containing, and/or carrying instruction(s) and/or data.
It should be understood that the terms "system" and "network" are often used interchangeably herein. The term "and/or" herein is merely an association describing an associated object, meaning that three relationships may exist, e.g., a and/or B, may mean: a exists alone, A and B exist simultaneously, and B exists alone. In addition, the character "/" herein generally indicates that the former and latter related objects are in an "or" relationship.
Fig. 2 is a schematic flow chart diagram of a scheduling request triggering method 200 according to an embodiment of the present application. The method 200 may alternatively be applied to the system shown in fig. 1, but is not limited thereto. The method 200 includes at least some of the following.
S210, 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.
It should be understood that BSR may be classified as Normal BSR (regular BSR), Padding BSR (padding BSR). The normal BSR, which may also be referred to as a regular BSR, may be triggered as follows: (1) the UE buffer is empty, but new data of a logic channel comes to be sent, and at the moment, a BSR (buffer status report) needs to be triggered; (2) when the UE has data of a logical channel to send, and the data of the logical channel with higher priority comes, the BSR is triggered by the logical channel with higher priority; (3) the Timer (retxsrb-Timer) for BSR retransmission times out, and there is at least one logical channel in the Logical Channel Group (LCG) on which uplink data needs to be transmitted. The triggering conditions for padding the BSR may be: for the uplink data sent this time, the allocated resources are large, some padding bits do not need to transmit data, and some sent BSRs can just use the padding data to send.
For example, when the terminal device needs to transmit first data on logical channel a and transmit second data on logical channel B, logical channel a and logical channel B trigger a normal buffer status report M, and the buffer status report M includes information of the amount of data that logical channel a needs to transmit and information of the amount of data that logical channel B needs to transmit. After the terminal device triggers the buffer status report M, the terminal device may determine to trigger the scheduling request or cancel the scheduling request under the first condition.
Therefore, after the terminal device triggers the normal buffer status report, the terminal device may trigger the scheduling request or cancel the scheduling request under the first condition, thereby implementing flexible triggering of the scheduling request or flexible cancellation of the scheduling request.
As example 1, the first condition is: and judging whether the available uplink resources can bear the logical channel triggering the normal buffer status report or not.
Specifically, if the available uplink resource can carry a logical channel that triggers the normal buffer status report, the terminal device cancels the scheduling request at a first time; or
And if the available uplink resources cannot bear the logical channel triggering the normal buffer status report, the terminal equipment cancels the scheduling request at a second moment.
For example, when the terminal device needs to transmit first data on logical channel a and transmit second data on logical channel B, logical channel a and logical channel B trigger a normal buffer status report M, and the normal buffer status report M includes information of the amount of data that logical channel a needs to transmit and information of the amount of data that logical channel B needs to transmit. After the terminal equipment triggers the normal buffer status report M and triggers the scheduling request N, available uplink resources exist at present, and if the available uplink resources can bear a logical channel A and a logical channel B, the terminal equipment cancels the scheduling request at the moment 1; if the available uplink resources cannot carry the logical channel a and the logical channel B, the terminal device cancels the scheduling request at time 2.
It should be noted that the second time is later than the first time.
Optionally, the first time and/or the second time is one of when the terminal device receives the uplink resource authorization, when the terminal device packages the MAC PDU, and when the terminal device sends the MAC PDU.
For example, when the terminal device receives the uplink resource grant at the first time, the second time may be when the terminal device receives the uplink resource grant, or when the terminal device packages the MAC PDU, or when the terminal device sends the MAC PDU. It should be noted that, when the terminal device receives the grant of uplink resources, the second time needs to be later than the first time.
For example, when the first time is MAC PDU grouping, the second time may be MAC PDU grouping or MAC PDU transmission. It should be noted that, when the second time is the MAC PDU packet, the second time needs to be later than the first time.
For another example, when the first time is MAC PDU transmission, the second time may be MAC PDU transmission. It should be noted that the second time needs to be later than the first time.
It should be understood that the first time and/or the second time may be a specific time point, or any time point within a specific time duration, for example, the first time and/or the second time may be any time point between the MAC PDU packet packing and the MAC PDU transmission.
Optionally, in embodiment 1, before the terminal device determines to cancel the scheduling request under the first condition, the terminal device may trigger the scheduling request under a second condition.
Specifically, the second condition is at least one of the following cases:
currently, there is no Uplink resource available, in other words, there is no Uplink Shared Channel (UL-SCH) resource currently dedicated to a new transmission;
currently, there is no semi-statically configured uplink resource;
after the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device from triggering the scheduling request is in an off state, in other words, a normal bsr (regular bsr) has been triggered and the SR suppression timer is not running;
the logical channel triggering the normal buffer status report can trigger the scheduling request, in other words, if the normal buffer status report is a normal BSR (regular BSR) and the logical channel triggering the normal BSR is not configured by the higher layer and does not allow SR (logical channel SR-Mask) to be triggered.
It should be appreciated that the timer used to suppress the terminal device from triggering the scheduling request may be an SR-suppression timer (SR-DelayTimer).
Therefore, when the available uplink resources can carry the logical channel triggering the buffer status report, the terminal device can cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission and reducing the signaling overhead caused by the transmission of the scheduling request. Further, when the available uplink resource cannot carry the logical channel triggering the buffer status report, the terminal device may defer canceling the scheduling request, thereby ensuring that the network device may acquire the buffer information for the terminal device, and avoiding the network device from scheduling inappropriate resources.
As example 2, the first condition is: it is determined whether the scheduling request is triggered by a third condition.
Specifically, if the scheduling request is triggered by the third condition, the terminal device cancels the scheduling request at a third time; or
And if the scheduling request is not triggered by the third condition, the terminal equipment cancels the scheduling request at a fourth moment.
Optionally, the third condition is at least one of:
there is currently no uplink resource available, in other words, there is currently no uplink shared channel resource for a new transmission;
currently, there is no semi-statically configured uplink resource;
after the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device from triggering the scheduling request is in an 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 triggering the normal buffer status report can trigger the scheduling request, in other words, if the normal buffer status report is a regular BSR and the logical channel triggering the normal BSR is not configured by a higher layer and is not allowed to trigger SR (logical channel SR-Mask).
Note that the fourth time is later than the third time.
It should be noted that, if the third condition includes uplink resources that are not currently configured in a semi-static manner, the third condition may not include uplink resources that are not configured in a semi-static manner and are used for transmitting the logical channel that triggers the normal buffer status report.
Optionally, the third time and/or the fourth time is one of when the terminal device receives the uplink resource authorization, when the terminal device packages the MAC PDU, and when the terminal device sends the MAC PDU.
For example, when the terminal device receives the uplink resource grant at the third time, the fourth time may be when the terminal device receives the uplink resource grant, or when the terminal device packages the MAC PDU, or when the terminal device sends the MAC PDU. It should be noted that, the fourth time is when the terminal device receives the grant of uplink resources, and the fourth time needs to be later than the third time.
For example, when the third time is MAC PDU grouping, the fourth time may be MAC PDU grouping or MAC PDU transmission. It should be noted that, when the fourth time is the MAC PDU packet, the fourth time needs to be later than the third time.
For another example, when the third time is MAC PDU transmission, the fourth time may be MAC PDU transmission. Note that the fourth time needs to be later than the third time.
It should be understood that the third time and/or the fourth time may be a specific time point, or any time point within a specific time duration, for example, the third time and/or the fourth time may be any time point between the MAC PDU packet and the MAC PDU transmission.
Therefore, when the scheduling request is triggered by the third condition, the terminal device can cancel the scheduling request in advance, thereby avoiding unnecessary scheduling request transmission and reducing signaling overhead caused by transmitting the scheduling request. Further, when the scheduling request is not triggered by the third condition, the terminal device may postpone canceling the scheduling request, thereby ensuring that the network device may acquire the cache information for the terminal device, and avoiding the network device from scheduling inappropriate resources.
As example 3, the first condition is: and currently, available uplink resources exist, meanwhile, a fourth condition for triggering the scheduling request is met, and whether the normal cache state report is triggered by the overtime of the retransmission timer or not is judged.
Specifically, there is currently available uplink resource, and the fourth condition for triggering the scheduling request is satisfied, and if the normal buffer status report is triggered by the timeout of the retransmission timer, the terminal device determines not to trigger the scheduling request; or
If the normal buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resources cannot carry the logical channel triggering the normal buffer status report, the terminal device determines to trigger the scheduling request.
It should be appreciated that the retransmission Timer may be a Timer for BSR retransmission (retxsbr-Timer).
Optionally, the fourth condition is at least one of:
after the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device from triggering the scheduling request is in an 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 triggering the normal buffer status report can trigger the scheduling request, in other words, if the normal buffer status report is a regular BSR and the logical channel triggering the normal BSR is not configured by a higher layer and is not allowed to trigger SR (logical channel SR-Mask).
Therefore, when the normal buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resource cannot carry the logical channel triggering the normal buffer status report, the terminal device may trigger the scheduling request, thereby ensuring that the network device can acquire the buffer information for the terminal device and avoiding the network device from scheduling the unsuitable resource. Further, when the normal buffer status report is triggered by the timeout of the retransmission timer, the terminal device may not trigger the scheduling request, thereby avoiding unnecessary transmission of the scheduling request and reducing signaling overhead caused by transmission of the scheduling request.
As example 4, the first condition was: and judging whether the logic channel with the data to be transmitted currently comprises at least one logic channel or not, wherein the available uplink resources cannot bear the at least one logic channel.
Specifically, the available uplink resource exists currently, and the fifth condition is satisfied, if the logical channel in which the data to be transmitted currently exists includes the at least one logical channel, and the available uplink resource cannot carry the at least one logical channel, the terminal device determines to trigger the scheduling request; or
If the available uplink resource exists currently and meets the fifth condition, and the available uplink resource can carry all the logical channels where the data to be transmitted currently exists, the terminal device determines not to trigger the scheduling request.
Optionally, the fifth condition is at least one of:
after the terminal device triggers the normal buffer status report, and the timer for suppressing the terminal device from triggering the scheduling request is in an 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 triggering the normal buffer status report can trigger a scheduling request, in other words, if the normal buffer status report is a regular BSR and the logical channel triggering the normal BSR is not configured by a higher layer and is not allowed to trigger an SR (local channel SR-Mask);
the normal buffer status report is triggered by the retransmission timer expiring.
Therefore, available uplink resources exist currently, and the fifth condition is satisfied, if at least one logical channel is included in the logical channels where data to be transmitted currently exists, and the available uplink resources cannot bear the at least one logical channel, the terminal device may trigger the scheduling request, thereby ensuring that the network device can acquire the cache information for the terminal device, and avoiding that the network device schedules inappropriate resources. Further, the available uplink resources currently exist and the fifth condition is satisfied, and if the available uplink resources can carry all the logical channels currently having data to be transmitted, the terminal device may not trigger the scheduling request, thereby avoiding unnecessary scheduling request transmission and reducing signaling overhead caused by transmitting 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 that a scheduling request is triggered or cancelled under a first condition after the terminal device 300 triggers a normal buffer status report.
Optionally, the first condition is: judging whether the available uplink resources can bear a logic channel triggering the normal buffer status report or not when the available uplink resources currently exist;
the processing unit 310 is specifically configured to:
if the available uplink resources can bear the logical channel triggering the normal buffer status report, canceling the scheduling request at a first moment; or
And if the available uplink resources cannot bear the logic channel triggering the normal buffer status report, canceling the scheduling request at a second moment.
Optionally, the second time is later than the first time.
Optionally, the first time and/or the second time is one of when the terminal device receives an uplink resource authorization, when the terminal device packages a MAC PDU, and when the terminal device sends a MAC PDU.
Optionally, before the processing unit 310 determines to cancel the scheduling request under the first condition, the processing unit 310 is further configured to trigger the scheduling request under a second condition.
Optionally, the second condition is at least one of:
currently, there is no available uplink resource;
currently, there is no semi-statically configured uplink resource;
after the terminal device 300 triggers the normal buffer status report, a timer for suppressing the terminal device 300 from triggering a scheduling request is in an off state;
the logical channel that triggers the normal buffer status report can trigger a scheduling request.
Optionally, the first condition is: judging whether the scheduling request is triggered by a third condition;
the processing unit 310 is specifically configured to:
if the scheduling request is triggered by the third condition, canceling the scheduling request at a third moment; or
And if the scheduling request is not triggered by the third condition, canceling the scheduling request at a fourth time.
Optionally, the third condition is at least one of:
currently, there is no available uplink resource;
currently, there is no semi-statically configured uplink resource;
after the terminal device 300 triggers the normal buffer status report, a timer for suppressing the terminal device 300 from triggering a scheduling request is in an off state;
the logical channel that triggers the normal buffer status report can trigger a scheduling request.
Optionally, the fourth time is later than the third time.
Optionally, the third time and/or the fourth time is one of when the terminal device receives the uplink resource authorization, when the terminal device packages the MAC PDU, and when the terminal device sends the MAC PDU.
Optionally, the first condition is: currently, available uplink resources exist, and meanwhile, a fourth condition for triggering a scheduling request is met, and whether the normal cache state report is triggered by the overtime of a retransmission timer is judged;
the processing unit 310 is specifically configured to:
if the normal buffer status report is triggered by the overtime of the retransmission timer, determining not to trigger the scheduling request; or
If the normal buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resources cannot carry the logical channel triggering the normal buffer status report, determining to trigger the scheduling request.
Optionally, the fourth condition is at least one of:
after the terminal device 300 triggers the normal buffer status report, a timer for suppressing the terminal device 300 from triggering a scheduling request is in an off state;
the available uplink resources are not statically configured uplink resources;
the logical channel that triggers the normal buffer status report can trigger a scheduling request.
Optionally, the first condition is: the method comprises the steps that available uplink resources exist currently, a fifth condition for triggering a scheduling request is met, whether at least one logic channel is included in logic channels where data to be transmitted exist currently is judged, and the available uplink resources cannot bear the at least one logic channel;
the processing unit 310 is specifically configured to:
if the available uplink resources currently exist and meet the fifth condition, and if the logical channel where the data to be transmitted currently exists includes the at least one logical channel and the available uplink resources cannot bear the at least one logical channel, the terminal device determines to trigger the scheduling request; or
And if the available uplink resources can bear all the logic channels of the data to be transmitted, the terminal equipment determines not to trigger the scheduling request.
Optionally, the fifth condition is at least one of:
after the terminal device 300 triggers the normal buffer status report, a timer for suppressing the terminal device 300 from triggering a scheduling request is in an off state;
the available uplink resources are not statically configured uplink resources;
the logic channel triggering the normal buffer status report can trigger a scheduling request;
the normal buffer status report is triggered by a retransmission timer timeout.
It should be understood that the terminal device 300 may correspond to the terminal device in the method 200, and corresponding operations implemented by the terminal device in the method 200 may be implemented, which are not described herein again for brevity.
Fig. 4 shows a schematic block diagram of an apparatus 400 for wireless communication provided by an embodiment of the application, where the apparatus 400 includes:
a memory 410 for storing a program, the program comprising code;
a transceiver 420 for communicating with other devices;
a processor 430 for executing the program code in the memory 410.
Optionally, the transceiver 420 is used to perform specific signal transceiving under the driving of the processor 430.
Optionally, when the code is executed, the processor 430 may implement each operation performed by the terminal device in the method 200 in fig. 2, and details are not described herein for brevity. In this case, the device 400 may be a terminal device, for example, a mobile phone.
It should be understood that, in the embodiment of the present application, 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), Application Specific Integrated Circuits (ASICs), Field Programmable Gate Arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, and the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.
The memory 410 may include both 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 non-volatile random access memory. For example, the memory 410 may also store device type information.
The transceiver 420 may be for performing signal transmission and reception functions such as frequency modulation and demodulation functions or frequency up-and down-conversion functions.
In implementation, at least one step of the above method may be performed by a hardware integrated logic circuit in the processor 430, or the integrated logic circuit may perform the at least one step under instruction driving in a software form. Thus, the device 400 for wireless communication may be a single chip or a chip set. The steps of a method disclosed in connection with the embodiments of the present application may be directly implemented by a hardware processor, or may be implemented by a combination of hardware and software modules in a processor. The software module may be located in ram, flash memory, rom, prom, or eprom, registers, etc. storage media as is well known in the art. The storage medium is located in a memory, and the processor 430 reads information in the memory and performs the steps of the method in combination with hardware thereof. To avoid repetition, it is not described in detail here.
Fig. 5 is a schematic block 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, which are connected via an internal communication connection, and the processor 503 is used for executing codes in the memory 504.
Optionally, when the code is executed, the processor 503 implements the method performed by the terminal device in the method embodiment. For brevity, no further description is provided herein.
In the above embodiments, the implementation may be wholly or partially realized by software, hardware, firmware, or any combination thereof. When implemented in software, may be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When loaded and executed on a computer, cause the processes or functions described in accordance with the embodiments of the application to occur, in whole or in part. The computer may be a general purpose computer, a special purpose computer, a network of computers, or other programmable device. The computer instructions may be stored in a computer readable storage medium or transmitted from one computer readable storage medium to another, for example, from one website site, computer, server, or data center to another website site, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, Digital Subscriber Line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.). The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device, such as a server, a data center, etc., that includes one or more of the available media. The usable medium may be a magnetic medium (e.g., floppy Disk, hard Disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., Solid State Disk (SSD)), among others.
It should be understood that, in the various embodiments of the present application, the sequence numbers of the above-mentioned processes do not mean the execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present application.
It can be clearly understood by those skilled in the art that, for convenience and brevity of description, the specific working processes of the system, the apparatus and the unit described above may refer to the corresponding processes in the foregoing method embodiments, and are not described herein again.
The above description is only for the specific embodiments of the present application, but the scope of the present application is not limited thereto, and any person skilled in the art can easily conceive of the changes or substitutions within the technical scope of the present application, and shall be covered by the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims (28)

  1. A scheduling request triggering method, comprising:
    after the terminal equipment triggers a normal buffer status report, the terminal equipment determines to trigger a scheduling request or cancel the scheduling request under a first condition.
  2. The method of claim 1, wherein the first condition is: judging whether the available uplink resources can bear a logic channel triggering the normal buffer status report or not when the available uplink resources currently exist;
    the terminal equipment determines to cancel the scheduling request under a first condition, and the method comprises the following steps:
    if the available uplink resources can carry the logical channel triggering the normal buffer status report, the terminal equipment cancels the scheduling request at a first moment; or
    And if the available uplink resources cannot bear the logical channel triggering the normal buffer status report, the terminal equipment cancels the scheduling request at a second moment.
  3. The method of claim 2, wherein the second time is later than the first time.
  4. The method according to claim 2 or 3, wherein the first time and/or the second time is one of when the terminal device receives uplink resource grant, when the terminal device receives MAC PDU packet, and when the terminal device sends MAC PDU.
  5. The method according to any of claims 2 to 4, wherein before the terminal device determines to cancel the scheduling request under the first condition, the method further comprises:
    and the terminal equipment triggers the scheduling request under a second condition.
  6. The method of claim 5, wherein the second condition is at least one of:
    currently, there is no available uplink resource;
    currently, there is no semi-statically configured uplink resource;
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the logical channel that triggers the normal buffer status report can trigger a scheduling request.
  7. The method of claim 1, wherein the first condition is: judging whether the scheduling request is triggered by a third condition;
    the terminal equipment determines to cancel the scheduling request under a first condition, and the method comprises the following steps:
    if the scheduling request is triggered by the third condition, the terminal equipment cancels the scheduling request at a third moment; or
    And if the scheduling request is not triggered by the third condition, the terminal equipment cancels the scheduling request at a fourth time.
  8. The method of claim 7, wherein the third condition is at least one of:
    currently, there is no available uplink resource;
    currently, there is no semi-statically configured uplink resource;
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the logical channel that triggers the normal buffer status report can trigger a scheduling request.
  9. Method according to claim 7 or 8, characterized in that the fourth moment in time is later than the third moment in time.
  10. The method according to any of claims 7 to 9, wherein the third time and/or the fourth time is one of when the terminal device receives uplink resource grant, when the terminal device packages MAC PDU, and when the terminal device transmits MAC PDU.
  11. The method of claim 1, wherein the first condition is: currently, available uplink resources exist, and meanwhile, a fourth condition for triggering a scheduling request is met, and whether the normal cache state report is triggered by the overtime of a retransmission timer is judged;
    the terminal device determines that a scheduling request is triggered under a first condition, and the method comprises the following steps:
    if the normal buffer status report is triggered by the timeout of the retransmission timer, the terminal device determines not to trigger the scheduling request; or
    If the normal buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resource cannot carry the logical channel triggering the normal buffer status report, the terminal device determines to trigger the scheduling request.
  12. The method of claim 11, wherein the fourth condition is at least one of:
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the available uplink resources are not statically configured uplink resources;
    the logical channel that triggers the normal buffer status report can trigger a scheduling request.
  13. The method of claim 1, wherein the first condition is: the method comprises the steps that available uplink resources exist currently, a fifth condition for triggering a scheduling request is met, whether at least one logic channel is included in logic channels where data to be transmitted exist currently is judged, and the available uplink resources cannot bear the at least one logic channel;
    the terminal device determines that a scheduling request is triggered under a first condition, and the method comprises the following steps:
    if the available uplink resources currently exist and meet the fifth condition, and if the logical channel where the data to be transmitted currently exists includes the at least one logical channel and the available uplink resources cannot bear the at least one logical channel, the terminal device determines to trigger the scheduling request; or
    And if the available uplink resources can bear all the logic channels of the data to be transmitted, the terminal equipment determines not to trigger the scheduling request.
  14. The method of claim 13, wherein the fifth condition is at least one of:
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the available uplink resources are not statically configured uplink resources;
    the logic channel triggering the normal buffer status report can trigger a scheduling request;
    the normal buffer status report is triggered by a retransmission timer timeout.
  15. A terminal device, comprising:
    and the processing unit is used for determining to trigger the scheduling request or cancel the scheduling request under a first condition after the terminal equipment triggers the normal buffer status report.
  16. The terminal device of claim 15, wherein the first condition is: judging whether the available uplink resources can bear a logic channel triggering the normal buffer status report or not when the available uplink resources currently exist;
    the processing unit is specifically configured to:
    if the available uplink resources can bear the logical channel triggering the normal buffer status report, canceling the scheduling request at a first moment; or
    And if the available uplink resources cannot bear the logic channel triggering the normal buffer status report, canceling the scheduling request at a second moment.
  17. The terminal device of claim 16, wherein the second time is later than the first time.
  18. The terminal device according to claim 16 or 17, wherein the first time and/or the second time is one of when the terminal device receives an uplink resource grant, when the terminal device packages a MAC PDU, and when the terminal device transmits a MAC PDU.
  19. The terminal device according to any of claims 16 to 18, wherein the processing unit is further configured to trigger the scheduling request in a second condition before the processing unit determines to cancel the scheduling request in the first condition.
  20. The terminal device of claim 19, wherein the second condition is at least one of:
    currently, there is no available uplink resource;
    currently, there is no semi-statically configured uplink resource;
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the logical channel that triggers the normal buffer status report can trigger a scheduling request.
  21. The terminal device of claim 15, wherein the first condition is: judging whether the scheduling request is triggered by a third condition;
    the processing unit is specifically configured to:
    if the scheduling request is triggered by the third condition, canceling the scheduling request at a third moment; or
    And if the scheduling request is not triggered by the third condition, canceling the scheduling request at a fourth time.
  22. The terminal device of claim 21, wherein the third condition is at least one of:
    currently, there is no available uplink resource;
    currently, there is no semi-statically configured uplink resource;
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the logical channel that triggers the normal buffer status report can trigger a scheduling request.
  23. The terminal device according to claim 21 or 22, wherein the fourth time is later than the third time.
  24. The terminal device according to any of claims 21 to 23, wherein the third time and/or the fourth time is one of when the terminal device receives uplink resource grant, when the terminal device packages MAC PDU, and when the terminal device transmits MAC PDU.
  25. The terminal device of claim 15, wherein the first condition is: currently, available uplink resources exist, and meanwhile, a fourth condition for triggering a scheduling request is met, and whether the normal cache state report is triggered by the overtime of a retransmission timer is judged;
    the processing unit is specifically configured to:
    if the normal buffer status report is triggered by the overtime of the retransmission timer, determining not to trigger the scheduling request; or
    If the normal buffer status report is not triggered by the timeout of the retransmission timer and the available uplink resources cannot carry the logical channel triggering the normal buffer status report, determining to trigger the scheduling request.
  26. The terminal device of claim 25, wherein the fourth condition is at least one of:
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the available uplink resources are not statically configured uplink resources;
    the logical channel that triggers the normal buffer status report can trigger a scheduling request.
  27. The terminal device of claim 15, wherein the first condition is: currently, available uplink resources exist, a fifth condition for triggering a scheduling request is met, and whether at least one logical channel is included in the logical channels where data to be transmitted currently exist is judged, and the available uplink resources cannot bear the at least one logical channel;
    the processing unit is specifically configured to:
    if the available uplink resources currently exist and meet the fifth condition, and if the logical channel where the data to be transmitted currently exists includes the at least one logical channel and the available uplink resources cannot bear the at least one logical channel, the terminal device determines to trigger the scheduling request; or
    And if the available uplink resources can bear all the logic channels of the data to be transmitted, the terminal equipment determines not to trigger the scheduling request.
  28. The terminal device of claim 27, wherein the fifth condition is at least one of:
    after the terminal equipment triggers the normal buffer status report, a timer used for restraining the terminal equipment from triggering a scheduling request is in a closed state;
    the available uplink resources are not statically configured uplink resources;
    the logic channel triggering the normal buffer status report can trigger a scheduling request;
    the normal buffer status report is triggered by a retransmission timer timeout.
CN201880037053.7A 2018-04-02 2018-04-02 Scheduling request cancellation method and terminal equipment Active CN110720244B (en)

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2018/081645 WO2019191883A1 (en) 2018-04-02 2018-04-02 Method for triggering scheduling request, and terminal device

Publications (2)

Publication Number Publication Date
CN110720244A true CN110720244A (en) 2020-01-21
CN110720244B CN110720244B (en) 2021-02-26

Family

ID=68099730

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201880037053.7A Active CN110720244B (en) 2018-04-02 2018-04-02 Scheduling request cancellation method and terminal equipment

Country Status (2)

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

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022205382A1 (en) * 2021-04-01 2022-10-06 北京小米移动软件有限公司 Scheduling request triggering method and apparatus

Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101771521A (en) * 2009-01-06 2010-07-07 中兴通讯股份有限公司 Management method of status report retransmission timer in buffer zone
CN101772070A (en) * 2009-01-05 2010-07-07 中兴通讯股份有限公司 Processing method for retransmission buffer status report timer and terminal
CN102668680A (en) * 2009-10-09 2012-09-12 三星电子株式会社 Method and apparatus for transmitting scheduling request signal in mobile communication system
CN102726113A (en) * 2010-01-26 2012-10-10 夏普株式会社 Processing method and mobile station apparatus
CN103299699A (en) * 2011-01-11 2013-09-11 三星电子株式会社 Random access method and apparatus of UE in mobile communication system
WO2016072592A1 (en) * 2014-11-05 2016-05-12 Lg Electronics Inc. Method for canceling scheduling requests triggered by a sidelink buffer status report in a d2d communication system and device therefor
WO2017007148A1 (en) * 2015-07-06 2017-01-12 Lg Electronics Inc. Method for cancelling a buffer status report or a scheduling request in dual connectivity and a device therefor
CN107454620A (en) * 2016-04-28 2017-12-08 Lg电子株式会社 For sending the method and user equipment of data amount information
CN109561511A (en) * 2017-09-27 2019-04-02 夏普株式会社 Wireless communications method and equipment
CN109587770A (en) * 2017-09-29 2019-04-05 华为技术有限公司 The processing method and terminal device of scheduling request
CN110741714A (en) * 2017-06-16 2020-01-31 三星电子株式会社 Method for supporting multiple scheduling requests in a mobile communication system of the next generation

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101695194B (en) * 2009-10-22 2011-12-07 普天信息技术研究院有限公司 Multiplexing method for dispatching middle uplink logic channel in semi-static state by LTE systecm
CN102056332A (en) * 2009-11-02 2011-05-11 中兴通讯股份有限公司 Method and system for optimizing processing flow of buffer zone status report
US10966119B2 (en) * 2015-05-12 2021-03-30 Lg Electronics Inc. Method for transmitting a contention-based PUSCH in a wireless communication system and a device therefor

Patent Citations (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101772070A (en) * 2009-01-05 2010-07-07 中兴通讯股份有限公司 Processing method for retransmission buffer status report timer and terminal
CN101771521A (en) * 2009-01-06 2010-07-07 中兴通讯股份有限公司 Management method of status report retransmission timer in buffer zone
CN102668680A (en) * 2009-10-09 2012-09-12 三星电子株式会社 Method and apparatus for transmitting scheduling request signal in mobile communication system
CN102726113A (en) * 2010-01-26 2012-10-10 夏普株式会社 Processing method and mobile station apparatus
CN103299699A (en) * 2011-01-11 2013-09-11 三星电子株式会社 Random access method and apparatus of UE in mobile communication system
WO2016072592A1 (en) * 2014-11-05 2016-05-12 Lg Electronics Inc. Method for canceling scheduling requests triggered by a sidelink buffer status report in a d2d communication system and device therefor
WO2017007148A1 (en) * 2015-07-06 2017-01-12 Lg Electronics Inc. Method for cancelling a buffer status report or a scheduling request in dual connectivity and a device therefor
CN107454620A (en) * 2016-04-28 2017-12-08 Lg电子株式会社 For sending the method and user equipment of data amount information
CN110741714A (en) * 2017-06-16 2020-01-31 三星电子株式会社 Method for supporting multiple scheduling requests in a mobile communication system of the next generation
CN109561511A (en) * 2017-09-27 2019-04-02 夏普株式会社 Wireless communications method and equipment
CN109587770A (en) * 2017-09-29 2019-04-05 华为技术有限公司 The processing method and terminal device of scheduling request

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
INTEL CORPORATION: "Remaining issues in BSR", 《3GPP TSG RAN WG2 MEETING #101 R2-1802952》 *
SAMSUNG ELECTRONICS R&D INSTITUTE UK: "Outcome of e-mail discussion [101#30][NR UP/MAC]: TP for TS 38.321 on SR and BSR triggering and cancellation mechanisms", 《3GPP TSG-RAN WG2 #101 R2-1803873》 *
VIVO: "Discussion on the immediate transmission for BSR and SR cancel", 《3GPP TSG-RAN WG2 MEETING #101 R2-1801999》 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2022205382A1 (en) * 2021-04-01 2022-10-06 北京小米移动软件有限公司 Scheduling request triggering method and apparatus

Also Published As

Publication number Publication date
WO2019191883A1 (en) 2019-10-10
CN110720244B (en) 2021-02-26

Similar Documents

Publication Publication Date Title
CN111869314B (en) Wireless communication method, terminal device, chip and medium
CN111586751B (en) Triggering method of Buffer Status Report (BSR) and communication device
CN112369094B (en) Wireless communication method, terminal device and network device
CN111106920B (en) Information determination method, terminal equipment and network equipment
CN115022948A (en) Method for monitoring PDCCH, terminal equipment and network equipment
CN112335297A (en) Power distribution method and terminal equipment
CN111278150A (en) Uplink transmission method and terminal equipment
CN112219419B (en) Wireless communication method, terminal equipment and network equipment
CN111434065B (en) Method for transmitting uplink data, terminal equipment and network equipment
US20230397298A1 (en) Timer operating method, terminal device, and network device
CN110720244B (en) Scheduling request cancellation method and terminal equipment
CN114667701B (en) Method for determining uplink feedback resource and terminal equipment
WO2022067611A1 (en) Method for reporting listen-before-talk failure, terminal device, and network device
CN113794544B (en) Wireless communication method and terminal device
CN111418241B (en) Resource authorization method and equipment
CN111479256B (en) Information transmission method, terminal equipment and network equipment
CN114731239B (en) Conflict processing method and terminal equipment
CN115211061B (en) Information transmission method, terminal equipment and network equipment
CN115190628B (en) Resource transmission method and terminal equipment
WO2021237428A1 (en) Method for cancelling transmission of configured grant uplink channel, terminal device, and network device
CN115804185A (en) Wireless communication method, terminal equipment and network equipment
CN114846892A (en) Method for determining transmission priority and terminal equipment
CN116210314A (en) Wireless communication method, terminal device and network device
CN117480798A (en) Wireless communication method, terminal equipment and network equipment
CN116669062A (en) Method and device for sensing computing power

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination
GR01 Patent grant
GR01 Patent grant