Communication method and apparatus, chip, chip module, and storage medium

Abstract

A communication method, device, chip, chip module and storage medium. When a first timer is expired, not running or not configured, and there is no resource for a delay status report, a scheduling request is triggered, and one or more time length values of the first timer are less than a minimum value of one or more time length values of a second timer. By reasonably setting the time length of the first timer, the scheduling request can be reasonably triggered when there is no resource for the delay status report, and the delay status report can be sent in time.

Description

Technical Field

[0001] This application relates to the field of communication technology, and in particular to a communication method, device, chip, chip module and storage medium. Background Technology

[0002] Latency status information (i.e., the remaining latency of data packets) can be reported to network devices through the newly introduced media access control (MAC) control element (CE), and a new procedure is introduced to send latency status reports. A latency status report is triggered when the remaining latency of a data packet is less than or equal to a threshold value.

[0003] When a latency status report is triggered, it will be sent directly via MAC-CE if the resource exists. However, if the resource is unavailable, a scheduling request (SR) will be triggered to request the resource from which the latency status report will be sent. Currently, there is no solution for how to reasonably trigger a scheduling request. Summary of the Invention

[0004] This application provides a communication method, device, chip, chip module, and storage medium to reasonably trigger scheduling requests, thereby enabling timely transmission of latency status reports.

[0005] In a first aspect, a communication method is provided, which is executed by a terminal device or a chip or circuit for said terminal device.

[0006] The method includes triggering a scheduling request when a first timer times out, is not running, is not configured, and there are no resources available for delay status reporting. One or more duration values ​​of the first timer are less than the minimum value of one or more duration values ​​of a second timer. By using this method, by reasonably setting the duration of the first timer, a scheduling request can be reasonably triggered when the first timer times out, is not running, is not configured, and there are no resources available for delay status reporting, thereby ensuring timely transmission of the delay status report.

[0007] In one possible implementation, when the latency status report is triggered, the first timer is started or restarted. With this implementation, in addition to triggering the latency status report, a scheduling request can be triggered in scenarios where the first timer times out and there are no resources available for the latency status report after starting or restarting the first timer. A scheduling request can also be triggered in scenarios where the first timer is not running or configured, and there are no resources available for the latency status report.

[0008] In another possible implementation, the method further includes starting the first timer when the first timer is configured or when a second indication is applied. With this implementation, the first timer is started upon receiving the configuration information or the second indication and when a delay status report is triggered. In other words, if the first timer is not configured or its application is not indicated, the first timer is not started even if a delay status report is triggered.

[0009] In another possible implementation, the latency status report includes latency status information of one or more first granularities. The method further includes: starting the first timer when the first granularity of the triggered latency status report is configured with a corresponding first timer or when a second indication information of the corresponding first timer is applied; or starting the first timer when one or more first granularities of the triggered latency status report are configured with a corresponding first timer or when a second indication information of the corresponding first timer is applied. Using this implementation, more precise control can be achieved by configuring a corresponding first timer for the first granularity of the latency status report or by applying a corresponding first timer.

[0010] In another possible implementation, the first granularity includes at least one of the following: logical channel (LCH), logical channel group (LCG), data radio bearer, quality of service stream, protocol data unit set, and data burst.

[0011] In another possible implementation, the duration of the first timer can be measured in any of the following units: symbols, time slots, subframes, or milliseconds. This implementation allows for more timely and precise triggering of scheduling requests by setting the duration of the first timer to either symbols or time slots, and further enables more timely transmission of latency status reports.

[0012] In another possible implementation, the duration of the first timer is 0ms. With this implementation, the scheduling request is triggered directly without a delay after the delay status report is triggered, thus enabling more timely and accurate triggering of the scheduling request, and further allowing for more timely sending of the delay status report.

[0013] In another possible implementation, the duration of the first timer is associated with the service requirements. Using this implementation, the duration of the first timer can be set within the range of the service's latency requirements.

[0014] In another possible implementation, the duration of the first timer is less than or equal to a first threshold. Using this implementation, by reasonably setting the duration of the first timer, a scheduling request can be reasonably triggered when the first timer times out, is not running, or is not configured, and there are no resources available for delay status reporting, thereby enabling the timely sending of a delay status report.

[0015] In another possible implementation, the first timer is an extended timer of the second timer or the first timer is the second timer, and the duration value of the first timer includes the duration value of the second timer and / or one or more extended values; or the first timer is a scheduling request delay timer for a delay status report; or the duration value of the first timer includes one or more values, which are partially the same as or completely different from the duration value of the second timer.

[0016] In another possible implementation, the duration of the first timer is specified by the fourth timer, or the duration of the first timer is a valid duration, or the first timer expires after being started N times, where N is a positive integer greater than or equal to 1.

[0017] Secondly, a communication method is provided, which is executed by a terminal device or a chip or circuit for said terminal device.

[0018] The method includes: when a scheduling request is triggered, starting a third timer; wherein the third timer is used to indicate the prohibition duration for triggering the scheduling request. By using this method, when a scheduling request is triggered, the scheduling request can be triggered again after a delay of the third timer duration by starting the third timer, thus avoiding frequent triggering of scheduling requests.

[0019] In one possible implementation, the scheduling request is triggered in the following ways: the scheduling request is triggered after a latency status report is triggered, and no resources are available for the latency status report; or the scheduling request is triggered when a first message needs to be sent, or after the first message is triggered, and no resources are available for the first message, and the third timer is not configured, or the third timer is not running, not configured, or has timed out; or the scheduling request is triggered when a first message needs to be sent, or after the first message is triggered, and no resources are available for the first message, and the first granularity corresponding to the first message does not configure the third timer, or the first granularity corresponding to the first message configures the third timer or applies third indication information of the third timer, and the third timer is not running, not configured, or has timed out. With this implementation, the scheduling request can be triggered at the latency status report granularity or at the first granularity, allowing for accurate triggering of the scheduling request.

[0020] In another possible implementation, starting the third timer includes: starting the third timer when the third timer is configured or when the third indication information of the third timer is applied; or starting the third timer when a first granularity configures the corresponding third timer or applies the corresponding third indication information of the third timer; or starting the third timer when one or more first granularities configure the corresponding third timer or apply the corresponding third indication information of the third timer. Using this implementation, the starting of the third timer can be at the delay status reporting granularity or at the first granularity, enabling accurate starting of the third timer.

[0021] In yet another possible implementation, the first granularity includes at least one of the following: logical channel, logical channel group, data radio bearer, quality of service stream, protocol data unit set, and data burst.

[0022] In another possible implementation, the duration of the third timer can be measured in any of the following units: symbol, time slot, subframe, or millisecond. This implementation allows for more timely and precise triggering of scheduling requests by setting the duration of the third timer to either a symbol or a time slot, and further enables more timely sending of scheduling requests.

[0023] In another possible implementation, the duration of the third timer is 0ms. With this implementation, the scheduling request is triggered directly without delay, allowing for more timely and accurate triggering of the scheduling request, and further enabling more timely sending of the scheduling request.

[0024] In another possible implementation, the duration of the third timer is associated with the service requirements. Using this implementation, the duration of the third timer can be set within the range of the service's latency requirements.

[0025] In another possible implementation, the duration of the third timer is less than or equal to the second threshold. Using this implementation, by appropriately setting the duration of the third timer, when a scheduling request is triggered, the third timer is started, and the scheduling request can be triggered again after a delay of its duration, thus avoiding frequent triggering of scheduling requests.

[0026] In another possible implementation, the duration of the third timer is specified by the fifth timer, or the duration of the third timer is a valid duration, or the third timer expires after being activated M times, where M is a positive integer greater than or equal to 1.

[0027] Thirdly, a communication method is provided, which is executed by a terminal device or a chip or circuit for said terminal device.

[0028] The method includes: receiving first indication information, wherein the first indication information is used to indicate that a scheduling request is triggered when a latency status report is triggered; or the first indication information is used to indicate whether the latency status report can trigger a scheduling request; and triggering the scheduling request according to the first indication information when no resources are available for the latency status report. By using this method, triggering a scheduling request according to the first indication information when no resources are available for the latency status report can avoid frequent triggering of scheduling requests.

[0029] Fourthly, a communication method is provided, which is executed by a network device or a chip or circuit for said network device.

[0030] The method includes: sending first indication information, wherein the first indication information is used to indicate that a scheduling request is triggered when a latency status report is triggered; or the first indication information is used to indicate whether the latency status report can trigger a scheduling request. By using this method, by sending the first indication information, the terminal device can trigger a scheduling request based on the first indication information when there are no resources available for the latency status report, thus avoiding frequent triggering of scheduling requests.

[0031] Fifthly, a communication method is provided, which is executed by a terminal device or a chip or circuit for said terminal device.

[0032] The method includes receiving first configuration information, which includes one or more of the following: the duration of a first timer as described in the first aspect or any implementation of the first aspect; the duration of a third timer as described in the second aspect or any implementation of the second aspect; first indication information as described in the third aspect or any implementation of the third aspect; second indication information for applying the first timer; third indication information for applying the third timer; the duration or number of times the first timer is used; the duration or number of times the third timer is used; the duration of the first timer is specified by a fourth timer, or the duration of the first timer is a valid duration; the duration of the third timer is specified by a fifth timer, or the duration of the third timer is a valid duration. By using this method, by configuring the duration of the first timer, the duration of the third timer, the first indication information, the second indication information for applying the first timer, the third indication information for applying the third timer, the fourth timer, and the fifth timer on the network side, scheduling requests can be triggered reasonably to avoid frequent triggering of scheduling requests.

[0033] In a sixth aspect, a communication method is provided, which is performed by a network device or a chip or circuit for said network device.

