Data status reporting

Abstract

Disclosed is a first apparatus 100 and method of determining the data status for each of a set of radio processing units 110. The method starts by constructing a sub-transport block for each of the r

Description

FIELDS

[0001] Various example embodiments of the present disclosure generally relate to the field of telecommunication and in particular, to apparatuses, methods and computer readable storage medium for data status reporting. BACKGROUND

[0002] In a design of the sixth generation (6G) radio protocols, an approach is suggested which relies on the following two radio protocol stacks: an anchor protocol stack (APS) which is designed for low bitrate services, coverage (e.g., bit-level optimizations) and reliability (e.g., radio link control (RLC) automatic repeat request (ARQ)); and a fast protocol stack (FPS) which is designed for high bitrate services, where the focus is on a processing-friendly and implementation-friendly design employing the concept of radio processing units (RPUs), enabling parallel processing of radio functions. SUMMARY

[0003] In a first aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: determine data status for each of a plurality of radio processing units; construct a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit; construct a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, where data in the plurality of sub-transport blocks is concatenated to construct data of the transport block, and the data status information in the plurality of sub-transport blocks is combined to construct data status information of the transport block; and transmit the transport block to a second apparatus.

[0004] In a second aspect of the present disclosure, there is provided a method at a first apparatus. The method comprises: determining data status for each of a plurality of radio processing units; constructing a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit; constructing a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, where data in the plurality of sub-transport blocks is concatenated to construct data of the transport block, and the data status information in the plurality of sub-transport blocks is combined to construct data status information of the transport block; and transmitting the transport block to a second apparatus.

[0005] In a third aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for determining data status for each of a plurality of radio processing units; means for constructing a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit; means for constructing a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, where data in the plurality of sub-transport blocks is concatenated to construct data of the transport block, and the data status information in the plurality of sub-transport blocks is combined to construct data status information of the transport block; and means for transmitting the transport block to a second apparatus.

[0006] In a fourth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the second aspect.

[0007] In a fifth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: determine data status for each of a plurality of radio processing units; construct a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit; construct a transport block by concatenating a plurality of sub-transport blocks for the plurality of radio processing units; and transmit the transport block to a second apparatus.

[0008] In a sixth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: receive a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and each of the plurality of sub-transport blocks contains data and data status information; and combine the data status information in the plurality of sub-transport blocks.

[0009] In a seventh aspect of the present disclosure, there is provided a method at a first apparatus. The method comprises: determining data status for each of a plurality of radio processing units; constructing a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit; constructing a transport block by concatenating a plurality of sub-transport blocks for the plurality of radio processing units; and transmitting the transport block to a second apparatus.

[0010] In an eighth aspect of the present disclosure, there is provided a method at a second apparatus. The method comprises: receiving a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and each of the plurality of sub-transport blocks contains data and data status information; and combining the data status information in the plurality of sub-transport blocks.

[0011] In a ninth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for determining data status for each of a plurality of radio processing units; means for constructing a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit; means for constructing a transport block by concatenating a plurality of sub-transport blocks for the plurality of radio processing units; and means for transmitting the transport block to a second apparatus.

[0012] In a tenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for receiving a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and each of the plurality of sub-transport blocks contains data and data status information; and means for combining the data status information in the plurality of sub-transport blocks.

[0013] In an eleventh aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the seventh aspect or the eighth aspect.

[0014] In a twelfth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to: construct a transport block, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit; and transmit the transport block to a second apparatus.

[0015] In a thirteenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises at least one processor; and at least one memory storing instructions that, when executed by the at least one processor, cause the second apparatus at least to: receive a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit.

[0016] In a fourteenth aspect of the present disclosure, there is provided a method at a first apparatus. The method comprises: constructing a transport block, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit; and transmitting the transport block to a second apparatus.

[0017] In a fifteenth aspect of the present disclosure, there is provided a method at a second apparatus. The method comprises: receiving a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit.

[0018] In a sixteenth aspect of the present disclosure, there is provided a first apparatus. The first apparatus comprises means for constructing a transport block, where the transport block includes a plurality of sub-transport blocks, and a subtransport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit; and means for transmitting the transport block to a second apparatus.

[0019] In a seventeenth aspect of the present disclosure, there is provided a second apparatus. The second apparatus comprises means for receiving a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit.

[0020] In an eighteenth aspect of the present disclosure, there is provided a computer readable medium. The computer readable medium comprises instructions stored thereon for causing an apparatus to perform at least the method according to the fourteenth or fifteenth aspect.

[0021] It is to be understood that the Summary section is not intended to identify key or essential features of embodiments of the present disclosure, nor is it intended to be used to limit the scope of the present disclosure. Other features of the present disclosure will become easily comprehensible through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0022] Some example embodiments will now be described with reference to the accompanying drawings, where:

[0023] FIG. 1 illustrates an example communication environment in which example embodiments of the present disclosure can be implemented;

[0024] FIGS. 2A to 2C illustrate three types of protocol stack architectures according to some example embodiments of the present disclosure;

[0025] FIG. 3 illustrates a schematic diagram of the relationship between instantaneous load and the number of RPUs according to some example embodiments of the present disclosure;

[0026] FIG. 4A illustrates an example of a radio protocol structure for the case of two LCHs according to some example embodiments;

[0027] FIG. 4B illustrates an example process for a buffer status report (BSR) according to some example embodiments;

[0028] FIG. 5 illustrates a signaling diagram showing an example process for data status reporting according to some example embodiments of the present disclosure;

[0029] FIG. 6 illustrates an example structure of a sub-transport block (TB) for an RPU according to some example embodiments of the present disclosure;

[0030] FIG. 7 illustrates a schematic diagram of an example dual stack operation for TB transmission according to some example embodiments of the present disclosure;

[0031] FIG. 8 illustrates a schematic diagram of another example dual stack operation for TB transmission according to some example embodiments of the present disclosure;

[0032] FIG. 9 illustrates a schematic diagram of yet another example dual stack operation for TB transmission according to some example embodiments of the present disclosure;

[0033] FIG. 10 illustrates a flowchart of a method implemented at a first apparatus according to some example embodiments of the present disclosure;

[0034] FIG. 11 illustrates a flowchart of a method implemented at a first apparatus according to some other example embodiments of the present disclosure;

[0035] FIG. 12 illustrates a flowchart of a method implemented at a second apparatus according to some example embodiments of the present disclosure;

[0036] FIG. 13 illustrates a flowchart of another method implemented at a first apparatus according to some other example embodiments of the present disclosure;

[0037] FIG. 14 illustrates a flowchart of another method implemented at a second apparatus according to some other example embodiments of the present disclosure;

[0038] FIG. 15 illustrates a simplified block diagram of a device that is suitable for implementing example embodiments of the present disclosure; and

[0039] FIG. 16 illustrates a block diagram of an example computer readable medium in accordance with some example embodiments of the present disclosure.

[0040] Throughout the drawings, the same or similar reference numerals represent the same or similar element. DETAILED DESCRIPTION

[0041] Principle of the present disclosure will now be described with reference to some example embodiments. It is to be understood that these embodiments are described only for the purpose of illustration and help those skilled in the art to understand and implement the present disclosure, without suggesting any limitation as to the scope of the disclosure. Embodiments described herein can be implemented in various manners other than the ones described below.

[0042] In the following description and claims, unless defined otherwise, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skills in the art to which this disclosure belongs.

