Method and apparatus for indicating end of uplink data burst

Abstract

Embodiments of the present application provide a method and apparatus for indicating the end of an uplink data burst. The method comprises: a terminal device generates a padding buffer status report (Padding BSR) with a buffer size of 0 for a first logical channel group (LCG), the Padding BSR being related to the end of a first data burst (EoDB); and the terminal device reports the Padding BSR to a network device. According to the embodiments of the present application, BSR-related enhancement is performed on an MAC layer, a UE implicitly indicates the end of a certain uplink data burst by using the BSR, and then a network side can perform a further operation, such as terminating a wake-up period of a DRX cycle in advance or adjusting a DRX configuration so as to achieve a better energy-saving effect of the UE, or re-allocating subsequent CG resources to other services of the UE or allocating the subsequent CG resources to other UEs so as to improve the network capacity.

Description

Method and apparatus for indicating the end of an uplink data burst Technical Field

[0001] The present application relates to the field of communications. Background Art

[0002] In Release 18, the 3rd Generation Partnership Project (3GPP) began researching enhancements to extended reality (XR) services. XR services refer to all combined real-world and virtual environments and human-computer interactions enabled by computing technology and wearable devices. Application areas include, but are not limited to, entertainment, healthcare, and education. XR services can encompass representative forms such as virtual reality (VR), augmented reality (AR), and mixed reality (MR), as well as hybrid and interdisciplinary areas.

[0003] Virtual reality is a rendered version of a visual and audio scene that is presented to the viewer or user, designed to simulate the visual and auditory sensory stimulation of the real world as naturally as possible as the viewer or user moves within the limitations defined by the application. Augmented reality refers to the provision of additional information or artificially generated items or content overlaid on the user's current environment. Mixed reality is an advanced form of AR, in which some virtual elements are inserted into the physical scene to provide the illusion that these elements are part of the real scene.

[0004] A PDU Set consists of one or more Protocol Data Units (PDUs) that carry the payload of an information unit generated at the application layer (e.g., a frame or video slice for XR and media services). In some embodiments, the application layer requires all PDUs in a PDU Set to use the corresponding information unit. In other embodiments, when some PDUs are lost, the application layer can still recover all or part of the information unit.

[0005] It's important to note that the PDUs used here are application-level PDUs, or PDUs within the session layer, typically IP packets or Ethernet frames. Within the access stratum (AS) protocol stack, each sublayer also has corresponding PDUs, such as the PDCP PDU (Packet Data Convergence Protocol PDU), the RLC PDU (Radio Link Control PDU), and the MAC PDU (Media Access Control PDU).

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

[0007] Summary of the Invention

[0008] The inventors have discovered that to address the processing requirements of PDU Sets, enhancements to the control and user planes are currently being proposed for downlink data transmission. However, how to utilize these enhanced information in downlink transmission requires further standardization and technical implementation. Furthermore, for uplink transmission, no technology currently addresses the integrated packet processing and differentiated processing of PDU Sets, including how to indicate the end of a data burst. A data burst is data generated by an application in a short period of time and consists of one or more PDUs from a PDU Set.

[0009] In response to at least one of the above problems or other similar problems, embodiments of the present application provide a data processing method and apparatus.

[0010] According to one aspect of an embodiment of the present application, there is provided an apparatus for indicating the end of an uplink data burst, configured in a terminal device, the apparatus comprising:

[0011] a generating unit configured to generate a padding buffer status report (Padding BSR) with a buffer size of 0 for a first logical channel group (LCG), the Padding BSR being associated with an end of a first data burst (EoDB);

[0012] A processing unit reports the Padding BSR to a network device.

[0013] According to another aspect of an embodiment of the present application, there is provided an apparatus for indicating the end of an uplink data burst, configured in a terminal device, the apparatus comprising:

[0014] a generating unit configured to generate a regular buffer status report (Regular BSR) with a buffer size of 0 for a third logical channel group (LCG), the Regular BSR being associated with an end of a second data burst (EoDB);

[0015] A processing unit reports the Regular BSR to a network device.

[0016] According to another aspect of the embodiments of the present application, a configuration device is provided, configured on a network device, the device comprising:

[0017] A sending unit, which sends configuration information to the terminal device, wherein the configuration information configures whether the logical channel or LCG reports on the end of the data burst;

[0018] A receiving unit is configured to receive a Padding BSR and / or a Regular BSR from the terminal device.

[0019] One of the beneficial effects of the embodiments of the present application is that: according to the embodiments of the present application, by performing BSR-related enhancements at the MAC (Medium Access Control) layer, the UE implicitly indicates the end of a certain uplink data burst by using BSR (Buffer Status Reporting), so that the network side can perform further operations, such as terminating the wake-up period of the DRX (Discontinuous Reception) cycle in advance, or adjusting the DRX configuration, thereby achieving better UE energy saving effect; or reallocating subsequent CG (Configured Grant) resources to other services of the UE or to other UEs, thereby improving network capacity.

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

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

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

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

[0024] The included drawings are used to provide a further understanding of the embodiments of the present application, which constitute a part of the specification, are used to illustrate the implementation methods of the present application, and together with the text description, explain the principles of the present application. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without inventive work. In the drawings:

[0025] FIG1 is a schematic diagram of a data burst;

[0026] FIG2 is a schematic diagram of a method for indicating the end of an uplink data burst according to an embodiment of the present application;

[0027] Figure 3 is an example of the frame format of the MAC CE of Long BSR and Long Truncated BSR;

[0028] FIG4 is a schematic diagram of a method for indicating the end of an uplink data burst according to an embodiment of the present application;

[0029] FIG5 is a schematic diagram of a configuration method according to an embodiment of the present application;

[0030] FIG6 is a schematic diagram of a device for indicating the end of an uplink data burst according to an embodiment of the present application;

[0031] 7 is another schematic diagram of a device for indicating the end of an uplink data burst according to an embodiment of the present application;

[0032] FIG8 is a schematic diagram of a configuration device according to an embodiment of the present application;

[0033] FIG9 is a schematic diagram of a terminal device according to an embodiment of the present application;

[0034] FIG10 is a schematic diagram of a network device according to an embodiment of the present application. DETAILED DESCRIPTION

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

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

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

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

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

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

[0041] Base stations may include, but are not limited to, NodeBs (NBs), evolved NodeBs (eNodeBs or eNBs), and 5G base stations (gNBs), among others. They may also include remote radio heads (RRHs), remote radio units (RRUs), relays, or low-power nodes (e.g., femto, pico, etc.). The term "base station" may include some or all of their functions, and each base station may provide communication coverage for a specific geographic area. The term "cell" may refer to a base station and / or its coverage area, depending on the context in which the term is used.

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

[0043] Terminal devices may include, but are not limited to, cellular phones, personal digital assistants (PDAs), wireless modems, wireless communication devices, handheld devices, machine-type communication devices, laptop computers, cordless phones, smartphones, smart watches, digital cameras, and IAB-MT, etc.

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

[0045] Currently, 5G technology is researching key issues, solutions, and conclusions to support advanced media services, such as High Data Rate Low Latency (HDRLL) services, AR / VR / XR services, and tactile / multimodal communication services. The goals include:

[0046] 1. Enhancements to support multi-mode services, including:

[0047] - Investigate whether and how to enable applications to provide relevant tactile and multimodal data to users at similar times (e.g., audio, video, and tactile data associated with a specific time), focusing on the need for enhanced policy control (e.g., QoS policy coordination).

[0048] 2. Enhanced network exposure to support interaction between 5GS (5G system) and applications, including:

[0049] - Study whether and how to perform application synchronization and QoS (Quality of Service) policy coordination between multiple UEs or multiple QoS flows per UE, and how to interact between AF and 5GS.

[0050] - Study the exposure of 5GS QoS information (e.g., QoS capabilities) and network conditions to applications to enable fast codec / rate adaptation that helps deliver the desired QoE (e.g., helping alleviate 5GS congestion).

[0051] 3. Study whether and how to implement the following QoS and policy enhancements for XR service and media service transport, including:

[0052] -Study the traffic characteristics of media services that can improve network resource utilization and QoE (Quality of Experience).

[0053] - Enhance the QoS framework to support PDU Set granularity (e.g. video / audio frame / tile, application data unit, control information), where a PDU Set consists of PDUs with the same QoS requirements.

[0054] - Considering the different importance of PDU Sets, it supports differentiated QoS processing. For example, packets belonging to less important PDU Sets can be legally discarded to reduce resource waste.

[0055] - Whether and how to support uplink-downlink transmission coordination to meet the RTT (Round Trip Time) delay requirement between the UE and the N6 termination point of the UPF (User Plane Function).

[0056] - Potential policy enhancements to minimize jitter, focusing on demand provisioning from AF (Application Function) and extensions of PCC (policy and charging control) rules.

[0057] To address the PDU Set processing requirements, enhancements to the control plane and user plane are currently being proposed for downlink data transmission.

[0058] The control plane enhancements include defining the following PDU Set QoS parameters:

[0059] PDU Set Error Rate (PSER) refers to the upper limit of the proportion of non-congestion-related PDU Set losses between the RAN and the UE;

[0060] PDU Set Delay Budget (PSDB) defines the upper limit of the transmission delay that a PDU Set can experience between the UE and the N6 termination of the UPF (that is, the time from the receipt of the first PDU to the successful delivery of the last arriving PDU in the PDU Set);

[0061] PDU Set Integrated Handling Indication (PSIHI) indicates whether the application layer needs all PDUs in order to use the PDU Set.

[0062] In addition, user plane enhancements include the UPF identifying the following information related to PDU Sets: PDU Set sequence number, last PDU marker of the PDU Set, PDU sequence number within the PDU Set, PDU Set size, and PDU Set Importance. Optionally, the core network can also provide the RAN with a downlink End of Data Burst (EoDB) indication, which is placed in the header of the last PDU of the data burst.

[0063] The inventors have discovered that utilizing this enhanced information in downlink transmission requires further standardization and technical implementation. Furthermore, for uplink transmission, no current technology addresses the integrated packet processing and differentiated processing of PDU Sets, including how to indicate the end of a data burst.

