Enhanced uplink scheduling assistance information for layer 2 design with 6g hardware optimization for variable size packet data units

Abstract

According to example embodiments of the present application, at least a method and apparatus are provided for performing at least the following: determining enhanced data volume information for data buffered at at least one processing unit of the apparatus, wherein the enhanced data volume information comprises at least one of: a set of sizes of individual buffered data units of the at least one processing unit of the apparatus, or a set of preferred data volume allocations based on the set of sizes of individual buffered data units; and transmitting the enhanced data volume information to a network node of a communications network based on the determining.

Description

Technical Field

[0001] The teachings of exemplary embodiments of the present invention generally relate to using enhanced data volume information to request data transfer from different RPUs, and more specifically, to using enhanced data volume information including enhanced buffer status information transmitted via signaling to request data transfer from different RPUs. Background Technology

[0002] This section is intended to provide background or context for the invention as set forth in the claims. The description herein may include concepts that may be employed but not necessarily previously conceived or employed. Therefore, unless otherwise stated herein, the content described in this section is not prior art to the specification and claims of this application, nor is it acknowledged as prior art by virtue of its inclusion in this section.

[0003] Some abbreviations that may appear in this description and / or figures are defined as follows: APS Anchor Protocol Stack BSR Buffer Status Report FPS Fast Protocol Stack LCG logical channel group MAC Media Access Control PBR Priority Bit Rate PDCP Packet Data Convergence Protocol PDU Protocol Data Unit PHY physical layer RLC Radio Link Control RPU Radio Processing Unit SDAP Service Data Adaptation Protocol SDU Service Data Unit TB transport block TBS transport block size For the design of 6G radio protocols, a new approach relying on two stacks is proposed: 1. The first radio protocol stack—the Anchor Protocol Stack (APS)—is designed for low bit rate service, coverage (e.g., bit-level optimization), and reliability (e.g., RLC ARQ); and 2. The second radio protocol stack—the Fast Protocol Stack (FPS)—is designed for high bit rate services, with an emphasis on a user-friendly and implementable design that employs the concept of a Radio Processing Unit (RPU) to enable parallel processing of radio functions.

[0004] Using this approach, complex mechanisms and optimizations that are perfectly reasonable for low bit rate services do not need to be applied to extremely high bit rate services.

[0005] The exemplary embodiments of the present invention propose one or more methods for at least solving these problems, as well as improvements for these operations. Summary of the Invention

[0006] This section contains examples of possible implementations and is not intended to be restrictive.

[0007] In another exemplary aspect of the invention, an apparatus, such as a user equipment side apparatus, is provided, comprising: at least one processor; and at least one non-transitory memory storing instructions that, when executed by the at least one processor, cause the apparatus to at least: determine enhanced data volume information of data buffered at at least one processing unit of the apparatus, wherein the enhanced data volume information includes at least one of the following: a set of sizes of individual buffered data units of the at least one processing unit of the apparatus, or a set of preferred data volume allocations based on the set of sizes of the individual buffered data units; and, based on the determination, transmit the enhanced data volume information to a network node of a communication network.

[0008] In another aspect of the invention, a method is provided, comprising: determining enhanced data volume information of data buffered at at least one processing unit of a device, wherein the enhanced data volume information includes at least one of the following: a set of sizes of individual buffered data units of the at least one processing unit of the device, or a set of preferred data volume allocations representing preferred allocation thresholds; and based on the determination, transmitting the enhanced data volume information to a network node of a communication network.

[0009] Another example embodiment is an apparatus and a method comprising the apparatus and method described in the preceding paragraph, wherein enhanced data volume information is used to determine how to split the allocated transport block size among at least two processing units in at least one processing unit to avoid or limit at least one of segmentation or padding; wherein enhanced data volume information is used to determine the transport block size to be allocated to the apparatus to avoid or limit at least one of segmentation or padding; wherein the set of preferred data volume allocations representing preferred allocation thresholds includes at least one of the following: a first data volume allocation required to transmit a minimum number of buffered data units consisting of at least one data unit, a second data volume allocation required to transmit a second number of buffered data units. A third data volume allocation (the second number is greater than the minimum number), or a third number of buffered data units required for transmission (the third number is greater than the second number); wherein the third number of data units is the maximum number of data units whose cumulative size is less than or equal to the buffered data threshold; wherein the size of each individual buffered data unit is in the exact order in which the data units are buffered in the transmission buffer of at least one processing unit, and is provided only for buffered data units whose cumulative size is less than or equal to the buffer threshold; wherein the buffered data unit includes at least one of the following: Radio Link Control Service Data Unit, Radio Link Control Service Data Unit segment, Radio Link Control State Protocol Data Unit, Packet Data Control... The data includes a Packet Data Control Protocol (PDCP) service data unit, a Packet Data Control Protocol (PDCP) data unit, or a PDCP control protocol data unit to be transmitted or retransmitted in at least one processing unit of the apparatus; wherein, based on enhancement information received from each of the at least one processing unit of the apparatus, the information is transmitted for each of the at least one processing unit of the apparatus, each logical channel group, or each device transmission; wherein, a data quantity strictly conforming to the enhancement data quantity information is requested from at least one processing unit, and padding is subsequently performed if at least one processing unit fails to deliver the exact amount of the requested data, or a data quantity not strictly conforming to the enhancement data quantity information is requested from at least one processing unit. The process includes: performing padding to match the requested data amount; performing segmentation of buffered data units to match the requested data amount; or delivering a set of buffered data units with a cumulative size less than or equal to the requested data amount; wherein at least one of zero padding or segmentation is performed to match the requested data amount to reach at least one preferred allocation threshold, and the at least one preferred allocation threshold is based on at least one of radio link control header size or number of bytes; wherein, based on the enhanced data amount information, enhanced buffer status information is reported to network nodes in an enhanced buffer status report, and enhanced buffer status information is reported to at least one radio processing unit, at least one logical channel group, or user equipment.The report is granular at a level lower than that of the user equipment, and the information indicates which radio processing units or logical channel groups the buffer status report applies to and / or how many radio processing units or logical channel groups it applies to; wherein the amount of data requested from at least one radio processing unit is not allowed to exceed a preferred allocation threshold; and / or wherein the apparatus is implemented in a user equipment within a communication network.

[0010] A non-transitory computer-readable medium storing program code that is executed by at least one processor to perform at least the methods described in the preceding paragraph.

[0011] In another exemplary aspect of the invention, an apparatus is provided, comprising: means for determining enhanced data volume information of data buffered at at least one processing unit of the apparatus, wherein the enhanced data volume information includes at least one of the following: a set of sizes of individual buffered data units of the at least one processing unit of the apparatus, or a set of preferred data volume allocations based on the set of sizes of the individual buffered data units; and means for transmitting the enhanced data volume information to a network node of a communication network based on the determination.

[0012] According to the example embodiments described in the preceding paragraph, at least the components used for identification, initiation, and determination include a network interface and computer program code stored on a computer-readable medium and executed by at least one processor.

[0013] A communication system includes a network-side device and a user equipment-side device for performing the above operations. Attached Figure Description