[0043] References in the present disclosure to “one embodiment,” “an embodiment,” “an example embodiment,” and the like indicate that the embodiment described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases are not necessarily referring to the same embodiment. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.

[0044] It shall be understood that although the terms “first,” “second” and the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first element could be termed a second element, and similarly, a second element could be termed a first element, without departing from the scope of example embodiments. As used herein, the term “and / or” includes any and all combinations of one or more of the listed terms.

[0045] As used herein, “at least one of the following: ” and “at least one of ” and similar wording, where the list of two or more elements are joined by “and” or “or”, mean at least any one of the elements, or at least any two or more of the elements, or at least all the elements.

[0046] As used herein, unless stated explicitly, performing a step “in response to A” does not indicate that the step has to be performed immediately after “A” occurs and one or more intervening steps may be included.

[0047] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of example embodiments. As used herein, the singular forms “a”, “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms “comprises”, “comprising”, “has”, “having”, “includes” and / or “including”, when used herein, specify the presence of stated features, elements, and / or components etc., but do not preclude the presence or addition of one or more other features, elements, components and / or combinations thereof.

[0048] As used in this application, the term “circuitry” may refer to one or more or all of the following: (a) hardware-only circuit implementations (such as implementations in only analog and / or digital circuitry) and (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) 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.

[0049] 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 also covers an implementation of merely a hardware circuit or processor (or multiple processors) or portion of a hardware circuit or processor and its (or their) accompanying software and / or firmware. The term circuitry also covers, for example and if applicable to the particular claim element, a baseband integrated circuit or processor integrated circuit for a mobile device or a similar integrated circuit in server, a cellular network device, or other computing or network device.

[0050] As used herein, the term “communication network” refers to a network following any suitable communication standards, such as New Radio (NR), Long Term Evolution (LTE), LTE-Advanced (LTE-A), Wideband Code Division Multiple Access (WCDMA), High-Speed Packet Access (HSPA), Narrow Band Internet of Things (NB-loT) and so on. Furthermore, the communications between a terminal device and a network device in the communication network may be performed according to any suitable generation communication protocols either currently known or to be developed in the future. Embodiments of the present disclosure may be applied in various communication systems. Given the rapid development in communications, there will of course also be future type communication technologies and systems with which the present disclosure may be embodied. It should not be seen as limiting the scope of the present disclosure to only the aforementioned system.

[0051] As used herein, the term “network device” or “network access device” refers to a node in a communication network via which a terminal device accesses the network and receives services therefrom. The network device may refer to a base station (BS) or an access point (AP), for example, a node B (NodeB or NB), an evolved NodeB (eNodeB or eNB), an NR NB (also referred to as a gNB), a Remote Radio Unit (RRU), a radio head (RH), a remote radio head (RRH), a relay, an Integrated Access and Backhaul (IAB) node, a low power node such as a femto, a pico, a non-terrestrial network (NTN) or non-ground network device such as a satellite network device, a low earth orbit (LEO) satellite and a geosynchronous earth orbit (GEO) satellite, an aircraft network device, and so forth, depending on the applied terminology and technology. In some example embodiments, radio access network (RAN) split architecture comprises a Centralized Unit (CU) and a Distributed Unit (DU) at an IAB donor node. An IAB node comprises a Mobile Terminal (IAB-MT) part that behaves like a UE toward the parent node, and a DU part of an IAB node behaves like a base station toward the nexthop IAB node.

