Enhanced uplink scheduling assistence information for 6g hardware-optimized layer 2 design with variable size packet data units

Abstract

In accordance with example embodiments of the invention there is at least a method and apparatus to at least perform determining enhanced data volume information of data that is buffered at at least one processing unit of an apparatus, wherein enhanced data volume information comprises at least one of a set of sizes of single 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 single buffered data units; and based on the determining, transmitting the enhanced data volume information towards a network node of a communication network.

Description

ENHANCED UPLINK SCHEDULING ASSISTENCE INFORMATION FOR 6G HARDWARE-OPTIMIZED LAYER 2 DESIGN WITH VARIABLE SIZE PACKET DATA UNITS TECHNICAL FIELD:

[0001] The teachings in accordance with the exemplary embodiments of this invention relate generally to using enhanced data volume information to request data for transmission from different RPUs and, more specifically, relate to using enhanced data volume information including signaling enhanced buffer status information to request data for transmission from different RPUs. BACKGROUND:

[0002] This section is intended to provide a background or context to the invention that is recited in the claims. The description herein may include concepts that could be pursued, but are not necessarily ones that have been previously conceived or pursued. Therefore, unless otherwise indicated herein, what is described in this section is not prior art to the description and claims in this application and is not admitted to be prior art by inclusion in this section.

[0003] Certain abbreviations that may be found in the description and / or in the Figures are herewith defined as follows: APS Anchor Protocol Stack BSR Buffer Status Report FPS Fast Protocol Stack LCG Logical Channel Group MAC Medium Access Control PBR Prioritised Bit Rate PDCP Packet Data Convergence Protocol PDU Protocol Data Unit PHY Physical LayerRLC Radio Link Control RPU Radio Processing Unit SDAP Service Data Adaptation Protocol SDU Service Data Unit TB Transport Block TBS Transport Block Size

[0004] For the design of 6G radio protocols, a novel approach was suggested which relies on two stacks: 1. One radio protocol stack - the Anchor Protocol Stack (APS) - designed for low bitrate services, coverage (e.g., bit-level optimizations) and reliability (e.g., RLC ARQ); and 2. A second radio protocol stack - the Fast Protocol Stack (FPS) - designed for high bitrate services, where the focus is on a processing-friendly and implementation- friendly design employing the concept of radio processing units (RPU), enabling parallel processing of the radio functions.

[0005] With such an approach, the complex mechanisms and optimizations that are fully justified for low bitrate services need not be used for very high bitrate services.

[0006] Example embodiments of this invention proposes method(s) to address at least these issues and improved operations for such operations. SUMMARY:

[0007] This section contains examples of possible implementations and is not meant to be limiting.

[0008] In another example aspect of the invention, there is an apparatus, such as a user equipment side apparatus, comprising: at least one processor; and at least one non-transitory memory storing instructions, that when executed by the at least oneprocessor, cause the apparatus at least to: determine enhanced data volume information of data that is buffered at at least one processing unit of the apparatus, wherein enhanced data volume information comprises at least one of a set of sizes of single 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 single buffered data units; and based on the determining, transmit the enhanced data volume information towards a network node of a communication network.

[0009] In still another example aspect of the invention, there is a method, comprising: determining enhanced data volume information of data that is buffered at at least one processing unit of an apparatus, wherein enhanced data volume information comprises at least one of a set of sizes of single buffered data units of the at least one processing unit of the apparatus, or a set of preferred data volume allocations representing preferred allocation thresholds; and based on the determining, transmitting the enhanced data volume information towards a network node of a communication network.

[0010] A further example embodiment is an apparatus and a method comprising the apparatus and the method of the previous paragraphs wherein the enhanced data volume information is used to determine how to split an allocated transport block size among at least two of the at least one processing unit to at least one of avoid or limit segmentation or padding, wherein the enhanced data volume information is used to determine the transport block size to be allocated to the apparatus to at least one of avoid or limit segmentation or padding, wherein the set of preferred data volume allocations representing preferred allocation thresholds comprises at least one of a first data volume allocation required for the transmission of a minimum number of buffered data units consisting of at least one data unit, a second data volume allocation required for the transmission of a second number of buffered data units larger than the minimum number of buffered data units, or a third data volume allocation required for the transmission of a third number of buffered data units larger than the second number of buffered data units, wherein the third number of data units is a largest number of data units whose cumulative size is lower or equal than a buffer data threshold, wherein the size of single buffered data units is provided in the exact order as data units are buffered in the transmission buffer of the at least one processing unit, and only for buffered dataunits whose cumulative size is lower or equal to a buffer threshold, wherein buffer data units are at least one of a radio link control service data unit, a radio link control service data unit segment, a radio link control status 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 pending for transmission or retransmission in the at least one processing unit of the apparatus, wherein, the information is transmitted per each of the at least one processing unit of the apparatus, per logical channel group, or per apparatus, based on the enhanced information received from each of the at least one processing unit of the apparatus, wherein there is requesting an amount of data from the at least one processing unit that strictly follows the enhanced data volume information, and perform padding afterwards for a case where the at least one processing unit does not deliver the exact amount of requested data, or requesting an amount of data from the at least one processing unit that does not strictly follow the enhanced data volume information, wherein there is performing padding to match the data amount requested, performing segmentation of buffered data units to match the data amount requested, or delivering a set of buffered data units whose cumulative size is lower or equal than the requested data amount, wherein the at least one processing unit performs at least one of: zero padding or segmentation to match the requested data amount up to at least one preferred allocation threshold, and wherein the at least one preferred allocation threshold is based on at least one of a radio link control header size or a number of bytes, wherein there is reporting, based on the enhanced data volume information, an enhanced buffer status information to the network node in an enhanced buffer status report, wherein the enhanced buffer status information is reported for the at least one radio processing unit, for at least one logical channel group, or for the user equipment, wherein a granularity of the reporting is below that of the user equipment, and wherein the information is indicating to at least one of which or for how many radio processing units or logical channel groups a buffered status report applies, wherein there is not allowing an amount of data requested from the at least one radio processing unit to exceed the preferred allocation threshold, and / or wherein the apparatus is embodied in a user equipment of the communication network.

[0011] A non-transitory computer-readable medium storing program code, the program code executed by at least one processor to perform at least the method as described in the paragraphs above.

[0012] In yet another example aspect of the invention, there is an apparatus comprising: means for determining enhanced data volume information of data that is buffered at at least one processing unit of an apparatus, wherein enhanced data volume information comprises at least one of a set of sizes of single 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 single buffered data units; and means, based on the determining, for transmitting the enhanced data volume information towards a network node of a communication network.

[0013] In accordance with the example embodiments as described in the paragraph above, at least the means for identifying, initiating, and determining comprises a network interface, and computer program code stored on a computer- readable medium and executed by at least one processor.

