Method for reporting buffer state, and communication apparatus

WO2024169448A9PCT designated stage expired Publication Date: 2024-12-05HUAWEI TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
PCT/CN2024/070491
Authority / Receiving Office
WO · WO
Patent Type
Applications
Current Assignee / Owner
Priority Date
2023-02-15
Filing Date
2024-01-04
Publication Date
2024-12-05

AI Technical Summary

Technical Problem

Existing terminal devices fail to fully consider the different attributes of data packets when reporting cache status reports, resulting in inaccurate allocation of transmission resources and affecting the reliability and efficiency of data packet transmission.

Method used

The terminal device generates different cache status reports for data packets with different attributes, including business type, expiration time, importance and type information of the protocol data unit set, so that the network device can consider the characteristics of the data packet when allocating transmission resources, using The combination of emergency BSR format and traditional BSR format is reported to reduce the occupation of transmission resources and control the restart of the periodic cache status report timer.

Benefits of technology

It improves the performance of cache status reporting and the reliability of data packet transmission, optimizes the allocation of transmission resources, reduces the occupation of transmission resources and the frequency of timer restarts, and enhances the resource management capabilities of network equipment.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN2024070491_05122024_PF_FP_ABST
    Figure CN2024070491_05122024_PF_FP_ABST
Patent Text Reader

Abstract

Provided in the present application are a method for reporting a buffer state, and a communication apparatus. The method comprises: buffering a plurality of data packets, wherein the plurality of data packets include a first data packet and a second data packet; and sending a first buffer state report and a second buffer state report to a network device, wherein the first buffer state report indicates a buffer state of the first data packet, the second buffer state report indicates a buffer state of the second data packet, and at least one of the following attributes of the first data packet and of the second data packet is different: a service type, a duration until an expiration time, the degree of importance of a protocol data unit set to which each data packet belongs, and the type of the protocol data unit set to which each data packet belongs. By means of the method, a first buffer state report and a second buffer state report are respectively generated for data packets having different attributes, such that when a network device allocates transmission resources for a first data packet and a second data packet on the basis of two buffer state reports, different attributes of the first data packet and of the second data packet can be taken into consideration, and the performance of reporting buffer states can be improved.
Need to check novelty before this filing date? Find Prior Art

Description

Method and communication device for reporting cache status

[0001] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on February 15, 2023, with application number 202310162556.X and application name “A method and communication device for reporting cache status”, the entire contents of which are incorporated by reference into this application. Technical Field

[0002] The present application relates to the field of communication technology, and more specifically, to a method and a communication device for reporting a cache status. Background Art

[0003] In a communication system, the transmission resources used by a terminal device to send data packets can be allocated by a network device. For example, a terminal device can send a buffer status report (BSR) to the network device to inform the network device of the buffer status of the data packet. The BSR then allows the network device to allocate transmission resources to the terminal device based on the BSR.

[0004] As terminal devices support increasingly more services, different data packets have different characteristics based on different service requirements. For example, different data packets may have different importance and lifecycles. These characteristics lead to different requirements for transmission resources for different data packets.

[0005] However, currently, terminal devices do not fully consider this feature when reporting BSR.

[0006] Summary of the Invention

[0007] The present application provides a method and a communication device for reporting cache status, which can improve the performance of reporting cache status.

[0008] In a first aspect, a method for reporting cache status is provided. The method can be implemented by a terminal device or a chip in the terminal device, and the method includes: caching multiple data packets, the multiple data packets including a first data packet and a second data packet. A first cache status report and a second cache status report are sent to a network device, the first cache status report indicating the cache status of the first data packet, and the second cache status report indicating the cache status of the second data packet. The first data packet and the second data packet differ in at least one of the following attributes: service type, time to expiration, importance of the protocol data unit set to which they belong, or type of the protocol data unit set to which they belong.

[0009] Based on this technical solution, the data packets cached by the terminal device include data packets with different attributes. The terminal device can generate a first cache status report and a second cache status report for the data packets with different attributes respectively. Therefore, when the network device allocates transmission resources for the first data packet and the second data packet based on the two cache status reports, it can take into account the different attributes of the first data packet and the second data packet, thereby improving the performance of reporting the cache status.

[0010] In combination with the first aspect, in some implementations of the first aspect, sending a first cache status report and a second cache status report to a network device includes: sending a protocol data unit to the network device, the protocol data unit including the first cache status report and the second cache status report.

[0011] Based on the technical solution, one protocol data unit may include two cache status reports, and the two cache status reports may respectively indicate the cache status of two data packets having at least one different attribute.

[0012] In combination with the first aspect, in certain implementations of the first aspect, the first cache status report includes first data volume information and time information, the first data volume information indicates the data volume of the first data packet, and the time information indicates the time when the first data packet needs to be completed and sent, and the second cache status report includes second data volume information, and the second data volume information indicates the data volume of the second data packet.

[0013] Based on this technical solution, the terminal device can report the data volume and the time required to complete transmission of the first data packet, and report the data volume of the second data packet, without having to report the time required to complete transmission of the second data packet. Thus, the network device can determine that the attributes of the first and second data packets regarding the time required to complete transmission are different, based on the fact that the first cache status report contains time information and the second cache status report does not contain time information. In other words, the two cache data reports of this technical solution do not need to both contain time information; time information can be included in only one cache status report, which can save transmission resources occupied by cache status reports.

[0014] In addition, the network device can allocate transmission resources to the first data packet based on time information. For example, the first data packet needs to be sent within a first time range, and the second data packet may not need to be sent within the first time range. The network device can allocate transmission resources that can be sent within the first time range to the first data packet based on time information, thereby improving the reliability of the network device in allocating transmission resources.

[0015] In combination with the first aspect, in some implementations of the first aspect, the first cache status report includes indication information, where the indication information indicates that the first cache status report indicates a cache status of the first data packet.

[0016] Based on the present technical solution, the terminal device and the network device can pre-agree on the difference in attributes between the first data packet and the second data packet, so that the first cache status report does not need to include information about the attributes of the first data packet. The network device can know through the indication information in the first cache status report that the first cache status report is a cache status report of the first data packet, thereby reducing the transmission resources occupied by the cache status report.

[0017] In combination with the first aspect, in some implementations of the first aspect, the first cache status report includes a sub-header field, and the indication information is a logical channel identification field or an extended logical channel identification field of the sub-header field.

[0018] In combination with the first aspect, in certain implementations of the first aspect, if the second buffer status report is not completely sent or the second buffer status report is in a truncated buffer status report format, the periodic buffer status report timer is not restarted.

[0019] Based on this technical solution, the terminal device does not need to restart the periodic cache status report timer every time it completes sending a cache status report. The terminal device does not need to restart the periodic cache status report timer after the first cache status report is sent, but can restart the periodic cache status report timer after the second cache status report is sent. This avoids the terminal device frequently restarting the periodic cache status report timer due to the frequent sending of the first cache status, reduces the possibility of the second cache status report not being able to be sent for a long time, and can improve the reliability of cache status report reporting.

[0020] In combination with the first aspect, in some implementations of the first aspect, the first data packet needs to be sent within a first time range.

[0021] Based on the present technical solution, the first data packet may be a data packet that needs to be sent within a first time range, for example, the first data packet has an expiration time within the first time range, so that the network device can allocate transmission resources that can be sent within the first time range to the first data packet based on the first cache status report, thereby improving the reliability of data packet transmission.

[0022] In combination with the first aspect, in some implementations of the first aspect, the method further includes: receiving configuration information from a network device, where the configuration information indicates a first time range.

[0023] In combination with the first aspect, in certain implementations of the first aspect, the format of the first cache status report is determined based on at least one of the following information: the number of logical channels from which the first data packet comes, the number of logical channel groups from which the first data packet comes, the number of protocol data unit sets from which the first data packet comes, the type of the first cache status report, or the number of bits occupied by the first cache status report.

[0024] With reference to the first aspect, in certain implementations of the first aspect, the second cache status report is a fill cache status report, and a format of the second cache status report is determined based on the number of bits occupied by the first cache status report.

[0025] Optionally, sending the first cache status report and the second cache status report to the network device includes: sending the first cache status report to the network device; and after sending the first cache status report to the network device, sending the second cache status report to the network device.

[0026] Optionally, the protocol data unit includes a first buffer status report and a second buffer status report, and a code stream corresponding to the first buffer status report is encapsulated before the second buffer status report.

[0027] In a second aspect, a method for reporting cache status is provided, which can be implemented by a terminal device or a chip in the terminal device, and the method includes: caching at least one data packet; sending a cache status report to a network device, the cache status report indicating the cache status of at least one data packet, the cache status report including indication information and / or time information, the indication information indicating whether the at least one data packet contains a first data packet, and the time information indicating the time when the at least one data packet needs to be sent, wherein the first data packet is related to at least one of the following information: service type information, time information to expiration, importance information of the protocol data unit set to which it belongs, or type information of the protocol data unit set to which it belongs.

[0028] Based on the present technical solution, the terminal device can carry indication information and / or time information in the cache status report, and use the indication information to indicate whether at least one data packet contains a data packet with the attribute of the first data packet, and / or use the time information to indicate the attribute of at least one data packet regarding the time when the transmission needs to be completed, so that the network device can allocate transmission resources based on the attribute of at least one data packet, thereby improving the performance of reporting the cache status report.

[0029] In combination with the second aspect, in certain implementations of the second aspect, before sending a cache status report to the network device, the method also includes: determining that at least one data packet contains a first data packet, and the cache status report includes time information, or time information and indication information, or indication information.

[0030] Based on the present technical solution, the terminal device may include indication information and / or time information in the cache status report when it is determined that at least one data packet contains the first data packet, and may not include indication information and / or time information in the cache status report when it is determined that at least one data packet does not contain the first data packet, thereby saving the transmission resources occupied by the cache status report.

[0031] In combination with the second aspect, in some implementations of the second aspect, the first data packet needs to be sent within a first time range.

[0032] Based on the present technical solution, the first data packet may be a data packet that needs to be sent within a first time range, for example, the first data packet has an expiration time within the first time range, so that the network device can allocate transmission resources that can be sent within the first time range to the first data packet based on the first cache status report, thereby improving the reliability of data packet transmission.

[0033] In combination with the second aspect, in some implementations of the second aspect, the method further includes: receiving configuration information from a network device, where the configuration information indicates a first time range.

[0034] In combination with the second aspect, in some implementations of the second aspect, the cache status report includes a sub-header field, and the sub-header field includes indication information.

[0035] In combination with the second aspect, in some implementations of the second aspect, the indication information is a logical channel identification field or an extended logical channel identification field of a sub-header field.

