CN114390589A

CN114390589A - BSR (buffer status report) sending method, device, equipment and storage medium

Info

Publication number: CN114390589A
Application number: CN202210129193.5A
Authority: CN
Inventors: 徐立振
Original assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Current assignee: Guangdong Oppo Mobile Telecommunications Corp Ltd
Priority date: 2022-01-25
Filing date: 2022-02-11
Publication date: 2022-04-22

Abstract

The application discloses a BSR sending method, a device, equipment and a storage medium, and belongs to the field of mobile communication. The method comprises the following steps: sending a second BSR under the condition that the byte number of the uplink authorization is smaller than that of the first BSR; wherein the first BSR is a non-padding type BSR, and the byte number of the second BSR is less than or equal to the byte number of the uplink grant. According to the method and the device, the second BSR with a small number of bytes is sent under the condition that the number of bytes of the uplink authorization is smaller than that of the first BSR, the UE can be ensured to send the BSR to the base station in time, the long SR process is not needed to be used for reapplication of the uplink authorization, the uplink sending efficiency of the BSR is improved, and the uplink sending time delay of the BSR is shortened.

Description

BSR (buffer status report) sending method, device, equipment and storage medium

The present application claims priority of chinese patent application having application number 202210087920.6 entitled "BSR transmitting method, apparatus, device, and storage medium" filed on 25/01/2022, the entire contents of which are incorporated herein by reference

Technical Field

The present invention relates to the field of mobile communications, and in particular, to a method, an apparatus, a device, and a storage medium for sending a Buffer Status Report (BSR).

Background

The BSR is uplink control information sent by a User Equipment (UE) to a base station. The BSR is configured to notify the base station of how much uplink data to be sent exists in the UE, so that the base station schedules a reasonable uplink transmission resource to the UE.

In some cases, the BSR cannot be sent to the base station side in time, which affects the uplink transmission rate of the UE and causes a long uplink transmission delay.

Disclosure of Invention

The application provides a BSR sending method, a device, equipment and a storage medium, which can ensure timely sending of non-filling type BSR in certain scenes. The technical scheme is as follows:

according to an aspect of the present application, there is provided a BSR transmission method, including:

sending a second BSR under the condition that the byte number of the uplink authorization is smaller than that of the first BSR;

wherein the second BSR is a non-padding type BSR, and the byte number of the second BSR is less than or equal to the byte number of the uplink grant.

According to another aspect of the present application, there is provided a BSR transmitting apparatus, the apparatus including:

a sending module, configured to send the second BSR when the number of bytes of the uplink grant is smaller than the number of bytes of the first BSR;

According to another aspect of the present application, there is provided a terminal, including: a processor; a transceiver coupled to the processor; a memory for storing executable instructions of the processor; wherein the processor is configured to load and execute the executable instructions to implement the BSR transmitting method as described in the above aspect.

According to another aspect of the present application, there is provided a computer-readable storage medium having stored therein executable instructions that are loaded and executed by the processor to implement the BSR transmitting method as described in the above aspect.

According to another aspect of the present application, a chip is provided, where the chip includes a programmable logic circuit and/or program instructions, and when the chip is run on a terminal, the chip is configured to implement the BSR transmission method according to the above aspect.

According to another aspect of the present application, there is provided a computer program product or a computer program, the computer program product or the computer program comprising computer instructions stored in a computer-readable storage medium, from which a processor reads and executes the computer instructions, so that a terminal performs the BSR transmitting method according to the above aspect.

The beneficial effect that technical scheme that this application provided brought includes at least:

by reselecting or generating the second BSR with a small number of bytes for transmission under the condition that the number of bytes of the uplink authorization is smaller than that of the first BSR of the non-padding type, the UE can be ensured to transmit the BSR of the non-padding type to the base station in time without using a long Scheduling Request (SR) flow to reapply the uplink authorization, the uplink transmission efficiency of the BSR is improved, and the uplink transmission delay of the BSR is shortened.

Meanwhile, the mechanism for changing the first BSR into the second BSR for sending only needs to be improved on the terminal side, the network side and the communication protocol do not need to be modified correspondingly, and the modification of the network side is not involved, so that the compatibility and the application range of the technical scheme of the application are improved.

Drawings

In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

Fig. 1 is a packet format diagram of a long BSR according to an exemplary embodiment of the present application;

fig. 2 is a schematic diagram of a system architecture of a communication system provided by an exemplary embodiment of the present application;

fig. 3 is a flowchart of a BSR transmission method according to an exemplary embodiment of the present application;

fig. 4 is a flowchart of a BSR transmission method according to an exemplary embodiment of the present application;

FIG. 5 is a packet format diagram of a content field (without a header field) of a short BSR according to an exemplary embodiment of the present application;

fig. 6 is a flowchart of a BSR transmission method according to an exemplary embodiment of the present application;

fig. 7 is a flowchart of a BSR transmission method according to an exemplary embodiment of the present application;

fig. 8 is a block diagram of a BSR transmitting apparatus according to an exemplary embodiment of the present application;

fig. 9 is a schematic structural diagram of a terminal according to an exemplary embodiment of the present application.

Detailed Description

To make the objects, technical solutions and advantages of the present application more clear, embodiments of the present application will be described in further detail below with reference to the accompanying drawings.

First, a number of nouns to which this application relates are summarized:

medium Access Control (MAC): during the communication process between the UE and the network, the UE and the network will follow the principle of peer-to-peer protocol stack, and the MAC is a protocol stack located above the physical layer protocol stack.

BSR: the method and the device are used for informing the UE of the buffer storage of the data to be sent to the base station, and the base station can conveniently distribute reasonable uplink authorization to the UE. The BSR is a MAC Control Element (CE) carried in a MAC Protocol Data Unit (PDU).

Uplink grant (UL grant): the base station is used for allocating a certain amount of uplink transmission resources to the UE.

Three formats of BSR (or BSR MAC CE format): long bsr (long bsr), short bsr (short bsr), and pruned bsr (truncate bsr).

Long BSR: long format BSR, with a number of bytes (m +3) of 4 to 11 bytes. Wherein, the header field occupies 2 bytes, and the m +1 bytes occupied by the content field can bear the buffer size of 1-8 logical channel groups, where m is the number of logical channel groups.