[0034] The method includes sending first configuration information, which includes one or more of the following: the duration of a first timer as described in the first aspect or any implementation of the first aspect; the duration of a third timer as described in the second aspect or any implementation of the second aspect; first indication information as described in the third aspect or any implementation of the third aspect; second indication information for applying the first timer; third indication information for applying the third timer; the duration or number of times the first timer is used; the duration or number of times the third timer is used; the duration of the first timer is specified by a fourth timer, or the duration of the first timer is a valid duration; the duration of the third timer is specified by a fifth timer, or the duration of the third timer is a valid duration. By using this method, by configuring the duration of the first timer, the duration of the third timer, the first indication information, the second indication information for applying the first timer, the third indication information for applying the third timer, the fourth timer, and the fifth timer on the network side, scheduling requests can be triggered reasonably to avoid frequent triggering of scheduling requests.

[0035] In a seventh aspect, a communication method is provided, which is executed by a terminal device or a chip or circuit for said terminal device.

[0036] The method includes: triggering a latency status report; and triggering a random access procedure to send the latency status report. Using this method, after triggering the latency status report, when there are no resources to send the latency status report, triggering a random access procedure to send the latency status report ensures timely transmission of the latency status report, avoiding timeouts that could prevent timely scheduling.

[0037] In one possible implementation, triggering the random access procedure to send the delay status report includes sending the delay status report via random access message A or random access message 3.

[0038] In conjunction with aspects one through seven, in another possible implementation, the delay status report is triggered when the delay status information of the first data is less than or equal to the second threshold.

[0039] In conjunction with aspects one through seven, in yet another possible implementation, the scheduling request is used to request the resources for sending the delay status report.

[0040] In conjunction with aspects one through seven, in another possible implementation, the logical channel of the media access control-control element carrying the delay status report has a higher priority than the sidelink-buffer status report, but a lower priority than the timed advance report. Using this implementation, by reasonably setting the priority of the logical channel of the media access control-control element carrying the delay status report, the delay status report can be sent in a timely manner.

[0041] Eighthly, a communication device is provided for implementing the communication methods described in any of the first, second, third, fifth, and seventh aspects, or any of the first, second, third, fifth, and seventh aspects. The device may be a terminal device, a module applied to a terminal device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of the terminal device. In one implementation, the communication device may include a transmitting unit, a receiving unit, and a processing unit. The transmitting unit and the receiving unit may be independent or combined (which may be referred to as a "transmit-receiver unit").

[0042] A ninth aspect provides a communication apparatus for implementing the communication methods described in the fourth, sixth, or any of the fourth and sixth aspects above. The apparatus may be a network device, a module applied to a network device (e.g., a processor, chip, or chip system), or a logical node, logical module, or software capable of implementing all or part of the functions of a network device. In one implementation, the communication apparatus may include a transmitting unit, a receiving unit, and a processing unit. The transmitting unit and the receiving unit may be independent or combined (which may be referred to as a "transmit-receive unit").

[0043] In one possible implementation, the communication device in the eighth to ninth aspects above includes a module for executing the method in any one of the first to seventh aspects or any implementation thereof.

[0044] Wherein, when the communication device is used to implement the method as described in the first aspect or any implementation of the first aspect, the communication device includes a processing unit and may further include a transceiver unit; wherein, the processing unit is used to trigger a scheduling request when the first timer times out, is not running or is not configured, and there are no resources for delay status reporting, wherein one or more duration values ​​of the first timer are less than the minimum value of one or more duration values ​​of the second timer.

[0045] Optionally, the processing unit is further configured to start or restart the first timer when the delay status report is triggered.

[0046] Optionally, the processing unit is further configured to start the first timer when the first timer is configured or when the second indication information of the first timer is applied.

[0047] Optionally, the processing unit is further configured to start the first timer when the first granularity of the delayed status report is configured with the corresponding first timer or the second indication information of the corresponding first timer is applied; or to start the first timer when one or more first granularities of the delayed status report are configured with the corresponding first timer or the second indication information of the corresponding first timer is applied.

[0048] Optionally, the first granularity includes at least one of the following: logical channel, logical channel group, data radio bearer, quality of service stream, protocol data unit set, and data burst.

[0049] Optionally, the duration of the first timer can be in any of the following units: symbol, time slot, subframe, or millisecond.

[0050] Optionally, the duration of the first timer is 0ms.

[0051] Optionally, the duration of the first timer is associated with the service.

[0052] Optionally, the duration of the first timer is less than or equal to the first threshold.

[0053] Optionally, the first timer is an extended timer of the second timer or the first timer is the second timer, and the duration value of the first timer includes the duration value of the second timer and / or one or more extended values; or the first timer is a scheduling request delay timer for a delay status report; or the duration value of the first timer includes one or more values, and the one or more values ​​are partially the same as or completely different from the duration value of the second timer.

[0054] Optionally, the duration of the first timer is specified by the fourth timer, or the duration of the first timer is a valid duration, or the first timer expires after being started N times, where N is a positive integer greater than or equal to 1.

[0055] When the communication device is used to implement the method as described in the second aspect or any implementation of the second aspect, the communication device includes a processing unit and may further include a transceiver unit; wherein, the processing unit is used to start a third timer when a scheduling request is triggered; wherein, the third timer is used to indicate the prohibition duration triggered by the scheduling request.

[0056] Optionally, the processing unit is further configured to trigger the scheduling request when a latency status report is triggered and there are no resources available for the latency status report; or when the first information needs to be sent or the first information is triggered and there are no resources available for the first information, and the third timer is not configured, or the third timer is not running, not configured, or has timed out; or when the first information needs to be sent or the first information is triggered and there are no resources available for the first information, and the first granularity corresponding to the first information does not configure the third timer, or the first granularity corresponding to the first information configures the third timer or applies the third indication information of the third timer, and the third timer is not running, not configured, or has timed out, the scheduling request is triggered.

[0057] Optionally, the processing unit is further configured to start the third timer when the third timer is configured or the third indication information of the third timer is applied; or to start the third timer when the first granularity is configured with the corresponding third timer or the third indication information of the corresponding third timer is applied; or to start the third timer when one or more first granularities are configured with the corresponding third timer or the third indication information of the corresponding third timer is applied.

[0058] Optionally, the first granularity includes at least one of the following: logical channel, logical channel group, data radio bearer, quality of service stream, protocol data unit set, and data burst.

[0059] Optionally, the duration of the third timer can be measured in any of the following units: symbol, time slot, subframe, or millisecond.

[0060] Optionally, the duration of the third timer is 0ms.

[0061] Optionally, the duration of the third timer is associated with the service.

[0062] Optionally, the duration of the third timer is less than or equal to the second threshold.

[0063] Optionally, the duration of the third timer is specified by the fifth timer, or the duration of the third timer is a valid duration, or the third timer expires after being activated M times, where M is a positive integer greater than or equal to 1.

[0064] When the communication device is used to implement the method as described in the third aspect or any implementation of the third aspect, the communication device includes a transceiver unit and may further include a processing unit; wherein the transceiver unit is used to receive first indication information, the first indication information being used to indicate that a scheduling request is triggered when a delay status report is triggered; or the first indication information being used to indicate whether the delay status report can trigger a scheduling request; and when there are no resources available for the delay status report, to trigger the scheduling request according to the first indication information.

[0065] When the communication device is used to implement the method as described in the fourth aspect or any of the implementations of the fourth aspect, the communication device includes a transceiver unit and may further include a processing unit; wherein the transceiver unit is used to send first indication information, the first indication information being used to indicate that a scheduling request is triggered when a latency status report is triggered; or the first indication information being used to indicate whether the latency status report can trigger a scheduling request; and when there are no resources available for the latency status report, to trigger the scheduling request according to the first indication information.

[0066] When the communication device is used to implement the method as described in the fifth aspect or any implementation of the fifth aspect, the communication device includes a transceiver unit and may further include a processing unit; wherein the transceiver unit is used to receive first configuration information, the first configuration information including one or more of the following: the duration of a first timer as described in the first aspect or any implementation of the first aspect, the duration of a third timer as described in the second aspect or any implementation of the second aspect, first indication information as described in the third aspect or any implementation of the third aspect, second indication information for applying the first timer, third indication information for applying the third timer, the duration or number of times the first timer is used, the duration or number of times the third timer is used, the duration of the first timer is specified by a fourth timer, or the duration of the first timer is a valid duration, the duration of the third timer is specified by a fifth timer, or the duration of the third timer is a valid duration.

[0067] When the communication device is used to implement the method as described in the sixth aspect or any implementation of the sixth aspect, the communication device includes a transceiver unit and may further include a processing unit; wherein the transceiver unit is used to send first configuration information, the first configuration information including one or more of the following: the duration of a first timer as described in the first aspect or any implementation of the first aspect, the duration of a third timer as described in the second aspect or any implementation of the second aspect, first indication information as described in the third aspect or any implementation of the third aspect, second indication information for applying the first timer, third indication information for applying the third timer, the duration or number of times the first timer is used, the duration or number of times the third timer is used, the duration of the first timer is specified by a fourth timer, or the duration of the first timer is a valid duration, the duration of the third timer is specified by a fifth timer, or the duration of the third timer is a valid duration.

[0068] When the communication device is used to implement the method as described in the seventh aspect or any implementation of the seventh aspect, the communication device includes a processing unit and a transceiver unit; wherein the processing unit is used to trigger a delay status report; and the transceiver unit is used to trigger a random access procedure to send the delay status report.

[0069] Optionally, the transceiver unit is configured to send the delay status report via random access message A or random access message 3.

[0070] In another possible implementation, the communication device in aspects eight to nine above includes a processor coupled to a memory; the processor is configured to implement the corresponding functions in the communication method described above. The memory is coupled to the processor and stores necessary programs (instructions) and / or data for the device. Optionally, the communication device may further include a communication interface for enabling communication between the device and other network elements. Optionally, the memory may be located inside or outside the communication device.