[0064] In order to reduce the power consumption of UE, 3GPP has been using DRX technology since the 3G era. The full name of DRX is Discontinuous Reception. DRX in the connected state (Connected DRX, C-DRX) wakes up and sleeps in each DRX cycle. In addition, in order to reduce signaling overhead and the delay caused by signaling, a periodic CG (Configured Grant, also called uplink scheduling-free transmission) can be used for uplink scheduling. Due to the periodicity of XR services, there are also data burst characteristics, and the amount of data in each data burst is variable, and these UE configurations have periodic characteristics, which will cause the configuration of XR services to fail to achieve the effect of energy saving and delay reduction. For example, because the network side does not know whether the data burst has ended, when the data burst of a certain uplink XR service ends, the UE may still be in the DRX wake-up period (ON duration), resulting in poor energy saving. Similarly, after the uplink data burst ends, CG resources may be wasted, thereby reducing transmission efficiency. Therefore, considering the data burst characteristics of XR service traffic, how to indicate the end of the uplink data burst on the network side requires further standardization and technical implementation.

[0065] Figure 1 illustrates the relationship between the PDU, PDU Set, Data Burst, and end of Data Burst for XR services. As shown in Figure 1, each block represents an application layer PDU, which can also be viewed as the corresponding SDU (Service Data Unit) from the application layer PDU to each Layer 2 sublayer, such as the PDCP SDU, RLC SDU, and MAC SDU.

[0066] Various embodiments of the present application are described below with reference to the accompanying drawings. These embodiments are merely exemplary and are not intended to limit the present application.

[0067] In the following description, the terms "if...", "in the event of...", and "when..." are synonymous and interchangeable. Furthermore, because the last PDU of a data burst is also the last PDU in a PDU Set, the end of a data burst can be replaced with the end of each PDU Set in the following description. In other words, the end of a data burst can be replaced with the end of a PDU Set. The basic approach remains unchanged.

[0068] Embodiments of the first aspect

[0069] The present invention provides a method for indicating the end of an uplink data burst, which is described from the perspective of a terminal device. FIG2 is a schematic diagram of the method for indicating the end of an uplink data burst according to an embodiment of the present invention. As shown in FIG2 , the method includes:

[0070] 210: The terminal device generates a padding buffer status report (Padding BSR) with a buffer size of 0 for the first logical channel group (LCG), where the Padding BSR is related to the end of the first data burst (EoDB).

[0071] 220: The terminal device reports the Padding BSR to the network device.

[0072] It is worth noting that FIG2 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG2 above.

[0073] According to the above embodiment, a Padding BSR containing a cache size of 0 is used to report the cache status of a certain LCG, thereby solving the problem of how to indicate the end of the uplink data burst to the network side. No redundant signaling is introduced, signaling overhead is reduced, the data burst characteristics of XR and media services are supported, and UE energy saving and network capacity improvement are achieved.

[0074] Currently, the BSR notifies the network of the amount of data to be sent in the UE's current buffer. The network then allocates uplink resources to the UE based on the amount of data buffered by the UE as reported by the BSR. BSRs are classified into three categories based on their triggering conditions: Regular BSR, Periodic BSR, and Padding BSR. After uplink data packetization is complete, a Padding BSR is triggered when the number of remaining bits is greater than or equal to the size of the BSR MAC CE (Control Element) and its subheader.

[0075] Since the Padding BSR is generated after the uplink data packet is completed, if a certain LCG (logical channel group) has no data to be sent (including the case where the data of the LCG is already completely contained in the assembled MAC PDU), there will be no cache status report for the LCG. However, when the MAC layer (MAC entity) knows that the assembled MAC PDU contains the last MAC SDU of the application layer data burst, it can use a Padding BSR with a cache size of 0 to notify the network side that a certain LCG has no data to be sent and that the MAC PDU contains the last application layer PDU in the data burst.

[0076] In an embodiment of the present application, the MAC layer's perception of the application layer PDU Set and Data Burst may be determined by the UE implementation. For example, a higher layer (e.g., NAS layer, SDAP layer) may transmit information related to the PDU Set and Data Burst corresponding to each MAC SDU to the MAC layer through inter-layer signaling. The present application is not limited thereto. The MAC layer's perception of the application layer PDU Set and Data Burst may also be determined by the MAC layer based on the cache status and data arrival pattern.

[0077] In some implementations of the embodiments of the present application, the related processes of Padding BSR may be enhanced.

[0078] For example, after MAC layer packetization, when constructing the Padding BSR, the Padding BSR includes a cache size field with a value of 0 for a certain LCG, the LCG has no available data to be transmitted, and the MAC PDU to which the Padding BSR belongs includes the last MAC SDU of a data burst (called the first data burst), and the MAC SDU comes from a logical channel in the above-mentioned LCG.

[0079] In the above embodiment, the above LCG can be called an LCG that needs to report a cache size of 0. In the embodiment of the present application, in order to distinguish it, it is called the first LCG.

[0080] In the above embodiment, the last MAC SDU of the first data burst refers to the MAC SDU corresponding to the last PDU in the application layer data burst, or the data last sent by the MAC entity in the data burst.

[0081] In the embodiment of the present application, the Padding BSR can use different formats, including Short BSR, Short Truncated BSR, Long BSR, and Long Truncated BSR, depending on the size of the Padding bits and the number of LCGs for which the cache status needs to be reported. When using Short Truncated BSR or Long Truncated BSR, it is necessary to consider the reporting priority, that is, how to report the cache status of some LCGs.

[0082] In some embodiments, the first LCG is selected from LCGs that need to report a buffer size of 0.

[0083] In some embodiments, the terminal device preferentially reports the cache status of the LCG containing available data to be transmitted. For ease of description, the LCG containing available data to be transmitted is referred to as the second LCG.

[0084] In the above embodiment, the terminal device reports a second BSR for the second LCG (referring to the cache status information for the second LCG in the Padding BSR) to the network device. The second LCG contains available data to be transmitted, and the cache status reporting priority of the second LCG is higher than the cache status reporting priority of the first LCG.

[0085] In the above embodiment, after the cache status information of the second LCG is preferentially selected, the first LCG is selected to report the cache status of the first LCG.

[0086] For example, the terminal device selects in descending order of the priority of the logical channel with the highest priority in each LCG that needs to report a cache size of 0. If the priorities are the same, the terminal device selects in ascending order of the LCG identifier (LCG ID) of the LCG that needs to report a cache size of 0.

[0087] For another example, the terminal device selects in descending order of the logical channel priority that contains the data burst end data during the packet assembly process in each LCG that needs to report a cache size of 0. If the priorities are the same, the terminal device selects in ascending order of the LCG identifier (LCG ID) of the LCG that needs to report a cache size of 0.

[0088] In the above two examples, the logical channel priority can be configured by the network device through RRC signaling. The embodiment of the present application does not limit the specific configuration method, and reference can be made to related technologies.

[0089] In other embodiments, the terminal device compares the priorities of one or more LCGs (or the logical channels containing the end data of the data burst in the LCG) that need to report a cache size of 0 and one or more LCGs (second LCGs) containing available data to be transmitted, and determines which LCG's cache status to report first based on the comparison result. That is, when selecting the LCG that needs to be reported, the logical channels containing the end data of the data burst in the LCG that needs to report a cache size of 0 are regarded as having available data to be transmitted (in fact, they do not, because the end data of the data burst has already been packaged).

[0090] In the above embodiment, if the priority of the highest-priority logical channel in a second LCG is higher than the priority of the highest-priority logical channel in an LCG that needs to report a cache size of 0, the terminal device prioritizes reporting the second BSR for the second LCG; if the priority of the highest-priority logical channel in an LCG that needs to report a cache size of 0 is higher than the priority of the highest-priority logical channel in a second LCG, the terminal device prioritizes reporting the Padding BSR for the LCG that needs to report a cache size of 0; if the highest-priority logical channel in an LCG that needs to report a cache size of 0 has the same priority as the highest-priority logical channel in a second LCG, the terminal device selects the LCG for BSR reporting in ascending order of these LCG identifiers.

[0091] In some embodiments, the Padding BSR may be generated by a MAC entity of the terminal device.

[0092] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the short BSR plus its sub-header length, but less than the long BSR plus its sub-header length; and if, when constructing the above-mentioned Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a cache size of 0 is greater than 1, then if the number of bits of the Padding BSR is equal to the short BSR plus its sub-header length, the terminal device reports a Short Truncated BSR, otherwise it reports a Long Truncated BSR.

[0093] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the long BSR plus its subheader length, the terminal device reports all second LCGs containing available data to be transmitted and all long BSRs corresponding to LCGs whose cache size needs to be reported to be 0.

[0094] In the above embodiment, when reporting a Short Truncated BSR, the terminal device may determine the LCG to report according to the above method, that is, prioritize reporting the cache status of the LCG containing available data to be transmitted, or determine which LCG's cache status to report by performing a priority comparison.

[0095] If the cache status of the LCG containing available data to be transmitted is reported first, the terminal device can select the second LCG corresponding to the logical channel with the highest priority among the logical channels containing available data to be transmitted for BSR reporting; if there is no second LCG containing available data to be transmitted, the terminal device can select the LCG with a cache size of 0 to be reported for BSR reporting.

[0096] If the cache status of which LCG to report is determined by performing a priority comparison, the terminal device can select the LCG corresponding to the logical channel containing available data to be transmitted or the logical channel to which the assembled data burst end data belongs, and the logical channel with the highest priority to report the BSR.

[0097] In the above embodiment, when reporting a Long Truncated BSR, the terminal device may also determine the LCG to report according to the above method. That is, the cache status of the LCG containing available data to be transmitted is reported first, or the cache status of the LCG(s) to be reported is determined by performing a unified priority comparison.

[0098] If the cache status of the LCG containing available data to be transmitted is reported first, the terminal device can select all the second LCGs containing available data to be transmitted for BSR reporting, and then select the LCG that needs to report the cache size of 0 for BSR reporting (if any). The order of selection is to select in descending order of the priority of the logical channel with the highest priority in each LCG that needs to report the cache size of 0. If the priorities are the same, the terminal device selects in ascending order of the LCG identifier (LCG ID) of the LCG that needs to report the cache size of 0.

