Method for processing DSR and terminal device

Abstract

Provided are a method for processing DSR and a terminal device. The method comprises: if a target condition is satisfied, a terminal device cancels or does not cancel first DSR, wherein the target condition comprises at least one of the following: a first condition, indicating that the terminal device triggers the first DSR; a second condition, indicating that, in a first LCH / LCG, there is no data having a delay budget less than a first threshold, wherein the first LCH / LCG is an LCH / LCG which triggers the first DSR or an LCH / LCG that satisfies a first DSR condition other than the LCH / LCG which triggers the first DSR, and the first threshold is used for triggering DSR; a third condition, indicating that the terminal device caches data of the first LCH / LCG or data of the LCH / LCG other than the first LCH / LCG; a fourth condition, indicating that the time interval between the data of the first LCH / LCG or the LCH / LCG other than the first LCH / LCG and a target moment is less than or equal to a second threshold and greater than the first threshold, wherein the target moment is a cut-off moment of a delay budget corresponding to target data; and a fifth condition, indicating that the terminal device has triggered a first SR.

Description

Method and terminal device for processing DSR Technical Field

[0001] The present application relates to the field of wireless communication technology, and in particular to a method and terminal device for processing DSR. Background Art

[0002] In certain services, such as extended reality (XR), terminal devices can trigger a delay status reporting (DSR) process to report the data's delay status to the network device to prevent uplink data from being discarded due to latency timeouts. However, how terminal devices handle triggered DSRs remains a key issue.

[0003] Summary of the Invention

[0004] The present application provides a method and terminal device for processing DSR, which are described below from the following aspects.

[0005] In a first aspect, a method for processing a DSR is provided, comprising: if a target condition is met, a terminal device cancels or does not cancel a first DSR; wherein the target condition includes one or more of the following: a first condition, indicating that the terminal device triggers the first DSR; a second condition, indicating that a first logical channel (logical channel, LCH) / logical channel group (logical channel The first LCH / LCG is the LCH / LCG that triggers the first DSR, or the first LCH / LCG is the LCH / LCG that meets the first DSR condition other than the LCH / LCG that triggers the first DSR, and the first threshold is used to trigger the DSR; the third condition indicates that the terminal device has cached data of the first LCH / LCG, or the terminal device has cached data of LCH / LCG other than the first LCH / LCG; the fourth condition indicates that the time interval between the data of the first LCH / LCG or the LCH / LCG other than the first LCH / LCG and the target time is less than or equal to the second threshold and greater than the first threshold, and the target time is the deadline of the delay budget corresponding to the target data; the fifth condition indicates that the terminal device has triggered a first scheduling request (scheduling request, SR).

[0006] According to a second aspect, a terminal device is provided, comprising: a first module, configured to cancel or not cancel a first DSR when a target condition is met; wherein the target condition comprises one or more of the following: a first condition, indicating that the terminal device has triggered the first DSR; a second condition, indicating that there is no data with a delay budget less than a first threshold in the first logical channel LCH / logical channel group LCG, and the first LCH / LCG is the LCH / LCG that triggers the first DSR, or the first LCH / LCG is the LCH / LCG that triggers the first DSR and satisfies the first DSR condition, and the first threshold is used to trigger the DSR; a third condition, indicating that the terminal device has data of the first LCH / LCG cached, or the terminal device has data of LCH / LCGs other than the first LCH / LCG cached; a fourth condition, indicating that the time interval between the data of the first LCH / LCG or the LCH / LCG other than the first LCH / LCG and the target moment is less than or equal to the second threshold and greater than the first threshold, and the target moment is the end time of the delay budget corresponding to the target data; a fifth condition, indicating that the terminal device has triggered the first SR.

[0007] In a third aspect, a terminal device is provided, comprising a transceiver, a memory, and a processor, wherein the memory is used to store programs, and the processor is used to call the programs in the memory and control the transceiver to receive or send signals so that the terminal device executes a method as described in any one of the first aspects.

[0008] In a fourth aspect, a device is provided, comprising a processor, configured to call a program from a memory so that the device executes the method as described in any one of the first aspects.

[0009] In a fifth aspect, a chip is provided, comprising a processor for calling a program from a memory so that a device equipped with the chip executes the method as described in any one of the first aspects.

[0010] In a sixth aspect, a computer-readable storage medium is provided, on which a program is stored, wherein the program enables a computer to execute the method as described in any one of the first aspects.

[0011] In a seventh aspect, a computer program product is provided, comprising a program, wherein the program enables a computer to execute the method as described in any one of the first aspects.

[0012] In an eighth aspect, a computer program is provided, which enables a computer to execute the method as described in any one of the first aspects.

[0013] In this application, the terminal device can cancel or not cancel the triggered DSR when different conditions are met, which helps the terminal device determine how to handle the triggered DSR. BRIEF DESCRIPTION OF THE DRAWINGS

[0014] FIG1 is a schematic diagram of a system structure of a method for processing DSR applicable to an embodiment of the present application.

[0015] FIG2 is a schematic flow chart of triggering DSR.

[0016] FIG3 is a schematic flowchart of triggering SR.

[0017] FIG4 is a schematic flowchart of canceling SR.

[0018] FIG5 is a schematic flowchart of a method for processing DSR provided in an embodiment of the present application.

[0019] FIG6 is a schematic diagram of the structure of a terminal device provided in an embodiment of the present application.

[0020] FIG7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0021] The technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, rather than all the embodiments.