[0071] In another possible implementation, the communication device in aspects eight to nine above includes a processor and a transceiver device. The processor is coupled to the transceiver device and is used to execute computer programs or instructions to control the transceiver device to receive and send information. When the processor executes the computer programs or instructions, it is also used to implement the above method through logic circuits or executing code instructions. The transceiver device can be a transceiver, a transceiver circuit, or an input / output interface, used to receive signals from other communication devices besides the communication device and transmit them to the processor, or to send signals from the processor to other communication devices besides the communication device. When the communication device is a chip, the transceiver device is a transceiver circuit or an input / output interface.

[0072] When the communication device in aspects eight to nine above is a chip, the transmitting unit can be an output unit, such as an output circuit or a communication interface; the receiving unit can be an input unit, such as an input circuit or a communication interface. When the communication device is a terminal, the transmitting unit can be a transmitter or a receiver; the receiving unit can be a receiver or a receiver.

[0073] In a tenth aspect, a computer-readable storage medium is provided, wherein a computer program or instructions are stored therein, which, when executed, implement the methods described in the above aspects.

[0074] In an eleventh aspect, a computer program product containing instructions is provided, which, when executed on a communication device, causes the communication device to perform the methods described in the above aspects.

[0075] In a twelfth aspect, a communication system is provided, which includes the communication device described in the eighth aspect and the communication device described in the ninth aspect. Attached Figure Description

[0076] Figure 1A This application provides a schematic diagram of the architecture of a communication system. Figure 1B This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application; Figure 2 This is a schematic diagram of the architecture of another communication system provided in an embodiment of this application; Figure 3 A schematic diagram illustrating the format of a latency status report provided in an embodiment of this application; Figure 4 This is a schematic diagram illustrating the reporting of a delay status report in this application where the current timer cannot be reused; Figure 5 A flowchart illustrating a communication method provided in an embodiment of this application; Figure 6A A diagram illustrating an example of triggering a scheduling request; Figure 6B A diagram illustrating another example of triggering a scheduling request; Figure 7 A flowchart illustrating another communication method provided in an embodiment of this application; Figure 8 A flowchart illustrating yet another communication method provided in an embodiment of this application; Figure 9 A flowchart illustrating yet another communication method provided in an embodiment of this application; Figure 10 A flowchart illustrating yet another communication method provided in an embodiment of this application; Figure 11 This is a schematic diagram of the structure of a communication device provided in an embodiment of this application; Figure 12 This is a schematic diagram of another communication device provided in an embodiment of this application. Detailed Implementation

[0077] The solutions provided in the embodiments of this application will be described in detail below with reference to the accompanying drawings.

[0078] The terms "one or more" as used in this application refer to one or more items. "More than" means two or more items. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship. Furthermore, it should be understood that although the terms "first," "second," etc., may be used to describe objects in this application, these objects should not be limited to these terms. These terms are only used to distinguish the objects from each other.

[0079] The terms "comprising" and "having," and any variations thereof, used in this application as described below, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or optionally include other steps or units inherent to such process, method, product, or apparatus. It should be noted that in this application, words such as "exemplary" or "for example" are used to indicate illustrative, explanatory, or descriptive purposes. Any method or design described as "exemplary" or "for example" in this application should not be construed as preferred or advantageous over other methods or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner.

[0080] The technology provided in this application can be applied to various communication systems, for example, the communication system can be a fourth-generation (4G) communication system. th Generation 4G) communication systems (such as Long Term Evolution (LTE) systems), 5G (5G) th This refers to a generation of communication systems, including 5G, WiMAX (worldwide interoperability for microwave access), WLAN (wireless local area network), a converged system of multiple systems, or future communication systems such as 6G. 5G communication systems can also be called new radio (NR) systems.

[0081] Figure 1A A schematic diagram of a communication system according to an embodiment of this application is provided. The communication system may include one or more network devices (only one is shown in the figure) and one or more terminal devices connected to the network devices. A network device can transmit data or control signaling to one or more terminal devices. Figure 1B Another communication system shown allows multiple network devices to simultaneously transmit data or control signaling to a single terminal device.

[0082] In the aforementioned communication system, the network device can be any device with wireless transceiver capabilities, including but not limited to: base station (NodeB), evolved NodeB, base station in a 5G communication system, base station or network device in a future communication system, access node in a Wi-Fi system, wireless relay node, wireless backhaul node, etc. The network device can also be a wireless controller in a cloud radio access network (CRAN) scenario. The network device can also be a small cell, transmission reference point (TRP), etc. The embodiments of this application do not limit the specific technology or device form used in the network device.

[0083] A terminal device is a device with wireless transceiver capabilities that can be deployed on land (including indoors or outdoors), handheld, wearable, or vehicle-mounted; it can also be deployed on water, such as on ships; and it can be deployed in the air, such as on airplanes, balloons, and satellites. Terminal devices can be mobile phones, tablets, computers with wireless transceiver capabilities, wearable devices, drones, helicopters, airplanes, ships, robots, robotic arms, smart home devices, virtual reality (VR) terminal devices, augmented reality (AR) terminal devices, wireless terminal devices in industrial control, wireless terminal devices in self-driving, complete vehicles, functional modules within vehicles, wireless terminal devices in remote medical care, wireless terminal devices in smart grids, wireless terminal devices in transportation safety, wireless terminal devices in smart cities (e.g., streetlights), wireless terminal devices in smart homes, and so on. The embodiments in this application do not limit the application scenarios. Terminal equipment may also be referred to as user equipment (UE), access terminal equipment, UE unit, mobile station, mobile station, remote station, remote terminal equipment, mobile device, terminal, wireless communication equipment, UE agent, or UE device, etc. The embodiments of this application do not limit the specific technologies or equipment forms used in the terminal equipment.

[0084] Optionally, in this embodiment, the terminal device or network device includes a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on top of the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory (also called main memory). The operating system can be any one or more computer operating systems that implement business processing through processes, such as Linux, Unix, Android, iOS, or Windows. The application layer includes applications such as browsers, address books, word processing software, and instant messaging software. Furthermore, this embodiment does not specifically limit the specific structure of the execution entity of the method provided in this embodiment. Communication can be performed by running a program that records the code of the method provided in this embodiment. For example, the execution entity of the method provided in this embodiment can be a terminal device or a network device, or a functional module in the terminal device or network device capable of calling and executing a program.

[0085] In other words, the relevant functions of the terminal device or network device in the embodiments of this application can be implemented by one device, multiple devices working together, or one or more functional modules within a single device. This application does not impose specific limitations on these aspects. It is understood that the aforementioned functions can be network elements within hardware devices, software functions running on dedicated hardware, a combination of hardware and software, or virtualization functions instantiated on a platform (e.g., a cloud platform).

[0086] Figure 1A and Figure 1B The communication between network devices and terminal devices in the communication system shown can also be represented in another form, such as... Figure 2 As shown, terminal device 10 includes a processor 101, a memory 102, and a transceiver 103. Transceiver 103 includes a transmitter 1031, a receiver 1032, and an antenna 1033. Network device 20 also includes a processor 201, a memory 202, and a transceiver 203. Transceiver 203 includes a transmitter 2031, a receiver 2032, and an antenna 2033. Receiver 1032 can be used to receive transmission control information through antenna 1033, and transmitter 1031 can be used to send transmission feedback information to network device 20 through antenna 1033. Transmitter 2031 can be used to send transmission control information to terminal device 10 through antenna 2033, and receiver 2032 can be used to receive transmission feedback information sent by terminal device 10 through antenna 2033.

[0087] The processor 101 / processor 201 may be a CPU, a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits used to control the execution of the program of the present application.

[0088] Memory 102 / Memory 202 can be a device with storage function. For example, it can be read-only memory (ROM) or other types of static storage devices capable of storing static information and instructions; random access memory (RAM) or other types of dynamic storage devices capable of storing information and instructions; electrically erasable programmable read-only memory (EEPROM); compact disc read-only memory (CD-ROM) or other optical disc storage; optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.); magnetic disk storage media or other magnetic storage devices; or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory can exist independently and be connected to the processor via communication lines. The memory can also be integrated with the processor.

[0089] The memory 102 / 202 stores computer execution instructions for implementing the scheme of this application, and the processor 101 / 201 controls the execution. The processor 101 / 201 executes the computer execution instructions stored in the memory 102 / 202, thereby implementing the communication method provided in the embodiments of this application.

[0090] Alternatively, in the embodiments of this application, the processor 101 / processor 201 may execute the processing-related functions in the communication method provided in the following embodiments of this application.

[0091] The computer execution instructions in the embodiments of this application may also be referred to as application code, and the embodiments of this application do not specifically limit this.

[0092] For certain services, such as extended reality (XR) (whose characteristics mainly include non-integer periods, arrival time jitter, variable packet sizes, multi-stream services, and large data volumes) and cloud gaming, latency requirements are high. Therefore, a latency status report is triggered when the remaining latency of a data packet is less than or equal to a threshold value. The latency status report in this application can be any report related to latency status information. For example, it can be called a delay status report (DSR). Of course, it can also have other names; this application does not limit this.

[0093] like Figure 3 The diagram shown illustrates a format of a latency status report provided in an embodiment of this application. The aforementioned data can be carried in multiple logical channel groups (LCGs), and the latency status report can include data volume information for multiple LCGs (i.e.,...). Figure 3 The buffer size and latency status information shown are displayed. Figure 3 The example illustrates the data volume information and latency status information for LCGs 0 through 7. When only one LCG in the latency status report is transmitting latency status information, the UE will report a short-format latency status report; when more than one LCG in the latency status report is transmitting latency status information, the UE will report a long-format latency status report.

[0094] The latency status report can be carried in a new MACCE. When the UE triggers the latency status report, if a resource exists, the latency status report is assembled and sent on that resource. Here, "assembly" can also be understood as "generation", that is, assembling or generating the latency status report in the above format.