Short BSR: the short format BSR has the byte number of 2 bytes. Wherein, the header field occupies 1 byte, and 1 byte occupied by the content field can bear the buffer size of 1 logical channel group.

BSR reduction: and performing byte-reduced BSR for adapting the size of uplink authorization on the basis of the regular BSR format. The pruned BSR is also called truncated BSR or truncated BSR. Corresponding to the Long BSR, there is a Long Truncated BSR MAC CE (Long Truncated BSR MAC CE) of variable length, such as a Long Truncated BSR MAC CE of 4 bytes in length; a long curtailed BSR MAC CE of 5 bytes length. Corresponding to the Short BSR, there is a Short Truncated BSR MAC CE (Short Truncated BSR MAC CE) of 2 bytes in length. The BSR is a BSR MAC CE type newly introduced in a New air interface system (New Radio), and is mainly used for enabling a UE to know that data of some logical channel groups are not put in resources to be reported when uplink resources are insufficient and the UE has more than one logical channel group to be reported. Different BSR formats are mainly used for different reporting scenarios.

In one example, BSRs are classified into three types: regular BSR (regular), periodic BSR (periodic BSR), and Padding BSR. That is, with respect to padding BSRs, non-padding type BSRs include regular BSRs and periodic BSRs.

In the related art, the regular BSR is transmitted in the case where the trigger condition of the regular BSR is satisfied. And transmitting the periodic BSR under the condition that the triggering condition of the periodic BSR is met. And transmitting the padding BSR under the condition that the triggering condition of the padding BSR is met.

The triggering conditions for the regular BSR generally include the following three.

1) The uplink data buffer (buffer) of the UE is empty and new data arrives.

When all Logical channels of all Logical Channel Groups (LCGs) have no uplink data that can be transmitted, if any Logical Channel belonging to any LCG becomes transmittable at this time, the UE may trigger a regular BSR.

2) High priority data arrives.

The UE may trigger a regular BSR if the UE has a higher priority than the logical channels currently available for data transmission and the logical channels belonging to a logical channel group have data to arrive.

3) When the BSR retransmission timer expires and there is data available to send in any logical channel of any LCG of the UE, the regular BSR will be triggered.

The triggering conditions for periodic BSR are: the BSR cycle TIMER (period TIMER) times out.

The triggering conditions for padding the BSR are: in the case that there is sufficient uplink resource (for transmitting other uplink information), the remaining padding portion in the uplink resource is sufficient to accommodate the BSR MAC CE, i.e., the number of bits padded in the uplink resource is greater than or equal to the sum of the BSR MAC CE and the size of its MAC subheader.

When the uplink does not send the regular BSR and the periodic BSR, the padding BSR can enable the base station to obtain the change condition of the LCG data in the UE buffer more timely. In most scenarios, the importance and priority of padding BSR is weaker than other uplink information.

For a conventional BSR and a periodic BSR, if there are multiple LCGs with transmittable data in a Transmission Time Interval (TTI) for transmitting the BSR, the reported BSR selects to use a long BSR to carry the buffer sizes of the multiple LCGs; if only 1 LCG has transmittable data, the reported BSR selects to use a short BSR to carry the buffer size of 1 LCG.

In the case of transmitting a long BSR, there may be a case where uplink resources scheduled by an uplink grant are insufficient to transmit the long BSR. For example, the length of the long BSR is 4 bytes, but the uplink resource scheduled by the uplink grant can only transmit 3 bytes, and the UE transmits an SR to the base station, where the SR is used to request the base station to reallocate the uplink grant. However, since the time consumption of the SR process cannot be controlled, a problem that a long BSR cannot be timely transmitted to the base station due to a long SR process may occur.

In the communication protocol TS38.321 of the Third Generation Partnership Project (3 GPP), it is specified that, in the case of triggering a long BSR at the MAC layer, the long BSR requires a MAC header of 2 bytes and an indefinite length content field. As shown in fig. 1, when the Logical Channel Group (LCG) configured by the MAC layer reaches 8, the content field of the long BSR is the longest, and the content field reaches 9 bytes, so that the number of bytes (m +3) of the long BSR reaches the longest 11 bytes. The format of a long BSR of up to 11 bytes, each byte comprising 8 bits, is shown in fig. 1.

The long BSR includes: R/F/LCID/L four header fields and content fields.

The four header fields of R/F/LCID/L occupy 2 bytes (OCT). In byte 1, R is a reserved bit and is set to be 0 to occupy 1 bit; f is a Service Data Unit (SDU) or the length of the control message is greater than 128 bytes, setting F to 1, otherwise setting to 0; the LCID is used to indicate a logical channel, a control message type, or a padding field. In byte 2, L indicates the length of the SDU or control message.

The content field occupies m +1 bytes, and the number m of logical channel groups is 8 in fig. 1as an example. In byte 1, IDs of 8 LCGs, i.e., bitmaps (bit maps) of 8 LCGs are contained. In byte 2, LCG is contained₁Buffer size 1; in byte 3, LCG is contained₂Buffer size 2; in byte 4, LCG is contained₃Buffer size 3; in byte 5, LCG is contained₄Buffer size 4; in byte 6, LCG is contained₅Buffer size 5; in byte 7, LCG is contained₆Buffer size 6; in byte 8, LCG is contained₇Buffer size 7; in byte 8, LCG is contained₈Buffer size 8.

Similarly, when the size of the buffer needing to transmit 1 LCG is known, the number of bytes of the long BSR is 4 bytes; when the size of a buffer area of 2 LCGs needs to be transmitted, the number of bytes of the long BSR is 5 bytes; when the size of a buffer area of 3 LCGs needs to be transmitted, the number of bytes of the long BSR is 6 bytes; when the size of a buffer area of 4 LCGs needs to be transmitted, the number of bytes of the long BSR is 7 bytes; when the size of a buffer area of 5 LCGs needs to be transmitted, the number of bytes of the long BSR is 8 bytes; when the size of a buffer area of 6 LCGs needs to be transmitted, the number of bytes of the long BSR is 9 bytes; when the buffer size of 7 LCGs needs to be transmitted, the byte number of the long BSR is 10 bytes; when a buffer size of 8 LCGs needs to be transmitted, the number of bytes of the long BSR is 11 bytes.