[0052] The term “terminal device” refers to any end device that may be capable of wireless communication. By way of example rather than limitation, a terminal device may also be referred to as a communication device, user equipment (UE), a Subscriber Station (SS), a Portable Subscriber Station, a Mobile Station (MS), or an Access Terminal (AT). The terminal device may include, but not limited to, a mobile phone, a cellular phone, a smart phone, voice over IP (VoIP) phones, wireless local loop phones, a tablet, a wearable terminal device, a personal digital assistant (PDA), portable computers, desktop computer, image capture terminal devices such as digital cameras, gaming terminal devices, music storage and playback appliances, vehicle-mounted wireless terminal devices, wireless endpoints, mobile stations, laptop-embedded equipment (LEE), laptop-mounted equipment (LME), USB dongles, smart devices, wireless customer-premises equipment (CPE), an Internet of Things (loT) device, a watch or other wearable, a head-mounted display (HMD), a vehicle, a drone, a medical device and applications (e.g., remote surgery), an industrial device and applications (e.g., a robot and / or other wireless devices operating in an industrial and / or an automated processing chain contexts), a consumer electronics device, a device operating on commercial and / or industrial wireless networks, and the like. The terminal device may also correspond to a Mobile Termination (MT) part of an IAB node (e.g., a relay node). In the following description, the terms “terminal device”, “communication device”, “terminal”, “user equipment” and “UE” may be used interchangeably. [00531 As used herein, the term “resource,” “transmission resource,” “resource block; “physical resource block” (PRB), “uplink resource,” or “downlink resource” may refer to any resource for performing a communication, for example, a communication between a terminal device and a network device, such as a resource in time domain, a resource in frequency domain, a resource in space domain, a resource in code domain, or any other resource enabling a communication, and the like. In the following, unless explicitly stated, a resource in both frequency domain and time domain will be used as an example of a transmission resource for describing some example embodiments of the present disclosure. It is noted that example embodiments of the present disclosure are equally applicable to other resources in other domains.

[0054] As described above, an approach is suggested for the design of 6G radio protocols, which relies on two radio protocol stacks including an APS for low bitrate services and an FPS for high bitrate services. With such an approach, complex mechanisms and optimizations that are justified for low bitrate services may not be used for very high bitrate services. A simple device may only have implement the first stack (APS), possibly removing a need to introduce equivalent of machine type communication (MTC), Narrowband Internet of Things (NB-IoT) and / or Reduced Capability (RedCap). A more complex and capable device may implement both protocol stacks. The higher the bitrates the device supports, the larger the number of RPUs the FPS may incorporate. Even though the terms “APS” and “FPS” are used in the present disclosure to refer to two (parallel) radio protocol stacks of different types, it is to be understood that other terms may be used, instead, to refer to two separate configurations of radio protocols and radio protocol stacks having at least one characteristic (e.g., the supported highest bitrate) different from one another. The scope of the present disclosure should, thus, not be limited to said two terms.

[0055] In addition, to maximize power saving gains made possible by the RPU framework, the number of RPUs that are activated may be adjusted according to an instantaneous bitrate or load to be provided.

[0056] On a transmitter side, there may be a common layer used for overseeing allocation of incoming protocol data units (PDUs) to each RPU. In order to maximize the number of tasks that can be executed in parallel, the common layer may be located as high up in the radio protocols as possible. The common layer may be located in a higher part of a Packet Data Convergence Protocol (PDCP) layer, 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 while allowing a receiver to re-order service data units (SDUs) coming out of the RPUs.

[0057] Depending on whether the RPUs share a common memory and how they are activated, it is possible that some RPU management schemes may 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, thereby impacting sequence numbers and status reports management. Conversely, RPUs operating on shared resources may allow common windows to be used, with no impact to sequence numbers or status reports.

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

[0059] A buffer status report (BSR) is a well-known medium access control (MAC) procedure that notifies a network how much data the UE has buffered for transmission. The BSR in third Generation Partnership Project (3GPP) systems may be performed for each Logical Channel Group (LCG), which means buffer status information from logical channels (LCHs) that belong to the same LCG needs to be collected before a BSR can be constructed and signalled in uplink (UL).

[0060] Following the principle of the current way of BSR building, to compute the buffer size information to be included in the BSR, an RPU controlling construction of a BSR needs to collect buffer size information from the other RPUs, which may require inter-CPU communication.

[0061] Example embodiments of the present disclosure propose a solution for data status reporting. In this solution, a first apparatus determines data status for each of a plurality of RPUs. The first apparatus constructs a sub-transport block (sub-TB) for each of the plurality of RPUs. The sub-TB includes data from the RPU and data status information of the RPU. The data status information indicates the data status of the RPU.

[0062] This solution allows construction of a sub-TB for each RPU which includes data status information of the RPU. In this way, a need for inter-CPU communications between RPUs may be minimized. Moreover, the proposed solution may be implementation-friendly and easily scalable as the number of RPUs in a device increases.

[0063] FIG. 1 illustrates an example communication environment 100 in which example embodiments of the present disclosure can be implemented.

[0064] In the communication environment 100, a plurality of communication devices, including a first apparatus 110 and a second apparatus 120, may communicate with each other. In some example embodiments, the first apparatus 110 may operate as a terminal device such as a UE, and the second apparatus 120 may operate as a network device (such as a gNB) serving the terminal device.

[0065] In the following, for the purpose of illustration, some example embodiments are described with the first apparatus 110 operating as a terminal device and the second apparatus 120 operating as a network device. However, in some example embodiments, operations described with respect to a terminal device may be implemented at a network device or other devices, and operations described with respect to a network device may be implemented at a terminal device or other devices.

[0066] In some example embodiments, if the first device 110 is a terminal device and the second device 120 is a network device, a link from the second device 120 to the first device 110 is referred to as a DL, while a link from the first device 110 to the second device 120 is referred to as an uplink (UL). In DL, the second device 120 is a transmitting (TX) device (or a transmitter), and the first device 110 is a receiving (RX) device (or a receiver). In UL, the first device 110 is a TX device, and the second device 120 is an RX device. If both the first device 110 and the second device 120 are terminal devices, a link between two terminal devices is referred to as a sidelink (SL). In SL, one of the first and second devices 110 and 120 is a TX device (or a transmitter), and the other of the first and second devices 110 and 120 is an RX device (or a receiver).

[0067] Communications in the communication environment 100 may be implemented according to any proper communication protocol(s), comprising, but not limited to, cellular communication protocols of the first generation (1G), the second generation (2G), the third generation (3G), the fourth generation (4G), the fifth generation (5G), the sixth generation (6G), and the like, wireless local network communication protocols such as Institute for Electrical and Electronics Engineers (IEEE) 802.11 and the like, and / or any other protocols currently known or to be developed in the future. Moreover, the communication may utilize any proper wireless communication technology, comprising but not limited to: Code Division Multiple Access (CDMA), Frequency Division Multiple Access (FDMA), Time Division Multiple Access (TDMA), Frequency Division Duplex (FDD), Time Division Duplex (TDD), Multiple-Input Multiple-Output (MIMO), Orthogonal Frequency Division Multiple (OFDM), Discrete Fourier Transform spread OFDM (DFT-s-OFDM) and / or any other technologies currently known or to be developed in the future.

[0068] It is to be understood that the number and types of apparatuses are shown in FIG. 1 for the purpose of illustration, without suggesting any limitation. The communication environment 100 may include any suitable numbers and types of devices and apparatuses.

[0069] The first apparatus 110 may implement an APS and / or an FPS. FIGS. 2A to 2C shows three types of protocol stack architectures of the first apparatus 110. In an architecture 200A, the first apparatus 110 may operate as a simple device that may only implement the first stack, an APS 230. In an architecture 200B, the first apparatus 110 may operate as a more complex and capable device that may implement both the APS 230 and an FPS 240. Compared with the architecture 200B, in an architecture 200C, a larger number of RPUs are incorporated in the FPS 240 to support higher bitrates. The number of RPUs that are activated may be adjusted according to the instantaneous bitrate or load to be provided, as shown in FIG. 3.

[0070] In some example embodiments, the first apparatus 110 may implement both the APS 230 and the FPS 240 with RPUs to handle high data rates. FIG. 4A shows an example of a radio protocol structure 400A for the case of two LCHs according to some example embodiments. In this example, one LCH 402, denoted by LCH#1, is mapped to the APS 230, and one LCH 404, denoted by LCH#2, is mapped to the FPS 240. 3 RPUs 406, 408 and 410 are shown where one RPU 406, denoted by RPU#1, is used for the APS 230, and two RPUs 408 and 410, denoted by RPU#2 and RPU#3, are used for the FPS 240. It should be noted that the processing in RPU#1 and RPU#2 / 3 may be different.

[0071] FIG. 4B shows an example process 400 for a BSR according to some example embodiments. In the process 400, when data arrives at a PDCP layer, PDCP-High 416 may assign an SN and routes the data packets to the RPUs 406, 408 and 410. At the RPUs 406, 408 and 410, data is buffered, ciphering and integrity protections are performed in parallel (if needed), and a PDCP header is added (including the SN). In some example embodiments, data buffering may occur at PDCP-High 416.

[0072] At each transmission time interval (TTI), on request by a MAC layer (e.g., MAC-Low 412 in FIG. 4A) based on an allocated UL grant, an RPU 406, 408 or 410 may deliver to the MAC layer a sub-TB 418, 420 or 422 including one or more MAC sub-protocol data unit (sub-PDUs). Each sub-PDU contains one or more RLC SDUs and / or RLC SDU segments. The sub-TBs 418, 420 are 422 may be then multiplexed in one transport block (TB) 424. In the case that the MAC functionality is split in MAC-Low 412 and MAC-High 414 as shown in FIG. 4A, some MAC functions (e.g., adding MAC subheader) may be executed in parallel within the RPU 406, 408 or 410 in MAC-High 414 while others (e.g., logical channel prioritization) may be executed at MAC-Low 412 across multiple RPUs 406, 408 and 410.

[0073] Each RPU 406, 408 or 410 may be required to provide an indication of buffered data to MAC-Low 412 for data volume determination for a BSR 426 and / or delay status report (DSR) (comparable to MAC requesting data volume information from each PDCP / RLC entities). The data volume information may be used to determine a buffer size field in the BSR for a corresponding LCG, e.g., LCG#1 or LCG#2. In the example of FIG. 4B, a long BSR format is used where each of the 2 configured LCHs 402 and 404 is mapped to a corresponding LCG, e.g. LCG#1 or LCG#2.

[0074] In various example embodiments, a sub-TB constructed for or by each RPU 406, 408 or 410 includes data status information (for example, a BSR or DSR) indicating data status of the RPU 406, 408 or 410. This data status information may be summed up to determine data status information for a TB, thereby reducing inter-CPU communication and improving processing efficiency. Some example implementations may be described below with reference to FIGS. 5 to 9.

[0075] FIG. 5 illustrates a signaling diagram showing an example communication process 500 between the first apparatus 110 and the second apparatus 120 for data status reporting according to some example embodiments of the present disclosure.

[0076] As shown in FIG. 5, in the process 500, the first apparatus 110 determines (505) data status for each of a plurality of RPUs (e.g., an RPU 406, 408 or 410 in FIGS. 4A and 4B). The data status may include any status related to data, for example a buffer size for the data and remaining transmission time (or remaining time) of the data. In an example, each RPU may compute its own data status (e.g., a buffer size and / or remaining time). Thus, each RPU may only need to compute and report buffer and / or delay status information for data buffered at the corresponding RPU, thereby minimizing the need for inter-CPU communications between RPUs and facilitating scalability of the RPU concept / implementation.

[0077] After the data status is determined, the first apparatus 110 constructs (510) a sub-TB for each of the plurality of RPUs. The sub-TB for an RPU contains data from the RPU. The data from the RPU may be encapsulated in any suitable form. In some example embodiments, the data may be carried in at least one MAC sub-PDU. In an example, the data from the RPU may include one or more MAC sub-PDUs from the corresponding LCH(s), where a LCH may be mapped to one or more RPUs.

[0078] In addition to the data from the RPU, the sub-TB for the RPU contains data status information of the RPU. The data status information indicates the data status of the RPU. In some example embodiments, the data status information of an RPU of the plurality of RPUs may include buffer status information (e.g., a BSR) and / or delay status information (e.g., a DSR) of data associated with the RPU.

[0079] In some example embodiments, the data associated with an RPU may include data buffered at the RPU. In an example, as shown in FIG. 4B, PDCP-Low 417 is within the RPU 406, 408 or 410 and associated with the RPU 406, 408 or 410. Data buffering may be performed at PDCP-Low 417 in the RPU 406, 408 or 410 and no data buffering is performed outside the RPU 406, 408 or 410. In this way, because buffer status information is self-contained in each RPU, buffering at PDCP-Low may improve the efficiency of data status reporting.

[0080] Alternatively, or in addition, the data associated with the RPU may include data buffered at an entity in a layer higher than a layer associated with the RPU. In some example embodiments, each of the plurality of RPUs may be associated with at least one sub-layer of a radio protocol layer. In some example embodiments, it may be possible to perform at least some data buffering at PDCP-High 416 (i.e., outside of an RPU and higher than the layer (e.g. PDCP-Low 417) associated with the RPU) before PDCP SDUs are processed by PDCP-Low 417. In some cases, for example, not all PDCP SDUs can be assigned with a PDCP SN immediately after reception from upper layers. In these cases, data buffered at PDCP-High 416 may be considered when determining the buffer size of one of the RPUs within FPS 240, also referred to as a primary RPU, which may be e.g., RPU#2 408 in FIG. 4B. Therefore, when determining the buffer size and / or remaining time to be included in the RPU-specific BSR and / or DSR, the primary RPU may consider both data buffered at RPU level (e.g. PDCP PDUs) as well as data buffered outside the RPU at PDCP-High 416 (e.g. PDCP SDUs prior to SN determination).

[0081] The data status information of the RPU may be encapsulated in any suitable form. In some example embodiments, the data status information may be carried in a MAC CE such as a BSR MAC CE (for a buffer size) or a DSR MAC CE (for a buffer size and remaining transmission time). FIG. 6 shows an example structure 600 of a sub-TB for an RPU according to some example embodiments of the present disclosure. As shown, an RPU 406, 408 or 410 may construct a sub-TB 606, 608 or 610. One sub-TB 606, 608 or 610 may include one or more MAC sub-PDUs from the corresponding LCH(s), e g. LCH#1 or LCH#2. The sub-TB 606, 608 or 610 may also include a BSR MAC CE 616, 618 or 620 including information about the data buffered at the corresponding RPU 406, 408 or 410 and / or related remaining time information. In addition to the BSR MAC CE 616, 618 or 620, or as an alternative, a sub-TB 606, 608 or 610 may include a DSR MAC CE.

[0082] In some example embodiments, a single RLC entity may be configured for a LCH, and the LCH may be mapped to at least one RPU of the plurality of RPUs. In an example, there may be a single RLC entity configured per LCH even if the LCH is mapped to different RPUs. This is the case illustrated in FIG. 6, where LCH#2 404 has a single RLC entity 602 despite being mapped to two RPUs (RPU#2 408 and RPU#3 410). This implementation option may be practical when RLC operates in Transparent Mode (TM) or in Unacknowledged Mode (UM) without segmentation. In this case, RLC does not need to include a SN in the RLC header, hence no coordination / communication between RPUs is required.

[0083] In some example embodiments, each of the plurality of RPUs may be associated with a RLC entity. For example, when RLC is operating in UM with segmentation or in RLC Acknowledged Mode (AM), coordination between RPUs is required, in which case the implementation option of one RLC entity per RPU in an FPS may be used. In an implementation, a protocol architecture like the one used with dual connectivity and PDCP duplication may be used, and each RPU may be associated with its own RLC entity / leg. Some example embodiments in this regard will be detailed in the following paragraphs.

[0084] According to some example embodiments of the present disclosure, illustrated to as Option 1 in FIG. 5, the data status information for the plurality of RPUs may be summed up by the first apparatus 110 to determine data status information for a TB. As shown, the first apparatus 110 constructs (515) a TB based on a plurality of sub-TBs for the plurality of RPUs, where data in the plurality of sub-TBs is concatenated to construct data of the TB, and the data status information in the plurality of sub-TBs is combined to construct data status information of the TB.

[0085] The buffer status information in the plurality of sub-TBs may be combined in any suitable way. For example, in the example embodiments where the buffer status information indicates a buffer size, the first apparatus 110 may summarize buffer sizes indicated in the plurality of sub-TBs, as combined buffer status information. In example embodiments where the delay status information indicates buffer status information and related remaining transmission time, the first apparatus 110 may summarize buffer sizes indicated in the plurality of sub-TBs, as combined buffer status information. Further, the first apparatus 110 may obtain a minimum value of remaining transmission time indicated in the plurality of sub-TBs, as the combined delay status information. As another example, the first apparatus 110 may obtain a plurality of values of the remaining transmission time indicated in the plurality of sub-TBs, as the combined delay status information.

[0086] By way of example, a common MAC layer may ask various RLC / PDCP entities of the buffered data and then build the BSR / DSR MAC CE with the result. This is possible if the RPUs (e.g. the RPUs 406, 408 and 410 in FIG. 4A) are preparing such data and pushing it down to MAC-Low (e.g. MAC-Low 412 in FIG. 4A). It is then MAC-Low that still processes the information and build the BSR / DSR MAC CE, which may avoid inter-CPU communication.

[0087] After the TB is constructed, the first apparatus 110 transmits (520) the TB to the second apparatus 120. In some example embodiments, the TB structure as shown in FIG. 4B may be used by the first apparatus 110 where only one BSR MAC CE 426 (and / or one DSR MAC CE) may be included in the TB. Correspondingly, the second apparatus 120 may receive (522) such a TB. Because the summation of multiple BSR / DSR reports is performed at the first apparatus 110, the second apparatus 120 may directly use the summed information included in the TB. According to some other example embodiments of the present disclosure, illustrated as Option 2 in FIG. 5, the data status information for the plurality of RPUs may be summed up by the second apparatus 120 to determine data status information for a TB. As shown, the first apparatus 110 constructs (525) the TB by concatenating a plurality of sub-TBs for the plurality of RPUs. In an example, MAC-Low (e.g. MAC-Low 412 in FIG. 4A) in the first apparatus 110 may construct the TB by concatenating the sub-TBs delivered by multiple RPUs (e.g. the RPUs 406, 408 and 410). One TB may therefore contain more than one BSR MAC CE and / or DSR MAC CE containing buffer status and / or delay status information of the same or different LCGs.

[0088] After the TB is constructed, the first apparatus 110 transmits (5j0) the TB to the second apparatus 120. The TB includes a plurality of sub-TBs, and each of the plurality of sub-TBs includes its own data and data status information.

[0089] After the second apparatus 120 receives (535) the TB, the second apparatus 120 combines (540) the data status information in the plurality of sub-TBs. The second apparatus 120 may sum up and process the multiple BSR / DSR reports to derive the complete picture of the delay status information.

[0090] For example, in example embodiments where the buffer status information indicates a buffer size, the second apparatus 120 may summarize buffer sizes indicated in the plurality of sub-TBs, as combined buffer status information. As another example, in the example embodiments where the delay status information indicates buffer status information and related remaining transmission time, the second apparatus 120 may summarize buffer sizes indicated in the plurality of sub-TBs, as the combined buffer status information. Further, the second apparatus 120 may obtain a minimum value of remaining transmission time indicated in the plurality of sub-TBs, as the combined delay status information. As another example, the second apparatus 120 may obtain a plurality of values of the remaining transmission time indicated in the plurality of sub-TBs, as the combined delay status information.

[0091] The TB transmitted (530) by the first apparatus 110 may be implemented in any suitable form. In some example embodiments, the data status information of a radio processing unit of the plurality of radio processing units is carried in a header of the RPU. In a case where RPUs in the first apparatus 110 are not transparent to the network (e.g. the second apparatus 120) and they are either configured by the second apparatus (e.g. a gNB) or the first apparatus 110 identifies them, BSR / DSR information (as an example of the data status information) may be included in the RPU headers.

[0092] In some example embodiments, the TB may include a plurality of sub-TBs, and a sub-TB of the plurality of sub-TBs includes at least one data unit and at least one status information unit.

[0093] In some example embodiments, the status information unit may carry at least one of buffer status information or delay status information. In an example, the buffer status information may indicate a buffer size and the delay status information may indicate a buffer size and remaining transmission time.

[0094] In some example embodiments, the at least one data unit may be carried in at least one MAC sub-PDU. The at least one status information unit may be carried in at least one MAC CE such as a BSR MAC CE (for the buffer status information) and a DSR MAC CE (for the buffer status information and the delay status information).

[0095] In some example embodiments, the at least one status information unit may follow or precede the at least one data unit in the sub-TB of the plurality of sub-TBs. In an example, when the sub-TB is constructed, a BSR MAC CE and / or a DSR MAC CE (as an example of data status information unit) may follow or precede one or more MAC sub-PDUs from the corresponding LCH(s) (as an example of the data unit in the sub-TB).

[0096] In some example embodiments, a sub-TB of the plurality of sub-TBs is constructed by an RPU of a plurality of RPUs of the first apparatus 110. In some example embodiments, the at least one status information unit in the sub-TB of the plurality of sub-TBs may carry at least one of buffer status information or delay status information of data associated with an RPU of the plurality of RPUs. The data associated with the RPU may include at least one of: data buffered at the RPU, or data buffered at an entity (e.g. PDCH-High 416 in FIG. 4B) in a layer higher than a layer associated with the RPU.

[0097] An example dual stack operation 700 for TB transmission (530) by the first apparatus 110 is shown in FIG. 7. As shown, one sub-TB 706, 708 or 710 includes one or more MAC sub-PDUs from the corresponding LCH(s), followed by a B SR MAC CE 716, 718 or 720 (and / or a DSR MAC CE) including information about the data buffered at the corresponding RPU 406, 408 or 410 (and / or related remaining time information). As an alternative example, the MAC CEs 716, 718 or 720 may precede the MAC sub-PDUs.

[0098] In some example embodiments, the process of constructing a TB may include the following steps. Firstly, PDCP-High 416 may route PDCP SDUs to different RPUs where, among other functions, e.g. ciphering and / or integrity protection may be applied, and a PDCP header may be added. Then, RLC 602 may process the PDCP PDUs by performing e.g. segmentation (on a need basis) and add the RLC header. RLC PDUs may then be processed by MAC-High 414 where the MAC header is added, including a logical channel identifier (LCID) of the corresponding LCH. The RPU-specific BSR MAC CE and / or DSR MAC CE may be added in this step, just after the MAC sub-PDUs including MAC SDUs delivered by the corresponding RPU 406. Finally, MAC-Low (e.g. MAC-Low 412 in FIG. 4A) may concatenate the sub-TBs delivered by multiple RPUs in one TB.

[0099] In this way, the large data volume LCGs may be sub-divided in multiple RPUs. By extensions, multiple BSRs may be used for smaller chunks of data. Thus, the BSR reporting may be moved to a lower index region of a BSR table, and therefore the overall absolute error of the reports may be reduced.

[0100] After the second apparatus 120 receives (535) such a TB, the second apparatus 120 may determine the buffer size and / or delay information of one LCG by combining (e.g., by summing the buffer sizes, and / or by taking the minimum value of the remaining time values) the buffer size and / or delay status information signaled in different RPU- specific BSR and / or DSR within one TB. In this way, buffer and delay status information of data belonging to one LCH or LCG may be conveyed to the second apparatus 120 using more than one buffer and / or delay status report within a TB. It can be observed that with the proposed solution, inter-RPU communication may be minimized / avoided by enabling each RPU to independently (i.e. without communication with other RPUs) compute its own buffer size and / or remaining time information, construct its own BSR and / or DSR, and copy / insert the computed BSR and / or DSR in a specific memory location prior to PHY processing.

[0101] In some example embodiments, which RPU in the first apparatus 110 processes which part of the data may be transparent to the receiver eg. the second apparatus 120. In such an embodiment, the first apparatus 110 may be given the opportunity (for instance through an explicit RRC configuration) to include multiple BSR MAC CEs and / or DSR MAC CEs within a TB. The fact that the first apparatus 110 is transmitting a TB with multiple BSR MAC CEs and / or DSR MAC CEs within a TB, may be used to determine that, in the first apparatus 110, different processing units (RPUs) are processing data in parallel. Such parallel processing may include computing RPU-specific buffer size and / or remaining time information, constructing RPU-specific BSR and / or DSR, and copying / inserting the RPU-specific BSR and / or DSR in a specific memory location prior to physical layer (PHY) processing.

[0102] In some example embodiments, a relative position between the at least one data unit and the at least one status information in the sub-TB of the plurality of sub-TBs may be different from a relative position between at least one data unit and at least one status information unit in a further sub-TB of the plurality of sub-TBs. In an example, the MAC CEs for BSR and / or DSR of the primary RPU (e.g. RPU#2 408 in the FPS 240) may be placed differently than for the MAC CEs for BSR and / or DSR of the other RPUs. For instance, the MAC CEs for BSR and / or DSR may be placed at the beginning of the sub-TBs corresponding to the primary RPU, while placed at the end of the sub-TBs corresponding to the other RPUs.

[0103] In the protocol stack structure as shown in FIG. 7, the single RLC entity 602 is configured for LCG#2 404 which is mapped to at least one RPU, for example, including RPU#2 408 and RPU#3 410. FIG. 8 illustrates an example dual stack operation 800 with one RLC entity per RPU according to some example embodiments of the present disclosure. As shown, each of the RPU#1 406, RPU#2 408 and RPU#3 410 is associated with a RLC entity 806, 808 or 810. As described above, such a structure may be used in case of RLC AM and RLC UM with segmentation as sequence numbering and window management. Retransmissions may be performed independently by each RPU without a need for inter-RPU coordination.

[0104] In some example embodiments, as data from two different RLC legs may be multiplexed within the same TB (while in both dual connectivity and PDCP duplication, data from different legs is transmitted over different cells, hence different TBs), an indication of an RLC entity (i.e. an RPU associated with the RLC entity) other than an LCID may need to be included in a MAC header to allow the receiver (e.g. the second apparatus 120) to route the RLC PDUs to the correct RLC entity. In this case, mapping of data to RPUs may not be completely transparent to the receiver.

[0105] In some example embodiments, the at least one data unit in the sub-TB of the plurality of sub-TBs may contain: data buffered at the RPU of the plurality of RPUs, and / or data buffered at an entity (e.g. PDCP-High 416) in a layer higher than a layer associated with the RPU. In the protocol stack structures as shown in FIGS. 7 and 8, data buffering may be performed at PDCP-Low 417, i.e. no data buffering outside of RPU #2 and RPU #3. In some example embodiments, some data buffering may be performed outside of the RPU, for example, at PDCP-High 416.

[0106] The data buffered outside of an RPU maybe separately reported. In some example embodiments, the at least one status information unit in the sub-TB of the plurality of sub-TBs may include a first status information unit for the RPU, and a second status information unit for the entity (e.g. PDCP-High 416) in the higher layer. In some example embodiments, the first status information unit and the second status information unit may be placed in separate positions in the sub-TB of the plurality of sub-TBs.

[0107] In an example, the data buffered at PDCP-High 416 maybe separately reported in a MAC CE identified as above. For example, the second status information unit for the data buffered at PDCP-High 416 may be included in a BSR MAC CE 716, 718 or 720, but separate from the second status information unit for the RPU 406, 408 or 410. In an alternative example, the second status information unit for the data buffered at PDCP-High 416 may be placed in a MAC CE differently than the other MAC CEs carrying the first status information unit for the RPU 406, 408 or 410. For instance, a MAC CE carrying the second status information unit may be placed at the beginning of a sub-TB while other MAC CEs carrying the first status information unit may be placed at the end of the sub-TB.

[0108] In some example embodiments, the positioning of the second status information may be configured by a network. In an example, the second apparatus 120 may transmit, to the first apparatus 110, a configuration of positioning of the second status information unit for the entity (e.g. PDCP-High 416) in the higher layer. Correspondingly, the first apparatus 110 may receive the configuration. The second status information unit may be positioned in the sub-TB of the plurality of sub-TBs based on the received configuration. The configuration may be transmitted in any suitable signaling. For example, the placement of the MAC CEs reflecting buffering at PDCP-High 416 may be configured via RRC signalling.

[0109] In case of data buffering at PDCP-High 416, yet another protocol architecture option may be considered with one data radio bearer (DRB)-LCH per RPU. FIG. 9 shows an example dual stack operation 900 with separate DRBs / LCHs per RPU according to some example embodiments of the present disclosure. In this example, each RPU 406, 408 or 410 may its own PDCP entity 906, 908 or 910 and RLC entity 806, 808 or 810. As such, PDCP processing may be fully contained within an RPU 406, 408 or 410. This means, routing of data to different RPUs needs to be performed at a higher level than PDCP, e.g., at Service Data Application Protocol (SDAP) 902. SDAP 902 is the protocol responsible for mapping from QoS flows to DRBs. This implementation option may therefore require the possibility to map one QoS flow to multiple DRBs / LCHs. In some example embodiments, the LCHs may be mapped to RPU#2 408 and RPU#3 still belongs to the same LCG. [OHO] It is to be noted that although the long BSR format is illustrated, but the proposed solution may in general apply to a DSR, as well as to other BSR formats (e g. a short BSR). When considering the long BSR format, it is assumed that the first apparatus 110 needs to indicate which LCGs are signaled in the BSR MAC CE. Assuming that each RPU reports its own buffer status in an RPU-specific BSR MAC CE (when a BSR is transmitted) and that one RPU may only carry data belonging to one LCH or LCG, there may not be a need to include a LCG field in the RPU-specific BSR MAC CE.

[0111] FIG. 10 shows a flowchart of an example method 1000 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1000 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0112] At block 1010, the first apparatus 110 determines data status for each of a plurality of radio processing units.

[0113] At block 1020, the first apparatus 110 constructs a sub-TB for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit. [0H4] At block 1030, the first apparatus 110 constructs a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, where data in the plurality of sub-transport blocks is concatenated to construct data of the transport block, and the data status information in the plurality of sub-transport blocks is combined to construct data status information of the transport block.

[0115] At block 1040, the first apparatus 110 transmits the transport block to a second apparatus 120.

[0116] In some example embodiments, the data status information of a radio processing unit of the plurality of radio processing units comprises at least one of buffer status information or delay status information of data associated with the radio processing unit.

[0117] In some example embodiments, the buffer status information indicates a buffer size, and the first apparatus 110 summarizes buffer sizes indicated in the plurality of sub-transport blocks, as combined buffer status information.

[0118] In some example embodiments, the delay status information indicates a buffer size and related remaining transmission time, and the first apparatus obtains a minimum value or a plurality of values of remaining transmission time indicated in the plurality of sub-transport blocks, as combined delay status information.

[0119] In some example embodiments, the data associated with the radio processing unit comprises at least one of: data buffered at the radio processing unit, or data buffered at an entity in a layer higher than a layer associated with the radio processing unit.

[0120] In some example embodiments, a single radio link control entity is configured for a logical channel, the logical channel being mapped to at least one radio processing unit of the plurality of radio processing unit.

[0121] In some example embodiments, each of the plurality of radio processing units is associated with a radio link control entity.

[0122] In some example embodiments, each of the plurality of radio processing units is associated with at least one sub-layer of a radio protocol layer.

[0123] FIG. 11 shows a flowchart of an example method 1100 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1100 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0124] At block 1110, the first apparatus 110 determines data status for each of a plurality of radio processing units.