[0095] When no resources are available for latency status reporting, a scheduling request needs to be triggered to request resources for latency status reporting. The scheduling request can be called an SR, or any other name; this application makes no limitation on this.

[0096] Currently, when resources are unavailable, scheduling requests can be triggered via regular buffer status reports (BSRs). The buffer status report (BSR) can be controlled via the logical channel scheduling request-delay timer (logicalChannelSR-DelayTimer) parameter to avoid frequent scheduling requests. Specifically, when a BSR is triggered, the logicalChannelSR-DelayTimer is started; when the logicalChannelSR-DelayTimer times out, a scheduling request is triggered.

[0097] The possible duration values ​​for the logicalChannelSR-DelayTimer are: {sf20,sf40,sf64,sf128,sf512,sf1024,sf2560,spare1}, and the unit of its duration value is a sub-frame (sf).

[0098] However, the delay status report in this application is triggered more frequently than the BSR (it can be triggered as long as the remaining delay of the data packet is below a threshold). Therefore, if the scheduling request is triggered directly without controlling the triggering frequency of the scheduling request in the absence of resources, it may lead to the frequent triggering of the scheduling request.

[0099] The cycle time for XR services is typically between 10ms and 30ms. The purpose of the latency status report is to report the remaining latency of services that are about to reach their latency requirements, such as... Figure 4 The diagram shown illustrates how the delay status report in this application cannot reuse the current timer. If the current logicalChannelSR-DelayTimer is directly reused, the remaining delay of the XR service is already less than 20ms. In this case, the delay will time out and be discarded before the logicalChannelSR-DelayTimer has even passed. Therefore, the existing value of logicalChannelSR-DelayTimer cannot meet the requirements of the delay status report.

[0100] On the one hand, dynamic scheduling after a period of delay can help reduce the triggering of scheduling requests and random access (RA) processes. However, the existing logicalChannelSR-DelayTimer cannot meet the needs of XR services, so it is necessary to enhance the logicalChannelSR-DelayTimer. On the other hand, in order to send a delay status report as soon as possible to obtain network-side scheduling and help the UE send data packets that are about to expire in a timely manner, resources can be requested directly without delay, and delay can be applied after the resources are requested.

[0101] Therefore, this application provides a communication scheme in which a scheduling request is triggered when a first timer times out, is not running, or is not configured, and there are no resources available for delay status reporting. One or more duration values ​​of the first timer are less than the minimum value of one or more duration values ​​of a second timer. By reasonably setting the duration of the first timer, a scheduling request can be reasonably triggered when there are no resources available for delay status reporting, thereby enabling timely transmission of delay status reports.

[0102] Based on the above communication system, the communication method provided in this application is described below: In this application, the phrase "sending information to... (e.g., UE)" or the related illustrations in the accompanying drawings can be understood as the destination of the information being the UE. This can include sending information directly or indirectly to the UE. Similarly, "receiving information from... (e.g., UE)" or "receiving information from... (e.g., UE)" or the related illustrations in the accompanying drawings can be understood as the source of the information being the UE. This can include receiving information directly or indirectly from the UE. The information may undergo necessary processing between the source and destination, such as format changes, but the destination can understand the valid information from the source. Similar expressions in this application can be interpreted similarly, and will not be elaborated further here.

[0103] The communication method provided in the embodiments of this application is described in detail below. It is understood that this application uses a UE and a network device as examples to illustrate the interaction, but this application does not limit the execution subject of the interaction. For example, the UE in the method provided by this application can also be a chip, chip system, or processor applied to the UE, or it can be a logical node, logical module, or software capable of implementing all or part of the UE's functions; the network device in the method provided by this application can also be a chip, chip system, or processor applied to the network device, or it can be a logical node, logical module, or software capable of implementing all or part of the network device's functions.

[0104] It is understood that, in the above embodiments, the methods and / or steps implemented by the UE can also be implemented by components (e.g., chips or circuits) that can be used by the UE; and the methods and / or steps implemented by the network device can also be implemented by components (e.g., chips or circuits) that can be used by the network device.

[0105] like Figure 5 The diagram shown is a flowchart illustrating a communication method provided in an embodiment of this application. Exemplarily, the method may include the following steps: S501. When the delay status report is triggered, start or restart the first timer.

[0106] In one implementation, the latency status report can be any report containing latency status information. As long as the message conveys latency status information, it can be a latency status report. Therefore, the latency status report can be a MAC CE, downlink control information (DCI), radio resource control (RRC) message, packet data convergence protocol (PDCP) CE, etc. In another implementation, the latency status report can be a DSR.

[0107] In one implementation, the latency status information can be the remaining latency of the first data, maintenance latency, cache latency, etc. Any information related to latency can be called latency status information.

[0108] In one implementation, the first data is uplink data, downlink data, or non-access stratum (NAS) data; the first data can be control plane data, user plane data, data packets, signaling, data transmitted in signalalling radio bearers (SRB), or data transmitted in data radio bearers (DRB).

[0109] For example, the UE triggers a DSR. The DSR is used to indicate the delay status information of the first data.

[0110] For example, a scenario that triggers a latency status report could be: When the latency status information of the first data is less than or equal to a certain threshold, the latency status report is triggered.

[0111] In one implementation, the UE's PDCP layer receives first data. If the delay status information of this first data is less than or equal to a certain threshold, the PDCP layer transmits indication information to the MAC layer to indicate the triggering of DSR. Upon receiving the indication information, the MAC layer triggers DSR.

[0112] One implementation involves the UE's MAC layer determining whether the latency status information of the first data is less than or equal to a certain threshold, and then triggering a latency status report.

[0113] In this embodiment, a first timer can be configured. This first timer can be used to extend the duration of the first timer after triggering the delay status report before triggering the scheduling request, or it can be used to trigger the delay of the scheduling request.

[0114] After configuring the first timer, it can be started when the latency status report is triggered. That is, when the latency status report is triggered and there are no resources available for the latency status report, the scheduling request is not triggered immediately, but the duration of the first timer is extended before the scheduling request is triggered, in order to avoid frequent triggering of scheduling requests.

[0115] Furthermore, when configuring the first timer, the duration or number of times the first timer is used can also be configured. One implementation of this duration is a fourth timer, which specifies the duration of the first timer's use, indicating how long the configured first timer is valid. For example, if the first configuration information is received at the first moment, and this first configuration information is used to configure the first timer, and the fourth timer is started at the first moment, with a duration of 100 subframes, then the first timer can be started when the delay status report is triggered between the first moment and the first moment + 100 subframes; after the first moment + 100 subframes, the first timer cannot be started when the delay status report is triggered. Another implementation is that the duration of the first timer is a validity period. For example, if the first configuration information is received at the first moment, and the validity period is 100 subframes, then the first timer expires after the 100th subframe after receiving the first configuration information, or the first moment (which is not the moment the first configuration information is received) is specified, and the first timer expires 100 subframes after the first moment. Yet another implementation is that the first timer expires after being started N times. N is a positive integer greater than or equal to 1.

[0116] When the time delay status report is triggered, the first timer is started, which can be implemented in the following ways: In the first implementation, the first timer is started when a first timer is configured or when a second indication message for applying the first timer is received. This start is per DSR (Delay Status Report). For example, the network device can send configuration information to the UE to configure the first timer. Further, after configuring the first timer, the network device can also send a second indication message to the UE to instruct the application of the first timer. Upon receiving the configuration information or the second indication message, and when a delay status report is triggered, the UE starts the first timer. In other words, if the first timer is not configured or its application is not indicated, the first timer will not be started even if a delay status report is triggered.

[0117] In the second implementation, the first timer is started when the first granularity of the latency status report is configured with a corresponding first timer or when the application has second indication information for the corresponding first timer. This start is at the first granularity. For example, the first granularity can be LCH / LCG / data radio bearers (DRB) / quality of service (QoS) stream / protocol data unit set (PDU set) / data burst, which can be interpreted as a channel, a data stream, or a dataset for transmitting data. For example, in this case, each LCH / LCG that triggers the latency status report corresponds to a first timer. If the LCH / LCG that triggers the latency status report is configured with a corresponding first timer or when the application has second indication information for the corresponding first timer, then the first timer is started.

[0118] In the third implementation, the first timer is started when one or more first granularities that trigger the latency status report are configured with a corresponding first timer or when a second indication information for the corresponding first timer is applied. For example, the first granularity is LCH / LCG / DRB / QoS stream / PDU set / data burst. For example, one implementation is that each LCH / LCG in the latency status report triggered in this case corresponds to a first timer; if all LCH / LCGs in the latency status report are configured with a corresponding first timer or when an indication information for the corresponding first timer is applied, then the first timer is started. Another implementation is that if one or more LCH / LCGs in all LCH / LCGs of the latency status report are configured with a corresponding first timer or when an indication information for the corresponding first timer is applied, then the first timer is started.

[0119] The first to the third implementations mentioned above can be independent or combined solutions.

[0120] In this embodiment, the second timer (e.g., the logicalChannelSR-DelayTimer mentioned above) is not directly reused because the current value of the second timer cannot meet the requirement of reasonably triggering a scheduling request when the delay status report is triggered. Since the delay status report in this application is triggered more frequently than the BSR (it can be triggered as long as the remaining delay of the data packet is below a threshold), when there are no resources available for the delay status report, scheduling requests need to be triggered more frequently to request resources. Therefore, in this embodiment, one or more duration values ​​of the first timer are less than the minimum value of one or more duration values ​​of the second timer.

[0121] The duration of the first timer can be implemented in the following ways: In the first implementation, the duration of the first timer can be in any of the following units: symbol, time slot, subframe, or millisecond. The aforementioned logicalChannelSR-DelayTimer is in units of subframes. This embodiment allows the first timer's duration to be set to either a symbol or a time slot, enabling more timely and accurate triggering of scheduling requests and, further, more timely transmission of delay status reports.

