Cache status reporting method and apparatus

Abstract

Embodiments of the present application provide a cache status reporting method and apparatus. The method comprises: when first data in a first logic channel (LCH) meets a first condition, triggering a DSR, wherein the first condition comprises: the remaining time corresponding to the first data is changed from being greater than or equal to a first threshold to less than the first threshold; sending the DSR to a network device; and after the DSR is sent, when the remaining time of second data comprised in the first data in the first LCH is less than the first threshold, not triggering the DSR. According to the method, when the remaining time corresponding to the first data in the first LCH is changed from being greater than or equal to a first threshold to less than the first threshold, the DSR is triggered once, and then the remaining time corresponding to the first data continues to be reduced and is always less than the first threshold; however, the DSR is not continuously triggered after the DSR is triggered once for the first data, so that the frequent triggering of the DSR can be avoided, thereby reducing the consumption of uplink resources.

Description

Cache status reporting method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of the People's Republic of China on September 28, 2023, with application number 202311295513.5 and application name "A cache status reporting method and device", the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a cache status reporting method and device. Background Art

[0004] Extended reality (XR) refers to various hybrid environments of real and virtual reality, as well as human-machine interactions, generated by computer technology and wearable devices. Typical forms include augmented reality (AR), virtual reality (VR), and mixed reality (MR). XR services typically generate data frames periodically at a certain frame rate. The frame size is not fixed, and each frame may experience varying encoding delays and forwarding delays within the core network. This can cause jitter in the arrival of XR data at the air interface within each cycle, meaning that XR data may arrive earlier or later than expected. XR services typically have high latency requirements. If XR data is not successfully transmitted within the latency budget, it will time out and become useless. The network should strive to schedule and transmit data within the latency budget to avoid data timeouts that affect the service experience.

[0005] For uplink XR services, in order to enable network devices (such as base stations) to understand the delay budget consumption of data in the user equipment (UE) buffer, so as to complete data transmission before the packet delay budget (PDB) / PDU set delay budget (PSDB) is exhausted, a remaining time concept and reporting mechanism are introduced, that is, the UE can report the remaining time of the data in the buffer to the base station. Specifically, the UE can send a medium access control control element (MAC CE) to the base station to explicitly or implicitly reflect the remaining time of part or all of the data in the UE buffer. The MAC CE can be called a delay status report (DSR). The current DSR triggering method is: when the remaining time of a protocol data unit (PDU) or PDU set in a logical channel group (LCG) is less than a threshold, the DSR is triggered. The threshold is configured by the network device for each LCG for the UE. After triggering DSR, the UE can send a DSR MAC CE on uplink transmission resources when uplink transmission resources become available. However, the current DSR triggering conditions are not reasonable. When the remaining time of data is less than the threshold, the remaining time of this data will always be less than the threshold. In other words, the DSR triggering conditions are always met. This will cause this data to repeatedly trigger DSR, resulting in a waste of uplink transmission resources.

[0006] Summary of the Invention

[0007] Embodiments of the present application provide a cache status reporting method and apparatus to reduce consumption of uplink transmission resources.

[0008] In the first aspect, the present application provides a cache status reporting method, which can be implemented by a terminal device or a chip or component inside the terminal device. In the following, taking the execution subject as an example of a terminal device, the method can be implemented by the following steps: when there is first data in the first logical channel LCH that meets the first condition, the terminal device triggers the DSR, wherein the first condition includes: the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold. The terminal device sends the DSR to the network device. After sending the DSR, when the remaining time of the second data included in the first data in the first LCH is less than the first threshold, the terminal device does not trigger the DSR.

[0009] Based on this solution, when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, a DSR is triggered once. After that, the remaining time corresponding to the first data continues to decrease. Although the remaining time corresponding to the first data is always less than the first threshold, the first data no longer triggers the DSR. In other words, the DSR will only be triggered once for the first data, thereby avoiding frequent triggering of the DSR and reducing the consumption of uplink resources.

[0010] In one possible implementation, the first condition further includes: the amount of data corresponding to the first data is greater than or equal to a second threshold. The first data may include one or more data items. When the first data includes multiple data items, the remaining time corresponding to the first data item changes from greater than or equal to the first threshold to less than the first threshold, including: the remaining time corresponding to the first portion of data included in the first data item all changes from greater than or equal to the first threshold to less than the first threshold, and the remaining time corresponding to the second portion of data included in the first data item all changes from greater than or equal to the first threshold to less than the first threshold, and the first portion of data item and the second portion of data item constitute the multiple data items. It is understood that the second portion of data may not exist, that is, the remaining time of the multiple data items included in the first data item all changes from greater than or equal to the first threshold to less than the first threshold. In this implementation, a DSR is triggered only when the remaining time corresponding to the first data item changes from greater than or equal to the first threshold to less than the first threshold, and the amount of data corresponding to the first data item is greater than or equal to the second threshold. The first condition for triggering a DSR considers not only the remaining time of the data in the first LCH but also the amount of data that meets the remaining time threshold. This effectively reduces the frequency of DSR triggering and significantly reduces uplink resource consumption due to DSR triggering.

[0011] In a possible implementation, the first data does not include data that has triggered DSR, that is, data that has triggered DSR is no longer counted in the amount of data used to determine whether to trigger DSR, to ensure that the data only triggers DSR once.

[0012] In a possible implementation, the second threshold is preset or indicated by the network device to the terminal device.

[0013] In one possible implementation, the first condition, in addition to including that the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, further includes any one of the following conditions 1.1, 1.2, 1.3, and 1.4:

[0014] Condition 1.1: There is no data in the second LCH, and the second LCH is different from the first LCH;

[0015] Condition 1.2: The second LCH does not contain data with a remaining time less than the first threshold;

[0016] Condition 1.3: The priority of the first LCH is higher than that of the third LCH, the third LCH contains data, and the third LCH is different from the first LCH;

[0017] Condition 1.4: The priority of the first LCH is higher than that of the fourth LCH, the fourth LCH contains data with a remaining time less than a first threshold, and the fourth LCH is different from the first LCH.

[0018] Through this implementation, the first condition for triggering DSR not only considers the remaining time of the data in the first LCH, but also considers whether there is data, or urgent data, or data with higher priority, or urgent data with higher priority, etc. in other LCHs, which can ensure that the data to be transmitted, or urgent data, or data with higher priority, or urgent data with higher priority can be sent out first.

[0019] In one possible implementation, the first condition, in addition to including that the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, further includes any one of the following conditions 2.1, 2.2, 2.3, 2.4, and 2.5:

[0020] Condition 2.1: The first data corresponds to a high importance;

[0021] Condition 2.2: The first data has a high importance, and the second LCH does not contain any data, and the second LCH is different from the first LCH;

[0022] Condition 2.3: The first data has high importance, and the second LCH does not contain data with a remaining time less than the first threshold;

[0023] Condition 2.4: The first data has a high importance, the priority of the first LCH is higher than that of the third LCH, the third LCH has data, and the third LCH is different from the first LCH;

[0024] Condition 2.5: The first data has high importance, and the priority of the first LCH is higher than that of the fourth LCH. The fourth LCH has data with a remaining time less than the first threshold, and the fourth LCH is different from the first LCH.

[0025] Through this implementation, the first condition for triggering DSR not only considers the remaining time of the data in the first LCH, but also considers the importance of the data and whether there is data in other LCHs, or urgent data, or data with higher priority, or urgent data with higher priority, etc., which can ensure that data with high importance, or urgent data with high importance, or data with high importance and higher priority, or urgent data with high importance and higher priority to be transmitted can be sent out first.

[0026] In one possible implementation, the first condition, in addition to including that the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold and the data volume corresponding to the first data is greater than or equal to the second threshold, further includes any one of the following conditions 2.1, 2.2, 2.3, 2.4, and 2.5:

[0027] Condition 2.1: The first data corresponds to a high importance;

[0028] Condition 2.2: The first data has a high importance, and the second LCH does not contain any data, and the second LCH is different from the first LCH;

[0029] Condition 2.3: The first data has high importance, and the second LCH does not contain data with a remaining time less than the first threshold;

[0030] Condition 2.4: The first data has a high importance, the priority of the first LCH is higher than that of the third LCH, the third LCH has data, and the third LCH is different from the first LCH;

[0031] Condition 2.5: The first data has high importance, and the priority of the first LCH is higher than that of the fourth LCH. The fourth LCH has data with a remaining time less than the first threshold, and the fourth LCH is different from the first LCH.

[0032] Through this implementation, the first condition for triggering DSR not only considers the amount of data in the first LCH that meets the remaining time condition, but also considers the importance of this data and whether there is data in other LCHs, or urgent data, or data with higher priority, or urgent data with higher priority, etc., thereby not only reducing the frequency of triggering DSR, but also ensuring that when other LCHs have important data, or important urgent data, or data with high importance and higher priority, or urgent data with high importance and higher priority to be transmitted, the data of other LCHs can be sent out first.

[0033] In one possible implementation, in addition to the first condition that the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, the first condition includes any one of the following conditions 3.1, 3.2, 3.3, and 3.4:

[0034] Condition 3.1: The first data corresponds to a high importance, and the second LCH does not contain any high importance data, and the second LCH is different from the first LCH;

[0035] Condition 3.2: The first data corresponds to a high importance, and the second LCH does not contain any high importance data with a remaining time less than the first threshold;

[0036] Condition 3.3: The first data has high importance, the priority of the first LCH is higher than that of the fifth LCH, the fifth LCH has high-importance data, and the fifth LCH is different from the first LCH;

[0037] Condition 3.4: The first data corresponds to high importance, and the priority of the first LCH is higher than that of the sixth LCH. The sixth LCH has data with a remaining time less than the first threshold and high importance, and the sixth LCH is different from the first LCH.

[0038] Through this implementation, the first condition for triggering DSR not only considers the remaining time and importance of the data in the first LCH, but also considers whether other LCHs have data of high importance, or urgent data of high importance, or data of high importance and higher priority, or urgent data of high importance and higher priority, etc. This ensures that when other LCHs do not have data of high importance, or urgent data of high importance, or data of high importance and higher priority, or urgent data of high importance and higher priority, etc. to be transmitted, the first data only triggers DSR once, and when other LCHs have data of high importance, or urgent data of high importance, or data of high importance and higher priority, or urgent data of high importance and higher priority to be transmitted, these data from other LCHs can be sent out first.

[0039] In one possible implementation, in addition to the first condition that the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold and the data volume corresponding to the first data is greater than or equal to the second threshold, the first condition includes any one of the following conditions 3.1, 3.2, 3.3, and 3.4:

[0040] Condition 3.1: The first data corresponds to a high importance, and the second LCH does not contain any high importance data, and the second LCH is different from the first LCH;

[0041] Condition 3.2: The first data corresponds to a high importance, and the second LCH does not contain any high importance data with a remaining time less than the first threshold;

[0042] Condition 3.3: The first data has high importance, the priority of the first LCH is higher than that of the fifth LCH, the fifth LCH has high-importance data, and the fifth LCH is different from the first LCH;

[0043] Condition 3.4: The first data corresponds to high importance, and the priority of the first LCH is higher than that of the sixth LCH. The sixth LCH has data with a remaining time less than the first threshold and high importance, and the sixth LCH is different from the first LCH.

[0044] Through this implementation, the first condition for triggering DSR not only considers the data amount and importance of the data in the first LCH that meets the remaining time condition, but also considers whether there are high-importance data, or high-importance urgent data, or high-importance and higher-priority data, or high-importance and higher-priority urgent data, etc. in other LCHs. Therefore, not only can the frequency of triggering DSR be reduced when there are no high-importance data, or high-importance urgent data, or high-importance and higher-priority data, or high-importance and higher-priority urgent data, etc. to be transmitted in other LCHs, but also these data in other LCHs can be sent out first when there are high-importance data, or high-importance urgent data, or high-importance and higher-priority data, or high-importance and higher-priority urgent data, etc. to be transmitted in other LCHs.

