Communication method and apparatus, and device and storage medium

Abstract

The present application provides a communication method and apparatus, and a device and a storage medium. The method can be applied to a terminal device or components in the terminal device, and comprises: a terminal device sending a first BSR and a first DSR, acquiring a first uplink resource, and then, on the basis of sending conditions of the first BSR and the first DSR and / or an accommodation condition of the first uplink resource, determining whether to restart a retransmission BSR timer. The method prevents the problem of a BSR transmission delay being caused due to a retransmission BSR timer always being restarted after the acquisition of a first uplink resource, and the data transmission of an LCH associated with a BSR being thus affected.

Description

Communication method, device, equipment and storage medium This application claims priority to the Chinese patent application filed with the China Patent Office on November 3, 2023, with application number 202311466478.9 and application name “Communication Method, Apparatus, Equipment and Storage Medium”, all contents of which are incorporated by reference in this application. Technical Field The present application relates to the field of communication technology, and in particular to a communication method, apparatus, device and storage medium. Background Art In some communication systems, a terminal device may send a buffer status report (BSR) to a network device to inform the network device of information about the amount of data in a logical channel (LCH) in a logical channel group (LCG), so that the network device can reasonably allocate uplink resources to the terminal device. In order to meet the delay requirements of some real-time multimedia services used in communication systems, such as extended reality (XR), cloud gaming, video transmission, etc. The terminal device can also send a delay status report (DSR) to the network device to notify the network device of the amount of data and the remaining time of the delayed emergency data in the LCH in the LCG. In this case, after the terminal device receives the uplink resources allocated by the network device, it cannot determine whether the uplink resources are allocated in response to the BSR or DSR, which may cause data transmission delays. Summary of the invention The present application provides a communication method, apparatus, device and storage medium to avoid transmission delay of BSR, thereby avoiding transmission delay of data on LCH or LCG associated with BSR. In a first aspect, the present application provides a communication method that can be applied to a terminal device or a component in a terminal device, such as a chip or a chip system. An exemplary description is given below using the terminal device as the execution subject. As a first example, the method includes: the terminal device sends a first BSR and a first DSR, and obtains a first uplink resource, and then determines whether to restart the retransmission BSR timer based on the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource, so as to avoid always restarting the retransmission BSR timer after obtaining the first uplink resource, resulting in BSR transmission delay, thereby affecting the data transmission of the LCH associated with the BSR. In a possible implementation, the first condition includes: the first BSR and the first DSR are included in the same media access control (MAC) protocol data unit (PDU). In this case, the terminal device can determine that the first uplink resource is allocated for the BSR, ensuring that restarting the retransmission BSR timer does not cause a BSR transmission delay. In a possible implementation, the first condition includes: The first uplink resource does not satisfy a first logical channel prioritization (LCP) mapping restriction; and / or, The first uplink resource satisfies the second LCP mapping restriction; The first LCP mapping restriction corresponds to the logical channel LCH associated with the XR service or the first DSR; the second LCP mapping restriction corresponds to the LCH associated with the non-XR service or the first BSR. The first uplink resource does not meet the first LCP mapping restriction, and the first uplink resource cannot carry: the LCH associated with the XR service or the first DSR or DSR, or the LCG associated with the XR service or the first DSR or DSR, or the data in the LCH in the LCG associated with the XR service or the first DSR or DSR. In this case, the terminal device can determine that the first uplink resource is not a resource allocated by the network device for the first DSR, so it is more likely to be a resource allocated for the first BSR, and the terminal device restarting the retransmission BSR timer will not cause BSR transmission delay. The first uplink resource satisfies the second LCP mapping restriction, and the first uplink resource can carry data in the LCH associated with the first BSR or BSR, or the LCG associated with the first BSR or BSR, or the LCH in the LCG associated with the first BSR or BSR, or the first uplink resource can carry data in the LCH of the terminal device, or the LCG of the terminal device, or the LCH in the LCG of the terminal device. In this case, it is more likely that the first uplink resource is the resource allocated by the network device for the first BSR, so the terminal device restarting the retransmission BSR timer will not cause BSR transmission delay. In a possible implementation, when the first condition includes: the first uplink resource does not satisfy the first LCP mapping restriction; and / or, when the first uplink resource satisfies the second LCP mapping restriction, the first condition may further include: the first BSR and the first DSR are not included in the same MAC PDU. In combination with the fact that the first BSR and the first DSR are not included in the same MAC PDU, when it is determined that the first uplink resource is not a resource allocated by the network device for the first DSR, it can be accurately determined that the first uplink resource is a resource allocated by the network device for the BSR, so as to ensure that restarting the retransmission BSR timer does not cause a BSR transmission delay. In a possible implementation, the first condition includes: the first uplink resource can accommodate the data in the LCH in the LCG. It can be determined with a high probability that the first uplink resource is a resource allocated by the network device for the first BSR, or the first uplink resource is a resource allocated by the network device for the first BSR and the first DSR. In other words, the first uplink resource can carry the data in the LCH associated with the first BSR. Therefore, restarting the retransmission BSR timer of the terminal device will not cause BSR transmission delay. In a possible implementation, when the first condition includes: the first uplink resource can accommodate the data in the LCH in the LCG, the first condition also includes: the first BSR and the first DSR are not included in the same MAC PDU; and / or, the first uplink resource satisfies the first LCP mapping restriction. It can be determined that the first uplink resource is a resource allocated by the network device for the first BSR. In other words, the first uplink resource can carry the data in the LCH associated with the first BSR. Therefore, restarting the retransmission BSR timer of the terminal device will not cause BSR transmission delay. In a possible implementation manner, after the terminal device acquires the first uplink resource, the method further includes: when a second condition is met, the terminal device does not restart the retransmission BSR timer; the second condition includes at least one of the following: The first BSR and the first DSR are not included in the same MAC PDU; The first uplink resource satisfies the first LCP mapping restriction; The first uplink resource does not meet the second LCP mapping restriction; or, The first uplink resource cannot accommodate all the data in the LCH. In this implementation, the content of the second condition corresponds to the first condition one by one, and has opposite expressions in content. The technical effects achieved are similar, and will not be repeated for the sake of brevity. In a possible implementation, in order to improve the robustness of DSR, the terminal device may determine whether to restart the DSR timer based on a third condition associated with the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource. If the third condition is met, the terminal device restarts the retransmission DSR timer; if the third condition is not met, the retransmission DSR timer is not restarted. In a possible implementation, the third condition includes: the first BSR and the first DSR are included in the same MAC PDU. As mentioned above, at this time, the first uplink resource can be configured for BSR and DSR, that is, the first uplink resource can carry the LCH associated with BSR or the LCG associated with BSR or the LCH in the LCG associated with BSR, and the LCH associated with DSR or the LCG associated with DSR or the BSR in the LCG associated with DSR. The terminal device restarts the retransmission DSR timer, which will not cause DSR transmission delay. In a possible implementation, the third condition includes: The first uplink resource satisfies the first LCP mapping restriction; and / or, The first uplink resource does not meet the second LCP mapping restriction; Among them, the first LCP mapping restriction corresponds to the LCH associated with the XR service or the first DSR; the second LCP mapping restriction corresponds to the LCH associated with the non-XR service or the first BSR. The first uplink resource meets the first LCP mapping restriction, the first uplink resource can carry the data of the XR service, or the first uplink resource can carry the LCH associated with the first DSR, or the LCG associated with the XR service or the first DSR or DSR, or the data in the LCH in the LCG associated with the XR service or the first DSR or DSR, wherein the data of the XR service is contained in the LCH associated with the first DSR, or the LCG associated with the first DSR, or the LCH in the LCG associated with the first DSR. In this case, it can be determined that the first uplink resource is a resource allocated by the network device for the first DSR, or in other words, the first uplink resource can carry the data of the LCH associated with the first DSR, or the LCG associated with the first DSR, or the LCH in the LCG associated with the first DSR, and restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. The first uplink resource does not meet the second LCP mapping restriction, and the second LCP mapping restriction corresponds to the non-XR service or the LCH associated with the first BSR. In other words, the first uplink resource cannot carry data for non-XR services, or the first uplink resource cannot carry data for the LCH associated with the first BSR. In this case, it can be determined that the first uplink resource is not a resource allocated by the network device for the first BSR, but is more likely to be a resource allocated by the network device for the first DSR, and restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. In a possible implementation manner, when the third condition includes: the first uplink resource satisfies the first LCP mapping restriction; and / or the first uplink resource does not satisfy the second LCP mapping restriction, the third condition may also include: the first BSR and the first DSR are not included in the same When it is determined that the first uplink resource is not a resource allocated by the network device for the first BSR, it can be accurately determined that the first uplink resource is a resource allocated by the network device for the DSR, so as to ensure that restarting the retransmission DSR timer does not cause a delay in the first DSR transmission. In a possible implementation, the third condition includes: the first uplink resource can accommodate the XR service or the data or emergency data in the LCH in the LCG associated with the first DSR. It can be determined that the first uplink resource is a resource allocated by the network device for the first DSR, or the first uplink resource is a resource allocated by the network device for the first BSR and the first DSR. In other words, the first uplink resource can carry the data in the LCH associated with the first DSR. Therefore, restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. In a possible implementation manner, when the third condition includes that the first uplink resource can accommodate the XR service or the data or emergency data in the LCH in the LCG associated with the first DSR, the third condition may also include any one or more of the following: The first BSR and the first DSR are not contained in the same MAC PDU; or, The first uplink resource meets the second LCP mapping restriction. In this case, it can be determined that the first uplink resource is a resource allocated by the network device for the first DSR, in other words, the first uplink resource can carry data in the LCH associated with the first DSR. Therefore, restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. In a possible implementation manner, after the terminal device acquires the first uplink resource, the method further includes: if a fourth condition is met, the retransmission DSR timer is not restarted; the fourth condition includes at least one of the following: The first BSR and the first DSR are not included in the same MAC PDU; The first uplink resource does not satisfy the first LCP mapping restriction; The first uplink resource satisfies the second LCP mapping restriction; or, The first uplink resource cannot accommodate all XR services or data or emergency data in the LCH in the LCG associated with the first DSR. In this implementation, the content of the second condition corresponds to the first condition one by one, and has opposite expressions in content. The technical effects achieved are similar, and will not be repeated for the sake of brevity. Optionally, the second LCP mapping restriction corresponds to a non-XR service or an LCH associated with the first BSR, including: Second LCP mapping restrictions include: LCP mapping restrictions for LCHs associated with non-XR services, or, LCP mapping restrictions for LCHs in the LCG included in the first BSR; or, The amount of data included in the first BSR is greater than the LCP mapping restriction of the LCH in the LCG of 0. Optionally, the first LCP mapping restriction corresponds to the LCH associated with the XR service or the first DSR, including: The first LCP mapping restrictions include: LCP mapping restrictions for LCH associated with XR services, or, LCP mapping restrictions for LCHs in the LCG included in the first DSR; or, The amount of data included in the first DSR is greater than the LCP mapping restriction of the LCH in the LCG. As a second example, the method includes: the terminal device triggers the first DSR when the fifth condition is met, wherein the fifth condition includes: the retransmission DSR timer times out, and there is data or emergency data in the LCH in the LCG associated with the XR service or the first DSR. By restarting the retransmission DSR timer to trigger the first DSR, the robustness of the DSR is improved. In a possible implementation, the terminal device starts or restarts the DSR retransmission timer after sending the first DSR. For example, the terminal device starts the DSR timer after sending the first DSR for the first time, and restarts the DSR retransmission timer after retransmitting the first DSR. In a possible implementation, the terminal device may obtain first confirmation information, the first confirmation information is associated with the first DSR, and the first confirmation information is used to indicate restarting or stopping the retransmission DSR timer. Further, the terminal device may restart or stop the retransmission DSR timer in response to the first confirmation information. Optionally, the first confirmation information may be carried in MAC CE. In a possible implementation, the LCH that triggers the first DSR is: when the first DSR is triggered, the LCH in the LCG associated with the XR service or the first DSR has the highest priority among the LCHs with data or urgent data, so as to reduce the transmission delay of important data or urgent data. In the second aspect, an embodiment of the present application provides a communication device, including: a transceiver module, used to send a first cache status report BSR; the transceiver module can also be used to send a first delay status report DSR; the transceiver module is also used to obtain a first uplink resource; a processing module, used to meet a first condition and restart the retransmission BSR timer; wherein the first condition is associated with the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource. In a possible implementation manner, the first condition includes: the first BSR and the first DSR are included in the same MAC PDU middle. In a possible implementation, the first condition includes: the first uplink resource does not satisfy the first logical channel priority division LCP mapping restriction; and / or the first uplink resource satisfies the second logical channel priority division LCP mapping restriction; wherein the first LCP mapping restriction corresponds to the extended reality XR service or the logical channel LCH associated with the first DSR; the second LCP mapping restriction corresponds to the non-XR service or the LCH associated with the first BSR. In a possible implementation manner, the first condition further includes: the first BSR and the first DSR are not included in the same MAC PDU. In a possible implementation manner, the first condition includes: the first uplink resource can accommodate data in the LCH in all logical channel groups LCG. In a possible implementation manner, the first condition further includes: the first BSR and the first DSR are not included in the same MAC PDU; and / or the first uplink resource satisfies a first LCP mapping restriction. In one possible implementation, after acquiring the first uplink resource, the processing module is further used to: meet the second condition and not restart the retransmission BSR timer; the second condition includes at least one of the following: the first BSR and the first DSR are not included in the same MAC PDU; the first uplink resource meets the first LCP mapping restriction; the first uplink resource does not meet the second LCP mapping restriction; or, the first uplink resource cannot accommodate all the data in the LCH. In a possible implementation, after acquiring the first uplink resource, the processing module is further used to: when a third condition is met, restart the retransmission DSR timer; the third condition is associated with the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource. In a possible implementation manner, the third condition includes: the first BSR and the first DSR are included in the same MAC PDU. In one possible implementation, the third condition includes: the first uplink resource satisfies a first LCP mapping restriction; and / or the first uplink resource does not satisfy a second LCP mapping restriction; wherein the first LCP mapping restriction corresponds to the LCH associated with the XR service or the first DSR; and the second LCP mapping restriction corresponds to the LCH associated with the non-XR service or the first BSR. In a possible implementation manner, the third condition also includes: the first BSR and the first DSR are not included in the same MAC PDU. In a possible implementation, the third condition includes: the first uplink resource can accommodate all XR services or data or emergency data in the LCH in the LCG associated with the first DSR. In a possible implementation manner, the third condition further includes any one or more of the following: the first BSR and the first DSR are not included in the same MAC PDU; or the first uplink resource satisfies the second LCP mapping restriction. In one possible implementation, after acquiring the first uplink resource, the processing module is also used to: meet the fourth condition and do not restart the retransmission DSR timer; the fourth condition includes at least one of the following: the first BSR and the first DSR are not included in the same MAC PDU; the first uplink resource does not meet the first LCP mapping restriction; the first uplink resource meets the second LCP mapping restriction; or, the first uplink resource cannot accommodate all XR services or data or emergency data in the LCH in the LCG associated with the first DSR. In one possible implementation, the second LCP mapping restriction corresponds to the LCH associated with the non-XR service or the first BSR, including: the second LCP mapping restriction includes: the LCP mapping restriction of the LCH associated with the non-XR service, or, the LCP mapping restriction of the LCH in the LCG included in the first BSR; or, the LCP mapping restriction of the LCH in the LCG whose data volume included in the first BSR is greater than 0. In one possible implementation, the first LCP mapping restriction corresponds to the LCH associated with the XR service or the first DSR, including: the first LCP mapping restriction includes: the LCP mapping restriction of the LCH associated with the XR service or the first DSR, or, the LCP mapping restriction of the LCH in the LCG included in the first DSR; or, the LCP mapping restriction of the LCH in the LCG whose data volume included in the first DSR is greater than 0. In the third aspect, an embodiment of the present application provides a communication device, including: a processing module, used to satisfy a fifth condition and trigger a first DSR; wherein the fifth condition includes: the retransmission DSR timer times out, and there is data or emergency data in the LCH in the LCG associated with the XR service or the first DSR. In a possible implementation, it includes: a transceiver module, configured to send the first DSR, and start or restart the retransmission DSR timer. In a possible implementation, it includes: a transceiver module, used to obtain first confirmation information, and restart or stop the retransmission DSR timer; wherein the first confirmation information is associated with the first DSR. In a possible implementation manner, the first confirmation information is carried in MAC CE. In a possible implementation manner, the processing module is specifically configured to: when the first DSR is triggered, there is an LCH with the highest priority among the LCHs for data or emergency data in the LCHs in the LCG associated with the XR service or the first DSR. In a fourth aspect, an embodiment of the present application provides a communication device, comprising: a processor and a memory, the memory being used to store a computer program, the processor being used to call and run the computer program stored in the memory, and executing the method in the first aspect or each possible implementation method. In a fifth aspect, an embodiment of the present application provides a chip, comprising: a processor, configured to call and execute computer instructions from a memory, so that a device equipped with the chip executes a method as in the first aspect or any possible implementation manner. In a sixth aspect, an embodiment of the present application provides a computer-readable storage medium for storing computer program instructions, wherein the computer program enables a computer to execute a method as in the first aspect or any possible implementation manner. In a seventh aspect, an embodiment of the present application provides a computer program product, comprising computer program instructions, which enable a computer to execute the method in the first aspect or each possible implementation manner. In an eighth aspect, an embodiment of the present application provides a device, comprising a logic circuit and an input-output interface, wherein the input-output interface is used to receive signals from other communication devices outside the device and transmit them to the logic circuit or send signals from the logic circuit to other communication devices outside the device, and the logic circuit is used to execute code instructions to implement the method in the first aspect or each possible implementation method. The beneficial effects of the solutions in the above-mentioned second to eighth aspects and the above-mentioned possible implementation modes can be referred to the beneficial effects brought about by the above-mentioned first aspect and the possible implementation modes of the first aspect, and will not be repeated here. BRIEF DESCRIPTION OF THE DRAWINGS FIG1 is a schematic diagram of the architecture of a communication system used in an embodiment of the present application; FIG2 is a schematic diagram of a network architecture applicable to an embodiment of the present application; FIG3 is a schematic diagram of a network architecture applicable to an embodiment of the present application; FIG4 is a schematic diagram of the structure of a GOP provided in an embodiment of the present application; FIG5A is a schematic diagram of a format of a short BSR or a truncated BSR provided by the present application; FIG5B is a schematic diagram of a format of a long BSR or a long truncated BSR provided by the present application; FIG5C is a schematic diagram of a format of an enhanced BSR, an enhanced truncated BSR, a long enhanced BSR, or a long enhanced truncated BSR provided in the present application; FIG5D is a schematic diagram of a format of a short enhanced BSR or a short enhanced truncated BSR provided by the present application; FIG6 is a schematic diagram of the structure of a medium access control control unit provided by the present application; FIG7A is a schematic diagram of the structure of a MAC subheader applicable to a variable-size MAC CE provided by the present application; FIG7B is a schematic diagram of a structure of a MAC subheader applicable to a variable-size MAC CE provided by the present application; FIG7C is a schematic diagram of a structure of a MAC subheader applicable to a fixed-size MAC CE provided by the present application; FIG7D is a schematic diagram of a structure of a MAC subheader applicable to a fixed-size MAC CE provided by the present application; FIG8 is a schematic diagram of a DSR format provided by the present application; FIG9 is a schematic flow chart of a communication method provided in an embodiment of the present application; FIG10 is a schematic block diagram of a communication device provided in an embodiment of the present application; FIG. 11 is another schematic block diagram of a communication device provided in an embodiment of the present application. DETAILED DESCRIPTION The technical solution in this application will be described below in conjunction with the accompanying drawings. In the description of the embodiments of the present application, unless otherwise specified, the terms "first" and "second" are used for descriptive purposes only and are not to be understood as indicating or implying relative importance or implicitly indicating the number of the indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of the features. In the description of the embodiments, unless otherwise specified, "multiple" means two or more. In addition, the terms "include" and "have" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps not listed. There are listed steps or units, or optionally further include other steps or units inherent to these processes, methods, products or apparatuses. In the embodiments of the present 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 the present application should not be interpreted as being more preferred or more advantageous than other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present related concepts in a concrete way for easy understanding. 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 than three. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships can exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b and (or) c can mean: 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 measures will be taken under certain objective circumstances. It does not limit the time, nor does it require any judgment when it is implemented, nor does it mean that there are other limitations. In the present application, "indication" may include: direct indication, or indirect indication, or explicit indication, or implicit indication. In the present application, "include" may include: direct inclusion, or, indirect inclusion, or, explicit inclusion, or, implicit inclusion. The technical solution of the embodiment of the present application can be applied to various communication systems, such as: global system of mobile communication (GSM) system, code division multiple access (CDMA) system, wideband code division multiple access (WCDMA) system, general packet radio service (GPRS), long term evolution (LTE) system, LTE frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS), worldwide interoperability for microwave access (WiMAX) communication system, fifth generation (5G) system or new radio (NR), 5.5G, sixth generation (6G) system or future communication system, etc. In addition, the term "system" can be replaced with "network". The terminal device involved in the embodiment of the present application is a device with wireless transceiver function, which can be a fixed device or a mobile device, and can refer to a user device, an access terminal, a user unit, a user station, a mobile station, a mobile station, a remote station, a remote terminal, a mobile device, a user terminal, a terminal, a wireless communication device, a user agent or a user device. The terminal device can also be a cellular phone, a cordless phone, a Session Initiation Protocol (Session Initiation Protocol, SIP) phone, a Wireless Local Loop (Wireless Local Loop, WLL) station, a personal digital assistant (personal digital assistant, PDA), a handheld device with wireless communication function, a computing device or other processing device connected to a wireless modem, a vehicle-mounted device, a wearable device, a terminal device in a 5G network or a terminal device in a public land mobile communication network (public land mobile network, PLMN) in the future evolution, etc. The terminal device can also be a handheld device (such as a mobile phone), a wearable device, a vehicle-mounted device, or a wireless device built into the above device (for example, a communication module, a modem, or a chip system, etc.). The terminal device is used to connect people, objects, machines, etc., and can be widely used in various scenarios, such as but not limited to the following scenarios: cellular communication, device-to-device communication (D2D), vehicle to everything (V2X), machine-to-machine / machine-type communications (M2M / MTC), Internet of Things (IoT), virtual reality (VR), augmented reality (AR), industrial control, self-driving, remote medical, smart grid, smart furniture, smart office, smart wear, smart transportation, smart city, drone, robot and other scenarios. Among them, the terminal device can also be other devices, such as the first device, and it should be understood that the embodiments of the present application are not limited to this. The network device in the embodiment of the present application may be a device for communicating with a terminal device. The network device may be a base station (base transceiver station, BTS) in a GSM system or CDMA, or a base station (NodeB, NB) in a WCDMA system, or an evolved base station (evolutional Node B, eNB or eNodeB) in an LTE system, or a wireless controller in a cloud radio access network (CRAN) scenario, or the network device may be a relay station, access point, vehicle-mounted device, wearable device, and network device in a future 5G network or a network device in a future evolved PLMN network, etc. For example, the network device may include an access network device, and / or a core network device. An access network device is a device with a wireless transceiver function, which is used to communicate with a terminal device. Access network devices include but are not limited to base stations (BTS, Node B, eNodeB / eNB, or gNodeB / gNB) and transmission reception points (TRP) in the above-mentioned communication systems, base stations of subsequent evolution of 3GPP, and base stations in WiFi systems. Access nodes, wireless relay nodes, wireless backhaul nodes, etc. The base station can be: a macro base station, a micro base station, a pico base station, a small station, a relay station, etc. Multiple base stations can support the network of the same access technology mentioned above, or they can support the network of different access technologies mentioned above. The base station may include one or more co-site or non-co-site transmission and receiving points. The network device can also be a wireless controller, a centralized unit (CU), and / or a distributed unit (DU) in a CRAN scenario. The network device can also be a server, a wearable device, or a vehicle-mounted device, etc. For example, the network device in the V2X technology can be a road side unit (RSU). Among them, the network device can also be other devices, such as a second device. It should be understood that this application does not make specific limitations on this. In an embodiment of the present application, a terminal device or a network device includes a hardware layer, an operating system layer running on the hardware layer, and an application layer running on the operating system layer. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and a memory (also referred to as main memory). The operating system may be any one or more computer operating systems that implement business processing through a process, such as a Linux operating system, a Unix operating system, an Android operating system, an iOS operating system, or a Windows operating system. The application layer includes applications such as a browser, an address book, a word processing software, and an instant messaging software. In addition, the embodiment of the present application does not specifically limit the specific structure of the execution subject of the method provided in the embodiment of the present application, as long as it can communicate according to the method provided in the embodiment of the present application by running a program that records the code of the method provided in the embodiment of the present application, for example, the execution subject of the method provided in the embodiment of the present application may be a terminal device or a network device, or a functional module, chip, or circuit in a terminal device or a network device that can call and execute a program. The technical solution of the present application is further described in detail below in conjunction with the accompanying drawings. FIG1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application. As shown in FIG1 , a terminal device 130 can access a wireless network to obtain services of an external network (such as the Internet) through the wireless network, or communicate with other devices through the wireless network, such as communicating with other terminal devices. The wireless network includes a radio access network (RAN) device 110 and / or a core network (CN) device 120, wherein the RAN device 110 is used to access the terminal device 130 to the wireless network, and the CN device 120 is used to manage the terminal device and provide a gateway for communicating with the external network. It should be understood that the number of each device in the communication system 100 shown in Figure 1 is for illustration only, and the embodiments of the present application are not limited to this. In actual applications, the communication system 100 may also include more terminal devices 130, more RAN devices 110, and may also include other devices. It should also be understood that when the terminal device 130 communicates with other terminal devices (such as the terminal device 130), the technical solutions in the embodiments of the present application are also applicable. FIG2 is a schematic diagram of a network architecture 200 applicable to an embodiment of the present application. As shown in FIG2 , the network architecture 200 includes CN equipment, RAN equipment, and terminal equipment. Among them, the RAN equipment includes a baseband device and a radio frequency device, wherein the baseband device can be implemented by one node or by multiple nodes, and the radio frequency device can be implemented independently from the baseband device, or can be integrated in the baseband device, or some functions can be integrated independently and some functions can be integrated in the baseband device. For example, in an LTE communication system, a RAN device (eNB) includes a baseband device and a radio frequency device, wherein the radio frequency device can be arranged remotely relative to the baseband device, for example, a remote radio unit (RRU) is a remote radio unit arranged relative to a BBU. The communication between RAN equipment and terminal equipment follows a certain protocol layer structure. For example, the control plane protocol layer structure may include the functions of protocol layers such as the radio resource control (RRC) layer, the packet data convergence protocol (PDCP) layer, the radio link control (RLC) layer, the media access control (MAC) layer and the physical layer; the user plane protocol layer structure may include the functions of protocol layers such as the PDCP layer, the RLC layer, the MAC layer and the physical layer; in a possible implementation, a service data adaptation protocol (SDAP) layer may also be included above the PDCP layer. The RAN device can implement the functions of the protocol layers such as RRC, PDCP, RLC and MAC by one node, or can implement the functions of these protocol layers by multiple nodes. For example, in an evolutionary structure, the RAN device may include a CU and a DU, and multiple DUs may be centrally controlled by one CU. As shown in FIG2 , the CU and the DU may be divided according to the protocol layers of the wireless network, for example, the functions of the PDCP layer and above protocol layers are set in the CU, and the functions of the protocol layers below the PDCP, such as the RLC layer and the MAC layer, are set in the DU. This division of the protocol layer is only an example. It can also be divided in other protocol layers, such as dividing in the RLC layer, setting the functions of the RLC layer and the protocol layers above in the CU, and the functions of the protocol layers below the RLC layer in the DU; or dividing in a certain protocol layer, for example, setting some functions of the RLC layer and the functions of the protocol layers above the RLC layer in the CU, and setting the remaining functions of the RLC layer and the functions of the protocol layers below the RLC layer in the DU. In addition, it can also be divided in other ways, such as dividing by latency, setting the functions whose processing time needs to meet the latency requirements in the DU, and the functions that do not need to meet the latency requirements in the CU. In addition, the RF device can be integrated independently and not placed in the DU, or it can be integrated in the DU, or part of it can be remotely located and part of it can be integrated in the DU. In DU, no restrictions are imposed. FIG3 is a schematic diagram of a network architecture 300 applicable to an embodiment of the present application. Compared with the network architecture shown in FIG2 , FIG3 may also separate the control plane (CP) and the user plane (UP) of the CU and implement them in different entities, namely, a control plane (CP) CU entity (i.e., a CU-CP entity) and a user plane (UP) CU entity (i.e., a CU-UP entity). In the above network architecture, the signaling generated by the CU can be sent to the terminal device through the DU, or the signaling generated by the terminal device can be sent to the CU through the DU. The DU can directly encapsulate the signaling through the protocol layer and transparently transmit it to the terminal device or CU without parsing it. In the following embodiments, if the transmission of such signaling between the DU and the terminal device is involved, at this time, the sending or receiving of the signaling by the DU includes this scenario. For example, the signaling of the RRC or PDCP layer will eventually be processed as the signaling of the PHY layer and sent to the terminal device, or it will be converted from the received signaling of the PHY layer. Under this architecture, the signaling of the RRC or PDCP layer can also be considered to be sent by the DU, or sent by the DU and the RF loader. The network architecture illustrated in Figures 1, 2 or 3 above can be applicable to communication systems of various radio access technologies (RAT), for example, it can be an LTE communication system, it can also be a 5G (or new radio (NR)) communication system, it can also be a transition system between an LTE communication system and a 5G communication system, the transition system can also be called a 4.5G communication system, and of course it can also be a future communication system. 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. It is known to those skilled in the art that with the evolution of the communication 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. For example, the present application can be applicable to vehicle to everything (V2X) scenarios. It should be understood that the network architecture shown in Figures 1 to 3 above is only an example of the present application and does not have any limiting effect on the embodiments of the present application. In particular, the embodiments of the present application can also be applied to other network architectures, for example, without distinguishing between base stations and core networks, that is, base stations and core networks can belong to the same network device, and the communication between the network device and the terminal device; or, the communication between terminal devices, etc. The network equipment and terminal equipment can be fixed or movable. The network equipment and terminal equipment can be deployed on land, including indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on the water surface; they can also be deployed on airplanes, balloons, and artificial satellites. The embodiments of the present application do not limit the application scenarios of the network equipment and terminal equipment. Network devices and terminal devices, terminal devices and terminal devices, and network devices and network devices can communicate through authorized spectrum, unauthorized spectrum (or unauthorized spectrum), or both authorized spectrum and unauthorized spectrum; can communicate through spectrum below 6 gigahertz (GHz), spectrum above 6 GHz, or spectrum below 6 GHz and spectrum above 6 GHz at the same time. The embodiments of the present application do not limit the spectrum resources used for wireless communication. In the embodiments of the present application, the functions of the network device may also be performed by a module (such as a chip) in the network device, or by a control subsystem including the network device function, without limitation. For example, the control subsystem including the network device function may be a control center in the above-mentioned application scenarios such as smart grid, industrial control, smart transportation, and smart city. The functions of the terminal device may also be performed by a module (such as a chip or a modem) in the terminal device, or by a device including the terminal device function, without limitation. In the present application, the network device sends a downlink signal or downlink information to the terminal device, and the downlink information is carried on the downlink resources (or downlink channels); the terminal device sends an uplink signal or uplink information to the network device, and the uplink information is carried on the uplink resources (or uplink channels). For the sake of uniformity, the following text uniformly refers to downlink information and uplink information, downlink resources and uplink resources. For example, when the network device allocates uplink resources to the terminal device, the uplink resources or the allocated uplink resources can be referred to as uplink authorization. For example, in order to communicate with the network device, the terminal device needs to establish a wireless connection with the cell controlled by the network device. The cell that has established a wireless connection with the terminal device is called the service cell of the terminal device. In order to better understand the embodiments of the present application, before introducing the embodiments of the present application, a brief description of the terms involved in the present application is first given. It is understood that these explanations are intended to make the embodiments of the present application easier to understand and should not be regarded as limiting the scope of protection required by the embodiments of the present application. 1. XR business: XR can refer to various environments that combine reality and virtuality, as well as human-machine interactions, generated by computing technologies and wearable devices. It mainly includes virtual reality (VR), augmented reality (AR), and mixed reality (MR) and other virtual-reality interaction technologies. In order to enhance the experience of human interaction with the virtual world, XR services have strict requirements on bandwidth and latency. For example, XR can include cloud gaming. For example, during downlink transmission, the server's encoder generates data content at a fixed frequency (e.g., 60 Hz or 120 Hz, etc.) and transmits it to the XR terminal via the core network and RAN. For example, during uplink transmission, the XR terminal can collect images through the built-in camera and continuously upload images of the current scene to the server at a specific frequency (e.g., 60 Hz or 120 Hz, etc.). For example, XR services usually generate data periodically at a certain frame rate. For example, the business model for downlink XR services is roughly: AR / VR and cloud gaming. Among them, the AR / VR frame rate can be 60fps, that is, 60 frames of video images are generated per second, and one video frame appears approximately every 16.66ms. The AR / VR frame rate can also be 120fps, that is, 120 frames of video images are generated per second, and one video frame appears approximately every 8.33ms. The cloud gaming frame rate can be 60fps or 120fps, that is, 60 frames of video images are generated per second or 120 frames of video images per second. For example, the latency requirement of XR services may be 10ms, 30ms, etc. Optionally, in an actual transmission system, data jitter may occur due to data encoding delay, network transmission delay, etc. For example, jitter may be considered to obey a truncated Gaussian distribution, with the truncation range being approximately [-4, 4] ms. For example, the jitter may include uplink jitter and / or downlink jitter. For example, for XR video services, images can be encoded in a group of pictures (GOP) encoding mode and / or a slice encoding mode during encoding. For example, for a slice encoding mode, a video frame may include an I slice and one or more P slices. For example, for a GOP encoding mode, a GOP may include an I frame, or a GOP may include an I frame and one or more P frames. Optionally, a GOP may also include a B frame. Exemplarily, an I frame is an intra-coded frame (also referred to as an intra-coded frame, a key frame, an important frame, etc.), and an I frame is a reference frame for a P frame and / or a B frame, and has the characteristics of independent encoding and decoding. Exemplarily, a P frame is a forward prediction frame (also referred to as a forward prediction coded frame, a forward reference frame, a dependent frame, a non-key frame, etc.). When decoding a P frame, it is necessary to refer to the most recent I frame or P frame in front, and a P frame can be a reference frame for a subsequent P frame and / or B frame. Exemplarily, a B frame is a bi-directional interpolated prediction frame, which may also be called a dependent frame, a non-key frame, etc. When decoding a B frame, it is necessary to refer to the most recent I frame or P frame in the front, as well as the most recent P frame in the back. Exemplarily, an I frame is a complete picture, and a P frame records the changes relative to the I frame. Without an I frame, the P frame cannot be decoded, so the transmission priority of the I frame must be higher than that of the P frame. If an I frame fails to be transmitted during the transmission process (for example, it is still not successfully transmitted even if its delay requirement is met), even if the subsequent video frame that depends on the I frame (for example, a P frame) is transmitted successfully, correct decoding cannot be achieved on the receiving side. Fig. 4 is a schematic diagram of the structure of a GOP 400 provided in an embodiment of the present application. As shown in Fig. 4, a GOP sequence (eg, GOP#1 or GOP#2) includes an I frame and multiple P frames. Exemplarily, a data burst may also be referred to as a data burst, which is a group of protocol data units (PDUs) generated and sent by an application in a short period of time (e.g., A set of data multiple PDUs generated and sent by the application in a short period of time). Exemplarily, a PDU set may include one or more PDUs carrying the payload of one unit of information generated at the application level (e.g., a PDU Set may include one or more PDUs carrying the payload of one unit of information generated at the application level (e.g., a frame or video slice for XRM Services, as used in TR 26.926