[0125] At block 1120, the first apparatus 110 constructs a sub-transport block for each of the plurality of radio processing units, where the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit.

[0126] At block 1130, the first apparatus 110 constructs a transport block by concatenating a plurality of sub-transport blocks for the plurality of radio processing units.

[0127] At block 1140, the first apparatus 110 transmits the transport block to a second apparatus.

[0128] In some example embodiments, the data status information of a radio processing unit of the plurality of radio processing units comprise at least one of buffer status information or delay status information of data associated with the radio processing unit.

[0129] In some example embodiments, the data associated with the radio processing unit comprises at least one of: data buffered at the radio processing unit, or data buffered at an entity in a layer higher than a layer associated with the radio processing unit.

[0130] In some example embodiments, a single radio link control entity is configured for a logical channel, the logical channel being mapped to at least one radio processing unit of the plurality of radio processing unit.

[0131] In some example embodiments, each of the plurality of radio processing units is associated with a radio link control entity.

[0132] In some example embodiments, each of the plurality of radio processing units is associated with at least one sub-layer of a radio protocol layer.

[0133] In some example embodiments, the data status information of a radio processing unit of the plurality of radio processing units is carried in a header of the radio processing unit.

[0134] FIG. 12 shows a flowchart of an example method 1200 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1200 will be described from the perspective of the second apparatus 120 in FIG. 1.

