Buffer status report reporting method and apparatus, buffer status report receiving method and apparatus, and communication system

Abstract

Provided in the embodiments of the present application are a buffer status report reporting method and apparatus, a buffer status report receiving method and apparatus, and a communication system. The buffer status report reporting apparatus is applied to a terminal device, and comprises a first processing unit, which controls the terminal device, such that the terminal device executes the following operations: determining that the number of uplink filler bits is greater than or equal to the sum of a first long buffer status report and sub-headers of the first long buffer status report; and reporting the first long buffer status report.

Description

Method, device and communication system for reporting and receiving cache status reports Technical Field

[0001] The embodiments of the present application relate to the field of communication technologies. Background Art

[0002] In the Third Generation Partnership Project (3GPP) standard, the Buffer Status Report (BSR) procedure is used to provide the serving base station (e.g., gNB) of a terminal device with information about the amount of uplink data in the Medium Access Control (MAC) entity so that the serving gNB can promptly provide appropriate uplink resources for the terminal device to send the uplink data.

[0003] The Buffer Status Report Media Access Control Control Element (BSR MAC CE) includes a Buffer Size (BS) field, which identifies the total amount of data to be sent for all logical channels in a Logical Channel Group (LCG) after the Media Access Control Protocol Data Unit (MAC PDU) is constructed. The Buffer Size field can be 5 or 8 bits long. According to the Buffer Size table (also known as the Buffer Status table or BSR table, etc.) specified in the 3GPP standard, the value of a BS field corresponds to a buffer size within a specific range. The current Buffer Size table is generated using an exponential formula. In this table, the larger the BS field value, the larger the buffer size range. In other words, the higher the BS field value, the greater the quantization error.

[0004] 3GPP began studying enhancements for Extended Reality (XR) services in Release 18. XR services refer to all environments that combine reality and virtuality, as well as human-computer interactions generated by computer technology and wearable devices. XR services can include Virtual Reality (VR) services, Augmented Reality (AR) services, and Mixed Reality (MR) services. Since the video images often transmitted in XR services are usually large in size and need to be sent quickly, when the terminal device performs such XR services, the value of the BS field of the BSR used is likely to fall within the larger value range of the Buffer Size table, resulting in a large quantization error. This error may be understood by the network as the terminal device requiring more uplink transmission resources, thereby increasing the network's delay in allocating uplink resources, reducing capacity, generating more interference, and affecting the power consumption of the terminal device.

[0005] Based on these considerations, 3GPP agreed to introduce a new Buffer Size table (BS table) for Release 18 XR, defined in the MAC specification. If the amount of data to be sent by an LCG falls within the range of the new table, the LCG's BS uses the new table; otherwise, the traditional BS table is used. Because the values ​​in each BS field in the new BS table correspond to a smaller range of buffer sizes, quantization error is reduced, allowing the network to more accurately allocate uplink resources, reducing interference and lowering power consumption in terminal devices.

[0006] To indicate whether an LCG uses the new BS table or the traditional BS table, a new BSR MAC CE is defined. This MAC CE includes a buffer size table (BT) field, indicating whether the corresponding LCG uses the new BS table or the traditional BS table. This new BSR MAC CE can be called, for example, a Refined Long BSR MAC CE or a Refined BSR MAC CE.

[0007] It should be noted that the above introduction to the technical background is merely intended to provide a clear and complete description of the technical solutions of this application and facilitate understanding by those skilled in the art. Simply because these solutions are described in the background technology section of this application, it should not be assumed that the above technical solutions are well known to those skilled in the art.

[0008] Summary of the Invention

[0009] Buffer Status Report (BSR) is classified into Regular BSR, Padding BSR and Periodic BSR according to the triggering conditions.

[0010] Currently, 3GPP has not yet determined whether a Padding BSR supports reporting a Refined Long BSR, that is, whether a Refined Long BSR can be used as a Padding BSR. Therefore, the conditions under which a Refined Long BSR should be reported for a Padding BSR are not specified. Because the lengths of the Refined Long BSR MAC CE and the Long BSR MAC CE are different—for example, the Refined Long BSR MAC CE has one more byte (i.e., contains the BT field bitmap) than the Long BSR MAC CE—there is a need to determine which BSR MAC CE a terminal device should report when a specific number of padding bits is present.

[0011] In response to at least one of the above problems or other similar problems, embodiments of the present application provide a method, device, and communication system for reporting and receiving a cache status report.

[0012] According to one aspect of an embodiment of the present application, a buffer status report reporting apparatus is provided, which is applied to a terminal device. The apparatus includes a first processing unit, which controls the terminal device to cause the terminal device to perform the following operations:

[0013] Determining that the number of uplink padding bits is greater than or equal to the sum of a first long buffer status report (Refined Long BSR) and a subheader size of the first long buffer status report; and

[0014] Report the first long buffer status report.

[0015] According to another aspect of an embodiment of the present application, a device for receiving a cache status report is provided, which is applied to a network device. The device includes a second processing unit, which controls the network device to cause the network device to perform the following operations:

[0016] receiving a first long buffer status report reported by a terminal device in an uplink padding bit,

[0017] The number of the uplink padding bits is greater than or equal to the sum of the size of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report.

[0018] One of the beneficial effects of the embodiments of the present application is that: the present application provides a method for reporting and receiving a cache status report when the number of uplink padding bits is within a predetermined range, and standardizes the behavior of the terminal device in reporting the cache status report.

[0019] With reference to the following description and accompanying drawings, specific embodiments of the present application are disclosed in detail, indicating the manner in which the principles of the present application can be employed. It should be understood that the embodiments of the present application are not limited in scope. Within the spirit and scope of the appended claims, the embodiments of the present application include many variations, modifications and equivalents.

[0020] Features described and / or illustrated with respect to one embodiment may be used in the same or similar manner in one or more other embodiments, combined with features in other embodiments, or substituted for features in other embodiments.

[0021] It should be emphasized that the term "include / comprising" when used herein refers to the presence of features, integers, steps or components, but does not exclude the presence or addition of one or more other features, integers, steps or components. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] The elements and features described in one figure or one embodiment of the present application can be combined with the elements and features shown in one or more other figures or embodiments. In addition, in the accompanying drawings, similar reference numerals represent corresponding parts in several figures and can be used to indicate corresponding parts used in more than one embodiment.

[0023] FIG1 is a schematic diagram of a communication system of the present application;

[0024] FIG2 is a schematic diagram of a long buffer status report media access control control element;

[0025] FIG3 is a schematic diagram of an improved long buffer status report media access control element;

[0026] FIG4 is a schematic diagram of a method for reporting a cache status report in an embodiment of the first aspect;