Taking the MAC layer with 8 logical channel groups as an example, when new data arrives or the BSR retransmission timer is overtime, a long BSR with a length of 11 bytes needs to be sent. However, if the uplink grant sent by the base station to the UE is less than 11 bytes, the MAC layer cannot send a complete long BSR.

It should be noted that, in the subsequent standard evolution, the occurrence of a long BSR with a byte number exceeding 11 bytes is not excluded.

According to the communication protocol convention of the TS38.321, under the condition that the number of bytes of the uplink grant is less than that of the long BSR and an SR Delay Timer (local Channel SR-Delay Timer) of the logical Channel is not in operation, directly triggering the UE to send an SR to the base station, where the SR is used to request to send the uplink grant of the long BSR; when the number of bytes of the uplink grant is smaller than the number of bytes of the long BSR and the SR delay timer of the logical channel is running, the UE is triggered to send the SR to the base station after the timer is overtime.

However, the sending waiting time of the SR is much longer than the issuing time of the uplink grant, so that the non-padding type long BSR on the UE side and the uplink data to be sent cannot be sent in time.

Fig. 2 is a schematic diagram illustrating a system architecture of a communication system according to an embodiment of the present application. The system architecture may include: a terminal 10 and an access network device 20.

Terminal 10 can refer to a UE, an access terminal, a subscriber unit, a subscriber station, a mobile station, a remote terminal, a mobile device, a wireless communication device, a user agent, or a user equipment. Alternatively, the terminal may be a cellular phone, a cordless phone, a SIP (Session Initiation Protocol) phone, a WLL (Wireless Local Loop) station, a PDA (Personal digital Assistant), a handheld device with Wireless communication function, a computing device or other processing device connected to a Wireless modem, a vehicle-mounted device, a wearable device, a terminal in a 5th Generation System (GS) or a terminal in a future evolved PLMN (Pub1ic Land mobile 1e Network), and the like, which is not limited by the embodiment of the present application. For convenience of description, the above-mentioned devices are collectively referred to as a terminal. The number of terminals 10 is usually plural, and one or more terminals 10 may be distributed in a cell managed by each access network device 20.

The access network device 20 is a device deployed in an access network to provide wireless communication functions for the terminal 10. The access network equipment 20 may include various forms of macro base stations, micro base stations, relay stations, access points, and the like. In systems using different radio access technologies, the names of devices that function as access network devices may differ, for example in a 5G NR system, called a nodeb or gNB. As communication technology evolves, the name "access network equipment" may change. For convenience of description, in the embodiment of the present application, the above-mentioned apparatuses providing the terminal 10 with the wireless communication function are collectively referred to as access network equipment. Alternatively, a communication relationship may be established between the terminal 10 and the core network device through the access network device 20. Illustratively, in the LTE system, the Access Network device 20 may be EUTRAN (Evolved Universal Terrestrial Radio Access Network) or one or more enodebs in EUTRAN; in a 5G NR system, the access network device 20 may be a RAN or one or more gnbs in a RAN.

Fig. 3 shows a flowchart of a BSR transmission method according to an exemplary embodiment of the present application. The present embodiment is exemplified by the method applied to the terminal 10. The method comprises the following steps:

step 202: sending a second BSR under the condition that the byte number of the uplink authorization is smaller than that of the first BSR;

illustratively, the BSR format of the first BSR is a long BSR, and the BSR format of the second BSR is a short BSR or a pruned BSR.

Illustratively, the number of bytes of the first BSR is greater than or equal to 4 bytes, for example, the number of bytes of the first BSR ranges from 4 to 11 bytes, but the case that the number of bytes of the first BSR is greater than 11 bytes is not excluded. In the embodiment of the present application, the maximum byte number of the first BSR is only illustrated as 11 bytes.

Illustratively, the first BSR and the second BSR are both non-padding type BSRs. For example, the types of the first BSR and the second BSR are regular BSRs or periodic BSRs.

In this embodiment, the number of bytes of the long BSR is greater than the number of bytes of the short BSR, and the number of bytes of the long BSR is greater than the number of bytes of the pruned BSR. In some embodiments, the number of bytes of the long BSR may be up to 11 bytes. That is, the number of bytes of the second BSR is less than the number of bytes of the first BSR.

The uplink grant is used to schedule uplink transmission resources to the UE. In this embodiment, the uplink grant is used for scheduling an uplink grant for transmitting a BSR. Or, the uplink grant is used to schedule the uplink grant for transmitting the first BSR.

In case that the number of bytes of the uplink grant (allowed to be sent) is smaller than the number of bytes of the first BSR, the UE cannot directly send the first BSR. At this time, the UE sends a second BSR, where the number of bytes of the second BSR is less than or equal to the number of bytes of the uplink grant.

In some embodiments, the UE selects or generates the long BSR in a scenario where there are multiple logical channel groups with uplink data transmission according to a generation rule of the non-padding type BSR. However, in the case that the number of bytes granted (allowed to be transmitted) in the uplink is smaller than that of the long BSR, the UE cannot directly transmit the long BSR. At this time, the UE reselects or generates a second BSR with a smaller number of bytes and then transmits the second BSR, where the number of bytes of the second BSR is less than or equal to the number of bytes of the uplink grant.

The second BSR is based on the first BSR. The second BSR is generated based on the first BSR. The second BSR is generated based on all or part of the information in the first BSR. The second BSR is generated based on the buffer information of all or a part of the Logical Channel Group (LCG) in the first BSR.

In some embodiments, the second BSR is generated based on the total information in the first BSR (or the buffer amount of the total LCGs), and the buffer amounts of the total logical channel groups are merged or compressed.

In some embodiments, the second BSR carries part of the information in the first BSR. Optionally, the second BSR carries a buffered amount of the portion of LCGs in the first BSR. For example, the second BSR carries the buffer amount of the logical channel group of the first n bits in the first BSR, which is ordered from high to low according to the priority of the LCG; for another example, the second BSR carries the buffer amounts of the first n logical channel groups in the first BSR in descending order according to the buffer amount of the LCG.

Here, the LCG priority is a numerical value indicating the priority level of the LCG, and may be simply referred to as a priority. In one example, the value of the LCG priority is in a negative correlation with the priority level, and when the value of the priority level is 1, the value represents the highest priority level; the value of the priority is 9, which represents the lowest priority.