[0122] In the second implementation, the duration of the first timer is 0ms, meaning that the scheduling request is triggered directly without any delay after the delay status report is triggered. This allows for more timely and accurate triggering of the scheduling request, and further, for more timely sending of the delay status report.

[0123] In the third implementation, the duration of the first timer is associated with the service requirements. For example, the duration of the first timer can be set according to the latency requirements of the service. For instance, if the latency requirement for XR is 0-30ms, then the value of the first timer can be 0-30ms.

[0124] In the fourth implementation, the duration of the first timer can be a range of values. For example, the duration of the first timer can be less than or equal to a first threshold, and the value of the first timer can be an integer or a decimal. For instance, if the value of the first timer is an integer, its data structure is of integer type, and its value is [A, B]. In this case, any integer between A and B can be configured.

[0125] For example, the first timer may be an extension of the second timer, or the first timer may be the second timer. In this case, the duration value of the first timer includes the duration value of the second timer and / or one or more extension values. For example, the second timer is the aforementioned logicalChannelSR-DelayTimer. In one scenario, the first timer is an extension of the second timer, in which case the second timer may only include the extension value, or it may include both the duration value of the second timer and the extension value. In another scenario, the first timer is the second timer, in which case the first timer includes both the duration value of the second timer and the extension value. The first timer is an improvement on the second timer for different application scenarios. To trigger scheduling requests more promptly according to business needs, the duration value of the first timer may include not only the duration value of the second timer but also / or one or more extension values.

[0126] Alternatively, the first timer can be a scheduling request delay timer for the delay status report. That is, the first timer is a newly defined timer. For example, the first timer can be dedicated solely to this delay status report.

[0127] Alternatively, the duration of the first timer may include one or more values, some of which may be the same as or completely different from the duration of the second timer. In this case, the first timer is a newly defined SR delay timer.

[0128] Alternatively, the configuration granularity of the first timer is set to the first granularity, meaning that each first granularity will be configured with a corresponding timer. The first timer will only be started or restarted when there is a behavior related to the first granularity.

[0129] In one implementation, if the first timer is configured, the value of the second timer is ignored. For example, when both timers are configured simultaneously, the latency status reporting process should use the second timer. When the first timer is configured but the second timer is not, in one scenario, if an instruction to apply the first timer related to the latency status report is received, the latency status reporting process will apply the first timer; in another scenario, the latency status report will directly apply the first timer. For example, if the second timer is configured but the first timer is not, and an instruction to apply the second timer to the latency status report is received, the second timer will be started if the latency status report is triggered; if both the first and second timers are configured simultaneously, the latency status report will apply the first timer. In another implementation, if there are two or more first timers, multiple first timers will not be configured simultaneously.

[0130] It is understood that in this embodiment, in addition to the delay status report triggering, a scheduling request can also be triggered in scenarios where the first timer times out after starting or restarting and there are no resources available for the delay status report. Furthermore, a scheduling request can also be triggered in scenarios where the first timer is not running or configured, and there are no resources available for the delay status report. Therefore, step S501 is optional and is represented by a dashed line in the figure.

[0131] S502. When the first timer times out, is not running or not configured, and there are no resources available for delay status reporting, a scheduling request is triggered.

[0132] When the first timer times out, is not running, or is not configured, and there are no resources available for latency status reporting, a scheduling request is triggered to request resources for sending latency status reports. This scheduling request is specifically for requesting resources for sending latency status reports.

[0133] No resources available for delay status reporting means that there are no resources available, the resources are insufficient to accommodate delay status reporting, or the logical channel priority is not met.

[0134] One implementation receives a first timer and triggers a scheduling request when the first timer times out or is not running, and there are no resources available for delay status reporting.

[0135] One implementation is that a scheduling request cannot be triggered while the first timer is running.

[0136] In the first implementation, a scheduling request is triggered when the first timer corresponding to a delayed status report expires, is not running, or is not configured. This triggering is at the delayed status report granularity (per DSR). In this case, each delayed status report corresponds to a first timer; if the first timer of that delayed status report expires, a scheduling request is triggered. For example, as... Figure 6A The diagram illustrates an example of triggering a scheduling request. When delay status report 1 is triggered at time T1, Timer1 is started; when delay status report 2 is triggered at time T2, Timer2 is started. When Timer1 times out, scheduling request 1 (requesting resources for delay status report 1) is triggered, but scheduling request 2 (requesting resources for delay status report 2) is not triggered. In another implementation, such as... Figure 6B The diagram illustrates another example of triggering a scheduling request. When delay status report 1 is triggered at time T1, Timer1 is started. When delay status report 2 is triggered at time T2, Timer1 is restarted, where time T2 is later than time T1. In this case, if Timer1 times out, scheduling requests corresponding to all delay status reports will be triggered. Therefore, the first timer timeout corresponding to the triggered delay status report can be referred to as the first timer timeout corresponding to the most recently triggered delay status report.

[0137] In the second implementation, a scheduling request is triggered when the first timer corresponding to the first granularity of the latency status report times out, is not running, or is not configured. This triggering is at the first granularity. For example, the first granularity is LCH / LCG / DRB / QoS stream / PDU set / data burst, which can be interpreted as a channel, a data stream, or a dataset for data transmission. For example, in this case, each LCH / LCG of the triggered latency status report corresponds to a first timer. If the first timer corresponding to the LCH / LCG of the latency status report times out, a scheduling request is triggered. For instance, if latency status report 1 is triggered at time T1, then LCG1 of latency status report 1 has its corresponding Timer1. When Timer1 times out, a scheduling request is triggered.

[0138] In the third implementation, a scheduling request is triggered when the first timer corresponding to one or more of the first granularities that trigger the latency status report times out, is not running, or is not configured. For example, the first granularity is LCH / LCG / DRB / QoS stream / PDUset / data burst. For example, in this case, each LCH / LCG of the triggered latency status report corresponds to a first timer. If the first timers corresponding to all LCH / LCGs of the latency status report time out, a scheduling request is triggered. In one implementation, taking LCG as the first granularity as an example, the scheduling request can be triggered when the first timer corresponding to one or more of the LCGs that trigger the latency status report times out, is not running, or is not configured. For example, if latency status report 1 is triggered at time T1, then LCG1 of latency status report 1 has its corresponding Timer1, and LCG2 has its corresponding Timer2. When Timer1 times out, a scheduling request can be triggered. In another implementation, the scheduling request can be triggered when the first timers corresponding to all LCGs that trigger the latency status report time out, are not running, or are not configured. When a delay status report is triggered at time T0, the LCG1 of the delay status report has its corresponding Timer1, the LCG2 of the delay status report has its corresponding Timer2, and the LCG3 of the delay status report has its corresponding Timer3. In this case, if Timer1 and Timer2 time out, no scheduling request will be triggered; if Timer1, Timer2, and Timer3 all time out, a scheduling request will be triggered. Therefore, the timeout of the first timer corresponding to all LCH / LCGs that trigger delay status reports can be referred to as the timeout of the first timer corresponding to all LCH / LCGs that most recently triggered delay status reports. One or more first granularities can include all first granularities.

[0139] The first to the third implementations mentioned above can be independent or combined solutions.

[0140] Resource unavailability typically includes situations where resources exist but the logical channel priority is not met. To expedite the transmission of delay status reports, the logical channel priority of the MAC CE carrying the delay status report can be increased or defined. The delay status report is carried on the MAC CE, and thus, the delay status report itself can be referred to as the MAC CE.

[0141] Since the latency status report transmits latency status information, and the user experience of XR is crucial, if a data packet is dropped due to latency issues, leading to the dropping of the entire PDU set, this would severely impact the UE's user experience, especially given the introduced PDU set discarding mechanism. Therefore, in one implementation, the logical channel of the MAC CE used to carry the latency status report should have a higher priority than the sidelink-buffer status report (SL-BSR) but a lower priority than the timing advance report (TAR).

[0142] TAR (Time Advance) is used to help the network better configure timing advance (TA). If the UE fails to report TAR in a timely manner, it may lead to uplink synchronization loss. Defining the logical channel carrying the MAC CE (Machine Edge Component) to carry this delay status report as having a lower priority than TAR ensures that the network can configure TA.

[0143] Based on the existing logical channel priority ranking, TAR has a lower priority than Listen Before Talk (LBT). Therefore, the priority of the logical channel that carries the delay status report for the MAC CE will not affect the priority of LBT.

[0144] According to an embodiment of this application, a communication method is provided in which the duration of a first timer is reasonably set so that when the first timer expires, is not running, or is not configured, and there are no resources available for the delay status report, a scheduling request can be reasonably triggered, thereby sending the delay status report in a timely manner.

[0145] The above embodiments describe how to reasonably set the duration of a first timer to trigger a scheduling request when the first timer expires, is not running, or is not configured, and there are no resources available for latency status reporting, thereby avoiding frequent triggering of scheduling requests. The following embodiments will describe how, after a scheduling request is triggered, a third timer can be started, and the duration of the third timer can be delayed before triggering the scheduling request again, to further avoid frequent triggering of scheduling requests. These two embodiments can be implemented independently or in combination.

[0146] like Figure 7 The diagram shown illustrates another communication method provided in this application. Exemplarily, the method may include the following steps: S701. When a scheduling request is triggered, a third timer is started. This third timer is used to indicate the duration of the inaccessibility period for triggering the scheduling request.

[0147] In this embodiment, a third timer is configured. This third timer is used to delay the scheduling request for a certain duration after it is triggered, so as to avoid triggering the scheduling request frequently.