[0014] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more apparent from the following detailed description with reference to the accompanying drawings, in which the same reference numerals are used to denote the same or equivalent elements. The drawings are provided to aid in a better understanding of the embodiments of the present disclosure and are not necessarily drawn to scale, wherein: Figure 1 The 6G UE type is shown; Figure 2 This illustrates the 6G radio protocol; Figure 3 The radio processing unit (RPU) management is shown; Figure 4 Dual-stack operation with a radio processing unit (RPU) is shown; Figure 5 A signaling diagram according to an example embodiment of the present invention is shown; Figure 6 A high-level block diagram of various devices for implementing aspects of the present invention is shown; and Figure 7A method executable by an apparatus according to an example embodiment of the present invention is shown. Detailed Implementation

[0015] In exemplary embodiments of the present invention, at least one method and apparatus are proposed for requesting data transfer from different RPUs using enhanced data volume information, including enhanced buffer state information transmitted via signaling.

[0016] As mentioned above, a novel approach relying on two stacks is proposed for the design of 6G radio protocols: 1. The first radio protocol stack—the Anchor Protocol Stack (APS)—is designed for low bit rate service, coverage (e.g., bit-level optimization), and reliability (e.g., RLC ARQ); and 2. The second radio protocol stack—the Fast Protocol Stack (FPS)—is designed for high bit rate services, with an emphasis on a design that is easy to process and implement using the concept of a Radio Processing Unit (RPU), thereby enabling parallel processing of radio functions.

[0017] This approach eliminates the need for complex mechanisms and optimizations perfectly adequate for low-bit-rate services to be used for extremely high-bit-rate services. Simpler devices can implement only the first stack (APS), potentially eliminating the need for equivalents of MTC, NB-IoT, and RedCap. More complex and powerful devices will implement both stacks. The higher the bit rate supported by the device, the more RPUs are included in the FPS, such as... Figure 1 The three UE types shown are illustrated.

[0018] Figure 1 The 6G UE type is shown. (Example) Figure 1 As shown in step 110, there exist low-cost UEs with an anchor protocol stack (APS), mainstream UEs with an anchor protocol stack and a fast protocol stack including multiple (in this case, four) radio processing units, and UEs with an anchor protocol stack and such Figure 1 Step 120 shows a high-end UE that includes a fast protocol stack comprising multiple (eight in this case) radio processing units.

[0019] On the transmitter side, a common layer needs to oversee the allocation of incoming Service Data Units (SDUs) to each RPU. To maximize the number of tasks that can be executed in parallel, this needs to be located in a higher part of the radio protocol. The ideal candidate is a higher part of the Packet Data Convergence Protocol (PDCP) layer (PDCP-HI or PDCP-high), after sequence number (SN) allocation but before other functions such as security and header compression. This allows these other functions to be executed in parallel on each RPU. Figure 2 An example of this structure is depicted in the text.

[0020] Figure 2 The 6G radio protocol is shown. (Example) Figure 2 As shown in step 210, the higher part of the Service Data Adaptation Protocol (SDAP) and the Packet Data Convergence Protocol (PDCP-HI) is located as follows: Figure 2 Step 220 shows the Anchor Protocol Stack (APS) and Fast Protocol Stack (FPS). Figure 2 The anchor protocol stack includes PDCP-LOW, Radio Link Control (RLC), Media Access Control (MAC), and the Physical Layer (PHY). Furthermore, in Figure 2 In the Fast Protocol Stack, PDCP-low, RLC, and MAC include several Radio Processing Units (RPUs).

[0021] To maximize the power savings that the RPU framework can achieve, the number of activated RPUs can be adjusted based on the instantaneous bit rate or load to be provided, such as... Figure 3 As shown, it is assumed that a total of four RPUs are available.

[0022] Figure 3 The radio processing unit (RPU) management is illustrated. For example... Figure 3 As shown in step 310, Figure 3 As shown in step 320, multiple RPUs are used to transfer the load over time, some of which are idle and others are active.

[0023] Depending on whether RPUs share common memory and how they are activated, specific mechanisms for RPU management schemes may need to be introduced into the standard. For example, if RPUs operate on isolated memory resources, each RPU may host its own transmit and receive windows, affecting sequence number and status report management. Conversely, RPUs operating on shared resources will be allowed to use common windows without affecting sequence numbers or status reports.

[0024] Because it is always present, the APS is the logical host for control plane functions such as idle mode, connected mode, and radio resource control (RRC) related configurations. By including all control plane (CP) functions within the APS, the FPS can not only focus on user plane transmissions to simplify the design, but also does not need to be active when bit rate requirements are low.

[0025] Buffer Status Report (BSR) is a well-known MAC procedure used to inform the network UE of the amount of data buffered for transmission. APS is expected to use the BSR of previous generations (referred to as A-BSR in this paper), while FPS is expected to adopt a new format so that: 1. Facilitate operation by utilizing hardware-optimized L2 implementations that allow for higher bit rates; 2. As a result of the above, it is possible to process PDUs of a fixed size for each RPU; 3. Potentially report the amount of data buffered for each RPU.

[0026] In an exemplary embodiment of the present invention, an enhancement mechanism is proposed for exporting advanced UL scheduling assistance information and reporting it to the gNB when the PDU size of each RPU is variable.

[0027] This document provides baseline operation of the proposed APS and FPS architecture according to exemplary embodiments of the present invention, and based on previously specified and / or discussed content, assumes the following to be the closest to the prior art of the proposed concept: - A 6G dual-stack radio protocol with Anchor Protocol Stack (APS) and Fast Protocol Stack (FPS), with the Fast Protocol Stack (FPS) employing a Radio Processing Unit (RPU) to handle high data rates; - IP packet concatenation (if supported) can be done at PDCP-high (i.e., outside the RPU) or at PDCP-low (i.e., inside the RPU) (assuming data splitting is at the PDCP layer (PDCP concatenation is already considered in NR)).

[0028] - PDCP-low can also apply encryption / encryption processing / integrity protection (the functional decomposition within the protocol layer can be considered obvious); - In each transmission time interval (TTI), the RPU delivers a set of RLC PDUs multiplexed in a TB to the MAC (-low) upon request (the MAC has been requesting data from higher layers since LTE). - It may be necessary to require each RPU to provide a buffered data indication to the MAC (-low) so that the MAC can determine the amount of data (for BSR) (similar to the MAC requesting data amount information from each PDCP entity).

[0029] Figure 4 An example of dual-stack operation with RPU is shown in the figure.

[0030] Figure 4 This illustrates dual-stack operation with a Radio Processing Unit (RPU). For example... Figure 4 As shown in step 410, RRC and SDAP provide SRB and two DRBs, respectively. Figure 4 As shown in step 420, the streams from RRC and SDAP are provided to several PDCP-HIs, and then as follows: Figure 4 Step 430 is provided to either the APS or the FPS. Figure 4Step 430 shows that the APS and FPS each include PDCP-LOW, RLC, and MAC-HI. Figure 4 In this context, the FPS includes several Radio Processing Units (RPUs). Then, as... Figure 4 In the example shown, these streams all enter Figure 4 Step 440 shows MAC-low, then proceeds to... Figure 4 The PHY shown in step 450.

[0031] Potential problems with existing technology solutions: -MAC (-low) only knows the total amount of data to be transmitted in each RPU. This may lead to excessive fragmentation of RLCSDUs in each RPU.

[0032] Segmentation overhead and complexity may increase with the number of RPUs.

[0033] Advantages of "existing technology" solutions: - Minimal changes compared to the NR implementation.