[0036] In combination with the second aspect, in certain implementations of the second aspect, at least one data packet does not include the first data packet, the cache status report is not sent completely or the cache status report is in a truncated cache status report format, and the periodic cache status report timer is not restarted.

[0037] According to a third aspect, a method for reporting cache status is provided, which can be implemented by a network device or a chip in the network device, and the method includes: receiving a first cache status report and a second cache status report from a terminal device, the first cache status report indicating the cache status of a first data packet, and the second cache status report indicating the cache status of a second data packet; determining the transmission resources of the first data packet and the transmission resources of the second data packet based on the first cache status report and the second cache status report; wherein at least one of the following attributes of the first data packet and the second data packet is different: service type, time to expiration, importance of the protocol data unit set to which they belong, or type of the protocol data unit set to which they belong.

[0038] For the description of the beneficial effects of the third aspect, please refer to the relevant description of the first aspect and will not be repeated here.

[0039] In combination with the third aspect, in some implementations of the third aspect, receiving a first cache status report and a second cache status report from a terminal device includes: receiving a protocol data unit from the terminal device, the protocol data unit including the first cache status report and the second cache status report.

[0040] In combination with the third aspect, in certain implementations of the third aspect, the first cache status report includes first data volume information and time information, the first data volume information indicates the data volume of the first data packet, and the time information indicates the time when the first data packet needs to be sent, and the second cache status report includes second data volume information, and the second data volume information indicates the data volume of the second data packet.

[0041] In combination with the third aspect, in some implementations of the third aspect, the first cache status report includes indication information, where the indication information indicates that the first cache status report indicates a cache status of the first data packet.

[0042] In combination with the third aspect, in certain implementations of the third aspect, the first cache status report includes a sub-header field, and the indication information is a logical channel identification field or an extended logical channel identification field of the sub-header field.

[0043] In combination with the third aspect, in certain implementations of the third aspect, the first data packet needs to be sent within a first time range.

[0044] In combination with the third aspect, in some implementations of the third aspect, the method further includes: sending configuration information to the terminal device, where the configuration information indicates the first time range.

[0045] In a fourth aspect, a method for reporting cache status is provided, which can be implemented by a network device or a chip in the network device, and the method includes: receiving a cache status report from a terminal device, the cache status report indicating the cache status of at least one data packet, the cache status report including indication information and / or time information, the indication information indicating whether the at least one data packet contains a first data packet, and the time information indicating the time when at least one data packet needs to complete sending, wherein the first data packet is related to at least one of the following information: service type information, time information to expiration, importance information of the protocol data unit set to which it belongs, or type information of the protocol data unit set to which it belongs; the network device determines the transmission resources of at least one data packet based on the cache status report.

[0046] For the description of the beneficial effects of the fourth aspect, please refer to the relevant description of the first aspect and will not be repeated here.

[0047] In combination with the fourth aspect, in certain implementations of the fourth aspect, the first data packet needs to be sent within a first time range.

[0048] In combination with the fourth aspect, in some implementations of the fourth aspect, the method further includes: sending configuration information to the terminal device, where the configuration information indicates the first time range.

[0049] In combination with the fourth aspect, in certain implementations of the fourth aspect, the cache status report includes a sub-header field, and the sub-header field includes indication information.

[0050] In combination with the fourth aspect, in certain implementations of the fourth aspect, the indication information is a logical channel identification field or an extended logical channel identification field of a sub-header field.

[0051] In a fifth aspect, a communication device is provided, wherein the communication device has the function of implementing the method in the first aspect, or any possible implementation of the first aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0052] In a sixth aspect, a communication device is provided, wherein the communication device has the function of implementing the method in the second aspect, or any possible implementation of the second aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0053] In a seventh aspect, a communication device is provided, wherein the communication device has the function of implementing the method in the third aspect, or any possible implementation of the third aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0054] In an eighth aspect, a communication device is provided, wherein the communication device has the function of implementing the method in the fourth aspect, or any possible implementation of the fourth aspect. The function can be implemented by hardware, or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions.

[0055] In a ninth aspect, a communication device is provided, comprising a processor and a memory. Optionally, a transceiver is further included. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory and control the transceiver to transmit and receive signals, so that the communication device performs the method of the first aspect or the second aspect, or any possible implementation of any of these aspects.

[0056] Exemplarily, the communication device is a terminal device or a chip applied to a terminal device.

[0057] In a tenth aspect, a communication device is provided, comprising a processor and a memory. Optionally, the device may further comprise a transceiver. The memory is configured to store a computer program, and the processor is configured to call and execute the computer program stored in the memory, and control the transceiver to transmit and receive signals, so that the communication device performs the method of the third aspect or the fourth aspect, or any possible implementation of any of these aspects.

[0058] Exemplarily, the communication device is a network device or a chip applied to a network device.

[0059] In the eleventh aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information, and the communication interface is also used to output the data and / or information after processing by the processor, so that the method in any possible implementation of the first aspect or the second aspect, or any of these aspects, is executed.

[0060] The communication device may be a terminal device or a chip applied to a terminal device.

[0061] In the twelfth aspect, a communication device is provided, comprising a processor and a communication interface, wherein the communication interface is used to receive data and / or information and transmit the received data and / or information to the processor, and the processor processes the data and / or information, and the communication interface is also used to output the data and / or information processed by the processor, so that the method in any possible implementation of the third aspect or the fourth aspect, or any of these aspects, is executed.

[0062] The communication device may be a network device or a chip applied to a network device.

[0063] In the thirteenth aspect, a computer-readable storage medium is provided, in which computer instructions are stored. When the computer instructions are executed on a computer, the method in any one of the first to fourth aspects, or any possible implementation of any one of these aspects, is executed.

[0064] In the fourteenth aspect, a computer program product is provided, which includes a computer program code, and when the computer program code is run on a computer, the method in any aspect from the first to the fourth aspect, or any possible implementation of any aspect of these aspects, is executed.

[0065] In the fifteenth aspect, a communication system is provided, comprising a communication device as described in any one or more of the fifth to fourteenth aspects, or a communication device in any possible implementation of any of these aspects. BRIEF DESCRIPTION OF THE DRAWINGS

[0066] FIG1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application;

[0067] FIG2 is a schematic structural diagram of a BSR;

[0068] FIG3 is a schematic flowchart of a method for reporting cache status provided in an embodiment of the present application;

[0069] FIG4 is a schematic structural diagram of another BSR provided in an embodiment of the present application;

[0070] FIG5 is a schematic flowchart of another method for reporting cache status provided in an embodiment of the present application;

[0071] 6 to 8 are schematic structural diagrams of possible devices provided in embodiments of the present application. DETAILED DESCRIPTION

[0072] The technical solution in this application will be described below with reference to the accompanying drawings.

[0073] FIG1 is a schematic diagram of a communication system 100 applicable to an embodiment of the present application.

[0074] As shown in Figure 1, the communication system 100 may include a network device 120 and may also include at least one terminal device 110. The terminal device 110 and the network device 120 may establish a connection to perform communication.

[0075] The terminal device in the embodiments of the present application may refer to user equipment, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal, wireless communication device, user agent or user device. The terminal in the embodiments of the present application can be a mobile phone, a tablet computer, a computer with wireless transceiver function, a virtual reality (VR) terminal, an augmented reality (AR) terminal, a wireless terminal in industrial control, a wireless terminal in self-driving, a wireless terminal in remote medical, a wireless terminal in a smart grid, a wireless terminal in transportation safety, a wireless terminal in a smart city, a wireless terminal in a smart home, a cellular phone, a cordless phone, a session initiation protocol (SIP) phone, a wireless local loop (WLL) station, a 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 in a 5G network or a terminal in a future evolution network, etc.

[0076] Wearable devices, also known as wearable smart devices, are a general term for wearable devices that use wearable technology to intelligently design and develop wearable devices for daily wear, such as glasses, gloves, watches, clothing, and shoes. Wearable devices are portable devices that are worn directly on the body or integrated into the user's clothing or accessories. Wearable devices are not just hardware devices, but also achieve powerful functions through software support, data interaction, and cloud interaction. In a broad sense, wearable smart devices include those that are fully functional, large in size, and can achieve full or partial functions without relying on smartphones, such as smart watches or smart glasses, as well as those that only focus on a certain type of application function and need to be used in conjunction with other devices such as smartphones, such as various smart bracelets and smart jewelry for vital sign monitoring.

[0077] Furthermore, the terminal device may also be a terminal device in an Internet of Things (IoT) system. IoT is an important component of future information technology development. Its main technical feature is to connect objects to the Internet through communication technologies, thereby realizing an intelligent network that interconnects humans and machines, and objects and things. This application does not limit the specific form of the terminal device.

[0078] It should be understood that in the embodiments of the present application, the terminal device may be a device for implementing a terminal device function, or a device capable of supporting the terminal device in implementing the function, such as a chip system, which may be installed in the terminal. In the embodiments of the present application, the chip system may be composed of a chip, or may include a chip and other discrete devices.

[0079] The network device in the embodiment of the present application can be any device with wireless transceiver functions. The device includes but is not limited to: an evolved Node B (eNB), a radio network controller (RNC), a Node B (NB), a base station controller (BSC), a base transceiver station (BTS), a home base station (e.g., home evolved node B, or home node B, HNB), a base band unit (BBU), an access point (AP) in a wireless fidelity (WIFI) system, a wireless relay node, a wireless backhaul node, a transmission point (TP) or a transmission and reception point (TRP), etc., and can also be a gNB in ​​a 5G, such as NR, system, or a transmission point (TRP or TP), one or a group of antenna panels (including multiple antenna panels) of a base station in a 5G system, or a network node constituting a gNB or a transmission point, such as a baseband unit (BBU) or a distributed unit (DU), etc.

[0080] In some deployments, a gNB may include a centralized unit (CU) and a DU. The gNB may also include an active antenna unit (AAU). The CU implements some gNB functions, while the DU implements some gNB functions. For example, the CU is responsible for processing non-real-time protocols and services, implementing the functions of the radio resource control (RRC) and packet data convergence protocol (PDCP) layers. The DU is responsible for processing physical layer protocols and real-time services, implementing the functions of the radio link control (RLC), media access control (MAC), and physical (PHY) layers. The AAU implements some physical layer processing functions, RF processing, and active antenna-related functions. Because RRC layer information ultimately becomes PHY layer information, or is converted from PHY layer information, in this architecture, higher-layer signaling, such as RRC layer signaling, can also be considered to be sent by the DU, or by both the DU and the AAU. It is understood that a network device can be a device that includes one or more of a CU node, a DU node, or an AAU node. In addition, the CU may be classified as a network device in an access network (radio access network, RAN), or the CU may be classified as a network device in a core network (core network, CN), which is not limited in this application.