Illustratively, the first BSR and the second BSR have the same BSR type, but different BSR formats. The number of bytes in the BSR format of the second BSR is less than the number of bytes in the BSR format of the first BSR. For example, the BSR types of the first BSR and the second BSR are both regular BSRs, or the BSR types of the first BSR and the second BSR are both periodic BSRs. For another example, the BSR format of the first BSR is a long BSR, and the BSR format of the second BSR is a short BSR or a reduced BSR.

In some embodiments, the second BSR is sent in the case where the first BSR needs to be sent but the number of bytes of the uplink grant is less than that of the first BSR. In some embodiments, the second BSR is sent in the event that the first BSR is generated but the number of bytes of the uplink grant is less than the number of bytes of the first BSR. In some embodiments, the second BSR is sent when the first BSR is a BSR to be sent but the number of bytes of the uplink grant is less than that of the first BSR.

In some embodiments, the MAC PDU is sent in the event that the number of bytes in the uplink grant is less than the number of bytes of the first BSR. The MAC PDU includes a second BSR.

In case that the number of bytes of the MAC PDU is greater than the number of bytes of the second BSR, the MAC PDU may include any one of the following combinations:

second BSR and MAC CEs other than short BSR;

in case the number of bytes of the MAC PDU is larger than the short BSR, the remaining number of bytes or bits is used to carry other MAC CEs besides the second BSR.

Second BSR and valid data;

and under the condition that the byte number of the MAC PDU is larger than the second BSR, the residual byte number or bit is used for carrying effective data. The valid data is also the uplink data in the valid state.

Second BSR, MAC CE and valid data.

In case that the number of bytes of the MAC PDU is greater than the second BSR, the remaining number of bytes or bits is used to carry other MAC CEs and valid data except the second BSR.

In summary, in the method provided in this embodiment, when the number of bytes of the uplink grant is smaller than the number of bytes of the first non-padding BSR, the second BSR with a smaller number of bytes is reselected or generated or transmitted, so that the UE can be ensured to transmit the non-padding BSR to the base station in time, and a long Scheduling Request (SR) procedure is not required to be used to re-apply for the uplink grant, thereby improving the uplink transmission efficiency of the BSR and shortening the uplink transmission delay of the BSR.

For embodiments where the first BSR is a long BSR and the second BSR is a short BSR (carrying a partial LCG):

fig. 4 shows a flowchart of a BSR transmission method according to an exemplary embodiment of the present application. The present embodiment is exemplified by the method applied to the terminal 10. The method comprises the following steps:

step 302: receiving an uplink grant;

and the terminal receives the uplink authorization sent by the base station. The uplink grant is sent dynamically or periodically. The uplink grant is used to schedule an uplink transmission resource to the terminal. In this embodiment, the uplink transmission resource is a transmission resource for transmitting a BSR.

Illustratively, the Uplink transmission resource is a Physical Uplink Shared Channel (PUSCH) resource.

The number of bytes of the uplink grant is related to the resource size of the scheduled uplink transmission resource, and the number of bytes of the uplink grant is the number of bytes allowed to be sent by the scheduled uplink transmission resource.

Step 304: whether there is a non-padding type BSR;

in some embodiments, BSRs may be classified into three types: regular BSR, periodic BSR, and padding BSR. Wherein the regular BSR or the periodic BSR belongs to a non-padding type BSR.

The triggering condition for the regular BSR generally includes at least one of the following three.

1) The uplink data buffer (buffer) of the UE is empty and new data arrives.

When all logical channels of all logical channel groups have no uplink data to transmit, if any logical channel belonging to any LCG becomes transmittable at this time, the UE triggers a regular BSR.

2) High priority data arrives.

The triggering conditions for the periodic BSR are: the BSR cycle TIMER (period TIMER) times out.

The triggering conditions for padding the BSR are: in the case of sufficient uplink resources, the padding portion is sufficient to accommodate the BSR MAC CE, i.e. the number of bits padded in the uplink resources is greater than or equal to the sum of the sizes of the BSR MAC CE and the MAC subheader thereof.

When the uplink does not send the regular BSR and the periodic BSR, the padding BSR can enable the base station to obtain the change condition of the LCG data in the UE buffer more timely.

For a regular BSR and a periodic BSR, if there are multiple LCGs with transmittable data in a Transmission Time Interval (TTI) for transmitting the BSR, the reported BSR is called a long BSR; otherwise, the reported BSR is called short BSR.

Retransmission BSR timer: after each time of sending a BSR, the UE starts the timer to determine whether the BSR needs to be retransmitted based on the subsequent control information of the base station. For example, during the validity period of the BSR retransmission timer, the UE listens to the BSR retransmission schedule of the base station, and retransmits the BSR.

If there is a BSR of non-padding type, go to step 306; if there is no non-padding type BSR, go to step 308;

step 306: if the non-filling type BSR exists, determining that the BSR format is a long BSR or a short BSR according to the number of the logical channel groups;

in some embodiments, the format of the BSR includes: short BSR and long BSR. Illustratively, LCID 61 is used for short BSR and LCID 62 is used for long BSR.

If the BSR is triggered using a regular or periodic mechanism, a long BSR or a short BSR is generated.

The long BSR is intended to accommodate information about multiple LCGs, and thus if multiple LCGs have uplink data to transmit, the long BSR is generated to provide information about the multiple LCGs. If only 1 LCG has uplink data to transmit, a short BSR is generated to provide information about a single LCG.

In this embodiment, it is assumed that determining the BSR format as a long BSR or a short BSR according to the number of LCGs includes: determining the BSR format as a long BSR under the condition that the number of LCGs is greater than 1; in case the number of LCGs is equal to 1, the BSR format is determined to be a short BSR.

In case a long BSR is selected or generated, step 310 is performed.

Step 308: if no non-padding BSR exists, performing other packaging;

for example, the padding BSR is packed, or other uplink control information related packages, or other uplink data related packages are packed.

Step 310: whether the byte number of the uplink authorization is larger than or equal to the byte number of the long BSR or not;

and under the condition that the BSR format is determined to be the long BSR format, the terminal also judges whether the byte number of the uplink authorization is larger than or equal to the byte number of the long BSR. I.e. whether the uplink resources scheduled by the uplink grant are sufficient to accommodate the number of bytes of the long BSR.