[0022] Communication system architecture

[0023] FIG1 is a diagram illustrating an exemplary system architecture of a wireless communication system 100 to which embodiments of the present application may be applied. The wireless communication system 100 may include a network device 110 and a terminal device 120. The network device 110 may be a device that communicates with the terminal device 120. The network device 110 may provide communication coverage for a specific geographic area and may communicate with the terminal device 120 within the coverage area.

[0024] FIG1 exemplarily shows a network device and a terminal device. Optionally, the wireless communication system 100 may include one or more network devices 110 and / or one or more terminal devices 120. For a network device 110, the one or more terminal devices 120 may all be located within the network coverage of the network device 110, or all be located outside the network coverage of the network device 110, or some may be located within the coverage of the network device 110 and others outside the network coverage of the network device 110. This is not limited in the embodiments of the present application.

[0025] Optionally, the wireless communication system 100 may further include other network entities such as a network controller and a mobility management entity, which is not limited in the embodiment of the present application.

[0026] It should be understood that the technical solutions of the embodiments of the present application can be applied to various communication systems, such as: fifth generation (5G) system or new radio (NR) system, long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD) system, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system, satellite communication system, etc.

[0027] The terminal device in the embodiments of the present application may also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station, mobile station (MS), mobile terminal (MT), remote station, remote terminal, mobile device, user terminal, terminal, wireless communication device, user agent or user device. The terminal device in the embodiments of the present application may refer to a device that provides voice and / or data connectivity to a user and can be used to connect people, objects and machines, such as a handheld device with wireless connection function, a vehicle-mounted device, etc. The terminal device in the embodiments of the present application can be a mobile phone, a tablet computer, a laptop computer, a PDA, a mobile internet device (MID), a wearable device, a virtual reality (VR) device, an augmented reality (AR) device, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical surgery, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, etc. Optionally, the UE can be used to act as a base station. For example, the UE can act as a scheduling entity that provides sidelink signals between UEs in vehicle-to-everything (V2X) or device-to-device (D2D). For example, a cellular phone and a car communicate with each other using sidelink signals. The cellular phone and smart home devices communicate without relaying the communication signal through the base station.

[0028] The network device in the embodiments of the present application may be a device for communicating with a terminal device, and may also be referred to as an access network device or a radio access network device. For example, the network device may be a base station. The network device in the embodiments of the present application may refer to a radio access network (RAN) node (or device) that connects a terminal device to a wireless network. A base station can broadly cover various names as follows, or be replaced with the following names, such as: NodeB, evolved NodeB (eNB), next generation NodeB (gNB), relay station, access point, transmission point (TRP), transmission point (TP), master station MeNB, secondary station SeNB, multi-standard radio (MSR) node, home base station, network controller, access node, wireless node, access point (AP), transmission node, transceiver node, baseband unit (BBU), remote radio unit (RRU), active antenna unit (AAU), remote radio head (RRH), central unit (CU), distributed unit (DU), positioning node, etc. A base station can be a macro base station, a micro base station, a relay node, a donor node or the like, or a combination thereof. A base station can also refer to a communication module, modem or chip used to be set in the aforementioned device or apparatus. The base station can also be a mobile switching center and a device that performs base station functions in device-to-device (D2D), V2X, and machine-to-machine (M2M) communications, a network-side device in a 6G network, or a device that performs base station functions in future communication systems. The base station can support networks with the same or different access technologies. The embodiments of this application do not limit the specific technology and specific device form used by the network device.

[0029] Base stations can be fixed or mobile. For example, a helicopter or drone can be configured to act as a mobile base station, and one or more cells can move based on the location of the mobile base station. In other examples, a helicopter or drone can be configured to act as a device that communicates with another base station.

[0030] In some deployments, the network device in the embodiments of the present application may refer to a CU or a DU, or the network device may include a CU and a DU. The gNB may also include an AAU.

[0031] The network equipment and terminal devices can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed in the air on aircraft, balloons, and satellites. The embodiments of this application do not limit the scenarios in which the network equipment and terminal devices are located.

[0032] It should be understood that all or part of the functions of the communication device in this application can also be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (such as a cloud platform).

[0033] DSR Process

[0034] With the development of communication technology, when using cellular wireless networks to transmit certain services (such as XR services), the transmission capacity of the network can be fully utilized, greatly improving the user experience. However, the amount of business data of these services is large, and the delay budget for data transmission is short. In order to transmit the data of these services in a timely manner and prevent the business data from being discarded due to delay timeout, the terminal device can trigger the DSR process to report the delay status of the business data to the network device. It is worth noting that the DSR here can be replaced by any other name. Regardless of what name DSR is called, as long as its technical essence remains unchanged, it does not affect the essence of the embodiments of the present application.

[0035] Typically, before service data is transmitted, the network device can configure a data delay threshold, known as the DSR threshold, for the service data. When the time interval between the uplink data in the terminal device and the deadline for the transmission delay budget is less than this threshold, the terminal device can trigger a DSR. If there are no corresponding uplink resources to send a DSR, the network device can further trigger a scheduling request (SR) process to obtain uplink scheduling. If there are no SR resources, the terminal device can trigger random access.