[0081] It should be understood that in the embodiments of the present application, the network device may be a device for implementing the function of the network device, or may be a device that can support the network device to implement the function, such as a chip system, which may be installed in the network device.

[0082] The technical solutions provided in this application can be applied to various communication systems, such as: fifth generation (5G) or new radio (NR) systems, long term evolution (LTE) systems, LTE frequency division duplex (FDD) systems, LTE time division duplex (TDD) systems, etc. The technical solutions provided in this application can also be applied to future communication systems, such as the sixth generation mobile communication system. The technical solutions provided in this application can also be applied to device to device (D2D) communication, vehicle-to-everything (V2X) communication, machine to machine (M2M) communication, machine type communication (MTC), and Internet of Things (IoT) communication systems or other communication systems.

[0083] It should be understood that the present application can be applied to independently deployed 5G or LTE systems or future mobile communication systems, etc. It can also be applied to non-independently deployed 5G or LTE systems or future mobile communication systems, etc., such as DC scenarios, including evolved universal terrestrial radio access-NR dual connectivity (EN-DC), etc., and carrier aggregation (CA) scenarios. The data unit in the present application can be a protocol data unit (PDU) or a service data unit SDU (SDUA), or other data units. The present application does not impose any special restrictions on this, and the following is an illustrative example using PDU.

[0084] To facilitate understanding of the technical solutions of the embodiments of the present application, before introducing the solutions of the embodiments of the present application based on the 5G architecture, a buffer state report (BSR) is first introduced in conjunction with Figure 2. Before sending a data packet to a network device, a terminal device may first send a BSR to the network device so that the network device is informed of the data volume of the buffered data packet to be sent by the terminal device, so that the network device can allocate an uplink grant (uplink grant) to the terminal device based on the data volume indicated by the BSR, that is, the transmission resources for the terminal device to send the data packet.