[0135] At block 1210, the second apparatus 120 receives a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and each of the plurality of sub-transport blocks contains data and data status information.

[0136] At block 1220, the second apparatus 120 combines the data status information in the plurality of sub-transport blocks.

[0137] In some example embodiments, the data status information comprises at least one of buffer status information or delay status information.

[0138] In some example embodiments, the buffer status information indicates a buffer size, and the instructions that, when executed by the at least one processor, cause the second apparatus to: summarize buffer sizes indicated in the plurality of sub-transport blocks, as combined buffer status information.

[0139] In some example embodiments, the delay status information indicates a buffer size and remaining transmission time, and the instructions that, when executed by the at least one processor, cause the second apparatus to: obtain a minimum value or a plurality of values of remaining transmission time indicated in the plurality of subtransport blocks, as combined delay status information.

[0140] Ine example embodiments, the data status information in a sub-transport block of the plurality of sub-transport blocks is carried in a header of a radio processing unit associated with the sub-transport block

[0141] FIG. 13 shows a flowchart of an example method 1300 implemented at a first apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1300 will be described from the perspective of the first apparatus 110 in FIG. 1.

[0142] At block 1310, the first apparatus 110 constructs a transport block, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit.

[0143] At block 1320, the first apparatus 110 transmits the transport block to a second apparatus.