[0099] If a unified priority comparison is performed to determine which LCG(s) to report their cache status, the terminal device can select LCGs for BSR reporting in descending order of the priority of the logical channel with the highest priority in each LCG (the logical channel may or may not have available data to be transmitted) in the LCG corresponding to the logical channel containing available data to be transmitted or the logical channel to which the assembled data burst end data belongs. If the priorities are the same, the LCGs can be selected for BSR reporting in ascending order of the LCG identifier (LCG ID).

[0100] The following is an example of enhancing the BSR process of TS 38.321 according to the above embodiment, illustrating a case where the buffer status of the LCG containing available data to be transmitted is reported preferentially.

[0101] The following is another example of enhancing the BSR process of TS 38.321 according to the above embodiment, illustrating a case where a unified priority comparison is performed to determine which LCG(s) of cache status to report.

[0102] FIG3 is an example of the frame format of the MAC CE of the Long BSR and the Long Truncated BSR. As shown in FIG3 , the first byte consists of a bit field LCGi, where i ranges from 0 to 7, corresponding to 8 LCGs.

[0103] In the example of Figure 3, for a Long Truncated BSR, the LCGi field indicates whether the i-th LCG (LCGi) has available data or whether the end of a data burst from the LCG (i.e., a logical channel in the LCG) is assembled in the MAC PDU. LCGi is set to 1 to indicate that LCGi has available data or that the end of a data burst from LCGi is assembled in the MAC PDU containing the Long Truncated BSR (if the corresponding buffer size field is 0). LCGi is set to 0 to indicate that LCGi has no available data.

[0104] In the example of FIG3 , in some embodiments, LCGi is set to 1, and the buffer size field corresponding to LCGi in the frame format of the Long Truncated BSR is 0, indicating that the end data of the data burst from LCGi is assembled in the MAC PDU containing the Long Truncated BSR.

[0105] In this embodiment of the present application, after receiving the Padding BSR MAC CE, the network side can determine which LCG's XR service has ended the current data burst by identifying the LCG with a cache size of 0, thereby optimizing scheduling on the corresponding CG PUSCH (Physical Uplink Shared Channel) occasion (time-frequency resources), reallocating CG resources, and improving network capacity. DRX adjustments can also be made to notify the UE to enter the sleep period early to achieve energy saving effects.

[0106] In some embodiments, the network device may further configure a certain logical channel or LCG for the terminal device to determine whether to report on the end of a data burst.

[0107] In the above embodiment, the terminal device receives configuration information from the network device, where the configuration information configures whether the logical channel or LCG reports on the end of the data burst.

[0108] In the above embodiment, the configuration information may be included in an RRCReconfiguration message. That is, the network device may perform the above configuration via the RRCReconfiguration message.

[0109] For example, if the configuration is for a logical channel, a configuration field (called the first configuration field) can be added to the LogicalChannelConfig IE (Information Element) in the RRCReconfiguration message. The first configuration field is used to indicate whether the current logical channel supports reporting information about the end of the data burst, for example, whether to report the Padding BSR of the LCG to which the logical channel belongs when the data burst of the logical channel ends.

[0110] In the above example, the first configuration field can be of enumeration type (value is true), and as long as it is configured, it is considered that the logical channel supports reporting the information of the end of the data burst; it can also be of Boolean type (true or false).

[0111] For another example, if the configuration is for a logical channel group, an IE (called the first IE) can be added to the RRCReconfiguration message, such as LCGConfig IE. A configuration field (called the second configuration field) can be added to the first IE. The second configuration field is used to indicate whether the current LCG supports reporting information about the end of the data burst, that is, whether to report the Padding BSR about the LCG when the data burst belonging to the LCG ends.

[0112] In the above example, the second configuration field can be of enumeration type (value is true). Once configured, it is considered that the logical channel group supports reporting the information of the end of the data burst; it can also be of Boolean type (true or false).

[0113] In some other implementations of the embodiments of the present application, the terminal device may use a Padding BSR with a cache size of 0 when the MAC entity has no available data.

[0114] For example, the terminal device reports the Padding BSR when the first data burst ends and all LCGs have no available data to be transmitted.

[0115] In the above embodiment, only UE energy saving is considered, so it is only necessary to report a Padding BSR containing a buffer size of 0 when a data burst ends and all LCGs have no available data to be transmitted. In this way, the network side can make the UE enter the sleep state directly.

[0116] In the above embodiment, if multiple LCGs have data bursts ended when assembling the MAC PDU to which the Padding BSR belongs, the terminal device can arbitrarily select one of the LCGs to report the BSR (the corresponding cache size is 0). The network side can therefore know that all data bursts have ended and there is no other available data to be transmitted. The present application is not limited to this. The terminal device can also report the cache status of all LCGs (the cache size is 0), or the terminal device can further indicate the above situation to the network side (that is, there is no other available data to be transmitted), and so on.

[0117] In some embodiments, the Padding BSR may be generated by a MAC entity of the terminal device.

[0118] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length; and if, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a cache size of 0 is less than or equal to 1, the terminal device reports the short BSR.

[0119] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the long BSR plus its sub-header length, the terminal device reports the Long BSR.

[0120] In the above embodiment, when the terminal device reports the short BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of an LCG, then the short BSR includes an LCG identifier and a cache size field with a value of 0.

[0121] In the above embodiment, when reporting a Long BSR, the terminal device may report a long BSR including all LCGs containing available data to be transmitted. If all LCGs do not have available data to be transmitted, and the assembled MAC PDU includes one or more MAC SDUs that end a data burst, and the MAC SDUs are from a logical channel (one or more LCGs), the terminal device sets the LCGi corresponding to the LCG in the long BSR to 1 and sets its cache size field to 0.

[0122] The following is an example of enhancing the BSR process of TS 38.321 according to the above embodiment.

[0123] For another example, the terminal device reports the above-mentioned Padding BSR when the first data burst ends and all logical channels that are not configured as configuredGrantType1Allowed have no available data to be transmitted.

[0124] In the above embodiment, if it is considered that the uplink service configured as Type 1 CG does not affect the DRX configuration, then it is only necessary to report the Padding BSR with a buffer size of 0 when the data burst ends and all logical channels that are not configured as configuredGrantType1Allowed (allowing the first type of configuration grant) have no available data to be transmitted.

[0125] In the above embodiment, the Padding BSR may be generated by the MAC entity of the terminal device.

[0126] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length; and if, when constructing the above-mentioned Padding BSR, the number of second LCGs containing available data to be transmitted is greater than 1, then the terminal device reports a Short Truncated BSR when the number of bits of the Padding BSR is equal to the short BSR plus its subheader length; otherwise, it reports a Long Truncated BSR; otherwise, if, when constructing the above-mentioned Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs whose cache size needs to be reported is less than or equal to 1, then the terminal device reports a short BSR.

[0127] In the above embodiment, if the number of bits of the above Padding BSR is greater than or equal to the long BSR plus its sub-header length, the terminal device reports the Long BSR.

[0128] In the above embodiment, when the terminal device reports the Long Truncated BSR, after reporting all the second LCGs containing available data to be transmitted, if there is still space, and all the logical channels containing available data to be transmitted are configured as configuredGrantType1Allowed, and the assembled MAC PDU contains a MAC SDU that ends the data burst, and the MAC SDU comes from the logical channel of a certain LCG, then the above Long Truncated BSR includes the identifier of the LCG and a cache size field with a value of 0.

[0129] In the above embodiment, when the terminal device reports the short BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from the logical channel of a certain LCG, then the above Short BSR contains the identifier of the LCG and a cache size field with a value of 0.

[0130] In the above embodiment, when reporting a Long BSR, the terminal device may report a Long BSR including all LCGs containing available data to be transmitted. If all logical channels containing available data to be transmitted are configured as configuredGrantType1Allowed, and the assembled MAC PDU includes a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of a certain LCG, then the LCGi corresponding to the LCG is set to 1, and the buffer size field corresponding to the LCG is set to 0.

[0131] The following is an example of enhancing the BSR process of TS 38.321 according to the above embodiment.

[0132] In some further implementations of the embodiments of the present application, a Padding BSR with a buffer size of 0 is used, and the triggering condition of the Padding BSR can be enhanced.

[0133] When a MAC PDU containing the end of a data burst is sent, there may not be enough bits to include the Padding BSR, or the Padding PSR may use a truncated format, resulting in the buffer size of some LCGs not being reported. These unreported LCGs may contain the end of the data burst. As a result, the network side cannot obtain the end of the data burst indication and cannot perform UE energy saving and other related configurations in a timely manner.

[0134] To address the above problem, when assembling (or sending) a MAC PDU containing the end of a data burst, a Padding BSR related to the end of the data burst can be triggered, and LCG identifiers corresponding to the LCG containing the end of the data burst can be recorded or associated.

[0135] As previously mentioned, when a Padding BSR related to the end of a data burst is constructed, it may include an LCG identifier associated with no available data to be transmitted and a buffer size of 0. In addition, when a BSR containing an associated LCG is reported, the Padding BSR related to the end of a data burst corresponding to the LCG may be canceled.

[0136] That is to say, if the end of a data burst is included in the packet assembly, the Padding BSR related to the end of the data burst will be triggered, along with the associated LCG identifier. If the Padding BSR is included in the packet assembly and all associated LCGs and their cache sizes are included in the Padding BSR, then the Padding BSR related to the end of the data burst triggered (after the packet assembly or after the Padding BSR MAC CE is sent) will be cancelled. If only some of the associated LCGs are reported (for example, a truncated BSR format is used), then only the associated LCG identifiers corresponding to the reported LCGs will be cancelled. If there is a Padding BSR in subsequent packet assembly, the BSRs corresponding to the LCGs that have not been cancelled will continue to be included until the BSRs corresponding to all associated LCGs are reported.

[0137] Based on the above considerations, in some embodiments, when the MAC PDU containing the end of the first data burst is assembled, the Padding BSR is triggered; wherein the Padding BSR is associated with the LCG to which the logical channel containing the end of the first data burst belongs.