[0014] A communication system comprising a network side apparatus and a user equipment side apparatus performing operations as described above. BRIEF DESCRIPTION OF THE DRAWINGS:

[0015] The above and other aspects, features, and benefits of various embodiments of the present disclosure will become more fully apparent from the following detailed description with reference to the accompanying drawings, in which like reference signs are used to designate like or equivalent elements. The drawings are illustrated for facilitating better understanding of the embodiments of the disclosure and are not necessarily drawn to scale, in which:

[0016] FIG.1 shows 6G UE Types;

[0017] FIG.2 shows 6G Radio Protocols;

[0018] FIG.3 shows radio processing unit (RPU) Management;

[0019] FIG.4 shows a dual stack operation with a radio processing unit (RPU);

[0020] FIG. 5 shows a signalling diagram in accordance with example embodiments of the invention;

[0021] FIG.6 shows a high level block diagram of various devices used in carrying out various aspects of the invention; and

[0022] FIG.7 shows a method in accordance with example embodiments of the invention which may be performed by an apparatus. DETAILED DESCRIPTION:

[0023] In example embodiments of this invention there is proposed at least a method and apparatus for using enhanced data volume information including signaling enhanced buffer status information to request data for transmission from different RPUs.

[0024] As similarly stated above, for the design of 6G radio protocols, a novel approach was suggested which relies on two stacks: 1. One radio protocol stack - the Anchor Protocol Stack (APS) - designed for low bitrate services, coverage (e.g., bit-level optimizations) and reliability (e.g., RLC ARQ); and 2. A second radio protocol stack - the Fast Protocol Stack (FPS) - designed for high bitrate services, where the focus is on a processing-friendly and implementation- friendly design employing the concept of radio processing units (RPU), enabling parallel processing of the radio functions.

[0025] With such an approach, the complex mechanisms and optimizations that are fully justified for low bitrate services need not be used for very high bitrate services. A simple device may only implement the first stack (APS), possibly removing the need to introduce the equivalent of MTC, NB-IoT and RedCap. A more complex and capable device would implement both stacks. The higher the bitrates the device supports, the larger the number of RPUs the FPS would incorporate, as exemplified in FIG. 1 with three types of UEs depicted.

[0026] FIG.1 shows 6G UE Types. As shown in step 110 of FIG.1 there is a low-cost UE with an Anchor Protocol Stack (APS), a mainstream UE with an Anchor Protocol Stack and a Fast Protocol Stack including multiple, in this case four, Radio Processing Units, and a High-End UE with an Anchor Protocol Stack and a Fast Protocol Stack as shown in step 120 of FIG. 1 including multiple, in this case eight, Radio Processing Units.

[0027] On the transmitter side, one 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 as high up in the radio protocols as possible. An ideal candidate is the 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 performed in parallel on each RPU. An example of such a structure is depicted in FIG.2.

[0028] FIG.2 shows 6G Radio Protocols. As shown in step 210 of FIG.2 there is a Service Data Adaptation Protocol (SDAP) and a Packet Data Convergence Protocol High (PDCP-HI) over an Anchor Protocol Stack (APS) and Fast Protocol Stack (FPS) as shown in step 220 of FIG.2. The Anchor Protocol Stack of FIG.2 including PDCP- LOW, Radio Link Control (RLC), Medium Access Control (MAC) and a Physical Layer (PHY). Further, in FIG.2 the PDCP-Low, RLC, and MAC of the Fast Protocol Stack include several Radio Processing Units (RPUs).

[0029] To maximize the power saving gains made possible by the RPU framework, the number of RPUs that are activated can be adjusted according to the instantaneous bitrate or load to be provided, as exemplified in FIG.3, where a total of four RPUs are assumed to be available.

[0030] FIG. 3 shows radio processing unit (RPU) Management. As shown in step 310 of FIG.3 there is a load transferred over time using multiple RPUs as shown in step 320 of FIG.3, some are idle while others are active.

[0031] Depending on whether the RPUs share a common memory and how they are activated, it is possible that some RPU management schemes would require specific mechanisms to be introduced in standards. For instance, if the RPUs operate on segregated memory resources, it is likely that each RPU would then host its own transmission and reception windows, thus impacting sequence numbers and status reports management. Conversely, RPUs operating on shared resources would allow common windows to be used, with no impact to sequence numbers or status reports.

[0032] Being always present, the APS is a logical host for the control plane functions such as idle mode, connect mode and related configurations of the radio resource control (RRC). By containing all control plane (CP) functions within the APS, not only is the FPS free to focus on user plane transfer for a simplified design, but it need not be active when the bitrate requirements are low.

[0033] Buffer Status Report (BSR) is a well-known MAC procedure that tells the network how much data the UE has buffered for transmission. The BSR of the APS is expected to follow that of previous generations (let us call it A-BSR), while for FPS, a new format is expected in order to: 1. facilitate operation with hardware optimized L2 implementation allowing much higher bit rates; 2. as a consequence of the above, possibly cope with fixed size PDU per RPU;3. potentially reporting the amount of data buffered per RPU. In example embodiment of this invention, there is proposed an enhanced mechanism for deriving and reporting to the gNB advanced UL scheduling assistance information in case of variable PDU size per RPU.

[0034] Herein is presented the baseline operation with the proposed APS and FPS architecture in accordance with example embodiments of the invention, and assume the following as closest prior art of the proposed idea based on what has been specified and / or discussed earlier: - 6G dual stack radio protocol with anchor protocol stack (APS) and fast protocol stack (FPS) with Radio Processing Units (RPU) to handle high data rates; - Concatenation of IP packets (if supported) may be done at PDCP-high (i.e., outside RPU) or at PDCP-low (i.e., within RPU) with the assumption data splitting at PDCP layer (PDCP concatenation considered in NR already). - PDCP-low may also apply encryption / ciphering / integrity protection (splitting functions within a protocol layer may be considered as obvious); - At each transmission time interval (TTI), on request by MAC(-low), an RPU delivers to MAC(-low) a set of RLC PDUs that are multiplexed in one TB (since LTE, MAC has been requesting data from upper layers); - Each RPU may be required to provide indication of buffered data to MAC(-low) for data volume determination (for BSR) at MAC (comparable to MAC requesting data volume information from each PDCP entity).

[0035] One example of dual stack operation with RPU is illustrated in FIG.4.

[0036] FIG.4 shows a dual stack operation with a radio processing unit (RPU). As shown step 410 in FIG. 4 there is an RRC and an SDAP providing SRB and twoDRBs, respectively. As shown in step 420 of FIG. 4 the flow from the RRC and an SDAP is provided to several PDCP-HI then to an APS or an FPS, respectively, as shown in step 430 of FIG.4. The APS and the FPS as shown in step 430 of FIG.4 each include a PDCP-LOW, RLC, and MAC-HI. In FIG.4 the FPS includes several radio processing units (RPUs). Then, as an example as shown in FIG. 4 these flows all go to a MAC- low as shown in step 440 of FIG.4and then to the PHY as shown in step 450 of FIG. 4.