[0036] The following uses the example of a terminal device transmitting an XR service as an example, and with reference to Figure 2, the triggering of the DSR process is described in detail. As shown in Figure 2, in step S210, the access layer of the terminal device receives 200 bytes of XR data from the application layer of the XR service at time T1. The transmission delay budget for this portion of XR data is T1 to T3, which means that this portion of XR data is valid until time T3. At T3, the data in this portion of XR data that has not been transmitted will be discarded. To ensure that this portion of XR data can be transmitted in a timely manner, the network device is configured with a DSR threshold, which is the time from T2 to T3. At time T2, if the terminal device detects that there is still XR data that has not been transmitted, it triggers DSR. There are two situations in which there is still XR data that has not been transmitted. The first situation is that all 200 bytes of XR data have not been transmitted. In this case, as shown in step S220, the terminal device can report the amount of untransmitted data as 200 bytes through DSR. The second situation is that part of the 200 bytes of XR data has not been transmitted. Furthermore, if there is no physical uplink shared channel (PUSCH) resource for transmitting DSR, the terminal device may trigger an SR procedure. Furthermore, if there is no resource for transmitting SR, the terminal device may trigger a random access procedure to obtain uplink scheduling.

[0037] The following example illustrates the triggering of the SR process with reference to Figure 3. In step S310, when the SR is triggered, the counter corresponding to the SR is set to 0, and the SR is in a pending state. When the SR is in the pending state, the terminal device can transmit the SR on the physical uplink control channel (PUCCH) resource corresponding to the SR and use the SR counter to count the number of SR transmissions. If the number of SR transmissions reaches the maximum threshold, the random access process is triggered. For example, as shown in Figure 3, after the terminal device triggers the SR, it transmits the SR three times in steps S320-S340. At this point, the number of SR transmissions reaches the maximum threshold. As shown in steps S350-S360, the terminal device can cancel the SR and subsequently trigger the random access process. When the SR is canceled, the SR is no longer in the pending state. In addition, a prohibit timer corresponding to the SR can be set in the SR process to prevent the terminal device from frequently transmitting the SR. When the prohibit timer runs, the terminal device does not transmit the SR. When the prohibit timer expires, the terminal device can transmit the SR.

[0038] The cancellation of the DSR process is introduced below. Generally, when the access layer of the terminal device does not include data whose distance between the remaining time and the deadline of the transmission delay budget is less than the DSR threshold, that is, when the access layer of the terminal device does not include data that can trigger DSR, the terminal device can cancel the triggered DSR process. Exemplarily, the scenarios in which the terminal device cancels DSR may include scenario one and scenario two. In scenario one, when the data that can trigger DSR in the access layer of the terminal device has been transmitted to the network device, the terminal device can cancel the triggered DSR process. In scenario two, when the deadline of the transmission delay budget of the data that can trigger DSR arrives, the untransmitted data in this part of the data is discarded, and the terminal device can also cancel the triggered DSR process at this time. However, if the terminal device triggers the DSR process and also triggers the SR process, when the terminal device cancels the DSR process, how to handle the SR process is not yet clear.

[0039] Similarly, the buffer status report (BSR) process triggered by the terminal device when transmitting certain business data also involves the triggering of the SR process. Generally, when transmitting certain business data, the terminal device can trigger the BSR process to report the amount of data to be transmitted to the network device. After triggering the BSR process, the terminal device can also trigger the SR process to obtain uplink scheduling. After the terminal device triggers the BSR process, if there is no longer data that needs to be transmitted in the terminal device, the terminal device can cancel the BSR process. Exemplarily, the scenarios in which the terminal device cancels the BSR process can also include scenario one and scenario two. In scenario one, when all the data that needs to be transmitted in the terminal device has been transmitted to the network device, the terminal device can cancel the BSR process. In scenario two, when the data that has not been transmitted in the data that needs to be transmitted in the terminal device has exceeded the delay budget and has been deleted, the terminal device can also cancel the BSR process.

[0040] If a terminal device triggers a BSR process and then triggers an SR process, it can also cancel the SR process when it cancels the BSR process. This is because the latency budget of the service data that triggered the BSR process is large, typically much larger than the scheduling period. Therefore, scenario 2, in which the BSR process is canceled, is less common, and the impact of canceling the SR process on service transmission is minimal. However, the latency budget of service data that triggered the DSR process is typically smaller, making scenario 2, in which the DSR process is canceled, more likely to occur. If the terminal device cancels the triggered SR process when it also cancels the triggered DSR process, this may affect service data transmission.

[0041] The following, using Figure 4 as an example, describes the cancellation of the SR process in detail, using the example of a terminal device transmitting an XR service. As shown in Figure 4, at time T1, the first batch of XR data arrives at the terminal device's access layer. The final transmission time (i.e., the transmission delay budget) for the first batch of XR data is T4, and the DSR threshold for the first batch of XR data is T2. At time T2, if there is still untransmitted data in the first batch of XR data, the terminal device triggers the DSR process. At this point, there are no PUSCH resources for DSR transmission, but there are resources for SR transmission, so the terminal device can further trigger the SR process. After the SR process is triggered, the SR enters the pending state, and the corresponding SR counter is initially set to 0. At this point, the terminal device can send an SR using the preconfigured SR resources. As shown in Figure 4, the terminal device sends two SRs, and the SR counter increments to 2. At time T3, the second batch of XR data arrives at the terminal device's access layer. The final transmission time (i.e., the transmission delay budget) for the second batch of XR data is T6, and the DSR threshold for the second batch of XR data is T5.