[0045] In one possible implementation, the first condition, in addition to the remaining time corresponding to the first data changing from greater than or equal to the first threshold to less than the first threshold, also includes: a flag bit corresponding to the first data having a first value, the first value being used to indicate that the first data has not triggered a DSR. With this implementation, the terminal device only needs to maintain the flag bit for each data item. The flag bit value can be used to determine which data items have triggered a DSR and which have not. This reduces the storage or processing overhead required of the terminal device compared to monitoring the remaining time of each data item.

[0046] In a possible implementation, after the terminal device triggers a delay status report DSR, the terminal device may further update a flag bit corresponding to the first data to a second value, where the second value is used to indicate that the first data has triggered the DSR.

[0047] In one possible implementation, the first condition, in addition to the remaining time corresponding to the first data changing from greater than or equal to the first threshold to less than the first threshold, also includes: the sequence number corresponding to the first data is greater than the DSR sequence number, where the DSR sequence number is the maximum sequence number corresponding to data that has triggered a DSR. With this implementation, the terminal device only needs to maintain one variable, namely the DSR sequence number. This DSR sequence number allows the terminal device to determine whether data before the DSR sequence number triggered a DSR, and whether data after the DSR sequence number did not. This reduces the storage or processing overhead required of the terminal device compared to monitoring the remaining time of each data item.

[0048] In a possible implementation, after the terminal device triggers the delay status report DSR, the terminal device may also update the DSR sequence number to a sequence number corresponding to the first data.

[0049] In a second aspect, the present application provides a cache status reporting method, which can be implemented by a terminal device or a chip or component within the terminal device. Taking the terminal device as an example, the method can be implemented by the following steps: the terminal device periodically triggers a Delay Status Report (DSR) for a first logical channel (LCH); and the terminal device periodically sends the DSR to a network device.

[0050] Based on this solution, the terminal device periodically triggers DSR for the first LCH, which can avoid unnecessary DSR triggering and sending, thereby saving network resources.

[0051] In a possible implementation, the terminal device may further receive first configuration information sent by the network device, where the first configuration information is used to indicate a period for triggering DSR corresponding to the first LCH. Thus, the terminal device may periodically trigger DSR according to the period indicated in the first configuration information.

[0052] In one possible implementation, the first configuration information is further used to indicate when the terminal device triggers DSR for the first time. The terminal device may trigger the first DSR according to the timing of the first DSR triggering indicated by the first configuration information, and then periodically trigger DSR according to the period indicated in the first configuration information.

[0053] In one possible implementation, the terminal device may also receive downlink control information DCI, where the DCI is used to indicate when the terminal device triggers the DSR for the first time. The terminal device may trigger the first DSR according to the timing of the first DSR triggering indicated by the DCI, and then periodically trigger the DSR according to the period indicated in the first configuration information.

[0054] In a third aspect, the present application further provides a communication device capable of implementing any of the methods provided in any of the first to second aspects above. The communication device may be implemented in hardware or by executing corresponding software implementations in hardware. The hardware or software includes one or more units or modules corresponding to the above functions.

[0055] In one possible implementation, the communication device includes a processor configured to support the communication device in executing the corresponding functions of the terminal device in the method described above. The communication device may also include a memory, which may be coupled to the processor and stores program instructions and data necessary for the communication device. Optionally, the communication device also includes an interface circuit for supporting communication between the communication device and a network device.

[0056] In one possible implementation, the communication device includes corresponding functional modules for implementing the steps in the above method. The functions can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions.

[0057] In one possible implementation, the structure of the communication device includes a processing unit and a communication unit, which can perform the corresponding functions in the above method examples. For details, please refer to the description of the method provided in any one of the first aspect to the second aspect, which will not be repeated here.

[0058] In a fourth aspect, a communication device is provided, comprising a processor and an interface circuit, wherein the interface circuit is used to receive signals from other communication devices outside the communication device and transmit them to the processor or send signals from the processor to other communication devices outside the communication device, and the processor is used to implement the method in any possible implementation of any of the first to second aspects through a logic circuit or by executing code instructions.

[0059] In a fifth aspect, a computer-readable storage medium is provided, which stores a computer program or instruction. When the computer program or instruction is executed by a processor, the method in any possible implementation of any one of the first to second aspects is implemented.

[0060] In a sixth aspect, a computer program product storing instructions is provided, which, when executed by a processor, implements the method in any possible implementation of any one of the first to second aspects.

[0061] In a seventh aspect, a circuit is provided, which is used to execute the method in any possible implementation of any one of the first to second aspects above, and the circuit may include a chip circuit. Optionally, the circuit may also be coupled to a memory.

[0062] In an eighth aspect, a chip is provided, comprising a processor configured to implement the method of any possible implementation of any of the first and second aspects. Optionally, the chip may further comprise a memory. The chip may be composed of a single chip or may include a chip and other discrete devices.

[0063] The technical effects brought about by the above-mentioned second to eighth aspects can be found in the relevant description of the above-mentioned first or second aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS

[0064] FIG1 is a schematic diagram of a system architecture provided in an embodiment of the present application;

[0065] FIG2 is a schematic diagram of triggering DSR in the prior art;

[0066] FIG3 is a flow chart of a cache status reporting method according to an embodiment of the present application;

[0067] FIG4 is a schematic diagram of triggering DSR based on remaining time according to an embodiment of the present application;

[0068] FIG5 is a schematic diagram of triggering DSR based on data volume according to an embodiment of the present application;

[0069] FIG6 is a schematic diagram of triggering a DSR based on a flag bit according to an embodiment of the present application;

[0070] FIG7 is a schematic diagram of triggering DSR based on a sequence number according to an embodiment of the present application;

[0071] FIG8 is a flow chart of a cache status reporting method according to an embodiment of the present application;

[0072] FIG9 is a schematic diagram of a periodically triggered DSR according to an embodiment of the present application;

[0073] FIG10 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

[0074] FIG11 is a schematic diagram of the structure of a communication device provided in an embodiment of the present application;

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

[0076] The present application provides a cache status reporting method and apparatus. The method and apparatus are based on the same inventive concept. Since the method and apparatus solve similar problems, the embodiments of the apparatus and method can refer to each other, and the repetitive parts will not be repeated.

[0077] In the description of the embodiments of the present application, "and / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent three situations: A exists alone, A and B exist at the same time, and B exists alone, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. In addition, it should be understood that in the description of the present application, words such as "first" and "second" are only used for the purpose of distinguishing the description, and cannot be understood as indicating or implying relative importance, nor can they be understood as indicating or implying order.

[0078] It should be understood that in the present application, "at least one (item)" refers to one or more. "Multiple" refers to two or more. "At least two (items)" refers to two or three and more. "At least one of the following (items)" or similar expressions refers to any combination of these items, including any combination of single items (items) or plural items (items). For example, at least one of a, b or c can represent: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple. "... when" and "if" both mean that corresponding processing will be carried out under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean that there are other limitations.

[0079] In the embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being preferred or advantageous over other embodiments or designs. Rather, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a concrete manner to facilitate understanding.

[0080] Furthermore, the terms "include," "comprise," and "have," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not limited to the listed steps or elements, but may optionally include steps or elements not listed, or may optionally include other steps or elements inherent to the process, method, product, or apparatus.

[0081] The cache status reporting method provided in the embodiment of the present application can be applied to various communication systems, and can be applied to the fourth generation (4G) communication system, such as the long term evolution (LTE) communication system, and can also be applied to the fifth generation (5G) communication system, such as the 5G new radio (NR) communication system, and can also be applied to the sixth generation (6G) communication system or new communication systems that will emerge in future communication development. The method provided in the embodiment of the present application can also be applied to a Bluetooth system, a wireless fidelity (WiFi) system, a long range radio (LoRa) system, or a vehicle network system. The method provided in the embodiment of the present application can also be applied to a satellite communication system. The satellite communication system can be integrated with the above-mentioned communication system. It is understandable that the cache status reporting method provided in the embodiment of the present application can be applied to other communication systems.

[0082] To facilitate understanding of the embodiments of the present application, the application scenarios used in the present application are described using the architecture of the communication system shown in FIG1 as an example. As shown in FIG1 , the communication system 100 includes a radio access network 110 and a core network 120. Optionally, the communication system 100 also includes a data network (DN) 130. The radio access network 110 includes at least one network device, such as the 5G base station (generation node B, gNB) 111 shown in FIG1 . The radio access network 110 may also include at least one terminal device, such as the XR device 112 and the XR device 113 shown in FIG1 . The downlink data transmission path is as follows: data generated by the application server is forwarded through the data network and sent to the core network 120 via the NG6 interface. The core network 120 then passes the data to the gNB 111 via the NG3 interface. The gNB 111 then sends the data to the XR device 112 via the Uu air interface. The uplink data transmission path is the opposite of the downlink data transmission path.

[0083] The terminal device is connected to the wireless access network device in a wireless manner, and the wireless access network device is connected to the core network in a wireless or wired manner. The core network device and the wireless access network device can be independent and different physical devices, or the functions of the core network device and the logical functions of the wireless access network device can be integrated into the same physical device, or a physical device can integrate some functions of the core network device and some functions of the wireless access network device. Terminal devices and wireless access network devices can be connected to each other in a wired or wireless manner. It can be understood that Figure 1 only shows a possible communication system architecture that can be applied in the embodiment of the present application. In other possible scenarios, the communication system architecture may also include other devices.

[0084] The network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field will know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0085] Below, some terms used in the embodiments of the present application are explained to facilitate understanding by those skilled in the art.

[0086] (1) The network devices involved in the embodiments of the present application may be devices in a wireless network, and the network devices may also be referred to as network devices. For example, the network devices may be radio access network (RAN) nodes that connect terminal devices to a wireless network, and may also be referred to as access network devices. The network devices include, but are not limited to, base stations, evolved NodeBs (eNodeBs), transmission reception points (TRPs), next generation NodeBs (gNBs) in fifth generation (5G) mobile communication systems, access network devices in open radio access networks (O-RANs), next generation base stations in sixth generation (6G) mobile communication systems, base stations in future mobile communication systems, or access nodes in wireless fidelity (WiFi) systems; or they may be modules or units that perform part of the functions of a base station, for example, they may be centralized units (CUs), distributed units (DUs), centralized unit control plane (CU-CP) modules, or centralized unit user plane (CU-UP) modules. The access network device may be a macro base station, a micro base station, an indoor station, a relay node, a donor node, etc. The present application does not limit the specific technology and specific device form used by the network device.

[0087] In some deployments, network equipment may include centralized units (CUs) and distributed units (DUs). RAN equipment, including CU and DU nodes, splits the protocol layers of the gNB in ​​the NR system. Some protocol layer functions are centrally controlled by the CU, while some or all of the remaining protocol layer functions are distributed in the DU, which is centrally controlled by the CU. Furthermore, the CU can be divided into a control plane (CU-CP) and a user plane (CU-UP). The CU-CP is responsible for control plane functions, primarily including radio resource control (RRC) and the control plane's corresponding packet data convergence protocol (PDCP) (i.e., PDCP-C). PDCP-C is primarily responsible for encryption, decryption, integrity protection, and data transmission of control plane data. The CU-UP is responsible for user plane functions, primarily including the service data adaptation protocol (SDAP) and the user plane's corresponding PDCP (i.e., PDCP-U). SDAP is primarily responsible for processing core network data and mapping flows to bearers. The PDCP-U is primarily responsible for data plane encryption and decryption, integrity protection, header compression, sequence number maintenance, and data transmission. The CU-CP and CU-UP are connected via the E1 interface. The CU-CP represents the gNB's connection to the core network via the NG interface and to the DU via the F1 interface control plane (i.e., F1-C). The CU-UP connects to the DU via the F1 interface user plane (i.e., F1-U). Alternatively, the PDCP-C may also reside in the CU-UP.