[0027] FIG5 is a schematic diagram of a method for receiving a cache status report according to an embodiment of the second aspect;

[0028] FIG6 is a schematic diagram of a reporting device for a cache status report according to an embodiment of the third aspect;

[0029] FIG7 is a schematic diagram of a receiving device for a cache status report according to an embodiment of the fourth aspect;

[0030] FIG8 is a schematic diagram of a terminal device according to an embodiment of the fifth aspect;

[0031] FIG9 is a schematic diagram of a network device according to an embodiment of the fifth aspect. DETAILED DESCRIPTION

[0032] The above and other features of the present application will become apparent through the following description with reference to the accompanying drawings. In the description and the accompanying drawings, specific embodiments of the present application are disclosed in detail, which illustrate some embodiments in which the principles of the present application can be adopted. It should be understood that the present application is not limited to the described embodiments. On the contrary, the present application includes all modifications, variations and equivalents that fall within the scope of the appended claims.

[0033] In the embodiments of the present application, the terms "first", "second", etc. are used to distinguish different elements from the name, but do not indicate the spatial arrangement or temporal order of these elements, and these elements should not be limited by these terms. The term "and / or" includes any one and all combinations of one or more of the associated listed terms. The terms "comprising", "including", "having", etc. refer to the presence of the stated features, elements, components or components, but do not exclude the presence or addition of one or more other features, elements, components or components.

[0034] In the embodiments of this application, the singular forms "a," "the," etc. include plural forms and should be broadly understood to mean "a" or "a type" rather than being limited to "one." Furthermore, the term "said" should be understood to include both singular and plural forms, unless the context clearly indicates otherwise. Furthermore, the term "according to" should be understood to mean "at least in part based on...", and the term "based on" should be understood to mean "at least in part based on...", unless the context clearly indicates otherwise.

[0035] In the embodiments of the present application, the term "communication network" or "wireless communication network" may refer to a network that complies with any of the following communication standards, such as Long Term Evolution (LTE), enhanced Long Term Evolution (LTE-A, LTE-Advanced), Wideband Code Division Multiple Access (WCDMA), High-Speed ​​Packet Access (HSPA), etc.

[0036] Furthermore, communication between devices in the communication system may be carried out according to communication protocols of any stage, for example, including but not limited to the following communication protocols: 1G (generation), 2G, 2.5G, 2.75G, 3G, 4G, 4.5G, 5G, New Radio (NR), 6G and future communications, etc., and / or other communication protocols currently known or to be developed in the future.

[0037] In the embodiments of the present application, the term "network device" refers to, for example, a device in a communication system that connects a terminal device to the communication network and provides services to the terminal device. Network devices may include, but are not limited to, the following devices: base station (BS), access point (AP), transmission reception point (TRP), broadcast transmitter, mobile management entity (MME), gateway, server, radio network controller (RNC), base station controller (BSC), etc.

[0038] Base stations may include, but are not limited to, NodeB (NB), evolved NodeB (eNodeB or eNB), 5G base station (gNB), 6G base station, and subsequent evolved base stations, IAB hosts, etc., and may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

[0039] In the embodiments of the present application, the term "user equipment" (UE) refers to, for example, a device that accesses a communication network through a network device and receives network services, and may also be referred to as "terminal equipment" (TE). Terminal equipment may be fixed or mobile, and may also be referred to as a mobile station (MS), terminal, user, subscriber station (SS), access terminal (AT), station, mobile terminal (MT), etc.

[0040] Terminal devices may include, but are not limited to, the following devices: cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, wearable devices, terminals that support XR services, and the like.

[0041] For another example, in scenarios such as the Internet of Things (IoT), the terminal device can also be a machine or device for monitoring or measurement, including but not limited to: machine type communication (MTC) terminal, vehicle-mounted communication terminal, device-to-device (D2D) terminal, machine-to-machine (M2M) terminal, and so on.

[0042] In addition, the term "network side" or "network device side" refers to one side of the network, which can be a base station or one or more network devices as described above. The term "user side" or "terminal side" or "terminal device side" refers to the user or terminal side, which can be a UE or one or more terminal devices as described above. Unless otherwise specified herein, "device" can refer to either network equipment or terminal equipment.

[0043] In the following description, the terms "uplink control signal" and "uplink control information (UCI)" or "physical uplink control channel (PUCCH)" are interchangeable, and the terms "uplink data signal" and "uplink data information" or "physical uplink shared channel (PUSCH)" are interchangeable to avoid confusion.

[0044] The terms "downlink control signal" and "downlink control information (DCI)" or "physical downlink control channel (PDCCH)" are interchangeable, and the terms "downlink data signal" and "downlink data information" or "physical downlink shared channel (PDSCH)" are interchangeable.

[0045] In addition, the uplink signal may include an uplink data signal and / or an uplink control signal and / or PRACH and / or SRS, etc., which may also be referred to as uplink transmission (UL transmission) or uplink information or uplink channel. Sending / receiving uplink transmission on an uplink resource may be understood as sending / receiving the uplink transmission using the uplink resource. The downlink signal may include a downlink data signal and / or a downlink control signal and / or a synchronization signal (SS, such as PSS / SSS) and / or a broadcast channel (PBCH) and / or an SSB (SS / PBCH block, including PSS, SSS and PBCH and its DMRS) and / or CSI-RS, etc., which may also be referred to as downlink transmission (DL transmission) or downlink information or downlink channel. Sending / receiving downlink transmission on a downlink resource may be understood as sending / receiving the downlink transmission using the downlink resource. In the embodiment of the present application, the high-layer signaling may be, for example, radio resource control (RRC) signaling; RRC signaling may include, for example, an RRC message, such as a broadcast / public RRC message / signaling (e.g., a master information block (MIB), system information), a dedicated RRC message / signaling; or an RRC information element (RRC information element, RRC IE); or an information field included in an RRC message or an RRC information element (or an information field included in an information field). The high-layer signaling may also be, for example, a medium access control layer (MAC) signaling; or a MAC control element (MAC control element, MAC CE). However, the present application is not limited thereto.

[0046] In the embodiments of the present application, a plurality refers to at least two, or two or more.

[0047] In the embodiments of the present application, predefined means specified in the protocol or determined according to the rules specified in the protocol, and no additional configuration is required. Configuration / indication refers to direct or indirect configuration / indication by the network device through high-layer signaling and / or physical layer signaling. Configuration / indication can be achieved by introducing high-layer parameters in high-layer signaling, and high-layer parameters refer to information fields (fields) and / or information elements / information units / information elements (IEs) in high-layer signaling. Physical layer signaling refers to, for example, control information (DCI) carried by the physical downlink control channel or control information carried by the sequence, but is not limited thereto.