It should be noted that step 310 may be performed before the generation of the long BSR, or may be performed after the generation of the long BSR, which is not limited in this embodiment.

If the number of bytes of the uplink grant is smaller than the number of bytes of the long BSR, go to step 312; in case the number of bytes of the uplink grant is greater than or equal to the number of bytes of the long BSR, step 314 is performed.

Step 312: sending a short BSR;

and sending the short BSR under the condition that the byte number of the uplink authorization is smaller than that of the long BSR. That is, in this embodiment, the BSR format of the second BSR is a short BSR.

The short BSR is data of fixed length format according to the specifications of the communication protocol TS38.321 of 3 GPP. As shown in fig. 5, the format of the short BSR includes: a MAC packet header field and a content field. Wherein, the MAC packet header field is 1 byte and carries an LCG ID, for example, the LCG ID is 61; the content field is 1 byte and carries the Buffer Size (Buffer Size) of the LCG.

In some embodiments, the MAC PDU is sent in the event that the number of bytes in the uplink grant is less than the number of bytes of the first BSR. The MAC PDU includes a short BSR.

In case that the number of bytes of the MAC PDU is greater than that of the short BSR, the MAC PDU may include any one of the following combinations:

short BSR and MAC CEs other than short BSR;

in case the number of bytes of the MAC PDU is larger than the short BSR, the remaining number of bytes or bits is used to carry other MAC CEs besides the short BSR.

Short BSR and valid data;

and under the condition that the byte number of the MAC PDU is larger than the short BSR, the residual byte number or bit is used for carrying effective data. The valid data is also the uplink data in the valid state.

Short BSR, MAC CE and valid data.

In case that the number of bytes of the MAC PDU is greater than the short BSR, the remaining number of bytes or bits is used to carry other MAC CEs and valid data except the short BSR.

In some embodiments, the short BSR includes any one of the following information:

an LCG ID of the first LCG and a first buffer amount of the first LCG, the first LCG being an LCG selected based on priority level;

illustratively, the first LCG is an LCG with the highest priority of the LCGs in the plurality of LCGs to be transmitted, or the first LCG is an LCG in Top n ordered according to the priority of the LCGs from high to low in the plurality of LCGs to be transmitted. Wherein n is a positive integer.

Illustratively, the BSR is transmitted in units of LCGs rather than Logical Channels (LCHs), although the same LCG may contain only one LCH. Typically, logical channels with the same (or similar) priority are linked to the same LCG. For example: the LCH used for signaling may be linked to a first LCG, while the LCH carrying voice data may be linked to a second LCG, and the LCH carrying web-browsing data may be linked to a third LCG. In some examples, the same UE may configure up to 8 LCGs. The base station links the LCH to the LCG using the field "locatalchannelgroup IE" in the MAC layer signaling "MAC-LogicalChannelConfig".

Wherein the first buffer amount of the first LCG is equal to: the sum of the buffer sizes of all LCHs belonging to the first LCG.

The LCG ID of the second LCG and a second buffer amount of the second LCG, the second LCG being an LCG selected based on how much the buffer amount of the LCG is.

Illustratively, the second LCG is the LCG with the highest buffer amount among the plurality of LCGs to be transmitted, or the second LCG is the LCGs with the buffer amounts sorted at Top n from most to least among the plurality of LCGs to be transmitted. Wherein n is a positive integer.

In the case of one LCH included in one LCG, the amount of buffering of the LCG is equal to the buffer size of the LCH; in the case where two or more LCHs are included in one LCG, the buffer size of the LCG is equal to the sum of the buffer sizes of the two or more LCHs.

In the process of generating the short BSR, the terminal needs to fill in the LCG ID and the buffer size, and the terminal should select from all the LCGs according to a scheduling policy, and there are two main principles:

(1) the method comprises the steps of selecting a first LCG where one or more LCHs with high priorities are located, reporting a first buffer storage amount of the first LCG, wherein the strategy is suitable for a scene that uplink authorization is insufficient due to multi-terminal competition in a network, and when a base station senses that the LCH with the highest priority needs the uplink authorization, preferentially distributing the uplink authorization to the terminal.

(2) And selecting a second LCG where one or more LCHs with the largest buffer amount are located, and reporting the second buffer amount of the second LCG, wherein the strategy is suitable for a non-tight competition network, and the terminal can acquire the maximum uplink authorization allocated by the base station through the maximum buffer amount and quickly send uplink data.

In this specification, "buffer amount" and "buffer size" are to be regarded as the same meaning. But those skilled in the art are conventionally referred to as the buffer size of the LCG, the buffer size of the LCH. In some documents, the buffer amount may also be referred to as buffer amount, buffer status, and other terms.

Step 314: reserving the byte number of the long BSR and performing other groups.

And reserving the byte number of the long BSR in the uplink transmission resource and performing other group packing under the condition that the byte number of the uplink authorization is greater than or equal to the byte number of the long BSR.

In summary, in the method provided in this embodiment, when the number of bytes of the uplink grant is smaller than the number of bytes of the long BSR, the short BSR with a smaller number of bytes is reselected or generated and then transmitted, so that the UE can be ensured to transmit the BSR to the base station in time without using a lengthy SR procedure to re-apply for the uplink grant, the uplink transmission efficiency of the BSR is improved, and the uplink transmission delay of the BSR is shortened.

Meanwhile, the mechanism for transmitting the long BSR into the short BSR only needs to be improved on the terminal side, the network side and a communication protocol do not need to be modified correspondingly, modification on the network side is not involved, and compatibility and application range of the technical scheme of the application are improved.

For embodiments where the first BSR is a long BSR and the second BSR is a pruned BSR (carrying partial LCG):

fig. 6 shows a flowchart of a BSR transmission method according to an exemplary embodiment of the present application. The present embodiment is exemplified by the method applied to the terminal 10. The method comprises the following steps:

step 402: receiving an uplink grant;

Illustratively, the uplink transmission resource is a PUSCH resource.

Step 404: whether there is a non-padding type BSR;

1) The uplink data buffer of the UE is empty and new data arrives.