[0138] For example, for an activated cell group, when a MAC PDU containing the end of a data burst is assembled, a Padding BSR related to the end of the data burst is triggered, which is associated with the LCG (identifier) ​​to which the logical channel containing the end of the data burst belongs. It can also be considered that the Padding BSR related to the end of the data burst is triggered by the LCG containing the end of the data burst.

[0139] In the above embodiment, except for the Padding BSR associated with the end of a data burst, all triggered BSRs are canceled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader. In addition, the Padding BSR associated with the end of the first data burst associated with a certain LCG needs to be canceled when the BSR for that LCG is reported.

[0140] In the above embodiment, the specific process of generating the Padding BSR is the same as the above, except that the LCG that needs to report a buffer size of 0 means that the LCG has triggered a Padding BSR related to the end of a data burst and has not been canceled.

[0141] Based on the above considerations, in other embodiments, when a MAC PDU including the end of the first data burst is assembled, the Padding BSR is triggered; wherein the Padding BSR is associated with the logical channel including the end of the first data burst.

[0142] For example, for an activated cell group, when a MAC PDU containing the end of a data burst is assembled, a Padding BSR related to the end of the data burst is triggered, which is associated with the logical channel (identifier) ​​containing the end of the data burst. It can also be considered that the Padding BSR related to the end of the data burst is triggered by the logical channel containing the end of the data burst.

[0143] In the above embodiment, if an LCG contains multiple logical channels containing data burst ends, only one of these logical channels, such as the logical channel with the highest priority, is associated. However, the present application is not limited thereto, and multiple channels may also be associated.

[0144] In the above embodiment, except for the Padding BSR associated with the end of a data burst, all triggered BSRs can be canceled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader. In addition, the Padding BSR associated with the end of a data burst associated with a logical channel needs to be canceled when the BSR of the LCG to which the logical channel belongs is reported.

[0145] In the above embodiment, the specific process of generating the Padding BSR is the same as the above, except that the LCG that needs to report a buffer size of 0 means that a logical channel in the LCG triggers a Padding BSR related to the end of a data burst and is not canceled.

[0146] In some further implementations of the embodiments of the present application, the terminal device may use a Regular BSR containing a buffer size value of 0 when the Padding BSR is insufficient.

[0147] When a MAC PDU containing the end of a data burst is sent or assembled, there may not be extra bits to include the Padding BSR, or the Padding PSR uses a truncated format, resulting in the buffer size of some LCGs not being reported. If these unreported LCGs contain the end of a data burst, a data burst end-related Regular BSR is triggered, containing the LCG identifier and a buffer size of 0. These LCG identifiers correspond to the LCGs containing the end of the data burst and their buffer sizes have not been reported.

[0148] In addition, when a Regular BSR related to the end of a data burst is constructed, the associated LCG identifier with no available data to be transmitted and a buffer size of 0 are included. The LCG contains a logical channel that has sent a data burst end, and the buffer size of 0 in the LCG has not been reported by the Padding BSR.

[0149] Based on the above considerations, in some embodiments, when the Padding BSR is insufficient, the terminal device generates a regular buffer status report (Regular BSR) with a cache size of 0 for the third logical channel group (LCG), and the Regular BSR is related to the end of the second data burst (EoDB); the terminal device reports the Regular BSR to the network device.

[0150] In some embodiments, for an activated cell group (not limited thereto), when a MAC PDU containing the end of a data burst from an LCG is assembled, if there are no padding bits available for the Padding BSR, or the Padding BSR is insufficient to accommodate all buffer size fields with a value of 0, the above-mentioned Regular BSR is triggered.

[0151] In the above embodiment, it can be considered that the Regular BSR related to the data burst is triggered by the unreported LCG with a buffer size of 0. That is, the Regular BSR is triggered by the third LCG, which includes the end of the data burst and whose buffer size has not been reported.

[0152] In the above embodiment, except for the above Regular BSR related to the end of the second data burst, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader.

[0153] In some embodiments, the above-mentioned Regular BSR can be generated by the MAC entity of the terminal device.

[0154] In the above embodiment, when the MAC entity of the terminal device generates the above-mentioned Regular BSR, if the sum of the number of second LCGs containing available data to be transmitted and the number of third LCGs containing Regular BSRs related to the end of the second data burst is greater than 1, then the terminal device can report Long BSR for all second LCGs containing available data to be transmitted and all third LCGs that triggered the above-mentioned Regular BSR due to the end of the second data burst.

[0155] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0156] According to the method of the embodiment of the present application, the problem of how to indicate the end of the uplink data burst to the network side is solved, no redundant signaling is introduced, signaling overhead is reduced, the data burst characteristics of XR and media services are supported, and UE energy saving and network capacity improvement are achieved.

[0157] Embodiments of the second aspect

[0158] An embodiment of the present application provides a method for indicating the end of an uplink data burst, which is described from the perspective of a terminal device.

[0159] FIG4 is a schematic diagram of a method for indicating the end of an uplink data burst according to an embodiment of the present application. Referring to FIG4 , the method includes:

[0160] 410: The terminal device generates a regular buffer status report (Regular BSR) with a buffer size of 0 for the third logical channel group (LCG), where the Regular BSR is associated with an end of data burst (EoDB);

[0161] 420: The terminal device reports the Regular BSR to the network device.

[0162] It is worth noting that FIG4 above only schematically illustrates an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above content, and are not limited to the description of FIG4 above.

[0163] According to the above embodiment, unlike the embodiment of the first aspect, the embodiment of the present application directly uses a Regular BSR containing a cache size value of 0 to report the cache status of a certain LCG, thereby solving the problem of how to indicate the end of the uplink data burst to the network side, without introducing redundant signaling, reducing signaling overhead, supporting the data burst characteristics of XR and media services, and achieving UE energy saving and network capacity improvement.

[0164] Currently, in the process of logical channel prioritization (LCP) performed by the MAC entity, when a MAC SDU containing the end of a data burst is in the buffer of a certain logical channel, a Regular BSR related to the end of the data burst is triggered.

[0165] If the MAC SDU in the buffer that ends the data burst is not assembled into the next MAC PDU containing the Regular BSR MAC CE (due to priority reasons, limited uplink resources, etc.), then when the Regular BSR associated with the end of the data burst is assembled, the Regular BSR will not be canceled (different from the existing Regular BSR cancellation technology). In other words, the end of the data burst is still in the buffer and has not been sent out, so the Regular BSR is still triggered and waits for the next uplink authorization to be assembled.

[0166] Based on the above considerations, in some embodiments, for an activated cell group (not limited thereto), when the uplink data of a logical channel belonging to a certain LCG becomes available to the MAC entity and the uplink data includes the end of the above-mentioned second data burst, the above-mentioned Regular BSR is triggered.

[0167] In the above embodiment, it can be considered that the Regular BSR related to the end of the data burst is triggered by the logical channel or the LCG.

[0168] In some embodiments, except for the above-mentioned Regular BSR related to the end of the second data burst, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader.

[0169] In some embodiments, except for the above-mentioned Regular BSR related to the end of the second data burst, all BSRs triggered before MAC PDU packetization are canceled when a MAC PDU including a BSR MAC CE is sent.

[0170] In the above embodiment, the BSR includes the buffer status up to and including the last event that triggers the BSR before the MAC PDU is assembled. The BSR may be a Long BSR, an Extended Long BSR, a Short BSR, or an Extended Short BSR, but the present application is not limited thereto.

[0171] In some embodiments, the Regular BSR associated with the end of the second data burst is cancelled when a MAC PDU is sent and the MAC PDU includes identification information of the LCG that triggers the Regular BSR and a BSR with a buffer size of 0.

[0172] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0173] According to the method of the embodiment of the present application, the problem of how to indicate the end of the uplink data burst to the network side is solved, no redundant signaling is introduced, signaling overhead is reduced, the data burst characteristics of XR and media services are supported, and UE energy saving and network capacity improvement are achieved.

[0174] Embodiments of the third aspect

[0175] The embodiment of the present application provides a configuration method, which is described from the perspective of a network device. The contents that are the same as those in the embodiment of the first aspect and the embodiment of the second aspect will not be repeated.

[0176] FIG5 is a schematic diagram of a configuration method according to an embodiment of the present application. As shown in FIG5 , the method includes:

[0177] 510: The network device sends configuration information to the terminal device, where the configuration information configures whether the logical channel or LCG reports the end of the data burst.

[0178] 520: The network device receives a Padding BSR and / or a Regular BSR from the terminal device.

[0179] It is worth noting that FIG5 above is merely a schematic illustration of an embodiment of the present application, and the present application is not limited thereto. For example, the execution order of the various operations may be appropriately adjusted, and other operations may be added or some operations may be reduced. Those skilled in the art may make appropriate modifications based on the above description, and are not limited to the description of FIG5 above.

[0180] According to the above embodiment, after receiving a Padding BSR and / or Regular BSR, the network device can determine which LCG's XR service has ended its current data burst by identifying the LCG with a buffer size of 0. This allows the network device to optimize scheduling on the corresponding CG PUSCH occasion, reallocate CG resources, and improve network capacity. The network device can also adjust DRX to notify the UE to enter a sleep period early, thereby achieving energy conservation.

[0181] In some embodiments, the configuration information is included in an RRCReconfiguration message. That is, the network device can perform the configuration via the RRCReconfiguration message.

[0182] If the configuration is for a logical channel, a first configuration field can be added to the LogicalChannelConfig IE in the RRCReconfiguration message. The first configuration field is used to indicate whether the current logical channel (this logical channel) supports reporting the end information of the data burst, that is, when the data burst of the logical channel ends, whether to report the Padding BSR, which contains the corresponding LCG identification information and the cache size is 0.

[0183] If the configuration is for a logical channel group, a first IE can be added to the RRCReconfiguration message, such as LCGConfig IE. A second configuration field is added to the first IE. The second configuration field is used to indicate whether this LCG supports reporting the end information of the data burst, that is, when the data burst belonging to the LCG ends, whether to report the Padding BSR, which includes the LCG identification information and the cache size of 0.