[0148] Furthermore, when configuring the third timer, the duration or number of times it can be used can also be configured. One implementation of this duration is a fifth timer, which specifies the duration of the third timer's use, indicating how long the configured third timer is valid. For example, if the first configuration information is received at the first moment, and this first configuration information is used to configure the third timer, and the fifth timer is started at the first moment with a duration of 100 subframes, then the third timer can be started when a scheduling request is triggered between the first moment and the first moment + 100 subframes; after the first moment + 100 subframes, the third timer cannot be started when a scheduling request is triggered. Another implementation is that the duration of the third timer is a validity period. For example, if the first configuration information is received at the first moment with a validity period of 100 subframes, then the third timer expires after the 100th subframe after receiving the first configuration information, or it can be specified that the third timer expires 100 subframes after the first moment (which is not the moment the first configuration information is received). Another implementation is that the third timer is disabled after being activated M times, where M is a positive integer greater than or equal to 1.

[0149] One scenario for triggering a scheduling request is when a latency status report is triggered, but no resources are available for that report. In this case, a scheduling request is triggered to request resources for sending the latency status report. Once the scheduling request is triggered, a third timer is started.

[0150] In one scenario, when the first message needs to be sent or is triggered, but there are no resources available for sending the first message, and if the third timer is not configured, or the third timer is not running, not configured, or has timed out, a scheduling request is triggered to request resources for sending the first message. Upon triggering the scheduling request, the third timer is started. The first message can be a latency status report.

[0151] In one scenario, when the first message needs to be sent or is triggered, but there are no resources available for it, if the first granularity corresponding to the first message (the first granularity that triggered the first message) is not configured with a third timer, or if the first granularity corresponding to the first message (the first granularity that triggered the first message) is configured with a third timer or has an indication that the third timer is not running, not configured, or has timed out, a scheduling request is triggered to request resources to send the first message. When the scheduling request is triggered, the third timer is started. The first message can be a latency status report.

[0152] It is understandable that the scheduling request could also be triggered in other scenarios.

[0153] After configuring the third timer, the third timer can be started when a scheduling request is triggered. That is, after a scheduling request is triggered, the scheduling request will not be triggered again immediately, but the duration of the third timer will be extended before the scheduling request is triggered, in order to avoid frequent triggering of scheduling requests.

[0154] When a scheduling request is triggered, the third timer is started, which can be implemented in several ways: In the first implementation, the third timer is started when a third timer is configured or when an indication message for applying the third timer is sent. For example, the network device can send configuration information to the UE to configure the third timer. Further, after configuring the third timer, the network device can also send indication information to the UE to instruct the application of the third timer. Upon receiving the configuration information or indication information and when a scheduling request is triggered, the UE starts the third timer. In other words, if the third timer is not configured or its application is not indicated, the third timer will not be started even if a scheduling request is triggered.

[0155] In the second implementation, if the first granularity is configured with a corresponding third timer or if the application has an indication of the corresponding third timer, then the third timer is started. For example, the first granularity can be LCH / LCG / DRB / QoS stream / PDUset / data burst, which can be interpreted as a channel, a data stream, or a dataset for data transmission. For example, in this case, each LCH / LCG of the triggered scheduling request will correspond to a third timer.

[0156] In the third implementation, the third timer is started when one or more first granularities are configured with a corresponding third timer or when an indication of the corresponding third timer is applied. For example, the first granularity is LCH / LCG / DRB / QoS stream / PDUset / data burst. For example, in this case, each LCH / LCG of the triggered scheduling request corresponds to a third timer. In one scenario, if all LCH / LCGs in the scheduling request are configured with a corresponding third timer or when an indication of the corresponding third timer is applied, the third timer is started; in another scenario, if one or more LCH / LCGs in the scheduling request are configured with a corresponding third timer or when an indication of the corresponding third timer is applied, the third timer is started.

[0157] The first to the third implementations mentioned above can be independent or combined solutions.

[0158] In this embodiment, the second timer (e.g., the logicalChannelSR-DelayTimer mentioned above) is not directly reused. Since the scheduling request in this application is triggered more frequently than the BSR (it can be triggered as long as the remaining delay of the data packet is below a threshold), scheduling requests need to be triggered more frequently to request resources when there are no resources available for sending them. Therefore, in this embodiment, one or more duration values ​​of the third timer are less than the minimum value of one or more duration values ​​of the second timer.

[0159] The duration of this third timer can be implemented in the following ways: In the first implementation, the duration of the third timer can be in any of the following units: symbol, time slot, subframe, or millisecond. Specifically, this embodiment allows the third timer's duration to be set to either a symbol or a time slot, enabling more timely and precise triggering of scheduling requests, and further, more timely sending of scheduling requests.

[0160] In the second implementation, the duration of the third timer is 0ms, meaning that the scheduling request is triggered directly without any delay after it is triggered, thus enabling the scheduling request to be triggered more promptly and accurately, and further enabling the scheduling request to be sent more promptly.

[0161] In the third implementation, the duration of the third timer is associated with the service requirements. For example, the duration of the third timer can be set according to the latency requirements of the service. For instance, if the latency requirement for XR is 0-30ms, then the value of the third timer can be 0-30ms.

[0162] In the fourth implementation, the duration of the third timer can be a range of values. For example, the duration of the third timer is less than or equal to the second threshold.

[0163] Furthermore, the aforementioned third timer differs from the scheduling request-prohibit timer (sr-ProhibitTimer). The third timer can be used for latency-sensitive services. This timer is used to prevent the frequent triggering of scheduling requests and to control the triggering frequency of scheduling requests. The sr-ProhibitTimer is used to control the sending frequency of scheduling requests, but if scheduling requests are constantly being triggered, there will always be scheduling requests being processed (pending). The third timer prevents scheduling requests from being triggered, meaning that if a scheduling request is sent, there will be no pending scheduling requests waiting to be sent within the runtime of the third timer.

[0164] In one implementation, the third timer is a timer used to disable the scheduling request triggering of the delay status report, which controls the frequency at which the delay status report triggers the scheduling request. In one implementation, the third timer is a newly defined scheduling request that triggers a timer disable mechanism.

[0165] In one implementation, the configuration granularity of the third timer is the same as that of the first timer.

[0166] According to a communication method provided in an embodiment of this application, when a scheduling request is triggered, a third timer is started, and the scheduling request can be triggered again after a delay of the duration of the third timer, thus avoiding frequent triggering of scheduling requests.

[0167] The above embodiments describe how the UE can avoid frequently triggering scheduling requests by using a timer. The following embodiments will describe how the network side can also indicate whether a scheduling request can be triggered when a latency status report is triggered.

[0168] like Figure 8 The diagram shown illustrates a flowchart of another communication method provided in this application. Exemplarily, the method may include the following steps: S801. Receive first indication information. Wherein, the first indication information is used to indicate that when the delay status report is triggered, a scheduling request is triggered; or the first indication information is used to indicate whether the delay status report can trigger a scheduling request.

[0169] Typically, a scheduling request is triggered when a latency status report is triggered and there are no resources available for the report. In this embodiment, to avoid frequent triggering of scheduling requests when a latency status report is triggered, the network device can control the duration for which a scheduling request is triggered directly when a latency status report is triggered.

[0170] Therefore, network devices can be configured with first indication information to trigger a scheduling request when a latency status report is triggered. The data format of the first indication information can be an enumeration type, where the enumeration type is 0 or 1. When it is 0, a scheduling request is triggered by the latency status report; when it is 1, a scheduling request is not triggered by the latency status report, and vice versa. Alternatively, the enumeration type can be enabled; when the first indication information is configured as enabled, a scheduling request can be triggered by the latency status report.

[0171] In the first implementation, the network device can configure first indication information. For example, the first indication information can be 1 bit. When the value of the 1 bit is the first value, it is used to indicate that a scheduling request can be triggered when the latency status report is triggered; when the value of the 1 bit is the second value, it is used to indicate that a scheduling request cannot be triggered when the latency status report is triggered.

[0172] In the second implementation, the network device can configure first indication information. When the UE receives this first indication information, it means that a scheduling request can be triggered when the latency status report is triggered. Conversely, if the network device does not configure or release the first indication information, a scheduling request cannot be triggered when the latency status report is triggered. For example, if the first indication information is configured when the latency status report is triggered for the first time, but is not configured when it is triggered for the second time, it means that the previously configured first indication information has been released. Alternatively, when the latency status report is triggered for the second time, there may be an explicit instruction to indicate the release of the previously configured first indication information, i.e., the first indication information is in the format of setuprelease, and is released via release.

[0173] S802. When there are no resources available for delay status reporting, a scheduling request is triggered based on the first indication information.

[0174] When there are no resources available for latency status reporting, and the aforementioned first indication information has been received, or the previously configured first indication information has not been released, or the first indication information indicates that the latency status report triggers a scheduling request, a scheduling request can be triggered based on the first indication information.

[0175] According to an embodiment of this application, a communication method is provided in which a scheduling request is triggered based on a first indication information when there are no resources available for delay status reporting, thereby avoiding the frequent triggering of scheduling requests.

[0176] like Figure 9 The diagram shown illustrates a flowchart of another communication method provided in this application. Exemplarily, the method may include the following steps: S901. The network device sends first configuration information to the UE. The first configuration information includes one or more of the following: the duration of a first timer, the duration of a third timer, first indication information, second indication information for applying the first timer, third indication information for applying the third timer, the duration or number of times the first timer is used, and the duration or number of times the third timer is used.

[0177] In the first implementation, the network device configures the duration of the first timer using first configuration information. This first timer is used to extend the duration after triggering a latency status report before triggering a scheduling request, or it can be used to indicate the latency for triggering a scheduling request. The network device can configure the duration of the first timer for the entire latency status report, or it can configure the duration of the first timer at the aforementioned first granularity. For information on the possible values ​​for the duration of the first timer, please refer to [reference needed]. Figure 5 The illustrated embodiment is described below. A first timer is configured and started. In other words, if the first timer is not configured, it will not be started even if a delay status report is triggered.