[0037] Potential problem of “prior art” solution: - MAC(-low) only knows the total amount of data pending for transmission in each RPU. This may result in excessive segmentation of RLC SDUs in each RPU.

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

[0039] Pros of “prior art” solution: - Minimize changes as compared to NR implementation.

[0040] Cons of “prior art” solution: - Each RPU may still needs to perform real time segmentation when MAC is building the TB; - Segmentation overhead (and complexity) may increase.

[0041] Before describing the example embodiments as disclosed herein in detail, reference is made to FIG.6 for illustrating a simplified block diagram of various electronic devices that are suitable for use in practicing the example embodiments of this invention.

[0042] FIG. 6 shows a block diagram of one possible and non-limiting exemplary system in which the example embodiments may be practiced. In FIG.6, a user equipment (UE) 10 is in wireless communication with a wireless network 1 or network, 1 as in FIG.6. The wireless network 1 or network 1 as in FIG.6 can comprise a communication network such as a mobile network e.g., the mobile network 1 or first mobile network as disclosed herein. Any reference herein to a wireless network 1 as in FIG.6 can be seen as a reference to any wireless network as disclosed herein. Further, the wireless network 1 as in FIG. 6 can also comprises hardwired features as may be required by a communication network. A UE is a wireless, typically mobile device that can access a wireless network. The UE, for example, may be a mobile phone (or called a "cellular" phone) and / or a computer with a mobile terminal function. For example, the UE or mobile terminal may also be a portable, pocket, handheld, computer- embedded or vehicle-mounted mobile device and performs a language signaling and / or data exchange with the RAN.

[0043] The UE 10 includes one or more processors DP 10A, one or more memories MEM 10B, and one or more transceivers TRANS 10D interconnected through 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 optics or other optical communication equipment, and the like. The one or more transceivers TRANS 10D which can be optionally connected to one or more antennas for communication to NN 12 and NN 13, respectively. The one or more memories MEM 10B include computer program code PROG 10C. The UE 10 communicates with NN 12 and / or NN 13 via a wireless link 11 or 16.

[0044] The NN 12 (NR / 5G / 6G Node B, an evolved NB, or LTE device) is a network node such as a master or secondary node base station (e.g., for NR or LTE long term evolution) that communicates with devices such as NN 13 and UE 10 of FIG.6. The NN 12 provides access to wireless devices such as the UE 10 to the wireless network 1. The NN 12 includes one or more processors DP 12A, one or more memories MEM 12B, and one or more transceivers TRANS 12D interconnected through one ormore buses. In accordance with the example embodiments these TRANS 12D can include X2 and / or Xn interfaces for use to perform the example embodiments. Each of the one or more transceivers TRANS 12D includes a receiver and a transmitter. The one or more transceivers TRANS 12D can be optionally connected to one or more antennas for communication over at least link 11 with the UE 10. The one or more memories MEM 12B and the computer program code PROG 12C are configured to cause, with the one or more processors DP 12A, the NN 12 to perform one or more of the operations as described herein. The NN 12 may communicate with another gNB or eNB, or a device such as the NN 13 such as via link 16 or link 18. Further, the link 11, link 16 and / or any other link may be wired or wireless or both and may implement, e.g., an X2 or Xn interface. Further the link 11 and / or link 16 and / or link 18 may be through other network devices such as, but not limited to an NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 device as in FIG.6. The NN 12 may perform functionalities of an MME (Mobility Management Entity) or SGW (Serving Gateway), such as a User Plane Functionality, and / or an Access Management functionality for LTE and similar functionality for 5G or 6G.

[0045] The NN 13 can be for WiFi or Bluetooth or other wireless device associated with a mobility function device such as an AMF or SMF, further the NN 13 may comprise a NR / 5G / 6G Node B or possibly an evolved NB a base station such as a master or secondary node base station (e.g., for NR or LTE long term evolution) that communicates with devices such as the NN 12 and / or UE 10 and / or the wireless network 1. The 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 through one or more buses. In accordance with the example embodiments these network interfaces of NN 13 can include X2 and / or Xn interfaces for use to perform the example embodiments. Each of the one or more transceivers TRANS 13D includes a receiver and a transmitter that can optionally be connected to one or more antennas. The one or more memories MEM 13B include computer program code PROG 13C. For instance, the one or more memories MEM 13B and the computer program code PROG 13C are configured to cause, with the one or more processors DP 13A, the NN 13 to perform one or more of the operations as described herein. The NN 13 may communicate with another mobility function device and / oreNB such as the NN 12 and the UE 10 or any other device using, e.g., link 11 or link 16 or link 18 or another link. The link 16 or link 18 as shown in FIG.6 can be used for communication with the NN12. These links maybe wired or wireless or both and may implement, e.g., an X2 or Xn interface. Further, as stated above the link 11 and / or link 16 and / or link 18 may be through other network devices such as, but not limited to an NCE / MME / SGW device such as the NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 of FIG.6.

[0046] The one or more buses of the device of FIG.6 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 optics or other optical communication equipment, wireless channels, and the like. For example, the one or more transceivers TRANS 12D, TRANS 13D and / or TRANS 10D may be implemented as a remote radio head (RRH), with the other elements of the NN 12 being physically in a different location from the RRH, and these devices can include one or more buses that could be implemented in part as fiber optic cable to connect the other elements of the NN 12 to a RRH.

[0047] It is noted that although FIG.6 shows a network nodes such as NN 12 and NN 13, any of these nodes may can incorporate or be incorporated into an eNodeB or eNB or gNB such as for LTE and NR, and would still be configurable to perform example embodiments.

[0048] Also it is noted that description herein indicates that “cells” perform functions, but it should be clear that the gNB that forms the cell and / or a user equipment and / or mobility management function device that will perform the functions. In addition, the cell makes up part of a gNB, and there can be multiple cells per gNB.

[0049] The wireless network 1 or any network it can represent may or may not include a NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 that may include (NCE) network control element functionality, MME (Mobility Management Entity) / SGW (Serving Gateway) functionality, and / or serving gateway (SGW), and / or MME (Mobility Management Entity) and / or SGW (Serving Gateway) functionality, and / oruser data management functionality (UDM), and / or PCF (Policy Control) functionality, and / or Access and Mobility Management Function (AMF) functionality, and / or Session Management (SMF) functionality, and / or Location Management Function (LMF), and / or Authentication Server (AUSF) functionality and which provides connectivity with a further network, such as a telephone network and / or a data communications network (e.g., the Internet), and which is configured to perform any 5G, 6G, and / or NR operations in addition to or instead of other standard operations at the time of this application. The NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 is configurable to perform operations in accordance with example embodiments in any of an LTE, NR, 5G, 6G, and / or any standards based communication technologies being performed or discussed at the time of this application. In addition, it is noted that the operations in accordance with example embodiments, as performed by the NN 12 and / or NN 13, may also be performed at the NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14.