[0088] It is understandable that in different systems, CU (including CU-CP or CU-UP) or DU may have different names, but those skilled in the art can understand their meanings. For example, in an open radio access network (O-RAN) system, CU may also be called an open CU (O-CU), DU may also be called O-DU, CU-CP may also be called O-CU-CP, and CU-UP may also be called O-CU-UP. For convenience of description, this application uses CU, CU-CP, CU-UP and DU as examples. The network device may also include an active antenna unit (AAU). The CU implements some functions of the gNB, and the DU implements some functions of the gNB. For example, the CU is responsible for processing non-real-time protocols and services and implementing the functions of the RRC layer. The DU is responsible for processing physical layer protocols and real-time services and implementing the functions of the radio link control (RLC) layer, the media access control (MAC) layer and the physical (PHY) layer. In some deployments, the CU can be further divided into a Centralized Unit Control Plane (CU-CP) node and a Centralized Unit User Plane (CU-UP) node, where the CU-CP is responsible for control plane functions and the CU-UP is responsible for user plane functions.

[0089] (2) Core network equipment refers to the equipment in the core network (CN) that provides service support for the terminal. At present, some examples of core network equipment are: access and mobility management function (AMF) entity, session management function (SMF) entity, user plane function (UPF) entity, etc., which are not listed here one by one. Among them, the AMF entity can be responsible for the access management and mobility management of the terminal; the SMF entity can be responsible for session management, such as user session establishment, etc.; the UPF entity can be a functional entity of the user plane, mainly responsible for connecting to the external network. It should be noted that the entity in this application can also be called a network element or a functional entity. For example, the AMF entity can also be called an AMF network element or an AMF functional entity. For another example, the SMF entity can also be called an SMF network element or an SMF functional entity, etc.

[0090] (3) The terminal devices involved in the embodiments of the present application may also be referred to as user equipment, mobile stations (MS), mobile terminals (MT), etc., which are devices that provide voice or data connectivity to users, and may also be Internet of Things devices. For example, terminal devices include handheld devices with wireless connection functions, vehicle-mounted devices, etc. At present, terminal devices may be: mobile phones, tablet computers, laptops, PDAs, mobile internet devices (MIDs), wearable devices (such as smart watches, smart bracelets, pedometers, etc.), vehicle-mounted devices (such as cars, bicycles, electric vehicles, airplanes, ships, trains, high-speed railways, etc.), VR devices, AR devices, wireless terminals in industrial control, smart home devices (such as refrigerators, TVs, air conditioners, electric meters, etc.), smart robots, workshop equipment, wireless terminals in unmanned driving, wireless terminals in remote surgery, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, or wireless terminals in smart homes, flying devices (such as smart robots, hot air balloons, drones, airplanes), etc. The terminal device may also be other devices with terminal functions. For example, the terminal device may also be a device that functions as a terminal in D2D communications such as sidelink (SL) communications. In this application, terminal devices with wireless transceiver functions and chips that can be provided in the aforementioned terminal devices are collectively referred to as terminal devices.

[0091] (4) XR can include but is not limited to the following forms: AR, VR and MR.

[0092] Typically, XR services will periodically generate data frames at a certain frame rate, and the period of XR services may be non-integer. The period of the XR service is calculated based on the frame rate X. The frame rate can also be called the frame generation rate. The unit of the frame rate is the number of frames transmitted per second (fps). The period of the XR service is the reciprocal of the frame rate X. Typical values ​​of the frame rate X include 30fps, 60fps, 90fps, and 120fps. The following Table 1 shows the relationship between the period of the XR service and the frame rate X.

[0093] Table 1 Relationship between the XR service cycle and frame rate X

[0094] In this application, XR data may refer to data related to XR services.

[0095] XR data and services typically have high transmission latency requirements. For example, uplink AR services typically have a packet delay budget (PDB) of 30ms. This means the upper limit for the transmission delay between a data packet arriving at the access layer of a terminal device and reaching the N6 interface of the UPF is 30ms. If a data packet is not successfully transmitted within the PDB time limit, it is considered to have timed out and lost its function.

[0096] Alternatively, a packet set delay budget (PSDB) may also be considered for XR services. Similar to a PDB, PSDB defines the upper limit for the transmission delay of a PDU set (i.e., a group of data packets). For uplink XR services, PSDB refers to the time from the first packet in a PDU set arriving at the access layer of the terminal device to the last packet arriving at the N6 interface of the UPF. The opposite is true for downlink services.

[0097] (5) PDU set: A collection of multiple data packets in the transport layer, corresponding to the minimum granularity of data processing at the application layer. In some application scenarios, the application layer can only correctly parse the corresponding data unit after correctly receiving all the packets in a PDU set. In other application scenarios, the application layer can only parse the corresponding data unit after correctly receiving a certain percentage of the packets in the PDU set.

[0098] (6) Data burst: According to the 3GPP definition, a burst refers to a set of data PDUs generated and sent by an application in a very short period of time, such as an XR service frame. A data burst may contain one or more PDU sets.

[0099] Currently, for uplink XR services, in order to enable the base station to understand the latency consumption of data in the terminal device cache and complete data transmission before the PDB / PSDB is exhausted, the current 3GPP has reached a conclusion and introduced the concept of remaining time and a reporting mechanism in R18.

[0100] The remaining time refers to the remaining time that data can be used for air interface transmission. The data here can be a data packet or a collection of multiple data packets, such as a PDU set or a data burst. For example, assuming that the PDB of a data packet is 20ms, after the data packet arrives at the cache of the terminal device, it has not been transmitted after 5ms. At this time, the remaining time of the data packet is only 15ms, which means that the base station needs to schedule the data packet within 15ms to ensure its transmission. Alternatively, the remaining time can be determined based on the remaining duration of the data's discard timer. When the data arrives at the terminal device cache, the terminal device starts a discard timer for it. After the timer expires, the terminal device will discard the corresponding data. That is, data transmission must be completed before the discard timer expires. Usually, the length of the discard timer is equal to the PDB / PSDB of the data, so its remaining duration is equivalent to the remaining PDB / PSDB.

[0101] In order to enable the base station to understand the data demand and schedule it in time, the terminal device can report the remaining time information of the data in the cache to the base station. Specifically, the terminal device can send a MAC CE to the base station. The MAC CE explicitly or implicitly reflects the remaining time of part or all of the data in the terminal device cache, and reflects the data volume corresponding to a certain remaining time. Among them, the cache time may also be a time interval, for example, the terminal device reports the amount of data with a remaining time less than 10ms. The above MAC CE can be called DSR. Currently, 3GPP has the following conclusions on DSR: (1) When the remaining time of a PDU or PDU set in a logical channel group (LCG) is less than the threshold, DSR is triggered; (2) The above threshold is configured by the network for each LCG to the terminal device. After the terminal device triggers DSR, it can wait until uplink transmission resources are available and then send the MAC CE of DSR on the uplink transmission resources. However, the aforementioned DSR triggering conditions are unreasonable in practical applications. Once the remaining time of data falls below the threshold, the remaining time of this data remains below the threshold, meaning the DSR triggering condition is always met. This causes this data to repeatedly trigger the DSR, potentially wasting uplink transmission resources. For example, with an LCG threshold of 15ms, as shown in Figure 2, when the remaining time of PDU set #1 falls below 15ms, for example, to 14ms, the DSR triggering condition is met and the UE triggers a DSR. If the remaining time of PDU set #1 continues to decrease, for example, to 13ms, it still meets the threshold, and the UE will continue to trigger the DSR. For example, if the remaining time of PDU set #1 falls below 15ms, the remaining time of PDU set #1 remains below the threshold, causing repeated DSR triggering, resulting in a waste of uplink transmission resources.

[0102] The present application provides a cache status reporting method. On the terminal device side, this method can be executed by the terminal device or a component (such as a chip, circuit, etc.) used in the terminal device; on the network side, this method can be executed by the network device or a component (such as a chip, circuit, etc.) used in the network device. For ease of explanation, the following description uses the method executed by a terminal device and a network device as an example.

[0103] As shown in FIG3 , the cache status reporting method provided in the embodiment of the present application may include the following steps:

[0104] Step 301: When there is first data in the first LCH that meets a first condition, the terminal device triggers DSR.

[0105] Before step 301, the network device may also configure an LCH that can trigger DSR for the terminal device, for example, the network device sends first configuration information to the terminal device, the first configuration information is used to instruct the terminal device to trigger DSR when data in any LCH meets the first condition. In this case, the first LCH is any LCH that meets the first condition; or, the first configuration information includes at least one preset LCH, the first configuration information is used to instruct the terminal device to trigger DSR when data in at least one configured preset LCH meets the first condition. In this case, the first LCH is the LCH that meets the first condition in the configured at least one preset LCH; or, the first configuration information includes at least one preset LCG, the first configuration information is used to instruct the terminal device to trigger DSR when data in a certain LCH of at least one configured preset LCG meets the first condition. In this case, the first LCH is the LCH that meets the first condition in the configured at least one preset LCG. This application does not limit the specific implementation method of the first configuration information.

[0106] In an embodiment of the present application, the first data may be one or more data packets, or one or more data frames, or one or more data packet sets (PDU sets), or one or more data bursts (data bursts), and the present application does not impose any restrictions on this.

[0107] The first condition in step 301 may include the remaining time corresponding to the first data changing from being greater than or equal to the first threshold to being less than the first threshold, or the first condition may include the remaining time corresponding to the first data changing from being greater than the first threshold to being less than or equal to the first threshold. The following embodiments are described using the example of the first condition including the remaining time corresponding to the first data changing from being greater than or equal to the first threshold to being less than the first threshold, but the same applies to the case where the first condition includes the remaining time corresponding to the first data changing from being greater than the first threshold to being less than or equal to the first threshold.

[0108] The remaining time referred to in the embodiments of the present application may include any one or more of the following: remaining delay, remaining PDB, remaining PSDB, time / duration until expiration, time / duration until discard, and time / duration until discard timer expires. For example, the expiration time may also be the deadline. This application does not limit the concept, name, calculation process, or acquisition process of the remaining time.

[0109] For example, the data granularity of the first data is a data packet, and the first data may include a PDU. In this case, the remaining time corresponding to the first data may be the remaining PDB or the remaining PDU discard timer duration; for another example, the data granularity of the first data is a data set, and the first data may include a PDU set. In this case, the remaining time corresponding to the first data may be the remaining PSDB or the remaining PDU set discard timer duration.

[0110] Step 302: The terminal device sends a DSR to the network device.

[0111] In response, the network device receives the DSR.

[0112] Step 303: After sending the DSR, when the remaining time of the second data included in the first data in the first LCH is less than the first threshold, the DSR is not triggered.

[0113] Here, the second data may be part or all of the first data.

[0114] It should be understood that in step 303, when the remaining time of the second data included in the first data in the first LCH is less than the first threshold, the DSR is not triggered. This may occur after sending the DSR or after triggering the DSR. That is, although the remaining time of the second data included in the first data is less than the first threshold, the second data included in the first data has triggered the DSR and will no longer trigger the DSR.

[0115] The following describes the cache status reporting method by taking the example where the first condition in step 301 includes the remaining time corresponding to the first data changing from being greater than or equal to the first threshold to being less than the first threshold, in conjunction with FIG. 4 .

[0116] As shown in Figure 4, the first threshold is 15ms. The first LCH has PDU1, PDU2, PDU3 and PDU4. The corresponding remaining times at time t1 are 16ms, 17ms, 19ms and 20ms respectively. The corresponding remaining times at time t2 are 13ms, 14ms, 16ms and 17ms respectively. That is, at time t2, the remaining time of PDU1 and PDU2 changes from greater than 15ms to less than 15ms. If the first condition is met, DSR is triggered.