[0034] Disadvantages of "existing technology" solutions: - When building a TB on a MAC, each RPU may still need to perform real-time segmentation; - Segmentation overhead (and complexity) may increase.

[0035] Before describing in detail the exemplary embodiments disclosed herein, refer to Figure 6 Simplified block diagrams are provided to illustrate various electronic devices applicable to the practice of exemplary embodiments of the present invention.

[0036] Figure 6 A block diagram of one possible, non-limiting, exemplary system in which example embodiments can be practiced is shown. Figure 6 In this context, User Equipment (UE) 10 communicates wirelessly with Wireless Network 1 or Network 1, such as... Figure 6 As shown. Figure 6 Wireless network 1 or network 1 in the document may include a communication network, such as a mobile network, for example, wireless network 1 or a first wireless network as disclosed herein. This document refers to... Figure 6 Any reference to Wireless Network 1 in this document can be considered a reference to any wireless network as disclosed herein. Furthermore, as... Figure 6The wireless network 1 in the RAN may also include hard-wired features that the communication network may require. The UE is wireless and is typically a mobile device that can access the wireless network. For example, the UE may be a mobile phone (or "cellular" phone) and / or a computer with mobile terminal capabilities. For example, the UE or mobile terminal may also be a portable, pocket, handheld, computer-embedded, or vehicle-mounted mobile device that performs voice signaling and / or data exchange with the RAN.

[0037] UE 10 includes one or more processors DP 10A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected via one or more buses. Each of the one or more transceivers TRANS 10D includes a receiver and a transmitter. The one or more buses may be address, data, or control buses and may include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic cable, or other optical communication device. The one or more transceivers TRANS 10D may optionally be connected to one or more antennas to communicate with NN 12 and NN 13 respectively. The one or more memories MEM 10B include computer program code PROG 10C. UE 10 communicates with NN 12 and / or NN13 via radio link 11 or 16.

[0038] NN 12 (NR / 5G / 6G Node B, evolved NB, or LTE equipment) is related to, for example, Figure 6The NN 12 is a network node that communicates with devices such as UE 10 and NN 13, such as a primary node base station or a secondary node base station (e.g., for NR or LTE Long Term Evolution). NN 12 provides access to wireless devices such as UE 10 to the wireless network 1. NN 12 includes one or more processors DP 12A, one or more memories MEM 12B, and one or more transceivers TRANS 12D interconnected via one or more buses. According to an example embodiment, these TRANS 12Ds may include X2 and / or Xn interfaces for performing the example embodiment. Each of the one or more transceivers TRANS 12Ds includes a receiver and a transmitter. The one or more transceivers TRANS 12Ds may optionally be connected to one or more antennas for communicating with UE 10 at least via link 11. One or more memories MEM 12B and computer program code PROG 12C are configured to cause NN 12 to perform one or more operations as described herein using one or more processors DP 12A. NN 12 may communicate with another gNB or eNB or devices such as NN 13, such as via link 16 or link 18. Furthermore, Link 11, Link 16, and / or any other link can be wired, wireless, or both, and can implement, for example, an X2 or Xn interface. Additionally, Link 11 and / or Link 16 and / or Link 18 can be connected to other network devices, such as, but not limited to, Figure 6 The NN 12 is an NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 device. It can perform the functions of MME (Mobility Management Entity) or SGW (Serving Gateway), such as user plane functions and / or access management functions for LTE and similar functions for 5G or 6G.

[0039] NN 13 can be used for WiFi, Bluetooth, or other wireless devices associated with mobility function devices such as AMF or SMF. Furthermore, NN 13 may include NR / 5G / 6G Node B, or may include evolved NB base stations, such as primary or secondary node base stations (e.g., for NR or LTE LTE) communicating with NN 12 and / or UE 10 and / or Wireless Network 1. NN 13 includes one or more processors DP 13A, one or more memories MEM 13B, one or more network interfaces, and one or more transceivers TRANS 13D interconnected via one or more buses. According to an example embodiment, these network interfaces of NN 13 may include X2 and / or Xn interfaces for performing the example embodiment. Each of the one or more transceivers TRANS 13D includes a receiver and a transmitter optionally connectable to one or more antennas. The one or more memories MEM 13B include computer program code PROG 13C. For example, the one or more memories MEM 13B and computer program code PROG 13C are configured to cause NN 13 to perform one or more operations described herein, together with the one or more processors DP 13A. NN 13 can use, for example, link 11, link 16, link 18 or another link to communicate with another mobility function device and / or eNB (such as NN 12 and UE 10 or any other device). Figure 6 Link 16 or link 18 shown can be used to communicate with NN12. These links can be wired, wireless, or a combination of both, and can implement, for example, an X2 or Xn interface. Furthermore, as mentioned above, link 11 and / or link 16 and / or link 18 can traverse other network devices, such as, but not limited to, those described above. Figure 6 NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 and other NCE / MME / SGW equipment.

[0040] Figure 6 One or more buses of the device can be address buses, data buses, or control buses, and can include any interconnection mechanism, such as a series of lines on a motherboard or integrated circuit, fiber optic or other optical communication devices, wireless channels, etc. For example, one or more transceivers TRANS 12D, TRANS 13D, and / or TRANS 10D can be implemented as remote radio heads (RRHs), where other components of the NN 12 are physically located at a different location from the RRH, and these devices can include one or more buses, which may be partially implemented by fiber optic cables, to connect other components of the NN 12 to the RRH.

[0041] It should be noted that, although Figure 6Network nodes such as NN 12 and NN 13 are shown, but any of these nodes may be incorporated into, or may be included in, an eNodeB, eNB or gNB for LTE and NR, and may still be configured to perform the example embodiments.

[0042] It should also be noted that while the description herein refers to the functions being performed by a “cell,” it should be clear that these functions are actually performed by the gNB and / or user equipment and / or mobility management function equipment that forms the cell. Furthermore, a cell constitutes part of a gNB, and each gNB may include multiple cells.

[0043] Wireless Network 1 or any network that it may represent may include or exclude NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14, which may include Network Control Element (NCE) functions, Mobility Management Entity (MME) / Serving Gateway (SGW) functions, Serving Gateway (SGW) functions, Mobility Management Entity (MME) and / or Serving Gateway (SGW) functions, User Data Management (UDM) functions, Policy Control (PCF) functions, Access and Mobility Management (AMF) functions, Session Management (SMF) functions, Location Management (LMF) functions, and / or Authentication Server (AUSF) functions, and provide connectivity to another network (e.g., a telephone network and / or a data communication network (e.g., the Internet)), and be configured to perform any 5G, 6G, and / or NR operations in addition to or as a substitute for other standard operations performed at the time of this application. NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 can be configured to perform operations according to the example embodiments in LTE, NR, 5G, 6G, and / or any standards-based communication technology being implemented or discussed at the time of this application. Furthermore, it should be noted that the operations according to the example embodiments performed by NN 12 and / or NN 13 can also be performed at NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14.

[0044] NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 includes one or more processors DP 14A, one or more memory MEM 14B, and (multiple) network interfaces (N / WI / F), which are interconnected via one or more buses coupled to link 13 and / or link 16 and / or link 18. According to an example embodiment, these network interfaces may include X2 and / or Xn interfaces for performing the example embodiment. One or more memory MEM 14B includes computer program code PROG 14C. The one or more memory MEM 14B and computer program code PROG 14C are configured, together with one or more processors DP 14A, to cause NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 to perform one or more operations that may be required to support the operation according to the example embodiment.