[0050] The NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 includes one or more processors DP 14A, one or more memories MEM 14B, and one or more network interfaces (N / W I / F(s)), interconnected through one or more buses coupled with the link 13 and / or link 16 and / or link 18. In accordance with the example embodiments these network interfaces can include X2 and / or Xn interfaces for use to perform the example embodiments. The one or more memories MEM 14B include computer program code PROG 14C. The one or more memories MEM14B and the computer program code PROG 14C are configured to, with the one or more processors DP 14A, cause the NCE / MME / SGW / UDM / PCF / AMF / SMF / LMF 14 to perform one or more operations which may be needed to support the operations in accordance with the example embodiments.

[0051] It is noted that that the NN 12 and / or NN 13 and / or UE 10 can be configured (e.g. based on standards implementations etc.) to perform functionality of a Location Management Function (LMF). The LMF functionality may be embodied in any of these network devices or other devices associated with these devices. In addition, an LMF such as the LMF of the MME / SGW / UDM / PCF / AMF / SMF / LMF 14 of FIG. 6, as at least described below, can be co-located with UE 10 such as to be separate fromthe NN 12 and / or NN 13 of FIG. 6 for performing operations in accordance with example embodiments as disclosed herein.

[0052] The wireless Network 1 may implement network virtualization, which is the process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network. Network virtualization involves platform virtualization, often combined with resource virtualization. Network virtualization is categorized as either external, combining many networks, or parts of networks, into a virtual unit, or internal, providing network-like functionality to software containers on a single system. Note that the virtualized entities that result from the network virtualization are still implemented, at some level, using hardware such as processors DP10, DP12A, DP13A, and / or DP14A and memories MEM 10B, MEM 12B, MEM 13B, and / or MEM 14B, and also such virtualized entities create technical effects.

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

[0054] In general, various embodiments of any of these devices can include, but are not limited to, cellular telephones such as smart phones, tablets, personal digital assistants (PDAs) having wireless communication capabilities, portable computers having wireless communication capabilities, image capture devices such as digitalcameras having wireless communication capabilities, gaming devices having wireless communication capabilities, music storage and playback appliances having wireless communication capabilities, Internet appliances permitting wireless Internet access and browsing, tablets with wireless communication capabilities, as well as portable units or terminals that incorporate combinations of such functions.

[0055] Further, the various embodiments of any of these devices can be used with a UE vehicle, a High Altitude Platform Station, or any other such type node associated with a terrestrial network or any drone type radio or a radio in aircraft or other airborne vehicle or a vessel that travels on water such as a boat.

[0056] Step 1: RLC in RPU provides enhanced data volume information

[0057] Each RPU provides MAC(-low) with enhanced data volume information on the data pending for transmission. I.e., not only the amount of data pending for transmission in RLC / PDCP(-low), but also more detailed information such as the size of single buffered RLC PDUs, RLC SDUs and RLC SDU segments. If there is data buffered at PDCP, enhanced data volume information may also include information about the size of pending (concatenated) PDCP PDUs, PDCP control PDUs, etc.

[0058] As a special embodiment in accordance with example embodiments of the invention, enhanced data volume information could be provided only up to a certain data volume value, e.g., only for the first T Bytes of data pending for (re)transmission in RLC / PDCP, each RPU reports the size of single buffered RLC PDUs, RLC SDUs, RLC SDUs segments, (concatenated) PDCP PDUs, etc.

[0059] Alternatively, or in addition to that, in accordance with example embodiments of the invention, each RPU may provide MAC(-low) with a set of preferred data volume requests or preferred data volume allocations based on the set of sizes of single buffered data units. For example, let us assume the following RLC PDUs, RLC SDUs and RLC SDU segments are pending for (re)transmission in one RPU:- 1 RLC SDU segment of 400 bytes; - 2 RLC PDUs of size 1500 bytes (each); - 2 RLC SDUs of size 930 bytes (each),

[0060] NOTE: the list above reflects the order in which buffered data units need to be transmitted, i.e. RLC SDU segments first, then RLC PDUs and finally RLC SDUs.

[0061] Then, in accordance with example embodiments of the invention, the RPU may signal to MAC(-low) the following preferred data volume requests: - 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.

[0062] Step 2: Enhanced data volume information is used to request data for transmission from different RPUs

[0063] In accordance with example embodiments of the invention, the enhanced data volume information and / or data volume requests from each RPU are then used by MAC(-low) when determining how to split the allocated TB size among different RPUs. Though primarily thought for helping MAC(-low) when splitting resources in a transport block among different RPUs within the FPS, the idea can be extended to support TB splitting between FPS and APS.

[0064] In accordance with example embodiments of the invention, when requesting data from RLC in each RPU to build the TB, MAC(-low) may decide to- Request an amount of data from RLC that strictly follows the enhanced data volume information and / or data volume requests and perform padding afterwards, e.g., in case RLC does not deliver the exact amount of requested data, or - Request an amount of data from RLC that does not strictly follow the enhanced data volume information and / or data volume requests (e.g., to match the TBS allocation). In this case, RLC may either deliver less data than requested by MAC(- low), in which case MAC(-low) must perform zero padding, or zero-padding can be performed by RLC in the RPU.

[0065] As an alternative to padding at RLC (or to not delivering the exact amount of requested data by MAC(-low)), when RLC has more data buffered, RLC in the corresponding RPU may also segment an RLC PDU, RLC SDU or RLC SDU segment pending for (re)transmission to match the amount of data allocated by MAC(- low).

[0066] Further, in accordance with example embodiments of the invention it can also be a mix of the above, for instance, the amount of data requested from an RPU is not allowed to exceed a certain threshold. Below that threshold, the RPU can take care of filling the allocation by zero padding and / or segmentation. Beyond that threshold, zero padding is handled by MAC(-low). The threshold can be based on the RLC header size.

[0067] Step 3: Enhanced data volume information is used to signal enhanced buffer status information to the gNB

[0068] In a similar way as done for BSR in legacy NR specifications, in accordance with example embodiments of the invention, MAC(-low) determines enhanced buffer status information after construction of the TB based on the enhanced data volume information and / or the data volume requests provided by each RPU, and potentially data volume information from APS.

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

[0070] Enhanced buffer status information could be reported per RPU, per LCG, or even per UE, based on information received by MAC(-low) from different RPUs.

[0071] When the granularity of the reporting is below that of the UE, the information can also indicate to which and / or for how many RPUs / LCGs or radio processing units the data volume request or a status reported applies.