[0144] In some example embodiments, the status information unit carries at least one of buffer status information or delay status information.

[0145] In some example embodiments, the at least one status information unit follows or precedes the at least one data unit in the sub-transport block of the plurality of subtransport blocks.

[0146] In some example embodiments, a relative position between the at least one data unit and the at least one status information unit in the sub-transport block of the plurality of sub-transport blocks is different from a relative position between at least one data unit and at least one status information unit in a further sub-transport block of the plurality of sub-transport blocks.

[0147] In some example embodiments, a sub-transport block of the plurality of sub transport blocks is constructed by a radio processing unit of a plurality of radio processing units of the first apparatus 110.

[0148] In some example embodiments, the at least one status information unit in the sub-transport block of the plurality of sub-transport blocks carries at least one of buffer status information or delay status information of data associated with a radio processing unit of the plurality of radio processing units.

[0149] In some example embodiments, the at least one status information unit is carried in a header of the radio processing unit.

[0150] In some example embodiments, the at least one data unit in the sub-transport block of the plurality of sub-transport blocks contains: data buffered at the radio processing unit of the plurality of radio processing units, and data buffered at an entity in a layer higher than a layer associated with the radio processing unit.

[0151] In some example embodiments, the at least one status information unit in the sub-transport block of the plurality of sub-transport blocks comprises a first status information unit for the radio processing unit, and a second status information unit for the entity in the higher layer.

