WO2023216986A1 - Buffer status report (bsr) indication method, and apparatus - Google Patents

Abstract

Provided in the embodiments of the present application are a buffer status report (BSR) indication method, and an apparatus. The method comprises: a terminal device receives a first message from a first device, and sends a BSR media access control (MAC) control element (CE) to the first device according to the first message, the first message being used for instructing the terminal device to trigger a BSR, and the BSR being used for indicating a buffer status of a logical channel group (LCG) of the terminal device. In the method disclosed in the present application, by receiving a BSR trigger instruction sent by the first device, timely BSR reporting by the terminal device can be ensured while transmitting data, so that the first device can perform reasonable transmission resource allocation for the terminal device, reducing resource waste and reducing transmission delay.

Description

Cache status report BSR indication method and device

This application requires the priority of the Chinese patent application submitted to the China Patent Office on May 12, 2022, with the application number 202210516327.9 and the application name "A BSR indication method, network equipment, and terminal equipment", and requires that it be filed in June 2022 The priority of the Chinese patent application submitted to the China Patent Office on March 25th with application number 202210727520.7 and the application title is "Cache Status Report BSR Instruction Method and Device", the entire content of which is incorporated into this application by reference.

Technical field

The present application relates to the field of communication technology, and in particular to a buffer status report (BSR) indication method and device.

Background technique

With the continuous development of communication systems, data transmission latency continues to decrease, and transmission capacity becomes larger and larger. The fifth generation (5th generation, 5G) communication system gradually emerges some multimedia services with strong real-time performance, such as video transmission, cloud Games, extended reality (XR), tactile Internet, etc. In order to achieve an immersive experience of interaction between people and the virtual world, the XR video service, which has ultra-high bandwidth and ultra-low latency requirements, has attracted much attention.

For example, taking the terminal device sending XR video data to the network device as an example, after the terminal device establishes a connection with the network device, the terminal device needs to send a buffer status report (BSR) to the network device to notify the network device. The amount of uplink buffered data to be transmitted on the current logical channel (logical channel, LCH) or logical channel group (LCG), so that the network device can schedule appropriate uplink transmission resources for the terminal device.

However, the current BSR triggering mechanism cannot well support timely reporting of BSR for XR video services, resulting in a waste of resources or additional transmission delays.

Contents of the invention

This application provides a cache status report BSR indication method and device, which can ensure that the terminal equipment reports the BSR in a timely manner while sending uplink data, so as to enable the network equipment to perform reasonable uplink resource allocation, thereby reducing resource waste and reducing transmission costs. time delay.

The first aspect provides a cache status report BSR indication method. The method can be executed by a terminal device (for example, user equipment, UE), or it can also be executed by a chip or circuit used for the terminal device. This application does not limit this. For the convenience of description, the following takes execution by the terminal device as an example. Be explained.

The method includes: the terminal device receives a first message from the first device, the first message is used to instruct the terminal device to trigger a BSR, and the BSR is used to indicate the cache status of the LCG of the terminal device; the terminal device sends a message to the first device according to the first message. BSR media access control (media access control, MAC) control unit (control element, CE).

In this way, by receiving the BSR trigger indication sent by the first device, it can be ensured that the terminal device reports the BSR in time while transmitting data, thereby enabling the first device to allocate reasonable transmission resources to the terminal device, so as to reduce resource waste and transmission delay. .

With reference to the first aspect, in some implementations of the first aspect, the terminal device receives a second message from the first device, the second message is used to indicate the transmission resources allocated by the first device to the terminal device, and the transmission resources are used to carry BSR MAC CE.

Combined with the first aspect, in some implementations of the first aspect, the transmission resources include physical uplink shared channel (PUSCH) resources or physical sidelink shared channel (PSSCH) resources.

Combined with the first aspect, in some implementations of the first aspect, the second message is carried in control information, and the control information includes downlink control information (DCI) or sidelink control information (SCI). ).

In conjunction with the first aspect, in some implementations of the first aspect, the control information is also used to carry the first message.

Combined with the first aspect, in some implementations of the first aspect, the first message is carried in the MAC CE.

Combined with the first aspect, in some implementations of the first aspect, the MAC subheader (subheader) of the MAC CE includes a logical channel identifier (LCID). Wherein, the terminal device sends the BSR MAC CE to the first device according to the first message, including: when the value of the LCID is a preset value, the terminal device sends the BSR MAC CE to the first device according to the first message.

In conjunction with the first aspect, in some implementations of the first aspect, the first message is also used to indicate at least one logical channel group identification LCG ID.

In connection with the first aspect, in some implementations of the first aspect, the terminal device receives first configuration information from the first device, and the first configuration information is used to configure at least one logical channel group identifier LCG ID.

Combined with the first aspect, in some implementations of the first aspect, the BSR MAC CE includes the cache status of the LCG corresponding to at least one LCG ID.

Based on the above solution, the first device can directly or indirectly indicate one or more LCG IDs to the terminal device through indication information (first message); or, the first device can also semi-statically configure the terminal device (first configuration information) One or more LCG IDs. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

Combined with the first aspect, in some implementations of the first aspect, the terminal device sends the BSR MAC CE to the first device according to the first message, including: the terminal device sends the BSR MAC to the first device when the first condition is met. CE.

Among them, the first condition is that the transmission resources are used for initial transmission; the transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and the BSR MAC CE is triggered by the first message.

Based on the above solution, the first condition is defined to explain that the reporting method is triggered by the MAC CE in the BSR.

In conjunction with the first aspect, in some implementations of the first aspect, the first message is also used to indicate a first duration, and the first duration is used to indicate a time offset of the first moment relative to the second moment, and the first moment The second moment is the moment when the terminal device triggers the BSR, and the second moment is the moment when the terminal device receives the first message.

Based on the above solution, by indicating the first duration (that is, the difference between the time when the terminal device receives the first message and the time when the terminal device triggers the BSR), the effect of triggering the BSR on a timed basis is achieved. For example, after the terminal device receives the MAC CE at time t0, the decoding is successful and the BSR report is triggered. At this time, the first duration may be zero. However, considering that the terminal device may fail to decode the MAC CE when it receives it during the initial transmission, the terminal device needs to request the first device to schedule a retransmission, which will lead to the terminal device correctly decoding the time and initial transmission schedule of the MAC CE. The time is inconsistent. Pass first The duration can ensure that when the terminal device triggers BSR, it enables the first device to obtain the BSR MAC CE in a timely and effective manner and allocate transmission resources to the terminal device.

Combined with the first aspect, in some implementations of the first aspect, when the terminal device triggers BSR, padding BSR, regular BSR and/or periodic BSR at the same time, the terminal device generates the BSR MAC CE according to the regular BSR and/or periodic BSR; Or, when the terminal device triggers the BSR and fills the BSR at the same time, the terminal device generates the BSR MAC CE based on the BSR.

It should be understood that a MAC protocol data unit SDU should contain at most one BSR MAC CE, even if multiple events trigger BSR reporting.

Based on the above solution, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of this application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

In the second aspect, a cache status report BSR indication method is provided. The method can be executed by a first device (for example, a base station or a UE), or can also be executed by a chip or circuit for the first device. This application provides This is not a limitation. For convenience of description, the following description takes execution by the first device as an example. The method includes: the first device sends a first message to the terminal device, the first message is used to instruct the terminal device to trigger BSR, and the BSR is used to indicate the cache status of the logical channel group LCG of the terminal device; the first device receives the BSR from the terminal device Mac CE.

It should be understood that this application is applicable to cellular uplink transmission scenarios and is also applicable to sidelink (SL) scenarios. In the SL scenario, UE1 and UE2 communicate through the SL PC5 interface, and UE1 communicates with the base station through the Uu interface. The PC5 communication requires resource allocation by the base station. At this time, in order to communicate with UE2, UE1 needs to report UE1's BSR to the base station. The BSR is used to indicate how much data UE1 needs to send to UE2 to enable the base station to schedule PC5 resources for UE1. When there is communication between UEs without the participation of a base station, UE1 in this implementation can be understood as the base station role mentioned above, and UE2 can be understood as the UE role in the above method.

In this way, by sending the BSR trigger indication to the terminal device, it can be ensured that the terminal device reports BSR in time while transmitting data, thereby enabling the first device to allocate reasonable transmission resources to the terminal device, thereby reducing resource waste and transmission delay.

Combined with the second aspect, in some implementations of the second aspect, the first device sends a second message to the terminal device, the second message is used to indicate the transmission resources allocated by the first device to the terminal device, and the transmission resources are used to carry the BSR Mac CE.

Combined with the second aspect, in some implementations of the second aspect, the transmission resources include PUSCH resources or PSSCH resources.

Combined with the second aspect, in some implementations of the second aspect, the second message is carried in a control message, and the control information includes DCI or SCI.

Combined with the second aspect, in some implementations of the second aspect, the control information is also used to carry the first message.

Combined with the second aspect, in some implementations of the second aspect, the first message is carried in the MAC CE.

Combined with the second aspect, in some implementations of the second aspect, the MAC sub-header of the MAC CE includes LCID; wherein, the first device receives the BSR MAC CE from the terminal device, including: when the value of LCID is a preset value When, the first device receives the BSR MAC CE from the terminal device.

Combined with the second aspect, in some implementations of the second aspect, the first message is also used to indicate at least one LCG ID.

Combined with the second aspect, in some implementations of the second aspect, the first device sends first configuration information to the terminal device, and the first configuration information is used to configure at least one LCG ID.

Combined with the second aspect, in some implementations of the second aspect, the BSR MAC CE includes at least one LCG ID The cache status of the corresponding LCG.

Based on the above solution, the first device can directly or indirectly indicate one or more LCG IDs to the terminal device through indication information (first message); or, the first device can also semi-statically configure the terminal device (first configuration information) One or more LCG IDs. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

Combined with the second aspect, in some implementations of the second aspect, the first device receives the BSR MAC CE from the terminal device, including: when the first condition is met, the first device receives the BSR MAC CE from the terminal device. .

Among them, the first condition is that the transmission resources are used for initial transmission; the transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and the BSR MAC CE is triggered by the first message.

Based on the above solution, the first condition is defined to explain that the reporting method is triggered by the MAC CE in the BSR.

Combined with the second aspect, in some implementations of the second aspect, the first message is also used to indicate a first duration, and the first duration is used to indicate a time offset of the first moment relative to the second moment, and the first moment The second moment is the moment when the terminal device triggers the BSR MAC CE, and the second moment is the moment when the terminal device receives the first message.

Based on the above solution, by indicating the first duration (that is, the difference between the time when the terminal device receives the first message and the time when the terminal device triggers the BSR), the effect of triggering the BSR on a timed basis is achieved. For example, after the terminal device receives the MAC CE at time t0, the decoding is successful and the BSR report is triggered. At this time, the first duration can be zero. However, considering that the terminal device may fail to decode the MAC CE when it receives it during the initial transmission, the terminal device needs to request the first device to schedule a retransmission, which will lead to the terminal device correctly decoding the time and initial transmission schedule of the MAC CE. The time is inconsistent. The first duration can ensure that when the terminal device triggers BSR, the first device is enabled to obtain the BSR MAC CE in a timely and effective manner and allocate transmission resources to the terminal device.

Combined with the second aspect, in some implementations of the second aspect, when the terminal device simultaneously triggers BSR, padding BSR, regular BSR and/or periodic BSR, the terminal device generates the BSR MAC CE according to the regular BSR and/or periodic BSR; or , when the terminal device triggers BSR and fills BSR at the same time, the terminal device generates BSR MAC CE based on BSR.

Based on the above solution, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of this application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

In the third aspect, a cache status report BSR triggering method is provided. The method may be executed by a terminal device (such as a UE), or may be executed by a chip or circuit used in the terminal device, which is not limited in this application. For convenience of description, the following description takes execution by a terminal device as an example.

The method includes: the terminal device receives second configuration information from the first device, the second configuration information is used to configure the first timer and first signaling, and the first signaling is used to instruct the terminal device to trigger the BSR; when the second If the condition is met, the terminal device starts or restarts the first timer, and the terminal device sends the BSR MAC CE to the first device.

Among them, the second condition is that the transmission resources are used for initial transmission, and the transmission resources are the transmission resources allocated by the first device to the terminal device; the transmission resources can accommodate the BSR MAC CE reported by the terminal device and the MAC sub-header corresponding to the BSR MAC CE; and The first signaling is a first value (for example, the first value indicates disable).

For example, the first signaling is periodicBSRrefresh-r18 signaling, which contains two values. For example, when periodicBSRrefresh-r18=disable, the first timer (for example, periodicBSR-Timer) will not be started or restarted due to the reporting of BSR MAC CE (for example, other reasons cause the terminal device to trigger BSR reporting); when periodicBSRrefresh-r18 =enable, the first timer is started or restarted according to the traditional triggering method.

According to the solution provided by this application, the BSR triggering method is configured through radio resource control (RRC) semi-static signaling, and the BSR triggering condition is modified (that is, the terminal device starts or restarts the first timer when the first timer times out. timer, and will not start or restart the first timer due to the BSR MAC CE report), ensuring the stability of the BSR triggering cycle.

Combined with the third aspect, in some implementations of the third aspect, the second configuration information also includes second signaling, the second signaling is used to indicate at least one LCG ID, and the BSR MAC CE includes at least one LCG ID corresponding to LCG cache status.

Based on the above solution, the first device indicates one or more LCG IDs to the terminal device through the second signaling. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