[0042] At time T4, there is still data that has not been transmitted in the first batch of XR data, so the terminal device discards this part of the data. And at this time, the second batch of XR data has not reached the DSR threshold. Therefore, at time T4, the access layer of the terminal device does not include data that can trigger DSR, so the terminal device can cancel the triggered DSR process. If the terminal device also cancels the triggered SR process, SR is no longer in the pending state. At time T5, there is still data that has not been transmitted in the second batch of XR data, so the terminal device can trigger DSR again. And if there are no PUSCH resources for transmitting DSR at this time, but there are resources for transmitting SR, the terminal device can further trigger the SR process. Since the previous SR has been canceled, the re-triggered SR re-enters the pending state, and the counter corresponding to SR is set to 0 again.

[0043] However, if uplink wireless conditions are poor, the network device may not receive the SR sent by the terminal device and will not allocate uplink resources to the terminal device. As XR data continues to arrive, the terminal device's uplink resources may no longer be sufficient for XR data transmission. Therefore, the terminal device may repeatedly trigger and cancel the SR, and the SR counter will continue to reset to zero. This may cause the SR transmission count to fail to reach the maximum, thus failing to trigger random access for uplink scheduling, which may affect service data transmission.

[0044] Based on the above problems, the embodiments of the present application are introduced in detail below.

[0045] As shown in FIG5 , an embodiment of the present application provides a method for processing DSR, which can be executed by any of the terminal devices described above.

[0046] The method shown in FIG5 may include step S510. In step S510, if a target condition is met, the terminal device cancels or does not cancel the first DSR. The target condition includes one or more of the following: a first condition, a second condition, a third condition, a fourth condition, and a fifth condition.

[0047] The first condition may indicate that the terminal device has triggered a first DSR, and the first DSR may indicate a DSR triggered by the terminal device. In other words, the first condition may indicate that the terminal device has triggered a DSR.

[0048] The second condition may indicate that there is no data in the first LCH / LCG with a delay budget less than the first threshold, and the first LCH / LCG may be the LCH / LCG that triggers the first DSR. The first LCH / LCG may also be an LCH / LCG that meets the first DSR condition other than the LCH / LCG that triggers the first DSR. The first DSR condition may refer to sharing the same SR resource with the LCH / LCG that triggers the first DSR, and the cached data has met the condition for triggering DSR, but because the first DSR has been triggered, DSR is not triggered. The first threshold can be used to trigger DSR, that is, the first threshold may be the DSR threshold described above. Therefore, the second condition may indicate that there is temporarily no data that can trigger DSR again in the LCH / LCG that has triggered DSR or the LCH / LCG that meets the DSR triggering condition.

[0049] The third condition may indicate that the terminal device has data of the first LCH / LCG cached, that is, there is data waiting to be transmitted in the first LCH / LCG. Alternatively, the third condition may also indicate that the terminal device has data of LCH / LCGs other than the first LCH / LCG cached (which may be referred to as "other LCH / LCGs"), that is, there is data waiting to be transmitted in LCH / LCGs other than the first LCH / LCG.

[0050] The fourth condition may indicate that the time interval between the data of the first LCH / LCG or an LCH / LCG other than the first LCH / LCG and the target time is less than or equal to the second threshold and greater than the first threshold. The target time may be the end time of the delay budget corresponding to the target data, that is, the target data that has not been transmitted at the target time will not be transmitted again. The target data may refer to the data of the first LCH / LCG or an LCH / LCG other than the first LCH / LCG. In other words, the data of the LCH / LCG that has triggered the DSR or the data of other LCH / LCGs will not trigger the DSR again for the time being, but it is very likely that the DSR will be triggered soon. For example, when the second threshold is greater than the first threshold.

[0051] The fifth condition may indicate that the terminal device has triggered the first SR, and the first SR may indicate a triggered SR.

[0052] It is worth noting that different LCHs / LCGs may use the same first threshold and / or second threshold, or may use their own first threshold and / or second threshold, which is not limited in this application.

[0053] In this application, the terminal device can cancel or not cancel the triggered DSR when different conditions are met, which helps the terminal device determine how to handle the triggered DSR.

[0054] The following details how the terminal device handles DSR when different target conditions are met.

[0055] In some implementations, if the first condition, the second condition, and the third condition are met, the terminal device may not cancel the first DSR. That is, if the terminal device has triggered the DSR, and there is temporarily no data that can trigger the DSR again in the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering conditions, and the terminal device has cached data of the LCH / LCG that triggered the DSR or data of other LCH / LCGs, the terminal device may not cancel the triggered DSR. The terminal device may not make a judgment on whether the SR has been triggered, which helps the terminal device determine the processing method of the DSR through fewer judgment conditions. If the terminal device has triggered the SR, the terminal device may not process it, so that uplink scheduling can continue. If the uplink wireless conditions are good, the network device can successfully receive the SR, thereby allocating uplink resources to the terminal device. If the uplink wireless conditions are not good, the number of SR transmissions can reach the maximum value faster, thereby triggering wireless access. Based on this, it helps to ensure that the data in the cache is transmitted in a timely manner.

[0056] In other implementations, if the first condition, the second condition, the third condition, and the fourth condition are met, the terminal device may not cancel the first DSR. That is, if the terminal device has triggered the DSR, and there is temporarily no data that can trigger the DSR again in the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering conditions, and the terminal device has cached data of the LCH / LCG that triggered the DSR or data of other LCH / LCGs, and these data will not trigger the DSR again temporarily, but it is very likely that the DSR will be triggered soon, then the terminal device may not cancel the triggered DSR. The terminal device may not make a judgment on whether to trigger the SR, which helps the terminal device determine the processing method of the DSR through fewer judgment conditions. If the terminal device has triggered the SR, the terminal device may not process it. Therefore, the terminal device can continue to perform uplink scheduling through the triggered SR based on the transmission status of the data in the cache, which helps to ensure that the data in the cache is transmitted in a timely manner.