[0178] In the second implementation, the network device includes second indication information in the first configuration information. This second indication information is used to instruct the application of a first timer. This second indication information can instruct the application of the first timer for the entire latency status report, or it can instruct the application of a first timer at a first granularity. Instructing the application of the first timer starts the first timer. In other words, if there is no instruction to apply the first timer, the first timer will not be started even if a latency status report is triggered.

[0179] In the third implementation, the network device includes first indication information in the first configuration information. This first indication information is used to indicate that a scheduling request should be triggered when a latency status report is triggered. If the network device does not send the first indication information or the previously configured first indication information is released, a scheduling request cannot be triggered when a latency status report is triggered.

[0180] In the fourth implementation, the network device configures the duration of the third timer using the first configuration information. This third timer indicates the inhibition duration triggered by the scheduling request. The network device can configure the duration of the third timer for the entire latency status report, or it can configure the duration of the third timer at the first granularity described above. For information on the possible values ​​for the third timer duration, please refer to [reference needed]. Figure 7 The illustrated embodiment is described below. A third timer is configured and can be started. In other words, if a third timer is not configured, it will not be started even if a delay status report is triggered.

[0181] In the fifth implementation, the network device includes third indication information in the first configuration information. This third indication information is used to indicate the application of a third timer. This third indication information can indicate the application of a third timer for the entire scheduling request, or it can indicate the application of a third timer at a first-granularity level. Indicating the application of a third timer allows the third timer to be started. In other words, if no third timer is indicated, the third timer will not be started even if the scheduling request is triggered.

[0182] In the sixth implementation, the network device configures the duration or number of times the first timer is used through the first configuration information. The duration of the first timer is specified by the fourth timer, or the duration of the first timer is a valid duration, or the first timer expires after being started N times, where N is a positive integer greater than or equal to 1.

[0183] In the seventh implementation, the network device configures the duration or number of times the third timer delay is executed through the first configuration information. The duration of the third timer is specified by the fifth timer, or the duration of the third timer is a valid duration, or the third timer expires after being started M times, where M is a positive integer greater than or equal to 1.

[0184] The first to seventh implementations mentioned above can be independent or combined solutions.

[0185] Accordingly, the UE receives the first configuration information.

[0186] In the first implementation described above, the UE's first configuration information configures the duration of the first timer. After receiving this first configuration information, the UE executes step S502 in the above embodiment, that is, when the first timer times out or does not run, and there are no resources available for the latency status report, a scheduling request is triggered. Furthermore, step S501 can also be executed, that is, when the latency status report is triggered, the first timer is started or restarted.

[0187] In the second implementation described above, the first configuration information includes second indication information for applying the first timer. After receiving the first configuration information, the UE executes step S502 in the above embodiment. When the first timer times out and there are no resources available for the latency status report, a scheduling request is triggered. Furthermore, step S501 can also be executed, i.e., when the latency status report is triggered, the first timer is started or restarted.

[0188] In the third implementation described above, the first configuration information includes first indication information. After receiving the first configuration information, the UE executes steps S801 and S802 in the above embodiments. When there are no resources available for delay status reporting, and the first indication information has been received or the previously configured first indication information has not been released, a scheduling request can be triggered based on the first indication information.

[0189] In the fourth implementation described above, the first configuration information includes the duration of the third timer. After the UE receives the first configuration information, it executes step S701 in the above embodiment. If the third timer times out or does not run, a scheduling request can be triggered.

[0190] In the fifth implementation described above, the first configuration information includes the third indication information of the third timer. After receiving the first configuration information, the UE executes step S701 in the above embodiment. If the third timer times out or does not run, a scheduling request can be triggered.

[0191] In the sixth implementation described above, the first configuration information includes the duration or number of times the first timer is used. After receiving the first configuration information, the UE executes step S502 in the above embodiment, that is, if the first timer times out or does not run within the duration or number of times the first timer is used, and there are no resources available for the latency status report, a scheduling request is triggered. Furthermore, step S501 can also be executed, that is, if the latency status report is triggered within the duration or number of times the first timer is used, the first timer is started or restarted.

[0192] In the seventh implementation described above, the first configuration information includes the duration or number of times the third timer is used. After the UE receives the first configuration information, it executes step S701 in the above embodiment. If the third timer times out or does not run within the duration or number of times the third timer is used, a scheduling request can be triggered.

[0193] According to a communication method provided in an embodiment of this application, by configuring one or more of the following on the network side: the duration of a first timer, the duration of a third timer, first indication information, second indication information for applying the first timer, third indication information for applying the third timer, the duration or number of times the first timer is used, and the duration or number of times the third timer is used, scheduling requests can be reasonably triggered to avoid frequent triggering of scheduling requests.

[0194] like Figure 10 The diagram shown illustrates a flowchart of another communication method provided in this application. Exemplarily, the method may include the following steps: S1001. Trigger delay status report.

[0195] For details on how to implement this step, please refer to [link / reference]. Figure 5 Step S501 of the illustrated embodiment will not be described again here.

[0196] S1002. Trigger the random access procedure to send a delay status report.

[0197] In one implementation, S1002. When there are no resources available for delay status reporting, a random access procedure is triggered to send a delay status report.

[0198] When network devices do not have resources configured for latency status reporting, for example, when there are many UEs within the network device's range and resources are scarce, there are no resources available for latency status reporting.

[0199] However, network devices typically have resources configured for UE-initiated random access. Therefore, in this embodiment, when there are no resources to send a latency status report, a random access procedure can be triggered to send the latency status report. One scenario is that when the UE triggers the latency status report, it is camped in cell 1 of the network device. However, if the UE finds that there are no resources for the latency status report and detects that the channel quality of neighboring cell 2 of cell 1 is better, then cell 1 may initiate a cell handover, switching the UE to cell 2. In this case, the UE needs to initiate a random access procedure to access cell 2. Another scenario is that when the UE triggers the latency status report, there are no resources available, so a random access procedure needs to be triggered to obtain the resources to send the latency status report.

[0200] In one implementation, the random access procedure can be a two-step random access (2-step RACH). The two-step random access includes the following process: the UE sends a random access message A (MsgA) to the network device, and the network device sends a random access message B (MsgB) to the UE. For example, the aforementioned latency status report can be sent via message A. It is understood that sending the latency status report via message A means that the latency status report is carried simultaneously with sending message A for random access; sending the latency status report does not affect the random access procedure. The network device can configure two-step random access resources for latency status reporting, which can reduce the latency of sending four-step random access and requesting resources through scheduling requests, avoiding timeouts that prevent scheduling. When there are no resources to send the latency status report, two-step random access can be directly triggered to send the latency status report (which can be a contention-free random access (CFRA) or a contention-based random access procedure), without comparing the threshold for using two-step random access resources.

[0201] In another implementation, the random access procedure can be a four-step random access (4-step RACH). The four-step random access includes the following steps: the UE sends a random access message 1 (Msg1 or preamble) to the network device; the network device sends a random access message 2 (Msg2 or random access response, RAR) to the UE; the UE sends a random access message 3 to the network device; and the network device sends a random access message 4 to the UE. For example, the aforementioned latency status report can be sent via random access message 3. It is understood that sending the latency status report via message 3 means that the latency status report is carried simultaneously with the random access process using message 3; sending the latency status report does not affect the random access procedure.

[0202] For more details on two-step random access and four-step random access, please refer to existing technologies, which will not be elaborated here.

[0203] The network side can be configured with a dedicated random access resource for latency status reporting. When a latency status report is triggered, a random access procedure is initiated, and the latency status report is sent through the random access resource.

[0204] According to a communication method provided in an embodiment of this application, after triggering a delay status report, when there are no resources to send a delay status report, a random access procedure is triggered to send a delay status report, which can send the delay status report in a timely manner and avoid timeouts that may prevent scheduling.

[0205] The foregoing mainly describes the communication methods provided in the embodiments of this application. Correspondingly, the embodiments of this application also provide a communication device for implementing the various methods described above. This communication device can be a UE in the above method embodiments, or a component usable by a UE; or, the communication device can be a network device in the above method embodiments, or a component usable by a network device. It is understood that, in order to achieve the above functions, the communication device includes hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily recognize that, based on the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein, this application can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed by hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0206] This application embodiment can divide the communication device into functional modules according to the above method embodiment. For example, each function can be divided into its own functional modules, or two or more functions can be integrated into one processing unit. The integrated modules can be implemented in hardware or as software functional modules. It should be noted that the module division in this application embodiment is illustrative and only represents one logical functional division. In actual implementation, there may be other division methods.

[0207] Based on the same concept as the above communication method, this application also provides the following communication device: like Figure 11 The diagram shown is a structural schematic of a communication device provided in an embodiment of this application. The communication device 1100 includes a transceiver unit 1101 and a processing unit 1102; wherein: When the communication device is used to implement the functions of the UE in the above method embodiment, the processing unit 1102 is used to perform, as follows: Figure 5 The operations of S501 and S502 in the illustrated embodiment; or, the processing unit 1102 is used to perform such... Figure 7 The operation of S701 in the illustrated embodiment; or, the processing unit 1102 is used to perform such as Figure 8 The operations of S801 and S802 in the illustrated embodiment; or, the transceiver unit 1101 is used to perform... Figure 9 In the illustrated embodiment, the operation of the UE in S901; or, the processing unit 1102 is used to perform, as in... Figure 10 The operation of S1001 and S1002 in the illustrated embodiment.

[0208] When the communication device is used to implement the functions of the network device in the above method embodiment, the transceiver unit 1101 is used to perform the following... Figure 9 The operation of the network device in S901 in the illustrated embodiment.

[0209] For details on the specific implementation of the above-mentioned transceiver unit 1101 and processing unit 1102, please refer to the description in the above method embodiments.