Combined with the third aspect, in some implementations of the third aspect, when the terminal device triggers BSR, padding BSR, regular BSR and/or periodic BSR at the same time, the terminal device generates a BSR MAC CE according to the regular BSR and/or periodic BSR; Or, when the terminal device triggers the BSR and fills the BSR at the same time, the terminal device generates the BSR MAC CE based on the BSR.

Based on the above solution, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of this application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

The fourth aspect provides a buffer status report BSR triggering method, which can be executed by a first device (for example, a base station or a UE), or can also be executed by a chip or circuit for the first device. This application provides This is not a limitation. For convenience of description, the following description takes execution by the first device as an example.

The method includes: a first device sends second configuration information to a terminal device, the second configuration information is used to configure a first timer and first signaling, and the first signaling is used to instruct the terminal device to trigger BSR; when the second condition is met In this case, the first device receives the BSR MAC CE from the terminal device, and the first timer is in a starting or restarting state.

Among them, the second condition is that the transmission resources are used for initial transmission, and the transmission resources are the transmission resources allocated by the first device to the terminal device; the transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and the first signaling is the first value.

According to the solution provided by this application, the BSR triggering method is configured through semi-static signaling (i.e., the first signaling), and the triggering condition of the BSR is modified (i.e., the terminal device starts or restarts the first timer when the first timer times out, The first timer will not be started or restarted due to the reporting of BSR MAC CE) to ensure the stability of the BSR triggering cycle.

Combined with the fourth aspect, in some implementations of the fourth aspect, the second configuration information also includes second signaling, the second signaling is used to indicate at least one logical channel group identifier LCG ID, and the BSR MAC CE includes at least one LCG The cache status of the logical channel group LCG corresponding to the ID.

Based on the above solution, the first device indicates one or more LCG IDs to the terminal device through the second signaling. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

In the fifth aspect, a cache status report BSR triggering method is provided. The method can be executed by a terminal device (such as a UE), or can also be executed by a chip or circuit used for the terminal device. This application is not limited to this. For convenience of description, the following description takes execution by a terminal device as an example.

The method includes: the terminal device receives third configuration information from the first device, the third configuration information is used to configure the second timer and the second duration, and the third configuration information is used to instruct the terminal device to trigger the BSR; in the second timer When the timing duration exceeds the second duration, the terminal device starts or restarts the second timer, and the terminal device sends a request to the third timer according to the BSR. A device sends a BSR MAC CE. It should be understood that the second timer is different from the first timer (the timer periodicBSR-Timer used to trigger the periodic BSR), and they exist independently of each other. In this way, the BSR triggering method is configured through RRC semi-static signaling, including configuring a constant BSR triggering period (ie, the second duration) and a second timer to ensure the stability of the BSR triggering period.

Combined with the fifth aspect, in some implementations of the fifth aspect, the third configuration information is also used to indicate at least one logical channel group identifier LCG ID, and the BSR MAC CE includes a cache of the logical channel group LCG corresponding to at least one LCG ID. state.

Based on the above solution, the first device indicates one or more LCG IDs to the terminal device through the third configuration information. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

Combined with the fifth aspect, in some implementations of the fifth aspect, when the terminal device triggers BSR, padding BSR, regular BSR and/or periodic BSR at the same time, the terminal device generates a BSR MAC CE according to the regular BSR and/or periodic BSR; Or, when the terminal device triggers the BSR and fills the BSR at the same time, the terminal device generates the BSR MAC CE based on the BSR.

Based on the above solution, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of this application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

The sixth aspect provides a cache status report BSR triggering method. The method can be executed by the first device (for example, a base station or a UE), or can also be executed by a chip or circuit for the first device. This application provides This is not a limitation. For convenience of description, the following description takes execution by the first device as an example.

The method includes: the first device sends third configuration information to the terminal device, the third configuration information is used to configure the second timer and the second duration, and the third configuration information is used to instruct the terminal device to trigger the BSR; When the timing duration exceeds the second duration, the first device receives the BSR MAC CE from the terminal device, and the second timer is in a starting or restarting state.

In this way, the BSR triggering method is configured through RRC semi-static signaling, including configuring a constant BSR triggering period (ie, the second duration) and a second timer to ensure the stability of the BSR triggering period.

Combined with the sixth aspect, in some implementations of the sixth aspect, the third configuration information is also used to indicate at least one LCG ID, and the BSR MAC CE includes the cache status of the LCG corresponding to the at least one LCG ID.

Based on the above solution, the first device indicates one or more LCG IDs to the terminal device through the third configuration information. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

In a seventh aspect, a communication device is provided. The communication device includes: a transceiver, a processor and a memory, the processor is used to control the transceiver to send and receive signals; the memory is used to store a computer program; the processor is used to call and run the computer program from the memory, so that the communication device executes The method provided by any one of the above implementations of the first to sixth aspects.

Optionally, there are one or more processors and one or more memories.

Alternatively, the memory may be integrated with the processor, or the memory may be provided separately from the processor.

Optionally, the communication device further includes a transmitter (transmitter) and a receiver (receiver).

In an eighth aspect, a computer-readable storage medium is provided. The computer-readable storage medium stores a program or code for device execution. When the computer program or code is run on a computer, it causes the computer to execute the above-mentioned first step. A method provided by any implementation manner from the aspect to the sixth aspect.

A ninth aspect provides a computer program product containing instructions. When the computer program product is run on a computer, the computer is caused to execute the method provided by any one of the above implementations of the first to sixth aspects.

In a tenth aspect, a chip is provided, including at least one processor, the at least one processor is coupled to a memory, the memory is used to store a computer program, the processor is used to call and run the computer program from the memory, so that the installation The communication device with the chip system executes the method provided by any one of the above implementations of the first to sixth aspects.

The chip may include an input circuit or interface for sending information or data, and an output circuit or interface for receiving information or data.

In an eleventh aspect, the present application provides a processor for executing the method provided by any one of the above implementations of the first to sixth aspects.

Description of the drawings

Figure 1A is a schematic diagram of a network architecture applicable to this application.

Figure 1B is a schematic diagram of another network architecture applicable to this application.

Figure 2 is a schematic diagram of the first triggering BSR reporting.

Figure 3 is a schematic diagram of the second type of triggering BSR reporting.

Figure 4 is a schematic flowchart of the first cache status report BSR indication method provided by an embodiment of the present application.

Figure 5 is a schematic flowchart of the second cache status report BSR indication method provided by an embodiment of the present application.

(a) to (e) in Figure 6 are schematic structural diagrams of different MAC CE formats provided by embodiments of the present application.

Figure 7 is a schematic diagram of determining the start time of the delay timer provided by an embodiment of the present application.

FIG. 8 is a schematic flowchart of the third cache status report BSR indication method provided by an embodiment of the present application.

Figure 9 is a schematic flowchart of the third cache status report BSR indication method provided by an embodiment of the present application.

Figure 10 is a schematic flowchart of the first cache status report BSR triggering method provided by an embodiment of the present application.

Figure 11 is a schematic diagram of the third triggering BSR reporting provided by the embodiment of the present application.

Figure 12 is a schematic flowchart of the second cache status report BSR triggering method provided by an embodiment of the present application.

Figure 13 is a schematic diagram of the fourth triggering BSR reporting provided by the embodiment of the present application.

Figure 14 is a schematic structural diagram of a communication device provided by an embodiment of the present application.

Detailed ways

The technical solutions in this application will be described below with reference to the accompanying drawings. The technical solutions of the embodiments of this application can be applied to various communication systems, such as: fifth generation (5G) systems or new radio (NR), long term evolution (LTE) systems, LTE frequency Frequency division duplex (FDD) system, LTE time division duplex (TDD), universal mobile telecommunication system (UMTS) or other evolved communication systems, etc. The technical solution provided by this application can also be applied to future communication systems, such as the sixth generation (6th generation, 6G) mobile communication system.

The technical solutions of the embodiments of the present application can also be applied to machine type communication (MTC), long term evolution-machine (LTE-M), and device-to-device (D2D). ) network, machine to machine (M2M) network, Internet of Things (Internet of things, IoT) network or other networks. Among them, the IoT network may include, for example, the Internet of Vehicles. Among them, the communication methods in the Internet of Vehicles system are collectively called vehicle to other devices (V2X, X can represent anything). For example, the V2X can include: vehicle to vehicle (V2V) communication, where the vehicle and Infrastructure (vehicle to infrastructure, V2I) communication, vehicle to pedestrian (V2P) communication, or vehicle to network (V2N) communication, etc.

For convenience of description, the embodiments of this application will take the 5G network architecture as an example for description.

FIG. 1A is a schematic diagram of a network architecture 100 applicable to the present application. As shown in FIG. 1A, the communication system 100 may include at least one network device, such as network device 101; the communication system 100 may also include at least one terminal device, such as terminal devices 102 to 107. Among them, the terminal devices 102 to 107 can be mobile or fixed. Network device 101 and one or more of terminal devices 102 to 107 may communicate via wireless links. That is, the network device can send signals to the terminal device, and the terminal device can also send signals to the network device. Illustratively, each network device may provide communication coverage for a specific geographic area and may communicate with end devices located within the coverage area. For example, the network device can send configuration information to the terminal device, and the terminal device can send uplink data to the network device based on the configuration information; for another example, the network device can send downlink data to the terminal device. Therefore, the network device 101 and the terminal devices 102 to 107 in Fig. 1 constitute a communication system.

One possible implementation method is that terminal devices can communicate directly with each other. For example, D2D technology can be used to achieve direct communication between terminal devices. As shown in Figure 1, D2D technology can be used to communicate directly between terminal devices 105 and 106, and between terminal devices 105 and 107. Terminal device 106 and terminal device 107 may communicate with terminal device 105 individually or simultaneously.

In another possible implementation, the terminal devices 105 to 107 can also communicate with the network device 101 respectively. For example, it can communicate with the network device 101 directly, that is, the terminal devices 105 and 106 can communicate with the network device 101 directly; it can also communicate with the network device 101 indirectly, that is, the terminal device 107 communicates with the network device 101 via the terminal device 105.

Figure 1B is a schematic diagram of another network architecture applicable to this application. As shown in Figure 1B, for BSR reporting, the technical solution of this application can be applied to cellular uplink transmission scenarios. For example, UE1 communicates with the base station through the Uu interface, that is, UE 1 reports BSR to the base station; or, it can also be applied to side chains. In the SL scenario, for example, UE1 communicates with UE2 through the SL PC5 interface. The PC5 communication requires resource allocation by the base station. At this time, UE1 needs to report UE1's BSR to the base station, that is, how much data UE1 needs to transmit to UE2, so as to enable the base station to schedule PC5 resources for UE1, thereby realizing communication between UE1 and UE2.

It should be noted that the BSR reported by UE1 at this time is the BSR for UE1 to transmit data to UE2, not the BSR for UE1 to transmit data to the base station. For example, the DCI format may be DCI format 3_0 or DCI format 3_1. Or, when there is communication between UEs without the participation of a base station, for example, when UE1 communicates with UE2, UE1 can be the above-mentioned base station role, and UE 2 can be the above-mentioned UE role. For example, UE1 instructs UE2 to trigger BSR reporting by sending sidelink control information (SCI) signaling. The SCI signaling can be SCI format 1-A, SCI format 2-A or SCI format 2-B. .

It should be understood that FIG. 1A and FIG. 1B respectively illustrate one network device and multiple terminal devices, as well as communication links between the communication devices. Optionally, the above communication system may include multiple network devices, and the coverage of each network device may include other numbers of terminal devices, such as more or less terminal devices. This application does not limit this. Below, some devices involved in the network architecture 100 will be described respectively.

1.Terminal equipment

In the embodiment of this application, the terminal equipment may be called user equipment (UE), terminal, access terminal, user unit, user station, mobile station, mobile station, remote station, remote terminal, mobile device, user terminal , terminal, wireless communication equipment, user agent or user device, etc. The terminal device in the embodiment of this application can be a mobile phone, a tablet computer, a computer with wireless transceiver functions, an XR terminal, a virtual reality (VR) terminal, an augmented reality (AR) terminal, or a mixed reality (mixed reality) , MR) terminal, wireless terminal in industrial control, wireless terminal in driverless driving, wireless terminal in telemedicine, wireless terminal in smart grid, wireless terminal in transportation safety, wireless terminal in smart city, smart home Wireless terminals, cellular phones, cordless phones, session initiation protocol (SIP) phones, wireless local loop (WLL) stations, personal digital assistants (PDAs), devices with wireless communications Functional handheld devices, computing devices or other processing devices connected to wireless modems, vehicle-mounted devices, wearable devices, terminals in 5G networks or terminals in future evolution networks, etc.

It should be understood that this application does not specifically limit the specific technology and specific equipment form used in the terminal equipment.

It should be noted that certain air interface technology (such as NR or LTE technology, etc.) can be used to communicate with each other between terminal equipment and access network equipment, and between terminal equipment and terminal equipment.

2. Network equipment

In this embodiment of the present application, the network device may be a device deployed in a wireless access network to provide wireless communication functions for terminal devices, or may be a device used to communicate with terminal devices or a chip of the device. The network equipment includes but is not limited to: radio network controller (RNC), base station controller (BSC), home base station (for example, home evolved nodeB, or home node B, HNB), baseband unit (baseband unit, BBU), access point (AP), wireless relay node, wireless backhaul node, transmission point (TP) or transmission and reception point (transmission and reception point) in the wireless fidelity system , TRP), etc., it can also be a gNB or transmission point (TRP or TP) in a 5G (such as NR) system, or one or a group (including multiple antenna panels) antenna panels of a base station in a 5G system, or it can also It is a network node that constitutes a gNB or transmission point, such as a baseband unit BBU, or a distributed unit (DU), etc.