[0184] In the above embodiment, the network device can determine, based on the above Padding BSR and / or Regular BSR, by identifying the LCG with a buffer size of 0, to which LCG the XR service has ended the current data burst.

[0185] The above embodiments are merely exemplary of the present invention, but the present invention is not limited thereto. Appropriate modifications may be made based on the above embodiments. For example, the above embodiments may be used alone, or one or more of the above embodiments may be combined.

[0186] According to the method of the embodiment of the present application, the network equipment can perform scheduling optimization on the corresponding CG PUSCH occasion, reallocate CG resources, and improve network capacity. It can also adjust DRX and notify the UE to enter the sleep period in advance to achieve energy saving.

[0187] Embodiments of the fourth aspect

[0188] An embodiment of the present application provides a device for indicating the end of an uplink data burst.

[0189] FIG6 is a schematic diagram of an apparatus for indicating the end of an uplink data burst according to an embodiment of the present application. The apparatus may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. Since the principle of solving the problem of the apparatus is the same as that of the embodiment of the first aspect, its specific implementation can refer to the implementation of the method of the embodiment of the first aspect, and the same content will not be repeated here.

[0190] As shown in FIG6 , the apparatus 600 for indicating the end of an uplink data burst includes:

[0191] a generating unit 610 for generating a padding buffer status report (Padding BSR) with a buffer size of 0 for a first logical channel group (LCG), the Padding BSR being associated with an end of data burst (EoDB);

[0192] The processing unit 620 reports the Padding BSR to the network device.

[0193] In some embodiments, the Padding BSR includes a cache size field with a value of 0 for the first LCG, and the first LCG has no available data to be transmitted. The MAC PDU to which the Padding BSR belongs includes the last MAC SDU of the first data burst, and the MAC SDU comes from a logical channel in the first LCG.

[0194] In the above embodiment, the last MAC SDU of the first data burst may refer to:

[0195] The MAC SDU corresponding to the last PDU in the application layer data burst, or

[0196] The last data sent by the MAC entity in an application layer data burst.

[0197] In the above embodiment, the first LCG is selected from LCGs that need to report a buffer size of 0.

[0198] In some embodiments, the processing unit 620 further reports a second BSR for a second LCG to the network device, where the second LCG contains available data to be transmitted, and the cache status reporting priority of the second LCG is higher than the cache status reporting priority of the first LCG.

[0199] In the above embodiment, the processing unit 620 can select in descending order of the priority of the logical channel with the highest priority in each LCG that needs to report a cache size of 0, and if the priorities are the same, select in ascending order of the LCG identifier of the LCG that needs to report a cache size of 0; or, the processing unit 620 can select in descending order of the priority of the logical channel that contains the end data of the data burst during the packet assembly process in each LCG that needs to report a cache size of 0, and if the priorities are the same, select in ascending order of the LCG identifier of the LCG that needs to report a cache size of 0.

[0200] In some embodiments, the processing unit 620 also compares the priorities of the LCG that needs to report a cache size of 0 and the second LCG containing available data to be transmitted; when the priority of the highest-priority logical channel in the second LCG is higher than the priority of the highest-priority logical channel in the LCG that needs to report a cache size of 0, the second BSR for the second LCG is reported first; when the priority of the highest-priority logical channel in the LCG that needs to report a cache size of 0 is higher than the priority of the highest-priority logical channel in the second LCG, the Padding BSR for the LCG that needs to report a cache size of 0 is reported first; when the priorities of the highest-priority logical channel in the LCG that needs to report a cache size of 0 and the highest-priority logical channel in the second LCG are the same, the LCG is selected in ascending order of the LCG identifier for BSR reporting.

[0201] In the aforementioned embodiments, the generating unit 610 may be included in the MAC entity of the terminal device, that is, the Padding BSR is generated by the MAC entity of the terminal device.

[0202] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length; and if, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a cache size of 0 is greater than 1, then if the number of bits of the Padding BSR is equal to the short BSR plus its subheader length, the processing unit 620 reports a Short Truncated BSR, otherwise it reports a Long Truncated BSR; if the number of bits of the Padding BSR is greater than or equal to the long BSR plus its subheader length, the processing unit 620 reports all second LCGs containing available data to be transmitted and all long BSRs corresponding to LCGs that need to report a cache size of 0.

[0203] In the above embodiment, the processing unit 620 reports the Short Truncated BSR, which may include:

[0204] Select the second LCG corresponding to the logical channel with the highest priority among the logical channels containing available data to be transmitted to report the BSR; if there is no second LCG containing available data to be transmitted, the terminal device selects the LCG with a buffer size of 0 to report the BSR; or,

[0205] The LCG corresponding to the logical channel with available data to be transmitted or the logical channel to which the assembled data burst end data belongs and the logical channel with the highest priority is selected for BSR reporting.

[0206] In the above embodiment, the processing unit 620 reports the Long Truncated BSR, which may include:

[0207] After selecting the second LCG corresponding to the logical channel with the highest priority among all logical channels containing available data to be transmitted to report the BSR, select the LCG that needs to report a buffer size of 0 to report the BSR; or,

[0208] In the LCG corresponding to the logical channel containing available data to be transmitted or the logical channel to which the assembled data burst end data belongs, the LCG is selected for BSR reporting in descending order of the priority of the logical channel with the highest priority in each LCG. If the priorities are the same, the LCG is selected for BSR reporting in ascending order of the LCG identifier.

[0209] In the above embodiment, one byte in the frame format of the Long Truncated BSR may consist of a bit field LCGi, where i ranges from 0 to 7, and the LCGi field indicates whether the i-th LCG has available data or whether the end data in the data burst has been assembled; LCGi is set to 1 to indicate that LCG i has available data, or that the end data of the data burst from the LCG i has been assembled in the MAC PDU containing the Long Truncated BSR; LCGi is set to 0 to indicate that LCG i has no available data.

[0210] In some embodiments, LCGi is set to 1, and the buffer size field corresponding to LCGi in the frame format of the Long Truncated BSR is 0, indicating that the end data of the data burst from LCG i is assembled in the MAC PDU containing the Long Truncated BSR.

[0211] In some embodiments, as shown in FIG6 , the apparatus 600 further includes:

[0212] The receiving unit 630 receives configuration information sent by the network device, where the configuration information configures whether the logical channel or LCG reports on the end of the data burst.

[0213] In some embodiments, the configuration information is included in an RRCReconfiguration message.

[0214] For example, the LogicalChannelConfig IE in the RRCReconfiguration message includes a first configuration field, and the first configuration field is used to indicate whether the current logical channel supports reporting of the data burst end information.

[0215] For another example, the RRCReconfiguration message includes a first IE, the first IE includes a second configuration field, and the second configuration field is used to indicate whether the current LCG supports reporting of the data burst end information.

[0216] In some embodiments, the processing unit 620 reports the Padding BSR when the first data burst ends and all LCGs have no available data to be transmitted.

[0217] In the above embodiment, the generating unit 610 may also be included in the MAC entity of the terminal device, that is, the MAC entity of the terminal device generates the above Padding BSR.

[0218] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length; and if, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a buffer size of 0 is less than or equal to 1, the processing unit 620 reports the short BSR; if the number of bits of the Padding BSR is greater than or equal to the long BSR plus its subheader length, the processing unit 620 reports the long BSR.

[0219] In the above embodiment, when the processing unit 620 reports the short BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of an LCG, then the short BSR includes the LCG identifier and a cache size field with a value of 0.

[0220] In the above embodiment, when the processing unit 620 reports the Long BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains one or more MAC SDUs that end a data burst, and the MAC SDUs come from the logical channels of one or more LCGs, then the LCGi corresponding to the LCG in the long BSR is set to 1, and its cache size field is set to 0.

[0221] In some embodiments, the processing unit 620 reports the Padding BSR when the first data burst ends and all logical channels that are not configured as configuredGrantType1Allowed have no available data to be transmitted.

[0222] In the above embodiment, the generating unit 610 may be included in the MAC entity of the terminal device, that is, the Padding BSR is generated by the MAC entity of the terminal device.

[0223] In the above embodiment, if the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length; and if, when constructing the Padding BSR, the number of second LCGs containing available data to be transmitted is greater than 1, then the processing unit 620 reports a Short Truncated BSR if the number of bits of the Padding BSR is equal to the short BSR plus its subheader length; otherwise, it reports a Long Truncated BSR; otherwise, if, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a buffer size of 0 is less than or equal to 1, then the processing unit 620 reports a Short BSR; if the number of bits of the Padding BSR is greater than or equal to the long BSR plus its subheader length, then the processing unit 620 reports a Long BSR.

[0224] In the above embodiment, when the processing unit 620 reports the Long Truncated BSR, after reporting all the second LCGs containing available data to be transmitted, if there is still space and all the logical channels containing available data to be transmitted are configured as configuredGrantType1Allowed, and the assembled MAC PDU contains a MAC SDU that ends the data burst, and the MAC SDU comes from the logical channel of an LCG, then the Long Truncated BSR includes the identifier of the above LCG and a cache size field with a value of 0.

[0225] In the above embodiment, when the processing unit 620 reports the short BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of an LCG, then the Short BSR includes the identifier of the above LCG and a cache size field with a value of 0.

[0226] In the above embodiment, when the processing unit 620 reports the Long BSR, if all logical channels containing available data to be transmitted are configured as configuredGrantType1Allowed, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from the logical channel of an LCG, then the LCGi corresponding to the LCG is set to 1, and the cache size field corresponding to the LCG is set to 0.

[0227] In some embodiments, when a MAC PDU containing the end of a first data burst is assembled, a Padding BSR is triggered; the Padding BSR is associated with the LCG to which the logical channel containing the end of the first data burst belongs.

[0228] In the above embodiment, optionally, except for the Padding BSR, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader.

[0229] In the above embodiment, optionally, the triggered Padding BSR associated with the end of the first data burst associated with an LCG is cancelled after the BSR of the LCG is reported.

[0230] In the above embodiment, optionally, the first LCG triggers a Padding BSR related to the end of a data burst and is not canceled.