[0057] In other implementations, if the first condition, the second condition, the third condition, and the fifth condition are met, the terminal device may not cancel the first DSR. That is, if the terminal device has triggered the DSR, and the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering condition does not temporarily have data that can trigger the DSR again, and the terminal device has cached the data of the LCH / LCG that triggered the DSR or the data of other LCH / LCGs, and the terminal device has triggered the SR, then the terminal device may not cancel the triggered DSR. In this case, the terminal device can determine whether to trigger the SR, and may not cancel the triggered DSR if the SR has been triggered. Accordingly, the terminal device may not cancel the triggered SR, so that the uplink scheduling can continue through the triggered SR, which helps to ensure that the data in the cache is transmitted in a timely manner.

[0058] In other implementations, if the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are met, the terminal device does not cancel the first DSR. That is, if the terminal device has triggered the DSR, and there is temporarily no data that can trigger the DSR again in the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering condition, and the terminal device has cached data of the LCH / LCG that triggered the DSR or data of other LCH / LCGs, and these data will not trigger the DSR again temporarily, but it is very likely that the DSR will be triggered soon, and the terminal device has triggered the SR, then the terminal device may not cancel the triggered DSR. In this case, the terminal device can determine whether to trigger the SR, and may not cancel the triggered DSR if the SR has been triggered. Accordingly, the terminal device may not cancel the triggered SR. Therefore, the terminal device can continue to perform uplink scheduling through the triggered SR based on the transmission status of the data in the cache, which helps to ensure that the data in the cache is transmitted in a timely manner.

[0059] In other implementations, if the first condition, the second condition, the third condition, and the fifth condition are met, the terminal device cancels the first DSR but does not cancel the first SR. That is, if the terminal device has triggered the DSR, and there is temporarily no data that can trigger the DSR again in the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering conditions, and the terminal device has cached the data of the LCH / LCG that triggered the DSR or the data of other LCH / LCGs, and the terminal device has triggered the SR, then the terminal device can cancel the triggered DSR but not the triggered SR. The terminal device can continue to apply for uplink resources through the triggered SR, which helps to ensure that the data in the cache is transmitted in a timely manner. And the SR counter will not be reset to zero, but will continue to count. If the uplink wireless conditions are not good, the maximum number of SRs can be reached earlier, thereby triggering random access as early as possible.

[0060] In other implementations, if the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are met, the terminal device cancels the first DSR but does not cancel the first SR. That is, if the terminal device has triggered the DSR, and there is temporarily no data that can trigger the DSR again in the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering conditions, and the terminal device has cached data of the LCH / LCG that triggered the DSR or data of other LCH / LCGs, and these data will not trigger the DSR again temporarily, but there is a high probability that the DSR will be triggered soon, and the terminal device has triggered the SR, then the terminal device may also cancel the triggered DSR, but not the triggered SR. The terminal device can continue to apply for uplink resources through the triggered SR, which helps to ensure that the data in the cache is transmitted in a timely manner. And the SR counter will not be reset to zero, but will continue to count. If the uplink wireless conditions are not good, the maximum number of SRs can be reached earlier, thereby triggering random access as early as possible.

[0061] In other implementations, if the first, second, third, and fifth conditions are met, the terminal device cancels the first DSR and the first SR. That is, if the terminal device has already triggered a DSR, and the LCH / LCG that triggered the DSR or the LCH / LCG that meets the DSR triggering conditions temporarily does not contain data that can trigger another DSR, and the terminal device has cached data for the LCH / LCG that triggered the DSR or data for other LCH / LCGs, and the terminal device has already triggered an SR, the terminal device can cancel the triggered DSR and the triggered SR. Based on this, the terminal device can reduce meaningless SRs, helping to save terminal device resource overhead.

[0062] In other implementations, if the first, second, third, fourth, and fifth conditions are met, the terminal device cancels the first DSR and the first SR. That is, if the terminal device has already triggered a DSR, and there is temporarily no data in the LCH / LCG that triggered the DSR or the LCH / LCG that meets the DSR triggering conditions that can trigger the DSR again, and the terminal device has cached data from the LCH / LCG that triggered the DSR or data from other LCH / LCGs, and this data will not trigger the DSR again for the time being, but is likely to trigger the DSR soon, and the terminal device has already triggered an SR, then the terminal device may also cancel the triggered DSR and the triggered SR. Based on this, the terminal device can reduce meaningless SRs, which helps save the terminal device's resource overhead.

[0063] Furthermore, if the first condition, the second condition, the third condition, and the fifth condition are met, or if the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are met, when the terminal device cancels both the first DSR and the first SR, the count value of the counter of the first SR can be recorded. And the terminal device can make the initial value of the counter of the second SR triggered after the first SR the count value of the counter of the first SR. Based on this, the counter of the second SR can reach the maximum value faster to trigger random access, which helps to ensure that the service data is transmitted in time. Furthermore, the time interval between the triggering time of the second SR and the triggering time of the first SR can be less than the third threshold, that is, the second SR can be triggered within a period of time after the first SR is triggered. During this period, the uplink wireless conditions change less. If the uplink wireless conditions are poor, triggering random access faster will help reduce the adverse effects on service data transmission.