It should be understood that all or part of the functions of the network device in the embodiment of the present application can be implemented through software functions running on hardware, or through virtualization functions instantiated on a platform (for example, a cloud platform).

In some network deployments, network equipment can adopt a CU-DU separation architecture, that is, including a centralized unit (centralized unit, CU) and a DU. Network equipment may also include active antenna units (active antenna units, AAU). CU implements some functions of network equipment, such as processing non-real-time protocols and services, implementing radio resource control (RRC), and packet data convergence protocol (PDCP) layer functions. DU implements some functions of network equipment, such as handling physical layer protocols and real-time services, implementing wireless link control (RLC) layer, media access control (MAC) layer and physical (PHY) layer. ) layer function. AAU implements some physical layer processing functions, radio frequency processing and active antenna related functions. The RRC layer information is generated by the CU, and will eventually be encapsulated by the PHY layer of the DU into PHY layer information, or converted from the PHY layer information. Therefore, under this architecture, high-level signaling (for example, RRC layer signaling) can also be considered to be sent by DU, or sent by DU+AAU. It can be understood that the network device may be a CU node, or a DU node, or a device including a CU node and a DU node, or a control plane CU Node (CU-CP node) and user plane CU node (CU-UP node) and DU node equipment.

It should be understood that this application does not specifically limit the specific technology and specific equipment form used by the network equipment.

Network equipment and terminal equipment can be deployed on land, such as indoors or outdoors, handheld or vehicle-mounted; they can also be deployed on water; they can also be deployed on aircraft, balloons and satellites in the sky. In the embodiments of this application, the scenarios in which network devices and terminal devices are located are not limited.

It should be noted that each of the above communication devices, such as the network device 101 in Figure 1 and the terminal devices 102 to 107, can be configured with multiple antennas. The plurality of antennas may include at least one transmit antenna for transmitting signals and at least one receive antenna for receiving signals. In addition, each communication device additionally includes a transmitter chain and a receiver chain. Those of ordinary skill in the art can understand that they may include multiple components related to signal transmission and reception (for example, processors, modulators, multiplexers, etc.) converter, demodulator, demultiplexer or antenna, etc.). Therefore, network equipment and terminal equipment can communicate through multi-antenna technology. Optionally, the communication system 100 may also include other network entities such as a network controller and a mobility management entity, to which the embodiments of the present application are not limited.

It should be understood that FIG. 1A and FIG. 1B are only simplified schematic diagrams for ease of understanding. The communication system 100 may also include other network devices or other terminal devices not shown in FIG. 1A and FIG. 1B; for example, a core network Equipment etc. On the one hand, access network equipment provides wireless access connections for terminal equipment, and can send data to or receive data from terminal equipment; on the other hand, access network equipment and core network equipment are also connected, and can receive data from terminal equipment. The received data is forwarded to the core network, or data that needs to be sent to the terminal device is received from the core network.

In order to facilitate understanding of the embodiments of this application, the terms involved in this application are briefly explained.

1. Extended Reality XR

XR refers to various types of combined real and virtual environments generated by computing technology and wearable devices, as well as human-computer interaction, and mainly includes virtual and reality interaction technologies such as VR, AR and MR. In order to improve the experience of people interacting with the virtual world, XR services have strict requirements on bandwidth and latency. During the uplink transmission process, the XR terminal can collect and continuously upload images of the current scene to the server through the built-in camera at a specific frequency (for example, 60Hz or 120Hz, etc.). During the downlink transmission process, the server's encoder generates data content at a fixed frequency (for example, 60Hz or 120Hz, etc.) and transmits it to the XR terminal via the core network and RAN.

Usually, XR services periodically generate data frames according to a certain frame rate. Due to the encoding characteristics of XR video data, such as intra-frame, inter-frame encoding, and the randomness of video content changes, XR data frame size usually varies greatly. For example, the sizes of two adjacent XR data frames may be different, and may be quite different. In addition, the changes in the size of the XR data frame are also random and conform to a certain distribution, but it is almost impossible to predict accurately. By way of example, the business models of downlink XR services include AR/VR and cloud games. Among them, the AR/VR frame rate can be 60fps or 120fps, that is, 60 or 120 frames of video images are generated per second, one video frame appears approximately every 16.67ms or 8.33ms, and the transmission rate is 20Mbps or 45Mbps, etc. The air interface transmission delay budget for a complete video frame is 10ms. The CG frame rate can be 60fps or 120fps, that is, 60 or 120 frames of video images are generated per second, and the transmission rate is 8Mbps or 30Mbps, etc. The air interface transmission delay budget of a complete video frame is 15ms.

It should be understood that the time starts from when the base station receives one frame of image data from the UPF until one frame of image is successfully sent from the base station to the UE. This period of time can be called the air interface transmission delay budget of the video frame.

2. BSR

BSR includes regular BSR (regular BSR), periodic BSR (periodic BSR), padding BSR (padding BSR), etc. Among them, the triggering conditions of regular BSR include the following (1)-(3), and the triggering conditions of periodic BSR include Following (4), BSR is triggered by periodicBSR-Timer timeout, and the triggering conditions for filling BSR include the following (5).

(1) When there is a new uplink data packet to be transmitted in the logical channel LCH belonging to a certain logical channel group LCG, and the priority of the logical channel is higher than the priority of the logical channel in any other logical channel group;

(2) When there is a new uplink data packet to be transmitted in the logical channel LCH belonging to a certain logical channel group LCG, and currently all logical channels in the logical channel group have no data to transmit.

(3) retxBSR-Timer times out, and the UE has transmittable data on any logical channel in a certain logical channel group;

(4)periodicBSR-Timer times out;

(5)paddingBSR: The remaining resources of MAC PDU can be put down BSR+BSR header. That is to say, uplink resources have been allocated, and the number of padding bits is greater than or equal to the sum of the number of bits of the BSR MAC CE and its MAC subheader.

It should be noted that when the UE triggers regular BSR and periodic BSR and has uplink resources, the UE determines to report long BSR or short BSR according to the LCG situation. Specifically, when there is more than one LCG buffer with data to be transmitted, the UE reports a long BSR; when there is only one LCG buffer with data to be transmitted, the UE reports a short BSR. Therefore, when the UE transmits data, it reports the BSR of the LCG where the XR data frame is located to the base station, which enables the base station to reasonably allocate uplink resources and reduce resource waste.

Under the new vision of 5.5G, real-time bandwidth interaction (RTBC) scenarios support large bandwidth and low interaction latency, aiming to increase bandwidth by 10 times under given latency and reliability requirements, and realize the realization of human-virtual world Immersive experience when interacting. Among them, the XR Pro business, which has ultra-high bandwidth and ultra-low latency requirements, poses more severe challenges to the current 5G.

For example, when there is uplink data to be sent, the UE sends a scheduling request (SR) to the base station on the physical uplink control channel (PUCCH) to request the uplink grant (UL grant) . SR only tells the base station whether there is uplink data transmission, but does not tell the base station how much data to transmit. The SR transmission resources (such as period, offset, etc.) of each LCH can be different, and each logical channel is configured separately. If the UE does not receive the uplink authorization from the base station, the UE can continue to send SR. After receiving the SR, the base station responds to the SR and indicates the scheduling information to the UE through the PDCCH (for example, DCI format 0_0 or DCI format 0_1). The base station will schedule the UE according to a small, fixed amount of data, because the base station does not know how much data the UE needs to send at this time. After receiving the scheduling instruction, the UE sends data on the PUSCH resources allocated by the base station, including BSR information, which is used to inform the base station of the amount of uplink data to be transmitted on the LCH or LCG. If the BSR received by the base station is greater than 0, it continues to indicate scheduling information to the UE through the PDCCH, and then the UE performs data transmission on the PUSCH resources indicated by the base station.

Currently, 5G uplink transmission can be divided into two scheduling methods: dynamic scheduling and semi-persistent scheduling (SPS). Among them, dynamic scheduling includes dynamic grant (DG), and semi-static scheduling includes configured grant (CG) scheduling. Dynamic scheduling refers to the base station scheduling PUSCH resources (such as frequency domain and time domain resource locations) for the UE through downlink control information (DCI), and the UE can transmit uplink data on the PUSCH resources. CG includes two scheduling methods. In configuration grant type 1 (CG type1), the base station configures the scheduling period, scheduling resources (such as frequency domain, time domain resource location), hybrid automatic repeat request (hybrid automatic repeat request) for the UE through RRC signaling. Repeat request, HARQ) process number, modulation and coding scheme (modulation and coding scheme, mcs) and other parameters, the UE can authorize uplink data transmission in this configuration. In configuration grant type 2 (CG type2), the base station configures parameters such as the scheduling cycle, the number of HARQ processes, and which mcs table to use for the UE through RRC signaling, and then indicates the frequency domain, time domain resource location, and mcs index value through DCI, that is, CG type2 is controlled by physical layer or layer 1 signaling to activate or deactivate the transmission of CG.

Based on the above scheduling method, it is necessary to consider how the base station accurately provides scheduling resources to the UE. That is to ensure that XR data frames are completely transmitted within the limited packet delay budget (PDB) without causing a waste of resources. In the traditional air interface uplink transmission process between the base station and the UE, the base station can be notified of the current UE's LCG cache status by the UE reporting the BSR, enabling the base station to reasonably allocate uplink resources and reduce the waste of uplink resources.

Specifically, the triggering of the above conventional BSR will be illustrated below with reference to FIG. 2 . Figure 2 shows a schematic diagram of the first triggering BSR reporting. As shown in Figure 2, taking the XR video service as an example, it includes 2 LCGs, such as LCG ID0 and LCG ID1. Among them, LCG ID0 includes 2 LCs, such as LCID1 and LCID2; LCG ID1 includes 2 LCs, such as LCID3 and LCID4.

Assume that the LC where the XR data frame is located is LCID1, the XR video service cycle is about 16.67ms or 8.33ms, and its air interface transmission PDB requirement is about 60ms. Since the air interface transmission PDB is greater than the interval for the XR data frame to arrive at the LC, the first XR may occur When the transmission of frame (data 1) is not completed, the second XR frame (data 2) has arrived at the LC. At this time, neither the above triggering conditions (1) nor (2) of the conventional BSR are satisfied, so the UE will not trigger the BSR report. That is, the current UE cannot report the BSR according to the data period of the XR data frame (for example, 16.67ms or 8.33ms). The failure of the BSR to be reported to the base station may cause a waste of resources, or the base station may mistakenly believe that the UE has no data to be transmitted and not continue to schedule uplink resources, resulting in additional transmission delays.

Specifically, the triggering of the above-mentioned periodic BSR and filling BSR will be illustrated below with reference to FIG. 3 .

In one possible implementation, the base station can configure periodicBSR-Timer through RRC signaling to instruct the UE to periodically trigger BSR reporting, that is, periodicBSR. For example, the periodicBSR-Timer is synchronized with the transmission period of the XR data frame to enable the UE to trigger BSR reporting when transmitting the XR data frame. It should be noted that the restart of the periodicBSR-Timer depends on the timeout time of the timer periodicBSR-Timer and also depends on whether the UE reports the BSR. That is to say, even if the periodicBSR-Timer does not time out, but the UE triggers a regular BSR report due to other reasons (for example, the above trigger condition (1) or (2)), the periodicBSR-Timer will be reset.

Figure 3 shows a schematic diagram of the second type of triggering BSR reporting. As shown in Figure 3, taking the subcarrier spacing (SCS) as 15kHz (each time slot is 1ms) and the time division duplex TDD configuration as 4:1, it is assumed that the transmission period of the XR data frame is 15ms. And the periodicBSR-Timer period is the same as the XR frame period. The UE transmits XR frame 1 in the first uplink time slot (U1), reports the BSR corresponding to XR frame 1, and restarts the periodicBSR-Timer. According to the above transmission cycle of the XR frame, XR frame 2 will arrive at the LC#1 in the fourth uplink time slot (U4). The UE correspondingly transmits the XR frame 2 on the U4 and reports the BSR corresponding to the XR frame 2, and Restart periodicBSR-Timer. However, if in the third uplink time slot (U3), the UE triggers and reports BSR due to new data to be transmitted on the high-priority logical channel LC#2, the periodicBSR-Timer will be restarted. Then, even if there is XR frame 2 to be transmitted at U4, considering that the transmission of XR frame 1 on LC#1 may not be completed, and the periodicBSR-Timer has not timed out at this time, the UE does not trigger BSR reporting at U4.

Therefore, even if the periodicBSR-Timer and the transmission period of the XR data frame are matched, the trigger time of the periodicBSR-Timer and the transmission period of the XR data frame cannot be guaranteed to be synchronized.

Another possible implementation is that after the UE fills the MAC PDU with the XR data frame, if the MAC PDU still has remaining resources, the UE can transmit BSR in the remaining resources, that is, padding BSR, to improve resource utilization. therefore, The reporting of filled BSR depends on the resources allocated by the base station and the resources required by the UE's LCG. That is to say, there is uncertainty in filling the BSR, and there is no guarantee that the filled BSR will be reported on time.