[0152] In some example embodiments, the first status information unit and the second status information unit are placed in separate positions in the sub-transport block of the plurality of sub-transport blocks.

[0153] In some example embodiments, the first apparatus receives, from the second apparatus, a configuration of positioning of the second status information unit for the entity in the higher layer, where the second status information unit is positioned in the sub-transport block of the plurality of sub-transport blocks based on the received configuration.

[0154] In some example embodiments, a relative position between at least one data unit and at least one status information unit for a reference radio processing unit of the plurality of radio processing units is different from a relative position between at least one data unit and at least one status information unit for a remaining reference radio processing unit of the plurality of radio processing units.

[0155] In some example embodiments, the at least one data unit is carried in at least one medium access control, MAC, sub-protocol data unit, sub-PDU, and the at least one status information unit is carried in at least one MAC control element, CE.

[0156] FIG. 14 shows a flowchart of an example method 1400 implemented at a second apparatus in accordance with some example embodiments of the present disclosure. For the purpose of discussion, the method 1400 will be described from the perspective of the second apparatus 120 in FIG. 1.

[0157] At block 1410, the second apparatus 120 receives a transport block from a first apparatus, where the transport block includes a plurality of sub-transport blocks, and a sub-transport block of the plurality of sub-transport block includes at least one data unit and at least one status information unit.

[0158] In some example embodiments, the status information unit carries at least one of buffer status information or delay status information.

[0159] In some example embodiments, the at least one status information unit follows or precedes the at least one data unit in the sub-transport block of the plurality of subtransport blocks.

[0160] In some example embodiments, a relative position between the at least one data unit and the at least one status information in the sub-transport block of the plurality of sub-transport blocks is different from a relative position between at least one data unit and at least one status information unit in a further sub-transport block of the plurality of sub-transport blocks.

[0161] In some example embodiments, a sub-transport block of the plurality of subtransport blocks is constructed by a radio processing unit of a plurality of radio processing units of the first apparatus 110.

[0162] In some example embodiments, the at least one status information unit in the sub-transport block of the plurality of sub-transport blocks carries at least one of buffer status information or delay status information of data associated with a radio processing unit of the plurality of radio processing units.

[0163] In some example embodiments, the at least one data unit in the sub-transport block of the plurality of sub-transport blocks contains at least one of: data buffered at the radio processing unit of the plurality of radio processing units, or data buffered at an entity in a layer higher than a layer associated with the radio processing unit.

[0164] In some example embodiments, the at least one status information unit in the sub-transport block of the plurality of sub-transport blocks comprises a first status information unit for the radio processing unit, and a second status information unit for the entity in the higher layer.

[0165] In some example embodiments, the first status information unit and the second status information unit are placed in separate positions in the sub-transport block of the plurality of sub-transport blocks.

[0166] In some example embodiments, the second apparatus transmits, to the first apparatus, a configuration of positioning of the second status information unit for the entity in the higher layer, where the second status information unit is positioned based on the received configuration in the sub-transport block of the plurality of sub-transport blocks.

[0167] In some example embodiments, a relative position between at least one data unit and at least one status information unit for a reference radio processing unit of the plurality of radio processing units is different from a relative position between at least one data unit and at least one status information unit for a remaining reference radio processing unit of the plurality of radio processing units.

[0168] In some example embodiments, the at least one data unit is carried in at least one medium access control, MAC, sub-protocol data unit, sub-PDU, and the at least one status information unit is carried in at least one MAC control element, CE.

[0169] FIG. 15 is a simplified block diagram of a device 1500 that is suitable for implementing example embodiments of the present disclosure. The device 1500 may be provided to implement a communication device, for example, the first apparatus 110 or the second apparatus 120 as shown in FIG. 1. As shown, the device 1500 includes one or more processors 1510, one or more memories 1520 coupled to the processor 1510, and one or more communication modules 1540 coupled to the processor 1510.

[0170] The communication module 1540 is for bidirectional communications. The communication module 1540 has one or more communication interfaces to facilitate communication with one or more other modules or devices. The communication interfaces may represent any interface that is necessary for communication with other network elements. In some example embodiments, the communication module 1540 may include at least one antenna.

[0171] The processor 1510 may be of any type suitable to the local technical network and may include one or more of the following: general purpose computers, special purpose computers, microprocessors, digital signal processors (DSPs) and processors based on multicore processor architecture, as non-limiting examples. The device 1500 may have multiple processors, such as an application specific integrated circuit chip that is slaved in time to a clock which synchronizes the main processor.