[0117] For example, at time t3, PDU1 in the first LCH has been sent. In addition to PDU2, PDU3, and PDU4, the first LCH also includes new data PDU5. The remaining times for PDU2, PDU3, PDU4, and PDU5 are 13ms, 15ms, 16ms, and 20ms, respectively. At this time, only the remaining time for PDU2 in the first LCH is less than 15ms. Since PDU2 has already triggered a DSR, no DSR is triggered at this time. Since there are no data packets in the first LCH that meet the first condition, no DSR is triggered at time t3.

[0118] In the above example, for the first data (for example, PDU2), if the remaining time corresponding to the PDU2 changes from greater than or equal to the first threshold to less than the first threshold, a DSR is triggered once. After that, the PDU2 is not sent out in the UE cache, and the remaining time corresponding to the PDU2 continues to decrease, that is, the remaining time corresponding to the PDU2 is always less than the first threshold, and the DSR is no longer triggered. In this way, PDU2 will only trigger the DSR once, which can avoid frequent triggering of the DSR, thereby reducing the consumption of uplink resources.

[0119] In an embodiment of the present application, the DSR may include the data volume and remaining time information corresponding to part or all of the data in the UE cache.

[0120] For example, taking the DSR sent by the terminal device including the data volume and remaining time information of PDU1 or PDU set1 as an example, the DSR can be a DSR triggered when the remaining time corresponding to the PDU1 or PDU set1 changes from greater than or equal to the first threshold to less than the first threshold; it can also be a DSR triggered when the remaining time corresponding to other PDUs or other PDU sets changes from greater than or equal to the first threshold to less than the first threshold, and the remaining time corresponding to the PDU1 or PDU set1 is greater than the first threshold, but the DSR MAC CE contains the data volume and remaining time information of the PDU1 or PDU set1.

[0121] There are many possible implementations of step 301 in the above embodiment.

[0122] Possible implementation method one, the first condition includes the remaining time corresponding to the first data changing from greater than or equal to the first threshold to less than the first threshold and any one of the following conditions 1.1 to 1.4. The above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold and any one of conditions 1.1, 1.2, 1.3, and 1.4 is met, the terminal device triggers DSR.

[0123] The following introduces conditions 1.1, 1.2, 1.3, and 1.4 respectively.

[0124] Condition 1.1: There is no data in the second LCH, and the second LCH is different from the first LCH.

[0125] Based on condition 1.1, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and there is no data in the second LCH, the terminal device triggers DSR.

[0126] Correspondingly, when the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, and there is data in the second LCH, the DSR is not triggered.

[0127] After the DSR is triggered, the MAC CE used to transmit the DSR consumes a certain amount of uplink resources, which may squeeze out resources for other data to be transmitted. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, if there is no data in LCHs other than the first LCH, the DSR is triggered and then sent to the network device. After the DSR is triggered once, if the remaining time corresponding to the first data continues to decrease and still meets the condition that the remaining time is less than the first threshold and there is no data in other LCHs, the DSR will not be triggered again. In other words, the first data only triggers the DSR once. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, if there is data in LCHs other than the first LCH (such as the second LCH), the DSR is not triggered, thereby ensuring that other data to be transmitted can be sent out first.

[0128] Condition 1.2: The second LCH does not contain data with a remaining time less than the first threshold. Data with a remaining time less than the first threshold can also be called urgent data.

[0129] Based on condition 1.2, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and there is no data in the second LCH with a remaining time less than the first threshold, the terminal device triggers DSR.

[0130] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the second LCH has data with a remaining time less than the first threshold, the DSR is not triggered.

[0131] Since the MAC CE used to transmit the DSR consumes a certain amount of uplink resources after the DSR is triggered, it may occupy resources for other data to be transmitted. If the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and if there is no data with a remaining time less than the first threshold (i.e., urgent data) in LCHs other than the first LCH, the DSR is triggered and then sent to the network device. Afterwards, even if the remaining time corresponding to the first data continues to decrease, if the remaining time is still less than the first threshold and there is no urgent data in other LCHs, the DSR will not be triggered again. In other words, the first data triggers the DSR only once. If the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, if there is data with a remaining time less than the first threshold (i.e., urgent data) in LCHs other than the first LCH (e.g., the second LCH), the DSR is not triggered, thereby ensuring that the urgent data can be sent out first.

[0132] Condition 1.3: The priority of the first LCH is higher than that of the third LCH, the third LCH contains data, and the third LCH is different from the first LCH.

[0133] Based on condition 1.3, step 301 can be implemented as follows: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the priority of the first LCH is higher than the priority of other LCHs containing data, the terminal device triggers a DSR. Data with a remaining time less than the first threshold can also be called urgent data.

[0134] Correspondingly, when the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, and the priority of the first LCH is lower than the priority of the third LCH, the DSR is not triggered.

[0135] After the DSR is triggered, the MAC CE used to transmit the DSR consumes a certain amount of uplink resources, which may squeeze out resources for other data to be transmitted. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, if the priority of the first LCH is higher than the priority of other LCHs with data, the DSR is triggered and then sent to the network device. Afterwards, even if the remaining time corresponding to the first data continues to decrease, as long as the remaining time is less than the first threshold and the priority of the first LCH is higher than the priority of other LCHs with data, the DSR will not be triggered again. In other words, the first data triggers the DSR only once. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, if there is data in other LCHs with higher priority (such as the third LCH), the DSR is not triggered, thereby ensuring that the higher priority data can be sent out first.

[0136] Condition 1.4: The priority of the first LCH is higher than that of the fourth LCH, the fourth LCH contains data with a remaining time less than a first threshold, and the fourth LCH is different from the first LCH.

[0137] Based on condition 1.4, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the priority of the first LCH is higher than the priority of other LCHs with data whose remaining time is less than the first threshold, the terminal device triggers DSR.

[0138] Correspondingly, when the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, and the priority of the first LCH is lower than the priority of the fourth LCH, the DSR is not triggered.

[0139] Because the MAC CE used to transmit the DSR consumes a certain amount of uplink resources after a DSR is triggered, it may occupy resources for other data to be transmitted. If the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and if the priority of the first LCH is higher than the priority of other LCHs containing data with a remaining time less than the first threshold, a DSR is triggered and then sent to the network device. Thereafter, even if the remaining time corresponding to the first data continues to decrease, if the remaining time is still less than the first threshold and the priority of the first LCH is higher than the priority of other LCHs containing data with a remaining time less than the first threshold, no further DSR is triggered. In other words, the first data triggers the DSR only once. If the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, if there is data with a remaining time less than the first threshold in another LCH with a higher priority (e.g., the fourth LCH) (data with a remaining time less than the first threshold is called urgent data), no DSR is triggered, thereby ensuring that the higher-priority urgent data is transmitted first.

[0140] In some other embodiments, the above step 301 can also be implemented in the following way: when there is emergency data in the first LCH that meets any one of conditions 1.5, 1.6, 1.7, 1.8, and 1.9, the terminal device triggers DSR.

[0141] The following introduces conditions 1.5, 1.6, 1.7, 1.8, and 1.9 respectively.

[0142] Condition 1.5: Urgent data becomes available, where the urgent data may be data whose remaining time is less than a first threshold.

[0143] Condition 1.6: urgent data becomes available and there is no data in the second LCH, which is different from the first LCH.

[0144] Condition 1.7: urgent data becomes available, and the second LCH does not contain data with a remaining time less than the first threshold, and the second LCH is different from the first LCH.

[0145] Condition 1.8: urgent data becomes available, the priority of the first LCH is higher than the priority of the third LCH, data exists in the third LCH, and the third LCH is different from the first LCH.

[0146] Condition 1.9: urgent data becomes available, the priority of the first LCH is higher than that of the fourth LCH, the fourth LCH has data with a remaining time less than the first threshold, and the fourth LCH is different from the first LCH.

[0147] In conditions 1.5 through 1.9 above, "emergency data becomes available" can be understood as meaning that the data can be sent. Specifically, the data has been processed by upper-layer protocols such as the SDAP, PDCP, and RLC layers before reaching the MAC layer, where it can be encapsulated into a MAC PDU and sent.

[0148] In any of the above embodiments, the threshold of the remaining time is set to one (i.e., the first threshold) as an example for introduction. In some other embodiments, the threshold of the remaining time can be set to multiple, for example, 15ms, 10ms, 5ms, wherein threshold 1 is greater than threshold 2, and threshold 2 is greater than threshold 3. For the first data, when the remaining time corresponding to the first data changes from greater than or equal to 15ms to less than 15ms, a DSR is triggered once; when the remaining time corresponding to the first data changes from greater than or equal to 10ms to less than 10ms, a DSR is triggered once; when the remaining time corresponding to the first data changes from greater than or equal to 5ms to less than 5ms, a DSR is triggered once. The case where the threshold value of the remaining time is set to multiple is also applicable to any of the possible implementation modes 2 to 6, and will not be described in detail below.

[0149] Possible implementation method two, the first condition includes the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold and any one of the following conditions 2.1 to condition 2.5. The above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold and any one of conditions 2.1, condition 2.2, condition 2.3, condition 2.4, and condition 2.5 is met, the terminal device triggers DSR.

[0150] Condition 2.1: The first data corresponds to a high importance.

[0151] Based on condition 2.1, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, the terminal device triggers DSR.

[0152] Correspondingly, when the remaining time corresponding to the first data changes from being greater than or equal to the first threshold to being less than the first threshold, and the importance corresponding to the first data is low, the DSR is not triggered.

[0153] When network congestion occurs, the network device may send a first indication message to the terminal device, where the first indication message is used to instruct the terminal device to trigger DSR for data of high importance first, or to instruct the terminal device to trigger DSR for data of high importance. Optionally, the first indication message is also used to instruct not to trigger DSR for data of low importance.

[0154] In XR services, data of varying importance may appear within the same data stream. This is due to the application's encoding method. For example, in XR video services, applications may use independent encoding for some video frames and inter-frame prediction for the remaining frames, thereby compressing the amount of data transmitted. The data generated by independent encoding contains complete information about the frame, and the receiver only needs to process this data to recover the complete video frame. However, the data generated by inter-frame prediction only contains partial information about the frame. In addition to processing this data, the receiver needs to combine data from other frames to recover the complete video frame. For example, in live broadcasts, the background typically remains unchanged. Therefore, only the complete data for the first frame is transmitted. Subsequent frames only transmit data related to changes in the foreground character, while background data is not transmitted. The receiving player must use the background data from the first frame to generate the images for subsequent frames. Obviously, in this way, the data using independent coding method is more important than the data using inter-frame prediction coding method, because this data not only affects the playback of this video frame, but also affects the playback of other video frames that are dependent on this video frame.

[0155] In one possible implementation, the terminal device can determine the importance of the data based on the PDU set importance (PSI) feature. Currently, 3GPP has agreed to introduce the concept of PSI to indicate the relative importance of a PDU set. PSI can take values ​​from 0 to 15, where a PSI value of 0 indicates the highest importance, a PSI value of 15 indicates the lowest importance, and so on. The application layer can add PSI information to the generated data so that the terminal device can understand the importance of the data. Specifically, the application layer adds a PSI with a value of 0 to 15 to the header of each data packet, and the terminal device determines the importance of the data by reading the PSI value in the data packet header.

[0156] For example, when the first data is a data packet or PDU, the terminal device reads the PSI of the data packet received from the application layer. When the PSI is less than a first threshold, the data packet is considered high-importance data; when the PSI is greater than or equal to the first threshold, the data packet is considered low-importance data. The first threshold can be determined by the terminal device itself or configured for the terminal device by a network device.

[0157] For example, when the first data is a PDU set, the terminal device reads the PSI of the data packet received from the application layer. When the PSI is less than the first threshold, the PDU set to which the data packet belongs is data of high importance; when the PSI is greater than or equal to the first threshold, the PDU set to which the data packet belongs is a data packet of low importance.