In short, the periodicBSR-Timer will be reset when the UE reports BSR, causing the reporting of periodic BSR to be unable to be fully synchronized with the transmission of XR data frames, resulting in a waste of resources or additional transmission delays.

In summary, the current BSR triggering mechanism cannot well support timely reporting of BSR for XR video services, resulting in a waste of resources or additional transmission delays.

In view of this, this application provides a communication method and communication device to ensure that the UE reports the BSR to the base station each time it transmits a new XR data frame, and enables the BSR to be reported in time with the transmission of the XR data frame. The method disclosed in this application can improve the utilization of uplink resources, reduce the transmission delay of uplink XR data frames, and reduce the waste of air interface resources.

In order to facilitate understanding of the embodiments of this application, the following points are explained:

First, if there are no special instructions or logical conflicts, the terms and/or descriptions between different embodiments are consistent and can be referenced to each other, and the technical features in different embodiments can be combined to form new ones based on their inherent logical relationships. Embodiments.

Second, “at least one” refers to one or more, and “multiple” refers to two or more (including two). "And/or" describes the association of associated objects, indicating that there can be three relationships, for example, A and/or B, which can mean: A exists alone, A and B exist simultaneously, and B exists alone, where A, B can be singular or plural. In the text description of this application, the character "/" generally indicates that the related objects are in an "or" relationship. "At least one of the following" or similar expressions thereof refers to any combination of these items, including any combination of a single item (items) or a plurality of items (items). For example, at least one of a, b and c can mean: a, or, b, or, c, or, a and b, or, a and c, or, b and c, or, a , b and c. Among them, a, b and c can be single or multiple respectively.