[0072] Based on eBSR, gNB can allocate the optimal TB to the UE minimizing segmentation at RPU level.

[0073] FIG. 5 shows a signalling diagram in accordance with example embodiments of the invention.

[0074] A detailed description of a possible implementation of the proposed idea is illustrated in the signalling diagram in FIG.5.

[0075] Steps of FIG.5 include as follows: 1. RPU determines enhanced data volume information and / or data volume requests and transmit the information to MAC(-low). Example of data volume information in accordance with example embodiments of the invention can be: a. Amount of data pending for (re)transmission in the RPU - Size of each RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, PDCP control PDU, etc. pending for (re)transmission in the RPU. This signaling could be limited up to a specific buffer threshold T. I.e., the RPU reports the size of the first yRLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. pending for (re)transmission in the RPU, where: - the sum of the sizes of the first y RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. pending for (re)transmission in the RPU is smaller 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. pending for (re)transmission in the RPU is larger than T. b. As an alternative or in addition to providing information on the size of single buffered RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. pending for (re)transmission in the RPU, the RPU may provide information on one or more preferred data volume requests. For example, the RPU could request: - a minimum data volume request required to transmit the first l RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, control PDCP PDUs, etc. pending for (re)transmission in the RPU; - a second data volume request required to transmit the first m RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, control PDCP PDUs, etc. pending for (re)transmission in the RPU; - a maximum data volume request required to transmit the first n RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, control PDCP PDUs, etc. pending for (re)transmission in the RPU.

[0076] In the example above, l < m < n, while in one possible implementation, n = y. Please note that while three data volume requests are considered in the example above, any number of data volume requests could be transmitted from the RPU to MAC(-low) to represent the boundaries between possible segments, buffer data units, and / or PDUs to avoid segmentation.

[0077] The main advantage of using data volume requests as compared to signaling the size of each buffered RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, PDCP control PDU, etc. pending for (re)transmission in the RPU, is the potentially reduced signaling overhead. E.g., instead of signaling the size of n RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. pending for (re)transmission in the RPU, the RPU can instead signal m (m < n) data volume requests, where the number of bits needed to signal the size of an RLC PDU, RLC SDU, RLC SDU segment, PDCP PDU, PDCP control PDU, etc. is the same as, or at least comparable to, the number of bits needed to signal a data volume request. 2. The procedure of step 1 is performed in parallel by every RPU. 3. The gNB schedules an UL grant to the UE. 4. After decoding the UL grant, PHY signals to MAC(-low) the allocated transport block size (TBS): - Note that steps 1 and 2 may be performed prior to the UE receiving an UL grant (as depicted in FIG.5). However, these steps may also be performed as a consequence of the UE receiving an UL grant. In this case, upon receiving and decoding the UL grant, PHY in the UE signals the TBS allocation to MAC(-low), which triggers upper layers in each RPU to determine and signal enhanced data volume information and / or data volume requests for the purpose of building the transport block. 5. Based on the enhanced data volume information and / or data volume requests received at step 1 / 2, and on the TBS allocated in steps 3 / 4, MAC(-low) determines how to “split” the allocated TBS among the active RPUs. 6. MAC(-low) instructs the RPU to deliver a certain amount of data.- In one possible implementation, the amount of data allocated by MAC(-low) must correspond to one of the data volume requests indicated by the corresponding RPU in step 1 / 2; - In yet another possible implementation, the amount of data allocated by MAC(- low) can be any value and may not correspond to any of the data volume requests indicated by the corresponding RPU in step 1 / 2. 7. The procedure of step 6 is repeated for each one of the selected RPUs. 8. The RPU then delivers to MAC(-low) as set of RLC SDUs and / or RLC SDU segments. - In one possible implementation in accordance with example embodiments of the invention, the amount of data allocated by 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 neither need to perform segmentation nor zero padding and can deliver to MAC(-low) a set of RLC SDUs and / or already existing SDU segments whose combined size matches the allocated data amount; - In yet another implementation in accordance with example embodiments of the invention, the amount of data allocated by MAC(-low) may not correspond to any of the data volume requests indicated by the corresponding RPU in step 1 / 2. In this case, the RPU may not be able to fit an integer number of RLC PDUs, RLC SDUs, already existing RLC SDU segments, PDCP PDUs, PDCP control PDUs, etc. pending for (re)transmission in the allocated data amount by MAC(-low). Therefore, the RPU may perform one (or a combination of) the following operations: i. Perform (re)segmentation of an RLC PDU, RLC SDU or an already existing RLC SDU segment pending for (re)transmission, so to match the amount of data allocated by MAC(-low), ii. Perform padding to match the amount of data allocated by MAC low,iii. Deliver to MAC(-low) an amount of data which is lower than what requested by MAC(-low) in step 5 / 6: - Note that operation according to i and iii above is already supported by current NR specifications (for a given logical channel), while operation according to ii may require some changes as compared to current NR specifications and / or UE implementation. While delivering a set of RLC SDUs and / or RLC SDU segments to MAC(-low), the RPU may also transmit updated enhanced data volume information and / or data volume requests, to be used for determination of the enhanced buffer status information to be signaled to the gNB (as described in more detail is step 10 below). 9. The procedure of step 8 is performed in parallel by each of the selected RPUs in step 6 / 7. 10. Upon receiving the RLC SDUs and / or RLC SDU segments to be included in the TB, MAC(-low) may first determine the enhanced buffer status information to be signaled to the gNB. - Enhanced buffer status information may include: i. Size of single buffered RLC PDUs, RLC SDUs, RLC SDUs segments, PDCP PDUs, PDCP control PDUs, etc. pending for (re)transmission from one or more RPUs, ii. Preferred transport block size allocation(s) To determine the enhanced buffer status information after the TB is constructed, MAC(- low) may only need to use the enhanced data volume information (including data volume requests) delivered by each RPU prior to data delivery in steps 8 / 9. In other cases, MAC(-low) may need the RPU to deliver at least some of the enhanced data volume information (including data volume requests) after data delivery in steps 8 / 9.In the latter case, this information may be conveyed together with the RLC SDUs and / or SDU / segments to be transmitted in a TB, as explained in step 8. - The enhanced buffer status information (size of buffered RLC PDUs, RLC SDUs, RLC SDU segments, PDCP PDUs, etc. and / or data volume requests) could be reported to the gNB per RPU, per LCG, or even per UE - based on the corresponding information received by MAC(-low) from different RPUs. - When the granularity of the reporting is below that of the UE, the information can also indicate to which and / or for how many radio processing units or RPUs / LCGs the reported enhanced buffer status information (possibly including data volume request) applies. 11. MAC(-low) may then proceed to construct the TB by assembling the RLC SDUs and / or RLC SDU segments from all the selected RPUs in step 6 / 7. MAC(-low) may perform padding while building the TB (e.g., in case of implementation option iii in step 8b is used). Note that the order of steps 10 and 11 could be interchanged, or the two steps could be performed in parallel, e.g. MAC(-low) may first proceed to assembly the RLC SDUs and / or SDU segments into a TB before determining the enhanced buffer status information and including the corresponding enhanced buffer status report in the TB. 12. The TB is then passed to PHY where … 13. … it passes through PHY layer processing including, for example, multiplexing with UCI, channel coding, modulation, mapping to symbols and spatial layers before … 14. …. being transmitted over the air interface using the resources (time, frequency) allocated by the gNB in step 3.15. Enhanced buffers status information conveyed in the eBSR may be used by the UL scheduler in the gNB to issue a new UL grant, and so on.