[0158] For example, when the first data is a data burst, the terminal device reads the PSI of the data packet received from the application layer. When the PSI is less than a first threshold, the data burst to which the data packet belongs is data of high importance; when the PSI is greater than or equal to the first threshold, the data burst to which the data packet belongs is data of low importance.

[0159] In another possible implementation, the terminal device determines the importance of the data based on its own implementation. For example, when the application layer does not provide PSI information or the terminal device cannot recognize PSI information, the terminal device can determine the importance of the data on its own.

[0160] For example, the terminal device can determine the importance of data based on its data volume. This is because highly important data often carries more application layer information and has a larger data payload.

[0161] For example, when the first data is a data burst, the terminal device calculates the amount of data in the received data burst. When the amount of data in the data burst is greater than or equal to a second threshold, the data burst is considered high-importance data; when the amount of data in the data burst is less than the second threshold, the data burst is considered low-importance data. The second threshold can be determined by the terminal device itself or configured for the terminal device by the network device.

[0162] For example, when the first data is a PDU set, the terminal device calculates the data size of the received PDU set. When the data size of the PDU set is greater than or equal to the second threshold, the PDU set is data of high importance; when the data size of the PDU set is less than the second threshold, the PDU set is data of low importance; or, the terminal device calculates the data size of the received data burst. When the data size of the data burst is greater than a certain value, the PDU set contained in the data burst is data of high importance; when the data size of the data burst is less than a certain value, the PDU set contained in the data burst is data of low importance.

[0163] For example, when the first data is a data packet or PDU, the terminal device calculates the data size of the received PDU set. When the data size of the PDU set is greater than the second threshold, the PDU contained in the PDU set is data of high importance; when the data size is less than the second threshold, the PDU contained in the PDU set is data of low importance; or, the terminal device calculates the data size of the received data burst. When the data size of the data burst is greater than the second threshold, the PDU contained in the data burst is data of high importance; when the data size of the data burst is less than the second threshold, the PDU contained in the data burst is data of low importance.

[0164] The terminal device may also determine the importance of data based on other implementation methods, such as machine learning or artificial intelligence, which is not limited in the present invention.

[0165] It should be understood that the method for determining the importance of data below can refer to the description in condition 2.1 and will not be repeated here.

[0166] Condition 2.2: The first data corresponds to a high importance, and the second LCH does not contain any data, and the second LCH is different from the first LCH.

[0167] Based on condition 2.2, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and there is no data in the second LCH, DSR is triggered.

[0168] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, the importance of the first data is low, and there is no data in the second LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, the importance of the first data is low, and there is data in the second LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, the importance of the first data is high, and there is data in the second LCH, the DSR is not triggered.

[0169] Condition 2.3: The first data has high importance, and the second LCH does not contain data with a remaining time less than the first threshold.

[0170] Based on condition 2.3, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and there is no data in the second LCH with a remaining time less than the first threshold, then DSR is triggered.

[0171] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the second LCH does not contain data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the second LCH contains data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is high, and the second LCH contains data with a remaining time less than the first threshold, the DSR is not triggered.

[0172] Condition 2.4: The first data has high importance, and the priority of the first LCH is higher than that of the third LCH. The third LCH has data, and the third LCH is different from the first LCH.

[0173] Based on condition 2.4, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and the priority of the first LCH is higher than the priority of the third LCH, DSR is triggered.

[0174] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is higher than the priority of the third LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is lower than the priority of the third LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is high, and the priority of the first LCH is lower than the priority of the third LCH, the DSR is not triggered.

[0175] Condition 2.5: The first data has high importance, and the priority of the first LCH is higher than that of the fourth LCH. The fourth LCH has data with a remaining time less than the first threshold, and the fourth LCH is different from the first LCH.

[0176] Based on condition 2.5, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and the priority of the first LCH is higher than the priority of the fourth LCH, DSR is triggered.

[0177] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is higher than the priority of the fourth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is lower than the priority of the fourth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is high, and the priority of the first LCH is lower than the priority of the fourth LCH, the DSR is not triggered.

[0178] Possible implementation method three, the first condition includes the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold and any one of the following conditions 3.1 to 3.4, that is, when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold and any one of conditions 3.1, 3.2, 3.3 and 3.4 is met, the terminal device triggers DSR.

[0179] Condition 3.1: The first data corresponds to a high importance, and the second LCH does not contain any high-importance data, and the second LCH is different from the first LCH.

[0180] Based on condition 3.1, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and there is no data of high importance in the second LCH, DSR is triggered.

[0181] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the first data has low importance, and there is no high-importance data in the second LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the first data has low importance, and there is high-importance data in the second LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the first data has high importance, and there is high-importance data in the second LCH, the DSR is not triggered.

[0182] Condition 3.2: The first data corresponds to high importance, and the second LCH does not contain high-importance data with a remaining time less than the first threshold, and the second LCH is different from the first LCH.

[0183] Based on condition 3.2, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and there is no high-importance data with a remaining time less than the first threshold in the second LCH, then DSR is triggered.

[0184] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the first data has low importance, and the second LCH does not contain high-importance data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the first data has low importance, and the second LCH contains high-importance data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the first data has high importance, and the second LCH contains high-importance data with a remaining time less than the first threshold, the DSR is not triggered.

[0185] Condition 3.3: The first data corresponds to a high importance, and the priority of the first LCH is higher than the priority of the fifth LCH. The fifth LCH contains data of high importance, and the fifth LCH is different from the first LCH.

[0186] Based on condition 3.3, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and the priority of the first LCH is higher than the priority of the fifth LCH, DSR is triggered.

[0187] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is higher than the priority of the fifth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is lower than the priority of the fifth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is high, and the priority of the first LCH is lower than the priority of the fifth LCH, the DSR is not triggered.

[0188] Condition 3.4: The first data corresponds to high importance, and the priority of the first LCH is higher than that of the sixth LCH. The sixth LCH has data with a remaining time less than the first threshold and high importance, and the sixth LCH is different from the first LCH.

[0189] Based on condition 3.4, the above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the importance corresponding to the first data is high, and the priority of the first LCH is higher than the priority of the sixth LCH, DSR is triggered.

[0190] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is higher than the priority of the sixth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is low, and the priority of the first LCH is lower than the priority of the sixth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the corresponding importance of the first data is high, and the priority of the first LCH is lower than the priority of the sixth LCH, the DSR is not triggered.

[0191] In a fourth possible implementation, the first condition includes the remaining time corresponding to the first data changing from greater than or equal to the first threshold to less than the first threshold and any one of the following conditions 4.1 to 4.4. That is, when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and any one of conditions 4.1, 4.2, 4.3, and 4.4 is met, the terminal device triggers a DSR. In this fourth possible implementation, the first data may include one or more data, and the first data does not include data that has already triggered a DSR.

[0192] The following introduces conditions 4.1, 4.2, 4.3, and 4.4 respectively.

[0193] Condition 4.1: The data volume corresponding to the first data is greater than or equal to the second threshold.

[0194] Based on condition 4.1, the first condition includes: the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold. The above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, the terminal device triggers DSR. Correspondingly, when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, the terminal device does not trigger DSR.

[0195] The first data may include one or more data. When the first data includes multiple data, the remaining time corresponding to the first data changes from being greater than or equal to a first threshold to being less than the first threshold, including: the remaining time corresponding to the first portion of the multiple data included in the first data all changes from being greater than or equal to the first threshold to being less than the first threshold, and the remaining time corresponding to the second portion of the multiple data included in the first data all is less than the first threshold. The first portion of data and the second portion of data constitute the multiple data.

[0196] In an embodiment of the present application, for each LCH or LCG that can trigger DSR, the terminal device can maintain an emergency data volume. Taking the emergency data volume maintained for the first LCH as an example, the initial value of the emergency data volume corresponding to the first LCH is set to 0. Whenever the remaining time of data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, the data volume of the data whose remaining time changes from greater than or equal to the first threshold to less than the first threshold is added to the emergency data volume. In this way, the first condition based on condition 4.1 can be understood as: the emergency data volume corresponding to the first LCH is greater than or equal to the second threshold, wherein the emergency data volume corresponding to the first LCH includes the data volume corresponding to the data whose remaining time in the first LCH changes from greater than or equal to the first threshold to less than the first threshold. The above step 301 can be implemented in the following way: when the emergency data volume corresponding to the first LCH is greater than or equal to the second threshold, DSR is triggered. And after DSR is triggered, the emergency data volume corresponding to the first LCH is reset (or updated) to 0. Correspondingly, when the emergency data volume corresponding to the first LCH is less than the second threshold, DSR is not triggered.

[0197] In one possible implementation, the terminal device can reset (or update) the amount of emergency data corresponding to the first LCH to 0 after sending the DSR. Because the DSR is not sent immediately after being triggered, it needs to wait until uplink resources are available before it can be sent. Therefore, the amount of emergency data can be reset to 0 after the DSR is sent.

[0198] For example, taking the data granularity that triggers DSR as PDU set and the second threshold as 5000 bytes, the data volume of PDU set1 is 3000 bytes, the data volume of PDU set2 is 3000 bytes, the data volume of PDU set3 is 2500 bytes, and the data volume of PDU set4 is 3000 bytes.

[0199] At time t1, the remaining time corresponding to PDU set1 changes from greater than or equal to the first threshold to less than the first threshold, while the remaining time corresponding to PDU set2 and PDU set3 is still greater than the first threshold. At this time, the emergency data volume includes the data volume of PDU set1, that is, 3000 bytes. At time t2, the remaining time corresponding to PDU set2 changes from greater than or equal to the first threshold to less than the first threshold. Time t2 is a time after time t1. At this time, the data volume of PDU set2 is added to the emergency data volume. At this time, the emergency data volume includes the data volume of PDU set1 whose remaining time is less than the first threshold and the data volume of PDU set2 whose remaining time changes from greater than or equal to the first threshold to less than the first threshold, that is, the emergency data volume is 5000 bytes. At this time, the emergency data volume meets or equals the second threshold, triggering a DSR. The emergency data volume is then reset to 0.

[0200] After the emergency data volume is reset to 0, at time t3, the remaining time corresponding to PDU set 3 changes from greater than or equal to the first threshold to less than the first threshold. The data volume of PDU set 3 is added to the emergency data volume. That is, the emergency data volume now includes the data volume of PDU set 3, which is 2500 bytes. At time t4, the remaining time corresponding to PDU set 4 changes from greater than or equal to the first threshold to less than the first threshold. The data volume of PDU set 4 is added to the emergency data volume. That is, the emergency data volume now includes the data volume of PDU set 3 and the data volume of PDU set 4, which is 5500 bytes. At this time, the emergency data volume meets the second threshold, triggering a DSR. The emergency data volume is then reset to 0.

[0201] In a possible implementation, the amount of emergency data may be maintained by one or more of the PDCP layer, the RLC layer, and the MAC layer of the terminal device. For example, when the PDCP layer finds that the remaining time of data in the PDCP entity corresponding to the first LCH changes from greater than or equal to the first threshold to less than the first threshold, the PDCP layer indicates to the MAC layer the amount of data whose remaining time changes from greater than or equal to the first threshold to less than the first threshold; when the RLC layer finds that the remaining time of data in the RLC entity corresponding to the first LCH changes from greater than or equal to the first threshold to less than the first threshold, the RLC layer indicates to the MAC layer the amount of data whose remaining time changes from greater than or equal to the first threshold to less than the first threshold; and the MAC layer uses the sum of the amounts of data indicated by the PDCP layer and the RLC layer as the amount of emergency data for the first LCH.