[0048] For ease of description, the following description will be made using a base station as an example of an access network device. In the following description, "if ...", "under ..." and "when ..." can be used interchangeably without causing confusion.

[0049] The following describes the scenarios of the embodiments of the present application through examples, but the present application is not limited thereto.

[0050] FIG1 is a schematic diagram of a communication system according to an embodiment of the present application, schematically illustrating a situation using a terminal device and a network device as an example. As shown in FIG1 , a communication system 100 may include a network device 101 and terminal devices 102 and 103. For simplicity, FIG1 illustrates only two terminal devices and one network device as an example, but the embodiments of the present application are not limited thereto.

[0051] In the embodiment of the present application, existing services or future services can be transmitted between the network device 101 and the terminal devices 102 and 103. For example, these services may include but are not limited to: enhanced mobile broadband (eMBB), massive machine type communication (mMTC), ultra-reliable and low-latency communication (URLLC), and XR services, etc.

[0052] Among them, the terminal device 102 can send data to the network device 101, for example, using an authorized or configured authorized transmission mode. The network device 101 can receive data sent by one or more terminal devices 102 and feedback information or downlink control information to the terminal device 102, such as confirmation ACK / non-confirmation NACK information or scheduling new or retransmitted downlink control information. The terminal device 102 can confirm the end of the transmission process, or can continue new data transmission, or can retransmit data based on the feedback information or downlink control information.

[0053] It is worth noting that FIG1 shows that both terminal devices 102 and 103 are within the coverage range of network device 101, but the present application is not limited thereto. Both terminal devices 102 and 103 may not be within the coverage range of network device 101, or one terminal device 102 may be within the coverage range of network device 101 while the other terminal device 103 is outside the coverage range of network device 101.

[0054] In each embodiment of the present application, "reporting" refers to a terminal device sending information to a network device, and "reporting" can be replaced by "report" or "instruction", etc.

[0055] In the various embodiments of the present application, the improved long buffer status report media access control control element (Refined Long BSR MAC CE) may also be referred to as a refined long buffer status report media access control control element, or may also be referred to as an improved buffer status report media access control control element (Refined BSR MAC CE) or a refined buffer status report media access control control element, which have the same meaning.

[0056] Similarly, in each embodiment of the present application, the improved long buffer status report (Refined Long BSR) may also be referred to as a refined long buffer status report, or as an improved buffer status report (Refined BSR MAC CE) or a refined buffer status report, which have the same meaning.

[0057] Embodiments of the first aspect

[0058] Figure 2 is a schematic diagram of a Long BSR MAC CE, and Figure 3 is a schematic diagram of a Refined Long BSR MAC CE. As shown in Figures 2 and 3, the Refined Long BSR MAC CE has one more byte than the Long BSR MAC CE (i.e., it contains a bitmap of the BT field).

[0059] The description of the formats of the improved long buffer status report media access control control element (Refined Long BSR MAC CE) and the long buffer status report media access control control element (Long BSR MAC CE) may be shown in Table 1 below.

[0060] Table 1

[0061] For Regular BSR, Padding BSR, and Periodic BSR, there are definitions as described in Table 2.

[0062] Table 2

[0063] Currently, 3GPP agrees that for regular BSR and periodic BSR, if the amount of buffered data of at least one logical channel group (LCG) configured with additionalBSR-TableAllowed (indicating that the new BS table can be used) is within the range of the new BS table, the terminal device reports a Refined Long BSR MAC CE, which reports all logical channel groups (LCGs) with data to be sent, as shown in Table 3.

[0064] Table 3

[0065] In the prior art, the reporting process of the padding BSR (Padding BSR) may be as shown in Table 4.

[0066] Table 4

[0067] In the prior art, in the process of reporting a padding BSR, the relationship between the number of uplink padding bits and the type of the reported BSR may be as shown in Table 5.

[0068] Table 5

[0069] In the above Table 4 or Table 5, there is no provision for the relationship between the number of uplink padding bits and the reporting of the Refined Long BSR MAC CE.

[0070] In order to solve the above problems, an embodiment of the first aspect of the present application provides a method for reporting a cache status report, which is applied to a terminal device, for example, the terminal device 102 shown in Figure 1.

[0071] FIG4 is a schematic diagram of a method for reporting a cache status report in an embodiment of the first aspect. As shown in FIG4 , the method for reporting a cache status report includes:

[0072] Operation 401: The terminal device determines whether the number of uplink padding bits is greater than or equal to the sum of a first long buffer status report and a subheader size of the first long buffer status report; and

[0073] Operation 402: The terminal device reports the first long buffer status report.

[0074] In the present application, uplink padding bits may refer to padding bits in uplink resources (or MAC PDU corresponding to uplink resources), for example, uplink resources may be uplink resources for new transmission, may be uplink shared channel (UL-SCH) resources or uplink grants (uplink grant) or resources indicated by uplink grants, etc., and padding bits may be the remaining bits in the UL-SCH resources or uplink grants before the terminal device performs logical channel prioritization (LCP) on the uplink resources (MAC CE for BSR included for padding and / or MAC CE for SL-BSR included for padding). The first long buffer status report may be, for example, a refined long buffer status report (Refined Long BSR).

[0075] In operation 402, the terminal device reports a first long buffer status report. For example, the terminal device determines to report the first long buffer status report in padding bits, and / or generates a first long buffer status report MAC CE, and / or sends the first long buffer status report. That is, the first long buffer status report is carried in uplink resources and included in padding bits, and the terminal device sends a MAC PDU including the padding bits in the uplink resources. Therefore, operations 401 and 402 are operations for a padding buffer status report (padding BSR).

[0076] As shown in FIG4 , the method for reporting the cache status report may further include:

[0077] Operation 400: The terminal device receives indication information from the network device, and the indication information instructs the terminal device to report the first long cache status report or the second long cache status report when the number of uplink padding bits is greater than or equal to the sum of the first long cache status report and the sub-header size of the first long cache status report.

[0078] The indication information is included in a Radio Resource Control (RRC) message or a Media Access Control Element (MAC CE). The second long buffer status report may be, for example, a long buffer status report (Long BSR).

[0079] In some embodiments of the present application, operation 400 may precede operation 401 , and thus, the terminal device may perform operations 401 and 402 under the instruction of the indication information.

[0080] In addition, in some other embodiments of the present application, operation 400 may not be present, and thus the terminal device can autonomously decide to perform operation 401.

[0081] As shown in FIG4 , the method for reporting the cache status report may further include:

[0082] Operation 403: The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the subheader sizes of the second long buffer status report and the second long buffer status report, and is less than the sum of the subheader sizes of the first long buffer status report and the first long buffer status report; and

[0083] Operation 404: The terminal device reports the second long buffer status report.