[0078] Note that when in description of example embodiments of the invention there is written “MAC(-low) request from RPU”, or “RPU delivers to MAC(-low)”, this could imply direct communication and / or exchange of information between MAC(- low) and each RPU. However, in yet another implementation, communication and / or information exchange between MAC(-low) and each RPU may happen indirectly via PDCP(-high). Essentially, when routing data packets to different RPUs, PDCP(-high) may keep a record of the PDCP PDUs that are delivered to RLC in each RPU, and possibly also of RLC SDUs pending for retransmission in each RPU (in case, e.g., RLC AM also needs to be supported). In this way, e.g., data volume information can be provided by PDCP(-high) without need for IPC if it is assumed an UE implementation where PDCP(-high) and MAC(-low) run on the same CPU, while RPUs are running on separate CPUs. Furthermore, an RPU envisioned as a dedicated HW processing unit will operate under a fixed CPU clock at any given time, therefore giving clear visibility as to the timing of when certain PDUs are “ready” or more specifically if they are SDUs or PDUs.

[0079] It is noted that the use of a MAC, MAC(-low), or medium access control unit performing any operations disclosed herein is non-limiting. It is submitted that any operations in accordance with example embodiments of the invention, which are indicated as performed by a MAC-low or a medium access control unit as disclosed herein, may be instead or in addition be performed by at least one processor executing instructions stored on a non-transitory memory incorporated into an apparatus, such as in a communication network device.

[0080] Advantages in accordance with example embodiments of the invention include at least: - Enhanced buffer status information and / or data volume requests may limit the need for segmentation in RLC, which could simplify L2 implementation:- Example embodiments of the invention can enable UE implementation with no support of segmentation at RLC in FPS. In this case, if the allocated portion of the transport block size to an RPU does not match the size(s) of the pending PDUs, zero padding may be needed, which may result in unnecessary overhead. This can be avoided in accordance with example embodiments of the invention. - Note that the proposed enhanced BSR scheme in accordance with example embodiments of the invention can be designed for situations where the gNB has enough time to process the eBSR and issue an UL grant between two consecutive UL transmissions. This could work, for example, in case of fixed TDD with, e.g., DDDSU frame structure, where there is a minimum of 2.5 ms (for 30 kHz sub-carrier spacing) between two consecutive UL transmissions. Assuming UEs may support faster processing time in 6G as compared to 5G, this should be a feasible scenario. Also, assuming enhanced BSR is used for XR-type of traffic, with an XR frame that is transmitted over several UL transmissions, the eBSR could be provided with the first transmission including data of one XR frame and used for optimally scheduling resources in the remaining UL transmissions.

[0081] For example, in accordance with example embodiments of the invention, the UE is first allocated resources in slot n for the transmission of the first TB with data from an XR frame. This could be based on CG, pre-scheduling, or dedicated grant (DG) issued based on SR (depending on gNB implementation). In slot n, the UE also transmits the eBSR including information on the buffered data in bytes, as well as the size of single buffered PDUs, data volume requests, etc. Based on the eBSR, the gNB can determine the optimal TBS to be scheduled in the following UL transmissions. This can be useful, especially when no new data arrives in the UE buffer while the remaining UL transmissions take place (which could be the case for XR traffic with fixed frame arrival rate). This still requires a pause in UL transmissions between the UL transmission with eBSR and the next UL transmission to ensure the gNB has enough time to process the information and issue a grant accordingly. Again, assuming fast UE and gNB processing time in 6G, this should be a feasible scenario as the minimum time between the uplink slot with enhanced buffer status information (eBSR)and the uplink slot with UL transmission scheduled based on eBSR is expected to be much smaller than the typical XR frame periodicity, as of the time of this application.

[0082] FIG.7 shows a method in accordance with example embodiments of the invention which may be performed by an apparatus.

[0083] FIG.7 illustrates operations which may be performed by a device such as, but not limited to, a network device (e.g., the UE 10 as in FIG.6). As shown in block 710 of FIG. 7 there is determining enhanced data volume information of data that is buffered at at least one processing unit of an apparatus. As shown in block 720 of FIG. 7, wherein enhanced data volume information comprises at least one of a set of sizes of single 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 single buffered data units. Then as shown in block 730 of FIG. 7 there is, based on the determining, transmitting the enhanced data volume information towards a network node of a communication network.

[0084] In accordance with the example embodiments as described in the paragraph above, wherein the enhanced data volume information is used to determine how to split an allocated transport block size among at least two of the at least one processing unit to at least one of avoid or limit segmentation or padding.

[0085] In accordance with the example embodiments as described in the paragraphs above, wherein the enhanced data volume information is used to determine the transport block size to be allocated to the apparatus to at least one of avoid or limit segmentation or padding.

[0086] In accordance with the example embodiments as described in the paragraphs above, wherein the set of preferred data volume allocations representing preferred allocation thresholds comprises at least one of a first data volume allocation required for the transmission of a minimum number of buffered data units consisting of at least one data unit, a second data volume allocation required for the transmission of a second number of buffered data units larger than the minimum number of buffereddata units, or a third data volume allocation required for the transmission of a third number of buffered data units larger than the second number of buffered data units.

[0087] In accordance with the example embodiments as described in the paragraphs above, wherein the third number of data units is a largest number of data units whose cumulative size is lower or equal than a buffer data threshold.

[0088] In accordance with the example embodiments as described in the paragraphs above, wherein the size of single buffered data units is provided in the exact order as data units are buffered in the transmission buffer of the at least one processing unit, and only for buffered data units whose cumulative size is lower or equal to a buffer threshold.

[0089] In accordance with the example embodiments as described in the paragraphs above, wherein buffer data units are at least one of a radio link control service data unit, a radio link control service data unit segment, a radio link control status 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 pending for transmission or retransmission in the at least one processing unit of the apparatus.

[0090] In accordance with the example embodiments as described in the paragraphs above, wherein, the information is transmitted per each of the at least one processing unit of the apparatus, per logical channel group, or per apparatus, based on the enhanced information received from each of the at least one processing unit of the apparatus.