[0202] The second threshold involved in the embodiment of the present application is pre-set (for example, defined by the protocol) or indicated by the network device to the terminal device. When the value of the second threshold is 0, the cache status reporting method implemented based on the condition 3.1 is consistent with the effect of the cache status reporting method implemented based on the first condition in the above step 301. When the value of the second threshold is greater than 0, the cache status reporting method implemented based on the condition 3.1 can effectively reduce the frequency of triggering DSR compared to the cache status reporting method implemented based on the first condition in the above step 301, and can avoid triggering DSR too frequently, thereby reducing network resource overhead. The relevant content of the second threshold will not be repeated in the following text.

[0203] The following describes the cases where the second threshold is 0 and greater than 0 with reference to FIG. 5 .

[0204] As shown in Figure 5, PDU sets #1 to 4 arrive at the cache of the terminal device one after another. Assuming that the arrival time of PDU set #1 is T1, the arrival time of PDU set #2 is T2, the arrival time of PDU set #3 is T3, and the arrival time of PDU set #4 is T4, and assuming that the PSDB of PDU sets #1 to 4 is 20ms and the remaining time threshold (i.e., the first threshold mentioned above) is 15ms, then according to the scheme of the embodiment shown in Figure 3 above, or according to the scheme in which the emergency data volume threshold (i.e., the second threshold) is 0, the UE needs to trigger DSR at T1-5ms, T2-5ms, T3-5ms, and T4-5ms respectively, which may consume four uplink resources. However, the arrival time of PDU sets #1 to 4 at the cache of the terminal device is very close, for example, if PDU sets #1 to 4 belong to the same data burst, then it is unnecessary to trigger DSR frequently. For example, when T1-5ms, the UE reports that the data volume with the remaining time less than 15ms is 3000 bytes (PDU set#1), and when T2-5ms, it reports that the data volume with the remaining time less than 15ms is 5000 bytes (PDU set#1+PDU set#2). The difference between T1 and T2 does not exceed 1ms, and there is a lot of duplication in the information reported twice.

[0205] By setting the emergency data volume threshold to a value greater than 0, the triggering frequency of DSR can be effectively reduced. For example, as shown in Figure 5, the emergency data volume threshold size can accommodate 5 data packets. The terminal device only needs to trigger DSR once at T2-5ms and once at T4-5ms, for a total of two DSR triggers, thereby significantly reducing the consumption of uplink resources by DSR.

[0206] Condition 4.2: The data volume corresponding to the first data is greater than or equal to the second threshold and any one of the above conditions 1.1 to 1.4.

[0207] Based on condition 4.2, the first condition includes: the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and any one of conditions 1.1 to 1.4 above. Step 301 above can be implemented in any of the following ways:

[0208] Method 1: When the remaining time corresponding to one or more data included in the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and there is no data in the second LCH, the terminal device triggers a DSR. The second LCH is different from the first LCH.

[0209] With reference to the above condition 4.1, the terminal device maintains the amount of emergency data for each LCH or LCG. The above step 301 can be implemented in the following manner: when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold and there is no data in the second LCH, the DSR is triggered. Correspondingly, when the amount of emergency data corresponding to the first LCH is less than the second threshold and there is no data in the second LCH, the DSR is not triggered. Alternatively, when the amount of emergency data corresponding to the first LCH is less than the second threshold and there is data in the second LCH, the DSR is not triggered. Alternatively, when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold and there is data in the second LCH, the DSR is not triggered.

[0210] Method 2: When the remaining time corresponding to one or more data included in the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and there is no data with a remaining time less than the first threshold in the second LCH, the terminal device triggers DSR.

[0211] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the second LCH contains data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and the second LCH contains data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and the second LCH does not contain data with a remaining time less than the first threshold, the DSR is not triggered.

[0212] With reference to the above condition 4.1, the terminal device maintains the amount of emergency data for each LCH or LCG. The above step 301 can be implemented in the following manner: when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold, and the second LCH does not contain data with a remaining time less than the first threshold, the DSR is triggered. Correspondingly, when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold, and the second LCH contains data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the amount of emergency data corresponding to the first LCH is less than the second threshold, and the second LCH does not contain data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the amount of emergency data corresponding to the first LCH is less than the second threshold, and the second LCH does not contain data with a remaining time less than the first threshold, the DSR is not triggered. Alternatively, when the amount of emergency data corresponding to the first LCH is less than the second threshold, and the second LCH contains data with a remaining time less than the first threshold, the DSR is not triggered.

[0213] Method three: when the remaining time corresponding to one or more data included in the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the priority of the first LCH is higher than the priority of the third LCH, the terminal device triggers DSR, wherein there is data in the third LCH and the third LCH is different from the first LCH.

[0214] Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the priority of the first LCH is lower than the priority of the third LCH, the DSR is not triggered. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and the priority of the first LCH is lower than the priority of the third LCH, the DSR is not triggered. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and the priority of the first LCH is higher than the priority of the third LCH, the DSR is not triggered.

[0215] With reference to the above condition 4.1, the terminal device maintains the amount of emergency data for each LCH or LCG. The above step 301 can be implemented in the following manner: when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold, and the priority of the first LCH is higher than the priority of the third LCH, the DSR is triggered. Correspondingly, when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold, and the priority of the first LCH is lower than the priority of the third LCH, the DSR is not triggered. When the amount of emergency data corresponding to the first LCH is less than the second threshold, and the priority of the first LCH is higher or lower than the priority of the third LCH, the DSR is not triggered.

[0216] Method four: when the remaining time corresponding to one or more data included in the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the priority of the first LCH is higher than the priority of the fourth LCH, the terminal device triggers DSR, wherein the fourth LCH contains data with a remaining time less than the first threshold, and the fourth LCH is different from the first LCH.

[0217] Correspondingly, when the remaining time corresponding to one or more data included in the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the priority of the first LCH is lower than the priority of the fourth LCH, the DSR is not triggered. Alternatively, when the remaining time corresponding to one or more data included in the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and the priority of the first LCH is lower than or higher than the priority of the fourth LCH, the DSR is not triggered.

[0218] With reference to the above condition 4.1, the terminal device maintains the amount of emergency data for each LCH or LCG. The above step 301 can be implemented in the following manner: when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold, and the priority of the first LCH is higher than the priority of the fourth LCH, the DSR is triggered. Correspondingly, when the amount of emergency data corresponding to the first LCH is less than the second threshold, and the priority of the first LCH is higher or lower than the priority of the fourth LCH, the DSR is not triggered. Alternatively, when the amount of emergency data corresponding to the first LCH is greater than or equal to the second threshold, and the priority of the first LCH is lower than the priority of the fourth LCH, the DSR is not triggered.

[0219] Condition 4.3: The data volume corresponding to the first data is greater than or equal to the second threshold and any one of the above conditions 2.1 to 2.5.

[0220] Based on condition 4.3, the first condition includes: the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and any one of the above conditions 2.1 to 2.5. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the first data meets any one of the above conditions 2.1 to 2.5, DSR is triggered. When the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and / or the first data does not meet any one of the above conditions 2.1 to 2.5, DSR is not triggered.

[0221] In some other implementations, the terminal device may maintain an emergency data volume for each LCH or LCG. The specific implementation of the emergency data volume can refer to the relevant description of the emergency data volume in the above condition 4.1. In conjunction with the emergency data volume, the first condition may include: the emergency data volume corresponding to the first LCH is greater than or equal to the second threshold and meets any one of the above conditions 2.1 to 2.5.

[0222] Condition 4.4: The data volume corresponding to the first data is greater than or equal to the second threshold and any one of the above conditions 3.1 to 3.5.

[0223] Based on condition 4.4, the first condition includes: the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and any one of the above conditions 3.1 to 3.5. The above step 301 can be implemented as follows: when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is greater than or equal to the second threshold, and the first data meets any one of the above conditions 3.1 to 3.5, DSR is triggered. Correspondingly, when the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the data volume corresponding to the first data is less than the second threshold, and / or the first data does not meet any one of the above conditions 3.1 to 3.5, DSR is not triggered.

[0224] In some other implementations, the terminal device may maintain an emergency data volume for each LCH or LCG. The specific implementation of the emergency data volume can refer to the description of the emergency data volume in condition 4.1 above. In conjunction with the emergency data volume, the first condition may include: the emergency data volume corresponding to the first LCH is greater than or equal to the second threshold and satisfies any of conditions 3.1 to 3.5 above. Step 301 above may be implemented as follows: When the emergency data volume corresponding to the first LCH is greater than or equal to the second threshold and satisfies any of conditions 3.1 to 3.5 above, a DSR is triggered. Correspondingly, when the emergency data volume corresponding to the first LCH is greater than or equal to the second threshold and does not satisfy any of conditions 3.1 to 3.5 above, a DSR is not triggered. Alternatively, when the emergency data volume corresponding to the first LCH is less than the second threshold and satisfies any of conditions 3.1 to 3.5 above, a DSR is not triggered. Alternatively, when the emergency data volume corresponding to the first LCH is less than the second threshold and does not satisfy any of conditions 3.1 to 3.5 above, a DSR is not triggered.

[0225] In the above-mentioned fourth embodiment, the example of setting the emergency data volume threshold to one (i.e., the second threshold) is used for introduction. In some other embodiments, when multiple remaining time thresholds are set, multiple corresponding emergency data volume thresholds can also be set, and the multiple emergency data volume thresholds can be the same or different. For example, for a larger remaining time threshold, a larger emergency data volume threshold can be used to avoid frequent triggering of DSR, while for a smaller remaining time threshold, a smaller or even 0 emergency data volume threshold is used to avoid data timeout due to long-term non-triggering of DSR. The emergency data volumes corresponding to the multiple thresholds are maintained separately and trigger DSR independently.

[0226] In the above possible implementation modes one to four, the UE needs to monitor the remaining time of each data, which places high requirements on the storage or processing overhead of the UE. Possible implementation modes five and six are provided below. By recording the data that has triggered the DSR to ensure that these PDUs or PDU sets no longer trigger the DSR, the storage or processing overhead requirements for the UE can be reduced.

[0227] Possible implementation method five, the terminal device can maintain a flag bit for each data, and the data granularity of the flag bit can be a data packet, or a PDU set, or a data burst, which is not limited here. The first condition includes: the remaining time corresponding to the first data changes from greater than or equal to the first threshold to less than the first threshold, and the flag bit corresponding to the first data is a first value, and the first value is used to indicate that the first data has not triggered DSR. The above step 301 can be implemented in the following way: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the flag bit corresponding to the first data is the first value, DSR is triggered. Afterwards, the terminal device sends the DSR to the network device.

[0228] In some embodiments, after the terminal device triggers the delay status report DSR, the terminal device may also update the flag bit corresponding to the first data to a second value, and the second value is used to indicate that the first data has triggered the DSR. In other embodiments, the terminal device may update the flag bit corresponding to the first data to a second value after sending the DSR, because the DSR is not sent immediately after being triggered, and it is necessary to wait until uplink resources are available before sending it. Therefore, the flag bit may be updated to the second value after the DSR is actually sent. After the flag bit corresponding to the first data is the second value, although the remaining time corresponding to the first data is less than the first threshold, the DSR is no longer triggered. This ensures that one data only triggers the DSR once.

[0229] In some embodiments, the first condition can be modified to: the remaining time corresponding to the first data is less than the first threshold, and the flag bit corresponding to the first data is the first value. It should be understood that in this way, the effect achieved is consistent with that of embodiment 5, but the terminal device does not need to determine when the remaining time of the first data changes from being greater than or equal to the first threshold to being less than the first threshold.