[0084] Based on operations 403 and 404 , the terminal device may send a second long buffer status report (eg, Long BSR) under appropriate conditions.

[0085] According to the embodiment of the first aspect, a method for reporting a buffer status report when the number of uplink padding bits is within a predetermined range is specified, and the behavior of a terminal device in reporting a buffer status report is standardized.

[0086] The following describes a method for reporting a cache status report in accordance with the first aspect of the present application through multiple embodiments. The following embodiments are all based on the condition that "the number of uplink padding bits is greater than or equal to the sum of the size of the first long cache status report and the subheader of the first long cache status report." In addition, some embodiments may add other conditions based on this condition.

[0087] In the following embodiments, the first long buffer status report may be, for example, a refined long buffer status report (Refined Long BSR), and the second long buffer status report may be, for example, a long buffer status report (Long BSR).

[0088] In the following embodiments, a logical channel group (LCG) has data to be sent, which may also be referred to as: the logical channel group has data to be sent, or the logical channel group has buffered data. This data may include data of a Packet Data Convergence Protocol (PDCP) entity and / or data of a Radio Link Control (RLC) entity corresponding to all logical channels in the logical channel group.

[0089] In the following embodiments, the first table is, for example, the new buffer size table (BS table) mentioned above, that is, the new BS table, which may also be expressed as a BSR table or a Buffer status table.

[0090] In some embodiments of the present application, a terminal device that supports Refined Long BSR and / or supports a new BS table performs operation 401, for example, the terminal device indicates to the network device in its capability information that it supports Refined Long BSR and / or supports a new BS table, or the network device configures at least one LCG of the terminal device to allow the use of the first table (for example, at least one LCG is configured with additionalBSR-TableAllowed).

[0091] In some embodiments of the present application, the sum of the sizes of the first long buffer status report and the subheader of the first long buffer status report is the sum of the sizes of the first long buffer status report MAC CE and its subheader.

[0092] Example 1

[0093] In embodiment 1, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and the terminal device reports the first long buffer status report.

[0094] For example, when the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the sub-header size of the first long buffer status report, the terminal device reports the first long buffer status report; otherwise, the terminal device reports the second long buffer status report (e.g., Long BSR).

[0095] The following Table 6a or Table 6b is a specific example of Example 1.

[0096] Table 6a

[0097] Table 6b

[0098] Example 2

[0099] In embodiment 2, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of the first table, and the terminal device reports the first long buffer status report. Wherein, when the logical channel group is configured with a predetermined parameter, the logical channel group is configured to allow the use of the first table, and the predetermined parameter is, for example, additionalBSR-TableAllowed. The first table is, for example, the new buffer size table (BS table) described above, that is, the new BS table.

[0100] For example, if the number of padding bits is greater than or equal to the size of the Refined Long BSR plus the subheader of the Refined Long BSR, and at least one LCG is configured with additionalBSR-TableAllowed, then the terminal device reports the Refined Long BSR, otherwise, the terminal device reports the second long buffer status report (e.g., Long BSR).

[0101] The following Table 7a or Table 7b is a specific example of Example 2.

[0102] Table 7a

[0103] Table 7b

[0104] Example 3

[0105] In embodiment 3, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of the first table, and the logical channel group has data to be sent, and the terminal device reports the first long buffer status report. Wherein, when the logical channel group is configured with a predetermined parameter, the logical channel group is configured to allow the use of the first table, and the predetermined parameter is, for example, additionalBSR-TableAllowed. The first table is, for example, the new buffer size table (BS table) described above, that is, the new BS table.

[0106] For example, if the number of padding bits is greater than or equal to the size of the Refined Long BSR plus the sub-header of the Refined Long BSR, and at least one LCG is configured with additionalBSR-TableAllowed and the LCG has data to be sent, then the terminal device reports the Refined Long BSR, otherwise, the terminal device reports the second long buffer status report (e.g., Long BSR).

[0107] The following Table 8a or Table 8b is a specific example of Example 3.

[0108] Table 8a

[0109] Table 8b

[0110] Example 4

[0111] In embodiment 4, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of the first table, and the amount of data to be sent of the logical channel group is within the buffer size range in the first table, and the terminal device reports the first long buffer status report.

[0112] When the logical channel group is configured with a predetermined parameter, the logical channel group is configured to allow the use of a first table, such as additionalBSR-TableAllowed. The first table is, for example, the new buffer size table (BS table) described above, i.e., the new BS table.

[0113] For example, if the number of padding bits is greater than or equal to the size of the Refined Long BSR plus the subheader of the Refined Long BSR, and at least one LCG is configured with additionalBSR-TableAllowed and the amount of data to be sent by the LCG is within the buffer size (buffer size) specified in the new BS table, then the terminal device reports the Refined Long BSR; otherwise, the terminal device reports the second long buffer status report (for example, Long BSR).

[0114] The following Table 9a or 9b is a specific example of Example 4.

[0115] Table 9a

[0116] Table 9b

[0117] In some embodiments of the present application, the type of buffer status report to be reported can be determined based on the amount of data to be sent by the logical channel group (LCG), in addition to the condition that "the number of uplink padding bits is greater than or equal to the sum of the size of the first long buffer status report and the subheader of the first long buffer status report." This will be described below with reference to specific embodiments.

[0118] Example 5

[0119] In embodiment 5, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and the logical channel group has no data to be sent, for example, all LCGs configured with the terminal device have no data to be sent.

[0120] Under the conditions of Example 5, the terminal device may adopt any one of the following options A1, A2, and A3.

[0121] Option A1:

[0122] In some examples of option A1, the terminal device reports a first long buffer status report; or, when at least one logical channel group (LCG) is configured to allow use of the first table (e.g., configured with additionalBSR-TableAllowed), the terminal device reports a first long buffer status report.

[0123] In Option A1, the number of Buffer Size (BS) fields included in the Refined Long BSR MAC CE may be 0. For example, as shown in Table 10 below.

[0124] Table 10

[0125] Option A2:

[0126] In some examples of option A2, the terminal device reports a second long buffer status report (e.g., Long BSR); or, no logical channel group (LCG) is configured to allow use of the first table (e.g., additionalBSR-TableAllowed is not configured), and the terminal device reports a second long buffer status report (e.g., Long BSR).

[0127] Option A3:

[0128] In some examples of option A3, the terminal device reports a short buffer status report (Short BSR); or, no logical channel group (LCG) is configured to allow the use of the first table (for example, additionalBSR-TableAllowed is not configured), and the terminal device reports a short buffer status report.

[0129] Example 6

[0130] In Example 6, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and that one logical channel group has data to be sent (e.g., only one logical channel group has data to be sent).