[0027] )). For example, a PDU set includes a frame or a slice. For example, a PDU set includes a frame or a slice. For example, in some implementations, the application layer needs all PDUs in a PDU Set to use the corresponding unit of information, or the application layer needs all PDUs in a PDU Set to obtain (decode) or use the corresponding information unit. For example, in other implementations, when some PDUs are missing, the application layer can still recover all or part of the information unit (for example, In some implementations all PDUs in a PDU Set are needed by the application layer to use the corresponding unit of information. In other implementations, the application layer can still recover parts all or of the information unit, when some PDUs are missing). Optionally, a data burst includes at least one PDU set. For example, data burst 1 may be associated with one or more data bursts, which need to depend on data burst 1. If data burst 1 is discarded, the one or more data bursts may not be decoded. For example, PDU set 1 may be associated with one or more PDU sets, which need to depend on PDU set 1. If PDU set 1 is discarded, the one or more PDU sets may not be decoded. For example, an XR service may be a periodic arrival service. For example, an XR service may be a periodic arrival service with jitter. For example, an XR service requires low latency and low power consumption. For example, the period of an XR service is a non-integer. The period of an XR service is calculated based on the frame generation rate X (unit: fps). The period of an XR service is the inverse of the frame generation rate X. Typical values ​​of the frame generation rate X are 30fps, 60fps, 90fps, 120fps. So the XR service cycles are: 30fps: (1 / 30fps)s=(1 / 30fps)×1000ms=1000 / 30ms=100 / 3ms≈33.3333ms 60fps: (1 / 60fps)s=(1 / 60fps)×1000ms=1000 / 60ms=50 / 3ms≈16.6667ms 90fps: (1 / 90fps)s=(1 / 90fps)×1000ms=1000 / 90ms=100 / 9ms≈11.1111ms 120fps: (1 / 120fps)s=(1 / 120fps)×1000ms=1000 / 120ms=25 / 3ms≈8.3333ms Optionally, the latency requirement for XR services is very short, for example, 30ms for UL. For example, all data of a data burst may not be delivered from the APP side of the terminal device to the access stratum (AS) of the terminal device at the same time. It may take a certain amount of time, for example, 3ms or 5ms, to deliver all data from the APP side of the terminal device to the AS layer of the terminal device. This can be called the delay spread of the data burst. Optionally, for XR services, the data volumes of different data bursts may be different. For example, the data volume of an I frame may be greater than the data volume of a P frame. In this embodiment of the present application, XR data may refer to data related to XR services. 2. Buffer status report (or buffer status reporting, BSR) For example, the BSR may include / be replaced by: Uu BSR, or uplink (UL) BSR. Uu is a communication interface between a terminal and a base station. For example, the BSR process may be used by the terminal device to provide the network device with information on the amount of uplink data in the Medium Access Control (MAC) entity. For example, media access control may also be referred to as medium access control. Exemplarily, BSR is a MAC control element (CE), and therefore may also be referred to as BSR MAC CE. For example, when certain trigger conditions are met, the terminal device sends a BSR to the network device to indicate the cache status of the terminal device's uplink. After receiving the BSR, the network device can allocate uplink resources to the terminal device according to the BSR reported by the terminal device, so that the terminal device can perform uplink transmission. 2.1 BSR format Optionally, the BSR MAC CE format may include one or more of the following: Short BSR format (short BSR format); Long BSR format; Short truncated BSR format; Long truncated BSR format; Enhanced BSR format; Enhanced truncated BSR format; short enhanced BSR format; short enhanced truncated BSR format; long enhanced BSR format; or, Long enhanced truncated BSR format. For example, the short BSR, the short truncated BSR, the short enhanced BSR, and the short enhanced truncated BSR have a fixed size. For example, the long BSR, the long truncated BSR, the enhanced BSR, the enhanced truncated BSR, the long enhanced BSR, and the long enhanced truncated BSR have a variable size. Exemplarily, a format of a short BSR or a truncated BSR is shown in Fig. 5A. For example, in the BSR format of the present application, LCG ID represents an LCG ID field, Buffer Size represents a Buffer Size field, and Oct represents a byte. Exemplarily, a format of a long BSR or a long truncated BSR is shown in Fig. 5B. For example, in the BSR format of the present application, LCGi represents an LCGi field. Exemplarily, as shown in FIG. 5C , there is a format of an enhanced BSR, an enhanced truncated BSR, a long enhanced BSR, or a long enhanced truncated BSR. Exemplarily, FIG. 5D shows a format of a short enhanced BSR or a short enhanced truncated BSR. For example, the BSR format is identified by the LCID in the MAC PDU subheader or the MAC subheader. Exemplarily, the fields in the BSR MAC CE are defined as follows: (1) The LCG ID field, or LCG ID for short, is used to identify the logical channel group whose cache status is being reported. For example, the cache status may include / be replaced by: cache size, or, buffer size, or, BS. Exemplarily, for a short BSR and a short truncated BSR, the length of this field is 3 bits. Exemplarily, for a short enhanced BSR and a short enhanced truncated BSR, the length of this field is 3 bits. (2) LCGi field, or LCGi for short. Among them, for the long BSR, enhanced BSR, and long enhanced BSR, the LCGi field indicates whether the cache size field of the logical channel group i exists, as follows (exemplarily): a. The LCGi field set to "1" indicates that the buffer size field of logical channel group i is to be reported. b. The LCGi field set to "0" indicates that the cache size field of logical channel group i is not reported. For long truncated BSR, enhanced truncated BSR, and long enhanced truncated BSR, the LCGi field indicates whether logical channel group i has available data, as follows: a. The LCGi field set to "1" indicates that logical channel group i has available data. b. The LCGi field set to "0" indicates that there is no available data for logical channel group i. (3) BTi field, also called buffer size table field or buffer status table field, or simply called Buffer Size table or BS table or buffer size table or buffer status table, the BTi field is used to indicate the BS table (or, buffer size table or buffer status table or buffer size table) used to encode the buffer size corresponding to LCGi. For example, the BTi field is 1, indicating that table 1 (or, 8-bit new table) is used for LCGi / used to encode the buffer size corresponding to LCGi, and the BTi field is 0, indicating that table 2 (or, 8-bit old table) is used for LCGi / used to encode the buffer size corresponding to LCGi; or vice versa. (4) Buffer Size field, also known as the buffer size field, or simply referred to as Buffer Size or BS or buffer size, is used to indicate the buffer size corresponding to the logical channel group. For example, this field is used to identify the total amount of data available in all logical channels of an LCG after constructing a MAC protocol data unit (PDU) according to the data volume calculation process in the third generation partnership project (3GPP) technical specification (TS) 38.322 and TS 38.323. For example, the data amount of the Buffer Size field is expressed in bytes (Oct). For example, the size of the RLC header and the MAC subheader are not considered in the calculation of the buffer size. Exemplarily, for short BSR and short truncated BSR, the length of the Buffer Size field is 5 bits. Exemplarily, for long BSR, long truncated BSR, enhanced BSR, enhanced truncated BSR, long enhanced BSR, long enhanced truncated BSR, short enhanced BSR, short enhanced truncated BSR, the length of this field is 8 bits. Exemplarily, for long BSR, long truncated BSR, the arrangement order of the Buffer Size field is included according to the ascending order of LCGi. Exemplarily, for enhanced BSR, enhanced truncated BSR, long enhanced BSR, long enhanced truncated BSR, the arrangement order of the Buffer Size field is included according to the ascending order of LCGi. For example, the arrangement order may include / be replaced by: placement order. Exemplarily, as shown in Figure 5B, if the LCG_1, LCG_3 and LCG_7 fields are all set to "1", and the LCG_0, LCG_2, LCG_4, LCG_5 and LCG_6 fields are all set to "0", it means that LCG_1, LCG_3 and LCG_7 are to report the buffer size, and other logical channel groups do not report the buffer size, that is, m is "3", so there are 3 buffer size fields located below, namely buffer size1, buffer size2, and buffer size3. Buffer size1 can be used to indicate the cache size of LCG_1, buffer size2 can be used to indicate the cache of LCG_3, and buffer size3 can be used to indicate the cache size of LCG_7. It should be noted that, this application uses "BSR" as an example for explanation, but is not limited to this term, for example, it can be replaced by MAC CE or others. For example, through the BSR, the terminal device can report information about the amount of data to be sent in the MAC entity to the network device. The network device can allocate resources to the terminal device according to the amount of data to be sent by the terminal device. It should be noted that the Buffer Size field indicates an index, and the index corresponds to the range of data volume. The relationship between the index indicated by the buffer size field and the corresponding data volume range is represented by the BS table. Currently, three BS tables are defined in the protocol, one BS table corresponds to a 5-bit Buffer Size field, and two BS tables correspond to an 8-bit Buffer Size field. Illustratively, Table 1 is a BS table corresponding to a 5-bit Buffer Size field. Table 1 For example, in Table 1, the BS value corresponding to index 3 is ≤20, and the BS value corresponding to index 2 is ≤14. It can be seen that when the index indicated by the Buffer Size field is 3, the data volume corresponding to the Buffer Size field is greater than 14 and less than or equal to 20. 2.2 BSR triggering: The current protocol defines a variety of events that can trigger BSR, among which an event that triggers BSR related to the embodiment of the present application is: The retransmission BSR timer (retxBSR-Timer) times out and at least one LCH in the LCG contains UL data. In this case, the triggered BSR is called a regular BSR. In addition, for a BSR triggered by a timeout of the retxBSR-Timer, the terminal device considers that the logical channel that triggers the BSR is a logical channel with the highest priority that has data to transmit when the BSR is triggered. It should be noted that triggering a BSR does not mean actually sending a BSR to the network device. After triggering a BSR, there must be resources to send the BSR before the terminal device can send the triggered BSR. For example, a triggered BSR can be canceled. Regarding the retxBSR-Timer in the above-mentioned event of triggering BSR, the following introduces the conditions for starting or restarting the retxBSR-Timer in combination with the BSR sending event. 2.3 Sending BSR Currently, the MAC entity of the terminal device can send a BSR according to the following process: Step 1: If it is determined that at least one BSR has been triggered and not cancelled, proceed to step 2. Step 2: If it is determined that the uplink shared channel (UL-SCH) resource or the UL resource is available for the new transmission, and the UL resource can accommodate the BSR MAC CE and the MAC subheader corresponding to the BSR MAC CE, perform at least one of the following three steps: 1. Indicates the multiplexing and encapsulation process to generate the BSR MAC CE. 2. Start or restart a periodic BSR-Timer, unless all generated BSRs are long truncated BSRs or short truncated BSRs. For example, the periodic BSR-Timer is a timer associated with another event that triggers a BSR. 3. Start or restart retxBSR-Timer. Based on the above process, it can be seen that after the terminal device triggers the BSR, if the conditions for sending the BSR are met, the BSR will be generated and the retxBSR-Timer will be started or restarted. In addition, the terminal device restarts the retxBSR-Timer when / after receiving any newly transmitted UL resources. 3. MAC PDU structure For example, the MAC entity of the terminal may encapsulate the BSR in the MAC PDU. For example, package may include / replace: group, or, group-package, or, include. For example, as shown in FIG6 , a MAC PDU may be composed of one or more MAC sub-PDUs. For example, a MAC subPDU may include a MAC subheader and a MAC service data unit (SDU). Or, for example, a MAC subPDU may include a MAC subheader and a MAC CE. Or, for example, a MAC subPDU may include a MAC subheader and padding. Or, for example, a MAC subPDU may include a MAC subheader. Optionally, a MAC SDU can be a bit string with a length that is byte-aligned (e.g., an integer multiple of 8 bits). A MAC CE can be a bit string with a length that is byte-aligned (e.g., an integer multiple of 8 bits). A MAC subheader can be a bit string with a length that is byte-aligned (e.g., an integer multiple of 8 bits). An integer multiple of . Exemplarily, FIG. 7A and FIG. 7B respectively show a structural example of a MAC subheader applicable to a variable-size MAC CE. As another example, FIG. 7C and FIG. 7D respectively show a structural example of a MAC subheader applicable to a fixed-size MAC CE. For example, the MAC subheader may include a logical channel identification (LCID) field. The LCID field is used to indicate an eLCID or a MAC CE (e.g., the format of a BSR MAC CE). Optionally, the length is 6 bits. Optionally, if the value of the LCID field is set to 34, there may be one additional octet in the MAC subheader containing the eLCID field, and the octet immediately follows the octet containing the LCID field. If the value of the LCID field is set to 33, there may be two additional octets in the MAC subheader containing the eLCID field, and the two additional octets immediately follow the octet containing the LCID field. eLCID: Extended logical channel identification field, which can be used to indicate LCH or MAC CE. L: Length field, indicating the size of the corresponding MAC SDU or MAC CE of variable size. Optionally, each MAC subheader may contain an L field, except for the subheader corresponding to a fixed-size MAC CE, padding, and a MAC SDU containing a UL common control channel (CCCH). Optionally, the size of the L field may be indicated by the F field in the MAC subheader. F: Format field, indicating the size of the "L" field. Each MAC subheader may include an F field, except for the subheaders corresponding to the fixed-size MAC CE, padding, and the MAC SDU containing the UL CCCH. Optionally, the size of the F field is 1 bit. Optionally, a value of 0 indicates that the L field is 8 bits. A value of 1 indicates that the L field is 16 bits. R: Reserved field. For example, the size of the above-mentioned MAC SDU may be variable. Optionally, the size of the MAC CE may be non-fixed, in other words, the size of the MAC CE may be variable. For such a variable size MAC CE, the corresponding MAC subheader includes the following fields: R / F / LCID / (eLCID) / L. Among them, the LCID field is used not only to indicate the format of the corresponding BSR, but also to indicate the format or type of the MAC CE. The L field may be used to indicate the size of the MAC CE. Or, for example, the size of the MAC CE may be a fixed size. In this type of MAC CE, the MAC subheader includes a field R / LCID. As can be seen, since the size of the MAC CE is fixed, the L field in the MAC subheader is no longer required to indicate the size of the MAC CE. 4. Logical Channel Prioritization (LCP) For example, the MAC layer of the terminal device is responsible for multiplexing the data / information of one or more LCHs and / or one or more MAC CEs into the MAC PDU, and this process may be referred to as LCP. Optionally, the data / information of the one or more LCHs includes one or more of the following: medium access control service data unit (MAC SDU), radio link control service data unit (RLC SDU), radio link control protocol data unit (RLC PDU), or media access control (MAC) control element (CE). In one possible implementation, during uplink transmission, the terminal device decides which logical channels to place data on and how much data to place on each logical channel based on the uplink resources configured by the base station and the rules specified by the protocol / standard. In one possible implementation, the LCP first selects the LCH according to the LCP restrictions, and then allocates resources to the LCH according to the starvation avoidance mechanism in descending order of LCH priority (such as the resource allocation described below). 4.1 Selection of logical channels For example, when performing a new transmission, the MAC entity in the terminal device should perform the selection of the LCH. For example, the terminal device selects a logical channel that satisfies all of the following conditions for the uplink UL grant: If an LCH is configured with allowSCS-List, the set of subcarrier spacing index values ​​allowed in the allowSCS-List includes the subcarrier spacing index associated with the UL grant; and, If an LCH is configured with maxPUSCH-Duration, maxPUSCH-Duration is greater than or equal to the PUSCH transmission duration associated with the UL grant; and, If an LCH is configured with configuredGrantType1Allowed, configuredGrantType1Allowed is set to TRUE if the UL grant is Configured Grant Type 1; and, If an LCH is configured with allowedServingCells, allowedServingCells includes cell information associated with the UL grant; and, If an LCH is configured with an allowedCG-List, the allowedCG-List includes the configured grant index associated with the UL grant; and, If an LCH is configured with allowedPHY-PriorityIndex, allowedPHY-PriorityIndex includes the priority index associated with the dynamic UL grant; and, If an LCH is configured with allowedHARQ-mode, allowedHARQ-mode includes the uplink HARQ mode of the HARQ process associated with the UL grant. For example, "if an LCH is configured" may include / be replaced by: if configured for a logical channel. It should be noted that for LCP-related content, please refer to Section 5.4.3.1 (Logical Channel Prioritization) and / or Section 5.22.1.4.1 in 3GPP TS 38.321: "NR; Medium Access Control (MAC); Protocol specification". Section (Logical channel prioritization) will not be repeated here. 5. DSR (Delay status reporting) For example, the DSR process can be used by a terminal device to provide delay status to a network device. For example, the DSR is used to notify the network device of the remaining time information and the data volume information of the LCG. Exemplarily, DSR is a type of MAC CE, and thus may also be referred to as DSR MAC CE. For example, when certain trigger conditions are met, the terminal device sends a DSR to the network device to indicate to the network device the cache status and remaining time information of the delay emergency data of the terminal device uplink. After receiving the DSR, the network device can allocate uplink resources to the terminal device according to the DSR reported by the terminal device, so that the terminal device can perform uplink transmission. 5.1 DSR format Optionally, the DSR MAC CE format may include one or more of the following: DSR format; Truncated DSR format. For example, DSR has a variable size. Exemplarily, a format of a DSR is shown in FIG8 . For example, the DSR format is identified by a MAC PDU subheader or a LCID in a MAC subheader. Exemplarily, the fields in the DSR MAC CE are defined as follows: (1) LCGi field, or LCGi for short. Among them, for DSR, the LCGi field indicates whether the cache size field of logical channel group i exists, as follows (exemplarily): a. The LCGi field set to "1" indicates that the buffer size field and / or remaining time field of logical channel group i is to be reported. b. The LCGi field set to "0" indicates that the buffer size field and / or the remaining time field of the logical channel group i is not reported. For a truncated DSR, the LCGi field indicates whether logical channel group i has available data, as follows: a. The LCGi field set to "1" indicates that logical channel group i has available data. b. The LCGi field set to "0" indicates that there is no available data for logical channel group i. (2) Buffer Size field, also known as the buffer size field, or simply referred to as Buffer Size or BS or buffer size, is used to indicate the buffer size corresponding to the logical channel group. For example, this field is used to indicate the total amount of delayed emergency data in the LCG. For example, this field is used to identify the total amount of delayed emergency data in all logical channels of an LCG obtained after constructing a MAC protocol data unit (PDU) according to the data volume calculation process in the third generation partnership project (3GPP) technical specification (TS) 38.322 and TS 38.323. Exemplarily, for DSR, the length of the Buffer Size field is 8 bits. Exemplarily, for DSR, the arrangement order of the Buffer Size field is included according to the ascending order of LCGi. (3) Remaining time field, or remaining time field, or simply remaining time or remaining time, is used to indicate the remaining time corresponding to the logical channel group. For example, this field is used to indicate the minimum remaining time corresponding to the logical channel group. 2.2, DSR trigger: An event that triggers DSR is: there is data in the LCG whose remaining time is less than a threshold. For example, if an LCG is configured for DSR, the terminal device triggers DSR for the LCG when the following conditions are met: there is data in the LCG with a remaining time less than a threshold, and there is no DSR triggered for the LCG. It should be noted that this document takes BSR as an example for introduction, and BSR may also have other names, and the embodiment of the present application does not limit the name of BSR. It should be noted that this article takes DSR as an example for introduction. DSR may also have other names. Said there is no restriction. As an implementation manner, the DSR may include data volume information and remaining time information of delayed emergency data in some LCGs (eg, LCGs configured for DSR), and the BSR may include data volume information of data in all LCGs. In the scenario where the terminal device sends BSR and DSR to the network device, since BSR and DSR are not always included in the same MAC PDU, if the terminal device receives uplink resources allocated by the network device, the terminal device cannot determine whether the uplink resources are allocated by the network device due to the BSR or DSR received. In this case, if the terminal device restarts the retransmission BSR timer / retransmission DSR timer, it may cause BSR / DSR triggering and / or transmission delay, so that the network device cannot timely learn the cache status of the terminal device, affecting data transmission, for example, increasing data transmission delay. Specifically: If a retransmission timer mechanism (or a robustness mechanism of DSR) is also introduced for DSR, if the network device only receives BSR, if the terminal device restarts the retransmission DSR timer, it will cause the triggering and / or transmission delay of DSR. The network device may not know / cannot know in time that some LCG / LCH of the terminal device (for example, LCG / LCH associated with DSR) has time-delayed urgent data, and the UL resources scheduled by the network device may not meet the delay requirements of the time-delayed urgent data in the LCG / LCH associated with DSR; or, If the network device only receives the DSR, if the terminal device restarts the retransmission BSR timer, it will cause the triggering and / or sending of the BSR to be delayed. The network device may not know / cannot know in time that there is data in some LCG / LCH of the terminal device (for example, LCG / LCH not associated with DSR), and the base station may not schedule UL resources for it. In response to the above technical problems, the embodiment of the present application introduces "the sending status of the first BSR and the first DSR" and / or "the accommodation status of the first uplink resource" as a basis for judgment, to judge whether to restart the retransmission BSR timer / retransmission DSR timer, so as to avoid BSR / DSR triggering and / or transmission delay, and thus avoid data transmission delay. If DSR also requires a robustness mechanism, how to design the robustness mechanism of DSR? In response to the above technical problems, an embodiment of the present application provides a solution related to a retransmission DSR timer, in order to further improve the robustness of DSR transmission. If LCH1 in LCG1 of the terminal device obtains new data, triggering BSR, the terminal device sends BSR, starts or restarts the retransmission BSR timer, and the BSR contains the amount of data of LCG1. After the terminal device obtains uplink resources, if the uplink resources cannot meet the LCP mapping restrictions of LCH1 in LCG1, if the network device does not receive the BSR, if the terminal device restarts the retransmission BSR timer, it will cause the triggering and / or sending of BSR to be delayed. The network device may not know / cannot know in time that there is data in some LCG / LCH (for example, LCH1 in LCG1) of the terminal device, and the base station may not schedule UL resources for it, affecting the transmission of data, for example, increasing the data transmission delay. In response to the above technical problems, the present application determines whether to restart the retransmission BSR timer based on whether the first uplink resource meets the LCP mapping restriction of the LCH associated with the BSR, so as to avoid BSR triggering and / or transmission delay, thereby avoiding data transmission delay. Optionally, in the present application, restarting may include / replaced by: stopping. Optionally, restarting the retransmission BSR timer may include / replaced by stopping the retransmission BSR timer. Optionally, restarting the retransmission DSR timer may include / replaced by stopping the retransmission DSR timer. Optionally, in the present application, not restarting may include / replaced by: not stopping. Optionally, not restarting the retransmission BSR timer may include / replaced by not stopping the retransmission BSR timer. Optionally, not restarting the retransmission DSR timer may include / replaced by not stopping the retransmission DSR timer. The communication method provided in the embodiments of the present application will be described in detail below with reference to the accompanying drawings. However, it should be understood that this should not constitute any limitation on the execution subject of the method provided in the present application. As long as it is possible to run a program that records the code of the method provided in the embodiment of the present application, according to the method provided in the embodiment of the present application, it can be used as the execution subject of the method provided in the embodiment of the present application. For example, the terminal device shown in the following embodiment can also be replaced by a component in the terminal device, such as a chip, a chip system, or other functional modules that can call and execute programs. The network device can also be replaced by a component in the network device, such as a chip, a chip system, or other functional modules that can call and execute programs. It should be understood that in the present application, "when" and "if" both mean that corresponding processing will be performed under certain objective circumstances, and do not limit the time, nor do they require any judgment action when implementing, nor do they mean the existence of other limitations. It should be understood that the prior art may change with the evolution of technical solutions, and the technical solutions provided in this application are not limited to the provided prior art. It should be noted that different embodiments or some steps (for example, any one or more steps) in different embodiments in the present application can be combined with each other to form new embodiments. It should be noted that some steps or any one or more steps in different embodiments may include optional steps in a certain embodiment, mandatory steps in a certain embodiment, or steps in a certain embodiment. The optional steps and required steps are not limited in this application. It should be noted that, unless otherwise specified or there is no logical conflict, the terms and / or descriptions between different embodiments are consistent and can be referenced to each other. It should be noted that the sequence of the steps in the embodiments of the present application is not limited by the present application. It should be noted that the order of judging different conditions in the embodiments of the present application is not limited by the present application. It should be noted that the words “after” and “when” in this application do not strictly limit the time point. It should be noted that the nouns, terms, etc. involved in this application are merely examples and may also be other names, which are not limited in this application. It should be noted that 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 can 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. It should be noted that the message names between network elements or the names of parameters in the messages in the following embodiments of the present application are merely examples, and other names may be used in specific implementations, and the embodiments of the present application do not impose any specific limitations on this. It should be noted that this document uses terminal devices and / or network devices as examples, and the present application can also be applied to other devices. For example, the terminal device can be replaced by the first device, and the network device can be replaced by the second device. Fig. 9 is a schematic flow chart of a communication method 500 provided in an embodiment of the present application. As shown in Fig. 9, the method 500 may include the following S510 to S550. Each step in the method 500 is described in detail below. Optionally, S510, the terminal device sends a first BSR to the network device. For example, the first BSR is used to provide the network device with information on the amount of UL data. Optionally, the present application may also include: the terminal device triggers a BSR or a first BSR. Optionally, BSR may be a general term. Optionally, the first BSR may be a specific BSR. Optionally, the present application may also include: the terminal device obtains a second uplink resource. For example, the second uplink resource may be a resource allocated by the network device or a resource that may be used to send a BSR or a resource that may accommodate a BSR. Optionally, the terminal device may obtain the second uplink resource after triggering the BSR or the first BSR. Alternatively, the terminal device may obtain the second uplink resource before triggering the BSR or the first BSR, or at the same time as triggering the BSR or the first BSR, without limitation. Optionally, the present application may further include: the terminal device generates a first BSR. For example, the terminal device sends the first BSR on the second uplink resource. For example, the network device receives a first BSR from the terminal device. Optionally, the network device allocates transmission resources to the terminal device according to the first BSR. Optionally, the terminal device sends a first BSR, or the terminal device generates a first BSR, or the second uplink resource can accommodate the first BSR, or the second uplink resource can accommodate the first BSR and the MAC subheader of the first BSR, and the terminal device starts or restarts the retransmission BSR timer. For example, the retransmission BSR timer may also be called a retransmission BSR timer, or a retxBSR-Timer. For example, the BSR retransmission timer can prevent the terminal device from sending a BSR (eg, a first BSR) but failing to receive resources (eg, a first uplink resource). For example, a retransmission BSR timer is associated with the BSR. For example, the retransmission BSR timer times out and there is data in the LCH (or, there is data in the LCH in the LCG), and the terminal device triggers the BSR or the first BSR. Optionally, S520, the terminal device sends a first DSR to the network device. For example, the first DSR is used to provide the network device with information on the amount of data and information on the remaining time. Optionally, the present application may also include: the terminal device triggers DSR or the first DSR. Optionally, DSR may be a general term. Optionally, the first DSR may be a specific DSR. Optionally, the present application may also include: the terminal device obtains a third uplink resource. For example, the third uplink resource may be a resource allocated by the network device or a resource that may be used to send the DSR or a resource that may accommodate the DSR. Optionally, the terminal device may obtain the third uplink resource after triggering the DSR or the first DSR. Before triggering DSR or the first DSR, or while triggering DSR or the first DSR, the third uplink resource is obtained without restriction. Optionally, the present application may also include: the terminal device generates a first DSR. For example, the terminal device sends the first DSR on the third uplink resource. For example, the network device receives a first DSR from the terminal device. Optionally, the network device allocates transmission resources to the terminal device according to the first DSR. Optionally, the terminal device sends the first DSR, or the terminal device generates the first DSR, or the third uplink resource can accommodate the first DSR, or the third uplink resource can accommodate the first DSR and the MAC subheader of the first DSR, and the terminal device starts or restarts the retransmission DSR timer. For example, the retransmission DSR timer may also be called a retransmission DSR timer, or a retxDSR-Timer. For example, the DSR retransmission timer can prevent the terminal device from sending a DSR (eg, a first DSR) but failing to receive resources (eg, a first uplink resource). For example, a retransmit DSR timer is associated with the DSR. For example, the retransmission DSR timer times out, and there is data / delay emergency data in the LCH associated with the DSR (or there is data / delay emergency data in the LCH in the LCG associated with the DSR), and the terminal device triggers the DSR or the first DSR. S530, the terminal device obtains the first uplink resource. For example, the first uplink resource is a new transmission resource. Optionally, the first uplink resource is dynamically authorized. Optionally, in a possible implementation, after the network device obtains the first BSR, it sends a first uplink resource to the terminal device. Optionally, in another possible implementation, after the network device obtains the first DSR, it sends the first uplink resource to the terminal device. Optionally, in another possible implementation, after the network device obtains the first BSR and the first DSR, it sends the first uplink resource to the terminal device. S540: The terminal device executes S540A or S540B. S540A, the first condition is met and the terminal device restarts the BSR retransmission timer. S540B, the second condition is met and the terminal device does not restart the retransmission BSR timer. For example, satisfying the second condition may include / be replaced by: not satisfying the first condition. It should be noted that S540A and S540B may be parallel solutions. For example, if the first condition is met, the terminal device executes S540A and the terminal device does not execute S540B, which is indicated by a dotted line in FIG. 9 . Optionally, S550, the terminal device executes S550A or S550B. S550A, the third condition is met and the terminal device restarts the DSR retransmission timer. S550B, if the fourth condition is met or the first condition is not met, the terminal device does not restart the retransmission DSR timer. For example, satisfying the fourth condition may include / be replaced by: not satisfying the third condition. It should be noted that S550A and S550B may be parallel solutions. For example, if the third condition is met, the terminal device executes S550A and does not execute S550B, which is indicated by a dotted line in FIG. 9 . It should be noted that the present application does not limit the execution order of any two or more of S530, S540, and S550; they may be executed sequentially or simultaneously without limitation. It should be noted that S530 and S550 can be used as an independent embodiment and are not dependent on other steps. Optionally, the first condition is associated with the sending condition of the first BSR and the first DSR and / or the first accommodation condition of the first uplink resource. Optionally, the first uplink resource may be sent by the network device after receiving the first BSR, or after receiving the first DSR, or after receiving the first BSR and the first DSR. The present application does not limit whether the first uplink resource is sent by the network device in response to the received first BSR, in response to the received first DSR, or in response to the received first BSR and the first DSR. Optionally, the first uplink resource may be sent by the network device in response to a received first BSR, or in response to a received first DSR, or in response to a received first BSR and a first DSR. It should be noted that, even if the network device receives the first BSR and / or the first DSR, the first uplink resource is not necessarily sent in response to the received first BSR and / or the first DSR, and this application does not limit this. Exemplarily, the sending conditions of the first BSR and the first DSR may include / be replaced by any one or more of the following: whether the first BSR and the first DSR are sent through the same MAC PDU, whether the first BSR and the first DSR are included in the same MAC PDU, Whether the uplink resource meets the first LCP mapping restriction, or whether the first uplink resource meets the second LCP mapping restriction. Exemplarily, the sending conditions of the first BSR and the first DSR may include / be replaced by any one or more of the following: whether the first uplink resource meets the first LCP mapping restriction, or whether the first uplink resource meets the second LCP mapping restriction. For example, the sending conditions of the first BSR and the first DSR may include / be replaced by any one or more of the following: the first BSR and the first DSR are included in the same MAC PDU; the first BSR and the first DSR are not included in the same MAC PDU; the first uplink resource satisfies the first LCP mapping restriction; the first uplink resource does not satisfy the first LCP mapping restriction; the first uplink resource satisfies the second LCP mapping restriction; or, the first uplink resource does not satisfy the second LCP mapping restriction. For example, the first BSR and the first DSR are included in the same MAC PDU, which may include / be understood as: the second uplink resource and the third uplink resource are the same resource. For example, the first BSR and the first DSR are not included in the same MAC PDU, which may include / be understood as: the second uplink resource and the third uplink resource are different resources. Exemplarily, the first accommodation condition of the first uplink resource may include any one or more of the following: whether the first uplink resource can accommodate the data in the LCH in all LCGs; or, whether the first uplink resource can accommodate the data in all LCHs; whether the first uplink resource satisfies the first LCP mapping restriction; or, whether the first uplink resource satisfies the second LCP mapping restriction. For example, the first accommodation situation of the first uplink resource may include any one or more of the following: the first uplink resource can accommodate data in the LCHs in all LCGs; the first uplink resource cannot accommodate data in the LCHs in all LCGs; the first uplink resource can accommodate data in all LCHs; the first uplink resource cannot accommodate data in all LCHs; the first uplink resource satisfies the first LCP mapping restriction; the first uplink resource does not satisfy the first LCP mapping restriction; the first uplink resource satisfies the second LCP mapping restriction; or, the first uplink resource does not satisfy the second LCP mapping restriction. For example, data in LCH in LCG may include / be replaced by: data in LCG. For example, LCHs in all LCGs may include / be replaced by: all LCHs in all LCGs. For example, LCP mapping restriction may include / be replaced by: LCH mapping restriction, LCH restriction, or LCP restriction. For example, all LCHs may include LCHs in all LCGs, or all LCHs may include all LCHs in all LCGs and all LCHs that do not belong to any LCG. Optionally, in the first example, the first condition is associated with the sending status of the first BSR and the first DSR. Optionally, in some implementations, the first condition may include: Condition 1. For example, condition 1 may include: the first BSR and the first DSR are included in the same MAC PDU. Optionally, if the first condition is not met, such as the first BSR and the first DSR are contained in different MAC PDUs, the retransmission BSR timer is not restarted. Optionally, in some other implementations, the first condition may include condition 2 and / or condition 3. For example, condition 2 may include: the first uplink resource does not satisfy the first LCP mapping restriction. For example, the first LCP mapping restriction corresponds to one of the LCH associated with the XR service, the LCG associated with the XR service, and the LCH in the LCG associated with the XR service, or corresponds to one of the LCH associated with the first DSR, the LCG associated with the first DSR, and the LCH in the LCG associated with the first DSR, or corresponds to one of the LCH associated with the DSR, the LCG associated with the DSR, and the LCH in the LCG associated with the DSR. For example, the network device may configure the LCG reported in the DSR. The first DSR may be a DSR that includes cache status information and / or remaining time information of a specific LCG. For example, the network device configures the LCGs reported in the DSR to include LCG 0 to LCG 2, wherein LCG 1 and LCG 2 have urgent data, and the first DSR may include LCG 1 data volume information and / or time information, as well as LCG 2 data volume information and / or time information. For example, the LCGs associated with the first DSR may be LCG 1 and LCG 2. For example, the LCGs associated with the DSR may be LCG 0 to LCG 2. For example, the first LCP mapping restriction may include any one or more of the following: LCP mapping restriction of the LCH associated with the XR service, LCP mapping restriction of the LCG associated with the XR service, LCP mapping restriction of the LCH in the LCG associated with the XR service, LCP mapping restriction of the LCH associated with the first DSR, LCP mapping restriction of the LCG associated with the first DSR, LCP mapping restriction of the LCH in the LCG associated with the first DSR, LCP mapping restriction of the LCH associated with the DSR, LCP mapping restriction of the LCG associated with the DSR, or LCP mapping restriction of the LCH in the LCG associated with the DSR. For example, an LCH may include / replace one or more or all LCHs. For example, an LCG may include / replace one or more or all LCGs. For example, an LCH in an LCG may include / replace one or more or all LCGs. or multiple or all LCHs). For example, the LCP mapping restriction of the LCH may include / replace with: the LCP mapping restriction corresponding to the LCH. For example, the LCP mapping restriction of the LCG may include / replace with: the LCP mapping restriction corresponding to the LCG. For example, the LCH mapping restriction in the LCG may include / replace with: the LCP mapping restriction corresponding to the LCH in the LCG. For example, the LCH associated with the DSR may include / replace any one or more of the following: an LCH that can be used for the DSR, an LCH that can be reported in the DSR, a network device configured to be used for the DSR, or a network device configured to be reported in the DSR. For example, the LCG associated with the DSR may include / replace any one or more of the following: an LCG that can be used for the DSR, an LCG that can be reported in the DSR, a network device configured to be used for the DSR, or a network device configured to be reported in the DSR. For example, the LCH in the LCG associated with the DSR may include / replace any one or more of the following: an LCH in the LCG that can be used for the DSR, an LCH in the LCG that can be reported in the DSR, a network device configured to be used for the LCG for the DSR, or a network device configured to be reported in the LCG. For example, the LCH associated with the first DSR may include / be replaced by any one or more of the following: an LCH in the first DSR including cache status information and / or remaining time information; an LCH in the first DSR indicating the existence of cache status information and / or remaining time information; an LCH in the first DSR including cache status information greater than or equal to 0; or an LCH in the first DSR including remaining time information greater than or equal to 0. For example, the LCG associated with the first DSR may include / be replaced by any one or more of the following: an LCG in the first DSR including cache status information and / or remaining time information; an LCG in the first DSR indicating the existence of cache status information and / or remaining time information; an LCG in the first DSR including cache status information greater than or equal to 0; or an LCG in the first DSR including remaining time information greater than or equal to 0. For example, the LCH in the LCG associated with the first DSR may include / be replaced by any one or more of the following: the LCH in the LCG in the first DSR that includes cache status information and / or remaining time information; the LCH in the LCG in the first DSR that indicates the existence of cache status information and / or remaining time information; the LCH in the LCG in the first DSR that includes cache status information greater than or equal to 0; or, the LCH in the LCG in the first DSR that includes remaining time information greater than or equal to 0. For example, the first uplink resource does not meet the first LCP mapping restriction, which may include / be understood as: the first uplink resource cannot carry / cannot carry any one or more of the following: LCH associated with the XR service or the first DSR or DSR, or LCG associated with the XR service or the first DSR or DSR, or data in the LCH in the LCG associated with the XR service or the first DSR or DSR. Optionally, in this case, the terminal device can determine that the first uplink resource is not a resource allocated by the network device for the first DSR, and therefore, it is more likely to be a resource allocated for the first BSR, and the terminal device restarting the BSR retransmission timer will not cause BSR transmission delay. Optionally, if the first condition is not met, such as the first uplink resource meets the first LCP mapping restriction, the first uplink resource can carry data in the LCH associated with the XR service or the first DSR or DSR, or the LCG associated with the XR service or the first DSR or DSR, or the LCH in the LCG associated with the XR service or the first DSR or DSR, and the terminal device does not restart the retransmission BSR timer. It should be noted that this application does not limit the specific content of the LCP mapping restriction. For example, condition 3 may include: the first uplink resource satisfies the second LCP mapping restriction. For example, the second LCP mapping restriction corresponds to the LCH associated with the first BSR, or the LCG associated with the first BSR, or the LCH in the LCG associated with the first BSR; or, corresponds to the LCH associated with the BSR, or the LCG associated with the BSR, or the LCH in the LCG associated with the BSR. For example, LCG0 to LCG7 (or all LCGs) may report data volume information in the BSR. For example, the first BSR may include LCG 1 data volume information and LCG 2 data volume information. For example, the LCGs associated with the first BSR may be LCG 1 and LCG 2. For example, the LCGs associated with the BSR may be LCG 0 to LCG 7. For example, the second LCP mapping restriction corresponds to the LCH of the terminal device, or the LCG of the terminal device, or the LCH in the LCG of the terminal device. For example, the second LCP mapping restriction corresponds to LCH, or LCG, or LCH in LCG. For example, an LCH may include / replace one or more or all LCHs. For example, an LCG may include / replace one or more or all LCGs. For example, an LCH in an LCG may include / replace one or more or all LCHs in an LCG (or one or more or all LCHs). For example, the second LCP mapping restriction may include any one or more of the following: an LCP mapping restriction of an LCH associated with the first BSR, an LCP mapping restriction of an LCG associated with the first BSR, an LCP mapping restriction of an LCH in an LCG associated with the first BSR, an LCP mapping restriction of an LCH associated with a BSR, an LCP mapping restriction of an LCG associated with a BSR, an LCP mapping restriction of an LCH in an LCG associated with a BSR, an LCP mapping restriction of an LCH of a terminal device, an LCP mapping restriction of an LCG of a terminal device, and an LCP mapping restriction of a terminal device. LCP mapping restrictions of LCHs in an LCG of a device, LCP mapping restrictions of LCHs, LCP mapping restrictions of LCGs, or LCP mapping restrictions of LCHs in an LCG. For example, the LCH associated with the BSR may include / replace any one or more of the following: an LCH that can be used for the BSR, an LCH that can be reported in the BSR, a network device configured LCH that can be used for the BSR, or a network device configured LCH that can be reported in the BSR. For example, the LCG associated with the BSR may include / replace any one or more of the following: an LCG that can be used for the BSR, an LCG that can be reported in the BSR, a network device configured LCG that can be used for the BSR, or a network device configured LCG that can be reported in the BSR. For example, the LCH in the LCG associated with the BSR may include / replace any one or more of the following: an LCH in the LCG that can be used for the BSR, or an LCH in the LCG that can be reported in the BSR, a network device configured LCH in the LCG that can be used for the BSR, or a network device configured LCH in the LCG that can be reported in the BSR. For example, the LCH associated with the first BSR may include / replaced with any one or more of the following: an LCH including cache status information in the first BSR; an LCH indicating the presence of cache status information in the first BSR; or an LCH including cache status information greater than or equal to 0 in the first BSR. For example, the LCG associated with the first BSR may include / replaced with any one or more of the following: an LCG including cache status information in the first BSR; an LCG indicating the presence of cache status information in the first BSR; or an LCG including cache status information greater than or equal to 0 in the first BSR. For example, the LCH in the LCG associated with the first BSR may include / replaced with any one or more of the following: an LCH in the LCG including cache status information in the first BSR; an LCH in the LCG indicating the presence of cache status information in the first BSR; or an LCH in the LCG including cache status information greater than or equal to 0 in the first BSR. For example, the first uplink resource satisfies the second LCP mapping restriction, which may include / be understood as: the first uplink resource may carry / may carry any one or more of the following: data in the LCH associated with the first BSR or BSR, or the LCG associated with the first BSR or BSR, or the LCH in the LCG associated with the first BSR or BSR, the LCH of the terminal device, or the LCG of the terminal device, or the LCH in the LCG of the terminal device, or, the LCH, or the LCG, or the LCH in the LCG. Optionally, in this case, it is more likely that the first uplink resource is the resource allocated by the network device for the first BSR, so restarting the retransmission BSR timer by the terminal device will not cause BSR transmission delay. Optionally, if the first condition is not met, such as the first uplink resource does not meet the second LCP mapping restriction, the first uplink resource cannot carry data in the first BSR or LCH associated with BSR, or the first BSR or LCG associated with BSR, or the LCH in the first BSR or LCG associated with BSR, and the terminal device does not restart the BSR retransmission timer. Optionally, according to conditions 2 and 3, it can be determined with a greater probability that the first uplink resource is the resource allocated by the network device for the first BSR, or it can be determined that the first uplink resource can carry data of the first BSR or the LCH associated with the BSR, or the first BSR or the LCG associated with the BSR, or the LCH in the first BSR or the LCG associated with the BSR, and the terminal device restarting the BSR retransmission timer will not cause BSR transmission delay. Optionally, if the first condition is not met, such as the first uplink resource meets the first LCP mapping restriction and / or does not meet the second LCP mapping restriction, the terminal device does not restart the retransmission BSR timer. Optionally, the first condition includes condition 2 and / or condition 3, and the first condition may further include condition 5. For example, condition 5 may include: the first BSR and the first DSR are not included in the same MAC PDU. Optionally, in the second example, the first condition is associated with a first accommodation situation of the first uplink resource. Optionally, in some implementations, the first condition may include condition 6. For example, condition 6 may include: the first uplink resource can accommodate data in LCHs in all LCGs, or the first uplink resource can accommodate data in all LCHs. Optionally, in this case, it can be determined with a high probability that the first uplink resource is a resource allocated by the network device for the first BSR, or the first uplink resource is a resource allocated by the network device for the first BSR and the first DSR, or the first uplink resource can carry data in the LCH associated with the first BSR. Therefore, restarting the retransmission BSR timer by the terminal device will not cause BSR transmission delay. Optionally, if the first condition is not met, such as the first uplink resource cannot accommodate the data in the LCH in all LCGs, the terminal device does not restart the retransmission BSR timer. Optionally, in the third example, the first condition is associated with the sending condition of the first BSR and the first DSR, and the first accommodation condition of the first uplink resource. Optionally, in some implementations, the first condition may include: condition 5 and condition 6. Optionally, in this case, it can be determined that the first uplink resource is a resource allocated by the network device for the first BSR, or that the first uplink resource can carry data in the LCH associated with the first BSR. Therefore, restarting the retransmission BSR timer of the terminal device will not cause the BSR Transmission delay. Optionally, if the first condition is not met, such as the first BSR and the first DSR are not contained in the same MAC PDU, and / or the first uplink resource cannot accommodate the data in the LCH in all LCGs, the terminal device does not restart the retransmission BSR timer. Optionally, in some other implementations, the first condition may include: condition 7 and condition 6. For example, condition 7 may include: the first uplink resource satisfies the first LCP mapping restriction. For example, the first uplink resource satisfies the first LCP mapping restriction and may include / be understood as: the first uplink resource can carry / may carry any one or more of the following: LCH associated with the XR service or the first DSR or DSR, or LCG associated with the XR service or the first DSR or DSR, or data in the LCH in the LCG associated with the XR service or the first DSR or DSR. Optionally, in this case, the terminal device can determine with a high probability that the first uplink resource is a resource allocated by the network device for the first DSR. Therefore, restarting the DSR retransmission timer by the terminal device will not cause DSR transmission delay. Optionally, in this case, it can be determined that the first uplink resource is a resource allocated by the network device for the first BSR, or the first uplink resource can carry data in the LCH associated with the first BSR, or the LCG associated with the first BSR, or the LCH in the LCG associated with the first BSR. Therefore, restarting the retransmission BSR timer will not cause a delay in the transmission of the first BSR. Optionally, if the first condition is not met, such as the first uplink resource does not meet the first LCP mapping restriction, and / or the first uplink resource cannot accommodate the data in the LCH in all LCGs, the retransmission BSR timer is not restarted. In some further implementations, the first condition may include condition 5, condition 7, and condition 6. For example, the first BSR and the first DSR are not included in the same MAC PDU, the first uplink resource meets the first LCP mapping restriction, and the first uplink resource can accommodate the data in the LCH in all LCGs. In this case, it can be more accurately determined that the first uplink resource is the resource allocated by the network device for the first BSR. In other words, the first uplink resource can carry the data in the LCH associated with the first BSR. Therefore, restarting the retransmission BSR timer will not cause a delay in the transmission of the first BSR. Optionally, if the first condition is not met, such as the first BSR and the first DSR are not included in the same MAC PDU, the first uplink resource does not meet the first LCP mapping restriction, and / or the first uplink resource cannot accommodate the data in the LCH in all LCGs, the retransmission BSR timer will not be restarted. Optionally, the second condition may include at least one of the following: condition 5, condition 7, condition 8, condition 4. For example, condition 8 may include: the first uplink resource does not satisfy the second LCP mapping restriction. For example, the first uplink resource satisfies the second LCP mapping restriction, which may include / be understood as: the first uplink resource cannot carry / cannot carry any one or more of the following: data in the LCH associated with the first BSR or BSR, or the LCG associated with the first BSR or BSR, or the LCH in the LCG associated with the first BSR or BSR, the LCH of the terminal device, or the LCG of the terminal device, or the LCH in the LCG of the terminal device, or the LCH, or the LCG, or the LCH in the LCG. Optionally, in this case, it is more likely that the first uplink resource is not the resource allocated by the network device for the first BSR. Therefore, the terminal device not restarting the BSR retransmission timer will not cause BSR transmission delay. For example, condition 4 may include: the first uplink resource cannot accommodate data in the LCHs in all LCGs, or the first uplink resource cannot accommodate data in all LCHs. For example, based on the first to third examples or possible implementations, the retransmission BSR timer is not restarted, and the second condition that needs to be met may include at least one of the following: The first BSR and the first DSR are not included in the same MAC PDU; The first uplink resource satisfies the first LCP mapping restriction; The first uplink resource does not meet the second LCP mapping restriction; or, The first uplink resource cannot accommodate all LCHs in the LCG or data in all LCHs. For example, the content of the second condition can refer to the description of the content of the first condition in the above example, which will not be repeated for the sake of brevity. Therefore, in an embodiment of the present application, the terminal device obtains the first uplink resource, and then determines whether to restart the retransmission BSR timer based on the sending status of the first BSR and the first DSR and / or the first accommodation status of the first uplink resource, so as to avoid always restarting the retransmission BSR timer after obtaining the first uplink resource, resulting in BSR transmission delay, thereby affecting data transmission. In the embodiment of the present application, the terminal device may determine whether to restart the DSR timer based on a third condition associated with the transmission status of the first BSR and the first DSR and / or the second accommodation status of the first uplink resource. For example, if the third condition is met, the terminal device restarts the retransmission DSR timer. For example, if the third condition is not met, the retransmission DSR timer is not restarted. Exemplarily, the second accommodation condition of the first uplink resource may include any one or more of the following: whether the first uplink resource can accommodate The data or delay-critical data in all LCHs associated with the XR service, or the LCG associated with the XR service, or one of the LCHs in the LCG associated with the XR service, or, whether the first uplink resource can accommodate the data or delay-critical data in all LCHs associated with the first DSR, or the LCG associated with the first DSR, or one of the LCHs in the LCG associated with the first DSR, or, whether the first uplink resource can accommodate the data or delay-critical data in all LCHs associated with the DSR, or the LCG associated with the DSR, or one of the LCHs in the LCG associated with the DSR. For example, the second accommodation situation of the first uplink resource may include any one or more of the following: the first uplink resource can accommodate all data or time-delayed emergency data in the LCH associated with the XR service or the LCG associated with the XR service or the LCH in the LCG associated with the XR service; the first uplink resource cannot accommodate all data or time-delayed emergency data in the LCH associated with the XR service or the LCG associated with the XR service or the LCH in the LCG associated with the XR service; the first uplink resource can accommodate all data or time-delayed emergency data in the LCH associated with the first DSR or the LCG associated with the first DSR or the LCH in the LCG associated with the first DSR; the first uplink resource cannot accommodate all data or time-delayed emergency data in the LCH associated with the first DSR or the LCG associated with the first DSR The first uplink resource can accommodate all the data or delayed emergency data in the LCH associated with the DSR or the LCG associated with the DSR or the LCH in the LCG associated with the DSR, the first uplink resource cannot accommodate all the data or delayed emergency data in the LCH associated with the DSR or the LCG associated with the DSR or the LCH in the LCG associated with the DSR, the first uplink resource satisfies the first LCP mapping restriction; the first uplink resource does not satisfy the first LCP mapping restriction; the first uplink resource satisfies the second LCP mapping restriction; or, the first uplink resource does not satisfy the second LCP mapping restriction. It should be understood that the terminal device's determination of whether to restart the retransmission DSR timer based on the third condition (and / or the fourth condition) can be used as an independent solution, or it can be used in combination with the solution of determining whether to restart the retransmission BSR timer based on the first condition (and / or the second condition) in the aforementioned example. Optionally, in Example 1, the third condition is associated with the sending status of the first BSR and the first DSR. Optionally, in some implementations, the third condition may include: Condition 1. Optionally, in the above implementation, combined with the scheme of restarting the retransmission BSR timer, the terminal device may restart the retransmission BSR timer and the retransmission DSR timer when the first BSR and the first DSR are included in the same MAC PDU. Optionally, if the third condition is not met, such as the first BSR and the first DSR are not included in the same MAC PDU, the retransmission DSR timer is not restarted to avoid DSR transmission delay. Optionally, in some other implementations, the third condition may include: condition 7 and / or condition 8. Optionally, if the third condition is not met, such as the first uplink resource does not meet the first LCP mapping restriction, the first uplink resource cannot carry the LCH associated with the XR service or the first DSR or DSR, or the LCG associated with the XR service or the first DSR or DSR, or the data in the LCH in the LCG associated with the XR service or the first DSR or DSR, the terminal device does not restart the retransmission DSR timer. Optionally, if the third condition is met, such as the first uplink resource does not meet the second LCP mapping restriction, the first uplink resource cannot carry the data in the LCH associated with the first BSR or BSR, or the LCG associated with the first BSR or BSR, or the LCH in the LCG associated with the first BSR or BSR, or the first uplink resource can carry the data in the LCH of the terminal device, or the LCG of the terminal device, or the LCH in the LCG of the terminal device. Optionally, in this case, it can be determined that the first uplink resource is not a resource allocated by the network device for the first BSR, but is more likely to be a resource allocated by the network device for the first DSR, and restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. Optionally, the third condition is not met, such as the first uplink resource meets the second LCP mapping restriction, the first uplink resource can carry data in the LCH associated with the first BSR or BSR, or the LCG associated with the first BSR or BSR, or the LCH in the LCG associated with the first BSR or BSR, and the terminal device does not restart the retransmission DSR timer to avoid DSR transmission delay. Optionally, according to conditions 7 and 8, it can be determined with a greater probability that the first uplink resource is the resource allocated by the network device for the first DSR, or it can be determined that the first uplink resource can carry data of the first DSR or the LCH associated with the first DSR, or the first BSR or the LCG associated with the BSR, or the LCH in the first BSR or the LCG associated with the BSR, and restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. Optionally, if the third condition is not met, such as the first uplink resource does not meet the first LCP mapping restriction and / or meets the second LCP mapping restriction, the retransmission DSR timer is not restarted to avoid DSR transmission delay. Optionally, the third condition includes condition 7 and / or condition 8, and the third condition can also be condition 5. Optionally, in Example 2, the third condition is associated with the second accommodation situation of the first uplink resource. Optionally, in some implementations, the third condition may include condition 14. For example, condition 14 may include: the first uplink resource can accommodate data or delay emergency data in all LCHs associated with the XR service or LCGs associated with the XR service or LCHs in LCGs associated with the XR service, or, the first uplink resource can accommodate data or delay emergency data in all LCHs associated with the first DSR or LCGs associated with the first DSR or LCHs in LCGs associated with the first DSR, or, the first uplink resource can accommodate data or delay emergency data in all LCHs associated with the DSR or LCGs associated with the DSR or LCHs in LCGs associated with the DSR. For example, delayed emergency data, or, emergency data may include / be: data with a remaining time less than a first threshold. For example, the first threshold may be configured by the network device for the terminal device, or may be pre-configured, or may be predetermined by a protocol, without limitation. For example, the first threshold may be per LCG. Optionally, in this case, it is highly likely that the first uplink resource is a resource allocated by the network device for the first DSR, or the first uplink resource is a resource allocated by the network device for the first BSR and the first DSR. In other words, the first uplink resource can carry data in the LCH associated with the first DSR. Therefore, restarting the retransmission DSR timer by the terminal device will not cause DSR transmission delay. Optionally, if the third condition is not met, such as the first uplink resource cannot accommodate data in all LCHs associated with XR services, LCGs associated with XR services, or LCHs in LCGs associated with XR services, or carries emergency data, the retransmission BSR timer is not restarted. Optionally, in Example 3, the third condition is associated with the sending condition of the first BSR and the first DSR, and the second accommodation condition of the first uplink resource. Optionally, in some implementations, the third condition may include: condition 5 and condition 14. For example, the third condition may include: the first BSR and the first DSR are not included in the same MAC PDU, and the first uplink resource can accommodate data in the LCH associated with all XR services, the LCG associated with the XR services, or the LCH in the LCG associated with the XR services, or carry emergency data. Optionally, in this case, it can be determined that the first uplink resource is a resource allocated by the network device for the first DSR, or the first uplink resource can carry data in the LCH associated with the first DSR, or the LCG associated with the first DSR, or the LCH in the LCG associated with the first DSR. Therefore, restarting the retransmission DSR timer will not cause DSR transmission delay. Optionally, if the third condition is not met, such as the first BSR and the first DSR are not contained in the same MAC PDU, and the first uplink resource cannot accommodate the data in all LCHs associated with the XR service, the LCG associated with the XR service, or the LCH in the LCG associated with the XR service, or carry emergency data, the retransmission DSR timer will not be restarted. Optionally, in some other implementations, the third condition may include condition 3 and condition 14. For example, the third condition may include that the first uplink resource satisfies the second LCP mapping restriction, and the first uplink resource can accommodate data in the LCH associated with all XR services, the LCG associated with the XR services, or the LCH in the LCG associated with the XR services, or carry emergency data. Optionally, in this case, it can be determined that the first uplink resource is a resource allocated by the network device for the first DSR. In other words, the first uplink resource can carry data in the LCH associated with the first DSR. Therefore, restarting the retransmission DSR timer will not cause a delay in the transmission of the first DSR. Optionally, if the third condition is not met, such as the first uplink resource does not meet the second LCP mapping restriction, and / or the first uplink resource cannot accommodate all LCHs associated with the XR service, the LCG associated with the XR service, or the data in the LCH in the LCG associated with the XR service, or emergency data, the retransmission DSR timer will not be restarted to avoid DSR transmission delay. Optionally, in some further implementations, the third condition may include condition 5, condition 3, and condition 14. For example, the third condition may include: the first BSR and the first DSR are not included in the same MAC PDU, the first uplink resource satisfies the second LCP mapping restriction, and the first uplink resource can accommodate all LCHs associated with XR services, LCGs associated with XR services, or data in LCHs in LCGs associated with XR services, or emergency data. Optionally, in this case, it can be more accurately determined that the first uplink resource is a resource allocated by the network device for the first DSR. In other words, the first uplink resource can carry data in the LCH associated with the first DSR. Therefore, restarting the retransmission DSR timer will not cause DSR transmission delay. Optionally, if the third condition is not met, such as when the first BSR and the first DSR are not included in the same MAC PDU, the first uplink resource does not meet the second LCP mapping restriction, and / or the first uplink resource cannot accommodate all LCHs associated with the XR service, the LCG associated with the XR service, or the data in the LCH in the LCG associated with the XR service, or emergency data, the retransmission DSR timer will not be restarted to avoid DSR transmission delay. Optionally, in some further implementations, the third condition may include condition 5, condition 7, and condition 14. Optionally, the fourth condition may include at least one of the following: condition 5, condition 2, condition 3, condition 15. For example, condition 15 may include: the first uplink resource cannot accommodate all LCHs associated with the XR service or LCGs associated with the XR service or data in the LCH in the LCG associated with the XR service or delayed emergency data, or the first uplink resource cannot accommodate all Data or time-delayed emergency data in the LCH associated with the first DSR or the LCG associated with the first DSR or the LCH in the LCG associated with the first DSR, or the first uplink resource cannot accommodate all data or time-delayed emergency data in the LCH associated with the DSR or the LCG associated with the DSR or the LCH in the LCG associated with the DSR. For example, based on the above examples 1 to 3 or each possible implementation, the retransmission DSR timer is not restarted, and the fourth condition that needs to be met may include at least one of the following: The first BSR and the first DSR are not included in the same MAC PDU; The first uplink resource does not satisfy the first LCP mapping restriction; The first uplink resource meets the second LCP mapping restriction; The first uplink resource cannot accommodate all data or delayed emergency data in the LCH in the LCG associated with the DSR or the first DSR. For example, the content of the fourth condition can refer to the description of the content of the third condition in the above example, which will not be repeated for the sake of brevity. Therefore, in an embodiment of the present application, the terminal device obtains the first uplink resource, and then determines whether to restart the retransmission DSR timer based on the sending status of the first BSR and the first DSR and / or the second accommodation status of the first uplink resource, so as to avoid always restarting the retransmission DSR timer after obtaining the first uplink resource, resulting in DSR transmission delay, thereby affecting data transmission. Optionally, the terminal device triggers the retransmission of BSR and DSR respectively through the retransmission BSR timer and the retransmission DSR timer, so as to avoid mutual interference between the BSR and DSR retransmissions. In the embodiment of the present application, in order to improve the robustness of DSR, a mechanism related to the retransmission DSR timer can be introduced. It should be noted that in the present application, any one or more contents related to the retransmission DSR timer can be used as an independent implementation example and is not dependent on other contents and / or steps. Optionally, if the fifth condition is met, the terminal device triggers DSR or the first DSR. For example, the fifth condition includes: the retransmission DSR timer expires, and condition 16. For example, condition 16 may include: the presence of data or time-delayed emergency data in the LCH associated with the XR service, the LCG associated with the XR service, or the LCH in the LCG associated with the XR service, or the presence of data or time-delayed emergency data in the LCH associated with the first DSR, the LCG associated with the first DSR, or the LCH in the LCG associated with the first DSR, or the presence of data or time-delayed emergency data in the LCH associated with the DSR, the LCG associated with the DSR, or the LCH in the LCG associated with the DSR. It should be understood that the relevant solution for the terminal device to trigger the DSR or the first DSR based on the fifth condition may be an independent technical solution or may be combined with the above embodiments. Optionally, in some embodiments, the terminal device sends a first BSR, or the terminal device generates a first BSR, or the second uplink resource can accommodate the first BSR, or the second uplink resource can accommodate the first BSR and the MAC subheader of the first BSR, and the terminal device starts or restarts the retransmission DSR timer. Optionally, in some embodiments, the terminal device may obtain the first confirmation information. For example, the first confirmation information is associated with the first DSR. For example, the first confirmation information is used to indicate restarting or stopping the retransmission DSR timer. For example, after the terminal device obtains the first confirmation information, the terminal device can restart or stop the retransmission DSR timer. Optionally, the first confirmation information may be carried in MAC CE. It should be noted that the solution related to the first confirmation information can be an independent technical solution, or can be combined with the above embodiments. Optionally, in some embodiments, for the DSR or the first DSR triggered by a retransmission DSR timer (or, due to the expiration of the retransmission DSR timer), the LCH that triggers the DSR or the first DSR may be: when the DSR or the first DSR is triggered, the LCH associated with the XR service, the LCG associated with the XR service, or the LCH in the LCG associated with the XR service has data or delay emergency data, which has the highest priority LCH; or, the LCH associated with the first DSR, the LCG associated with the first DSR, or the LCH in the LCG associated with the first DSR has data or delay emergency data, which has the highest priority LCH; or, the LCH associated with the DSR, the LCG associated with the DSR, or the LCH in the LCG associated with the DSR has data or delay emergency data, which has the highest priority LCH. In some scenarios, the first uplink resource obtained by the terminal device may not be the data for the LCH in the LCG associated with the BSR. For example, LCH 1 in LCG 1 of the terminal device obtains new data to trigger the BSR, and restarts the retransmission BSR timer after obtaining the first uplink resource. When the first uplink resource cannot meet the LCP mapping restriction of LCH 1 in LCG 1, it will cause BSR transmission delay, and then the network device will not be able to schedule resources for LCH 1 in LCG 1, resulting in data transmission delay of LCH 1. To solve the above problem, in an embodiment of the present application, whether to restart the retransmission BSR timer is determined based on whether the first uplink resource meets the LCP mapping restriction of the first LCH. For example, the first LCH is an LCH in the LCG associated with the BSR (for example, the BSR sent by the terminal device, or the BSR or the first BSR sent by the terminal device last time). Exemplarily, if the first uplink resource meets the LCP mapping restriction of the first LCH, LCP mapping restriction, the terminal device restarts the retransmission BSR timer. For example, if the first uplink resource does not meet the LCP mapping restriction of the first LCH, the terminal device does not restart the retransmission BSR timer. FIG10 is a schematic block diagram of a communication device provided in an embodiment of the present application. In one possible implementation, the communication device 600 may include a module or unit corresponding to the method / operation / step / action performed by the terminal device in the above method embodiment, and the unit may be a hardware circuit, or software, or a hardware circuit combined with software. In one possible implementation, as shown in FIG10, the device 600 may include: a transceiver module 610 and a processing module 620. In one example, the transceiver module 610 can be used to send a first cache status report BSR; the transceiver module 610 can also be used to send a first delay status report DSR; the transceiver module 610 can also be used to obtain a first uplink resource; the processing module 620 can be used to meet a first condition and restart the retransmission BSR timer; wherein the first condition is associated with the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource. In another example, the processing module 620 can be used to satisfy a fifth condition to trigger a first DSR; wherein the fifth condition includes: the retransmission DSR timer expires, and there is data or emergency data in the LCH in the LCG associated with the XR service. It should be understood that the specific process executed by each module has been described in detail in the above method embodiment, and for the sake of brevity, it will not be repeated here. The transceiver module 610 in the communication device 600 may be implemented by a transceiver, for example, corresponding to the transceiver 720 in the communication device 700 shown in FIG. 11 . The processing module 620 in the communication device 600 may be implemented by at least one processor, for example, corresponding to the processor 710 in the communication device 700 shown in FIG. 11 . When the communication device 600 is a chip or a chip system configured in a communication device, the transceiver module 610 in the communication device 600 can be implemented through an input / output interface, circuit, etc., and the processing module 620 in the communication device 600 can be implemented through a processor, microprocessor or integrated circuit integrated on the chip or chip system. Fig. 11 is another schematic block diagram of a communication device provided in an embodiment of the present application. As shown in Fig. 11, the communication device 700 may include: a processor 710. The processor 710 may be used to execute the method executed by the terminal device in the above method embodiment. In some possible implementations, the communication device 700 may include a transceiver 720. The transceiver 720 may communicate with the processor 710 via an internal connection path. The processor 710 may control the transceiver 720 to send and / or receive signals. In some possible implementations, the communication device 700 may include a memory 730. The memory 730 may communicate with the processor 710 through an internal connection path. The memory 730 and the processor 710 may be integrated together or separately arranged. The memory 730 may also be a memory outside the device. The memory 730 is used to store instructions, and the processor 710 is used to execute the instructions stored in the memory 730 to execute the method in the above method embodiment. It should be understood that the communication device 700 can be used to execute the various steps and / or processes executed by the terminal device in the above method embodiment. Optionally, the memory 730 may include a read-only memory and a random access memory, and provide instructions and data to the processor. A portion of the memory may also include a non-volatile random access memory. The memory 730 may be a separate device or may be integrated in the processor 710. The processor 710 may be used to execute instructions stored in the memory 730, and when the processor 710 executes instructions stored in the memory, the processor 710 is used to execute the various steps and / or processes of the above method embodiment. Optionally, the communication device 700 is the terminal device in the previous embodiment. Among them, the transceiver 720 may include a transmitter and a receiver. The transceiver 720 may further include an antenna, and the number of antennas may be one or more. The processor 710 and the memory 730 and the transceiver 720 may be devices integrated on different chips. For example, the processor 710 and the memory 730 may be integrated in a baseband chip, and the transceiver 720 may be integrated in a radio frequency chip. The processor 710 and the memory 730 and the transceiver 720 may also be devices integrated on the same chip. This application does not limit this. The transceiver 720 may also be a communication interface, such as an input / output interface, a circuit, etc. The transceiver 720, the processor 710, and the memory 730 may be integrated into the same chip, such as a baseband chip. The present application also provides a processing device, including at least one processor, which runs a computer program or a logic circuit so that the processing device executes the method executed by the terminal device in the above method embodiment. The above processing device may also include a memory, which is used to store the above computer program. The embodiment of the present application also provides a processing device, including a processor and an input / output interface. The input / output interface is coupled to the processor. The input / output interface is used to input and / or output information. The information includes at least one of an instruction and data. The processor is used to execute a computer program so that the processing device executes the method executed by the terminal device in the above method embodiment. The present application also provides a processing device, including a processor and a memory. The memory is used to store a computer program, and the processor is used to call and run the computer program from the memory, so that the processing device executes the method executed by the terminal device in the above method embodiment. It should be understood that the above-mentioned processing device may be one or more chips. For example, the processing device may be a field programmable gate array (FPGA), an application specific integrated circuit (ASIC), a system on chip (SoC), a central processor unit (CPU), a network processor (NP), a digital signal processor (DSP), a microcontroller unit (MCU), a programmable logic device (PLD) or other integrated chips. In the implementation process, each step of the above method can be completed by an integrated logic circuit of hardware in a processor or an instruction in the form of software. The steps of the method disclosed in conjunction with the embodiment of the present application can be directly embodied as a hardware processor for execution, or a combination of hardware and software modules in a processor for execution. The software module can be located in a storage medium mature in the art such as a random access memory, a flash memory, a read-only memory, a programmable read-only memory or an electrically erasable programmable memory, a register, etc. The storage medium is located in a memory, and the processor reads the information in the memory and completes the steps of the above method in conjunction with its hardware. To avoid repetition, it is not described in detail here. It can be understood that the memory in the embodiments of the present application can be a volatile memory or a non-volatile memory, or can include both volatile and non-volatile memories. Among them, the non-volatile memory can be a read-only memory (ROM), a programmable read-only memory (PROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), or a flash memory. The volatile memory can be a random access memory (RAM), which is used as an external cache. By way of example and not limitation, many forms of RAM are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDR SDRAM), enhanced SDRAM (ESDRAM), synchlink DRAM (SLDRAM), and direct rambus RAM (DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory. According to the method provided in the embodiment of the present application, the present application also provides a computer program product, which includes: a computer program or a set of instructions, when the computer program or a set of instructions is run on a computer, the computer executes the method executed by the terminal device in the above method embodiment. According to the method provided in the embodiment of the present application, the present application also provides a computer-readable storage medium, which stores a program. When the program runs on a computer, the computer executes the method executed by the terminal device in the above method embodiment. According to the method provided in the embodiment of the present application, the present application also provides a communication system, which may include the aforementioned terminal device. Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of this application.

Claims

1. A communication method, characterized in that: Applied to terminal equipment, including: Sending a first buffer status report BSR; Sending a first delay status report DSR; Acquire the first uplink resource; If the first condition is met, the retransmission BSR timer is restarted; The first condition is associated with the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource.

2. The method according to claim 1, characterized in that The first condition includes: the first BSR and the first DSR are included in the same MAC PDU.

3. The method according to claim 1, characterized in that The first condition includes: The first uplink resource does not satisfy a first logical channel prioritization LCP mapping restriction; and / or, The first uplink resource meets a second logical channel prioritization LCP mapping restriction; The first LCP mapping restriction corresponds to a logical channel LCH associated with an extended reality XR service or the first DSR; The second LCP mapping restriction corresponds to a non-XR service or an LCH associated with the first BSR.

4. The method according to claim 3, characterized in that The first condition also includes: the first BSR and the first DSR are not included in the same MAC PDU.

5. The method according to claim 1, characterized in that The first condition includes: the first uplink resource can accommodate data in all LCHs.

6. The method according to claim 5, characterized in that The first condition also includes: The first BSR and the first DSR are not included in the same MAC PDU; and / or, The first uplink resource meets a first LCP mapping restriction.

7. The method according to any one of claims 1 to 6, characterized in that: After acquiring the first uplink resource, the method further includes: If the second condition is met, the retransmission BSR timer is not restarted; The second condition includes at least one of the following: The first BSR and the first DSR are not included in the same MAC PDU; The first uplink resource satisfies a first LCP mapping restriction; The first uplink resource does not satisfy the second LCP mapping restriction; or, The first uplink resource cannot accommodate all the data in the LCH.

8. The method according to any one of claims 1 to 7, characterized in that: After acquiring the first uplink resource, the method further includes: If the third condition is met, the retransmission DSR timer is restarted; The third condition is associated with the sending status of the first BSR and the first DSR and / or the accommodation status of the first uplink resource.

9. The method according to claim 8, characterized in that The third condition includes: the first BSR and the first DSR are included in the same MAC PDU.

10. The method according to claim 8, characterized in that The third condition includes: The first uplink resource satisfies a first LCP mapping restriction; and / or, The first uplink resource does not satisfy the second LCP mapping restriction; The first LCP mapping restriction corresponds to the XR service or the LCH associated with the first DSR; The second LCP mapping restriction corresponds to a non-XR service or an LCH associated with the first BSR.

11. The method according to claim 10, characterized in that The third condition also includes: the first BSR and the first DSR are not included in the same MAC PDU.

12. The method according to claim 8, characterized in that The third condition includes: the first uplink resource can accommodate all XR services or the first DSR associated LCG Data in LCH or urgent data.

13. The method according to claim 12, characterized in that The third condition also includes any one or more of the following: The first BSR and the first DSR are not included in the same MAC PDU; or, The first uplink resource meets the second LCP mapping restriction.

14. The method according to any one of claims 8 to 13, characterized in that: After acquiring the first uplink resource, the method further includes: If the fourth condition is met, the retransmission DSR timer is not restarted; The fourth condition includes at least one of the following: The first BSR and the first DSR are not included in the same MAC PDU; The first uplink resource does not satisfy a first LCP mapping restriction; The first uplink resource satisfies a second LCP mapping restriction; or, The first uplink resource cannot accommodate all XR services or data or emergency data in the LCH in the LCG associated with the first DSR.

15. The method according to any one of claims 1 to 14, characterized in that: The second LCP mapping restrictions include: LCP mapping restrictions for LCHs associated with non-XR services, or, LCP mapping restriction of LCH in LCG included in the first BSR; or, The amount of data included in the first BSR is greater than the LCP mapping restriction of the LCH in the LCG of 0.

16. The method according to any one of claims 1 to 15, characterized in that: The first LCP mapping restrictions include: LCP mapping restrictions for LCH associated with XR services, or, LCP mapping restrictions of LCHs in the LCG included in the first DSR; or, The first DSR includes an LCP mapping restriction of an LCH in an LCG having a data volume greater than 0.

17. A communication method, characterized in that: Applied to terminal equipment, including: The fifth condition is met, triggering the first DSR; The fifth condition includes: the retransmission DSR timer times out, and there is data or emergency data in the LCH in the LCG associated with the XR service or the first DSR.

18. The method according to claim 17, characterized in that The method further comprises: The first DSR is sent, and the retransmission DSR timer is started or restarted.

19. The method according to claim 17 or 18, characterized in that The method further comprises: Obtaining first confirmation information, and restarting or stopping the retransmission DSR timer; The first confirmation information is associated with the first DSR.

20. The method according to any one of claims 19, characterized in that: The first confirmation information is carried in MAC CE.

21. The method according to any one of claims 17 to 20, characterized in that: The method further comprises: The LCH that triggers the first DSR is: when the first DSR is triggered, the LCH in the LCG associated with the XR service or the first DSR has data or emergency data and has the highest priority LCH.

22. A communication device, characterized in that: Comprising means for performing the method as claimed in any one of claims 1 to 21.

23. A communication device, characterized in that: include: A processor for executing the method according to any one of claims 1 to 21.

24. A computer-readable storage medium, characterized in that: Used to store computer program instructions, the computer program causing a computer to execute the method according to any one of claims 1 to 21.

25. A computer program product, characterized in that The method comprises computer program instructions which cause a computer to execute the method according to any one of claims 1 to 21.

Images