[0064] In other implementations, if the first, second, and fifth conditions are met, the terminal device cancels the first DSR and the first SR. That is, if the terminal device has triggered a DSR, and there is temporarily no data that can trigger the DSR again in the LCH / LCG that has triggered the DSR or the LCH / LCG that meets the DSR triggering conditions, and the terminal device has triggered an SR, the terminal device can cancel the triggered DSR and the triggered SR. Based on this, it helps the terminal device reduce the sending of meaningless SRs. Furthermore, if the prohibition timer of the first SR is running, the terminal device can stop the prohibition timer after canceling the first SR.

[0065] In other implementations, if the first and fifth conditions are met, the terminal device cancels the first DSR and the first SR. That is, if the terminal device has already triggered a DSR and an SR, the terminal device can cancel the triggered DSR and the triggered SR. This helps the terminal device reduce the sending of meaningless SRs. Furthermore, if the prohibit timer for the first SR is running, the terminal device can stop the prohibit timer after canceling the first SR.

[0066] It is worth noting that the second threshold and / or third threshold described above can be predefined by the protocol or configured by the network device. For example, the network device can configure the second threshold and / or third threshold via a radio resource control (RRC) message. For another example, the network device can also configure the second threshold and / or third threshold via a dedicated RRC message. Furthermore, the second threshold and / or third threshold can be configured for each LCH. Alternatively, the second threshold and / or third threshold can also be configured for each LCG.

[0067] The method embodiment of the present application is described in detail above in conjunction with Figures 1 to 5 . The device embodiment of the present application is described in detail below in conjunction with Figures 6 and 7 . It should be understood that the description of the method embodiment corresponds to the description of the device embodiment. Therefore, for parts not described in detail, reference can be made to the above method embodiment.

[0068] Figure 6 is a schematic diagram of the structure of a terminal device provided by an embodiment of the present application. The terminal device 600 in Figure 6 includes a first module 610. The first module 610 is used to cancel or not cancel the first DSR when the target condition is met; wherein the target condition includes one or more of the following: a first condition, indicating that the terminal device has triggered the first DSR; a second condition, indicating that there is no data in the first LCH / LCG with a delay budget less than the first threshold, the first LCH / LCG is the LCH / LCG that triggers the first DSR, or the first LCH / LCG is the LCH / LCG other than the LCH / LCG that triggers the first DSR condition, and the first threshold is used to trigger the DSR; a third condition, indicating that the terminal device has data in the first LCH / LCG cache, or the terminal device has data in the LCH / LCG other than the first LCH / LCG cache; a fourth condition, indicating that the time interval between the data of the first LCH / LCG or the LCH / LCG other than the first LCH / LCG and the target time is less than or equal to the second threshold and greater than the first threshold, and the target time is the end time of the delay budget corresponding to the target data; a fifth condition, indicating that the terminal device has triggered the first SR.

[0069] In some implementations, if the first condition, the second condition, and the third condition are satisfied, the first module 610 is configured to not cancel the first DSR.

[0070] In some implementations, if the first condition, the second condition, the third condition, and the fourth condition are satisfied, the first module 610 is configured to not cancel the first DSR.

[0071] In some implementations, if the first condition, the second condition, the third condition, and the fifth condition are satisfied, the first module 610 is configured to not cancel the first DSR.

[0072] In some implementations, if the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the first module 610 is configured to not cancel the first DSR.

[0073] In some implementations, if the first condition, the second condition, the third condition, and the fifth condition are satisfied, the first module 610 is configured to cancel the first DSR but not the first SR.

[0074] In some implementations, if the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the first module 610 is configured to cancel the first DSR but not the first SR.

[0075] In some implementations, if the first condition, the second condition, the third condition, and the fifth condition are satisfied, the first module 610 is configured to cancel the first DSR and the first SR.

[0076] In some implementations, if the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the first module 610 is configured to cancel the first DSR and the first SR.

[0077] In some implementations, the first module 610 is further configured to record the count value of the counter of the first SR, and set the initial value of the counter of the second SR triggered after the first SR to be the count value of the counter of the first SR.

[0078] In some implementations, a time interval between a triggering time of the second SR and a triggering time of the first SR is smaller than a third threshold.

[0079] In some implementations, the second threshold and / or the third threshold are configured for each LCH or each LCG.

[0080] In some implementations, if the first condition, the second condition, and the fifth condition are satisfied, the first module 610 is configured to cancel the first DSR and the first SR.

[0081] In some implementations, the first module 610 is further configured to: if the prohibit timer of the first SR is running, stop the prohibit timer.

[0082] In some implementations, if the first condition and the fifth condition are satisfied, the first module 610 is configured to cancel the first DSR and cancel the first SR.

[0083] Figure 7 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application. The communication device 700 in Figure 7 can be used to implement the method described in the above method embodiment. The device 700 can be a chip, a terminal device, or a base station.

[0084] The communication device 700 may include one or more processors 710. The processor 710 may support the device 700 to implement the method described in the above method embodiment. The processor 710 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be another general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, etc. The general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0085] The communication device 700 may further include one or more memories 720. The memories 720 store programs that can be executed by the processor 710, causing the processor 710 to perform the methods described in the above method embodiments. The memories 720 may be independent of the processor 710 or integrated into the processor 710.

[0086] The communication device 700 may further include a transceiver 730. The processor 710 may communicate with other devices or chips via the transceiver 730. For example, the processor 710 may transmit and receive data with other devices or chips via the transceiver 730.