[0131] Under the conditions of Example 6, the terminal device may adopt any one of the following options B1, B2, and B3.

[0132] Option B1:

[0133] In some examples of option B1:

[0134] The terminal device reports the first long buffer status report; or

[0135] At least one logical channel group (LCG) is configured to allow use of the first table (e.g., configured with additionalBSR-TableAllowed), and the terminal device reports a first long buffer status report (e.g., Refined Long BSR); or

[0136] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the terminal device reports a first long buffer status report (for example, Refined Long BSR); or

[0137] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the terminal device reports a first long buffer status report (for example, Refined Long BSR).

[0138] Option B2:

[0139] Some examples of option B2:

[0140] The terminal device reports a second longest buffer status report (eg, Long BSR); or

[0141] No logical channel group (LCG) is configured to allow the use of the first table (eg, configured with additionalBSR-TableAllowed), and the terminal device reports a second long buffer status report (eg, Long BSR); or

[0142] The logical channel group (LCG) with data to be sent is not configured to allow the use of the first table (for example, not configured with additionalBSR-TableAllowed), and the terminal device reports a second long buffer status report (for example, Long BSR); or

[0143] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size range in the first table, and the terminal device reports a second long buffer status report (for example, Long BSR).

[0144] Option B3:

[0145] In some examples of option B3:

[0146] The terminal device reports a Short Buffer Status Report (Short BSR); or

[0147] No logical channel group (LCG) is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the terminal device reports a short buffer status report (Short BSR); or

[0148] The logical channel group (LCG) with data to be sent is not configured to allow the use of the first table (for example, not configured with additionalBSR-TableAllowed), and the terminal device reports a short buffer status report (Short BSR); or

[0149] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size range in the first table, and the terminal device reports a short buffer status report (Short BSR).

[0150] Example 7

[0151] In embodiment 7, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent.

[0152] Under the conditions of Example 7, the terminal device can adopt any one of the following options C1 and C2.

[0153] Option C1:

[0154] In some examples of option C1:

[0155] The terminal device reports a first long buffer status report (eg, Refined Long BSR); or

[0156] At least one logical channel group (LCG) is configured to allow use of the first table (for example, configuring additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0157] At least one logical channel group (LCG) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0158] At least one logical channel group (LCG) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the terminal device reports a first long buffer status report.

[0159] Option C2:

[0160] In some examples of option C2:

[0161] The terminal device reports a second longest buffer status report (eg, Long BSR); or

[0162] No logical channel group (LCG) is configured to allow the use of the first table (eg, configured with additionalBSR-TableAllowed), and the terminal device reports a second long buffer status report (eg, Long BSR); or

[0163] None of the logical channel groups (LCGs) with data to be sent is configured to allow the use of the first table (for example, configured with additionalBSR-TableAllowed), and the terminal device reports a second long buffer status report (for example, Long BSR); or

[0164] At least one logical channel group (LCG) with data to be sent is configured to allow the use of the first table (e.g., configured with additionalBSR-TableAllowed), and the terminal device reports a second long buffer status report (e.g., Long BSR); or

[0165] At least one logical channel group (LCG) is configured to allow use of the first table (e.g., configured with additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size in the first table, and the terminal device reports a second long buffer status report (e.g., Long BSR).

[0166] In some examples of this application, Examples 5, 6, and 7 can be represented as Table 11 below.

[0167] Table 11

[0168] According to the embodiment of the first aspect, a method for reporting a buffer status report when the number of uplink padding bits is within a predetermined range is specified, and the behavior of a terminal device in reporting a buffer status report is standardized.

[0169] Embodiments of the second aspect

[0170] The embodiment of the second aspect provides a method for receiving a cache status report, which is applied to a network device, such as the network device 101 in Figure 1. For the parts of the embodiment of the second aspect that are the same as those of the embodiment of the first aspect, reference can be made to the description of the embodiment of the first aspect, which will not be repeated here.

[0171] FIG5 is a schematic diagram of a method for receiving a cache status report according to an embodiment of the second aspect. As shown in FIG5 , the method includes:

[0172] Operation 501: Receive a first long buffer status report reported by a terminal device in an uplink padding bit, wherein the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (e.g., Refined Long BSR) and the subheader size of the first long buffer status report.

[0173] In at least one embodiment, as shown in FIG5 , the method further includes:

[0174] Operation 500: The network device sends an indication message to the terminal device, wherein the indication message instructs the terminal device to report the first long buffer status report or the second long buffer status report (Long BSR) when the number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report.

[0175] The indication information is included in a radio resource control (RRC) message or a medium access control element (MAC CE).

[0176] In at least one embodiment, as shown in FIG5 , the method further includes:

[0177] Operation 502: The network device receives the second long buffer status report reported by the terminal device, wherein the number of uplink padding bits is greater than or equal to the sum of the sub-header sizes of the second long buffer status report (Long BSR) and the second long buffer status report, and is less than the sum of the sub-header sizes of the first long buffer status report (Refined Long BSR) and the first long buffer status report.

[0178] In the following embodiments, the first long buffer status report may be, for example, a refined long buffer status report (Refined Long BSR), and the second long buffer status report may be, for example, a long buffer status report (Long BSR).

[0179] In the following embodiments, a logical channel group (LCG) has data to be sent, which may also be referred to as: the logical channel group has data to be sent, or the logical channel group has buffered data. This data may include data of a Packet Data Convergence Protocol (PDCP) entity and / or data of a Radio Link Control (RLC) entity corresponding to all logical channels in the logical channel group.

[0180] In at least one embodiment of operation 501: the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report.

[0181] In at least one embodiment of operation 501: the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the logical channel group has data to be sent, and the network device receives the first long buffer status report.

[0182] In at least one embodiment of operation 501: the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent of the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0183] In at least one embodiment of operation 501:

[0184] The number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and the logical channel group has no data to be sent:

[0185] The network device receives the first long buffer status report; or

[0186] At least one of the logical channel groups (LCGs) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0187] The network device receives a second long buffer status report (Long BSR) reported by the terminal device; or

[0188] None of the logical channel groups (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0189] The network device receives a short buffer status report (Short BSR) reported by the terminal device; or

[0190] None of the logical channel groups (LCGs) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the short buffer status report.

[0191] In at least one embodiment of operation 501:

[0192] The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and a logical channel group has data to be sent:

[0193] The network device receives the first long buffer status report; or

[0194] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0195] The logical channel group (LCG) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0196] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0197] In at least one embodiment of operation 501:

[0198] The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and a logical channel group has data to be sent:

[0199] The network device receives a second long buffer status report or a short buffer status report reported by the terminal device; or

[0200] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report or the short buffer status report; or