[0210] like Figure 12 The diagram shows a structural schematic of another communication device provided in an embodiment of this application. The communication device 1200 includes one or more processors 1201 (a processor is illustrated in the figure). Optionally, the communication device 1200 may also include a memory 1203 (shown as a dashed line in the figure). The memory 1203 is used to store instructions executed by the processor 1201, or to store input data required by the processor 1201 to execute instructions, or to store data generated after the processor 1201 executes instructions. Optionally, the communication device 1200 may also include an interface circuit 1202 (shown as a dashed line in the figure), with the processor 1201 and the interface circuit 1202 coupled to each other. It is understood that the interface circuit 1202 can be a transceiver or an input / output interface. The processor 1201 is used to implement the above-described... Figure 11 The processing unit 1102 in the illustrated embodiment has the function of [function name]; and the interface circuit 1202 is used to implement the above. Figure 11 The transceiver unit 1101 in the illustrated embodiment has the following functions.

[0211] When the aforementioned communication device is a chip applied to the UE, the chip implements the functions of the UE in the above method embodiments. The chip receives information from other modules (such as radio frequency modules or antennas) in the UE, which is sent to the UE by the network device; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the UE, which is sent to the network device by the UE.

[0212] When the aforementioned communication device is a chip applied to a network device, the chip implements the functions of the network device in the above method embodiments. The chip receives information from other modules (such as radio frequency modules or antennas) in the network device, which is sent by the UE to the network device; or, the chip sends information to other modules (such as radio frequency modules or antennas) in the network device, which is sent by the network device to the UE.

[0213] Furthermore, it should be noted that the aforementioned transceiver unit and / or processing unit can be implemented through virtual modules. For example, the processing unit can be implemented through software functional units or virtual devices, and the transceiver unit can be implemented through software functions or virtual devices. Alternatively, the processing unit or transceiver unit can also be implemented through physical devices. For example, if the device is implemented using a chip / chip circuit, the transceiver unit can be an input / output circuit and / or a communication interface, performing input operations (corresponding to the aforementioned receiving operation) and output operations (corresponding to the aforementioned sending operation); the processing unit is an integrated processor, microprocessor, or integrated circuit.

[0214] The module division in this application is illustrative and represents only one logical functional division. In actual implementation, other division methods are possible. Furthermore, the functional modules in the various examples of this application can be integrated into a single processor, exist as separate physical entities, or be integrated into a single module. The integrated modules described above can be implemented in hardware or as software functional modules.

[0215] It is understood that the processor in the embodiments of this application can be a central processing unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. A general-purpose processor can be a microprocessor or any conventional processor.

[0216] This application also provides a computer-readable storage medium storing a computer program or instructions that, when executed, implement the methods described in the above embodiments.

[0217] This application also provides a computer program product containing instructions that, when executed on a computer, cause the computer to perform the methods described in the above embodiments.

[0218] This application also provides a communication system, including the communication device described above.

[0219] This application also provides a circuit coupled to a memory, which is used to perform the methods shown in the above embodiments. This circuit may include a chip circuit.

[0220] When the aforementioned communication device is a module applied to a base station, the base station module implements the functions of the base station in the above method embodiments. The base station module receives information from other modules (such as radio frequency modules or antennas) in the base station, information sent to the base station by the first node; or, the base station module sends information to other modules (such as radio frequency modules or antennas) in the base station, information sent to the first node by the base station. Here, the base station module can be the baseband chip of the base station, or a CU, DU, or other module, or a device under an open radio access network (O-RAN) architecture, such as an open CU, open DU, etc.

[0221] It should be noted that one or more of the above units can be implemented by software, hardware, or a combination of both. When any of the above units is implemented by software, the software exists as computer program instructions and is stored in memory. The processor can be used to execute the program instructions and implement the above method flow.

[0222] In this application, the processor can be a general-purpose processor, a digital signal processor, an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or all or part of the circuitry in the aforementioned devices used to implement the processing functions, capable of implementing or executing the methods, steps, and logic block diagrams disclosed in this application. The general-purpose processor can be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in this application can be directly embodied in the execution of the hardware processor, or can be executed by a combination of hardware and software modules within the processor.

[0223] When the above units or components are implemented in hardware, the hardware can be any one or any combination of a CPU, microprocessor, digital signal processing (DSP) chip, microcontroller unit (MCU), artificial intelligence processor, ASIC, SoC, FPGA, PLD, application-specific digital circuit, hardware accelerator, or non-integrated discrete device, which can run the necessary software or perform the above method flow independently of software.

[0224] Optionally, embodiments of this application also provide a chip system, including: one or more processors and an interface, wherein the one or more processors are coupled to a memory through the interface, and when the one or more processors execute a computer program or instructions in the memory, the chip system performs the method in any of the above method embodiments. Optionally, the chip system may be composed of chips, or may include chips and other discrete devices; embodiments of this application do not specifically limit this.

[0225] The memory in this application can also be a circuit or any other device capable of performing storage functions, used to store program instructions and / or data. Memory is any other medium capable of carrying or storing desired program code in the form of instructions or data structures, and accessible by a computer, but is not limited thereto. For example, memory can be non-volatile memory, such as digital versatile disc (DVD), hard disk drive (HDD), or solid-state drive (SSD), or it can be volatile memory, such as random-access memory (RAM).

[0226] It should be understood that in the description of this application, unless otherwise stated, " / " indicates that the objects before and after it are in an "or" relationship. For example, A / B can represent A or B; where A and B can be singular or plural. Furthermore, in the description of this application, unless otherwise stated, "multiple" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one of a, b, or c can represent: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple. Additionally, to facilitate a clear description of the technical solutions of the embodiments of this application, the terms "first," "second," etc., are used in the embodiments of this application to distinguish identical or similar items with substantially the same function and effect. Those skilled in the art will understand that the terms "first," "second," etc., do not limit the quantity or execution order, and the terms "first," "second," etc., do not necessarily imply difference. In this application, the terms "exemplary" or "for example" are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" or "for example" in this application should not be construed as being better or more advantageous than other embodiments or designs. Specifically, the use of terms such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner to facilitate understanding.

[0227] In the above embodiments, implementation can be achieved, in whole or in part, through software, hardware, firmware, or any combination thereof. When implemented using software programs, implementation can be, in whole or in part, in the form of a computer program product. This computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. 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 transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another via wired (e.g., coaxial cable, fiber optic, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) means.

[0228] Although this application has been described herein in conjunction with various embodiments, those skilled in the art, by reviewing the accompanying drawings, disclosure, and appended claims, will understand and implement other variations of the disclosed embodiments in carrying out the claimed application. In the claims, the word "comprising" does not exclude other components or steps, and "a" or "an" does not exclude multiple components. A single processor or other unit can implement several functions listed in the claims. While different dependent claims may recite certain measures, this does not mean that these measures cannot be combined to produce good results.

[0229] It is understood that the various numerical designations used in the embodiments of this application are merely for descriptive convenience and are not intended to limit the scope of the embodiments of this application. The order of the process numbers described above does not imply the order of execution; the execution order of each process should be determined by its function and internal logic.

[0230] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0231] The components in the device described in this application embodiment can be combined, divided, or removed according to actual needs. Those skilled in the art can combine or integrate the different embodiments and features described in this specification.

[0232] In this application, examples may reference each other without logical contradiction. For example, methods and / or terms between method embodiments may reference each other, functions and / or terms between device embodiments may reference each other, and functions and / or terms between device examples and method examples may reference each other.

Claims

1. A communication method, characterized in that, The method includes: A latency status report is triggered if the remaining latency of the first data is less than or equal to a second threshold; the latency status report includes remaining latency information and data volume information. When there are resources available for sending the delay status report according to the logical channel priority, the delay status report is sent. Among them, the logical channel of the medium access control-control element used to carry the delay status report has a higher priority than the side link-buffer status report, but a lower priority than the timed advance report.

2. The method as described in claim 1, characterized in that: After a latency status report is triggered, if there are no resources available to send the latency status report and there are currently no scheduling requests being processed, then a scheduling request is triggered; or, If, after the latency status report is triggered, there are no resources available to send the latency status report, and the first granularity corresponding to the latency status report does not have a scheduling request triggered by a latency status report that is currently being processed, then a scheduling request is triggered.

3. The method as described in claim 2, characterized in that, The third timer is used to determine the scheduling request that is not being processed, wherein the third timer is used to indicate the prohibition duration triggered by the scheduling request.

4. The method as described in claim 2, characterized in that, The first granularity includes at least one of the following: logical channel, logical channel group, data radio bearer, quality of service stream, protocol data unit set, and data burst.

5. The method as described in claim 1, characterized in that, The method further includes: Receive first indication information, which is used to indicate that when the delay status report is triggered, a scheduling request is triggered; or the first indication information is used to indicate whether the delay status report can trigger a scheduling request. If there are no resources available to send the latency status report, the scheduling request is triggered based on the first indication information.

6. The method as described in claim 5, characterized in that, The method further includes: Receive first configuration information, which is used to configure the first indication information.

7. The method according to any one of claims 2 to 6, characterized in that, The statement that there are no resources available to send the latency status report includes: There are no resources available for sending the latency status report; or, There are resources available for sending the latency status report, but the resources cannot accommodate the latency status report.

8. The method as described in claim 1, characterized in that, Sending the delay status report includes: The random access procedure is triggered to send the latency status report.

9. The method as described in claim 8, characterized in that, The triggering of the random access procedure to send the latency status report includes: The delay status report is sent via random access message A or random access message 3.

10. A communication device, characterized in that, The invention includes a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that the processor, when executing the computer program, implements the method as described in any one of claims 1-9.

11. A chip, characterized in that, The chip is used to perform the method as described in any one of claims 1-9.

12. A chip module, characterized in that, It includes an interface component and a chip, the chip being used to perform the method as described in any one of claims 1-9.

13. A computer-readable storage medium, characterized in that, The storage medium stores a computer program or instructions, which, when executed by a communication device, implement the method as described in any one of claims 1-9.

Images