[0087] It should be understood that in the embodiment of the present application, the processor 710 can adopt a general central processing unit (CPU), a microprocessor, an application specific integrated circuit (ASIC), or one or more integrated circuits to execute relevant programs to implement the technical solutions provided in the embodiment of the present application.

[0088] The memory 720 may include a read-only memory and a random access memory, and provides instructions and data to the processor 710. A portion of the processor 710 may also include a non-volatile random access memory. For example, the processor 710 may also store information about the device type.

[0089] During implementation, each step of the above method can be completed by an integrated logic circuit of the hardware in the processor 710 or by instructions in the form of software. The method for requesting uplink transmission resources disclosed in conjunction with the embodiments of the present application can be directly embodied as being executed by a hardware processor, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in a mature storage medium in the art, such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory, or an electrically erasable programmable memory, a register, etc. The storage medium is located in the memory 720, and the processor 710 reads the information in the memory 720 and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

[0090] It should be understood that in the embodiment of the present application, the processor 710 may be a central processing unit (CPU), or may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0091] The present application also provides a computer-readable storage medium for storing a program. The computer-readable storage medium can be applied to a terminal device or network device provided in the present application, and the program enables a computer to execute the method for processing DSR in various embodiments of the present application.

[0092] The present application also provides a computer program product. The computer program product includes a program. The computer program product can be applied to the terminal device or network device provided in the embodiments of the present application, and the program causes a computer to execute the method for processing DSR in various embodiments of the present application.

[0093] The present application also provides a computer program that can be applied to a terminal device or a network device provided in the present application, and enables a computer to execute the method for processing DSR in each embodiment of the present application.

[0094] It should be understood that the terms "system" and "network" in this application can be used interchangeably. In addition, the terms used in this application are only used to explain the specific embodiments of this application and are not intended to limit this application. The terms "first", "second", "third", and "fourth" in the specification and claims of this application and the accompanying drawings are used to distinguish different objects rather than to describe a specific order. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions.

[0095] In the embodiment of the present application, "B corresponding to A" means that B is associated with A and B can be determined based on A. However, it should be understood that determining B based on A does not mean determining B based solely on A, but B can also be determined based on A and / or other information.

[0096] In the embodiments of the present application, the term "corresponding" may indicate a direct or indirect correspondence between the two, or an association relationship between the two, or a relationship between indication and indication, configuration and configuration, etc.

[0097] In the embodiments of the present application, "pre-definition" or "pre-configuration" may be implemented by pre-storing corresponding codes, tables, or other methods that can be used to indicate relevant information in a device (e.g., a terminal device and a network device). The present application does not limit the specific implementation method. For example, pre-definition may refer to information defined in a protocol.

[0098] In the embodiments of the present application, the “protocol” may refer to a standard protocol in the communications field, for example, it may include an LTE protocol, an NR protocol, and related protocols used in future communication systems, and the present application does not limit this.

[0099] In the embodiments of this application, the term "and / or" is simply a description of the association relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. In addition, the character " / " in this document generally indicates that the related objects are in an "or" relationship.

[0100] In various embodiments of the present application, the size of the serial numbers of the above-mentioned processes does not mean the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application.

[0101] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0102] The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0103] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0104] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. 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 computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be read by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital versatile disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0105] The above description is merely a specific embodiment of the present application, but the scope of protection of the present application is not limited thereto. Any changes or substitutions that can be easily conceived by a person skilled in the art within the technical scope disclosed in this application should be included in the scope of protection of this application. Therefore, the scope of protection of this application should be based on the scope of protection of the claims.

Claims

1. A method for processing a Delayed Status Report (DSR), characterized in that, including: If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR; wherein, the target condition includes one or more of the following: The first condition, indicating that the terminal device triggers the first DSR; The second condition, indicating that there is no data with a delay budget less than a first threshold in the first logical channel LCH / logical channel group LCG, where the first LCH / LCG is the LCH / LCG that triggers the first DSR, or the first LCH / LCG is an LCH / LCG other than the LCH / LCG that triggers the first DSR and satisfies the first DSR condition, and the first threshold is used to trigger DSR; The third condition, indicating that the terminal device caches data of the first LCH / LCG, or the terminal device caches data of an LCH / LCG other than the first LCH / LCG; The fourth condition, indicating that the time interval between the data of the first LCH / LCG or the LCH / LCG other than the first LCH / LCG and the target time is less than or equal to a second threshold and greater than the first threshold, and the target time is the deadline of the delay budget corresponding to the target data; The fifth condition, indicating that the terminal device has triggered a first scheduling request SR.

2. The method according to claim 1, characterized in that, The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, and the third condition are satisfied, the terminal device does not cancel the first DSR.

3. The method according to claim 1, characterized in that, The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, the third condition, and the fourth condition are satisfied, the terminal device does not cancel the first DSR.

4. The method according to claim 1, characterized in that The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, the third condition, and the fifth condition are satisfied, the terminal device does not cancel the first DSR.

5. The method according to claim 1, characterized in that The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the terminal device does not cancel the first DSR.

6. The method according to claim 1, characterized in that The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, the third condition, and the fifth condition are satisfied, the terminal device cancels the first DSR, but does not cancel the first SR.

7. The method according to claim 1, characterized in that The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the terminal device cancels the first DSR, but does not cancel the first SR.