[0085] Figure 2 is a schematic structural diagram of a BSR. The BSR includes two parts: a BSR media access control (MAC) control element (CE) sub-header and a BSR MAC CE. Referring to Figure 2, the BSR MAC CE sub-header may include two reserved fields, an extension (E) field, and a logical channel identifier (LCID) or an enhanced LCID (eLCID) field. The extension field indicates whether the BSR MAC CE sub-header is the last BSR MAC CE sub-header. The LCID / eLCID field is used to identify the type of BSR MAC CE. Optionally, the BSR MAC CE sub-header may also include a format (F) field and a length field. The format field indicates the length of the length field. For example, when the format field is 0, it indicates that the length field contains 7 bits, and when the format field is 1, it indicates that the length field contains 15 bits. The BSR MAC CE can adopt different BSR formats. Exemplarily, a terminal device may have multiple logical channels (logical channels, LCHs), and multiple LCHs may be divided into multiple groups. For example, a terminal device may have 16 LCHs, and the 16 LCHs may be divided into 4 groups, each group containing 4 LCHs. If the terminal device reports a data packet on a logical channel group (logical channel group, LCG), the terminal device may use a BSR MAC CE in a short BSR format or a short truncated BSR format. Referring to Figure 2, the BSR MAC CE in the short BSR format or the short truncated BSR format may include an LCG ID field and a buffer size field. The LCG ID field is used to indicate the identifier of the LCG, and the buffer size field is used to indicate the amount of data of the cached data packet on the LCG. If the terminal device reports the amount of data on each LCG in multiple LCGs in one BSR, the terminal device may use a BSR MAC CE in a long BSR format or a long truncated BSR format.As shown in Figure 2, the first byte of the BSR MAC CE in the long BSR format or the long truncated BSR format can contain 8 LCG identification fields (LCG0-LCG7). If LCG0-LCG7 contain data packets cached in m LCGs, the BSR MAC CE contains m cache size fields (cache size #1 to cache size #m), which respectively indicate the amount of data cached on the m LCGs, where m is an integer less than or equal to 8 and equal to or greater than 2.

[0086] It should be noted that the formats of the BSR MAC CE currently defined by the protocol may also include an extended short BSR format, an extended long BSR format, an extended short truncated BSR format, and an extended long truncated BSR format. For a more detailed description, please refer to the provisions of the existing protocol. In the embodiment of the present application, the four BSR format methods shown in Figure 2 may be applied to the four extended BSR formats described above.

[0087] It should be noted that the short BSR format or the long BSR format, and the short truncated BSR format or the long truncated BSR format are distinguished based on the type of BSR. The types of BSR may include the following three types: regular BSR, periodic BSR, and padding BSR. For example, if a logical channel receives a new data packet, and the priority of the logical channel is higher than that of other logical channels containing data in the same logical channel group, then the terminal device may trigger a BSR of the regular BSR type. If the terminal device sends a BSR according to a predefined period, then the terminal device may trigger a BSR of the periodic BSR type. For example, the terminal device may configure a periodic BSR timer (periodicBSR-Timer), restart the periodic BSR timer after each BSR is sent, and send a periodic BSR type BSR when the periodic BSR timer expires. If the terminal device sends a BSR through the remaining bits in the PDU, then a padding type BSR may be triggered.

[0088] If the terminal device triggers a regular BSR or a periodic BSR, the BSR MAC CE format is a short BSR format or a long BSR format. If the terminal device triggers a padding BSR, the BSR MAC CE format is a short truncated BSR format or a long truncated BSR format.

[0089] As terminal devices increasingly support more services, different data packets have different characteristics based on different service requirements. For example, different data packets may have different importance and lifecycles. For example, some services, such as extended reality (XR) services such as augmented reality (AR), virtual reality (VR), and mixed reality (MR), have strict requirements on the time it takes for terminal devices to send data packets. Terminal devices must send data to network devices within a certain timeframe. If the terminal device fails to send data within this timeframe, the data becomes invalid. This timeframe can be referred to as the data lifecycle or delay budget. For another example, video frames in the application layer of XR services may include base frames (or I-frames, I-slices) and enhanced frames (or P-frames, P-slices), with base frames and enhanced frames having different importance. For example, when a terminal device is editing a video about the starry sky, it may encode the complete image of the starry sky in the first frame. In subsequent frames, if the image information is the same as the previous frame, it will not be encoded and transmitted again. Instead, only the different parts will be encoded and transmitted. These frames that rely on other frames for decoding are called enhanced frames. It can be seen that the importance of the basic frame is higher than that of the enhanced frame.

[0090] The present application proposes a method and a communication device for reporting a cache status. The method for reporting a cache status is first described below with reference to FIG. 3 .

[0091] FIG3 is a schematic flowchart of a method for reporting cache status provided in an embodiment of the present application.

[0092] S310: The terminal device buffers multiple data packets.

[0093] The multiple data packets include a first data packet and / or a second data packet, wherein the first data packet and the second data packet differ in at least one of the following attributes: service type, time to expiration, importance of the protocol data unit set to which they belong, or type of the protocol data unit set to which they belong. The terminal device may generate a first cache status report and a second cache status report for the data packets with different attributes, respectively, so that the network device can take into account the different attributes of the first data packet and the second data packet when allocating transmission resources for the first data packet and the second data packet based on the two cache status reports.

[0094] Exemplarily, the first data packet may include XR service type data, and the second data packet may include non-XR service type legacy data. Furthermore, exemplarily, the first data packet may include urgent data within the XR service type data, and the second data packet may include non-urgent data within the XR data and legacy data within the non-XR service type.

[0095] Exemplarily, whether the data packet needs to be sent within the first time range may be related to at least one of the above attributes. The above attributes may be determined based on the following information respectively: service type information, time to expiration information, importance information of the PDU set to which it belongs, or type information of the PDU set to which it belongs. That is, the first data packet among the multiple data packets is related to at least one of the above information. The service type information may indicate the service type of the data packet, such as XR service; the time to expiration information may indicate the time when the data needs to be sent, or the time to expiration, such as the PDU set delay budget (PSDB) of the PDU set or frame to which it belongs, or the remaining time after the PSDB deducts the time already cached in the sending side device; the importance information of the PDU set to which it belongs indicates the importance or importance level or priority of the data packet; the type information of the PDU set to which it belongs may indicate the data type, such as the basic frame or enhanced frame in the data of the XR service.

[0096] The terminal device can use a variety of methods to determine the first data packet and the second data packet in the data packet based on one or more of the above information. Exemplarily, the terminal device can determine the first data packet in the data packet based on the service type information. For example, data of certain specific service types are configured to need to be sent within the first time range, such as the data packet of the XR service type is the first data packet, and the data packets of other service types are the second data packets. In another exemplary embodiment, the terminal device can determine the first data packet in the data packet based on the distance to expiration time information. For example, the terminal device can determine whether the distance to expiration time of each data packet is within the first time range. The data packet with the distance to expiration time within the first time range is the first data packet, and the data packet with the distance to expiration time not within the first time range is the second data packet. In another exemplary embodiment, the terminal device can determine the first data packet in the data packet based on the distance to expiration time information and the importance information of the PDU set to which it belongs. For example, the data packet with the distance to expiration time within the first time range and is a basic frame is the first data packet, and the remaining data packets are the second data packets. For example, if the data packet is an enhanced frame with low importance, even if the distance to expiration time of the data packet is within the first time range, the terminal device does not consider the data packet to be a data packet that needs to be sent within the first time range. That is to say, the terminal device determines whether a data packet is the first data packet, in addition to the first time range and the distance expiration time of the data packet, it can also be based on the service type to which the data packet belongs (for example, whether it is an XR service), or the importance of the PDU set to which the data packet belongs (for example, whether it is an important PDU set), or the priority of the PDU set to which the data packet belongs (for example, whether it is a high-priority PDU set), or the type of the PDU set to which the data packet belongs (for example, whether it is an I frame, or an I slice, or a basic frame, or a data set containing key information), etc. The present application does not specifically limit the way in which the terminal device determines the first data packet in the data packet.

[0097] That is, the first data packet may include data of an XR service type, and the second data packet may include data of a non-XR service type. Alternatively, the first data packet may include data of an XR service type, with a due date within a first time range, and an I-frame data type, while the second data packet may include data of an XR service type and a P-frame data type.

[0098] It should be noted that the "time to expiration" mentioned above can be understood as the remaining time until a packet expires. For example, the time to expiration can be determined based on the AN-PSDB. The AN-PSDB is the time from packet generation to expiration. A packet's time to expiration can be equal to the AN-PSDB minus the time the packet has been cached. For example, if the AN-PSDB for a PDU to which a packet belongs is 30 milliseconds and the packet has been cached for 10 milliseconds, then the packet's time to expiration is 20 milliseconds. In this case, the packet's time to expiration can also be expressed as the remaining time in the packet's AN-PSDB. The AN-PSDB is the upper bound (i.e., the maximum tolerable delay) for the transmission and processing of a PDU set between the UE and the RAN. The AN-PSDB can be obtained by splitting the PSDB, where the PSDB is the upper bound on the end-to-end delay of a packet between the UE and the UPF (including from the UE to the RAN and from the RAN to the UPF). In other words, the PSDB can be split into the AN-PSDB between the UE and the RAN and the CN-PSDB between the RAN and the UPF. The CN-PSDB may be statically configured, or may be dynamically acquired through time-consuming transmission between the UPF and the RAN.

[0099] It is understandable that the first data packet can be regarded as a more urgent or more important data packet than the second data packet, so that the network device can allocate transmission resources to the first data packet first, thereby improving the reliability of data transmission.

[0100] It should be noted that when one or more of the information changes, the data packet may change from a first data packet to a second data packet, or from a second data packet to a first data packet. The following takes the distance to expiration time information as an example for explanation. The terminal device receives a new data packet. Since the distance to expiration time is large, the data packet is now the second data packet. As time goes by, the data packet fails to be sent, and the distance to expiration time becomes within the first time range, then the data packet changes from the second data packet to the first data packet. If the data packet still fails to be sent within the first time range, and the distance to expiration time becomes less than the first time range, then the data packet changes from the first data packet to the second data packet. It should be noted that in addition to changes in the distance to expiration information, it is also possible that the original first data packet becomes the second data packet, or the original second data packet becomes the first data packet due to other information, such as changes in the importance of the PDU set to which it belongs. We will not elaborate on this.

[0101] The first time range may be formed by at least one time threshold. For example, the first time range may be defined by an upper time limit, e.g., if the first time range is less than or equal to 10 milliseconds (ms), a data packet that needs to be sent within 10 ms is a first data packet, and a data packet that does not need to be sent within 10 ms is a second data packet. For another example, the first time range may be defined by an upper time limit and a lower time limit, e.g., if the upper time limit is 10 milliseconds (ms) and the lower time limit is 2 ms, a data packet that needs to be sent within a range of 2 ms to 10 ms is a first data packet, and a data packet that does not need to be sent within a range of 2 ms to 10 ms is a second data packet.

[0102] It should be noted that the lower time limit of the first time range can be determined based on the time required for the network device to allocate transmission resources to the terminal device. For example, if a data packet is less than 2ms away from the expiration time, the time is not enough for the network device to allocate transmission resources for it, then the data packet does not need to be regarded as the first data packet that needs to be allocated transmission resources first.

[0103] The manner in which the terminal device determines whether a data packet is the first data packet or the second data packet may be pre-configured or may be configured by the network device. For example, the network device may send configuration information to the terminal device, where the configuration information indicates a first time range. For example, the configuration information may include at least one time threshold value, so that the terminal device may determine the first data packet and the second data packet based on the at least one time threshold value and the distance to expiration time of the data packet. For another example, the configuration information may include service type information, such as the network device may indicate that all data packets of the XR service are first data packets.

[0104] The first time range can be configured based on any of the following granularities: LCG, LCH, resource block (RB), PDCP entity, or terminal device. That is, different first time ranges can be configured for different LCGs, LCHs, PDCP entities, RBs, or terminal devices. For example, the network device can configure a first time range for each LCG, and the terminal device can sequentially determine whether the time until expiration of a data packet on each LCG is within the corresponding first time range.

[0105] S320: The terminal device sends a first buffer status report (hereinafter referred to as BSR#1) and / or a second buffer status report (hereinafter referred to as BSR#2) to the network device. Accordingly, the network device receives the first buffer status report (hereinafter referred to as BSR#1) and / or the second buffer status report (hereinafter referred to as BSR#2).

[0106] BSR#1 indicates the cache status of the first data packet, and BSR#2 indicates the cache status of the second data packet. That is, when the multiple data packets cached by the terminal device only include the first data packet, the terminal device generates and sends BSR#1; when the multiple data packets cached by the terminal device only include the second data packet, the terminal device generates and sends BSR#2; and when the multiple data packets cached by the terminal device include the first data packet and the second data packet, the terminal device generates and sends BSR#1 and BSR#2, respectively. It should be noted that BSR#1 and BSR#2 can be two different MAC control elements, and the two different MAC control elements are within two different MAC protocol data units. BSR#1 and BSR#2 can also be two different MAC control elements but within the same MAC protocol data unit, and they can also be considered the same MAC control element. If BSR#1 and BSR#2 are within two different MAC protocol data units, the terminal device first sends the protocol data unit containing BSR#1, and then sends the MAC protocol data unit containing BSR#2. If BSR#1 and BSR#2 are two different MAC control elements but are within the same MAC protocol data unit, the MAC control element associated with BSR#1 is located outside the MAC control element associated with BSR#2. If BSR#1 and BSR#2 are within the same MAC control element, the domain associated with BSR#1 is located outside the domain associated with BSR#2. In other words, the terminal device can generate BSR#1 and BSR#2 separately for two different types of packets, rather than generating a unified BSR for all cached packets.

[0107] The terminal device can determine whether to encapsulate BSR#1 and BSR#2 in one MAC PDU or two MAC PDUs based on the number of bits occupied by BSR#1 and the number of bits occupied by BSR#2. For example, when the total number of bits occupied by BSR#1 and BSR#2 is less than or equal to the remaining number of bits in a MAC PDU, the terminal device can send BSR#1 and BSR#2 by sending a MAC PDU to the network device, and the MAC PDU includes BSR#1 and BSR#2. In other words, BSR#1 and BSR#2 can be encapsulated in one MAC PDU. When the total number of bits occupied by BSR#1 and BSR#2 is greater than the remaining number of bits in a MAC PDU, the terminal device can send BSR#1 and BSR#2 through multiple MAC PDUs, for example, BSR#1 and BSR#2 can be encapsulated in two MAC PDUs respectively. Or, for another example, when BSR#1 and BSR#2 are padding BSRs, the terminal device can fill BSR#1 and BSR#2 into multiple MAC PDUs.

[0108] The terminal device can first send the MAC PDU containing BSR#1, followed by the MAC PDU containing BSR#2. When a MAC PDU contains both BSR#1 and BSR#2, the code stream corresponding to BSR#1 can be encapsulated before the code stream corresponding to BSR#2. This allows BSR#1 to reach the network device before BSR#2. By accelerating the reporting of BSR#1, the allocation of transmission resources for the first data packet can be accelerated, improving data transmission reliability.

[0109] The terminal device can select BSR MAC CE in different formats based on different situations. In order to facilitate understanding of the embodiments of the present application, the selectable BSR formats are first described below. The embodiments of the present application provide 8 possible BSR formats. The 8 BSR formats can be divided into two categories. For the convenience of description, one category can be called a traditional BSR format, and the other category can be called an emergency BSR format. The BSR using the traditional BSR format includes data volume information, and the BSR using the emergency BSR format includes data volume information and time information. The data volume information indicates the data volume of the data packet, and the time information indicates the time when the data packet needs to be sent. The time indicated by the time information in BSR#1 is within the first time range. It can be understood that the names of the traditional BSR format and the emergency BSR format above are only exemplary illustrations for the convenience of description, and this application does not specifically limit this.

[0110] For an explanation of the traditional BSR format, please refer to the description of FIG. 2 above, which includes the following four BSR formats: short BSR format, short truncated BSR format, long BSR format, and long truncated BSR format.

[0111] To facilitate description of the embodiments of the present application, the structure of the emergency BSR format is exemplarily described below with reference to Figure 4. The emergency BSR format may include the following four BSR formats: urgent short BSR format, urgent long BSR format, urgent short truncated BSR format, and urgent long truncated BSR format.

[0112] Referring to Figure 4, the emergency short BSR format or the emergency short truncated BSR format may include identification information, data volume information, and time information. When the terminal device reports the cache status of a data packet on an LCG, the identification information may be the LCG ID information field, indicating the identification of the LCG. When the terminal device reports the cache status of a data packet on an LCH, the identification information may be the LCH ID information field, indicating the identification of the LCH. The data volume information indicates the data volume of the data packet on the LCG or LCH. The time information indicates the time when the data packet on the LCG or LCH needs to be completed. The BSR in the emergency long format or the emergency long truncated format may include multiple identification information, multiple data volume information, and multiple time information. Similarly, the multiple identification information may respectively indicate the identifications of multiple LCGs or LCHs, the multiple data volume information may respectively indicate the data volume of the data packets on multiple LCGs or LCHs, and the multiple time information may respectively indicate the time when the data packets on multiple LCGs or LCHs need to be completed.

[0113] It is understandable that in various embodiments of the present application, "indication" may include direct indication and indirect indication, and may also include explicit indication and implicit indication. The information indicated by a certain information (such as the time information mentioned above) is called information to be indicated. In the specific implementation process, there are many ways to indicate the information to be indicated, such as but not limited to, the information to be indicated can be directly indicated, such as the information to be indicated itself or the index of the information to be indicated. The information to be indicated can also be indirectly indicated by indicating other information, wherein the other information and the information to be indicated have an association relationship. It is also possible to indicate only a part of the information to be indicated, while the other parts of the information to be indicated are known or agreed in advance. For example, the indication of specific information can also be achieved with the help of the arrangement order of each information agreed in advance (such as specified in the protocol).

[0114] For example, the time information may directly indicate the time when the data packet needs to be sent. For example, the time information may include a time value or a time value range for the data packet to be sent. For example, the time information includes the time to expiration of the data packet. The time to expiration time indicates that the time when the data packet needs to be sent is within 5ms, so that the network device can know that the terminal device has a data packet that needs to be sent within 5ms. Alternatively, the time information field may also indirectly indicate the time when the data packet needs to be sent. For example, the time information may include a time index value, and the network device may determine the time value or time value range for the data packet to be sent based on the index value. For example, if the index value is "1", the network device knows that the terminal device has a data packet that needs to be sent within 0ms to 5ms based on the index value; if the index value is "2", the network device knows that the terminal device has a data packet that needs to be sent within 5ms to 10ms based on the index value. The time information may also include a flag or an indicator to indicate that the data packet needs to be sent within a first time range. For example, a flag of 1 indicates that the corresponding data packet needs to be sent within the first time range, or a flag of 1 indicates that the corresponding data packet is sent before other data packets.

[0115] It should also be noted that the terminal device may support all eight BSR formats described above, or the terminal device may only support some of the eight BSR formats. For example, the terminal device may support four traditional BSR formats and any one of the four emergency BSR formats (such as the emergency short BSR format), which is not particularly limited in this application.

[0116] Terminal devices can select the BSR format in several ways:

[0117] In a first possible implementation, BSR#1 uses one of the aforementioned emergency BSR formats, and BSR#2 uses one of the aforementioned traditional BSR formats. That is, BSR#1 may include time information and data volume information #1. The time information indicates the time (or remaining time until expiration) when the first data packet needs to be sent, and data volume information #1 indicates the data volume of the first data packet. BSR#2 may include data volume information #2, which indicates the data volume of the second data packet, but does not include the time information indicating the time when the first data packet needs to be sent.

[0118] If the terminal device supports multiple emergency BSR formats and multiple traditional BSR formats, the terminal device selects one of the multiple emergency BSR formats to generate BSR#1 and selects one of the multiple traditional BSR formats to generate BSR#2. The following describes a method provided by an embodiment of the present application for selecting one of the four emergency BSR formats to generate BSR#1:

[0119] If BSR#1 type is regular BSR or periodic BSR:

[0120] When the first buffered data packet comes from an LCG or LCH or PDU set, the terminal device can select the emergency short BSR format to generate BSR#1;

[0121] When the first buffered data packet comes from multiple LCGs or LCHs or PDU sets, the terminal device can select the emergency long BSR format to generate BSR#1;

[0122] If BSR#1 type is padding BSR:

[0123] When the number of padding bits is greater than or equal to the number of bits required for an emergency long BSR format, the terminal device can select the emergency long BSR format to generate BSR#1;

[0124] When the number of padding bits is less than the number of bits required for an emergency long BSR format and greater than or equal to the number of bits required for an emergency short BSR format, and the first data packet comes from an LCG or LCH or PDU set, the terminal device may select the emergency short BSR format;

[0125] When the number of padding bits is equal to the number of bits required for the emergency short BSR format and the first data packet is carried on multiple LCGs or LCHs or PDU sets, the terminal device may select the emergency truncated BSR format;

[0126] When the number of padding bits is greater than the number of bits required by the emergency short BSR format and less than the number of bits required by the emergency long BSR format, and the first data packet is carried on multiple LCGs or LCHs or PDU sets, the terminal device can select the emergency long truncated BSR format.

[0127] The above introduces a method for a terminal device to select an emergency BSR format from four emergency BSR formats to generate BSR#1. It is understandable that the present application does not specifically limit this. For example, if the terminal device supports two emergency BSR formats, the emergency long BSR format and the emergency short BSR format, then the terminal device can select from the two emergency BSR formats based on the number of LCGs or LCHs carried by the first data packet. If the terminal device supports multiple traditional BSR formats, the terminal device can select a traditional BSR format from the multiple traditional BSR formats to generate BSR#2. The following introduces a method for selecting a traditional BSR format from four traditional BSR formats to generate BSR#2 provided in an embodiment of the present application:

[0128] If the BSR#2 type is regular BSR or periodic BSR:

[0129] When the buffered second data packet comes from an LCG or LCH or PDU set, the terminal device can select the traditional short BSR format to generate BSR#2;

[0130] When the buffered second data packet comes from multiple LCGs or LCHs or PDU sets, the terminal device can select the traditional long BSR format to generate BSR#2;

[0131] If BSR#2 is a padding BSR, the terminal device can select the BSR#2 format based on the number of bits remaining after deducting the number of bits occupied by BSR#1 from the number of padding bits:

[0132] When the number of remaining bits is greater than or equal to the number of bits required for a traditional long BSR format, the terminal device may select the traditional long BSR format to generate BSR#2;

[0133] When the number of remaining bits is less than the number of bits required for a traditional long BSR format and greater than or equal to the number of bits required for a traditional short BSR format, and the second data packet is carried on an LCG or LCH, the terminal device may select the traditional short BSR format;

[0134] When the number of remaining bits is equal to the number of bits required for the conventional short BSR format and the second data packet is carried on multiple LCGs or LCHs, the terminal device may select the conventional truncated BSR format;

[0135] When the number of remaining bits is greater than the number of bits required by the traditional short BSR format and less than the number of bits required by the traditional long BSR format, and the first data packet is carried on multiple LCGs or LCHs, the terminal device can select the traditional long truncated BSR format.

[0136] The above describes a method for a terminal device to select a traditional BSR format from four traditional BSR formats to generate BSR#2. If the data packets cached by the terminal device include a first data packet and a second data packet, the terminal device may first use the above method for selecting an emergency BSR format to generate BSR#1, and then use the above method for selecting a traditional BSR format to generate BSR#2. If the data packets cached by the terminal device include the first data packet but not the second data packet, the terminal device may use the above method for selecting an emergency BSR format to generate BSR#1. If the data packets cached by the terminal device include the second data packet but not the first data packet, the terminal device may use the above method for selecting an appropriate traditional BSR format to generate BSR#2. In this case, the number of remaining bits is equal to the number of padding bits.

[0137] In one possible implementation method described above, as long as the first data packet exists, the terminal device generates BSR#1 using the emergency BSR format and generates BSR#2 using the emergency BSR format. That is, the terminal device can report the data volume of the first data packet and the time it needs to be sent, and report the data volume of the second data packet, without having to report the time it needs to be sent. The network device can allocate transmission resources to the first data packet based on the time it needs to be sent. Based on the different characteristics of the first data packet and the second data packet, the terminal device generates BSR#1 containing time information and BSR#2 not containing time information, respectively. BSR#1 containing time information can improve the reliability of the network device in allocating transmission resources to data packets that need to be sent within the first time range. BSR#2 does not need to contain time information, which can reduce the transmission resources occupied by the BSR.

[0138] In a second possible implementation manner, BSR#1 adopts one of the above-mentioned traditional BSR formats, and BSR#1 includes indication information, where the indication information indicates the cache status of the first data packet indicated by BSR#1.

[0139] For example, the terminal device generates BSR#1 and BSR#2 using a traditional BSR format. Unlike the first implementation, which uses time information to indicate the time when the first data packet needs to be sent, this implementation uses indication information in BSR#1 to indicate that BSR#1 is the BSR for the first data packet. Consequently, the terminal device can use fewer bits to report the buffer status of the first and second data packets.

[0140] Optionally, BSR#1 includes a sub-header field, which includes the indication information. The structure of the sub-header field is shown in Figure 2. The indication information can be the LCID or eLCID in the sub-header field, or the indication information can be a separate information field.

[0141] When the indication information is the LCID or eLCID in the sub-header field, the first value of the LCID or eLCID in BSR#1 may directly or indirectly indicate the cache status of the first data packet.

[0142] When the indication information is a separate information field, the indication information may use any one or more reserved bits in the sub-header field. For example, a bit in the sub-header field may be configured to indicate whether the corresponding data packet is the first data packet, such as when the bit is set to 1, indicating that the corresponding data packet is the first data packet.

[0143] It should be noted that for BSR#2, the network device can determine the data packet corresponding to BSR#2 by the LCID or eLCID not being the first value, or can also indicate that the corresponding data packet is the second data packet by setting the above bit to 0. This application does not specifically limit this.

[0144] It should also be noted that BSR#1 may also include both indication information and time information. That is, BSR#1 may adopt an emergency BSR format that includes time information, and the included subheader may also include indication information. In this case, the indication information may also indicate that BSR#1 is the BSR for the first data packet by indicating the emergency BSR format. For example, the first value of the LCID corresponds to an emergency BSR format. The network device may determine that BSR#1 is the BSR for the first data packet based on the selection rules for the emergency BSR format. This is not specifically limited in this application.

[0145] Optionally, after BSR#2 is sent, the terminal device does not restart the periodic BSR timer. That is, the terminal device does not need to restart the periodic BSR timer every time it sends a BSR. The terminal device can restart the periodic BSR timer after sending a BSR other than the BSR for the data packet that needs to be sent within the first time. For example, the terminal device can restart the periodic BSR timer after sending a BSR other than the emergency BSR format.

[0146] If a terminal device restarts the periodic BSR timer each time it completes sending a BSR, and if the terminal device frequently sends BSRs for the first data packet due to other triggering conditions, thereby frequently restarting the periodic BSR timer, then the terminal device will have difficulty sending periodic BSRs, which may result in the BSRs for the second data packet, which are mostly periodic, not being reported for a long time. Therefore, in this embodiment, the terminal device does not restart the periodic BSR timer after BSR#1 is sent, but restarts the periodic BSR timer after BSR#2 is sent, which can improve the reliability of BSR reporting.

[0147] It should be noted that if the type of BSR#2 is a padding BSR and the number of padding bits is insufficient to report the cache status of the entire second data packet, then the cache status of the second data packet can be decomposed into multiple BSR#2s for reporting. In this case, the terminal device does not need to restart the periodic BSR timer until all multiple BSR#2s are sent.

[0148] In some implementations, if a terminal device determines that a first data packet is within a first time range based on time-to-expiry information, i.e., the time-to-expiry time of the first data packet is within a first time range, and the terminal device generates a BSR#1 based on the first data packet, but over time, the BSR#1 for the first data packet is not transmitted, and the time-to-expiry time of the first data packet becomes outside the first time range, then the first data packet no longer needs to be transmitted within the first time range. In this case, for a BSR#1 that was generated / triggered for a data packet that was already required to be transmitted within the first time range, the terminal device may cancel the triggered BSR#1, or cancel the BSR#1 and re-determine that the first data packet no longer needs to be transmitted within the first time range, and generate a report based on the data packet no longer required to be transmitted within the first time range. Alternatively, the terminal device may not cancel the transmission of the BSR#1 or the triggered BSR#1, but may set the data volume information in the BSR#1 to indicate a data volume of 0. Therefore, upon receiving the BSR#1, the network device may also learn that the data volume of the data packet that needs to be transmitted within the first time range is 0. Alternatively, the terminal device may not cancel the sending of BSR#1 or the triggered BSR#1, but may set the data volume information in BSR#1 to indicate the remaining data volume after deducting the data volume that has fallen outside the first time range from the current data volume. For example, if the original data volume is 10 bytes, and there are 2 bytes of data packets, and as time passes, the corresponding distance to expiration time falls outside the first time range, then the data volume information in BSR#1 is set to indicate the data volume is 8 bytes.

[0149] S330: The network device determines a transmission resource for the first data packet and / or a transmission resource for the second data packet.

[0150] When the network device receives BSR#1 from the terminal device, the network device can determine that BSR#1 is the BSR for the first data packet based on the time information and / or indication information in BSR#1. For example, if the first data packet needs to be transmitted within the first time range, transmission resources can be allocated to the first data packet first. When the network device receives BSR#2 from the terminal device, the network device can confirm that BSR#2 is the BSR for the second data packet by determining that BSR#2 does not include time information, that BSR#2 includes indication information indicating that BSR#2 is the BSR for the second data packet, or by other means, and thus can process the second data packet as a normal data packet.

[0151] S340: The network device sends authorization information to the terminal device. Correspondingly, the terminal device receives the authorization information from the network device.

[0152] The grant information indicates transmission resources for the first data packet and / or transmission resources for the second data packet.

[0153] S350: The terminal device sends multiple data packets to the network device.

[0154] The terminal device sends the first data packet and / or the second data packet based on the transmission resources indicated by the authorization information.

[0155] Based on this technical solution, the data packets cached by the terminal device include data packets with different attributes. The terminal device can generate a first cache status report and a second cache status report for the data packets with different attributes respectively. Therefore, when the network device allocates transmission resources for the first data packet and the second data packet based on the two cache status reports, it can take into account the different attributes of the first data packet and the second data packet, thereby improving the performance of reporting the cache status.

[0156] It is understandable that the above describes an implementation in which BSR#1 includes a time domain (i.e., time information) and BSR#2 does not include a time domain. In another possible implementation, both BSR#1 and BSR#2 may include a time domain. In this case, the time domain in BSR#2 may be set by default (e.g., a value of 0, an index indicating the second data packet, or a flag indicating the second data packet, etc.) to indicate that BSR#2 reports the cache status of the second data packet. In another possible implementation, both BSR#1 and BSR#2 may not include a time domain, and the cache status of the first data packet or the second data packet may be determined by the indication information in the sub-header fields of BSR#1 and BSR#2.

[0157] It should be noted that any of the methods for generating BSR#1 described in the embodiments of this application can be used alone, and any of the methods for generating BSR#2 can be used alone, and any of the methods for generating BSR#1 and any of the methods for generating BSR#2 can be used in combination. This embodiment of the application does not impose any restrictions on the order in which the terminal device generates BSR#1 and generates BSR#2. This order can be related to the cached data packets or the method used by the terminal device to generate the BSR.

[0158] The present application also provides a method for reporting cache status. Different from the method shown in Figure 3, the terminal device can use a BSR to report the cache status of data packets with different characteristics, and indicate it through the indication information and / or time information in the BSR. The method is explained below in conjunction with Figure 5.

[0159] FIG5 is a schematic flowchart of another method for reporting cache status provided in an embodiment of the present application.

[0160] S510: The terminal device buffers at least one data packet.

[0161] For ease of description, in the embodiment described in FIG5 , the first data packet and the second data packet are still used to represent at least one data packet with different attributes. For example, the first data packet is still used to represent a data packet that needs to be completed within the first time range, while the second data packet is used to represent a data packet that does not need to be completed within the first time range. For an introduction to the first data packet, the second data packet, and the first time range, please refer to the description of step S310 in FIG3 , and will not be repeated here. The at least one data packet may fall into one of the following three situations, depending on whether it contains the first data packet: Scenario 1: only the first data packet; Scenario 2: both the first and second data packets; and Scenario 3: only the second data packet.

[0162] S520: The terminal device sends a buffer status report (hereinafter referred to as BSR#3) to the network device. Correspondingly, the network device receives the BSR#3 from the terminal device.

[0163] BSR#3 includes indication information and / or time information. The indication information indicates whether the at least one data packet includes the first data packet, and the time information indicates the time when the at least one data packet needs to be sent. In other words, the terminal device can generate BSR#3 in any of the following three forms.

[0164] Form 1: BSR#3 includes indication information but does not include time information. The subheader field of BSR#3 may include the indication information, and BSR#3 may adopt one of the traditional BSR formats. The indication information may be an LCID or eLCID in the subheader field, or the indication information may be a separate information field. For an explanation of the indication information and the traditional BSR format, please refer to the description of S320 in Figure 3 and will not be repeated here. In this case, the network device may determine whether the first data packet is included in the at least one data packet based on the indication information, and if so, may prioritize allocating transmission resources to all of the at least one data packet.

[0165] Form 2: BSR#3 includes time information but no indication information. The format of BSR#3 can adopt one of the emergency BSR formats. For an explanation of the emergency BSR format, refer to the description of S320 in Figure 3 and are not repeated here. In this case, the network device can determine which of the at least one data packet needs to be transmitted within the first time range based on the time information in BSR#3, thereby preferentially allocating transmission resources to the data packet of the at least one data packet that needs to be transmitted within the first time range.

[0166] Form 3: BSR#3 includes time information and indication information. The subheader field of BSR#3 may include the indication information, and the format of BSR#3 may adopt one of the emergency BSR formats. This allows the network device to prioritize allocating transmission resources to the at least one data packet that needs to be sent within the first time range.

[0167] For ease of description, the three forms of BSR described above are collectively referred to as new BSRs below. The terminal device can be pre-configured to use one of the new BSR forms to generate BSR#3. Alternatively, the terminal device can also determine whether to adopt the new BSR based on whether the first data packet is included in at least one data packet. If the terminal device determines that the first data packet is included in at least one data packet, the terminal device can adopt BSR#3 in any form of the new BSR described above (if indication information is included, in this case the indication information indicates that the first data packet is included in the at least one data packet). If the terminal device determines that the first data packet is not included in the at least one data packet, the terminal device can select a BSR that does not include indication information and time information based on the provisions of the existing protocol. For example, if the at least one data packet includes the first data packet, the BSR#3 includes time information, or time information and indication information. If the at least one data packet does not include the first data packet, the BSR#3 does not include time information, thereby reducing bit consumption.

[0168] It should be noted that for BSR#3 containing time information, the time information can indicate the time when all of the at least one data packet need to be sent. Alternatively, the time information can also indicate the time when the first data packet in the at least one data packet needs to be sent. Exemplarily, the first data packet in the at least one data packet is configured with a time domain in BSR#3, and the second data packet is configured with a time information resource in the middle of BSR#3. Another exemplary embodiment is that each data packet in the at least one data packet is configured with a time domain in BSR#3, the time domain corresponding to the first data packet indicates the time when the first data packet needs to be sent, and the time domain corresponding to the second data packet is set by default (for example, a value of 0, an index indicating the second data packet, or a flag indicating a non-first data packet, etc.), indicating that it does not need to be sent within the first time range.

[0169] Regarding the manner in which the terminal device determines whether the first data packet is included in at least one data packet, reference may be made to the description of step S310 in FIG. 3 above. Specifically, the terminal device may determine the first data packet using at least one of the following information: service type information, time-to-expiry information, importance information of the PDU set to which it belongs, and type information of the PDU set to which it belongs. For a more detailed description, reference may be made to the description of step S310 in FIG. This description is omitted here.

[0170] Optionally, when at least one data packet includes a first data packet and a second data packet, the code stream corresponding to the cache status information of the first data packet may be encapsulated within the code stream corresponding to the cache status information of the second data packet. Thus, the cache status information of the first data packet may reach the network device earlier than the cache status information of the second data packet, enabling the network device to accelerate the allocation of transmission resources for the first data packet and improve data transmission reliability.

[0171] Optionally, if at least one data packet includes the second data packet and BSR#3 has not been completely sent, the terminal device does not restart the periodic BSR timer. That is, if BSR#3 includes the cache status information of the second data packet and the cache status information of the second data packet has not been completely sent, the terminal device does not restart the periodic BSR timer. After the cache status information of the second data packet has been completely sent, the terminal device can restart the periodic BSR timer, thereby improving the reliability of BSR reporting.

[0172] S530: The network device determines a transmission resource for at least one data packet.

[0173] When BSR#3 uses the aforementioned form 1 and includes indication information but does not include time information, if the indication information indicates that the first data packet exists in the at least one data packet, the network device may preferentially allocate transmission resources to all of the at least one data packet. When BSR#3 uses the aforementioned form 2 or form 3 and includes time information, the network device may determine the first data packet in the at least one data packet based on the time information and preferentially allocate resources to the first data packet.

[0174] S540: The network device sends authorization information to the terminal device. Correspondingly, the terminal device receives the authorization information from the network device.

[0175] The grant information indicates transmission resources of at least one data packet.

[0176] S550: The terminal device sends at least one data packet to the network device. Correspondingly, the network device receives the at least one data packet from the terminal device.

[0177] The terminal device may send at least one data packet using the transmission resources indicated by the authorization information.

[0178] Based on the present technical solution, the terminal device can carry indication information and / or time information in the cache status report, and use the indication information to indicate whether at least one data packet contains a data packet with the attribute of the first data packet, and / or use the time information to indicate the attribute of at least one data packet regarding the time when the transmission needs to be completed, so that the network device can allocate transmission resources based on the attribute of at least one data packet, thereby improving the performance of reporting the cache status report.

[0179] The above describes the way in which the terminal device reports the cache status of the cached PDU. In some embodiments, some of the PDUs cached by the terminal device may be discarded due to transmission failure. For example, the PDU has not obtained transmission resources and is discarded due to PDCP timeout (discard timer), or the PDU has been sent to the network device, but due to poor network conditions, decoding or verification fails and is discarded by the network device. Among them, the value of the PDCP discard timer (discard timer) of the PDU set can be determined based on the value of AN-PSDB. If the time a data packet waits to be sent in the terminal device is close to the AN-PSDB, that is, the time to expiration is less than or equal to the preset threshold, then the data packet is said to be about to expire.

[0180] When a certain number of PDUs in a PDU set are discarded, the terminal device may discard the remaining PDUs in the PDU set, triggering frame-level packet loss or PDU set discarding. This is because the remaining PDUs are no longer necessary to be sent. Even if the network device successfully receives the remaining PDUs, it cannot successfully obtain information based on the remaining PDUs. The present application also provides a method for discarding PDUs, which is described below.

[0181] Step 1: The network device determines whether to perform PDU set integrated handling.

[0182] PDU set integrity processing refers to discarding all PDUs in a PDU set when the number of discarded PDUs in the PDU set is greater than or equal to N, where N is a positive integer.

[0183] The network device can determine whether to perform PDU aggregate integrity processing based on the QoS parameters of the QoS flow associated with the DRB associated with the PDCP entity corresponding to the PDU set. The QoS parameters include enable information #1, which indicates whether PDU aggregate integrity processing is performed on the PDUs in the QoS flow. The following three possible methods are described:

[0184] Method 1: If the value of the enabling information #1 of the QoS flows mapped to the same DBR is the same, and the enabling information #1 indicates that the PDUs in the QoS flow need to be processed with PDU set integrity, the network device determines that the PDCP entity associated with the DBR needs to perform PDU set integrity processing on the associated PDU set.

[0185] Method 2: If the QoS flows mapped to the same DBR contain enabling information #1 in at least one QoS flow indicating that the PDUs in the QoS flow need to be processed with PDU set integrity, the network device determines that the PDCP entity associated with the DBR needs to perform PDU set integrity processing on the associated PDU set.

[0186] Mode 3: Only QoS flows with the same value of Enable Information #1 can be mapped to the same DBR. If Enable Information #1 indicates that the relevant QoS flows perform PDU aggregate integrity processing, the network device determines that the PDCP entity associated with the DBR needs to perform PDU aggregate integrity processing on the associated PDU set.

[0187] Step 2: The network device sends PDCP enabling information #2 to the terminal device.

[0188] According to step 1, the network device determines enabling information #2 of the PDCP entity based on enabling information #1, where the enabling information #2 instructs the PDCP entity to perform PDU aggregate integrity processing.

[0189] It can be understood that since the PDCP layer of the terminal device cannot obtain the enabling information #1 of the QoS flow, and the PDU set integrity processing of the PDCP entity needs to be consistent with the PDU set integrity processing of the associated QoS flow, the network device can instruct the PDCP entity of the terminal device to perform PDU set integrity processing through PDCP configuration (including enabling information #2) based on the known PDU set integrity processing parameters of the QoS flow (enabling information #1).

[0190] The enabling information #2 may directly instruct the PDCP entity of the terminal device to perform PDU aggregate integrity processing. Alternatively, the PDCP enabling information #2 may indirectly instruct the PDCP entity of the terminal device to perform PDU aggregate integrity processing. For example, the PDCP enabling information #2 includes information about the PDU aggregate discard timer. When the number of PDUs in a PDU aggregate that has reached the duration specified by the PDU aggregate discard timer is greater than or equal to N, all PDUs in the PDU aggregate are discarded.

[0191] Step 3: The terminal device performs PDU aggregate integrity processing based on PDCP enable information #2.

[0192] When N PDUs in a PDU set reach the time specified by the PDU set discard timer, the terminal device discards all PDUs in the PDU set. In other words, if the terminal device receives enable information #2, the terminal device may discard all PDUs in the PDU set based on the PDU set discard timer instead of the PDU level discard timer.

[0193] Exemplarily, the discard timer of the Mth PDU in the PDU set can be set as a PDU set-level discard timer. When the Mth PDU is discarded due to timeout (M is a positive integer, M can be equal to N), the terminal device can discard all PDUs in the PDU set at the same time.

[0194] It should be noted that, in this example, since the discard timer of the Mth PDU can be used for the discard timing of the entire PDU set in this example, the discard timer of the Mth PDU cannot stop timing due to the successful transmission of the Mth PDU. In other words, the PDCP entity of the transmitting side device (the terminal device in this example) determines that the Mth PDU has been successfully received through methods such as a PDCP status report or a lower layer indication, and the transmitting side terminal device does not discard the SDU corresponding to the Mth PDU, so that the timing of the Mth PDU timer continues to run.

[0195] Corresponding to the methods provided in the above-mentioned method embodiments, the embodiments of the present application also provide corresponding devices, which include modules for executing the corresponding methods in the above-mentioned method embodiments. The modules can be software, hardware, or a combination of software and hardware. It is understood that the technical features described in the above-mentioned method embodiments are also applicable to the following device embodiments. Therefore, for the content not described in detail, please refer to the above method embodiments. For the sake of brevity, they will not be repeated here.

[0196] Figure 6 is a schematic block diagram of a communication device 10 provided in an embodiment of the present application. The device 10 includes a transceiver module 11 and / or a processing module 12. The transceiver module 11 can implement corresponding communication functions, and the processing module 12 is used to process data. In other words, the transceiver module 11 is used to perform operations related to receiving and sending, and the processing module 12 is used to perform other operations in addition to receiving and sending. The transceiver module 11 can also be referred to as a communication interface or a communication unit.

[0197] Optionally, the device 10 may also include a storage module 13, which can be used to store instructions and / or data. The processing module 12 can read the instructions and / or data in the storage module so that the device can implement the actions of the equipment or network element in the aforementioned method embodiments.

[0198] In a first design, the apparatus 10 may correspond to the terminal device in the above method embodiment, or a component (such as a chip) of the terminal device.

[0199] The device 10 can implement the steps or processes executed by the terminal device in the above method embodiment, wherein the transceiver module 11 can be used to execute the transceiver-related operations of the terminal device in the above method embodiment, and the processing module 12 can be used to execute the processing-related operations of the terminal device in the above method embodiment.

[0200] In one possible implementation, the apparatus 10 can implement the steps or processes executed by the terminal device in the embodiment shown in FIG. 3 above, wherein the processing module 12 is configured to cache multiple data packets, the multiple data packets including a first data packet and a second data packet; and the transceiver module 11 is configured to send a first cache status report and a second cache status report, the first cache status report indicating the cache status of the first data packet, and the second cache status report indicating the cache status of the second data packet. The first data packet and the second data packet differ in at least one of the following attributes: service type, time to expiration, importance of the protocol data unit set to which they belong, and type of the protocol data unit set to which they belong.

[0201] In another possible implementation, the device 10 can implement the steps or processes executed by the terminal device in the embodiment shown in FIG. 5 above, wherein the processing module 12 is used to cache at least one data packet; the transceiver module 11 is used to send a cache status report, the cache status report indicates the cache status of at least one data packet, and the cache status report includes indication information and / or time information, the indication information indicates whether the at least one data packet contains the first data packet, and the time information indicates the time when the at least one data packet needs to be sent. The first data packet is related to at least one of the following information: service type information, time to expiration information, importance information of the protocol data unit set to which it belongs, and type information of the protocol data unit set to which it belongs.

[0202] In a second design, the apparatus 10 may correspond to the network device in the above method embodiment, or a component (such as a chip) of the network device.

[0203] The device 10 can implement the steps or processes executed by the network device in the above method embodiment, wherein the transceiver module 11 can be used to perform the transceiver-related operations of the network device in the above method embodiment, and the processing module 12 can be used to perform the processing-related operations of the network device in the above method embodiment.

[0204] In one possible implementation, the apparatus 10 can implement the steps or processes executed by the network device in the embodiment shown in FIG. 3 above, wherein the transceiver module 11 is configured to receive a first cache status report and a second cache status report, wherein the first cache status report indicates the cache status of the first data packet and the second cache status report indicates the cache status of the second data packet; and the processing module 12 is configured to determine the transmission resources of the first data packet and the transmission resources of the second data packet based on the first cache status report and the second cache status report. The first data packet and the second data packet may differ in at least one of the following attributes: service type, time to expiration, importance of the protocol data unit set to which they belong, and type of the protocol data unit set to which they belong.

[0205] In another possible implementation, the device 10 can implement the steps or processes executed by the network device in the embodiment shown in FIG. 5 above, wherein the transceiver module 11 is used to receive a cache status report from the terminal device, the cache status report indicates the cache status of at least one data packet, and the cache status report includes indication information and / or time information, the indication information indicates whether the at least one data packet contains the first data packet, and the time information indicates the time when the at least one data packet needs to be sent; the processing module 12 is used to determine the transmission resources of at least one data packet based on the cache status report. The first data packet is related to at least one of the following information: service type information, time to expiration information, importance information of the protocol data unit set to which it belongs, and type information of the protocol data unit set to which it belongs; the network device determines the transmission resources of at least one data packet based on the cache status report.

[0206] It should be understood that the specific process of each module executing the above corresponding steps has been described in detail in the above method embodiments, and for the sake of brevity, it will not be repeated here.

[0207] It should also be understood that the device 10 here is embodied in the form of a functional module. The term "module" here may refer to an application specific integrated circuit (ASIC), an electronic circuit, a processor (such as a shared processor, a dedicated processor or a group processor, etc.) and a memory for executing one or more software or firmware programs, a combined logic circuit and / or other suitable components that support the described functions. In an optional example, those skilled in the art will understand that the device 10 may be specifically the terminal device in the above embodiment, and may be used to execute the various processes and / or steps corresponding to the terminal device in the above method embodiments; or, the device 10 may be specifically the network device in the above embodiment, and may be used to execute the various processes and / or steps corresponding to the network device in the above method embodiments. To avoid repetition, it will not be described here.

[0208] The apparatus 10 of each of the above-mentioned solutions has the function of implementing the corresponding steps performed by the device (such as a terminal device or a network device) in the above-mentioned method. This function can be implemented by hardware, or it can be implemented by hardware executing the corresponding software. The hardware or software includes one or more modules corresponding to the above-mentioned functions; for example, the transceiver module can be replaced by a transceiver (for example, the sending unit in the transceiver module can be replaced by a transmitter, and the receiving unit in the transceiver module can be replaced by a receiver), and other units, such as the processing module, can be replaced by a processor to respectively perform the transceiver operations and related processing operations in each method embodiment.

[0209] In addition, the transceiver module 11 may also be a transceiver circuit (for example, may include a receiving circuit and a sending circuit), and the processing module may be a processing circuit.

[0210] FIG7 is a schematic diagram of another communication device 20 provided in an embodiment of the present application. Device 20 includes a processor 21, which is configured to execute computer programs or instructions stored in memory 22, or read data / signaling stored in memory 22, to perform the methods described in the above method embodiments. Optionally, there may be one or more processors 21.

[0211] Optionally, as shown in FIG7 , the apparatus 20 further includes a memory 22 for storing computer programs or instructions and / or data. The memory 22 may be integrated with the processor 21 or may be separately provided. Optionally, there may be one or more memories 22 .

[0212] Optionally, as shown in Figure 7, the device 20 further includes a transceiver 23, which is used to receive and / or send signals. For example, the processor 21 is used to control the transceiver 23 to receive and / or send signals.

[0213] As a solution, the apparatus 20 is used to implement the operations performed by the terminal device in each of the above method embodiments.

[0214] As another solution, the device 20 is used to implement the operations performed by the network device in the above various method embodiments.

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

[0216] It should also be understood that the memory mentioned in the embodiments of the present application may be a volatile memory and / or a non-volatile memory. Among them, the non-volatile memory may 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 may be a random access memory (RAM). For example, RAM can be used as an external cache. By way of example and not limitation, RAM includes the following forms: static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced synchronous dynamic random access memory (ESDRAM), synchronous link dynamic random access memory (SLDRAM), and direct rambus RAM (DR RAM).

[0217] It should be noted that when the processor is a general-purpose processor, DSP, ASIC, FPGA or other programmable logic device, discrete gate or transistor logic device, discrete hardware component, the memory (storage module) can be integrated into the processor.

[0218] It should also be noted that the memory described herein is intended to include, but is not limited to, these and any other suitable types of memory.

[0219] 8 is a schematic diagram of a chip system 30 according to an embodiment of the present application. The chip system 30 (or also referred to as a processing system) includes a logic circuit 31 and an input / output interface 32.

[0220] The logic circuit 31 may be a processing circuit in the chip system 30. The logic circuit 31 may be coupled to a storage unit and call instructions in the storage unit so that the chip system 30 can implement the methods and functions of the various embodiments of the present application. The input / output interface 32 may be an input / output circuit in the chip system 30, outputting information processed by the chip system 30 or inputting data or signaling information to be processed into the chip system 30 for processing.

[0221] As a solution, the chip system 30 is used to implement the operations performed by the terminal device in the various method embodiments described above. For example, the logic circuit 31 is used to implement the processing-related operations performed by the terminal device in the method embodiments described above (Figures 6 and 7); the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the terminal device in the method embodiments described above (Figures 6 and 7).

[0222] As another solution, the chip system 30 is used to implement the operations performed by the network device in the various method embodiments described above. For example, the logic circuit 31 is used to implement the processing-related operations performed by the network device in the method embodiments described above (see Figures 6 and 7 ); the input / output interface 32 is used to implement the sending and / or receiving-related operations performed by the virtual infrastructure manager in the method embodiments described above (see Figures 6 and 7 ).

[0223] An embodiment of the present application further provides a computer-readable storage medium on which computer instructions for implementing the methods executed by the device in the above-mentioned method embodiments are stored.

[0224] For example, when the computer program is executed by a computer, the computer can implement the method executed by the terminal device in each embodiment of the above method.

[0225] For another example, when the computer program is executed by a computer, the computer can implement the methods performed by the network device in each embodiment of the above method.

[0226] An embodiment of the present application also provides a computer program product, comprising instructions, which, when executed by a computer, implement the methods performed by a device (such as a terminal device or a network device) in the above-mentioned method embodiments.

[0227] An embodiment of the present application also provides a communication system, including the aforementioned terminal device and network device.

[0228] The explanation of the relevant contents and beneficial effects of any of the above-mentioned devices can be referred to the corresponding method embodiments provided above, which will not be repeated here.

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

[0230] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. For example, the computer can be a personal computer, a server, or a network device, etc. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (e.g., a floppy disk, a hard disk, a magnetic tape), an optical medium (e.g., a DVD), or a semiconductor medium (e.g., a solid state disk (SSD)). For example, the aforementioned available medium includes, but is not limited to, various media that can store program code, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.

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

Claims

1. A method for reporting cache status, characterized in that: The method comprises: Buffering a plurality of data packets, the plurality of data packets comprising a first data packet and a second data packet; Sending a first cache status report and a second cache status report to the network device, wherein the first cache status report indicates a cache status of the first data packet, and the second cache status report indicates a cache status of the second data packet; Among them, at least one of the following attributes of the first data packet and the second data packet is different: service type, time to expiration, importance of the protocol data unit set to which it belongs, or type of the protocol data unit set to which it belongs.

2. The method according to claim 1, characterized in that The sending the first cache status report and the second cache status report to the network device includes: A protocol data unit is sent to the network device, the protocol data unit including the first cache status report and the second cache status report.

3. The method according to claim 1 or 2, characterized in that The first cache status report includes first data volume information and time information, the first data volume information indicates the data volume of the first data packet, and the time information indicates the time when the first data packet needs to be sent. The second cache status report includes second data volume information, and the second data volume information indicates the data volume of the second data packet.

4. The method according to claim 1 or 2, characterized in that: The first buffer status report includes indication information, where the indication information indicates that the first buffer status report indicates a buffer status of the first data packet.

5. The method according to claim 4, characterized in that The first buffer status report includes a sub-header field, and the indication information is a logical channel identification field or an extended logical channel identification field of the sub-header field.

6. The method according to any one of claims 1 to 5, characterized in that If the second buffer status report is not sent completely or the second buffer status report is in a truncated buffer status report format, the periodic buffer status report timer is not restarted.

7. The method according to any one of claims 1 to 6, characterized in that The first data packet needs to be sent within a first time range.

8. The method according to any one of claims 1 to 7, characterized in that The method further comprises: Configuration information is received from the network device, the configuration information indicating the first time range.

9. The method according to any one of claims 1 to 8, characterized in that The format of the first cache status report is determined based on at least one of the following information: the number of logical channels from which the first data packet comes, the number of logical channel groups from which the first data packet comes, the number of protocol data unit sets from which the first data packet comes, the type of the first cache status report, or the number of bits occupied by the first cache status report.

10. The method according to any one of claims 1 to 9, characterized in that The second cache status report is a fill cache status report, and a format of the second cache status report is determined based on the number of bits occupied by the first cache status report.

11. A method for reporting cache status, characterized in that: The method comprises: Buffer at least one data packet; A cache status report is sent to a network device, wherein the cache status report indicates the cache status of the at least one data packet, and the cache status report includes indication information and / or time information, wherein the indication information indicates whether the at least one data packet includes a first data packet, and the time information indicates the time when the at least one data packet needs to complete sending, wherein the first data packet is related to at least one of the following information: service type information, time information until expiration, importance information of the protocol data unit set to which it belongs, or type information of the protocol data unit set to which it belongs.

12. The method according to claim 11, characterized in that Before sending the cache status report to the network device, the method further includes: It is determined that the at least one data packet includes the first data packet, and the cache status report includes the time information, or the time information and the indication information, or the indication information.

13. The method according to claim 11 or 12, characterized in that: The first data packet needs to be sent within a first time range.

14. The method according to any one of claims 11 to 13, characterized in that The method further comprises: Configuration information is received from the network device, the configuration information indicating the first time range.

15. The method according to any one of claims 11 to 14, characterized in that The cache status report includes a sub-header field, and the sub-header field includes the indication information.

16. The method according to claim 15, characterized in that, The indication information is a logical channel identification field or an extended logical channel identification field of the sub-header field.

17. The method according to any one of claims 11 to 16, characterized in that The at least one data packet does not include the first data packet, the buffer status report is not sent completely or the buffer status report is in a truncated buffer status report format, and the periodic buffer status report timer is not restarted.

18. A method for reporting cache status, characterized in that: The method comprises: Receiving a first cache status report and a second cache status report from a terminal device, wherein the first cache status report indicates a cache status of a first data packet, and the second cache status report indicates a cache status of the second data packet; Determine a transmission resource of the first data packet and a transmission resource of the second data packet based on the first cache status report and the second cache status report; Among them, at least one of the following attributes of the first data packet and the second data packet is different: service type, time to expiration, importance of the protocol data unit set to which it belongs, or type of the protocol data unit set to which it belongs.

19. The method according to claim 18, characterized in that The receiving the first cache status report and the second cache status report from the terminal device includes: A protocol data unit is received from the terminal device, wherein the protocol data unit includes the first cache status report and the second cache status report.

20. The method according to claim 18 or 19, characterized in that The first cache status report includes first data volume information and time information, the first data volume information indicates the data volume of the first data packet, and the time information indicates the time when the first data packet needs to be sent. The second cache status report includes second data volume information, and the second data volume information indicates the data volume of the second data packet.

21. The method according to claim 18 or 19, characterized in that The first buffer status report includes indication information, where the indication information in the first buffer status report indicates a buffer status of the first data packet.

22. The method according to claim 21, characterized in that The first buffer status report includes a sub-header field, and the indication information is a logical channel identification field or an extended logical channel identification field of the sub-header field.

23. The method according to any one of claims 18 to 22, characterized in that The first data packet needs to be sent within a first time range.

24. The method according to any one of claims 18 to 23, characterized in that The method further comprises: Configuration information is sent to the terminal device, where the configuration information indicates the first time range.

25. A method for reporting cache status, characterized in that: The method comprises: receiving a cache status report from a terminal device, the cache status report indicating a cache status of the at least one data packet, the cache status report including indication information and / or time information, the indication information indicating whether the at least one data packet includes a first data packet, the time information indicating a time when the at least one data packet needs to be sent, wherein the first data packet is related to at least one of the following information: service type information, time information to expiration, importance information of a protocol data unit set to which it belongs, or type information of a protocol data unit set to which it belongs; A transmission resource for the at least one data packet is determined based on the buffer status report.

26. The method of claim 25, wherein: The first data packet needs to be sent within a first time range.

27. The method according to claim 25 or 26, characterized in that The method further comprises: Configuration information is sent to the terminal device, where the configuration information indicates the first time range.

28. The method according to any one of claims 25 to 27, characterized in that The cache status report includes a sub-header field, and the sub-header field includes the indication information.

29. The method of claim 28, wherein: The indication information is a logical channel identification field or an extended logical channel identification field of the sub-header field.

30. A communication device, characterized in that: comprising a module for executing the method according to any one of claims 1 to 10, or a module for executing the method according to any one of claims 11 to 17, 31. A communication device, characterized in that: The method comprises a module for executing the method as claimed in any one of claims 18 to 24, or a module for executing the method as claimed in any one of claims 25 to 29.

32. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which, when executed on a computer, enables the computer to execute the method as claimed in any one of claims 1 to 10, or enables the computer to execute the method as claimed in any one of claims 11 to 17, or enables the computer to execute the method as claimed in any one of claims 18 to 24, or enables the computer to execute the method as claimed in any one of claims 25 to 29.

33. A computer program product, characterized in that The method comprises a computer program code, which, when executed on a computer, enables the computer to implement the method as claimed in any one of claims 1 to 10, or enables the computer to implement the method as claimed in any one of claims 11 to 17, or enables the computer to implement the method as claimed in any one of claims 18 to 24, or enables the computer to implement the method as claimed in any one of claims 25 to 29.

34. A communication device, characterized in that: The method comprises a processor coupled to a memory, the memory being used to store a computer program or instructions, the processor being used to execute the computer program or instructions in the memory, so that the apparatus performs the method according to any one of claims 1 to 10, or the method according to any one of claims 11 to 17, or the computer implements the method according to any one of claims 18 to 24, or the method according to any one of claims 25 to 29.

35. A communication system, characterized in that: Comprises the communication device as claimed in claim 30 and the communication device as claimed in claim 31.