[0230] For example, the flag is recorded as DSR-flag, and the first value and the second value can be set to 0 and 1 respectively. For example, the first value is set to 0, indicating that DSR has not been triggered; the second value is set to 1, indicating that DSR has been triggered, that is, initially, DSR-flag is 0. Taking the data granularity of one PDU as an example, as shown in Figure 6, the initial DSR-flag of PDU1, PDU2, PDU3, and PDU4 is 0. When the remaining time of PDU1 and PDU2 at time t1 is less than the first threshold and the DSR-flag corresponding to PDU1 and PDU2 is equal to 0, DSR is triggered. Afterwards, the DSR-flag corresponding to PDU1 and PDU2 is updated to 1. At this time, only the DSR-flag corresponding to PDU3 and PDU4 is equal to 0. In other words, only PDU3 and PDU4 can trigger DSR, and PDU1 and PDU2 no longer trigger DSR.

[0231] In some other embodiments, the first value may be set to 1, indicating that DSR has not been triggered; and the second value may be set to 0, indicating that DSR has been triggered, that is, initially, DSR-flag is 1. Taking the data granularity of one PDU as an example, when the remaining time of a PDU is less than the first threshold and the DSR-flag corresponding to the PDU is equal to 1, DSR is triggered. Thereafter, the DSR-flag corresponding to the PDU is set to 0, and DSR is no longer triggered for PDUs with DSR-flag 0.

[0232] In some other embodiments, when multiple remaining time thresholds are set, multiple DSR-flags may also be set accordingly. The DSR-flags corresponding to the multiple remaining time thresholds are maintained separately and trigger DSR independently.

[0233] In the fifth embodiment described above, the terminal device needs to maintain a state variable for each data. The following provides a method that only needs to maintain one variable, namely the DSR sequence number (DSR-SN), which represents the sequence number (SN) of the last data that triggered the DSR. The sequence number of the data entering the cache of the terminal device is incremented from small to large according to the sequence number, and the remaining time corresponding to the data that enters the cache first is always less than the remaining time corresponding to the data that enters the cache later. Therefore, there is a sequence number, and the remaining time corresponding to the data before this sequence number is less than the first threshold, and the DSR has been triggered. The remaining time corresponding to the data after this sequence number is greater than the first threshold, and the DSR has not been triggered. The DSR sequence number is used to record this sequence number, that is, the DSR sequence number can be the maximum sequence number corresponding to the data that has triggered the DSR.

[0234] In a sixth possible implementation, the first condition includes: the remaining time corresponding to the first data changes from greater than or equal to a first threshold to less than the first threshold, and the sequence number corresponding to the first data is greater than the DSR sequence number. Step 301 can be implemented as follows: when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the sequence number corresponding to the first data is greater than the DSR sequence number, triggering a DSR. Thereafter, the terminal device sends the DSR to the network device.

[0235] In some embodiments, after the terminal device triggers a delay status report DSR, the terminal device may also update the DSR sequence number to the sequence number corresponding to the first data. In other embodiments, the terminal device may update the DSR sequence number corresponding to the first data after sending the DSR, and may update it to the maximum sequence number of the data (e.g., PDU or PDU set) contained in the amount of data whose remaining time in the DSR MAC CE is less than a threshold.

[0236] In other embodiments, the terminal device may also assign the serial number of the last data that triggers DSR plus 1 to the DSR sequence number. In this case, DSR-SN represents the serial number of the next data that can trigger DSR.

[0237] Correspondingly, when the remaining time corresponding to the first data in the first LCH changes from greater than or equal to the first threshold to less than the first threshold, and the sequence number corresponding to the first data is less than the DSR sequence number, the DSR is not triggered.

[0238] In some embodiments, the first condition can be modified to: the remaining time corresponding to the first data is less than the first threshold, and the corresponding sequence number is greater than the DSR sequence number. It should be understood that in this way, the effect achieved is consistent with that of embodiment 6, but the terminal device does not need to determine when the remaining time of the first data changes from greater than or equal to the first threshold to less than the first threshold.

[0239] For example, taking the data granularity of one PDU as an example, as shown in Figure 7, the serial numbers corresponding to PDU1, PDU2, PDU3, and PDU4 are 1, 2, 3, and 4 respectively. When the DSR sequence number is 2 at time t1, it means that PDU1 and PDU2 have triggered DSR, and the data packet with the largest serial number among the data packets that have triggered DSR is PDU2. After that, only PDU3 and PDU4 with serial numbers greater than the DSR serial number can trigger DSR, and PDU1 and PDU2 no longer trigger DSR.

[0240] In some other embodiments, when multiple remaining time thresholds are set, multiple DSR-SNs may also be set accordingly. The DSR-SNs corresponding to the multiple remaining time thresholds are maintained separately and trigger DSR independently.

[0241] Through the above-mentioned possible implementation method six, the terminal device does not need to pay attention to the remaining time of all data at all times, and can also ensure that each data triggers DSR only once, thereby avoiding the data meeting the remaining time threshold requirements for a long time, resulting in a large number of repeated DSRs, which can reduce the consumption of uplink resources.

[0242] The present application also provides another cache status reporting method. On the terminal device side, this method can be executed by the terminal device or a component (such as a chip, circuit, etc.) used in the terminal device; on the network side, it can be executed by the network device or a component (such as a chip, circuit, etc.) used in the network device. For ease of explanation, the following description uses the terminal device and the network device executing this method as an example.

[0243] As shown in FIG8 , the cache status reporting method provided in the embodiment of the present application may include the following steps:

[0244] Step 801: The terminal device periodically triggers DSR for the first LCH.

[0245] In one possible implementation, for an LCH or LCG, whenever a DSR is triggered, the terminal device may start a periodic timer whose duration is equal to the period. When the periodic timer expires, a DSR is triggered. The period may be the arrival period of uplink data within the LCH or LCG. The period may be determined by the terminal device itself or configured by the network device.

[0246] In the case where the period is configured by the network device to the terminal device, the terminal device may also receive first configuration information sent by the network device, where the first configuration information is used to indicate the period for triggering DSR corresponding to the first LCH.

[0247] In a possible implementation, after the terminal device receives the first configuration information, the terminal device determines the timing of triggering the DSR for the first time by itself, and then periodically triggers the DSR according to the period indicated in the first configuration information.

[0248] In another possible implementation, after the terminal device receives the first configuration information, the terminal device triggers the first DSR according to any one of the aforementioned implementations one to six, and then periodically triggers the DSR according to the period indicated in the first configuration information.

[0249] In another possible implementation, the first configuration information is also used to indicate the timing when the terminal device triggers DSR for the first time. That is, the terminal device can trigger the first DSR according to the timing of the first triggering of DSR indicated by the first configuration information, and then periodically trigger DSR according to the period indicated in the first configuration information.

[0250] For example, for an LCH or LCG, the network device may configure a starting offset and a period to the terminal device through a radio resource control (RRC) message, where the starting offset is used to indicate the timing of the first DSR triggering for the LCH or LCG. The starting offset may be in the form of the system frame number, subframe number, time slot number, or symbol number offset backward from the system frame number #0 (SFN) as the reference point.

[0251] In another possible implementation, the terminal device further receives downlink control information (DCI), which is used to indicate the timing of the first DSR triggering by the terminal device. The terminal device may trigger the first DSR according to the timing of the first DSR triggering indicated by the DCI, and then periodically trigger the DSR according to the period indicated in the first configuration information.

[0252] For example, for an LCH or LCG, the network may first configure a period through an RRC message, but without indicating the DSR starting position. Afterwards, the network sends a DCI, and the UE immediately triggers a DSR upon receiving the DCI, and then triggers subsequent DSRs according to the period configuration.

[0253] Step 802: The terminal device periodically sends a DSR to the network device.

[0254] The embodiment shown in FIG8 above can be applied to periodic service scenarios, such as XR service scenarios. Since XR data generally arrives at the cache of the terminal device periodically, and the data in each period all arrives at the UE cache in a short time, which is called a data burst, the remaining time corresponding to the data in a data burst is always close. By periodically triggering DSR, as shown in FIG9, a DSR can be periodically triggered for each data burst, which can avoid unnecessary DSR triggering and sending, thereby saving network resources.

[0255] It is understood that, in order to implement the functions in the above embodiments, the base station and the terminal include hardware structures and / or software modules corresponding to the execution of each function. Those skilled in the art should readily appreciate that, in conjunction with the units and method steps of the various examples described in the embodiments disclosed in this application, this application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in hardware or in a computer software-driven hardware manner depends on the specific application scenario and design constraints of the technical solution.

[0256] The following is a schematic diagram of the structure of possible communication devices provided in the embodiments of the present application. These communication devices can be used to implement the functions of the terminal device or network device in the above method embodiments, and thus can also achieve the beneficial effects possessed by the above method embodiments.

[0257] As shown in Figure 10, the communication device 1000 includes a processing unit 1001 and a communication unit 1002. The communication device 1000 is used to implement the functions of the terminal device / network device in the method embodiment shown in Figure 3 or Figure 8 above.

[0258] When the communication device 1000 is used to implement the functions of the terminal device in the method embodiment shown in Figure 3: the processing unit 1001 is used to execute steps 301 and 303; the communication unit 1002 is used to execute step 302.

[0259] When the communication apparatus 1000 is used to implement the function of the terminal device in the method embodiment shown in FIG8 : the processing unit 1001 is used to execute step 801 ; the communication unit 1002 is used to execute step 802 .

[0260] A more detailed description of the processing unit 1001 and the communication unit 1002 can be directly obtained by referring to the relevant description in the method embodiment shown in FIG3 or FIG8 , and is not repeated here.

[0261] It should be understood that the division of units in the above device is merely a division of logical functions. In actual implementation, they can be fully or partially integrated into one physical entity, or physically separated. Moreover, the units in the device can all be implemented in the form of software called through processing elements; or all be implemented in the form of hardware; or some units can be implemented in the form of software called through processing elements, and some units can be implemented in the form of hardware. For example, each unit can be a separately established processing element, or it can be integrated into a certain chip of the device. In addition, it can also be stored in the form of a program in a memory, called by a certain processing element of the device and execute the function of the unit. In addition, all or part of these units can be integrated together, or they can be implemented independently. The processing element here can also be a processor, which can be an integrated circuit with signal processing capabilities. In the implementation process, each operation of the above method or each unit above can be implemented by the integrated logic circuit of the hardware in the processor element or by software called through the processing element.

[0262] In one example, the unit in any of the above devices may be one or more integrated circuits configured to implement the above method, such as one or more application specific integrated circuits (ASICs), one or more digital singnal processors (DSPs), one or more field programmable gate arrays (FPGAs), or a combination of at least two of these integrated circuit forms. For another example, when the unit in the device can be implemented in the form of a processing element scheduler, the processing element can be a processor, such as a general-purpose central processing unit (CPU), or other processor that can call a program. For another example, these units can be integrated together and implemented in the form of a system-on-a-chip (SOC).

[0263] The above-mentioned receiving unit is an interface circuit of the device, which is used to receive signals from other devices. For example, when the device is implemented as a chip, the receiving unit is the interface circuit of the chip used to receive signals from other chips or devices. The above-mentioned sending unit is an interface circuit of the device, which is used to send signals to other devices. For example, when the device is implemented as a chip, the sending unit is the interface circuit of the chip used to send signals to other chips or devices.

[0264] As another possible product form, the terminal device or network device of the embodiment of the present application can be implemented by a general bus architecture. For ease of explanation, refer to Figure 11, which is a structural diagram of a communication device 1100 provided in an embodiment of the present application, and the communication device 1100 includes a processor 1101 and a transceiver 1102. The communication device 1100 can be a terminal device, or a chip or chip system therein; or, the communication device 1100 can be a network device, or a chip or module therein. Figure 11 only shows the main components of the communication device 1100. In addition to the processor 1101 and the transceiver 1102, the communication device 1100 can further include a memory 1103, and an input and output device (not shown in the figure).

[0265] Optionally, the processor 1101 is primarily used to process communication protocols and communication data, as well as control the entire communication device, execute software programs, and process software program data. The memory 1103 is primarily used to store software programs and data. The transceiver 1102 may include a radio frequency circuit and an antenna. The radio frequency circuit is primarily used to convert baseband signals into radio frequency signals and process radio frequency signals. The antenna is primarily used to transmit and receive radio frequency signals in the form of electromagnetic waves. Input and output devices, such as a touch screen, display, and keyboard, are primarily used to receive user input and output data to the user.