[0045] Note that NN 12 and / or NN 13 and / or UE 10 can be configured (e.g., based on standard implementations, etc.) to perform Location Management Function (LMF) functionality. LMF functionality can be embodied in any of these network devices or other devices associated with them. Furthermore, at least as described below, LMF (such as...) Figure 6 The MME / SGW / UDM / PCF / AMF / SMF / LMF14 LMF) can be co-located with UE 10, such as with Figure 6 The NN 12 and / or NN 13 are separated for performing operations according to the example embodiments disclosed herein.

[0046] Wireless Network 1 can achieve network virtualization, which is the process of combining hardware and software network resources and network functions into a single software-based managed entity (virtual network). Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is classified as external, combining many networks or parts of networks into virtual units, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities created by network virtualization are still implemented to some extent using hardware such as processors DP10, DP12A, DP13A and / or DP14A and memory MEM10B, MEM 12B, MEM 13B and / or MEM 14B, and such virtualized entities also produce technical effects.

[0047] Computer-readable storage devices MEM 10B, MEM 12B, MEM 13B, and MEM 14B can be of any type suitable for the local technical environment and can be implemented using any suitable data storage technology, such as semiconductor-based memory devices, flash memory, magnetic storage devices and systems, optical storage devices and systems, fixed memory, and removable memory. Computer-readable storage devices MEM 12B, MEM 13B, and MEM 14B can be means for performing storage functions. As a non-limiting example, processors DP10, DP12A, DP13A, and DP14A can be of any type suitable for the local technical environment and can include one or more of general-purpose computers, special-purpose computers, microprocessors, digital signal processors (DSPs), and processors based on multi-core processor architectures. Processors DP10, DP12A, DP13A, and DP14A can be components for performing functions, such as controlling UE 10, NN 12, NN 13, and other functions as described herein.

[0048] Typically, various embodiments of any of these devices may include, but are not limited to, cellular phones (such as smartphones), tablets, personal digital assistants (PDAs) with wireless communication capabilities, portable computers with wireless communication capabilities, image capture devices (such as digital cameras with wireless communication capabilities), gaming devices with wireless communication capabilities, music storage and playback devices with wireless communication capabilities, internet devices that allow wireless internet access and browsing, tablets with wireless communication capabilities, and portable units or terminals that include a combination of these functions.

[0049] Furthermore, various embodiments of any of these devices can be used with any other node of this type associated with a UE vehicle, an aerial platform station, or a ground network or any type of drone radio or aircraft or other air vehicle or vessel traveling on water (such as a ship).

[0050] Step 1: RLC in the RPU provides enhanced data volume information. Each RPU provides the MAC (-low) with enhanced data volume information related to the data to be transmitted. That is, it provides not only the amount of data to be transmitted in the RLC / PDCP (-low), but also more detailed information, such as the size of each individual buffered RLC PDU, RLCSDU, and RLC SDU segment. If there is data buffered at the PDCP, the enhanced data volume information may also include the size information of the (cascaded) PDCP PDUs, PDCP control PDUs, etc., to be transmitted.

[0051] As a specific embodiment of the present invention, enhanced data volume information may be provided only if it does not exceed a certain data volume value. For example, each RPU may report the size of each individual buffered RLC PDU, RLC SDU, RLC SDU segment, (cascaded) PDCP PDU, etc., only for the first T bytes of data to be (re)transmitted in RLC / PDCP.

[0052] Alternatively or additionally, according to exemplary embodiments of the invention, each RPU may provide the MAC (-low) with a set of preferred data volume requests or a set of preferred data volume allocations based on the set of sizes of each individual buffered data unit. For example, suppose an RPU contains the following RLC PDU, RLC SDU, and RLC SDU segments to be (re)transmitted: - One 400-byte RLC SDU segment; - Two RLC PDUs, each 1500 bytes in size; - Two RLC SDUs, each 930 bytes in size.

[0053] Note: The list above reflects the order in which buffered data units need to be transmitted, i.e., RLC SDU segments are transmitted first, followed by RLC PDUs, and finally RLC SDUs.

[0054] Then, according to an exemplary embodiment of the invention, the RPU can send a signal to the MAC (-low) to indicate the following preferred data volume request: - Data volume request #1 (bytes): 400 + RLC header size; - Data volume request #2 (bytes): 400 + RLC header size + 1500 * 2 = 3400 + RLC header size; - Data volume request #3 (bytes): 400 + RLC header size + 1500*2 + 2*(930 + RLC header size) = 5260 + 3*RLC header size.

[0055] Step 2: Use the enhanced data volume information to request data transfer from different RPUs. According to an exemplary embodiment of the invention, when determining how to split the allocated TB size among different RPUs, the MAC (-low) uses enhanced data volume information and / or data volume requests from each RPU. Although this concept is primarily intended to help the MAC (-low) split resources in a transport block among different RPUs within an FPS, it can also be extended to support splitting TBs between FPS and APS.

[0056] According to an exemplary embodiment of the present invention, when requesting data from the RLC in each RPU to construct a TB, the MAC (-low) can determine: - Request the data volume from the RLC strictly according to the enhanced data volume information and / or the data volume requested, and perform padding subsequently, for example, in cases where the RLC does not deliver the exact amount of the requested data; or - The data requested from the RLC does not strictly follow the enhanced data volume information and / or the data volume requested (e.g., to match the TBS allocation). In this case, the RLC may deliver less data than requested by the MAC (-low), in which case the MAC (-low) must perform zero padding; or, zero padding may be performed by the RLC in the RPU.