When all logical channels of all LCGs have no uplink data to transmit, if any logical channel belonging to any LCG becomes available to transmit at this time, the UE may trigger a regular BSR.

2) High priority data arrives.

The triggering conditions for the periodic BSR are: the BSR period timer times out.

If there is a BSR of non-padding type, go to step 406; if there is no non-padding type BSR, go to step 408;

step 406: if the non-filling type BSR exists, determining that the BSR format is a long BSR or a short BSR according to the number of the logical channel groups;

in some embodiments, the BSR format includes: short BSR and long BSR. Illustratively, LCID 61 is used for short BSR and LCID 62 is used for long BSR.

In case a long BSR is selected or generated, step 410 is performed.

Step 408: if no non-padding BSR exists, performing other packaging;

Step 410: whether the byte number of the uplink authorization is larger than or equal to the byte number of the long BSR or not;

When the number of bytes of the uplink grant is smaller than the number of bytes of the long BSR, execute step 412; in case the number of bytes of the uplink grant is greater than or equal to the number of bytes of the long BSR, step 414 is performed.

Step 412: (forced) sending a pruned BSR;

and forcibly sending the reduced BSR under the condition that the byte number of the uplink authorization is smaller than that of the long BSR. That is, in the present embodiment, the second BSR includes a pruned BSR.

In some embodiments, the BSR format further comprises: short and long paredown BSR. Wherein, the length of the short reduction BSR is at least 2 bytes, and the format is the same as that of the short BSR; the length of the long pruned BSR is at least 4 bytes, which must be less than or equal to the number of bytes of the uplink grant. Under the condition that the byte number of the uplink authorization is smaller than that of the long BSR, the terminal selects LCG with the priority rank in the first n bits, carries out bit filling of the reduced BSR, and reports the buffer area states of several LCG to the base station as much as possible.

Optionally, the pruned BSR comprises: an LCG ID and a first buffer amount of a first LCG, the first LCG being an LCG selected based on a priority level of the LCG. Illustratively, the first LCG is an LCG with the highest priority of the LCGs in the plurality of LCGs to be transmitted, or the first LCG is an LCG in Top n ordered according to the priority of the LCGs from high to low in the plurality of LCGs to be transmitted. Wherein n is a positive integer. The value of n is related to the length of information that can be accommodated by the number of bytes of the uplink grant.

Illustratively, the BSR is transmitted in LCG units rather than in LCH units, although the same LCG may contain only one LCH. Typically, logical channels with the same (or similar) priority are linked to the same LCG. For example: the LCH used for signaling may be linked to a first LCG, while the LCH carrying voice data may be linked to a second LCG, and the LCH carrying web-browsing data may be linked to a third LCG. In some examples, the same UE may configure up to 8 LCGs. The base station links the LCH to the LCG using the field "locatalchannelgroup IE" in the MAC layer signaling "MAC-LogicalChannelConfig".

Optionally, the pruned BSR comprises: an LCG ID of the second LCG and a second buffer amount of the second LCG, the second LCG being an LCG selected based on how much the buffer amount of the LCG is.

In the case of including an LCH within an LCG, the amount of buffering of the LCG is equal to the amount of buffering of the LCH; in the case where two or more LCHs are included in one LCG, the buffer amount of the LCG is equal to the sum of the buffer amounts of the two or more LCHs.

In some embodiments, the second BSR is carried in a MAC PDU, the MAC PDU comprising at least one of the following combinations:

pare down BSR and MAC CE except short BSR;

cut BSR and valid data;

prune BSR, MAC CE and payload data.

In some embodiments, the LCP priority of the BSR is lower than that of the normal packet, and the normal process flow is to send the normal packet first and send the BSR only when there is an idle location in the uplink transmission resource, so forced sending is required to send the BSR to the base station preferentially. That is, in the case of forced transmission, the transmission priority of the BSR is higher than that of the normal packet.

Step 414: reserving the byte number of the long BSR and performing other groups.

In summary, in the method provided in this embodiment, when the number of bytes of the uplink grant is smaller than the number of bytes of the long BSR, the reduced BSR with a smaller number of bytes is reselected or generated and then transmitted, so that the UE can be ensured to transmit the BSR to the base station in time without using a lengthy SR procedure to re-apply for the uplink grant, the uplink transmission efficiency of the non-padding BSR is improved, and the uplink transmission delay of the non-padding BSR is shortened.

Meanwhile, the mechanism for transmitting the long BSR by changing the reduced BSR only needs to be improved on the terminal side, the network side and the communication protocol do not need to be modified correspondingly, and the modification of the network side is not involved, so that the compatibility and the application range of the technical scheme of the application are improved.

For embodiments where the first BSR is a long BSR, the second BSR is a short BSR or a pruned BSR (carrying the compressed full LCGs):

fig. 7 shows a flowchart of a BSR transmission method according to an exemplary embodiment of the present application. The present embodiment is exemplified by the method applied to the terminal 10. The method comprises the following steps:

step 502: receiving an uplink grant;

Illustratively, the uplink transmission resource is a PUSCH resource.

Step 504: whether there is a non-padding type BSR;

1) The uplink data buffer of the UE is empty and new data arrives.

2) High priority data arrives.

If there is a BSR of non-padding type, go to step 506; if there is no non-padding type BSR, go to step 508;

step 506: if the non-filling type BSR exists, determining that the BSR format is a long BSR or a short BSR according to the number of the logical channel groups;

In case a long BSR is selected or generated, step 410 is performed.

Step 508: if no non-padding BSR exists, performing other packaging;

Step 510: whether the byte number of the uplink authorization is larger than or equal to the byte number of the long BSR or not;

Executing step 512 under the condition that the byte number of the uplink authorization is smaller than the byte number of the long BSR; in case the number of bytes of the uplink grant is greater than or equal to the number of bytes of the long BSR, step 516 is performed.

Step 512: compressing or combining the buffer storage of LCG in the long BSR to generate a short BSR or a reduced BSR;

ways to compress or merge the buffer amount of LCGs in the long BSR include, but are not limited to, at least one of the following:

1. the buffer amounts of all LCGs in the long BSR are merged into the buffer amount of the (one) third LCG.