[0172] The memory 1520 may include one or more non-volatile memories and one or more volatile memories. Examples of the non-volatile memories include, but are not limited to, a Read Only Memory (ROM) 1524, an electrically programmable read only memory (EPROM), a flash memory, a hard disk, a compact disc (CD), a digital video disk (DVD), an optical disk, a laser disk, and other magnetic storage and / or optical storage. Examples of the volatile memories include, but are not limited to, a randomaccess memory (RAM) 1522 and other volatile memories that will not last in the powerdown duration.

[0173] A computer program 1530 includes computer executable instructions that are executed by the associated processor 1510. The instructions of the program 1530 may include instructions for performing operations / acts of some example embodiments of the present disclosure. The program 1530 may be stored in the memory, e.g., the ROM 1524. The processor 1510 may perform any suitable actions and processing by loading the program 1530 into the RAM 1522.

[0174] The example embodiments of the present disclosure may be implemented by means of the program 1530 so that the device 1500 may perform any process of the disclosure as discussed with reference to FIG. 1 to FIG. 9. The example embodiments of the present disclosure may also be implemented by hardware or by a combination of software and hardware.

[0175] In some example embodiments, the program 1530 may be tangibly contained in a computer readable medium which may be included in the device 1500 (such as in the memory 1520) or other storage devices that are accessible by the device 1500. The device 1500 may load the program 1530 from the computer readable medium to the RAM 1522 for execution. In some example embodiments, the computer readable medium may include any types of non-transitory storage medium, such as ROM, EPROM, a flash memory, a hard disk, CD, DVD, and the like. The term “non-transitory,” as used herein, is a limitation of the medium itself (i.e., tangible, not a signal) as opposed to a limitation on data storage persistency (e.g., RAM vs. ROM).

[0176] FIG. 16 shows an example of the computer readable medium 1600 which may be in form of CD, DVD or other optical storage disk. The computer readable medium 1600 has the program 1530 stored thereon.

[0177] Generally, various embodiments of the present disclosure may be implemented in hardware or special purpose circuits, software, logic or any combination thereof. Some aspects may be implemented in hardware, and other aspects may be implemented in firmware or software which may be executed by a controller, microprocessor or other computing device. Although various aspects of embodiments of the present disclosure are illustrated and described as block diagrams, flowcharts, or using some other pictorial representations, it is to be understood that the block, apparatus, system, technique or method 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.

[0178] Some example embodiments of the present disclosure also provide at least one computer program product tangibly stored on a computer readable medium, such as a non-transitory computer readable medium. The computer program product includes computer-executable instructions, such as those included in program modules, being executed in a device on a target physical or virtual processor, to carry out any of the methods as described above. Generally, program modules include routines, programs, libraries, objects, classes, components, data structures, or the like that perform particular tasks or implement particular abstract data types. The functionality of the program modules may be combined or split between program modules as desired in various embodiments. Machine-executable instructions for program modules may be executed within a local or distributed device. In a distributed device, program modules may be located in both local and remote storage media.

[0179] Program code for carrying out methods of the present disclosure may be written in any combination of one or more programming languages. The program code may be provided to a processor or controller of a general-purpose computer, special purpose computer, or other programmable data processing apparatus, such that the program code, when executed by the processor or controller, cause the functions / operations specified in the flowcharts and / or block diagrams to be implemented. The program code may execute entirely on a machine, partly on the machine, as a stand-alone software package, partly on the machine and partly on a remote machine or entirely on the remote machine or server.

[0180] In the context of the present disclosure, the computer program code or related data may be carried by any suitable carrier to enable the device, apparatus or processor to perform various processes and operations as described above. Examples of the carrier include a signal, computer readable medium, and the like.

[0181] The computer readable medium may be a computer readable signal medium or a computer readable storage medium. A computer readable medium may include but not limited to an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples of the computer readable storage medium would include an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random-access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

[0182] Further, although operations are depicted in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be 5 advantageous. Likewise, although several specific implementation details are contained in the above discussions, these should not be construed as limitations on the scope of the present disclosure, but rather as descriptions of features that may be specific to particular embodiments. Unless explicitly stated, certain features that are described in the context of separate embodiments may also be implemented in combination in a 10 single embodiment. Conversely, unless explicitly stated, various features that are described in the context of a single embodiment may also be implemented in a plurality of embodiments separately or in any suitable sub-combination.

[0183] Although the present disclosure has been described in languages specific to structural features and / or methodological acts, it is to be understood that the present 15 disclosure defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

1. A first apparatus comprising:at least one processor; andat least one memory storing instructions that, when executed by the at least one processor, cause the first apparatus at least to:determine data status for each of a plurality of radio processing units;construct a sub-transport block for each of the plurality of radio processing units, wherein the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit;construct a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, wherein data in the plurality of sub-transport blocks is concatenated to construct data of the transport block, and the data status information in the plurality of sub-transport blocks is combined to construct data status information of the transport block; andtransmit the transport block to a second apparatus.

2. The first apparatus of claim 1, wherein the data status information of a radio processing unit of the plurality of radio processing units comprises at least one of buffer status information or delay status information of data associated with the radio processing unit.

3. The first apparatus of claim 2, wherein the buffer status information indicates a buffer size, andthe instructions that, when executed by the at least one processor, cause the first apparatus to:summarize buffer sizes indicated in the plurality of sub-transport blocks, as combined buffer status information.

4. The first apparatus of claim 2 or 3, wherein the delay status information indicates remaining transmission time, andthe instructions that, when executed by the at least one processor, cause the first apparatus to:obtaining a minimum value or a plurality of values of remaining transmission time indicated in the plurality of sub-transport blocks, as combined delay status information.

5. The first apparatus of any of claims 2 to 4, wherein the data associated with the radio processing unit comprises at least one of:data buffered at the radio processing unit, ordata buffered at an entity in a layer higher than a layer associated with the radio processing unit.

6. The first apparatus of any of claims 1 to 5, wherein a single radio link control entity is configured for a logical channel, the logical channel being mapped to at least one radio processing unit of the plurality of radio processing unit.

7. The first apparatus of any of claims 1 to 5, wherein each of the plurality of radio processing units is associated with a radio link control entity.8 The first apparatus of any of claims 1 to 5, wherein each of the plurality of radio processing units is associated with at least one sub-layer of radio protocol layer.

9. A method comprising:determining data status for each of a plurality of radio processing units;constructing a sub-transport block for each of the plurality of radio processing units, wherein the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit;constructing a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, wherein data in the plurality of sub-transport blocks is concatenated to construct data of the transport block, and the data status information in the plurality of sub-transport blocks is combined to construct data status information of the transport block; andtransmitting the transport block to a second apparatus.

10. A first apparatus comprising:means for determining data status for each of a plurality of radio processing units;means for constructing a sub-transport block for each of the plurality of radio processing units, wherein the sub-transport block contains data from the radio processing unit and data status information of the radio processing unit, the data status information indicating the data status of the radio processing unit;means for constructing a transport block based on a plurality of sub-transport blocks for the plurality of radio processing units, wherein data in the plurality of subtransport blocks is concatenated to construct data of the transport block, and the datastatus information in the plurality of sub-transport blocks is combined to construct data status information of the transport block; andmeans for transmitting the transport block to a second apparatus.5 11. A computer readable medium comprising instructions stored thereon forcausing an apparatus at least to perform the method of claim 9.34

Images