[0057] As an alternative to padding at the RLC (or not delivering the exact amount of data requested by MAC (-low), when the RLC buffer has more data, the RLC in the corresponding RPU can also segment the RLC PDU, RLC SDU, or RLCSDU segments to be (re)transmitted to match the amount of data allocated by MAC (-low).

[0058] Furthermore, according to exemplary embodiments of the present invention, the above methods can also be used in combination. For example, the amount of data requested from the RPU is not allowed to exceed a certain threshold. When the amount is below the threshold, the RPU can fill the allocated amount of data with zero padding and / or segmentation; when the amount exceeds the threshold, zero padding is handled by MAC (-low). This threshold can be based on the RLC header size.

[0059] Step 3: Send a signal to the gNB using the enhanced data volume information to indicate the enhanced buffer status information. Following a similar approach to BSR in the traditional NR specification, according to an example embodiment of the present invention, after constructing the TB, the MAC (-low) determines the enhanced buffer state information based on the enhanced data volume information and / or data volume requests provided by each RPU and the data volume information that may come from the APS.

[0060] The UE reports enhanced buffer status information to the gNB in ​​the enhanced buffer status report (eBSR).

[0061] Enhanced buffer status information can be reported for each RPU, each LCG, or even each UE based on information received from different RPUs using MAC (-low).

[0062] When the reporting granularity is lower than the UE granularity, this information can also indicate which RPU / LCG or radio processing units and / or how many RPU / LCG or radio processing units the reported data volume request or status applies to.

[0063] Based on eBSR, gNB can allocate the optimal TB to UE, thereby minimizing RPU-level segmentation.

[0064] Figure 5 A signaling diagram according to an example embodiment of the present invention is shown.

[0065] Figure 5 The signaling diagram illustrates a detailed description of one possible implementation of the proposed concept.

[0066] Figure 5 The steps include: 1. The RPU determines the augmented data volume information and / or data volume request, and transmits this information to the MAC (-low).

[0067] According to an exemplary embodiment of the present invention, examples of data volume information may include: a. The amount of data to be transmitted (retransmitted) in the RPU - The size of each RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, PDCP control PDU, etc., to be retransmitted in the RPU. This signaling can be limited to a specific buffer threshold T. That is, the RPU reports the size of the first y RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc., to be retransmitted in the RPU, where: - The sum of the sizes of the first y RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, and PDCP control PDUs to be transmitted in the RPU is less than T; and - The sum of the sizes of the first y+1 RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc., to be transmitted in the RPU is greater than T.

[0068] b. As an alternative to or supplement to providing size information for each individual buffered RLC PDU, RLC SDU, RLC SDU segment, PDCPPDU, PDCP control PDU, etc., to be transmitted (retransmitted) in the RPU, the RPU can provide information on one or more preferred data volume requests. For example, the RPU can request: - Minimum data volume request required for the first RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, and control PDCP PDU to be transmitted (retransmitted) in the transmission RPU; - The second data volume request required for the first m RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, control PDCP PDUs, etc. to be transmitted (retransmitted) in the transmission RPU; - The maximum data volume request required to transmit the first n RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, control PDCP PDUs, etc. to be (re)transmitted in the RPU.

[0069] In the above example, l < m < n, and in a possible implementation, n = y. It should be noted that although the above example considers three data volume requests, any number of data volume requests can be transmitted from the RPU to the MAC (-low) to represent the boundaries between possible segments, buffered data units, and / or PDUs, thereby avoiding fragmentation.

[0070] Compared with signaling the size of each buffered RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, PDCP control PDU, etc. to be (re)transmitted in the RPU, the main advantage of using a data volume request is that it can reduce signaling overhead. For example, instead of signaling the size of the n RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. to be (re)transmitted in the RPU, the RPU can signal m (m < n) data volume requests, where the number of bits used to signal the size of the RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. is the same as or at least comparable to the number of bits used to signal the data volume requests.

[0071] 2. The process of step 1 is executed in parallel by each RPU.

[0072] 3. The gNB schedules UL grant for the UE.

[0073] 4. After decoding the UL grant, the PHY sends a signal to the MAC (-low) to indicate the allocated transport block size (TBS): - It should be noted that steps 1 and 2 can be executed before the UE receives the UL grant (as Figure 5 shown). However, these steps can also be executed due to the UE receiving the UL grant. In this case, upon receiving and decoding the UL grant, the PHY in the UE sends a signal to the MAC (-low) to indicate the TBS allocation, thereby triggering the determination and signaling of enhanced data volume information and / or data volume requests in the higher layers of each RPU to construct the transport block.

[0074] 5. Based on the enhanced data volume information and / or data volume requests received in steps 1 / 2, and based on the TBS allocated in steps 3 / 4, the MAC (-low) determines how to "split" the allocated TBS among the active RPUs.

[0075] 6. MAC (-low) instructs the RPU to deliver a certain amount of data.

[0076] - In one possible implementation, the amount of data allocated by the MAC (-low) must correspond to one of the data amount requests indicated by the corresponding RPU in step 1 / 2; - In another possible implementation, the amount of data allocated by MAC (-low) can be any value and may not correspond to any data volume request indicated by the corresponding RPU in step 1 / 2.

[0077] 7. Repeat step 6 for each selected RPU.

[0078] 8. Subsequently, the RPU delivers a set of RLC SDUs and / or RLC SDU segments to the MAC (-low).

[0079] - In one possible implementation according to an exemplary embodiment of the present invention, the amount of data allocated by the MAC (-low) may correspond to one of the data volume requests indicated by the corresponding RPU in step 1 / 2. In this case, the RPU may not need to perform segmentation or zero-padding, and may deliver to the MAC (-low) a set of RLC SDUs and / or existing SDU segments, the combined size of which matches the allocated data volume; - In another implementation of the exemplary embodiment of the present invention, the amount of data allocated by MAC (-low) may not correspond to any data volume request indicated by the corresponding RPU in step 1 / 2. In this case, the RPU may not be able to accommodate an integer number of RLC PDUs, RLC SDUs, existing RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. to be (re)transmitted within the amount of data allocated by MAC (-low). Therefore, the RPU may perform one or a combination of the following operations: i. Perform (re)segmentation on the RLC PDU, RLC SDU or existing RLC SDU segment to be (re)transmitted to match the amount of data allocated by MAC (-low); ii. Perform padding to match the amount of data allocated by the MAC (-low); iii. Send data to MAC (-low) in a quantity smaller than the amount requested by MAC (-low) in step 5 / 6: - It should be noted that the operations in items i and iii above are supported by the current NR specification (for a given logical channel), while the operation in item ii may require some changes compared to the current NR specification and / or UE implementation.

[0080] When delivering RLC SDUs and / or sets of RLC SDU segments to the MAC (-low), the RPU may also transmit updated enhanced data volume information and / or data volume requests to determine the enhanced buffer status information to be transmitted to the gNB via signaling (as described in more detail in step 10 below).

[0081] 9. In steps 6 / 7, the process of step 8 is executed in parallel by each selected RPU.

[0082] 10. Upon receiving an RLC SDU and / or RLC SDU segment to be included in the TB, the MAC (-low) may first determine the enhanced buffer status information to be transmitted to the gNB via signaling.

[0083] - Enhanced buffer status information may include: i. The size of each individual buffered RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, PDCP control PDU, etc., to be transmitted from one or more RPUs; ii. (Multiple) Preferred transport block size allocation To determine the augmented buffer status information after the TB is constructed, the MAC (-low) may only need the augmented data volume information (including data volume requests) delivered by each RPU before the data delivery in steps 8 / 9. In other cases, after the data delivery in steps 8 / 9, the MAC (-low) may require the RPU to deliver at least some augmented data volume information (including data volume requests). In the latter case, this information may be transmitted along with the RLC SDUs and / or SDU / segments to be transmitted in the TB, as explained in step 8.

[0084] - Enhanced buffer status information (size and / or data volume requests of buffered RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, etc.) can be reported to the gNB by RPU, by LCG, or even by UE based on the corresponding information received from different RPUs by MAC (-low).

[0085] - When the reporting granularity is lower than the UE granularity, this information can also indicate which radio processing units or RPUs / LCGs the reported enhanced buffer status information (which may include data volume requests) applies to and / or how many radio processing units or RPUs / LCGs it applies to.

[0086] 11. Then, in step 6 / 7, MAC (-low) can continue to construct the TB by assembling RLC SDUs and / or RLC SDU segments from all selected RPUs. MAC (-low) can perform padding while constructing the TB (e.g., using option iii in step 8b, if implemented correctly).

[0087] Note that the order of steps 10 and 11 can be interchanged, or these two steps can be performed in parallel. For example, MAC (-low) can first assemble the RLC SDU and / or SDU segments into the TB, then determine the enhancement buffer status information and include the corresponding enhancement buffer status report in the TB.

[0088] 12. Then TB is passed to PHY, where… 13. …processed by the PHY layer prior to the following, including, for example, multiplexing with UCI, channel coding, modulation, mapping to previous symbols and spatial layers… 14. …. Use the resources (time, frequency) allocated by the gNB in ​​step 3 to transmit over the air interface (before).

[0089] 15. Enhanced buffer status information transmitted in the eBSR can be used by the UL scheduler in the gNB to issue new UL authorizations, etc.

[0090] Note that when phrases like "MAC(-low) request from RPU" or "RPU delivery to MAC(-low)" are used in the description of exemplary embodiments of the invention, this may imply direct communication and / or information exchange between the MAC(-low) and each RPU. However, in another embodiment, communication and / or information exchange between the MAC(-low) and each RPU can occur indirectly via the PDCP(-high). Essentially, when data packets are routed to different RPUs, the PDCP(-high) can maintain a record of the PDCP PDUs delivered to the RLC in each RPU, and may also maintain a record of the RLC SDUs awaiting retransmission in each RPU (where RLC AM support is also required, for example). In this way, for example, if a UE implementation is assumed to have the PDCP(-high) and MAC(-low) running on the same CPU while the RPUs run on separate CPUs, data volume information can be provided by the PDCP(-high) without the need for IPC. Furthermore, the RPU, conceived as a dedicated HW processing unit, will operate at a fixed CPU clock at any given time, thus providing clear visibility into when certain PDUs are “ready” or, more specifically, whether certain PDUs are SDUs or PDUs.

[0091] Note that the use of a MAC, MAC (-low), or media access control unit that performs any of the operations disclosed herein is not limiting. It is proposed that any operation instructed to be performed by a MAC-low or media access control unit as disclosed herein, according to exemplary embodiments of the invention, may alternatively or additionally be performed by at least one processor that executes instructions stored in non-transitory memory incorporated into the device (such as a communication network device).

[0092] The advantages of the exemplary embodiments of the present invention include at least the following: - Enhancing buffer state information and / or data volume requests can limit the need for segmentation in RLC, which can simplify L2 implementation: - Example embodiments of the present invention enable UE implementations where RLC in FPS does not support segmentation. In such cases, if the transport block size allocated to the RPU does not match the size(s) of the PDU(s) to be transmitted, zero-padding may be required, potentially leading to unnecessary overhead. According to example embodiments of the present invention, this overhead can be avoided.

[0093] - Note that the proposed enhanced BSR scheme according to the exemplary embodiments of the present invention can be designed for situations where the gNB has sufficient time to process the eBSR and issue a UL grant between two consecutive UL transmissions. For example, this can work in the case of fixed TDD with, for example, a DDDSU frame structure, where there is a minimum of 2.5 ms (for a 30 kHz subcarrier spacing) between two consecutive UL transmissions. Assuming that the UE can support faster processing times in 6G compared to 5G, this should be a feasible scenario. Furthermore, assuming the enhanced BSR is used for XR-type services where XR frames are transmitted over several UL transmissions, the eBSR can be provided along with the first transmission including data from one XR frame and used to optimally schedule resources in the remaining UL transmissions.

[0094] For example, according to an exemplary embodiment of the invention, the UE first allocates resources in slot n for transmitting a first TB of data from an XR frame. This can be based on a CG, pre-scheduled, or dedicated grant (DG) issued based on an SR (depending on the gNB implementation). In slot n, the UE also transmits an eBSR including information about the buffered data in bytes, as well as the size of a single buffered PDU, data volume requests, etc. Based on the eBSR, the gNB can determine the optimal TBS to schedule in subsequent UL transmissions. This can be useful, especially when no new data arrives at the UE buffer and the remaining UL transmissions occur (this may be the case for XR services with a fixed frame arrival rate). This still requires pausing the UL transmission between the UL transmission with the eBSR and the next UL transmission to ensure the gNB has sufficient time to process the information and issue grants accordingly. Again, assuming fast UE and gNB processing times in 6G, this should be a feasible scenario because the minimum time between an uplink slot with enhanced buffer state information (eBSR) and an uplink slot with an UL transmission scheduled based on eBSR is expected to be much smaller than the typical XR frame period of the time in this application.

[0095] Figure 7 A method that can be performed by an apparatus according to an example embodiment of the present invention is shown.

[0096] Figure 7 This demonstrates that it can be made by, but is not limited to, network devices (e.g., such as...). Figure 6 The operations performed by the device (UE 10) in the example. Figure 7 As shown in box 710, information on the augmented data volume of data buffered at at least one processing unit of the device is determined. Figure 7 As shown in box 720, the enhanced data volume information includes at least one of the following: a set of sizes of individual buffered data units of at least one processing unit of the device, or a set of preferred data volume allocations based on the set of sizes of individual buffered data units. Then, as Figure 7 As shown in box 730, based on this determination, enhanced data volume information is transmitted to network nodes of the communication network.

[0097] According to the example embodiments described in the preceding paragraphs, the enhanced data volume information is used to determine how to divide the allocated transport block size between at least two processing units in at least one processing unit to avoid or limit at least one of splitting or padding.

[0098] According to the example embodiments described in the preceding paragraphs, enhanced data volume information is used to determine the size of the transport block to be allocated to the device in order to avoid or limit at least one of segmentation or padding.

[0099] According to the example embodiments described in the above paragraphs, the set of preferred data volume allocations representing preferred allocation thresholds includes at least one of the following: a first data volume allocation required to transmit a minimum number of buffered data units consisting of at least one data unit, a second data volume allocation required to transmit a second number of buffered data units (the second number is greater than the minimum number), or a third data volume allocation required to transmit a third number of buffered data units (the third number is greater than the second number).

[0100] According to the example embodiments described in the above paragraphs, the third number of data units is the maximum number of data units whose cumulative size is less than or equal to the buffer data threshold.

[0101] According to the example embodiment described in the preceding paragraphs, when data units are buffered in the transmission buffer of at least one processing unit, the size of a single buffered data unit is provided in a precise order and only for buffered data units whose cumulative size is less than or equal to a buffer threshold.

[0102] According to the example embodiments described in the preceding paragraphs, the buffer data unit is at least one of the following: a radio link control service data unit, a radio link control service data unit segment, a radio link control state packet data unit, a packet data control protocol service data unit, a packet data control protocol data packet data unit, or a packet data control protocol control packet data unit waiting to be transmitted or retransmitted in the at least one processing unit of the apparatus.

[0103] According to the example embodiments described in the preceding paragraphs, information is transmitted according to each of the at least one processing unit of the apparatus, according to a logical channel group, or according to the apparatus, based on enhanced information received from each of the at least one processing unit of the apparatus.

[0104] According to the example embodiments described in the preceding paragraphs, a data volume that strictly follows the enhanced data volume information is requested from at least one processing unit, and then padding is performed if at least one processing unit does not deliver the exact amount of the requested data, or a data volume that does not strictly follow the enhanced data volume information is requested from at least one processing unit.

[0105] According to the example embodiments described in the preceding paragraphs, padding is performed to match the requested amount of data, segmentation of buffered data units is performed to match the requested amount of data, or a set of buffered data units with a cumulative size less than or equal to the requested amount of data is delivered.

[0106] According to the example embodiments described in the preceding paragraphs, at least one processing unit performs at least one of the following: matching the requested data volume by zero padding or segmentation to achieve at least one preferred allocation threshold, and the at least one preferred allocation threshold is based on at least one of the radio link control header size or the number of bytes.

[0107] According to the example embodiments described in the preceding paragraphs, enhanced buffer status information is reported to network nodes in an enhanced buffer status report based on enhanced data volume information, wherein the enhanced buffer status information is reported for at least one radio processing unit, at least one logical channel group, or user equipment.

[0108] According to the example embodiments described in the preceding paragraphs, the reporting granularity is lower than that of the user equipment, and the information indicates which radio processing units or logical channel groups the buffer status report applies to and / or how many radio processing units or logical channel groups it applies to.

[0109] According to the example embodiments described in the above paragraphs, the amount of data requested from at least one radio processing unit is not allowed to exceed a preferred allocation threshold.

[0110] According to the example embodiments described in the preceding paragraphs, the device is embodied in a user equipment of a communication network.

[0111] A non-transitory computer-readable medium (such as Figure 5 MEM 10B in the middle), storing program code (such as Figure 6 In PROG10C), the program code is generated by at least one processor (such as...). Figure 6 DP 10A in the above paragraph is executed to perform at least the operations described in the preceding paragraph.

[0112] According to the above exemplary embodiments of the present invention, an apparatus (such as...) is provided. Figure 6 UE 10 in the image), the device includes: for determining (e.g. Figure 6 A component that provides enhanced data volume information for data buffered at at least one processing unit of a device by one or more transceivers 10D, MEM 10B, PROG 10C, and DP 10A, wherein the enhanced data volume information includes at least one of the following: the set of sizes of each individual buffered data unit of the at least one processing unit of the device, or based on each individual buffered data unit (e.g., Figure 6 A preferred data volume allocation set for a set of sizes of one or more transceivers 10D, MEM 10B, PROG 10C, and DP 10A; and a set for transmitting enhanced data volume information (such as...) based on this determination. Figure 6A component that connects one or more transceivers (10D, MEM 10B, PROG 10C, and DP 10A) to network nodes in a communication network.

[0113] In the example aspect of the invention according to the preceding paragraph, at least the components for determining, buffering, and transmitting include those encoded with a computer program (such as...). Figure 6 Non-transitory computer-readable media (such as PROG 10C) Figure 6 (MEM 10B in the text), this computer program can be generated by at least one processor (such as...) Figure 6 Execute DP 10A in the middle.

[0114] Furthermore, according to exemplary embodiments of the present invention, circuitry is provided for performing the operations disclosed herein according to exemplary embodiments of the present invention. This circuitry may include any type of circuitry, including content encoding circuitry, content decoding circuitry, processing circuitry, image generation circuitry, data analysis circuitry, etc. Furthermore, this circuitry may include discrete circuitry, application-specific integrated circuits (ASICs) and / or field-programmable gate arrays (FPGAs), as well as processors specifically configured by software to perform corresponding functions, or dual-core processors having software and corresponding digital signal processors, etc. Additionally, the necessary inputs and outputs of the circuitry, the functions performed by the circuitry, and interconnections (possibly via inputs and outputs) between the circuitry and other components that may include other circuitry are also provided to perform the exemplary embodiments of the present invention described herein.

[0115] According to the exemplary embodiments of the present invention disclosed in this application, the provided "circuit" may include one, more, or all of the following: (a) Hardware circuit implementation only (such as implementation in analog and / or digital circuits only); (b) A combination of hardware circuitry and software, such as (if applicable): (i) A combination of (multiple) analog and / or digital hardware circuits with software / firmware; and (ii) Any portion of the hardware processor(s) having software (including the digital signal processor(s)), software, and memory(s) that work together to enable a device (e.g., a mobile phone or server) to perform various functions, such as the functions or operations disclosed herein according to exemplary embodiments of the invention; and (c) (Multiple) hardware circuits and / or (multiple) processors, such as (multiple) microprocessors or a portion thereof, which require software (e.g., firmware) to function, but may be absent if the operation does not require the software. According to an exemplary embodiment of the present invention, there exists a circuit sufficient to perform at least the novel operations disclosed in this application according to an exemplary embodiment of the present invention; as used herein, "circuit" refers to at least the following: (a) Hardware circuit implementation only (e.g., implementation using only analog and / or digital circuits); and (b) A combination of circuitry and software (and / or firmware), such as (if applicable): (i) a combination of (multiple) processors, or (ii) portions of (multiple) processors / software (including (multiple) digital signal processors), software, and (multiple) memories, which work together to enable a device (e.g., a mobile phone or server) to perform various functions; and (c) Circuits that require software or firmware to function, such as (multiple) microprocessors or a portion thereof, even if the software or firmware does not exist physically.

[0116] This definition of "circuit" applies to all uses of the term in this application (including in any claim). As another example, as used in this application, the term "circuit" will also cover only the implementation of a processor (or processors) or a portion thereof and its accompanying software and / or firmware. The term "circuit" will also cover, for example and if applicable to a particular claim element, baseband integrated circuits or application processor integrated circuits for mobile phones, or similar integrated circuits in servers, cellular network devices, or other network devices.

[0117] Generally, various embodiments can be implemented in hardware or dedicated circuitry, software, logic, or any combination thereof. For example, some aspects may be implemented in hardware, while others may be implemented in firmware or software that can be executed by a controller, microprocessor, or other computing device, but the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flowcharts, or using some other graphical representation, it should be understood that these blocks, apparatuses, systems, techniques, or methods described herein may be implemented in hardware, software, firmware, dedicated circuitry or logic, general-purpose hardware or controllers or other computing devices, or some combination thereof, as non-limiting examples.

[0118] Embodiments of the present invention can be practiced in various components such as integrated circuit modules. The design of integrated circuits is primarily a highly automated process. Complex and powerful software tools can be used to transform logic-level designs into semiconductor circuit designs ready for etching and formation on semiconductor substrates.

[0119] The term "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" should not necessarily be construed as preferred or advantageous over other embodiments. All embodiments described in this detailed description are exemplary embodiments designed to enable those skilled in the art to make or use the invention, and are not intended to limit the scope of the invention as defined by the claims.

[0120] The foregoing description has provided a complete and informative description of the best methods and apparatus currently contemplated by the inventors for carrying out the invention, by way of exemplary and non-limiting examples. However, various modifications and adjustments may become apparent to those skilled in the art when read in conjunction with the accompanying drawings and appended claims, given the foregoing description. Nevertheless, all such and similar modifications to the teachings of the exemplary embodiments of the invention will still fall within the scope of the invention.

[0121] It should be noted that the terms “connection,” “coupling,” or any variation thereof mean any direct or indirect connection or coupling between two or more elements, and may encompass the presence of one or more intermediate elements between two elements that are “connected” or “coupled” together. The coupling or connection between elements can be physical, logical, or a combination thereof. As adopted herein, as several non-limiting and non-exhaustive examples, two elements may be considered “connected” or “coupled” together by using one or more wires, cables, and / or printed electrical connections, and by using electromagnetic energy, such as electromagnetic energy with wavelengths in the radio frequency region, microwave region, and optical (visible and invisible) region.

[0122] Furthermore, some features of the preferred embodiments of the invention can be used advantageously without the need for corresponding use of other features. Therefore, the foregoing description should be considered merely as an illustration of the principles of the invention, and not as a limitation thereof.

Claims

1. An apparatus comprising: At least one processor; as well as At least one non-transitory memory storing instructions, which, when executed by the at least one processor, cause the device to at least: Determine the augmented data volume information of the data buffered at at least one processing unit of the device. The enhanced data volume information includes at least one of the following: a set of sizes of individual buffered data units of the at least one processing unit of the device, or a set of preferred data volume allocations based on the set of sizes of individual buffered data units; as well as Based on the determination, the enhanced data volume information is transmitted to the network node of the communication network.

2. The apparatus according to claim 1, wherein, The enhanced data volume information is used to determine how to split the allocated transport block size among at least two processing units in the at least one processing unit to avoid or limit at least one of segmentation or padding.

3. The apparatus according to claim 1, wherein, The enhanced data volume information is used to determine the size of the transport block to be allocated to the device in order to avoid or limit at least one of segmentation or padding.

4. The apparatus according to claim 1, wherein, The set of preferred data volume allocations represents the preferred allocation thresholds and includes at least one of the following: The initial data allocation required to transmit the minimum number of buffered data units consisting of at least one data unit. A second data volume allocation required to transmit a second number of buffered data units, wherein the second number is greater than the minimum number; or A third data allocation is made for transmitting a third number of buffered data units, the third number being greater than the second number.

5. The apparatus according to claim 4, wherein, The third number of data units is the maximum number of data units whose cumulative size is less than or equal to the buffer data threshold.

6. The apparatus according to claim 1, wherein, The size of each individual buffered data unit is provided in the exact order in which the data units are buffered in the transmission buffer of the at least one processing unit, and is provided only for buffered data units whose cumulative size is less than or equal to the buffer threshold.

7. The apparatus according to claim 1, wherein, The buffered data unit includes at least one of the following: a radio link control service data unit, a radio link control service data unit segment, a radio link control status protocol data unit, a packet data control protocol service data unit, a packet data control protocol data unit, or a packet data control protocol data unit to be transmitted or retransmitted in the at least one processing unit of the device.

8. The apparatus according to claim 1, wherein, Enhanced information received from each of the at least one processing unit of the device, the information being transmitted for each of the at least one processing unit of the device, for each logical channel group, or for each device.

9. The apparatus according to claim 1, wherein, At least one non-transitory memory stores instructions executed by the at least one processor to cause the device to perform at least one of the following: Request a data volume from the at least one processing unit that strictly follows the enhanced data volume information, and subsequently perform padding if the at least one processing unit fails to deliver the exact amount of the requested data; or Request a data volume from the at least one processing unit that does not strictly follow the enhanced data volume information.

10. The apparatus according to claim 1, wherein, At least one non-transitory memory stores instructions executed by the at least one processor to cause the device to perform at least one of the following: Perform padding to match the requested amount of data; Perform segmentation of buffered data units to match the requested data volume; or Deliver a set of buffered data units whose cumulative size is less than or equal to the requested data size.

11. The apparatus according to claim 1, wherein, The at least one processing unit performs at least one of the following: The requested data volume is matched by zero padding or segmentation to achieve at least one preferred allocation threshold, and the at least one preferred allocation threshold is based on at least one of the radio link control header size or the number of bytes.

12. The apparatus according to claim 1, wherein, The at least one non-transitory memory stores instructions executed by the at least one processor, such that the device at least: Based on the enhanced data volume information, the enhanced buffer status information is reported to the network node in the enhanced buffer status report. The enhanced buffer status information is reported to the at least one radio processing unit, to the at least one logical channel group, or to the user equipment.

13. The apparatus according to claim 12, wherein, The granularity of the report is lower than that of the user equipment, and the information therein indicates which radio processing units or logical channel groups the buffer status report applies to and / or how many radio processing units or logical channel groups it applies to.

14. The apparatus according to claim 1, wherein, The at least one non-transitory memory stores instructions executed by the at least one processor, such that the device at least: The amount of data requested from the at least one radio processing unit shall not exceed the preferred allocation threshold.

15. The apparatus according to claim 1, wherein, The device is implemented in the user equipment of the communication network.

16. A method comprising: Determine the augmented data volume information of the data buffered at at least one processing unit of the device. The enhanced data volume information includes at least one of the following: a set of sizes of individual buffered data units of the at least one processing unit of the device, or a set of preferred data volume allocations based on the set of sizes of individual buffered data units; and Based on the determination, the enhanced data volume information is transmitted to the network node of the communication network.

17. The method according to claim 16, wherein, The enhanced data volume information is used to determine how to split the allocated transport block size among at least two processing units in the at least one processing unit to avoid or limit at least one of segmentation or padding.

18. The method according to claim 16, wherein, The enhanced data volume information is used to determine the size of the transport block to be allocated to the device at the network node, in order to avoid or limit at least one of segmentation or padding.

19. The method of claim 16, wherein, The set of preferred data volume allocations represents the preferred allocation thresholds and includes at least one of the following: The initial data allocation required to transmit the minimum number of buffered data units consisting of at least one data unit. A second data volume allocation required to transmit a second number of buffered data units, wherein the second number is greater than the minimum number; or A third data allocation is made for transmitting a third number of buffered data units, the third number being greater than the second number.

20. The method according to claim 19, wherein, The third number of data units is the maximum number of data units whose cumulative size is less than or equal to the buffer data threshold.

21. The method according to claim 16, wherein, The size of each individual buffered data unit is determined according to the exact order in which the data units are buffered in the transmission buffer of the at least one processing unit, and is provided only for buffered data units whose cumulative size is less than or equal to a specific buffer threshold.

22. The method according to claim 16, wherein, The buffered data unit includes at least one of the following: a radio link control service data unit segment, a radio link control state protocol data unit, a packet data protocol control protocol data unit, a packet data unit, a packet data protocol control protocol service data unit, or a packet control protocol data unit to be transmitted or retransmitted in the at least one processing unit of the device.

23. The method according to claim 16, wherein, Enhanced information received from each of the at least one processing unit of the device, the information being transmitted for each of the at least one processing unit of the device, for each logical channel group, or for each device.

24. The method of claim 16, comprising: The system requests a data volume that strictly follows the enhanced data volume information from the at least one processing unit, and then performs padding if the at least one processing unit fails to deliver the exact amount of the requested data; or it requests a data volume that does not strictly follow the enhanced data volume information from the at least one processing unit.

25. The method of claim 16, comprising: Perform padding to match the requested amount of data; Perform segmentation of buffered data units to match the requested amount of data; or Deliver a set of buffered data units whose cumulative size is less than or equal to the requested data size.

26. The method of claim 16, wherein, When the data is below at least one preferred allocation threshold, the at least one radio processing unit is capable of filling the transport block size allocation by at least one of the following: Zero padding or segmentation, The threshold is based on at least one of the following: radio link control header size or number of bytes.

27. The method according to claim 16, wherein, The at least one non-transitory memory stores instructions executed by the at least one processor, such that the device at least: Based on the aforementioned information, the enhanced buffer status information is reported to the network node in the enhanced buffer status report. The enhanced buffer status information is reported to the at least one processing unit, the at least one logical channel group, or the user equipment.

28. The method according to claim 27, wherein, The granularity of the report is lower than that of the user equipment, and the information is assembled to indicate which radio processing units or logical channel groups the buffer status report applies to and / or how many radio processing units or logical channel groups it applies to.

29. The method according to claim 22, wherein, The at least one non-transitory memory stores instructions executed by the at least one processor, such that the device at least: The amount of data requested from the at least one radio processing unit shall not exceed the preferred allocation threshold.

30. The method of claim 16, wherein, The device is implemented in the user equipment of the communication network.

Images