[0091] In accordance with the example embodiments as described in the paragraphs above, wherein there is requesting an amount of data from the at least one processing unit that strictly follows the enhanced data volume information, and perform padding afterwards for a case where the at least one processing unit does not deliver the exact amount of requested data, or requesting an amount of data from the at least one processing unit that does not strictly follow the enhanced data volume information.

[0092] In accordance with the example embodiments as described in the paragraphs above, wherein there is performing padding to match the data amount requested, performing segmentation of buffered data units to match the data amount requested, or delivering a set of buffered data units whose cumulative size is lower or equal than the requested data amount.

[0093] In accordance with the example embodiments as described in the paragraphs above, wherein the at least one processing unit performs at least one of: zero padding or segmentation to match the requested data amount up to at least one preferred allocation threshold, and wherein the at least one preferred allocation threshold is based on at least one of a radio link control header size or a number of bytes.

[0094] In accordance with the example embodiments as described in the paragraphs above, wherein there is reporting, based on the enhanced data volume information, an enhanced buffer status information to the network node in an enhanced buffer status report, wherein the enhanced buffer status information is reported for the at least one radio processing unit, for at least one logical channel group, or for the user equipment.

[0095] In accordance with the example embodiments as described in the paragraphs above, wherein a granularity of the reporting is below that of the user equipment, and wherein the information is indicating to at least one of which or for how many radio processing units or logical channel groups a buffered status report applies.

[0096] In accordance with the example embodiments as described in the paragraphs above, wherein there is not allowing an amount of data requested from the at least one radio processing unit to exceed the preferred allocation threshold.

[0097] In accordance with the example embodiments as described in the paragraphs above, wherein the apparatus is embodied in a user equipment of the communication network.

[0098] A non-transitory computer-readable medium (MEM 10B as in FIG. 5) storing program code (PROG 10C as in FIG.6), the program code executed by at leastone processor (DP 10A as in FIG.6) to perform the operations as at least described in the paragraphs above.

[0099] In accordance with an example embodiment of the invention as described above there is an apparatus (UE 10 as in FIG. 6) comprising: means for determining (one or more transceivers 10D; MEM 10B; PROG 10C; and DP 10A as in FIG. 6) enhanced data volume information of data that is buffered at at least one processing unit of an apparatus, wherein enhanced data volume information comprises at least one of a set of sizes of single 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 single buffered (one or more transceivers 10D; MEM 10B; PROG 10C; and DP 10A as in FIG.6) data units; and means, based on the determining, for transmitting (one or more transceivers 10D; MEM 10B; PROG 10C; and DP 10A as in FIG.6) the enhanced data volume information towards a network node of a communication network.

[0100] In the example aspect of the invention according to the paragraph above, wherein at least the means for determining, buffering, and transmitting comprises a non-transitory computer readable medium [MEM 10B as in FIG. 6] encoded with a computer program [PROG 10C as in FIG.6] executable by at least one processor [DP 10A as in FIG.6].

[0101] Further, in accordance with example embodiments of the invention there is circuitry for performing operations in accordance with example embodiments of the invention as disclosed herein. This circuitry can include any type of circuitry including content coding circuitry, content decoding circuitry, processing circuitry, image generation circuitry, data analysis circuitry, etc.). Further, this circuitry can include discrete circuitry, application-specific integrated circuitry (ASIC), and / or field- programmable gate array circuitry (FPGA), etc. as well as a processor specifically configured by software to perform the respective function, or dual-core processors with software and corresponding digital signal processors, etc.). Additionally, there are provided necessary inputs to and outputs from the circuitry, the function performed by the circuitry and the interconnection (perhaps via the inputs and outputs) of the circuitrywith other components that may include other circuitry in order to perform example embodiments of the invention as described herein.

[0102] In accordance with example embodiments of the invention as disclosed in this application this application, the “circuitry” provided can include at least one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); (b) combinations of hardware circuits and software, such as (as applicable): (i) a combination of analog and / or digital hardware circuit(s) with software / firmware; and (ii) any portions of hardware processor(s) with software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions, such as functions or operations in accordance with example embodiments of the invention as disclosed herein); and (c) hardware circuit(s) and or processor(s), such as a microprocessor(s) or a portion of a microprocessor(s), that requires software (e.g., firmware) for operation, but the software may not be present when it is not needed for operation.”

[0103] In accordance with example embodiments of the invention, there is adequate circuitry for performing at least novel operations in accordance with example embodiments of the invention as disclosed in this application, this `circuitry` as may be used herein refers to at least the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry); and(b) to combinations of circuits and software (and / or firmware), such as (as applicable): (i) to a combination of processor(s) or (ii) to portions of processor(s) / software (including digital signal processor(s)), software, and memory(ies) that work together to cause an apparatus, such as a mobile phone or server, to perform various functions); and (c) to circuits, such as a microprocessor(s) or a portion of a microprocessor(s), that require software or firmware for operation, even if the software or firmware is not physically present.

[0104] This definition of `circuitry` applies to all uses of this term in this application, including in any claims. As a further example, as used in this application, the term "circuitry" would also cover an implementation of merely a processor (or multiple processors) or portion of a processor and its (or their) accompanying software and / or firmware. The term "circuitry" would also cover, for example and if applicable to the particular claim element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or other network device.

[0105] In general, the various embodiments may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. For example, some aspects may be implemented in hardware, while other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device, although the invention is not limited thereto. While various aspects of the invention may be illustrated and described as block diagrams, flow charts, or using some other pictorial representation, it is well understood that these blocks, apparatus, systems, techniques or methods described herein may be implemented in, as non-limiting examples, hardware, software, firmware, special purpose circuits or logic, general purpose hardware or controller or other computing devices, or some combination thereof.

[0106] Embodiments of the inventions may be practiced in various components such as integrated circuit modules. The design of integrated circuits is by and large a highly automated process. Complex and powerful software tools are available for converting a logic level design into a semiconductor circuit design ready to be etched and formed on a semiconductor substrate.

[0107] The word "exemplary" is used herein to mean "serving as an example, instance, or illustration." Any embodiment described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments. All of the embodiments described in this Detailed Description are exemplary embodiments provided to enable persons skilled in the art to make or use the invention and not to limit the scope of the invention which is defined by the claims.

[0108] The foregoing description has provided by way of exemplary and non- limiting examples a full and informative description of the best method and apparatus presently contemplated by the inventors for carrying out the invention. However, various modifications and adaptations may become apparent to those skilled in the relevant arts in view of the foregoing description, when read in conjunction with the accompanying drawings and the appended claims. However, all such and similar modifications of the teachings of example embodiments of this invention will still fall within the scope of this invention.