[0266] Optionally, the processor 1101 , the transceiver 1102 , and the memory 1103 may be connected via a communication bus.

[0267] When the communication device is powered on, the processor 1101 can read the software program in the memory 1103, interpret and execute the instructions of the software program, and process the data of the software program. When data needs to be sent wirelessly, the processor 1101 performs baseband processing on the data to be sent and outputs the baseband signal to the radio frequency circuit. The radio frequency circuit performs radio frequency processing on the baseband signal and then transmits the radio frequency signal to the outside in the form of electromagnetic waves through the antenna. When data is sent to the communication device, the radio frequency circuit receives the radio frequency signal through the antenna, converts the radio frequency signal into a baseband signal, and outputs the baseband signal to the processor 1101. The processor 1101 converts the baseband signal into data and processes the data.

[0268] In another implementation, the RF circuit and antenna may be provided independently of the processor performing baseband processing. For example, in a distributed scenario, the RF circuit and antenna may be remotely located independent of the communication device.

[0269] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the above-mentioned communication device may take the form of the communication device 1100 shown in FIG. 11 .

[0270] As an example, the functions / implementation process of the processing unit 1001 in FIG10 may be implemented by the processor 1101 in the communication device 1100 shown in FIG11 calling computer-executable instructions stored in the memory 1103. The functions / implementation process of the communication unit 1002 in FIG10 may be implemented by the transceiver 1102 in the communication device 1100 shown in FIG11.

[0271] As another possible product form, the terminal device or network device in the present application may adopt the structure shown in Figure 12, or include the components shown in Figure 12. Figure 12 is a schematic diagram of the structure of a communication device 1200 provided in the present application.

[0272] As shown in FIG12 , the communication device 1200 includes at least one processor 1201. Optionally, the communication device further includes a communication interface 1202.

[0273] When the program instructions are executed in the at least one processor 1201, the apparatus 1200 may implement the method provided in any of the aforementioned embodiments and any possible designs thereof. Alternatively, the processor 1201 may implement the method provided in any of the aforementioned embodiments and any possible designs thereof through logic circuits or by executing code instructions.

[0274] The communication interface 1202 can be used to receive program instructions and transmit them to the processor. Alternatively, the communication interface 1202 can be used for the communication device 1200 to communicate with other communication devices, such as exchanging control signaling and / or service data. Exemplarily, the communication interface 1202 can be used to receive signals from devices other than the communication device 1200 and transmit them to the processor 1201, or to send signals from the processor 1201 to other communication devices other than the communication device 1200.

[0275] Optionally, the communication interface 1202 may be a code and / or data read and write interface circuit, or the communication interface 1202 may be a signal transmission interface circuit between a communication processor and a transceiver, or a pin of a chip.

[0276] Optionally, the communication device 1200 may further include at least one memory 1203, which may be used to store required program instructions and / or data. It should be noted that the memory 1203 may exist independently of the processor 1201 or may be integrated with the processor 1201. The memory 1203 may be located within or outside the communication device 1200, without limitation.

[0277] Optionally, the communication device 1200 may further include a power supply circuit 1204, which may be used to supply power to the processor 1201. The power supply circuit 1204 may be located in the same chip as the processor 1201, or in another chip other than the chip where the processor 1201 is located.

[0278] Optionally, the communication device 1200 may further include a bus, and various parts of the communication device 1200 may be interconnected via the bus.

[0279] In some embodiments, in terms of hardware implementation, those skilled in the art may conceive that the communication device 1000 shown in FIG. 10 may take the form of the communication device 1200 shown in FIG. 12 .

[0280] As an example, the functions / implementation process of the processing unit 1001 in FIG10 can be implemented by the processor 1201 in the communication device 1200 shown in FIG12 calling the computer-executable instructions stored in the memory 1203. The functions / implementation process of the communication unit 1002 in FIG10 can be implemented by the communication interface 1202 in the communication device 1200 shown in FIG12.

[0281] It should be noted that the structure shown in FIG12 does not constitute a specific limitation on the terminal device or network device. For example, in other embodiments of the present application, the terminal device or network device may include more or fewer components than shown in the figure, or combine or split some components, or arrange the components differently. The components shown in the figure may be implemented in hardware, software, or a combination of software and hardware.

[0282] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0283] It is understood that the processor in the embodiments of the present application 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, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor may be a microprocessor or any conventional processor.

[0284] The method steps in the embodiments of the present application can be implemented by hardware or by a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory, a flash memory, a read-only memory, a programmable read-only memory, an erasable programmable read-only memory, an electrically erasable programmable read-only memory, a register, a hard disk, a mobile hard disk, a CD-ROM or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor so that the processor can read information from the storage medium and write information to the storage medium. Of course, the storage medium can also be an integral part of the processor. The processor and the storage medium can be located in an ASIC. In addition, the ASIC can be located in a base station or a terminal. Of course, the processor and the storage medium can also exist in a base station or a terminal as discrete components.

[0285] In the above embodiments, all or part of the embodiments may be implemented using software, hardware, firmware, or any combination thereof. When implemented using software, all or part of the embodiments may be implemented in the form of a computer program product. A computer program product includes one or more computer programs or instructions. When the computer program or instructions are loaded and executed on a computer, all or part of the processes or functions of the embodiments of the present application are performed. The computer may be a general-purpose computer, a special-purpose computer, a computer network, a network device, a user device, or other programmable device. The computer program or instructions may be stored in a computer-readable storage medium or transferred from one computer-readable storage medium to another. For example, the computer program or instructions may be transferred from one website, computer, server, or data center to another website, computer, server, or data center via wired or wireless means. The computer-readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server or data center that integrates one or more available media. The available media may be magnetic media, such as floppy disks, hard disks, or magnetic tapes; optical media, such as digital video disks; or semiconductor media, such as solid-state drives. The computer-readable storage medium may be a volatile or nonvolatile storage medium, or may include both volatile and nonvolatile types of storage media.

[0286] In the various embodiments of the present application, unless otherwise specified or there is a logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced by each other. The technical features in different embodiments can be combined to form new embodiments according to their inherent logical relationships.

[0287] Those skilled in the art will appreciate that the embodiments of the present application can be provided as methods, systems, or computer program products. Therefore, the present application can adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application can adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to magnetic disk storage, optical storage, etc.) that contain computer-usable program code.

[0288] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0289] These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a product including an instruction device that implements the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0290] Obviously, those skilled in the art may make various changes and modifications to the present application without departing from the scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is intended to include these modifications and variations.

Claims

1. A cache status reporting method, characterized in that: include: When there is first data in the first logical channel LCH that satisfies a first condition, triggering a delay status report DSR; The first condition includes: the remaining time corresponding to the first data changes from being greater than or equal to a first threshold to being less than the first threshold; The DSR is sent to a network device.

2. The method according to claim 1, characterized in that The first condition also includes: The data volume corresponding to the first data is greater than or equal to a second threshold.

3. The method according to claim 1, characterized in that The first data does not include data for which DSR has been triggered.

4. The method according to claim 2 or 3, characterized in that The second threshold is preset or indicated by the network device to the terminal device.

5. The method according to claim 1, characterized in that After sending the DSR to the network device, the method further includes: When the remaining time of the second data included in the first data in the first LCH is less than the first threshold, the DSR is not triggered.

6. The method according to any one of claims 1 to 5, characterized in that: The first condition also includes any of the following: There is no data in the second LCH, and the second LCH is different from the first LCH; The second LCH does not contain any data with a remaining time less than the first threshold; The priority of the first LCH is higher than the priority of the third LCH, the third LCH has data, and the third LCH is different from the first LCH; The priority of the first LCH is higher than that of the fourth LCH, the fourth LCH has data whose remaining time is less than the first threshold, and the fourth LCH is different from the first LCH.

7. The method according to any one of claims 1 to 5, characterized in that: The first condition also includes any of the following: The first data corresponds to a high importance; The first data corresponds to a high importance, and no data exists in the second LCH, and the second LCH is different from the first LCH; The first data has high importance, and the second LCH does not have any data with a remaining time less than the first threshold; The first data corresponds to a high importance, and the priority of the first LCH is higher than the priority of the third LCH, the third LCH has data, and the third LCH is different from the first LCH; The first data corresponds to a high importance, and the priority of the first LCH is higher than that of the fourth LCH. The fourth LCH has data whose remaining time is less than the first threshold, and the fourth LCH is different from the first LCH.

8. The method according to any one of claims 1 to 5, characterized in that: The first condition includes any of the following: The first data corresponds to a high importance, and the second LCH does not have any high importance data, and the second LCH is different from the first LCH; The first data corresponds to high importance, and the second LCH does not contain high importance data with a remaining time less than the first threshold; The first data corresponds to a high importance, and the priority of the first LCH is higher than the priority of the fifth LCH, the fifth LCH contains data of high importance, and the fifth LCH is different from the first LCH; The first data corresponds to high importance, and the priority of the first LCH is higher than the priority of the sixth LCH. The sixth LCH has data with a remaining time less than the first threshold and high importance. The sixth LCH is different from the first LCH.

9. The method according to claim 1, characterized in that The first condition also includes: The flag bit corresponding to the first data is a first value, and the first value is used to indicate that the first data has not triggered DSR.

10. The method according to claim 9, characterized in that After the terminal device triggers a delay status report DSR, the method further includes: The flag bit corresponding to the first data is updated to a second value, where the second value is used to indicate that the first data has triggered the DSR.

11. The method according to claim 1, characterized in that The first condition also includes: The sequence number corresponding to the first data is greater than the DSR sequence number, and the DSR sequence number is the maximum sequence number corresponding to the data that has triggered the DSR.

12. The method according to claim 11, characterized in that After the terminal device triggers a delay status report DSR, the method further includes: Update the DSR sequence number to the sequence number corresponding to the first data.

13. A method for reporting cache status, characterized in that: include: Periodically triggering a delay status report DSR for a first logical channel LCH; The DSR is periodically sent to the network device.

14. The method according to claim 13, characterized in that The method further comprises: Receive first configuration information sent by the network device, where the first configuration information is used to indicate a period for triggering DSR corresponding to the first LCH.

15. The method according to claim 14, characterized in that The method further comprises: The first configuration information is also used to indicate when the terminal device triggers DSR for the first time.

16. The method according to claim 14, characterized in that The method further comprises: Receive downlink control information DCI, where the DCI is used to indicate when the terminal device triggers DSR for the first time.

17. A communication device, characterized in that: including a processor, an interface circuit, and a memory; The processor is used to execute the computer program or instructions stored in the memory, so that the communication device implements the method described in any one of claims 1 to 12, or the communication device implements the method described in any one of claims 13 to 16.

18. A communication device, characterized in that: including a processor and a memory; The processor is used to execute the computer program or instructions stored in the memory, so that the communication device implements the method described in any one of claims 1 to 12, or the communication device implements the method described in any one of claims 13 to 16.

19. A computer-readable storage medium, characterized in that: Used to store computer programs or instructions, when the computer programs or instructions are executed by a computer, the computer implements the method according to any one of claims 1 to 12, or the computer implements the method according to any one of claims 13 to 16.

20. A chip, characterized in that: The chip comprises a processor, the processor being coupled to a memory and configured to execute a computer program or instruction stored in the memory, so that the chip implements the method described in any one of claims 1 to 12, or the chip implements the method described in any one of claims 13 to 16.

21. A computer program product, characterized in that The computer program product stores a computer program, which includes program instructions. When the program instructions are executed by a computer, the computer executes a method as described in any one of 1 to 12, or the computer executes a method as described in any one of 13 to 16.

Images