[0201] The logical channel group (LCG) having data to be sent is not configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report or the short buffer status report; or

[0202] The logical channel group (LCG) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size range in the first table, and the network device receives the second long buffer status report or the short buffer status report.

[0203] In at least one embodiment of operation 501:

[0204] The number of uplink padding bits is greater than or equal to the sum of the subheader size of the first long buffer status report (Refined Long BSR) and the first long buffer status report, and more than one logical channel group has data to be sent:

[0205] The network device receives the first long buffer status report; or

[0206] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0207] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0208] At least one of the logical channel groups (LCGs) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0209] In at least one embodiment of operation 501:

[0210] The number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent:

[0211] The network device receives a second long buffer status report reported by the terminal device; or

[0212] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0213] None of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0214] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0215] At least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size (buffer size) in the first table, and the network device receives the second long buffer status report.

[0216] Embodiments of the third aspect

[0217] At least for the same problem as the embodiment of the first aspect, the embodiment of the third aspect of the present application provides a reporting device for a cache status report, which is applied to a terminal device and corresponds to the embodiment of the first aspect.

[0218] FIG6 is a schematic diagram of a buffer status report reporting apparatus according to an embodiment of the third aspect. As shown in FIG6 , the buffer status report reporting apparatus 600 includes: a first processing unit 701 .

[0219] The first processing unit 601 causes the terminal device to perform the following operations:

[0220] The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of a first long buffer status report (Refined Long BSR) and a subheader size of the first long buffer status report; and

[0221] The terminal device reports the first long buffer status report.

[0222] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report.

[0223] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the logical channel group has data to be sent, and the terminal device reports the first long buffer status report.

[0224] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the terminal device reports the first long buffer status report.

[0225] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and that the logical channel group has no data to be sent:

[0226] The terminal device reports the first long buffer status report; or

[0227] At least one of the logical channel groups (LCGs) is configured to allow use of a first table (additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0228] The terminal device reports a second long buffer status report (Long BSR); or

[0229] None of the logical channel groups (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0230] The terminal device reports a short buffer status report (Short BSR); or

[0231] If none of the logical channel groups (LCGs) is configured to allow the use of the first table (additionalBSR-TableAllowed), the terminal device reports the short buffer status report.

[0232] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and that a logical channel group has data to be sent:

[0233] The terminal device reports the first long buffer status report; or

[0234] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0235] The logical channel group (LCG) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0236] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size (buffer size) range in the first table, and the terminal device reports the first long buffer status report.

[0237] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and that a logical channel group has data to be sent:

[0238] The terminal device reports a second long buffer status report or a short buffer status report; or

[0239] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report or the short buffer status report; or

[0240] The logical channel group (LCG) having data to be sent is not configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report or the short buffer status report; or

[0241] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size range in the first table, and the terminal device reports the second long buffer status report or the short buffer status report.

[0242] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of a first long buffer status report (Refined Long BSR) and a subheader size of the first long buffer status report, and more than one logical channel group has data to be sent:

[0243] The terminal device reports the first long buffer status report; or

[0244] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0245] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the terminal device reports the first long buffer status report; or

[0246] At least one of the logical channel groups (LCGs) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the terminal device reports the first long buffer status report.

[0247] In at least one embodiment, the terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent:

[0248] The terminal device reports a second long buffer status report; or

[0249] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0250] None of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0251] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0252] At least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size (buffer size) in the first table, and the terminal device reports the second long buffer status report.

[0253] In at least one embodiment, the operations performed by the terminal device further include:

[0254] The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the subheader sizes of a second long buffer status report (Long BSR) and the second long buffer status report, and is less than the sum of the subheader sizes of the first long buffer status report (Refined Long BSR) and the first long buffer status report; and

[0255] The terminal device reports the second long buffer status report.

[0256] In at least one embodiment, the operations performed by the terminal device further include:

[0257] The terminal device receives indication information from a network device, and the indication information instructs the terminal device to report the first long buffer status report or the second long buffer status report (Long BSR) when the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the sub-header size of the first long buffer status report.

[0258] The indication information is included in a radio resource control (RRC) message or a medium access control element (MAC CE).

[0259] Embodiments of the fourth aspect

[0260] An embodiment of the fourth aspect of the present application provides a device for receiving a cache status report, which is applied to a network device and corresponds to the method of the embodiment of the second aspect.

[0261] FIG7 is a schematic diagram of a buffer status report receiving apparatus 700 according to an embodiment of the fourth aspect. As shown in FIG7 , the buffer status report receiving apparatus 700 includes: a second processing unit 701 .

[0262] In at least one embodiment, the second processing unit 701 controls the network device to perform the following operations:

[0263] A first long buffer status report reported by a receiving terminal device in an uplink padding bit, wherein the number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and a subheader size of the first long buffer status report.

[0264] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report.

[0265] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the logical channel group has data to be sent, and the network device receives the first long buffer status report.

[0266] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and at least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0267] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and the logical channel group has no data to be sent:

[0268] The network device receives the first long buffer status report; or

[0269] At least one of the logical channel groups (LCGs) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0270] The network device receives a second long buffer status report (Long BSR) reported by the terminal device; or

[0271] None of the logical channel groups (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0272] The network device receives a short buffer status report (Short BSR) reported by the terminal device; or

[0273] None of the logical channel groups (LCGs) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the short buffer status report.

[0274] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and a logical channel group has data to be sent:

[0275] The network device receives the first long buffer status report; or

[0276] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0277] The logical channel group (LCG) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0278] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0279] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and a logical channel group has data to be sent:

[0280] The network device receives a second long buffer status report or a short buffer status report reported by the terminal device; or

[0281] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report or the short buffer status report; or

[0282] The logical channel group (LCG) having data to be sent is not configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report or the short buffer status report; or

[0283] The logical channel group (LCG) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size range in the first table, and the network device receives the second long buffer status report or the short buffer status report.

[0284] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the subheader size of the first long buffer status report (Refined Long BSR) and the first long buffer status report, and more than one logical channel group has data to be sent:

[0285] The network device receives the first long buffer status report; or

[0286] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0287] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0288] At least one of the logical channel groups (LCGs) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0289] In at least one embodiment, the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent:

[0290] The network device receives a second long buffer status report reported by the terminal device; or

[0291] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0292] None of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0293] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0294] At least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size (buffer size) in the first table, and the network device receives the second long buffer status report.

[0295] In at least one embodiment, the operations performed by the network device further include:

[0296] The network device receives the second long buffer status report reported by the terminal device,

[0297] The number of uplink padding bits is greater than or equal to the sum of the subheader sizes of the second long buffer status report (Long BSR) and the second long buffer status report, and less than the sum of the subheader sizes of the first long buffer status report (Refined Long BSR) and the first long buffer status report.