[0109] It should be noted that the terms "connected," "coupled," or any variant thereof, mean any connection or coupling, either direct or indirect, 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 the elements can be physical, logical, or a combination thereof. As employed herein two elements may be considered to be "connected" or "coupled" together by the use of one or more wires, cables and / or printed electrical connections, as well as by the use of electromagnetic energy, such as electromagnetic energy having wavelengths in the radio frequency region, the microwave region and the optical (both visible and invisible) region, as several non-limiting and non-exhaustive examples.

[0110] Furthermore, some of the features of the preferred embodiments of this invention could be used to advantage without the corresponding use of other features. As such, the foregoing description should be considered as merely illustrative of the principles of the invention, and not in limitation thereof.

Claims

CLAIMS What is claimed is:

1. An apparatus, 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 at least to: determine enhanced data volume information of data that is 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 single 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 single buffered data units; and based on the determining, transmit the enhanced data volume information towards a network node of a communication network.

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

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

4. The apparatus of claim 1, wherein the set of preferred data volume allocations representing preferred allocation thresholds comprises at least one of a first data volume allocation required for the transmission of a minimum number of buffered data units consisting of at least one data unit, a second data volume allocation required for the transmission of a second number of buffered data units larger than the minimum number of buffered data units, ora third data volume allocation required for the transmission of a third number of buffered data units larger than the second number of buffered data units.

5. The apparatus of claim 4, wherein the third number of data units is a largest number of data units whose cumulative size is lower or equal than a buffer data threshold.

6. The apparatus of claim 1, wherein the size of single buffered data units is provided in the exact order as data units are buffered in the transmission buffer of the at least one processing unit, and only for buffered data units whose cumulative size is lower or equal to a buffer threshold.

7. The apparatus of claim 1, wherein buffer data units are at least one of a radio link control service data unit, a radio link control service data unit segment, a radio link control status 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 pending for transmission or retransmission in the at least one processing unit of the apparatus.

8. The apparatus of claim 1, wherein, the information is transmitted per each of the at least one processing unit of the apparatus, per logical channel group, or per apparatus, based on the enhanced information received from each of the at least one processing unit of the apparatus.

9. The apparatus of claim 1, wherein at least one non-transitory memory is storing instructions executed by the at least one processor to cause the apparatus to at least one of: request an amount of data from the at least one processing unit that strictly follows the enhanced data volume information, and perform padding afterwards for a case where the at least one processing unit does not deliver the exact amount of requested data, or request an amount of data from the at least one processing unit that does not strictly follow the enhanced data volume information.

10. The apparatus of claim 1, wherein at least one non-transitory memory is storing instructions executed by the at least one processor to cause the apparatus to at least one of: perform padding to match the data amount requested, perform segmentation of buffered data units to match the data amount requested, or deliver a set of buffered data units whose cumulative size is lower or equal than the requested data amount.

11. The apparatus of claim 1, wherein the at least one processing unit performs at least one of: zero padding or segmentation to match the requested data amount up to at least one preferred allocation threshold, and wherein the at least one preferred allocation threshold is based on at least one of a radio link control header size or a number of bytes.

12. The apparatus of claim 1, wherein the at least one non-transitory memory is storing instructions executed by the at least one processor to cause the apparatus at least to: report, based on the enhanced data volume information, an enhanced buffer status information to the network node in an enhanced buffer status report, wherein the enhanced buffer status information is reported for the at least one radio processing unit, for at least one logical channel group, or for the user equipment.

13. The apparatus of claim 12, wherein a granularity of the reporting is below that of the user equipment, and wherein the information is indicating to at least one of which or for how many radio processing units or logical channel groups a buffered status report applies.

14. The apparatus of claim 1, wherein the at least one non-transitory memory is storing instructions executed by the at least one processor to cause the apparatus to at least one of:not allow an amount of data requested from the at least one radio processing unit to exceed the preferred allocation threshold.

15. The apparatus of claim 1, wherein the apparatus is embodied in a user equipment of the communication network.

16. A method, comprising: determining enhanced data volume information of data that is buffered at at least one processing unit of an apparatus, wherein enhanced data volume information comprises at least one of a set of sizes of single 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 single buffered data units; and based on the determining, transmitting the enhanced data volume information towards a network node of a communication network.

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

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

19. The method of claim 16, wherein the set of preferred data volume allocations representing preferred allocation thresholds comprises at least one of a first data volume allocation required for the transmission of a minimum number of buffered data units consisting of at least one data unit, a second data volume allocation required for the transmission of a second number of buffered data units larger than the minimum number of buffered data units, ora third data volume allocation required for the transmission of a third number of buffered data units larger than the second number of buffered data units.

20. The method of claim 19, wherein the third number of data units is a largest number of data units whose cumulative size is lower or equal than a buffer data threshold.

21. The method of claim 16, wherein the size of single buffered data units is provided in the exact order as data units are buffered in the transmission buffer of the at least one processing unit, and only for buffered data units whose cumulative size is lower or equal to the certain buffer threshold value.

22. The method of claim 16, wherein buffer data units are at least one of a radio link control service data unit segment, radio link control status packet data units, packet data protocol control protocol data unit, packet data units, or packet data protocol control protocol service data unit, packet control protocol packet data units pending for transmission or retransmission in the at least one processing unit of the apparatus.

23. The method of claim 16, wherein, the information is transmitted per each of the at least one processing unit of the apparatus, per logical channel group, or per apparatus, based on the enhanced information received from each of the at least one processing unit of the apparatus.

24. The method of claim 16, comprising: requesting an amount of data from the at least one processing unit that strictly follows the enhanced data volume information, and performing padding afterwards for a case where the at least one processing unit does not deliver the exact amount of requested data, or requesting an amount of data from the at least one processing unit that does not strictly follow the enhanced data volume information.

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

26. The method of claim 16, wherein below at least one preferred allocation threshold the at least one radio processing unit can fill a transport block size allocation by at least one of zero padding or segmentation, wherein the threshold is based on at least one of a radio link control header size or a number of bytes.

27. The method of claim 16, wherein the at least one non-transitory memory is storing instructions executed by the at least one processor to cause the apparatus at least to: report based on the information an enhanced buffer status information to the network node in an enhanced buffer status report, wherein the enhanced buffer status information is reported for the at least one processing unit, for at least one logical channel group, or for the user equipment.

28. The method of claim 27, wherein a granularity of the reporting is below that of the user equipment, and wherein the information is indicating to at least one of which or for how many radio processing units or logical channel groups a buffered status report applies.

29. The method of claim 22, wherein the at least one non-transitory memory is storing instructions executed by the at least one processor to cause the apparatus to at least one of: not allow an amount of data requested from the at least one radio processing unit to exceed the preferred allocation threshold.

30. The method of claim 16, wherein the apparatus is embodied in a user equipment of the communication network.

Images