[0231] In some embodiments, a Padding BSR is triggered when a MAC PDU containing the end of a first data burst is assembled; the Padding BSR is associated with the logical channel containing the end of the first data burst.

[0232] In the above embodiment, optionally, the Padding BSR associated with the end of the first data burst associated with a logical channel that is triggered is cancelled after the BSR of the LCG to which the logical channel belongs is reported.

[0233] In the above embodiment, optionally, a logical channel in the first LCG triggers a Padding BSR related to the end of a data burst and is not canceled.

[0234] In some embodiments, when the Padding BSR is insufficient, the generation unit 610 generates a regular buffer status report (Regular BSR) with a cache size of 0 for the third logical channel group (LCG), and the Regular BSR is related to the end of the second data burst (EoDB); the processing unit 620 reports the above-mentioned Regular BSR to the network device.

[0235] In the above embodiment, optionally, when a MAC PDU containing the end of a data burst from an LCG is assembled, if there are no padding bits available for the Padding BSR or the Padding BSR is insufficient to accommodate all buffer size fields with a value of 0, the above Regular BSR is triggered.

[0236] In the above embodiment, optionally, the Regular BSR is triggered by the third LCG, which includes the end of the data burst and whose buffer size has not been reported.

[0237] In the above embodiment, optionally, except for the above Regular BSR related to the end of the second data burst, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader.

[0238] In the above embodiment, optionally, if the sum of the number of second LCGs containing available data to be transmitted and the number of third LCGs containing Regular BSRs related to the end of the second data burst is greater than 1, the processing unit 620 reports a Long BSR for all second LCGs containing available data to be transmitted and all third LCGs that triggered the Regular BSR due to the end of the second data burst.

[0239] FIG7 is another schematic diagram of an apparatus for indicating the end of an uplink data burst according to an embodiment of the present application. The apparatus may be, for example, a terminal device, or one or more components or assemblies configured in the terminal device. Since the principle of solving the problem of the apparatus is the same as that of the embodiment of the second aspect, its specific implementation can refer to the implementation of the method of the embodiment of the second aspect, and the same content will not be repeated here.

[0240] As shown in FIG7 , the apparatus 700 for indicating the end of an uplink data burst includes:

[0241] a generating unit 710 for generating a regular buffer status report (Regular BSR) with a buffer size of 0 for a third logical channel group (LCG), the Regular BSR being associated with an end of a second data burst (EoDB);

[0242] The processing unit 720 reports the Regular BSR to the network device.

[0243] In some embodiments, the Regular BSR is triggered when uplink data of a logical channel belonging to an LCG becomes available to the MAC entity, and the uplink data includes the end of the second data burst.

[0244] In some embodiments, optionally, except for the Regular BSR associated with the end of the second data burst, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate an additional BSR MAC CE and its subheader.

[0245] In some embodiments, optionally, except for the Regular BSR associated with the end of the second data burst, all BSRs triggered before MAC PDU packetization are canceled when a MAC PDU including a BSR MAC CE is sent.

[0246] In the above embodiment, optionally, the above BSR includes the buffer status up to (and including) the last event that triggers the BSR before the MAC PDU is assembled.

[0247] In the above embodiment, the BSR may be at least one of the following:

[0248] Long BSR, Extended Long BSR, Short BSR, or Extended Short BSR.

[0249] In some embodiments, optionally, the above-mentioned Regular BSR related to the end of the second data burst is cancelled when a MAC PDU is sent and the MAC PDU includes identification information of the LCG that triggers the Regular BSR and a BSR with a buffer size of 0.

[0250] An embodiment of the present application also provides a configuration device.

[0251] FIG8 is a schematic diagram of a configuration device according to an embodiment of the present application. The device may be, for example, a network device or one or more components or assemblies configured within the network device. Since the principle of solving the problem of the device is the same as that of the embodiment of the third aspect, its specific implementation may refer to the implementation of the method of the embodiment of the third aspect, and the details of the same content will not be repeated here.

[0252] As shown in FIG8 , the configuration device 800 includes:

[0253] A sending unit 810 sends configuration information to a terminal device, where the configuration information configures whether a logical channel or LCG reports on the end of a data burst;

[0254] The receiving unit 820 receives a Padding BSR and / or a Regular BSR from a terminal device.

[0255] In some embodiments, the configuration information is included in an RRCReconfiguration message.

[0256] In some embodiments, the LogicalChannelConfig IE in the RRCReconfiguration message includes a first configuration field, where the first configuration field is used to indicate whether the current logical channel supports reporting of data burst end information.

[0257] In some embodiments, the RRCReconfiguration message includes a first IE, the first IE includes a second configuration field, and the second configuration field is used to indicate whether the current LCG supports reporting of the end of the data burst.

[0258] In some embodiments, as shown in FIG8 , the apparatus 800 further includes:

[0259] The processing unit 830 determines, according to the Padding BSR and / or Regular BSR, by identifying an LCG with a buffer size of 0, to which LCG the XR service has ended the current data burst.

[0260] It is worth noting that the above only describes the components or modules related to the present application, but the present application is not limited thereto. The devices 600, 700, and 800 of the embodiments of the present application may also include other components or modules. For the specific contents of these components or modules, reference may be made to the relevant art.

[0261] In addition, for the sake of simplicity, Figures 6 to 8 only illustrate the connection relationships or signal paths between various components or modules. However, it should be clear to those skilled in the art that various related technologies such as bus connections can be used. The above-mentioned components or modules can be implemented by hardware facilities such as processors, memories, transmitters, and receivers; this application is not limited to this.

[0262] According to the device of the embodiment of the present application, the network capacity is improved and the UE energy saving effect is achieved.

[0263] Embodiments of the fifth aspect

[0264] Embodiments of the present application provide a communication system, including a terminal device and a network device. The terminal device is configured to perform the method described in the first or second embodiment, and / or the network device is configured to perform the method described in the third embodiment. The behaviors of the terminal device and the network device have been described in detail in the embodiments of the first to third aspects, and their contents are incorporated herein and will not be repeated here.

[0265] An embodiment of the present application further provides a terminal device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in the embodiment of the first aspect or the second aspect.

[0266] Figure 9 is a schematic diagram of a terminal device according to an embodiment of the present application. As shown in Figure 9 , terminal device 900 may include a processor 910 and a memory 920. Memory 920 stores data and programs and is coupled to processor 910. It should be noted that this diagram is exemplary; other types of structures may be used to supplement or replace this structure to implement telecommunication or other functions.

[0267] For example, the processor 910 may be configured to execute a program to implement the method described in the embodiments of the first aspect or the second aspect.

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

[0269] An embodiment of the present application further provides a network device, which includes a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in the embodiment of the third aspect.

[0270] Figure 10 is a schematic diagram of a network device according to an embodiment of the present application. As shown in Figure 10, network device 1000 may include a central processing unit (CPU) 1010 and a memory 1020; memory 1020 is coupled to CPU 1010. Memory 1020 can store various data and information processing programs, which are executed under the control of CPU 1010 to receive various information sent by terminal devices and send various information to terminal devices.

[0271] For example, the processor 1010 may be configured to execute a program to implement the method as described in the embodiment of the third aspect.

[0272] In addition, as shown in Figure 10, network device 1000 may further include: a transceiver 1030 and an antenna 1040; wherein, the functions of the above components are similar to those in the prior art and are not described here in detail. It is worth noting that network device 1000 does not necessarily include all the components shown in Figure 10; in addition, network device 1000 may also include components not shown in Figure 10, and reference may be made to the prior art for details.

[0273] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in a terminal device, the program enables the computer to execute the method described in the embodiment of the first aspect or the second aspect in the terminal device.

[0274] An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in the embodiment of the first aspect or the second aspect in a terminal device.

[0275] An embodiment of the present application further provides a computer-readable program, wherein when the program is executed in a network device, the program enables a computer to execute the method described in the embodiment of the third aspect in the network device.

[0276] An embodiment of the present application further provides a storage medium storing a computer-readable program, wherein the computer-readable program enables a computer to execute the method described in the embodiment of the third aspect in a network device.

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

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

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

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

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

[0282] Regarding the above implementation methods disclosed in this embodiment, the following additional notes are also disclosed:

[0283] 1. A method for indicating the end of an uplink data burst, wherein the method comprises:

[0284] The terminal device generates a padding buffer status report (Padding BSR) with a buffer size of 0 for a first logical channel group (LCG), the Padding BSR being associated with an end of a first data burst (EoDB);

[0285] The terminal device reports the Padding BSR to the network device.

[0286] 2. The method according to Note 1, wherein the Padding BSR includes a cache size field with a value of 0 for the first LCG, the first LCG has no available data to be transmitted, and the MAC PDU to which the Padding BSR belongs includes the last MAC SDU of the first data burst, and the MAC SDU comes from a logical channel in the first LCG.

[0287] 3. The method according to Note 2, wherein the last MAC SDU of the first data burst is:

[0288] The MAC SDU corresponding to the last PDU in the application layer data burst, or

[0289] The last data sent by the MAC entity in an application layer data burst.

[0290] 4. The method according to Note 2, wherein the first LCG is selected from LCGs that need to report a cache size of 0.

[0291] 5. The method according to Supplement 4, wherein the method further comprises:

[0292] The terminal device reports a second BSR for a second LCG to the network device, where the second LCG contains available data to be transmitted, and a cache status reporting priority of the second LCG is higher than a cache status reporting priority of the first LCG.

[0293] 6. The method according to Supplement 5, wherein:

[0294] The terminal device selects in descending order the logical channel with the highest priority in each LCG that needs to report a cache size of 0; if the priorities are the same, the terminal device selects in ascending order the LCG identifiers of the LCGs that need to report a cache size of 0; or

[0295] The terminal device selects in descending order of the logical channel priority that contains the data burst end data in the packet assembly process in each LCG that needs to report a cache size of 0. If the priority is the same, the terminal device selects in ascending order of the LCG identifier of the LCG that needs to report a cache size of 0.

[0296] 7. The method according to Supplement 4, wherein the method further comprises:

[0297] The terminal device compares the priority of the LCG that needs to report a buffer size of 0 and the second LCG containing available data to be transmitted;