8. The method according to claim 1, wherein The "If the target condition is satisfied, the terminal device cancels or does not cancel the first DSR" includes: If the first condition, the second condition, the third condition, and the fifth condition are satisfied, the terminal device cancels the first DSR and cancels the first SR.

9. The method according to claim 1, characterized in that, The case where the terminal device cancels or does not cancel the first DSR if a target condition is satisfied includes: If the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the terminal device cancels the first DSR and cancels the first SR.

10. The method according to claim 8 or 9, characterized in that The method further includes: The terminal device records the count value of the counter of the first SR and sets the initial value of the counter of the second SR triggered after the first SR to the count value.

11. The method according to claim 10, wherein The time interval between the triggering time of the second SR and the triggering time of the first SR is less than a third threshold.

12. The method according to claim 11, wherein The second threshold and / or the third threshold are configured for each LCH or each LCG.

13. The method according to claim 1, wherein The case where the terminal device cancels or does not cancel the first DSR if a target condition is satisfied includes: If the first condition, the second condition, and the fifth condition are satisfied, the terminal device cancels the first DSR and cancels the first SR.

14. The method according to claim 13, characterized in that The method further includes: If the prohibition timer of the first SR is running, stop the prohibition timer.

15. The method according to claim 1, wherein The case where the terminal device cancels or does not cancel the first DSR if a target condition is satisfied includes: If the first condition and the fifth condition are satisfied, the terminal device cancels the first DSR and cancels the first SR.

16. A terminal device, characterized in that, including: A first module, configured to cancel or not cancel a first delayed status report (DSR) when a target condition is satisfied; Wherein, the target condition includes one or more of the following: A first condition, indicating that the terminal device has triggered the first DSR; A second condition, indicating that there is no data with a delay budget less than a first threshold in a first logical channel (LCH) / logical channel group (LCG), where the first LCH / LCG is the LCH / LCG that triggers the first DSR, or the first LCH / LCG is an LCH / LCG other than the LCH / LCG that triggers the first DSR and satisfies the first DSR condition, and the first threshold is used to trigger a DSR; A third condition, indicating that the terminal device has buffered data of the first LCH / LCG, or the terminal device has buffered data of an LCH / LCG other than the first LCH / LCG; A fourth condition, indicating that the time interval between the data of the first LCH / LCG or the LCH / LCG other than the first LCH / LCG and a target time is less than or equal to a second threshold and greater than the first threshold, and the target time is the deadline of the delay budget corresponding to the target data; A fifth condition, indicating that the terminal device has triggered a first scheduling request (SR).

17. The terminal device according to claim 16, wherein If the first condition, the second condition, and the third condition are satisfied, the first module is configured not to cancel the first DSR.

18. The terminal device according to claim 16, characterized in that, If the first condition, the second condition, the third condition, and the fourth condition are satisfied, the first module is used not to cancel the first DSR.

19. The terminal device according to claim 16, characterized in that, If the first condition, the second condition, the third condition, and the fifth condition are satisfied, the first module is used not to cancel the first DSR.

20. The terminal device according to claim 16, characterized in that, If the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the first module is used not to cancel the first DSR.

21. The terminal device according to claim 16, wherein, If the first condition, the second condition, the third condition, and the fifth condition are satisfied, the first module is used to cancel the first DSR, but not to cancel the first SR.

22. The terminal device according to claim 16, wherein If the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the first module is used to cancel the first DSR, but not to cancel the first SR.

23. The terminal device according to claim 16, characterized in that, If the first condition, the second condition, the third condition, and the fifth condition are satisfied, the first module is used to cancel the first DSR and cancel the first SR.

24. The terminal device according to claim 16, characterized in that, If the first condition, the second condition, the third condition, the fourth condition, and the fifth condition are satisfied, the first module is used to cancel the first DSR and cancel the first SR.

25. The terminal device according to claim 23 or 24, characterized in that, The first module is further used to record the count value of the counter of the first SR, and make the initial value of the counter of the second SR triggered after the first SR be the count value.

26. The terminal device according to claim 25, characterized in that, The time interval between the triggering time of the second SR and the triggering time of the first SR is less than a third threshold.

27. The terminal device according to claim 26, wherein, The second threshold and / or the third threshold are configured for each LCH or each LCG.

28. The terminal device according to claim 16, wherein If the first condition, the second condition, and the fifth condition are satisfied, the first module is used to cancel the first DSR and cancel the first SR.

29. The terminal device according to claim 28, characterized in that, The first module is further used to: If the inhibition timer of the first SR is running, stop the inhibition timer.

30. The terminal device according to claim 16, wherein If the first condition and the fifth condition are satisfied, the first module is used to cancel the first DSR and cancel the first SR.

31. A terminal device, characterized in that, Comprising a transceiver, a memory, and a processor, the memory is used to store a program, and the processor is used to call the program in the memory and control the transceiver to receive or send signals, so that the terminal device executes the method according to any one of claims 1-15.

32. A device, characterized in that, Comprising a processor, used to call a program from a memory, so that the device executes the method according to any one of claims 1-15.

33. A chip, characterized in that, Comprising a processor, used to call a program from a memory, so that the device installed with the chip executes the method according to any one of claims 1-15.

34. A computer-readable storage medium, characterized in that, A program is stored thereon, and the program causes a computer to execute the method according to any one of claims 1-15.

35. A computer program product, characterized in that, Comprising a program, the program causes a computer to execute the method according to any one of claims 1-15.

36. A computer program, characterized in that, The computer program causes a computer to execute the method according to any one of claims 1-15.

Images