Third, “first”, “second” and various numerical numbers (for example, #1, #2) are only distinctions for convenience of description and are not used to limit the scope of the embodiments of the present application. For example, distinguish different instruction information, etc.

Fourth, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or equipment that includes a series of steps or units and need not be limited to those explicitly listed may include other steps or elements not expressly listed or inherent to the process, method, product or apparatus.

Fifth, “for indicating” or “instructing” may include direct indicating and indirect indicating, or “for indicating” or “instructing” may indicate explicitly and/or implicitly. For example, when describing certain information as indicating information I, it may include that the information directly indicates I or indirectly indicates I, but it does not mean that the information must contain I. As another example, an implicit indication may be based on the location and/or resources used for transmission; an explicit indication may be based on one or more parameters, and/or one or more indexes, and/or one or more bits it represents. model.

The instruction methods involved in this application should be understood to cover various methods that can enable the party to be instructed to obtain the information to be instructed. The information to be instructed can be sent together as a whole, or can be divided into multiple sub-information and sent separately, and the sending cycle and/or sending timing of these sub-information can be the same or different. This application does not limit the specific sending method. The sending period and/or sending timing of these sub-information may be predefined, for example, according to a protocol, or may be configured by the transmitting device by sending configuration information to the receiving device. The configuration information may include, for example but not limited to, one or a combination of at least two of radio resource control signaling, MAC layer signaling and physical layer signaling. The radio resource control signaling includes, for example, RRC signaling, the MAC layer signaling includes, for example, a MAC control element (CE), and the physical layer signaling includes DCI signaling.

The communication method provided by the embodiment of the present application will be described in detail below with reference to the accompanying drawings.

It should be understood that this application is mainly applicable to services requiring low latency and high reliability, such as XR or URLLC video services. Of course, it is also applicable to other services that do not have such high latency and reliability requirements, and can improve user-perceived throughput and user experience. For ease of understanding, the communication method provided by the embodiments of the present application will be described in detail by taking the interaction between the network device and the terminal device of the XR video service as an example.

Figure 4 is a schematic flowchart of the first cache status report BSR indication method 400 provided by an embodiment of the present application. As shown in Figure 4, the method specifically includes the following steps.

S410. The terminal device receives the first message from the first device.

Correspondingly, the first device sends the first message to the terminal device.

The first message is used to instruct the terminal device to trigger the BSR, and the BSR is used to indicate the cache status of the logical channel group LCG of the terminal device.

In the embodiment of this application, the amount of data may be called data size, and the cache status (buffer status) may be called cache data size, or cache size (buffer size), or cache data amount. For example, the upstream cache status may be referred to as upstream cache data volume, upstream cache data size, or upstream cache size. The amount of uplink data to be transmitted may be called the size of the uplink data to be transmitted, etc. This application does not specifically limit the specific name.

For example, the first device may be a network device (such as a base station) or a terminal device (such as UE2). That is, the technical solution of this application is applicable to both cellular uplink transmission scenarios and sidelink SL scenarios. It should be noted that in the SL scenario, in order to communicate with UE2, UE1 needs to report the BSR of UE1 to the base station to enable the base station to schedule resources for UE1. The BSR at this time is the BSR used by UE1 to transmit data to UE2.

In addition, the terminal device also receives a second message from the first device. The second message is used to indicate the transmission resources allocated by the first device to the terminal device. The transmission resources are used to carry the BSR MAC CE.

Optionally, the second message may be sent after the terminal device sends the first message. For example, the first message is carried in the MAC CE and the second message is carried in the DCI. Alternatively, the second message may be sent simultaneously with the first message. For example, the first message and the second message may be carried in the same DCI, which is not specifically limited in this application.

For example, the transmission resources include physical uplink shared channel PUSCH resources or physical sidelink shared channel PSSCH resources. Specifically, UE1 can send the BSR MAC CE to the base station on the PUSCH resources allocated by the base station; or, UE1 can send the BSR MAC CE to UE2 on the PSSCH resources allocated by the base station.

Optionally, the second message is carried in control information, and the control information includes downlink control information DCI or side link control information SCI. Further, the control information is also used to carry the first message.

For example, both the first message and the second message are carried in the same control information. For the uplink, the control information may be DCI, and for the sidelink, the control information may be SCI. For example, the first message and the second message are fields of DCI format 0_0, or DCI format 0_1, or DCI format 0_2, where the second message may include multiple fields.

Optionally, the second message is carried in control information, and the control information includes downlink control information DCI or side link control information SCI. Further, the first message is carried in the MAC CE.

Exemplarily, the first message is carried in the MAC CE, and the second message is carried in the control information, such as DCI or SCI.

In a possible implementation, the first message is carried on the MAC CE, and the MAC subheader of the MAC CE includes the logical channel identifier LCID.

Exemplarily, the first message is also used to indicate at least one logical channel group identification LCG ID.

Exemplarily, the terminal device receives first configuration information from the first device, and the first configuration information is used to configure at least one logical channel group identification LCG ID.

Further, the first message is also used to indicate the first duration, and the first duration is used to indicate the time offset of the first moment relative to the second moment. The first moment is the moment when the terminal device triggers the BSR, and the second moment is when the terminal device triggers the BSR. The moment the device received the first message.

For example, the unit of the first duration may be a slot, a symbol, or a millisecond, for example, 2 slots.

It should be understood that by indicating the first duration (ie, the difference between the time when the terminal device receives the first message and the time when the terminal device triggers the BSR), the effect of timing the BSR can be achieved. For example, after the terminal device receives the MAC CE at time t0, the decoding is successful and the BSR report is triggered. At this time, the first duration can be zero. However, considering that the terminal device may fail to decode the MAC CE when it receives it during the initial transmission, the terminal device needs to request the first device to schedule a retransmission, which will lead to the terminal device correctly decoding the time and initial transmission schedule of the MAC CE. The time is inconsistent. The first duration can ensure that when the terminal device triggers BSR, the first device is enabled to obtain the BSR MAC CE in a timely and effective manner and allocate transmission resources to the terminal device.

S420: The terminal device sends the BSR media access control MAC control element CE to the first device according to the first message.

In a possible implementation, the terminal device sends the BSR MAC CE to the first device when the first condition is met. Among them, the first condition is that the transmission resources are used for initial transmission; the transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and the BSR MAC CE is triggered by the first message.

It should be understood that by defining the first condition, it is explained that the reporting method is triggered by the MAC CE in the BSR.

In another possible implementation, when the value of the LCID is a preset value, the terminal device sends the BSR MAC CE to the first device according to the first message.

For example, the MAC CE includes an 8-bit MAC subheader, and the terminal device can determine whether the received MAC subheader is used to trigger BSR reporting based on the LCID. For example, the preset value of the LCID of the MAC CE used to trigger the BSR can be any value from 35 to 44, such as 38. If the value of LCID is 45, it indicates that the MAC CE is not used to trigger BSR reporting; similarly, if the value of LCID is 38, it indicates that the terminal device triggers BSR reporting, that is, after receiving the MAC CE, the terminal device will trigger A BSR report.

In a possible manner, the BSR triggered in the above manner may be a conventional BSR. That is, when the terminal device triggers BSR reporting through the first message, the UE will transmit the BSR MAC CE on the available transmission resources in the conventional BSR manner.

In yet another possible implementation, when the first message is also used to indicate at least one logical channel group identifier LCG ID, or the terminal device receives the first configuration information from the first device, the first configuration information is used to configure at least one When a logical channel group identifies an LCG ID, the BSR MAC CE includes the cache status of at least one LCG corresponding to the LCG ID.

For example, the first device semi-statically configures the LCG ID for the terminal device in advance, for example, LCG ID=6. Then, after receiving the first message, the terminal device triggers the reporting of the BSR MAC CE including the LCG ID corresponding to 6. LCG cache status. Alternatively, the values of the LCG ID carried in the MAC CE received by the terminal device are 4 and 5, and the BSR MAC CE immediately reported by the terminal device includes the LCG cache status corresponding to the LCG ID of 4 and 5. Or Or, the MAC CE received by the terminal device contains 8 bits, each bit corresponding to the bitmap of LCG0-LCG7. If the corresponding bit "1" of LCGi indicates that the BSR report of LCGi is triggered, the corresponding bit "0" of LCGi indicates not to report. LCGi. For example, if the bits corresponding to LCG3 and LCG4 are "1", the BSR MAC CE reported by the terminal device carries the cache status of LCG3 and LCG4. Or, bit information "011" is carried through DCI to instruct the terminal device to trigger LCG3 reporting, etc.

Based on the above solution, the first device can directly or indirectly indicate one or more LCG IDs to the terminal device through indication information (first message); or, the first device can also semi-statically configure the terminal device (first configuration information) One or more LCG IDs. Based on one or more LCG IDs specified by the first device, the terminal device carries the cache status of the LCG corresponding to the at least one LCG ID when reporting the BSR MAC CE.

For example, when the terminal device triggers BSR, padding BSR, regular BSR and/or periodic BSR at the same time, the terminal device generates the BSR MAC CE according to the regular BSR and/or periodic BSR; or, when the terminal device triggers BSR and padding BSR at the same time , the terminal device generates BSR MAC CE based on BSR.

It should be understood that a MAC protocol data unit SDU should contain at most one BSR MAC CE, even if multiple events trigger BSR reporting. That is to say, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of the present application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

In this way, by receiving the BSR trigger indication sent by the first device, it can be ensured that the terminal device reports the BSR in time while sending data, so as to enable the first device to allocate reasonable transmission resources to the terminal device, thereby reducing resource waste and transmission delay. .

Taking the interaction between the base station and the UE in the XR video service in the cellular uplink transmission scenario as an example, a method for the base station to actively trigger the UE to report BSR is explained in detail with reference to Figure 5.

FIG. 5 is a schematic flowchart of the second cache status report BSR indication method 500 provided by an embodiment of the present application. In this implementation, the base station actively triggers the reporting of BSR through MAC CE to ensure that the UE reports BSR while sending data to enable resource allocation by the base station. As shown in Figure 5, the method specifically includes the following steps.

S510: The base station sends the MAC CE (ie, the first message) to the UE.

Correspondingly, the UE receives the MAC CE from the base station.

Among them, the MAC CE is used to instruct the UE to trigger BSR reporting, and the BSR is used to indicate the amount of uplink buffered data of at least one LCG of the UE.

It should be understood that compared with the traditional BSR triggering mechanism, the embodiment of the present application defines the UE receiving the MAC CE that triggers BSR as a new trigger condition for conventional BSR.

For example, in the XR video service, the UE transmits data frames to the base station periodically (for example, 60Hz). The base station can know the specific moment when the UE uploads video data, so the base station can pass the MAC CE before the UE uploads the XR data frame. Instructs the UE to trigger BSR reporting.

Specifically, the following is a detailed description of how the base station instructs the UE to trigger BSR reporting through the MAC CE format based on the design of the MAC CE format.

Figure 6(a) is a schematic structural diagram of the first MAC CE format provided by the embodiment of the present application. As shown in (a) of Figure 6, the MAC CE subPDU includes an 8-bit MAC subheader and a 0-bit MAC CE. Among them, MAC subheader includes R and LCID. R is a reserved bit (reserved). LCID is the logical channel identifier or MAC CE identifier.

One possible implementation method is that the UE determines whether the MAC subheader is used to trigger BSR reporting based on the LCID.

For example, it is assumed that the LCID value of the MAC CE used to trigger BSR belongs to the range 35 to 44. This value range can be configured by the base station through signaling, or it can be pre-configured by the factory. For example, the LCID of the MAC CE sent by the base station to trigger BSR is equal to 38, which is used to instruct the UE to trigger BSR reporting. After receiving the MAC CE, the UE will trigger a regular BSR report. Specifically, when there are multiple LCG caches with data to be transmitted, the UE reports a long BSR, including the amount of uplink cache data of the multiple LCGs, and optionally also includes the LCG ID. On the contrary, the UE reports the short BSR, which is the amount of uplink buffered data of a certain LCG.

Further, the base station can trigger the UE to report the BSR of the specified LCG through the MAC CE.

One possible implementation method is that the base station can semi-statically configure an LCG ID for the BSR triggered by the MAC CE. For example, the base station semi-statically configures at least one LCG ID for the UE through the first configuration information, that is, the BSR triggered by the MAC CE only uses The size of the uplink cache data corresponding to the semi-statically configured LCG ID is reported.

For example, the base station can add logicalChannelGroup in the BSR-config information element signaling. The specific configuration method can be as follows:

It should be understood that when a logicalChannelGroup is configured, the BSR triggered by the MAC CE only reports the uplink cache data size corresponding to the logicalChannelGroup, that is, this reporting method is only performed when the BSR is triggered by the MAC CE.

Optionally, due to the newly introduced MAC CE, it is necessary to define the priority order of BSR triggered by the newly introduced MAC CE and other types of BSR.

That is to say, when the UE triggers the BSR, filling BSR, regular BSR and/or periodic BSR provided by this application at the same time, the BSR MAC CE is generated according to the regular BSR and/or periodic BSR; or, when the UE triggers the BSR and the filling BSR at the same time , the BSR generates the BSR MAC CE according to this solution, that is, the generated BSR MAC CE only contains the cache status report of the LCG ID corresponding to the logicalChannelGroup.

For example, if the UE has already triggered a BSR report due to other conditions before reporting the BSR triggered by the MAC CE, such as the arrival of new data to be transmitted triggering regular and/or periodic BSR, the UE will follow the current regular BSR method. Report long BSR or short BSR.

Another possible implementation method is that the base station can semi-statically configure multiple LCG IDs for the BSR triggered by the MAC CE. That is, the BSR triggered by the MAC CE is used to report the uplink buffer number corresponding to the multiple LCG IDs configured semi-statically. According to size.

For example, the above logicalChannelGroup can be extended to logicalChannelGroupList, as shown below:

logicalChannelGroupList SEQUENCE(SIZE(1…maxNrof

maxLCG-ID))OPTIOAL,--Need R

In another possible implementation, the base station can dynamically instruct to trigger BSR reporting of multiple designated LCGs.

For example, the base station instructs the UE to trigger BSR reporting through DCI, which carries the LCG ID (for example, LCG3). Then the UE reports the BSR corresponding to LCG3 to the base station.

In view of the above base station triggering the BSR to report the amount of uplink cache data of one or more designated LCGs through the MAC CE, the technical solution of this application also provides the following possible implementation methods for exemplary explanation.

Figure 6(b) is a schematic structural diagram of the second MAC CE format provided by the embodiment of the present application. As shown in (b) of Figure 6, the MAC CE subPDU contains an 8-bit MAC subheader and an 8-bit MAC CE. Among them, the MAC subheader part is the same as the MAC subheader shown in (a) of Figure 6, and will not be described again here. The 8-bit MAC CE corresponds to the bitmaps of LCG0~LCG7 respectively.

One possible implementation is that when the bit corresponding to the LCGi is '1', the UE will report the BSR corresponding to the LCGi; when the bit corresponding to the LCGi is '0', the UE will not report the BSR corresponding to the LCGi. For example, when the UE receives the LCGi bitmap in the MAC CE as '10001000', it can determine that the bits corresponding to LCG7 and LCG3 are '1', and the bits corresponding to other LCGs are '0', then the UE The reported BSR will include the cache data sizes of LCG7 and LCG3.

Figure 6(c) is a schematic structural diagram of the third MAC CE format provided by the embodiment of the present application. As shown in (c) of Figure 6, the MAC CE subPDU contains an 8-bit MAC subheader and MAC CE. Among them, the MAC subheader part is the same as the MAC subheader shown in (a) of Figure 6, and will not be described again here. The LCGi in the MAC CE part is used to indicate an LCG number that the BSR should contain when triggering the UE to report the BSR. For example, when the LCGi is LCG3, the BSR reported by the UE includes the buffered data size of LCG3. When the LCGi is LCG5, the BSR reported by the UE includes the cache data size of LCG5.

Figure 6(d) is a schematic structural diagram of the fourth MAC CE format provided by the embodiment of the present application. As shown in (d) of Figure 6, the MAC CE subPDU contains an 8-bit MAC subheader and MAC CE. Among them, the MAC subheader part is the same as the MAC subheader shown in (a) of Figure 6, and will not be described again here. Part of the LCGi of the MAC CE is used to indicate the multiple LCG numbers that the BSR should contain when triggering the UE to report the BSR. For example, when the LCGi are LCG3 and LCG7 respectively, the BSR reported by the UE includes the cache data sizes of LCG3 and LCG7.

Furthermore, the base station can also instruct the UE through the MAC CE the specific time to trigger the BSR report.

Figure 6(e) is a schematic structural diagram of the fifth MAC CE format provided by the embodiment of the present application. As shown in (e) of Figure 6, a MAC CE that can trigger BSR regularly is provided. The MAC CE subPDU contains the 8-bit MAC subheader and MAC CE. Among them, the MAC subheader part is the same as the MAC subheader shown in (a) of Figure 6, and will not be described again here. The MAC CE part includes a delay timer (delay Timer) used to indicate the first duration. The first duration is used to indicate the time offset of the time when the UE triggers BSR relative to the time when the UE receives the MAC CE. In other words, the delay Timer is used to determine the time when the UE triggers or reports BSR.

For example, the unit of the delay Timer may be a time slot, a millisecond, or a number of symbols.

It should be understood that the timer starts counting after the UE receives the MAC CE, and the time corresponding to the timer expires. Trigger BSR.

One possible implementation is that after the UE receives the transport block (TB) carrying the MAC CE for the first time, the decoding fails. The UE can report a negative acknowledgment (NACK) to the base station through HARQ feedback. After receiving the NACK, the base station schedules a retransmission for the TB of the UE, and then the UE re-receives, decodes and reports. Therefore, it may happen that the time when the UE correctly decodes the MAC CE is inconsistent with the time of the initial transmission schedule. In this case, the UE will determine the delay timer start time based on the initial transmission time.

For example, as shown in Figure 7, the UE receives the MAC CE for the first time at time t0, and the delay timer is started at time t0. However, due to the decoding failure, the UE needs to request the base station to schedule retransmission and re-receive the MAC CE at time t3. The decoding is successful, and the delay Timer included in the MAC CE part instructs the UE to trigger the BSR report at t5. At this time, the first duration is the difference between t5 and t0.

Based on the above solution, by carrying the delay timer in the MAC CE, when the time of correctly decoding the MAC CE is inconsistent with the initial transmission scheduling time, the UE can still report the BSR in time, avoiding transmission delay and waste of resources. .

To sum up, Figure 6 (a) is the base station instructing the UE to trigger BSR reporting through MAC CE. The MAC CE shown in Figure 6 (b) to (e) is based on the MAC CE shown in Figure 6 (a). further improvements. It should be understood that (b) to (d) of Figure 6 are parallel relationships, that is, the base station instructs the UE through MAC CE to trigger the BSR to report the amount of uplink buffered data corresponding to one or more designated LCGs, and (e) of Figure 6 is the base station Use MAC CE to indicate the specific moment when the UE triggers BSR reporting.

It should be understood that the MAC CE shown in (e) of Figure 6 can also be used in combination with the MAC CE shown in (b) to (d) of Figure 6 respectively. In other words, the base station can also use the MAC CE to instruct the UE when to trigger the BSR to report the amount of uplink buffered data corresponding to one or more LCGs. For specific implementation methods, please refer to the above and will not be repeated here.

It should be noted that the MAC CE implementation provided above is only an exemplary description, and this application does not specifically limit it. For example, the number of LCGis that the base station triggers to report to the BSR through the MAC CE can be m, where m is an integer greater than or equal to 1 and less than or equal to the maximum configurable number of LCGs, such as 8.

S520: The base station allocates uplink resources to the UE.

Illustratively, the uplink resources are physical layer resources, such as PUSCH resources. The base station allocates PUSCH resources to the UE through DCI signaling.

Exemplarily, the UE receives a second message from the base station, and the second message is used to indicate the uplink transmission resources allocated by the base station to the UE, and the uplink transmission resources are used to carry the BSR MAC CE.

It should be understood that if there are uplink resources when BSR is triggered, the UE can report BSR on the uplink resources. If there are no uplink resources when the BSR is triggered, the UE can suspend the triggered BSR, wait for the uplink resources to be applied to the base station, and then report the BSR on the applied uplink resources. For example, the UE sends a scheduling request (SR) to the base station to request uplink resources for reporting BSR, and the base station configures uplink resources for the UE based on the SR.

One possible implementation method is that the base station configures uplink resources for the UE through dynamic scheduling.

For example, the base station may schedule PUSCH resources for the UE through DCI, and the UE may transmit uplink data on the PUSCH resources.

Another possible implementation manner is that the base station configures uplink resources for the UE through semi-static scheduling.

For example, the base station can configure the scheduling cycle, time-frequency domain scheduling resources, HARQ and other parameters for the UE through RRC signaling, and the UE can transmit uplink data in the configuration authorization; or, the base station can also first configure the UE through RRC signaling. Configure the scheduling cycle, HARQ and other parameters, and then activate the transmission of the configuration authorization through DCI.

S530, the UE sends the BSR MAC CE to the base station on the allocated uplink resources.

Correspondingly, the base station receives the BSR MAC CE from the UE.

Among them, BSR MAC CE is used to indicate the amount of uplink buffered data of at least one LCG of the UE.

It should be noted that before sending the BSR MAC CE, the UE needs to determine the uplink buffer data size (buffer size) carried in the BSR based on the amount of data to be transmitted in the current LCG buffer area, that is, generate a BSR.

A possible implementation method is that the UE sends the BSR MAC CE to the base station when the first condition is met.

Among them, the first condition is that the uplink transmission resources are used for initial transmission; the uplink transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and the BSR MAC CE is triggered by the first message (such as MAC CE).

It should be understood that the BSR is reported at LCG granularity, that is, the UE accumulates the amount of uplink data to be transmitted on at least one LCH belonging to the same LCG, and generates a BSR of the LCG for reporting. When the base station configures the logical channel, it will specify the LCG to which each LCH belongs. Further, the UE may be configured with multiple LCGs, so the BSR reported by the UE may include the uplink cache size of one or more LCGs.

For example, if the UE has more than one LCG buffer area to transmit data, the long BSR is reported, and otherwise the short BSR is reported.

Optionally, for the above-mentioned MAC CE used to trigger BSR, the logical channel LCH can be used as the granularity, and uplink resources for transmitting uplink data can be applied to the base station for each logical channel.

In this implementation, the base station actively triggers the UE to report the BSR through the MAC CE. For example, when the UE wants to upload an XR data frame, it triggers the UE to report the BSR by sending signaling, enabling the BSR to be implemented in time with the transmission of the XR data frame. Report.

It should be understood that this application is also applicable to SL scenarios. Next, taking the interaction between UE1 and UE2 in the XR video service in the SL scenario as an example, the method of triggering BSR reporting between UE1 and UE2 is explained in detail with reference to Figure 8. It should be understood that UE1 and UE2 communicate through the SL PC5 interface, and UE1 communicates with the base station through the Uu interface. The PC5 communication requires resource allocation by the base station. At this time, in order to communicate with UE2, UE1 needs to report UE1's BSR to the base station. The BSR is used to indicate how much data UE1 needs to send to UE2 to enable the base station to schedule PC5 resources for UE1. When there is communication between UEs without the participation of a base station, UE1 in this implementation can be understood as the base station role in the above method 500, and UE2 can be understood as the UE role in the above method 500.

Figure 8 is a schematic flowchart of the third cache status report BSR indication method 800 provided by the embodiment of the present application. As shown in Figure 8, the method specifically includes the following steps.

S810, the base station sends MAC CE (ie, the first message) to UE1.

Correspondingly, UE1 receives the MAC CE from the base station.

Among them, the MAC CE is used to instruct UE1 to trigger BSR# reporting, and BSR# is used to indicate how much data UE1 needs to send to UE2.

Specifically, the base station can instruct UE1 to trigger BSR# reporting through the design of different formats of MAC CE.

S820: The base station allocates uplink resources to UE1.

Illustratively, the uplink resources are physical layer resources, such as PUSCH resources. For example, the base station allocates PUSCH resources to UEl through DCI signaling.

One possible implementation method is that the base station configures uplink resources for UE1 through dynamic scheduling.

Another possible implementation method is that the base station configures uplink resources for UE1 through semi-static scheduling.

S830, UE1 sends BSR#MAC CE to the base station on the allocated uplink resources.

Correspondingly, the base station receives the BSR#MAC CE from UE1.

S840: The base station allocates sidelink transmission resources to UE1.

Illustratively, the sidelink transmission resources are physical layer resources, such as PSSCH resources. For example, the base station allocates PSSCH resources to UEl through DCI signaling.

Exemplarily, UE1 receives message #1 from the base station. Message #1 is used to indicate the sidelink transmission resources allocated by the base station to UE1, such as PSSCH. The sidelink transmission resources are used to carry data transmitted by UE1 to UE2. .

One possible implementation method is that the base station configures sidelink transmission resources for UE1 through dynamic scheduling, such as through DCI format 3_0 or DCI format 3_1.

In another possible implementation manner, the base station configures sidelink transmission resources for UE1 through semi-static scheduling.

S850: UE1 sends data to UE2 on the allocated sidelink transmission resources.

Correspondingly, UE2 receives data from UE1.

In this implementation, the base station actively triggers UE1 to report BSR# through MAC CE. For example, when UE1 wants to upload an XR data frame to UE2, it triggers UE1 to report BSR# by sending signaling, and enables BSR# to follow the XR data. Frame transmission and timely reporting.

It should be noted that the specific implementation of the above-mentioned steps S810-S830 may refer to the steps S510-S530 in the above-mentioned method 500. For the sake of brevity, no further details will be given here.

Next, taking the interaction between the base station and the UE in the XR video service in the cellular uplink transmission scenario as an example, another way for the base station to actively trigger the UE to report BSR will be described in detail with reference to Figure 9. The difference from the method shown in Figure 5 is that this implementation is that the base station instructs the UE to trigger BSR reporting through DCI.

FIG. 9 is a schematic flowchart of the fourth cache status report BSR indication method 900 provided by the embodiment of the present application. As shown in Figure 9, the method specifically includes the following steps.

S910: The base station sends DCI (ie, the first message) to the UE.

Correspondingly, the UE receives DCI from the base station.

The DCI is used to instruct the UE to trigger BSR reporting, and the BSR is used to indicate the amount of uplink buffered data of at least one LCG of the UE.

Further, if the DCI is an uplink scheduled DCI (such as DCI format 0_0, DCI format 0_1 or DCI format 0_2), the DCI is also used to indicate uplink transmission resources, such as PUSCH resources.

Optionally, the control information DCI indicating the bearer of the uplink transmission resource and the control information DCI indicating the bearer that the UE triggers BSR reporting may be the same or different. In other words, the uplink transmission resources can be sent separately, which is not specifically limited in this application. Optionally, this implementation may include the following steps:

S911. The base station allocates uplink transmission resources to the UE.

Illustratively, the uplink resources are physical layer resources, such as PUSCH resources. The base station allocates PUSCH resources to the UE through DCI signaling.

For specific implementation methods, reference may be made to step S520 of the above-mentioned method 500. For the sake of brevity, details will not be described again here.

As a possible implementation, the base station can add a 1-bit field to the traditional DCI format to instruct the UE to trigger BSR. When the bit in this field is '1', it is used to instruct the UE to trigger BSR reporting; or when the bit in this field is '0', it is used to instruct the UE not to trigger BSR reporting.

It should be noted that when the bit in this field is '0', the UE does not trigger BSR, but the UE can still trigger BSR due to the other conditions mentioned above. For example, when the conventional BSR triggering conditions in the traditional BSR triggering mechanism are met (for example, a certain LCG has new data arriving, and the priority of this LCG is higher than the priority of other LCGs to be transmitted, or there is no LCG buffer When there is data to be transmitted), the UE can still report the BSR to the base station.

Optionally, the DCI format may be DCI format 0_0, DCI format 0_1, DCI format 0_2 used to indicate uplink transmission, or the DCI format may also be DCI format 1_0, DCI format 1_1, DCI used to indicate downlink transmission. Format 1_2.

As an example and not a limitation, after receiving the DCI indicating to trigger the BSR, the UE will report the BSR at the next transmission time when the BSR can be reported. As an example, when the DCI indicating triggering BSR is an uplink scheduled DCI (for example, DCI format 0_0, or DCI format 0_1, or DCI format 0_2), the UE can report the BSR on the uplink resource scheduled by the DCI. In another example, when the DCI indicating triggering BSR is downlink scheduling DCI, the base station also needs to allocate uplink resources to the UE. Correspondingly, the UE reports the BSR on the allocated uplink resources. That is, the method of triggering BSR through downlink DCI can refer to the above method 500. The difference from the above method 500 is that this implementation method is that the base station triggers BSR reporting through uplink scheduling DCI, rather than triggering the UE to report BSR through MAC CE.

Further, the base station can instruct the UE to trigger BSR reporting of a certain LCG through DCI.

One possible implementation is that since each UE can be allocated up to 8 LCGs, such as LCG0 to LCG7, the base station can indicate these 8 LCGs through a 3-bit field, such as 000 to 111.

For example, when this field bit is '011', it is used to instruct the UE to trigger a BSR report, and the BSR contains the uplink data size of the buffer area of LCG3. Or, when this field bit is '101', it is used to instruct the UE to trigger a BSR report, and the BSR includes the uplink data size of the LCG5 buffer area, etc.

Another possible implementation method is that since the LCG corresponding to the XR video service is semi-statically configured by the base station for the UE through RRC signaling, the UE can be triggered to report the BSR of a certain LCG through RRC signaling and DCI joint indication. . Specifically, the base station can configure the LCG number for the UE that needs to report the BSR through RRC signaling, such as the LCG ID corresponding to the XR video service. After the configuration is completed, the base station can instruct the UE to trigger BSR reporting through DCI. At this time, the DCI can only add a 1-bit field to indicate triggering BSR reporting. When the bit in this field is '1', it is used to instruct the UE to trigger a BSR report; or when the bit in this field is '0', it is used to instruct the UE not to trigger a BSR report.

For example, the base station semi-statically configures the LCG number that needs to report the BSR to 2 for the UE through RRC signaling, and then the base station indicates to the UE at a certain moment (for example, the moment when the UE wants to upload the XR data frame) through the field bit '1' When a BSR report is triggered, the BSR includes the uplink cache data size corresponding to LCG2.

It should be noted that if the base station needs to report the LCG number of the BSR through semi-static configuration, please refer to the above method 500. For the sake of brevity, no further details will be given here.

Further, the base station can also instruct the UE through DCI the specific time to trigger BSR reporting.

As a possible implementation, the base station can add a bit field to the traditional DCI format to indicate the moment when the UE triggers BSR. For example, a 3-bit field has values from ‘000’ to ‘111’.

For example, when the bit value of this field is '000', it is used to indicate that the UE does not trigger BSR reporting; or when the bit value of this field is '010', it is used to indicate that BSR reporting is triggered and the triggering time is late. 2 time slots, or 2 milliseconds, etc. in receiving the DCI.

It should be noted that for the above situation where the DCI instructs the UE to trigger the BSR to report an LCG, the UE will Before receiving the DCI, or after the UE receives the DCI and before sending the BSR, if the UE triggers the BSR report due to other ways, the UE still reports the BSR normally. When there are multiple LCG uplink cache data sizes that need to be reported When, the UE reports the long BSR. Otherwise, a short BSR is reported.

In another possible implementation, the base station can add an additional bit field #2 to the traditional DCI format to indicate the time when the UE triggers BSR. It should be understood that this bit field #2 is independent of the bit field #1 that indicates triggering the BSR reporting of a certain LCG.

For example, the DCI includes bit field #1 and bit field #2. Bit field #1 is used to indicate whether to trigger BSR reporting, or to instruct the UE to trigger BSR reporting of a certain LCG. Bit field #2 is used to indicate the BSR reporting time. . For example, when bit field #1 is '1' and bit field #2 is '010', the UE needs to trigger a BSR report, and the triggering time is later than 2ms after receiving the DCI; or, when bit field #1 is '010', and bit field #2 is '100', the UE needs to trigger a BSR report. The BSR contains the uplink data size of the buffer area of LCG2, and the triggering time is later than 4 slots of receiving the DCI, etc. It should be understood that the above time unit may be milliseconds, time slots, or other time units, and this application does not limit this.

To sum up, the above methods respectively provide implementation methods such as the base station instructing the UE to trigger BSR reporting through DCI, instructing the UE to trigger BSR reporting of a certain LCG through DCI, and instructing the UE to trigger the BSR reporting through DCI at the specific time. The above-mentioned multiple implementation methods can be used individually or in combination, and this application does not specifically limit this.

It should be noted that the above base station instructs the UE to trigger the BSR reporting time through DCI, and instructs the UE to trigger the BSR reporting of a certain LCG through DCI, can be used together to form a new implementation. That is to say, the base station can also instruct the UE through one or more DCIs when to trigger the BSR to report the amount of uplink buffered data corresponding to a certain LCG. For specific implementation methods, please refer to the above. For the sake of brevity, details will not be described here.

S920, the UE sends the BSR MAC CE to the base station on the PUSCH resource.

Correspondingly, the base station receives the BSR MAC CE from the UE.

It should be noted that before sending the BSR MAC CE, the UE needs to determine the size of the uplink cache data carried in the BSR based on the amount of data to be transmitted in the current LCG buffer area, that is, generate a BSR.

A possible implementation method is that the UE sends the BSR MAC CE to the base station when the first condition is met.

Among them, the first condition is that the uplink transmission resources are used for initial transmission; the uplink transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and the BSR MAC CE is triggered by the first message (such as DCI).

It should be understood that the UE accumulates the data amount of uplink data to be transmitted on at least one LCH belonging to the same LCG, and generates a BSR of the LCG for reporting. That is, BSR is reported with LCG as the granularity.

Further, the UE may be configured with multiple LCGs, so the BSR reported by the UE may include the uplink cache size of one or more LCGs. For example, if the UE has more than one LCG buffer area to transmit data, the long BSR is reported, and otherwise the short BSR is reported.

It should be understood that the above implementation method is also applicable to triggering BSR reporting between UE1 and UE2 in the SL scenario. For details, please refer to the above Figure 8, which will not be described again here.

In this implementation, the base station actively triggers the UE to report the BSR through DCI. For example, when the UE wants to upload an XR data frame, it triggers the UE to report the BSR by sending signaling, enabling the BSR to be reported in time with the transmission of the XR data frame. .

It should be understood that the above methods 500, 800 and 900 are actively triggered by the base station through MAC CE signaling or DCI signaling. The UE reports the BSR. Next, taking the interaction between the base station and the UE in the XR video service as an example, the base station provided by this application semi-statically triggers the UE to periodically report BSR through RRC signaling with reference to Figure 10.

Figure 10 is a schematic flowchart of the first cache status report BSR triggering method 1000 provided by an embodiment of the present application. In this implementation, the base station modifies the triggering method of periodic BSR for the UE through RRC signaling based on the traditional triggering method of periodic BSR reporting. As shown in Figure 10, the method specifically includes the following steps.

S1010: The base station sends configuration information #1 (ie, second configuration information) to the UE.

Correspondingly, the UE receives configuration information #1 from the base station.

The configuration information #1 is used to configure the first timer and the first signaling, and the first signaling is used to instruct the UE to trigger BSR reporting.

In one possible implementation, the configuration information includes indication information #A, which is used to indicate the second condition, that is, the uplink transmission resources are used for initial transmission; the uplink transmission resources can accommodate the BSR MAC CE reported by the UE and the The MAC sub-header corresponding to BSR MAC CE; and the first signaling is the first value. The uplink transmission resources are transmission resources allocated by the base station to the UE.

That is to say, the UE can determine whether the traditional periodicBSR-Timer will be restarted (or refreshed) every time the UE reports the BSR based on the second condition.

For example, the configuration information #1 may be RRC configuration signaling, such as BSR-config signaling. This indication information #A is periodicBSRrefresh-r18 signaling (ie, first signaling). Among them, the periodicBSRrefresh-r18 signaling may contain two values: enabled and disabled (ie, the first value). For example, the base station can add periodicBSRrefresh-r18 signaling (first signaling) to BSR-config signaling (configuration information #1). The specific configuration method can be as follows:

Specifically, when periodicBSRrefresh-r18=enabled, it indicates that periodicBSR-Timer will be triggered according to the traditional triggering method (for example, starting or restarting), that is, the restart of periodicBSR-Timer depends on the timeout moment of the first timer, or depends on Whether the UE reports BSR. That is to say, when the periodicBSR-Timer times out, or when the UE reports the BSR, the periodicBSR-Timer is restarted. When periodicBSRrefresh-r18=disabled, it indicates that the triggering of periodicBSR-Timer depends on the timeout moment of the first timer and does not depend on whether the UE is online. Report BSR. That is to say, when the periodicBSR-Timer times out, the UE triggers BSR reporting and restarts the periodicBSR-Timer.

Optionally, the specific configuration of the above periodicBSRrefresh-r18 signaling can also include a value of enabled. In this case, disabled can default to the configuration parameter periodicBSRrefresh-r18 being not configured. For example, periodicBSRrefresh-r18 can be replaced here with: ForbitperiodicBSRtrigger-r18, for example, indicating that when the value is enabled, periodicBSR-Timer will not be reset due to BSR reporting.

It should be understood that in this implementation, the periodicBSR-Timer and the transmission period of the XR data frame need to be synchronized, that is, it is ensured that the opening or restarting of the periodicBSR-Timer is at the same time as the transmission time of the new XR data frame. That is to say, during the transmission of data frame 1 within a certain period, periodicBSR-Timer will not be restarted regardless of whether the BSR is reported due to other trigger conditions (for example, see the traditional trigger mechanism).

Further, the base station can instruct the UE to trigger BSR reporting of a certain LCG through configuration information #1.

In a possible implementation manner, the configuration information #1 includes indication information #B, and the indication information #B is used to indicate the LCG corresponding to the BSR triggered by the UE. For example, the identification information of the LCG (for example, LCG ID or LCG number) is indicated through indication information #B.

For example, the configuration information #1 is BSR-config signaling, and the indication information #B is periodicBSRrefresh-r18 signaling (ie, the second signaling). For example, the base station introduces periodicBSR-LCG-r18 signaling into the BSR-config signaling to indicate that the LCG corresponding to the BSR triggered by the UE is LCG3.

For example, the configuration information #1 is BSR-config signaling, and the indication information #B is periodicBSR-LCGlist-r18 signaling. For example, the base station introduces a periodicBSR-LCGlist-r18 signaling into the BSR-config signaling to indicate that the LCGs corresponding to the BSR triggered by the UE are LCG3 and LCG7.

It should be noted that the LCG indicated by the indication information #B may be an explicit indication. For example, the indication information #B carries the LCG ID or LCG number. If the indication information #B carries LCG3, it means that the BSR reported by the UE contains the buffered data amount of LCG3. If the indication information #B carries bits LCG5 and LCG6, it means that the BSR reported by the UE contains the buffered data amount of LCG5 and LCG6. Alternatively, the LCG indicated by the indication information #B may also be an implicit indication, for example, the LCG is indicated through a 3-bit field. If the indication information #B carries bit "010", it indicates that the BSR reported by the UE includes the buffered data amount of LCG2. If the indication information #B carries bits "100" and "111", it means that the BSR reported by the UE includes the buffered data amount of LCG4 and LCG7. This application does not specifically limit this.

Therefore, based on the implementation method provided above, the UE can trigger BSR reporting of one or more designated LCGs.

In this implementation, if BSR is triggered only when the periodicBSR-Timer times out, the UE can report the cache size of the LCG indicated in periodicBSR-LCG-r18 or periodicBSR-LCGlist-r18; if there are other ways to trigger BSR reporting ( For example, if new transmission data appears on a high-priority logical channel), the BSR can be reported according to the traditional BSR triggering mechanism. It should be understood that these two methods of reporting BSR do not conflict and can be used together.

As an example and not a limitation, the above base station instructs the UE to trigger BSR reporting of a certain LCG through configuration information #1, and instructs the UE to trigger BSR reporting of a certain LCG through configuration information #1, which can be used together to form a new implementation.

A possible implementation method is that the base station can first configure periodicBSRrefresh-r18=disabled (ie, indication information #A) through RRC signaling, so that periodicBSR-Timer is restarted only when it times out; and then through periodicBSR-LCG-r18 or periodicBSR- LCGlist-r18 (ie, indication information #B) configures one or more LCGs included in the BSR reporting triggered by the periodicBSR, that is, enabling the UE to periodically trigger BSR reporting, and further, enabling the UE to Periodically trigger BSR reporting of one or more specified LCGs.

Another possible implementation is to configure periodicBSR-LCG-r18 or periodicBSR-LCGlist-r18 to also support the function of periodicBSRrefresh-r18. For example, when the base station configures periodicBSR-LCG-r18 or periodicBSR-LCGlist-r18 through RRC signaling, periodicBSR-Timer will not restart because the UE reports the BSR, which is similar to implicitly triggering periodicBSRrefresh-r18=disabled.

S1020. When the second condition is met, the UE starts or restarts the first timer and sends the BSR MAC CE to the base station.

It should be noted that when the UE triggers the BSR, padding BSR, regular BSR and/or periodic BSR provided by this application at the same time, the BSR MAC CE is generated according to the regular BSR and/or the periodic BSR; or, when the UE triggers the BSR at the same time, When BSR and filling BSR, UE generates BSR MAC CE based on BSR.

That is to say, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of the present application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

In a possible implementation, the configuration information #1 includes indication information #A.

For example, the indication information #A is used to indicate that BSR reporting is triggered periodically. Among them, the restart of periodicBSR-Timer depends on the timeout time of the first timer, and does not restart (or refresh) with each BSR report. Then, after receiving configuration information #1, the UE triggers BSR reporting each time it uploads a new XR data frame, and restarts the periodicBSR-Timer.

Specifically, taking periodicBSRrefresh-r18=disabled as an example, the third reporting method for triggering BSR provided by the embodiment of the present application will be described in detail with reference to FIG. 11 . As shown in Figure 11, taking the subcarrier spacing (SCS) as 15kHz (each time slot is 1ms) and the time division duplex TDD configuration as 4:1 as an example, assuming that the transmission period of the XR data frame is 15ms, And the periodicBSR-Timer period is the same as the XR frame period, so that the UE can report the BSR and restart the periodicBSR-Timer each time it reports the XR frame.

For example, the UE can transmit XR frame 1 to the base station at U0, report the BSR, and at the same time enable or restart the periodicBSR-Timer. According to the transmission cycle of the above-mentioned XR frame, XR frame 2 will arrive at the logical channel at U4. Due to other reasons (for example, new data to be transmitted on the high-priority logical channel) at U2, the UE can report the BSR again according to traditional trigger conditions. However, because periodicBSRrefresh-r18=disabled, the periodicBSR-Timer will not be reset because it has not timed out, but will continue to count until the periodicBSR-Timer times out at U4. At this time, the transmission of XR frame 1 is completed and XR frame 2 is waiting to be transmitted. Therefore, the UE needs to trigger BSR, report BSR on U4 and transmit XR frame 2 to the base station, and restart periodicBSR-Timer at the same time.

In another possible implementation, the configuration information #1 includes indication information #B.

Exemplarily, the indication information #B includes one or more LCG IDs, such as LCG1 and/or LCG5. Among them, the restart of periodicBSR-Timer depends on the timeout time of the first timer, and does not restart (or refresh) with each BSR report. Then, after receiving configuration information #1, the UE triggers BSR reporting of LCG1 and/or LCG5.

In another possible implementation, the configuration information #1 includes indication information #A and indication information #B.

For example, the indication information #A is used to instruct the UE to periodically trigger BSR reporting, and the indication information #B indicates that the LCGs corresponding to the UE's periodically triggered BSR are LCG3 and LCG7. Among them, the restart of periodicBSR-Timer depends on the timeout time of the first timer, and does not restart (or refresh) with each BSR report. Then, after receiving configuration information #1, the UE triggers BSR periodic reporting of LCG3 and LCG7.

It should be understood that the above implementation method is also applicable to triggering BSR reporting between UE1 and UE2 in the SL scenario. Refer to Figure 8 above, which will not be described again here.

In this implementation, a method for semi-static signaling to configure periodic BSR triggering is provided. By changing the triggering conditions of the current periodic BSR (periodicBSR-Timer), the stability of the BSR triggering period is ensured, and the UE is enabled to simultaneously report the BSR and restart periodicBSR each time it transmits a new XR frame (for example, XR frame 2). -Timer enables the base station to allocate appropriate uplink resources to the UE to improve the utilization of uplink resources in the cell and reduce the transmission delay of uplink XR frame data.

Next, taking the interaction between the base station and the UE in the XR video service as an example, another type of base station semi-statically triggers the UE to periodically report BSR through RRC signaling is described in detail with reference to Figure 12. The difference from the method shown in Figure 10 is that the base station configures a new periodicBSR-Timer-r18 for the UE through RRC configuration signaling, that is, semi-statically configures a constant BSR triggering period.

Figure 12 is a schematic flowchart of the second cache status report BSR triggering method 1200 provided by the embodiment of the present application. As shown in Figure 12, the method specifically includes the following steps.

S1210: The base station sends configuration information #a (ie, third configuration information) to the UE.

Correspondingly, the UE receives the configuration information #a from the base station.

The configuration information #a is used to configure timer #1 (ie, the second timer) and the second duration, and the configuration information #a is used to instruct the UE to trigger a BSR report.

In a possible implementation, the configuration information #a is used to instruct the UE to trigger BSR when timer #1 times out.

For example, the configuration information #1 may be RRC configuration signaling, such as BSR-config signaling. The timer #1 can be periodicBSR-Timer-r18. For example, the base station can add periodicBSR-Timer-r18 (timer #1) in BSR-Config signaling. The specific configuration method can be as follows:

For example, the time unit of timer #1periodicBSR-Timer-r18 may be a subframe, a time slot, a millisecond, etc., which is not limited in this application.

It should be understood that the timer periodicBSR-Timer-r18 and the traditional periodicBSR-Timer are independent of each other and can be configured at the same time.

It should be noted that the restart of periodicBSR-Timer-r18 is synchronized with the transmission cycle of the XR data frame, that is, the restart of periodicBSR-Timer-r18 is periodic. That is, periodicBSR-Timer-r18 will restart only when periodicBSR-Timer-r18 times out.

Optionally, periodicBSR-Timer-r18 can also be BSRtriggerPeriodicity-r18, that is, the base station can configure a constant BSR triggering period through RRC signaling. The time unit of this period can be a time slot, or milliseconds, etc. For example, a constant BSR trigger period is 5ms.

Illustratively, taking the semi-static configuration BSRtriggerPeriodicity-r18 as an example, the fourth reporting method for triggering BSR provided by the embodiment of the present application will be described in detail with reference to FIG. 13 . As shown in Figure 13, taking the subcarrier spacing (SCS) as 15kHz (each time slot is 1ms) and the time division duplex TDD configuration as 4:1 as an example, assuming that the transmission period of the XR data frame is 15ms, And the period of BSRtriggerPeriodicity-r18 is the same as the XR frame period, so that the UE can report the BSR each time it sends an XR frame.

For example, the UE can transmit XR frame 1 to the base station at U0, report the BSR, and enable periodicBSR-Timer and BSRtriggerPeriodicity-r18 at the same time. According to the transmission cycle of the above-mentioned XR frame, XR frame 2 will arrive at the logical channel at U4. Due to other reasons (for example, new data to be transmitted on the high-priority logical channel) at U2, the UE can report the BSR again according to traditional trigger conditions. At this time, periodicBSR-Timer restarts, but since BSRtriggerPeriodicity-r18 is synchronized with the XR frame period, BSRtriggerPeriodicity-r18 will not be reset because it has not timed out, but continues to time until the BSRtriggerPeriodicity-r18 times out at U4. However, the traditional periodicBSR-Timer has not timed out at this time, so it will not be restarted in U4. It should be understood that at U4, XR frame 1 is transmitted and XR frame 2 is to be transmitted. The UE can trigger BSR, report BSR on U4 and continue to transmit XR frame 2 to the base station, while restarting BSRtriggerPeriodicity-r18. And so on.

Further, the base station can instruct the UE to trigger BSR reporting of a certain LCG through configuration information #a.

That is, when timer #1 times out, or every BSRtriggerPeriodicity-r18 time unit, the UE triggers a BSR report of a certain LCG.

In one possible implementation manner, the configuration information #a carries indication information #B, and the indication information #B includes the LCG corresponding to the BSR triggered by the UE. For example, LCG identification information (LCG ID or LCG number). For specific implementation methods, please refer to step S1210 of the above-mentioned method 1200. For the sake of simplicity, details will not be described here.

S1220: When the timing duration of the second timer (timer #1) exceeds the second duration, the UE starts or restarts the second timer, and sends the BSR media access control MAC control element CE to the base station according to the BSR.

Correspondingly, the base station receives the BSR MAC CE from the UE.

It should be noted that when the UE triggers BSR, padding BSR, regular BSR and/or periodic BSR at the same time, the BSR MAC CE is generated according to the regular BSR and/or the periodic BSR; or, when the UE triggers BSR and padding BSR at the same time When, the UE generates the BSR MAC CE based on the BSR.

That is to say, regular BSR and periodic BSR should take priority over padding BSR. In the embodiment of the present application, the priority of BSR triggered by MAC CE takes precedence over padding BSR, but is lower than the priority of regular BSR and/or periodic BSR.

In a possible implementation, the configuration information #a includes timer #1. That is, when timer #1 times out, the UE triggers BSR reporting.

For example, the restart of timer #1 (for example, periodicBSR-Timer-r18) is the same as the transmission period of the XR data frame, for example, 5ms. For example, the UE transmits XR frame 1 to the base station at 1ms, and the transmission ends at 6ms. At this time, timer #1 times out, and the UE immediately restarts timer #2 and continues to transmit XR frame 2 to the base station. And so on.

Optionally, during the transmission process of XR frame 1, BSR reporting may be triggered due to other conditions. The UE can still report BSR according to the traditional BSR triggering mechanism, that is, timer #1periodicBSR-Timer-r18 and traditional periodicBSR- Timer restarts are independent of each other.

In a possible implementation, the configuration information #a includes indication information #B.

Exemplarily, the indication information #B includes one or more LCG IDs, such as LCG2 and/or LCG4. Then when timer #1 times out, or every BSRtriggerPeriodicity-r18 time unit, the UE triggers BSR reporting of LCG2 and/or LCG4.

It should be understood that the above implementation method is also applicable to triggering BSR reporting between UE1 and UE2 in the SL scenario. For details, please refer to the above Figure 8, which will not be described again here.

In this implementation, the base station semi-statically configures a timer #1 independent of the traditional periodicBSR-Timer (for example, periodicBSR-Timer-r18) through RRC signaling, or configures a constant BSR trigger period (for example, BSRtriggerPeriodicity-r18 ), ensure the stability of BSR triggering, and enable the UE to report BSR and restart timer #1 at the same time each time it transmits a new XR frame (for example, XR frame 2), so that the base station allocates appropriate uplink resources to the UE. This improves the utilization of uplink resources in the cell and reduces the transmission delay of uplink XR frame data.

In this way, the base station actively triggers the UE's BSR reporting through MAC CE or DCI, enabling on-time triggering of BSR. In addition, the base station also semi-statically configures the BSR triggering conditions through RRC signaling, and semi-statically configures a constant BSR triggering period to ensure the stability of the BSR triggering period. Further, the base station can also trigger BSR reporting of a specific LCG through dynamic indication or semi-static configuration, and/or dynamically indicate the triggering time of BSR. The method disclosed in this application can ensure that the UE reports the BSR in time when sending new data for each transmission, so as to enable the base station to perform reasonable resource allocation, thereby reducing the waste of air interface resources and reducing the data transmission delay.

It should be noted that the communication methods provided above can be implemented individually or in combination, and this application does not specifically limit this. In addition, the above-mentioned communication methods 500, 800, and 900 can be regarded as a detailed process of the above-mentioned communication method 400. Among them, the related concepts and steps involved in the communication methods 400, 500, 800, 900, 1000 and 1200 can be referred to each other, and some contents will not be repeated in this application.

The above embodiments of the BSR indication/triggering method side of the present application are described in detail with reference to Figures 4 to 13. The above method of obtaining information is mainly introduced from the perspective of interaction between various devices. It can be understood that, in order to implement the above functions, each device includes a corresponding hardware structure and/or software module to perform each function.

Illustratively, FIG. 14 shows a communication device 3000 provided by an embodiment of the present application. As shown in Figure 14, the device 3000 includes a processor 3010 and a transceiver 3020. The processor 3010 and the transceiver 3020 communicate with each other through an internal connection path, and the processor 3010 is used to execute instructions to control the transceiver 3020 to send signals and/or receive signals.

Optionally, the device 3000 may also include a memory 3030, which communicates with the processor 3010 and the transceiver 3020 through internal connection paths. The memory 3030 is used to store instructions, and the processor 3010 can execute the instructions stored in the memory 3030.

In a possible implementation, the apparatus 3000 is used to implement various processes and steps corresponding to the terminal device in the above method embodiment.

In another possible implementation, the apparatus 3000 is used to implement various processes and steps corresponding to the first device (for example, network device) in the above method embodiment.

It should be understood that the device 3000 may be specifically the terminal device or network device in the above embodiment, or may be a terminal device. A chip or system-on-a-chip for a device or network device. Correspondingly, the transceiver 3020 may be the transceiver circuit of the chip, which is not limited here. Specifically, the apparatus 3000 may be used to perform various steps and/or processes corresponding to network equipment or terminal equipment in the above method embodiments.

Optionally, the memory 3030 may include read-only memory and random access memory and provide instructions and data to the processor. A portion of the memory may also include non-volatile random access memory. For example, the memory may also store device type information. The processor 3010 can be used to execute instructions stored in the memory, and when the processor 3010 executes the instructions stored in the memory, the processor 3010 is used to execute each step of the above method embodiment corresponding to the sending end or the receiving end. and/or process.

During the implementation process, each step of the above method can be completed by instructions in the form of hardware integrated logic circuits or software in the processor. The steps of the methods disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware processor for execution, or can be executed by a combination of hardware and software modules in the processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.

It should be noted that the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capabilities. During the implementation process, each step of the above method embodiment can be completed through an integrated logic circuit of hardware in the processor or instructions in the form of software. The above-mentioned processor may be a general-purpose processor, a digital signal processor, an application-specific integrated circuit, a field programmable gate array or other programmable logic device, a discrete gate or transistor logic device, or a discrete hardware component. The processor in the embodiment of the present application can implement or execute the various methods, steps and logical block diagrams disclosed in the embodiment of the present application. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc. The steps of the method disclosed in conjunction with the embodiments of the present application can be directly implemented by a hardware decoding processor, or executed by a combination of hardware and software modules in the decoding processor. The software module can be located in random access memory, flash memory, read-only memory, programmable read-only memory or electrically erasable programmable memory, registers and other mature storage media in this field. The storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.

It can be understood that the memory in the embodiment of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memories. Among them, non-volatile memory can be read-only memory (ROM), programmable ROM (PROM), erasable programmable read-only memory (erasable PROM, EPROM), electrically removable memory. Erase electrically programmable read-only memory (EPROM, EEPROM) or flash memory. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of illustration, but not limitation, many forms of RAM are available, such as static random access memory (SRAM), dynamic random access memory (DRAM), synchronous dynamic random access memory (synchronous DRAM, SDRAM), double data rate synchronous dynamic random access memory (double data rate SDRAM, DDR SDRAM), enhanced synchronous dynamic random access memory (enhanced SDRAM, ESDRAM), synchronous link dynamic random access memory (synchlink DRAM, SLDRAM) ) and direct memory bus random access memory (direct rambus RAM, DR RAM). It should be noted that the memory of the systems and methods described herein is intended to include, but is not limited to, these and any other suitable types of memory.

According to the method provided by the embodiment of the present application, the present application also provides a computer program product. The computer program product includes: computer program code. When the computer program code is run on a computer, it causes the computer to execute the above embodiments. Methods.

According to the method provided by the embodiment of the present application, the present application also provides a computer-readable medium. The computer-readable medium stores program code. When the program code is run on a computer, it causes the computer to execute the above-described embodiments. Methods.

Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments disclosed herein can be implemented with electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution.

Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working processes of the systems, devices and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be described again here.

In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. On the other hand, the coupling or direct coupling or communication connection between each other shown or discussed may be through some interfaces, and the indirect coupling or communication connection of the devices or units may be in electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place, or they may be distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application can be integrated into one processing unit, each unit can exist physically alone, or two or more units can be integrated into one unit.

If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the traditional technology or the part of the technical solution can be embodied in the form of a software product. The computer software product is stored in a storage medium and includes several The instructions are used to cause a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of this application. The aforementioned storage media include: U disk, mobile hard disk, read-only memory, random access memory, magnetic disk or optical disk and other various media that can store program codes.

The above are only specific embodiments of the present application, but the protection scope of the present application is not limited thereto. Any person familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present application. should be covered by the protection scope of this application. Therefore, the protection scope of this application should be subject to the protection scope of the claims.

Claims (28)

1. A cache status report BSR indication method, which is characterized by including:

   The terminal device receives a first message from the first device, the first message is used to instruct the terminal device to trigger the BSR, and the BSR is used to indicate the cache status of the logical channel group LCG of the terminal device;

   The terminal device sends a BSR media access control MAC control element CE to the first device according to the first message.
2. The method of claim 1, further comprising:

   The terminal device receives a second message from the first device, the second message is used to indicate the transmission resources allocated by the first device to the terminal device, and the transmission resources are used to carry the BSR MAC CE.
3. The method according to claim 2, characterized in that the second message is carried in control information, and the control information includes downlink control information DCI or side link control information SCI.
4. The method according to claim 3, characterized in that the control information is also used to carry the first message.
5. The method according to claim 3, characterized in that the first message is carried in MAC CE.
6. The method according to claim 5, characterized in that the MAC sub-header of the MAC CE includes a logical channel identifier LCID;

   Wherein, the terminal device sends BSR MAC CE to the first device according to the first message, including:

   When the value of the LCID is a preset value, the terminal device sends the BSR MAC CE to the first device according to the first message.
7. The method according to any one of claims 1 to 6, characterized in that the first message is also used to indicate at least one logical channel group identification LCG ID.
8. The method according to any one of claims 1 to 6, characterized in that the method further includes:

   The terminal device receives first configuration information from the first device, and the first configuration information is used to configure at least one logical channel group identification LCG ID.
9. The method according to claim 7 or 8, characterized in that the BSR MAC CE includes the cache status of the LCG corresponding to the at least one LCG ID.
10. The method according to any one of claims 2 to 9, characterized in that the terminal device sends the BSR MAC CE to the first device according to the first message, including:

    The terminal device sends the BSR MAC CE to the first device when the first condition is met;

    Among them, the first condition is:

    The transmission resources are used for initial transmission;

    The transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and,

    The BSR MAC CE is triggered by the first message.
11. The method according to any one of claims 1 to 10, characterized in that the first message is also used to indicate a first duration, and the first duration is used to indicate the time of the first moment relative to the second moment. offset, the first moment is the moment when the terminal device triggers the BSR, and the second moment is when the terminal device receives the A moment of news.
12. The method according to any one of claims 1 to 11, characterized in that the method further includes:

    When the terminal device triggers the BSR, filling BSR, regular BSR and/or periodic BSR at the same time, the terminal device generates the BSR MAC CE according to the regular BSR and/or the periodic BSR; or,

    When the terminal device triggers the BSR and the filling BSR at the same time, the terminal device generates the BSR MAC CE according to the BSR.
13. The method according to any one of claims 2 to 12, characterized in that the transmission resources include physical uplink shared channel (PUSCH) resources or physical sidelink shared channel (PSSCH) resources.
14. A cache status report BSR indication method, which is characterized by including:

    The first device sends a first message to the terminal device, the first message is used to instruct the terminal device to trigger the BSR, and the BSR is used to indicate the cache status of the logical channel group LCG of the terminal device;

    The first device receives the BSR media access control MAC control element CE from the terminal device.
15. The method of claim 14, further comprising:

    The first device sends a second message to the terminal device, the second message is used to indicate the transmission resources allocated by the first device to the terminal device, and the transmission resources are used to carry the BSR MAC CE .
16. The method according to claim 15, characterized in that the second message is carried in a control message, and the control information includes downlink control information DCI or side link control information SCI.
17. The method according to any one of claims 14 to 16, characterized in that the method further includes:

    The first device sends first configuration information to the terminal device, where the first configuration information is used to configure at least one logical channel group identifier LCG ID.
18. The method according to any one of claims 15 to 17, characterized in that the first device receives the BSR MAC CE from the terminal device, including:

    When the first condition is met, the first device receives the BSR MAC CE from the terminal device;

    Among them, the first condition is:

    The transmission resources are used for initial transmission;

    The transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and,

    The BSR MAC CE is triggered by the first message.
19. A cache status report BSR triggering method is characterized by including:

    The terminal device receives second configuration information from the first device, the second configuration information is used to configure a first timer and first signaling, and the first signaling is used to instruct the terminal device to trigger the BSR;

    When the second condition is met, the terminal device starts or restarts the first timer, and the terminal device sends a BSR media access control MAC control element CE to the first device;

    Among them, the second condition is:

    Transmission resources are used for initial transmission, and the transmission resources are resources allocated by the first device to the terminal device;

    The transmission resources can accommodate the BSR MAC CE reported by the terminal device and the MAC sub-header corresponding to the BSR MAC CE; and,

    The first signaling is a first value.
20. A cache status report BSR triggering method is characterized by including:

    The first device sends second configuration information to the terminal device, the second configuration information is used to configure the first timer and first signaling, the first signaling is used to instruct the terminal device to trigger the BSR;

    When the second condition is met, the first device receives the BSR media access control MAC control element CE from the terminal device, and the first timer is in a starting or restarting state;

    Wherein, the second condition is:

    Transmission resources are used for initial transmission, and the transmission resources are resources allocated by the first device to the terminal device;

    The transmission resources can accommodate the BSR MAC CE and the MAC sub-header corresponding to the BSR MAC CE; and,

    The first signaling is a first value.
21. The method according to claim 19 or 20, characterized in that the second configuration information also includes second signaling, the second signaling is used to indicate at least one logical channel group identifier LCG ID, the BSR MAC The CE includes the cache status of the logical channel group LCG corresponding to the at least one LCG ID.
22. A cache status report BSR triggering method is characterized by including:

    The terminal device receives third configuration information from the first device, the third configuration information is used to configure a second timer and a second duration, and the third configuration information is used to instruct the terminal device to trigger the BSR;

    When the timing duration of the second timer exceeds the second duration, the terminal device starts or restarts the second timer, and the terminal device sends a message to the first device according to the BSR. BSR media access control MAC control element CE.
23. A cache status report BSR triggering method is characterized by including:

    The first device sends third configuration information to the terminal device, the third configuration information is used to configure a second timer and a second duration, and the third configuration information is used to instruct the terminal device to trigger the BSR;

    When the timing duration of the second timer exceeds the second duration, the first device receives the BSR media access control MAC control unit CE from the terminal device, and the second timer is in Startup or restart status.
24. The method according to claim 22 or 23, characterized in that the third configuration information is also used to indicate at least one logical channel group identification LCG ID, and the BSR MAC CE includes the logic corresponding to the at least one LCG ID. The cache status of the channel group LCG.
25. A communication device, characterized in that it includes: a processor and a memory coupled to the processor, the memory stores a computer program, and when the processor executes the computer program, the communication device causes the communication device to execute as follows: The method of any one of claims 1 to 24.
26. A communication system, characterized in that it includes: a first device and a terminal device, the terminal device is used to perform the method according to any one of claims 1 to 13, 19 or 21, 22 or 24, said The first device is used to perform the method according to any one of claims 14 to 18, 20 or 21, 23 or 24.
27. A computer-readable storage medium, characterized in that a computer program is stored in the computer-readable storage medium, and when the computer program is run on a terminal device, it causes the terminal device to execute claims 1 to 13 and 19 Or the method according to any one of claims 14 to 18, 20 or 21, 23 or when the computer program is run on the first device, causing the first device to execute The method described in any one of 24.
28. A chip, characterized in that it includes: a processor and a memory coupled to the processor, the memory stores a computer program, the chip is located in a terminal device, and when the processor executes the computer program, causing the terminal device to execute the method as described in any one of claims 1 to 13, 19 or 21, 22 or 24; or, the chip is located in the first device, and when the processor executes the computer program when the first device is caused to perform the method as described in any one of claims 14 to 18, 20 or 21, 23 or 24.