[0298] When the priority of the logical channel with the highest priority in the second LCG is higher than the priority of the logical channel with the highest priority in the LCG whose reporting buffer size is 0, the terminal device preferentially reports the second BSR for the second LCG;

[0299] In a case where the priority of the logical channel with the highest priority in the LCG that needs to report a buffer size of 0 is higher than the priority of the logical channel with the highest priority in the second LCG, the terminal device preferentially reports the Padding BSR for the LCG that needs to report a buffer size of 0;

[0300] When the priority of the logical channel with the highest priority in the LCG whose buffer size needs to be reported is 0 is the same as the priority of the logical channel with the highest priority in the second LCG, the terminal device selects LCG for BSR reporting in ascending order of LCG identifier.

[0301] 8. The method according to any one of Notes 1 to 7, wherein the terminal device generates the Padding BSR, comprising:

[0302] The MAC entity of the terminal device generates the Padding BSR,

[0303] in,

[0304] If the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length;

[0305] If, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a buffer size of 0 is greater than 1, then if the number of bits of the Padding BSR is equal to the short BSR plus its subheader length, the terminal device reports a Short Truncated BSR, otherwise it reports a Long Truncated BSR;

[0306] If the number of bits of the Padding BSR is greater than or equal to the long BSR plus its subheader length, the terminal device reports all second LCGs containing available data to be transmitted and all long BSRs corresponding to LCGs whose cache size needs to be reported is 0.

[0307] 9. The method according to Supplementary Note 8, wherein the terminal device reports a Short Truncated BSR, comprising:

[0308] The terminal device selects the second LCG corresponding to the logical channel with the highest priority among the logical channels containing available data to be transmitted to report the BSR; if there is no second LCG containing available data to be transmitted, the terminal device selects the LCG with a buffer size of 0 to report the BSR; or

[0309] The terminal device selects the LCG corresponding to the logical channel with the highest priority among the logical channels to which the assembled data burst end data belongs, which contains available data to be transmitted, to report the BSR.

[0310] 10. The method according to Supplementary Note 8, wherein the terminal device reports the Long Truncated BSR, including:

[0311] The terminal device selects the second LCG corresponding to the logical channel with the highest priority among all logical channels containing available data to be transmitted to report the BSR, and then selects the LCG with a buffer size of 0 to report the BSR; or

[0312] The terminal device selects LCG for BSR reporting in descending order of the priority of the logical channel with the highest priority in each LCG in the LCG corresponding to the logical channel containing available data to be transmitted or the logical channel to which the assembled data burst end data belongs. If the priorities are the same, the LCG is selected for BSR reporting in ascending order of the LCG identifier.

[0313] 11. The method according to Supplementary Note 10, wherein:

[0314] One byte in the Long Truncated BSR frame format consists of a bit field LCGi, where i ranges from 0 to 7.

[0315] The LCGi field indicates whether the i-th LCG has available data or whether the end data in the data burst has been assembled;

[0316] LCGi is set to 1 to indicate that LCG i has available data, or that the end data of the data burst from LCG i is assembled in the MAC PDU containing the Long Truncated BSR;

[0317] LCGi is set to 0 to indicate that no data is available for LCG i.

[0318] 12. The method according to Supplement 11, wherein:

[0319] The LCGi is set to 1, and the buffer size field corresponding to the LCGi in the frame format of the Long Truncated BSR is 0, indicating that the end data of the data burst from the LCGi is assembled in the MAC PDU containing the Long Truncated BSR.

[0320] 13. According to the method described in Note 1, the method further comprises:

[0321] The terminal device receives configuration information sent by the network device, where the configuration information configures whether the logical channel or LCG reports on the end of the data burst.

[0322] 14. The method according to Supplement 13, wherein:

[0323] The configuration information is included in the RRCReconfiguration message;

[0324] The LogicalChannelConfig IE in the RRCReconfiguration message includes a first configuration field, and the first configuration field is used to indicate whether the current logical channel supports reporting information about the end of a data burst; or, the RRCReconfiguration message includes a first IE, and the first IE includes a second configuration field, and the second configuration field is used to indicate whether the current LCG supports reporting information about the end of a data burst.

[0325] 15. The method according to Supplement 1, wherein:

[0326] The terminal device reports the Padding BSR when the first data burst ends and all LCGs have no available data to be transmitted.

[0327] 16. The method according to supplementary note 15, wherein the terminal device generates the Padding BSR, comprising:

[0328] The MAC entity of the terminal device generates the Padding BSR,

[0329] in,

[0330] If the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length;

[0331] If, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a buffer size of 0 is less than or equal to 1, the terminal device reports a short BSR;

[0332] If the number of bits of the Padding BSR is greater than or equal to the long BSR plus its sub-header length, the terminal device reports the Long BSR.

[0333] 17. The method according to Supplement 16, wherein:

[0334] When the terminal device reports the short BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of an LCG, then the short BSR includes the LCG identifier and a cache size field with a value of 0.

[0335] 18. The method according to Supplement 16, wherein:

[0336] When the terminal device reports the Long BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains one or more MAC SDUs that end a data burst, and the MAC SDUs come from the logical channels of one or more LCGs, then the LCGi corresponding to the LCG in the long BSR is set to 1, and its cache size field is set to 0.

[0337] 19. The method according to Supplement 1, wherein:

[0338] The terminal device reports the Padding BSR when the first data burst ends and all logical channels that are not configured as configuredGrantType1Allowed have no available data to be transmitted.

[0339] 20. The method according to Supplementary Note 19, wherein the terminal device generates the Padding BSR, comprising:

[0340] The MAC entity of the terminal device generates the Padding BSR,

[0341] in,

[0342] If the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length;

[0343] If, when constructing the Padding BSR, the number of second LCGs containing available data to be transmitted is greater than 1, the terminal device reports a Short Truncated BSR if the number of bits in the Padding BSR is equal to the Short BSR plus its subheader length; otherwise, it reports a Long Truncated BSR;

[0344] If, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a buffer size of 0 is less than or equal to 1, a short BSR is reported;

[0345] If the number of bits of the Padding BSR is greater than or equal to the long BSR plus its sub-header length, the terminal device reports the Long BSR.

[0346] 21. The method according to Supplement 20, wherein:

[0347] When the terminal device reports the Long Truncated BSR, after reporting all the second LCGs containing available data to be transmitted, if there is still space, and all the logical channels containing available data to be transmitted are configured as configuredGrantType1Allowed, and the assembled MAC PDU contains a MAC SDU that ends the data burst, and the MAC SDU comes from the logical channel of an LCG, then the Long Truncated BSR includes the identifier of the LCG and a cache size field with a value of 0.

[0348] 22. The method according to Note 20, wherein:

[0349] When the terminal device reports the short BSR, if all LCGs have no available data to be transmitted, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of an LCG, then the Short BSR includes the identifier of the LCG and a cache size field with a value of 0.

[0350] 23. The method according to Supplement 20, wherein:

[0351] When the terminal device reports a Long BSR, if all logical channels containing available data to be transmitted are configured as configuredGrantType1Allowed, and the assembled MAC PDU contains a MAC SDU that ends a data burst, and the MAC SDU comes from a logical channel of an LCG, then the LCGi corresponding to the LCG is set to 1, and the cache size field corresponding to the LCG is set to 0.

[0352] 24. The method according to Supplement 1, wherein:

[0353] The Padding BSR is triggered when a MAC PDU containing the end of the first data burst is assembled;

[0354] The Padding BSR is associated with the LCG to which the logical channel containing the end of the first data burst belongs.

[0355] 25. The method according to Note 24, wherein:

[0356] Except for the Padding BSR, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate the BSR MAC CE and its subheader.

[0357] 26. The method according to Note 24, wherein:

[0358] The triggered Padding BSR associated with the end of the first data burst associated with an LCG is cancelled after the BSR of the LCG is reported.

[0359] 27. The method according to any one of Notes 24 to 26, wherein:

[0360] The first LCG triggers a Padding BSR related to the end of a data burst and is not canceled.

[0361] 28. The method according to Supplement 1, wherein:

[0362] The Padding BSR is triggered when a MAC PDU containing the end of the first data burst is assembled;

[0363] The Padding BSR is associated with a logical channel containing the end of the first data burst.

[0364] 29. The method according to Supplementary Note 28, wherein:

[0365] The Padding BSR associated with the end of the first data burst associated with a logical channel that is triggered is cancelled after the BSR of the LCG to which the logical channel belongs is reported.

[0366] 30. The method according to Note 28 or 29, wherein:

[0367] A logical channel in the first LCG triggers a Padding BSR related to a data burst end and is not canceled.

[0368] 31. The method according to any one of Notes 1 to 30, wherein:

[0369] When the Padding BSR is insufficient, the terminal device generates a regular buffer status report (Regular BSR) with a buffer size of 0 for a third logical channel group (LCG), the Regular BSR being associated with an end of a second data burst (EoDB);

[0370] The terminal device reports the Regular BSR to the network device.

[0371] 32. The method according to Note 31, wherein:

[0372] When a MAC PDU containing the end of a data burst from an LCG is assembled, if there are no padding bits available for the Padding BSR or the Padding BSR is insufficient to accommodate all buffer size fields with a value of 0, the Regular BSR is triggered.

[0373] 33. The method according to claim 32, wherein

[0374] The Regular BSR is triggered by the third LCG, which contains the end of the data burst and whose buffer size has not been reported.

[0375] 34. The method according to any one of Notes 31 to 33, wherein:

[0376] Except for the Regular BSR associated with the end of the second data burst, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate an additional BSR MAC CE and its subheader.

[0377] 35. The method of claim 33, wherein:

[0378] If the sum of the number of second LCGs containing available data to be transmitted and the number of third LCGs containing Regular BSRs related to the end of the second data burst is greater than 1, the terminal device reports a Long BSR for all second LCGs containing available data to be transmitted and all third LCGs that triggered the Regular BSR due to the end of the second data burst.

[0379] 36. A method for indicating the end of an uplink data burst, wherein the method comprises:

[0380] The terminal device generates a regular buffer status report (Regular BSR) with a buffer size of 0 for a third logical channel group (LCG), the Regular BSR being associated with an end of data burst (EoDB);

[0381] The terminal device reports the Regular BSR to the network device.

[0382] 37. The method according to Supplement 36, wherein:

[0383] The Regular BSR is triggered when uplink data of a logical channel belonging to an LCG becomes available to the MAC entity and the uplink data includes the second data burst end.

[0384] 38. The method according to Note 36 or 37, wherein:

[0385] Except for the Regular BSR associated with the end of the second data burst, all triggered BSRs are cancelled when the uplink grant can accommodate all available data to be transmitted but is insufficient to accommodate an additional BSR MAC CE and its subheader.

[0386] 39. The method according to any one of claims 36 to 38, wherein:

[0387] Except for the Regular BSR associated with the end of the second data burst, all BSRs triggered before MAC PDU packetization are canceled when a MAC PDU including a BSR MAC CE is sent.

[0388] 40. The method according to Supplement 39, wherein:

[0389] The BSR contains the buffer status up to the last event that triggered the BSR before the MAC PDU assembly.

[0390] 41. The method according to note 40, wherein the BSR is at least one of the following:

[0391] Long BSR, Extended Long BSR, Short BSR, or Extended Short BSR.

[0392] 42. The method according to any one of Notes 36 to 41, wherein:

[0393] The Regular BSR associated with the end of the second data burst is cancelled when a MAC PDU is sent and the MAC PDU includes identification information of the LCG that triggers the Regular BSR and a BSR with a buffer size of 0.

[0394] 43. A configuration method, wherein the method comprises:

[0395] The network device sends configuration information to the terminal device, wherein the configuration information configures whether the logical channel or LCG reports the end of the data burst;

[0396] The network device receives a Padding BSR and / or a Regular BSR from the terminal device.

[0397] 44. The method according to Note 43, wherein:

[0398] The configuration information is included in the RRCReconfiguration message;

[0399] The LogicalChannelConfig IE in the RRCReconfiguration message includes a first configuration field, and the first configuration field is used to indicate whether the current logical channel supports reporting information about the end of a data burst; or, the RRCReconfiguration message includes a first IE, and the first IE includes a second configuration field, and the second configuration field is used to indicate whether the current LCG supports reporting information about the end of a data burst.

[0400] 45. The method according to claim 43 or 44, wherein the method further comprises:

[0401] The network device determines, according to the Padding BSR and / or Regular BSR, by identifying an LCG with a cache size of 0, to which LCG the XR service has ended the current data burst.

[0402] 46. ​​A terminal device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 1 to 42.

[0403] 47. A network device comprising a memory and a processor, wherein the memory stores a computer program, and the processor is configured to execute the computer program to implement the method as described in any one of Notes 43 to 45.

[0404] 48. A communication system comprising a terminal device and a network device, wherein the terminal device is configured to execute the method described in any one of Notes 1 to 42, and / or the network device is configured to execute the method described in any one of Notes 43 to 45.

Claims

1. A device for indicating the end of an uplink data burst, configured in a terminal device, wherein: The device comprises: a generating unit, which generates a padding buffer status report (Padding BSR) with a buffer size of 0 for a first logical channel group (LCG), wherein the Padding BSR is associated with an end of a first data burst (EoDB); A processing unit reports the Padding BSR to a network device.

2. The device according to claim 1, wherein: The Padding BSR includes a cache size field with a value of 0 for the first LCG, the first LCG has no available data to be transmitted, the MAC PDU to which the Padding BSR belongs includes the last MAC SDU of the first data burst, and the MAC SDU comes from a logical channel in the first LCG.

3. The device according to claim 2, wherein: The first LCG is selected from LCGs that need to report a cache size of 0.

4. The device according to claim 3, wherein: The processing unit further reports a second BSR for a second LCG to the network device, where the second LCG contains available data to be transmitted, and a cache status reporting priority of the second LCG is higher than a cache status reporting priority of the first LCG.

5. The device according to claim 4, wherein: The processing unit selects in descending order the logical channel with the highest priority in each LCG that needs to report a cache size of 0; if the priorities are the same, the processing unit selects in ascending order the LCG identifiers of the LCGs that need to report a cache size of 0; or The processing unit selects in descending order of the logical channel priority that contains the data burst end data during the packet assembly process in each LCG that needs to report a cache size of 0. If the priorities are the same, the processing unit selects in ascending order of the LCG identifier of the LCG that needs to report a cache size of 0.

6. The device according to claim 3, wherein: The processing unit compares the priorities of the LCG that needs to report a cache size of 0 and the second LCG that contains available data to be transmitted; In a case where the priority of the logical channel with the highest priority in the second LCG is higher than the priority of the logical channel with the highest priority in the LCG that needs to report a buffer size of 0, the processing unit preferentially reports the second BSR for the second LCG; In a case where the priority of the logical channel with the highest priority in the LCG that needs to report a buffer size of 0 is higher than the priority of the logical channel with the highest priority in the second LCG, the processing unit preferentially reports the Padding BSR for the LCG that needs to report a buffer size of 0; When the priority of the logical channel with the highest priority in the LCG that needs to report the buffer size of 0 is the same as the priority of the logical channel with the highest priority in the second LCG, the processing unit selects LCGs for BSR reporting in ascending order of LCG identifiers.

7. The device according to claim 1, wherein: The generating unit generates the Padding BSR, including: The generating unit generates the Padding BSR at the MAC entity of the terminal device, in, If the number of bits of the Padding BSR is greater than or equal to the short BSR plus its subheader length, but less than the long BSR plus its subheader length; If, when constructing the Padding BSR, the sum of the number of second LCGs containing available data to be transmitted and the number of LCGs that need to report a buffer size of 0 is greater than 1, then if the number of bits of the Padding BSR is equal to the short BSR plus its subheader length, the processing unit reports a Short Truncated BSR, otherwise it reports a Long Truncated BSR; If the number of bits of the Padding BSR is greater than or equal to the long BSR plus its subheader length, the processing unit reports all second LCGs containing available data to be transmitted and all long BSRs corresponding to LCGs whose buffer size is 0 need to be reported.

8. The device according to claim 7, wherein: The processing unit reports the Short Truncated BSR, including: The processing unit selects a second LCG corresponding to a logical channel with the highest priority among logical channels containing available data to be transmitted to report the BSR; if there is no second LCG containing available data to be transmitted, the processing unit selects an LCG with a buffer size of 0 to report the BSR; or, The processing unit selects a logical channel containing available data to be transmitted or an LCG corresponding to a logical channel with the highest priority among logical channels to which assembled data burst end data belongs to report the BSR.

9. The device according to claim 7, wherein: The processing unit reports the Long Truncated BSR, including: The processing unit selects the second LCG corresponding to the logical channel with the highest priority among all logical channels containing available data to be transmitted to report the BSR, and then selects the LCG whose buffer size needs to be reported as 0 to report the BSR; or, The processing unit selects LCG for BSR reporting in descending order of the priority of the logical channel with the highest priority in each LCG, in the LCG corresponding to the logical channel containing available data to be transmitted or the logical channel to which the assembled data burst end data belongs. If the priorities are the same, then selects LCG for BSR reporting in ascending order of LCG identifiers.

10. The device according to claim 9, wherein: One byte in the frame format of the Long Truncated BSR consists of a bit field LCGi, where i ranges from 0 to 7. The LCGi field indicates whether the i-th LCG has available data or whether the end data in the data burst has been assembled; LCGi is set to 1 to indicate that LCG i has available data, or that the end data of the data burst from LCG i is assembled in the MAC PDU containing the Long Truncated BSR; LCGi is set to 0 to indicate that no data is available for LCG i.

11. The device according to claim 10, wherein: The LCGi is set to 1, and the cache size field corresponding to the LCGi in the frame format of the Long Truncated BSR is 0, indicating that the end data of the data burst from the LCGi is assembled in the MAC PDU containing the Long Truncated BSR.

12. The device according to claim 1, wherein: The device also includes: A receiving unit receives configuration information sent by the network device, wherein the configuration information configures whether a logical channel or LCG reports on the end of a data burst.

13. The device according to claim 12, wherein: The configuration information is included in the RRCReconfiguration message; The LogicalChannelConfig IE in the RRCReconfiguration message includes a first configuration field, and the first configuration field is used to indicate whether the current logical channel supports reporting information on the end of a data burst; or, the RRCReconfiguration message includes a first IE, and the first IE includes a second configuration field, and the second configuration field is used to indicate whether the current LCG supports reporting information on the end of a data burst.

14. The device according to claim 1, wherein: The processing unit reports the Padding BSR when the first data burst ends and all LCGs have no available data to be transmitted.

15. The device according to claim 1, wherein: The Padding BSR is triggered when a MAC PDU including the end of the first data burst is assembled; The Padding BSR is associated with the LCG to which the logical channel including the end of the first data burst belongs.

16. The device according to claim 15, wherein: The Padding BSR associated with the end of the first data burst associated with an LCG that is triggered is cancelled after the BSR of the LCG is reported.

17. The device according to claim 1, wherein: When the Padding BSR is insufficient, the generating unit generates a regular buffer status report (Regular BSR) with a buffer size of 0 for a third logical channel group (LCG), the Regular BSR being associated with an end of a second data burst (EoDB); The processing unit reports the Regular BSR to the network device.

18. A device for indicating the end of an uplink data burst, configured in a terminal device, wherein: The device comprises: a generating unit, which generates a regular buffer status report (Regular BSR) with a buffer size of 0 for a third logical channel group (LCG), wherein the Regular BSR is associated with an end of a second data burst (EoDB); A processing unit reports the Regular BSR to a network device.

19. The device according to claim 18, wherein: The Regular BSR is triggered when uplink data of a logical channel belonging to an LCG becomes available to the MAC entity and the uplink data includes the end of the second data burst.

20. A configuration device, configured in a network device, wherein: The device comprises: A sending unit, which sends configuration information to the terminal device, wherein the configuration information configures whether the logical channel or LCG reports on the end of the data burst; A receiving unit receives a Padding BSR and / or a Regular BSR from the terminal device.

Images