[0298] In at least one embodiment, the operations performed by the network device further include:

[0299] The network device sends indication information to the terminal device, and the indication information instructs the terminal device to report the first long buffer status report or the second long buffer status report (Long BSR) when the number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the sub-header size of the first long buffer status report.

[0300] The indication information is included in a radio resource control (RRC) message or a medium access control element (MAC CE).

[0301] Embodiments of the fifth aspect

[0302] An embodiment of the fifth aspect of the present application provides a communication system, which may include a network device and a terminal device.

[0303] FIG8 is a schematic diagram of a terminal device according to an embodiment of the fifth aspect. As shown in FIG8 , the terminal device 800 (e.g., corresponding to the terminal device 102 in FIG1 ) may include a processor 810 and a memory 820; the memory 820 stores data and programs and is coupled to the processor 810. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication functions or other functions.

[0304] For example, the processor 810 can be configured to execute a program to implement the method in the embodiment of the first aspect.

[0305] As shown in Figure 8 , the terminal device 800 may further include: a communication module 830, an input unit 840, a display 850, and a power supply 860. The functions of these components are similar to those in the prior art and are not described in detail here. It is worth noting that the terminal device 800 does not necessarily include all of the components shown in Figure 8 , and these components are not essential. Furthermore, the terminal device 800 may also include components not shown in Figure 8 , for which reference may be made to the prior art.

[0306] FIG9 is a schematic diagram of a network device according to an embodiment of the fifth aspect. As shown in FIG9 , network device 900 (e.g., corresponding to network device 91 in FIG1 ) may include a processor 99 (e.g., a central processing unit (CPU)) and a memory 920; the memory 920 is coupled to the processor 99. The memory 920 may store various data and may also store an information processing program 930, which is executed under the control of the processor 99.

[0307] For example, the processor 99 may be configured to execute a program to implement the method described in the embodiment of the second aspect.

[0308] In addition, as shown in Figure 9, network device 900 may further include: a transceiver 940 and an antenna 950; wherein, the functions of these components are similar to those in the prior art and are not further described here. It is worth noting that network device 900 does not necessarily include all the components shown in Figure 9; in addition, network device 900 may also include components not shown in Figure 9, and reference may be made to the prior art for details.

[0309] An embodiment of the present application also provides a computer program, wherein when the program is executed in a terminal device, the program causes the terminal device to execute the method described in the embodiment of the first aspect.

[0310] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a terminal device to execute the method described in the embodiment of the first aspect.

[0311] An embodiment of the present application also provides a computer program, wherein when the program is executed in a network device, the program causes the network device to execute the method described in the embodiment of the second aspect.

[0312] An embodiment of the present application also provides a storage medium storing a computer program, wherein the computer program enables a network device to execute the method described in the embodiment of the second aspect.

[0313] The above devices and methods of the present application can be implemented by hardware or by a combination of hardware and software. The present application relates to such a computer-readable program that, when executed by a logic component, enables the logic component to implement the devices or components described above, or enables the logic component to implement the various methods or steps described above. The present application also relates to a storage medium for storing the above program, such as a hard disk, a magnetic disk, an optical disk, a DVD, a flash memory, etc.

[0314] The method / device described in conjunction with the embodiments of the present application can be directly embodied as hardware, a software module executed by a processor, or a combination of the two. For example, one or more of the functional block diagrams shown in the figure and / or one or more combinations of functional block diagrams can correspond to various software modules of the computer program flow or to various hardware modules. These software modules can respectively correspond to the various steps shown in the figure. These hardware modules can be implemented by solidifying these software modules, for example, using a field programmable gate array (FPGA).

[0315] The software module may be located in RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of storage medium known in the art. A storage medium may be coupled to a processor so that the processor can read information from the storage medium and write information to the storage medium; or the storage medium may be an integral part of the processor. The processor and the storage medium may be located in an ASIC. The software module may be stored in the memory of the mobile terminal or in a memory card that can be inserted into the mobile terminal. For example, if the device (such as a mobile terminal) uses a large-capacity MEGA-SIM card or a large-capacity flash memory device, the software module may be stored in the MEGA-SIM card or the large-capacity flash memory device.

[0316] One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may be implemented as a general-purpose processor, a digital signal processor (DSP), an application-specific integrated circuit (ASIC), a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic device, a discrete hardware component, or any appropriate combination thereof for performing the functions described in this application. One or more of the functional blocks and / or one or more combinations of functional blocks described in the accompanying drawings may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in communication with a DSP, or any other such configuration.

[0317] The present application has been described above in conjunction with specific embodiments. However, those skilled in the art should understand that these descriptions are merely illustrative and are not intended to limit the scope of protection of the present application. Those skilled in the art may make various modifications and variations to the present application based on the spirit and principles of the present application, and such modifications and variations are also within the scope of the present application.

[0318] Regarding the implementation methods including the above embodiments, the following additional notes are also disclosed:

[0319] 1. A method for receiving a cache status report, applied to a network device, the method comprising:

[0320] receiving a first long buffer status report reported by a terminal device in an uplink padding bit,

[0321] The number of the uplink padding bits is greater than or equal to the sum of the size of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report.

[0322] 2. The method as described in Note 1, wherein:

[0323] The number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and the logical channel group has no data to be sent:

[0324] The network device receives the first long buffer status report; or

[0325] At least one of the logical channel groups (LCGs) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0326] The network device receives a second long buffer status report (Long BSR) reported by the terminal device; or

[0327] None of the logical channel groups (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the terminal device reports the second long buffer status report; or

[0328] The network device receives a short buffer status report (Short BSR) reported by the terminal device; or

[0329] None of the logical channel groups (LCGs) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the short buffer status report.

[0330] 3. The method as described in Note 1, wherein:

[0331] The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and a logical channel group has data to be sent:

[0332] The network device receives the first long buffer status report; or

[0333] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0334] The logical channel group (LCG) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0335] The logical channel group (LCG) with data to be sent is configured to allow the use of the first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0336] 4. The method as described in Note 1, wherein:

[0337] The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and a logical channel group has data to be sent:

[0338] The network device receives a second long buffer status report or a short buffer status report reported by the terminal device; or

[0339] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report or the short buffer status report; or

[0340] The logical channel group (LCG) having data to be sent is not configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report or the short buffer status report; or

[0341] The logical channel group (LCG) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size range in the first table, and the network device receives the second long buffer status report or the short buffer status report.

[0342] 5. The method as described in Note 1, wherein:

[0343] The number of uplink padding bits is greater than or equal to the sum of the subheader size of the first long buffer status report (Refined Long BSR) and the first long buffer status report, and more than one logical channel group has data to be sent:

[0344] The network device receives the first long buffer status report; or

[0345] At least one logical channel group (LCG) is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0346] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of a first table (additionalBSR-TableAllowed), and the network device receives the first long buffer status report; or

[0347] At least one of the logical channel groups (LCGs) with data to be sent is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the network device receives the first long buffer status report.

[0348] 6. The method as described in Note 1, wherein:

[0349] The number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report (Refined Long BSR) and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent:

[0350] The network device receives a second long buffer status report reported by the terminal device; or

[0351] No logical channel group (LCG) is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0352] None of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0353] At least one of the logical channel groups (LCGs) having data to be sent is configured to allow use of the first table (additionalBSR-TableAllowed), and the network device receives the second long buffer status report; or

[0354] At least one logical channel group (LCG) is configured to allow the use of a first table (additionalBSR-TableAllowed), and the amount of data to be sent by the logical channel group is outside the buffer size (buffer size) in the first table, and the network device receives the second long buffer status report.

Claims

1. A cache status report reporting device, applied to a terminal device, comprising a first processing unit, the first processing unit controlling the terminal device to cause the terminal device to perform the following operations: Determining that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report; and Report the first long buffer status report.

2. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and at least one logical channel group is configured to allow use of the first table, The terminal device reports the first long buffer status report.

3. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and at least one logical channel group is configured to allow use of the first table, and the logical channel group has data to be sent, The terminal device reports the first long buffer status report.

4. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and at least one logical channel group is configured to allow use of the first table, and the amount of data to be sent by the logical channel group is within the buffer size range in the first table. The terminal device reports the first long buffer status report.

5. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and that the logical channel group has no data to be sent: The terminal device reports the first long buffer status report; or At least one of the logical channel groups is configured to allow use of a first table, and the terminal device reports the first long buffer status report; or The terminal device reports a second long buffer status report; or None of the logical channel groups is configured to allow use of the first table, and the terminal device reports the second long buffer status report; or The terminal device reports a short buffer status report; or None of the logical channel groups is configured to allow use of the first table, and the terminal device reports the short buffer status report.

6. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and that a logical channel group has data to be sent: The terminal device reports the first long buffer status report; or At least one logical channel group is configured to allow use of a first table, and the terminal device reports the first long buffer status report; or The logical channel group having data to be sent is configured to allow use of a first table, and the terminal device reports the first long buffer status report; or The logical channel group with data to be sent is configured to allow the use of the first table, and the amount of data to be sent by the logical channel group is within the buffer size range in the first table, and the terminal device reports the first long buffer status report.

7. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and that a logical channel group has data to be sent: The terminal device reports a second long buffer status report or a short buffer status report; or No logical channel group is configured to allow use of the first table, and the terminal device reports the second long buffer status report or the short buffer status report; or The logical channel group having data to be sent is not configured to allow use of the first table, and the terminal device reports the second long buffer status report or the short buffer status report; or The logical channel group with data to be sent is configured to allow the use of the first table, and the amount of data to be sent by the logical channel group is outside the cache size range in the first table, and the terminal device reports the second long cache status report or the short cache status report.

8. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent: The terminal device reports the first long buffer status report; or At least one logical channel group is configured to allow use of a first table, and the terminal device reports the first long buffer status report; or At least one of the logical channel groups having data to be sent is configured to allow use of a first table, and the terminal device reports the first long buffer status report; or At least one of the logical channel groups with data to be sent is configured to allow the use of the first table, and the amount of data to be sent by the logical channel group is within the cache size range in the first table, and the terminal device reports the first long cache status report.

9. The device according to claim 1, wherein The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and more than one logical channel group has data to be sent: The terminal device reports a second long buffer status report; or No logical channel group is configured to allow use of the first table, and the terminal device reports the second long buffer status report; or None of the logical channel groups having data to be sent is configured to allow use of the first table, and the terminal device reports the second long buffer status report; or At least one of the logical channel groups having data to be sent is configured to allow use of the first table, and the terminal device reports the second long buffer status report; or At least one logical channel group is configured to allow use of the first table, and the amount of data to be sent of the logical channel group is outside the buffer size in the first table, and the terminal device reports the second long buffer status report.

10. The device of claim 1, wherein: The operations performed by the terminal device further include: The terminal device determines that the number of uplink padding bits is greater than or equal to the sum of the subheader sizes of the second long buffer status report and the second long buffer status report, and is less than the sum of the subheader sizes of the first long buffer status report and the first long buffer status report; and The terminal device reports the second long buffer status report.

11. The device according to claim 1, wherein The operations performed by the terminal device further include: The terminal device receives indication information from a network device, and the indication information instructs the terminal device to report the first long cache status report or the second long cache status report when the number of uplink padding bits is greater than or equal to the sum of the first long cache status report and the sub-header size of the first long cache status report.

12. The apparatus of claim 11, wherein: The indication information is included in a radio resource control message or a medium access control control element.

13. A device for receiving a cache status report, applied to a network device, the device comprising a second processing unit, the second processing unit controlling the network device to cause the network device to perform the following operations: receiving a first long buffer status report reported by a terminal device in uplink fill bits, in, The number of the uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report.

14. The apparatus of claim 13, wherein: The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and at least one logical channel group is configured to allow use of the first table, The network device receives the first long buffer status report.

15. The apparatus of claim 13, wherein: The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and at least one logical channel group is configured to allow use of the first table, and the logical channel group has data to be sent. The network device receives the first long buffer status report.

16. The apparatus of claim 13, wherein: The number of uplink padding bits is greater than or equal to the sum of the first long buffer status report and the subheader size of the first long buffer status report, and at least one logical channel group is configured to allow use of the first table, and the amount of data to be sent by the logical channel group is within the buffer size range in the first table. The network device receives the first long buffer status report.

17. The apparatus of claim 13, wherein: The operations performed by the network device further include: The network device receives the second long buffer status report reported by the terminal device, The number of uplink padding bits is greater than or equal to the sum of the subheader sizes of the second long buffer status report and the second long buffer status report, and is less than the sum of the subheader sizes of the first long buffer status report and the first long buffer status report.

18. The apparatus of claim 13, wherein: The operations performed by the network device further include: The network device sends indication information to the terminal device, and the indication information instructs the terminal device to report the first long cache status report or the second long cache status report when the number of the uplink padding bits is greater than or equal to the sum of the first long cache status report and the sub-header size of the first long cache status report.

19. The apparatus of claim 18, wherein: The indication information is included in a radio resource control message or a medium access control control element.

20. A communication system comprising a terminal device and a network device, The terminal device comprises the buffer status report reporting device according to claim 1, The network device comprises the buffer status report receiving device according to claim 13.

Images