The LCG ID of the third LCG is the LCG ID of the LCG with the highest priority in all the LCGs; or the LCG ID of the third LCG is the LCG ID of the LCG with the lowest priority in all the LCGs; or the LCG ID of the third LCG is an additional LCG ID, such as an LCG₉. The priority of the newly added LCG is the highest priority, the lowest priority or the average priority of all LCGs.

Wherein the third buffer size of the third LCG is equal to the sum of the buffer sizes of all LCGs in the long BSR.

Then, a short BSR is generated based on the LCG ID of the third LCG and the third buffer amount.

2. The buffer amounts of the other LCGs except the first LCG of the highest priority in the long BSR are merged into the buffer amount of the third LCG.

It is assumed that at least three LCGs are included in the long BSR, and the first LCG is the highest priority LCG of the at least two LCGs.

The LCG ID of the third LCG is the LCG ID of the LCG with the highest priority in all the LCGs; or the LCG ID of the third LCG is the LCG ID of the LCG with the lowest priority in all the LCGs; or, LCG ID of third LCG is additional LCG ID, e.g. LCG₉. The priority of the newly added LCG is the highest priority, the lowest priority or the average priority among the other LCGs except the first LCG.

Wherein the third buffer amount of the third LCG is equal to the sum of the buffer amounts of the LCGs other than the first LCG in the long BSR.

Then, a pruned BSR is generated based on the LCG ID and the first buffer amount of the first LCG and the LCG ID and the third buffer amount of the third LCG. The pruned BSR carries a buffer of 2 LCGs.

3. Merging the buffer quantities of other LCGs except the first k LCGs with the priorities from high to low in the long BSR into the buffer quantity of a third LCG, wherein k +3 is less than or equal to the byte number n of the uplink authorization_UL。

Assuming that the long BSR includes at least three LCGs, the number of bytes n of the uplink grant_ULThe maximum number of LCGs that can be accommodated is n_UL-3。

The LCG ID of the third LCG is the LCG ID of the (k + 1) th LCG with the priority from high to low in all LCGs; or the LCG ID of the third LCG is the LCG ID of the LCG with the lowest priority in all the LCGs; or, the LCG ID of the third LCG is the additional LCG ID. The priority of the newly added LCG is the highest priority, the lowest priority or the average priority of other LCGs except the first k LCGs with the priorities from high to low. Wherein k is a positive integer.

Wherein the third buffer amount of the third LCG is equal to the sum of the buffer amounts of the LCGs except the first k LCGs with the priorities from high to low in the long BSR.

Then, a pare BSR is generated based on LCG IDs and buffer amounts of the first k LCGs whose priorities are from high to low, and an LCG ID and a third buffer amount of a third LCG.

4. And merging the buffer amounts of the at least two LCGs with the same priority into the buffer amount of the third LCG.

Step 514: sending a short BSR or (forced) a pruned BSR;

and sending the short BSR or forcibly sending the reduced BSR under the condition that the byte number of the uplink authorization is smaller than that of the long BSR.

Step 516: reserving the byte number of the long BSR and performing other groups.

In summary, the method provided in this embodiment compresses or merges the buffer amounts of all the LCGs in the long BSR, so that the short BSR or the reduced BSR can still carry the buffer amounts of all the LCGs, which is convenient for the network side to schedule the corresponding uplink transmission resource to the terminal in time, and ensures that the uplink signaling or the uplink data of all the LCGs can be sent in time.

However, it should be noted that the above-mentioned merging schemes are performed on the premise of meeting the communication protocol or terminal performance requirements or terminal testing requirements or local regulatory requirements.

Fig. 8 is a block diagram of a BSR transmitting apparatus according to an exemplary embodiment of the present application, where the apparatus includes:

a sending module 720, configured to send a second BSR when the number of bytes of the uplink grant is smaller than the number of bytes of the first BSR;

In some embodiments of the present application, the type of the first BSR and the second BSR is a regular BSR or a periodic BSR.

In some embodiments of the present application, the sending module 720 is configured to send a short BSR when a byte number of an uplink grant is smaller than a byte number of the first BSR;

wherein, the short BSR is data with a fixed length format, such as 2 bytes. That is, the BSR format of the second BSR is a short BSR.

In some embodiments of the present application, the sending module 720 is configured to (forcibly) send the pruned BSR if the number of bytes of the uplink grant is smaller than the number of bytes of the first BSR. That is, the BSR format of the second BSR is a pruned BSR.

In some embodiments of the present application, the sending module 720 is configured to send the MAC PDU when the number of bytes of the uplink grant is less than the number of bytes of the first BSR. That is, the second BSR is carried in a MAC PDU.

In some embodiments of the present application, the MAC PDU includes at least one of the following combinations:

the second BSR and a MAC CE other than the second BSR;

the second BSR and valid data;

the second BSR, the MAC CE, and the valid data.

In some embodiments of the present application, the second BSR is based on the first BSR.

In some embodiments of the present application, the second BSR carries a buffer amount of all or a part of the LCGs in the first BSR.

In some embodiments of the present application, the second BSR carries: an LCG ID of a first LCG and a first amount of caching for the first LCG, the first LCG being an LCG selected based on a priority level of the LCG; or an LCG ID of a second LCG and a second buffering amount of the second LCG, the second LCG being an LCG selected based on how much buffering amount of the LCG is.

In some embodiments of the present application, in the case of the forced transmission, the transmission priority of the pruned BSR is higher than the transmission priority of the normal packet.

In some embodiments, the second BSR carries a buffer amount of all LCGs in the first BSR, and the buffer amount of all LCGs is merged or compressed.

In some embodiments, the merging or compressing of the buffer amounts of all LCGs comprises at least one of:

The LCG ID of the third LCG is the LCG ID of the LCG with the highest priority in all the LCGs; or the LCG ID of the third LCG is the LCG ID of the LCG with the lowest priority in all the LCGs; or the LCG ID of the third LCG is an additional LCG ID, such as an LCG₉. The priority of the newly added LCG is the highest priority, the lowest priority or the average priority among the other LCGs except the first LCG.

3. Prioritizing the first k high to low in long BSRThe buffer quantities of other LCGs except the LCG are combined into the buffer quantity of the third LCG, and k +3 is less than or equal to the byte number n of the uplink authorization_UL。

Alternatively, the merging method or the compressing method may be performed by a generating module or a merging module or a compressing module (not shown in the figure) in the apparatus.

It should be noted that, when the apparatus provided in the foregoing embodiment implements the functions thereof, only the division of the above functional modules is illustrated, and in practical applications, the above functions may be distributed by different functional modules according to actual needs, that is, the content structure of the device is divided into different functional modules, so as to complete all or part of the functions described above.

With regard to the apparatus in the above-described embodiment, the specific manner in which each module performs the operation has been described in detail in the embodiment related to the method, and will not be elaborated here.

Fig. 9 is a schematic structural diagram of a terminal provided in an exemplary embodiment of the present application, where the terminal is connected to the BSR sending device, and the terminal 80 includes: a processor 801, a receiver 802, a transmitter 803, a memory 804 and a bus 805.

The processor 801 includes one or more processing cores, and the processor 801 executes various functional applications and information processing by running software programs and modules.

The receiver 802 and the transmitter 803 may be implemented as one communication component, which may be a piece of communication chip.

The memory 804 is coupled to the processor 801 by a bus 805.

The memory 804 may be used to store at least one instruction for execution by the processor 801 to implement the various steps in the method embodiments described above.

Further, the memory 804 may be implemented by any type or combination of volatile or non-volatile storage devices, including, but not limited to: magnetic or optical disks, Electrically Erasable Programmable Read Only Memories (EEPROMs), Erasable Programmable Read Only Memories (EPROMs), Static Random Access Memories (SRAMs), Read-Only memories (ROMs), magnetic memories, flash memories, Programmable Read Only Memories (PROMs).

The processor and the transceiver in the terminal according to the embodiment of the present application may perform each step in the method shown in any method embodiment described above, and are not described herein again.

In an exemplary embodiment, a computer-readable storage medium is further provided, where at least one instruction, at least one program, a code set, or a set of instructions is stored in the computer-readable storage medium, and the at least one instruction, the at least one program, the code set, or the set of instructions is loaded and executed by the processor to implement the BSR transmission method provided by the above-mentioned various method embodiments.

In an exemplary embodiment, a chip is further provided, where the chip includes a programmable logic circuit and/or a program instruction, and when the chip runs on a communication device, the chip is configured to implement the BSR sending method provided in the foregoing method embodiments.

In an exemplary embodiment, a computer program product is also provided, which, when running on a processor of a terminal, causes the terminal to perform the BSR transmitting method described above.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in the embodiments of the present application may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Computer-readable media includes both computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another. A storage media may be any available media that can be accessed by a general purpose or special purpose computer.

The above description is only exemplary of the present application and should not be taken as limiting the present application, and any modifications, equivalents, improvements and the like that are made within the spirit and principle of the present application should be included in the protection scope of the present application.

Claims

1. A method for sending a Buffer Status Report (BSR), the method comprising:

2. The method of claim 1, wherein the BSR format of the second BSR is a short BSR.

3. The method of claim 1, wherein the BSR format of the second BSR is a pruned BSR.

4. The method of claim 3, wherein the transmission priority of the pruned BSR is higher than the transmission priority of normal packets.

5. The method according to any of claims 1 to 4, wherein the second BSR is carried in a Medium Access protocol data Unit, MAC, PDU, the MAC PDU comprising at least one of the following combinations:

the second BSR and a media access control element (MAC CE) other than the second BSR;

the second BSR and valid data;

the second BSR, the MAC CE, and the valid data.

6. The method of any of claims 1 to 4, wherein the second BSR includes:

a logical channel group of a first LCG identifies an LCGID and a first buffer amount of the first LCG, the first LCG being selected based on a priority level of the LCG;

or the like, or, alternatively,

an LCG ID of a second LCG and a second amount of buffering for the second LCG, the second LCG being an LCG selected based on how much the amount of buffering for the LCG is.

7. The method of any of claims 1 to 4, wherein the second BSR is based on the first BSR.

8. The method of any of claims 1 to 4, wherein the second BSR carries a buffer amount of all or a part of the LCGs in the first BSR.

9. The method according to any of claims 1 to 4, wherein the type of the second BSR is a regular BSR or a periodic BSR.

10. The method of any of claims 1 to 4, wherein the BSR format of the first BSR is a long BSR.

11. An apparatus for Buffer Status Report (BSR) transmission, the apparatus comprising:

the sending module is used for sending the second BSR under the condition that the byte number of the uplink authorization is smaller than that of the first BSR;

12. The apparatus of claim 11, wherein the BSR format of the second BSR is a short BSR.

13. The apparatus of claim 11, wherein the BSR format of the second BSR is a pruned BSR.

14. The apparatus of claim 13, wherein the transmission priority of the pruned BSR is higher than a transmission priority of normal packets.

15. The apparatus according to any of claims 11 to 14, wherein the second BSR is carried in a medium access protocol data unit, MAC PDU, comprising at least one of the following combinations:

the second BSR and valid data;

the second BSR, the MAC CE, and the valid data.

16. The apparatus of any of claims 11 to 14, wherein the second BSR comprises:

or the like, or, alternatively,

17. The apparatus of any of claims 11 to 14, wherein the second BSR is based on the first BSR.

18. The apparatus of any of claims 11 to 14, wherein the second BSR carries a buffer amount of all or a part of the LCGs in the first BSR.

19. The apparatus according to any one of claims 11 to 14, wherein the type of the second BSR is a regular BSR or a periodic BSR.

20. The apparatus of any of claims 11 to 14, wherein the BSR format of the second BSR is a long BSR.

21. A terminal, characterized in that the terminal comprises:

a processor;

a transceiver coupled to the processor;

a memory for storing executable instructions of the processor;

wherein the processor is configured to load and execute the executable instructions to implement the BSR transmission method according to any one of claims 1 to 10.

22. A computer-readable storage medium having stored therein executable instructions loaded and executed by a processor to implement the BSR transmitting method according to any one of claims 1 to 10.

23. A chip characterized in that it comprises a programmable logic circuit or a program, said chip being configured to implement the BSR transmission method according to any one of claims 1 to 10.

24. A computer program product, characterized in that the computer program product comprises computer instructions stored in a computer-readable storage medium, which are read from by a processor of a terminal, the processor executing the computer instructions, causing the terminal to perform the BSR transmitting method according to any one of claims 1 to 10.