Methods, devices, and systems for network coordination in wireless network
A loosely coupled, container-based communication method improves wireless network coordination by segregating UE capabilities and configurations, addressing inefficiencies in cloud-native architectures through flexible and scalable signaling.
Patent Information
- Application Number
- PCT/CN2025/094758
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2025-05-14
- Publication Date
- 2026-11-19
AI Technical Summary
Existing wireless communication networks struggle with efficiently coordinating diverse wireless devices due to centralized and tightly coupled designs, which are inadequate for cloud-native architectures, leading to inefficiencies in UE capability reporting and network configuration.
Implementing a loosely coupled, container-based communication approach that segregates UE capabilities and network configurations into separate containers, using predefined encoding schemes like ASN.1 and TLV, and utilizing lower layer control elements (LLCEs) for flexible and scalable signaling.
Enhances scalability and reduces signaling overhead by enabling independent handling and interpretation of configuration aspects, facilitating efficient coordination between UEs and networks, particularly in cloud-native deployments.
Smart Images

Figure CN2025094758_19112026_PF_FP_ABST
Abstract
Description
METHODS, DEVICES, AND SYSTEMS FOR NETWORK COORDINATION IN WIRELESS NETWORKTECHNICAL FIELD
[0001] This disclosure is generally directed to wireless communications, and particularly to a method, device, and system for loosely coupled, container based communication in a wireless network, such as a 4G LTE, 5G, or a 6G network and beyond.BACKGROUND
[0002] With the rapid evolution of wireless communication technology, more and more wireless devices are introduced to provide various services that need to meet various requirements. The wireless device may include a User Equipment (UE) , an Internet of Things (IoT) device, a Machine-to-Machine (M2M) device, a Machine Type Communications (MTC) device, etc. Different wireless devices may have different capabilities. To provide optimal service to a wireless device based on its capability, it is critical to coordinate wireless device and wireless network in an accurate and efficient manner.SUMMARY
[0003] This disclosure is directed to a method, device, and system for loosely coupled, container based communication in a wireless network, such as a 4G LTE, 5G, or a 6G network and beyond.
[0004] In some embodiments, a method performed by a first network element is disclosed. The method may include: transmitting, by the first network element or by a first layer of the first network element, to a wireless device, a message comprising a Compound Data Unit (CDU) , the CDU comprising at least one container, wherein each of the at least one container comprises data encoded using a predefined encoding scheme.
[0005] In some embodiments, a method performed by a wireless device is disclosed. The method may include: receiving, by the wireless device or a first layer of the wireless device, from a network element, a message comprising a Compound Data Unit (CDU) , the CDU comprising at least one container, wherein each of the at least one container comprises data encoded using a predefined encoding scheme.
[0006] In some embodiments, there is a wireless device, a network element, or a network node comprising a processor and a memory, wherein the processor is configured to read code from the memory and implement any methods recited in any of the embodiments.
[0007] In some embodiments, a computer program product comprising a computer-readable program medium code stored thereupon, the code, when executed by a processor, causing the processor to implement any method recited in any of the embodiments.
[0008] The above embodiments and other aspects and alternatives of their implementations are described in greater detail in the drawings, the descriptions, and the claims below.BRIEF DESCRIPTION OF THE DRAWINGS
[0009] FIG. 1 shows an example wireless communication network.
[0010] FIG. 2 shows an example wireless network node.
[0011] FIG. 3 shows an example user equipment.
[0012] FIG. 4 shows exemplary a split base station with CU and DU.
[0013] FIGs. 5A-5B show exemplary payload to container mappings.
[0014] FIGs. 6A-6F show various exemplary methods for transmitting containers.
[0015] FIGs. 7A-7D show exemplary Lower Layer (e.g., MAC layer) Control Elements (LLCE) each carrying various containers.
[0016] FIGs. 8A-8B show exemplary methods for transmitting containers using LLCE.
[0017] FIGs. 9A-9E show various exemplary methods for transmitting containers.
[0018] FIGs. 10A-10C show various exemplary flow charts for transmitting DU and / or CU data / signaling.
[0019] FIG. 11 shows an exemplary extended Protocol Data Unit (PDU) or Combined Data Unit (CDU) according to embodiments of this disclosure.
[0020] FIG. 12A-12G show various exemplary subPDUs.
[0021] FIG. 13A shows an example CDU including security protected containers.
[0022] FIG. 13B shows an example subheader carrying security information.
[0023] FIGs. 14A-14B show various example CDU using various security protection
[0024] FIGs. 15A-15F show various exemplary methods for transmitting containers in uplink direction from UE to network. options.DETAILED DESCRIPTION
[0025] Wireless Communication Network
[0026] FIG. 1 shows an exemplary wireless communication network 100 that includes a core network 110 and a radio access network (RAN) 120. The core network 110 further includes at least one Mobility Management Entity (MME) 112 and / or at least one Access and Mobility Management Function (AMF) . Other functions that may be included in the core network 110 are not shown in FIG. 1. The RAN 120 further includes multiple base stations, for example, base stations 122 and 124. The base stations may include at least one evolved NodeB (eNB) for 4G LTE, an enhanced LTE eNB (ng-eNB) , or a Next generation NodeB (gNB) for 5G New Radio (NR) , or any other type of signal transmitting / receiving device such as a UMTS NodeB. The eNB 122 communicates with the MME 112 via an S1 interface. Both the eNB 122 and gNB 124 may connect to the AMF 114 via an Ng interface. Each base station manages and supports at least one cell. For example, the base station gNB 124 may be configured to manage and support cell 1, cell 2, and cell 3.
[0027] The gNB 124 may include a central unit (CU) and at least one distributed unit (DU) . The CU and the DU may be co-located in a same location, or they may be split in different locations. The CU and the DU may be connected via an F1 interface. Alternatively, for an eNB which is capable of connecting to the 5G network, it may also be similarly divided into a CU and at least one DU, referred to as ng-eNB-CU and ng-eNB-DU, respectively. The ng-eNB-CU and the ng-eNB-DU may be connected via a W1 interface.
[0028] The wireless communication network 100 may include one or more tracking areas. A tracking area may include a set of cells managed by at least one base station. For example, tracking area 1 labeled as 140 includes cell 1, cell 2, and cell 3, and may further include more cells that may be managed by other base stations and not shown in FIG. 1. The wireless communication network 100 may also include at least one UE 160. The UE may select a cell among multiple cells supported by a base station to communication with the base station through Over the Air (OTA) radio communication interfaces and resources, and when the UE 160 travels in the wireless communication network 100, it may reselect a cell for communications. For example, the UE 160 may initially select cell 1 to communicate with base station 124, and it may then reselect cell 2 at certain later time point. The cell selection or reselection by the UE 160 may be based on wireless signal strength / quality in the various cells and other factors.
[0029] The wireless communication network 100 may be implemented as, for example, a 2G, 3G, 4G / LTE, or 5G cellular communication network. Correspondingly, the base stations 122 and 124 may be implemented as a 2G base station, a 3G NodeB, an LTE eNB, or a 5G NR gNB. The UE 160 may be implemented as mobile or fixed communication devices which are capable of accessing the wireless communication network 100. The UE 160 may include but is not limited to mobile phones, laptop computers, tablets, personal digital assistants, wearable devices, Internet of Things (IoT) devices, MTC / eMTC devices, distributed remote sensor devices, roadside assistant equipment, XR devices, and desktop computers. The UE 160 may also be generally referred to as a wireless communication device, or a wireless terminal. The UE 160 may support sidelink communication to another UE via a PC5 interface.
[0030] While the description below focuses on cellular wireless communication systems as shown in FIG. 1, the underlying principles are applicable to other types of wireless communication systems for paging wireless devices. These other wireless systems may include but are not limited to Wi-Fi, Bluetooth, ZigBee, and WiMax networks.
[0031] FIG. 2 shows an example of electronic device 200 to implement a network base station (e.g., a radio access network node) , a core network (CN) , and / or an operation and maintenance (OAM) . Optionally in one implementation, the example electronic device 200 may include radio transmitting / receiving (Tx / Rx) circuitry 208 to transmit / receive communication with UEs and / or other base stations. Optionally in one implementation, the electronic device 200 may also include network interface circuitry 209 to communicate the base station with other base stations and / or a core network, e.g., optical or wireline interconnects, Ethernet, and / or other data transmission mediums / protocols. The electronic device 200 may optionally include an input / output (I / O) interface 206 to communicate with an operator or the like.
[0032] The electronic device 200 may also include system circuitry 204. System circuitry 204 may include processor (s) 221 and / or memory 222. Memory 222 may include an operating system 224, instructions 226, and parameters 228. Instructions 226 may be configured for the one or more of the processors 221 to perform the functions of the network node. The parameters 228 may include parameters to support execution of the instructions 226. For example, parameters may include network protocol settings, bandwidth parameters, radio frequency mapping assignments, and / or other parameters.
[0033] FIG. 3 shows an example of an electronic device to implement a terminal device 300 (for example, a user equipment (UE) ) . The UE 300 may be a mobile device, for example, a smart phone or a mobile communication module disposed in a vehicle. The UE 300 may include a portion or all of the following: communication interfaces 302, a system circuitry 304, an input / output interfaces (I / O) 306, a display circuitry 308, and a storage 309. The display circuitry may include a user interface 310. The system circuitry 304 may include any combination of hardware, software, firmware, or other logic / circuitry. The system circuitry 304 may be implemented, for example, with one or more systems on a chip (SoC) , application specific integrated circuits (ASIC) , discrete analog and digital circuits, and other circuitry. The system circuitry 304 may be a part of the implementation of any desired functionality in the UE 300. In that regard, the system circuitry 304 may include logic that facilitates, as examples, decoding and playing music and video, e.g., MP3, MP4, MPEG, AVI, FLAC, AC3, or WAV decoding and playback; running applications; accepting user inputs; saving and retrieving application data; establishing, maintaining, and terminating cellular phone calls or data connections for, as one example, internet connectivity; establishing, maintaining, and terminating wireless network connections, Bluetooth connections, or other connections; and displaying relevant information on the user interface 310. The user interface 310 and the inputs / output (I / O) interfaces 306 may include a graphical user interface, touch sensitive display, haptic feedback or other haptic output, voice or facial recognition inputs, buttons, switches, speakers and other user interface elements. Additional examples of the I / O interfaces 306 may include microphones, video and still image cameras, temperature sensors, vibration sensors, rotation and orientation sensors, headset and microphone input / output jacks, Universal Serial Bus (USB) connectors, memory card slots, radiation sensors (e.g., IR sensors) , and other types of inputs.
[0034] Referring to FIG. 3, the communication interfaces 302 may include a Radio Frequency (RF) transmit (Tx) and receive (Rx) circuitry 316 which handles transmission and reception of signals through one or more antennas 314. The communication interface 302 may include one or more transceivers. The transceivers may be wireless transceivers that include modulation / demodulation circuitry, digital to analog converters (DACs) , shaping tables, analog to digital converters (ADCs) , filters, waveform shapers, filters, pre-amplifiers, power amplifiers and / or other logic for transmitting and receiving through one or more antennas, or (for some devices) through a physical (e.g., wireline) medium. The transmitted and received signals may adhere to any of a diverse array of formats, protocols, modulations (e.g., QPSK, 16-QAM, 64-QAM, or 256-QAM) , frequency channels, bit rates, and encodings. As one specific example, the communication interfaces 302 may include transceivers that support transmission and reception under the 2G, 3G, BT, WiFi, Universal Mobile Telecommunications System (UMTS) , High Speed Packet Access (HSPA) +, 4G / Long Term Evolution (LTE) , 5G, and 6G standards. The techniques described below, however, are applicable to other wireless communications technologies whether arising from the 3rd Generation Partnership Project (3GPP) , GSM Association, 3GPP2, IEEE, or other partnerships or standards bodies.
[0035] Referring to FIG. 3, the system circuitry 304 may include one or more processors 321 and memories 322. The memory 322 stores, for example, an operating system 324, instructions 326, and parameters 328. The processor 321 is configured to execute the instructions 326 to carry out desired functionality for the UE 300. The parameters 328 may provide and specify configuration and operating options for the instructions 326. The memory 322 may also store any BT, WiFi, 3G, 4G, 5G or other data that the UE 300 will send, or has received, through the communication interfaces 302. In various implementations, a system power for the UE 300 may be supplied by a power storage device, such as a battery or a transformer.
[0036] FIG. 4 shows an example gNB architecture split into CU and DU units, and how they interact with the 5G core network. As shown in FIG. 4, the gNB may include a DU 420, which handles lower-layer functions like Radio Link Control (RLC) , Medium Access Control (MAC) , and physical layer (PHY) . The DU 420 may connect to the CU-CP (Control Plane) 410 and CU-UP (User Plane) 412 via F1-C interface and F1-U interface, respectively. The CU may include a CU-CP 410 and a CU-UP 412. The CU-CP 410 manages control signaling (e.g., RRC, NG-C) and communicates with the AMF (Access and Mobility Management Function) in the 5G core network via an NG-C interface. The CU-UP 412 handles user data, and connects to the UPF (User Plane Function) in the 5G core network via an NG-U interface. CU-CP 410 may connect to CU-CP 430 of another gNB via an Xn interface.
[0037] Loosely coupled architecture
[0038] In a traditional network structure, the UE capabilities and network configuration for all functions / modules are encoded and reported / sent together, and only one network / UE entity can decode these messages, reflecting a centralized and tightly coupled design in which functions / modules are tightly coupled. However, with the evolution toward cloud-native network architectures, this centralized approach can no longer meet increasingly stringent requirements. Therefore, a loosely coupled scheme for UE capability reporting, UE requests or indications, and network configuration is needed, particularly suited for cloud-native deployments, such as those based on the CU-DU split architecture as shown in FIG. 4.
[0039] The concept of loosely coupled architectures has been recognized as a key component of cloud-native friendly design from the RAN perspective. A loosely coupled architecture refers to an application design strategy in which the various components of the system are developed, deployed, and operated independently of one another.
[0040] FIGs. 5A and 5B illustrate exemplary methods of modularizing RRC configuration data and UE capability information using dedicated containers, thereby enabling a loosely coupled and flexible signaling architecture.
[0041] In this disclosure, a container may be considered as encoded data (e.g., payload data) , signaling, configuration, etc. The encoding scheme may include, for example, Abstract Syntax Notation One (ASN. 1) , and Type-Length-Value (TLV) encoding.
[0042] In FIG. 5A, an RRC configuration comprising multiple configuration items (e.g., Config A, Config B, Config C, and Config D) is segmented into respective RRC configuration containers (e.g., configuration A-D containers) , where each container encapsulates an individual configuration item (e.g., config A is encapsulated in config A container) . This containerization facilitates independent handling, transfer, or interpretation of specific configuration aspects.
[0043] In FIG. 5B, UE capability information originally grouped as a single capability set (e.g., Capability A through Capability D) is arranged into separate UE capability containers, each corresponding to a specific capability aspect. These containers enable selective reporting or exchange of UE capabilities, improving scalability and reducing signaling overhead in cloud-native or CU-DU split architectures.
[0044] In some embodiments, a separate (UE) capability container is provided for each function, such that each container is categorized based on functional granularity.
[0045] In some embodiments, a separate signaling container is provided for each function, such that each container is categorized based on functional granularity or layer granularity. The functions may include, for example, measurement, Packet Data Convergence Protocol (PDCP) , Radio Link Control (RLC) , Medium Access Control (MAC) , and Physical (PHY) layer functions. For example, signaling associated with each function may be encapsulated within a self-contained container corresponding to that function. The layers may include PDCP, RLC, MAC, PHY layers, and so on.
[0046] In some embodiments, there is a MAC Control Element (MAC CE) container including (encapsulating) one or more MAC CEs.
[0047] In some embodiments, as shown in FIG. 6A, an entity may communicate with another entity by transmitting a message including one or more containers. The entity may include, but is not limited to, a protocol layer (e.g., physical layer, MAC layer, RLC layer, or PDCP layer) , an entity corresponding to a layer (e.g., RRC entity, PDCP entity, RLC entity, RLC entity, MAC entity, or PHY entity) , a protocol stack, a network domain (e.g., control plane or user plane) , a network node, a software module, a hardware module (e.g., processing unit, radio unit, or interface component) , a virtualized function, a logical processing unit, or any combination thereof.
[0048] FIG. 6B show an example UE capability message that carries one or more UE capability containers.
[0049] FIG. 6C show an example NW (network) config message that carries one or more NW config containers.
[0050] In some embodiments, the container for (or corresponding to) a layer / entity may be transmitted peer to peer from an entity in one element to a peer entity in another element. For example, as shown in FIG. 6D, UE capability may include capability at different layer / entity (e.g., UE capability container for RRC layer, PDCP layer, etc. ) . The capability container for a layer / entity may be transmitted peer to peer from a corresponding entity in UE to a peer entity in NW. For another example, as shown in FIG. 6E, NW configuration may include configurations for different layer / entity (e.g., NW container for RRC layer, PDCP layer, etc. ) . The NW config container for a layer / entity may be transmitted peer to peer from a corresponding entity in NW to a peer entity in UE.
[0051] In some embodiments, as shown in FIG. 6F, the network may collect container (s) from one or more entities via, for example, a network config central unit, or more generally, a hub, and then transmit the containers to UE. On UE side, there is a counterpart central unit or a hub for distributing each of the containers to its corresponding entity. The peer entity may be responsible for decoding the container. Exemplarily, the containers may include network configuration containers. For example, an RRC container may carry RRC layer configuration information. In some implementations, the entities at transmission side are responsible for encoding the configuration information into container, and the entities at receiving side are responsible for decoding the container, to retrieve / recover the configuration. In some implementations, the central unit at transmission side is responsible for encoding the configuration information into container, and the central unit at receiving side is responsible for decoding the containers, to recover the configuration information for each respective entity.
[0052] In this disclosure, a lower layer control element (LLCE) may be used to serve a layer, an entity, a module, a function, or a domain. A lower layer may typically include a layer that is RRC layer and below (e.g., RRC, PDCP, RLC, MAC, PHY, and so on) . For example, there may be a MAC level CE, MAC CE. The LLCE may be used to carry information / data for other layers in addition to its own layer.
[0053] There are various manners to define module / function / domain.
[0054] In some implementations, module / function / domain may be defined according to the different protocol layers, e.g., RRC, PDCP, RLC, MAC, PHY and so on. The module may include different PHY (physical layer) functions, such as PHY measurement function, PHY MIMO function, and so on.
[0055] In some implementations, module / function / domain may be defined according to the different functions, such as measurement function, MIMO function, report function, and so on.
[0056] In some implementations, module / function / domain may be defined according to the different domains, such as Perception Domain, Trust Domain, Resource Domain, Intelligence Domain, Data Domain, Management Domain, Operations Domain, and Communication Domain and so on.
[0057] As an example, if the lower layer is a MAC layer, the MAC CE (or extended MAC CE in this disclosure, see details in below sections) may be used to carry containers corresponding to modules, functions, or domains.
[0058] FIG. 7A shows an example LLCE carrying containers corresponding to various layers (i.e., layer based containers) .
[0059] FIG. 7B shows an example LLCE carrying containers corresponding to various functions (i.e., function based containers) .
[0060] FIG. 7C shows an example LLCE carrying containers corresponding to various domains (i.e., domain based containers) .
[0061] FIG. 7D show an example LLCE carrying mixed containers corresponding to layer, function, or domain.
[0062] FIG. 8A shows an example diagram for a network to send an LLCE to a UE, with the LLCE containing one or more LLCE containers (e.g., as depicted in FIGs. 7A–7D) .
[0063] FIG. 8B shows another example diagram for a network to send an LLCE to a UE, in which a central unit is used to collect containers or distributing containers. The LLCE containing one or more LLCE containers (e.g., as depicted in FIGs. 7A–7D) . For example, a container corresponding to RRC entity may be collected in the network side, and will be distributed to the peer RRC entity in the UE side. The encoding / decoding of the containers may occur at the central unit, or the respective entity.
[0064] In some embodiments, when the lower layer is MAC layer, the MAC layer may receive container for information, such as control command information (or bit string) from another layer (e.g., PHY layer) , and encapsulate the control information container into a MAC CE (to be more specific, an extended / enhanced MAC CE, with details described in later sections) . The another layer may include a layer lower than the MAC layer, or a layer higher than the MAC layer. Using PHY layer as an example:
[0065] The content of the command is defined in PHY instead of MAC. That is, the container corresponds to PHY layer and carries command for PHY layer. A Logical Channel ID (LCID) or MAC control element ID may be allocated to the MAC CE which carry the container. In some implementations, the LCID indicates the corresponding payload in the MAC CE is a container. In some implementations, the LCID not only indicates the corresponding payload in the MAC CE is a container, but may also indicate the layer / entity / module / function / domain corresponding to the container (i.e., a specific type of container) . For example, an LCID=100 indicates a PHY layer container, whereas an LCID=101 indicates a trust domain container.
[0066] In some implementations, there may be a length indication in the header of the concerned MAC CE, indicating the length of corresponding container.
[0067] In some implementations, there may be a command type field (or lower layer command type) in the header of concerned MAC CE to indicate the type of the content of the low layer command, or, optionally, the command type is encoded as part of the low layer command by PHY layer directly, that is, not part of the header of the MAC CE, but rather embedded with the command itself from PHY layer. In this case, the container itself includes the command type as part of the command.
[0068] From a UE perspective, whenever UE receives the MAC CE and determines that the MAC CE contains a command container (e.g., for lower layer PHY) , UE MAC layer may deliver the received command container to physical layer.
[0069] In some implementations, the UE MAC layer is not required to decode the content of the command container (e.g., for the PHY layer) , but the destined layer will decode it.
[0070] In some implementations, the MAC layer may decode the container and send the decoded content to the layer corresponding to the container (e.g., MAC decodes a PHY container and pass the content to PHY layer) .
[0071] Note that in the above descriptions, when “layer” is used for example purpose, the same concept / practice also apply to other categories, such as function / domain / target / message types, etc.
[0072] CU-DU based self-contained encoding / decoding scheme for downlink (e.g., configuration)
[0073] In this disclosure, DU of a base station is enhanced to have a self-contained encoding / decoding function for encoding / decoding container. For example, the configuration for the DU (or from the DU) may be encoded as a container, and this container may be transmitted by lower layer signaling (LLS) or lower layer control element (LLCE) , e.g., as a container of a MAC CE (or enhanced MAC CE to differentiate from existing MAC CE –see later sections) . Note that LLS may carry the containers. Various schemes / structures are described below for passing containers from base station (with CU / DU split deployment, such as gNB) to a UE.
[0074] Scheme 1
[0075] FIG. 9A shows an example scheme 1. In this scheme, RRC signaling is transmitted from CU to UE RRC layer in its own path. Lower layer signaling, may be transmitted as DU configuration / signal container (s) from DU to UE lower layer (e.g., MAC layer) . Exemplarily, the UE lower layer is responsible for decoding the containers (s) and using the decoded content (e.g., configuration parameters) to configure its corresponding layer (e.g., RLC, MAC, PHY layers) . In other implementations, the containers may be distributed to their respective layers for decoding.
[0076] Scheme 2
[0077] FIG. 9B shows an example scheme 2. In this scheme, there are 4 steps:
[0078] Step 1. CU encodes its signal (e.g., configuration, or more general, CU payload) into a corresponding CU signal container, and sends it to the DU for transmission.
[0079] Step 2. DU transmits the CU signal container (may also include DU signal container (s) ) to the UE (e.g., using UE lower layer, such as MAC as recipient) .
[0080] Step 3. The UE lower layer is responsible for decoding the DU signal containers (s) and using the decoded content (e.g., configuration parameters) to configure its corresponding layer (e.g., RLC, MAC, PHY layers) . In other implementations, the containers may be distributed to their respective layers for decoding.
[0081] Step 3a. The UE lower layer is also responsible for decoding the CU signal containers and forward the decoded content (e.g., configuration parameters) to CU (so CU may apply the configuration) . In other implementations, the CU container may be distributed to CU for decoding.
[0082] Scheme 3
[0083] FIG. 9C shows an example scheme 3. In this scheme, there are 4 steps:
[0084] Step 1. CU sends its signal (e.g., configuration, or more general, CU payload data) to the DU for transmission. CU does not encode the signal into a container.
[0085] Step 2. DU encodes the CU signal into CU signal container, and transmits the CU signal container (may also include DU signal container (s) ) to the UE (e.g., using UE lower layer, such as MAC as recipient) . Alternatively, DU may encode combined CU signal and DU signal into a single container.
[0086] Step 3a. The UE lower layer is responsible for decoding the CU signal container, and forward the decoded content (e.g., CU signal) to UE RRC layer for further processing.
[0087] In case a container including both CU and DU signals, the UE lower layer may decode this container and retrieve / uncover both CU signal and DU signal, then forward CU signal to CU.
[0088] Step 3b. The UE lower layer is responsible for decoding the DU signal containers (s) and using the decoded content (e.g., configuration parameters) to configure its corresponding layer (e.g., RLC, MAC, PHY layers) . In other implementations, the containers may be distributed to their respective layers for decoding.
[0089] Scheme 4
[0090] FIG. 9D shows an example scheme 4 which is CU centric. In this scheme, there are 4 steps:
[0091] Step 1. DU encodes its signal (e.g., configuration, or more general, DU payload) into a corresponding DU signal container, and sends it to the CU for transmission.
[0092] Step 2. CU transmits the DU signal container (may also include CU signal container (s) ) to the UE (e.g., using UE RRC as recipient) .
[0093] Step 3a. On UE side, UE’s RRC layer may forward the DU signal container to DU for further processing.
[0094] Step 3b. The UE lower layer (e.g., MAC) is responsible for decoding the DU signal containers and using the decoded content (e.g., configuration parameters) to configure its corresponding layer (e.g., RLC, MAC, PHY layers) .
[0095] Scheme 5
[0096] FIG. 9E shows an example scheme 5. In this scheme, CU signal may be transmitted in a similar way as in schemes 1-4, which is not shown in FIG. 9E.
[0097] On DU side, each layer may encode its own container (e.g., RLC layer container, MAC layer container, and PHY layer container) . DU may send these containers in DU in one or more lower layer signals.
[0098] On UE side, upon receiving the LLS carrying the containers, the UE lower layer (e.g., MAC) is responsible for decoding the DU signal containers (s) and using the decoded content (e.g., configuration parameters) to configure its corresponding layer (e.g., RLC, MAC, PHY layers) . In other implementations, the UE lower layer may distribute containers to their respective layers for decoding.
[0099] In some implementations, the UE may have a layer, or a module / entity that has encoding and / or decoding capabilities that apply to encoding schemes such as ANS. 1, or TLV. Such layer or module / entity may be responsible for container encoding / decoding, and UE may use this layer or module / entity to perform decoding and / or encoding related to containers. In this case, the UE lower layer may forward the container (s) to this layer or module / entity for decoding. After the decoding, this layer or module / entity may then forward the decoded content (e.g., configuration to be applied) to the respective layers. This implementation may be used for all of the embodiments in this disclosure when applicable.
[0100] With this implementation, at the network side, the lower layer may use self-contained encoding / decoding scheme (i.e., each layer may be responsible for encoding and / or decoding) , which may help to reduce the inter-action delay between different layers (e.g., upler layer and lower layer) at the NW side; at the UE side, at least due to that the interaction delay between the UE upper layer and lower layer is minimal and may be ignored, the UE can delegate the encoding / decoding tasks to a specific layer or module / entity.
[0101] Using FIG. 9A as an example, the UE lower layer may do part of the decoding work for the LLS / CE first, e.g., UE may decode the sub-header and / or perform security related tasks such as deciphering or integrity checking. With the decoded sub-header, UE may determine that the LLS (or CE) encapsulates a container (alower layer container, such as an RLC, MAC, or PHY container, or a upper layer container, such as an RRC container) , it may then forward this container to the delegated encoding / decoding layer (e.g., rrc layer) or module / entity, then the delegated layer (may perform the decoding and / or configuration work. Note that security protection in this disclosure refers to at least one of: cyphering (encryption) ; or integrity protection.
[0102] For illustrative purposes, the following scenarios demonstrate the application of the above-described schemes.
[0103] Scenario 1
[0104] Only DU intends to modify DU related configuration (e.g., the configuration for the UE lower layers, no CU related configuration is required) . In this case, the DU may directly send the DU related configuration to the UE using a container (s) . Once the UE received the DU container, it may decode the container at the lower layer (e.g., MAC layer) , it may also forward the container to an upper layer (e.g., RRC layer) for the decoding. For example, the Lower-layer Triggered Mobility (LTM) configuration may be generated or modified solely at the DU without CU involvement. Therefore, the LTM related configuration may be encoded at the DU and sent to the UE immediately.
[0105] Scenario 2
[0106] In this scenario, both CU and DU are involved. There are three options depending on which entity (DU or CU) makes a final configuration decision.
[0107] Option 1:
[0108] In this option, The DU makes the final decision and sends both DU / CU configuration to UE.
[0109] The configuration impacts both the CU and the DU, there are 2 options.
[0110] Option 1: The DU make the final decision and send both DU / CU configuration with the above structure 2. An exemplary method as shown in FIG. 10A may include following steps: Step 1. CU sends CU signal to DU, including CU configuration information, or configuration information recommended by CU. DU makes decision on a final CU configuration, based on the CU signal.
[0111] Step 2: DU sends a DU level signal, such as an LLS (lower layer signaling) to UE. The LLS may carry one or more containers for configuration from both DU and CU.
[0112] Option 2:
[0113] In this option, the DU and CU each make their respective final decision. Optionally, CU may make its final configuration decision based on DU input. An exemplary method as shown in FIG. 10B may include following steps:
[0114] Step 1. CU sends CU signal to DU, including CU configuration information, or CU configuration recommended by CU. DU makes decision on a final CU configuration, based on the CU signal in step 1.
[0115] Step 2. DU send it decision (e.g., CU configuration related) back to CU.
[0116] Step 2a. DU sends DU related configuration to UE, using LLS carrying container for DU configuration.
[0117] Step 3. CU sends its final configuration to DU.
[0118] Step 3a. DU sends CU configuration (i.e., upper layer configuration) in step 3 to UE.
[0119] In some implementations, the CU typically hosts upper layer (s) compared to DU, which hosts lower layer (s) .
[0120] Option 3:
[0121] In this option, CU makes a final decision (e.g., for configuration) for both CU and DU.An exemplary method as shown in FIG. 10C may include following steps:
[0122] Step 1. CU sends CU signal to DU, including CU configuration information, or CU configuration recommended by CU. DU makes decision on a final CU configuration, based on the CU signal in step 1.
[0123] Step 2. DU sends it decision based on the CU configuration in step 1 (e.g., DU and / or CU configuration related) as a response to CU.
[0124] Step 2a. DU sends DU related configuration to UE, using LLS carrying container for DU configuration.
[0125] CU then makes a final decision for both CU and DU (e.g., for CU / DU configurations) .
[0126] Step 3. CU sends its final configuration to DU.
[0127] There are two options for DU sending CU / DU configurations to the UE.
[0128] Option 1 includes steps 4a and 4b:
[0129] Step 4a1. DU sends DU related configuration to UE, using LLS carrying container for DU configuration.
[0130] Step 4a2. DU send CU related configuration to UE, using LLS carrying container for CU configuration.
[0131] Option 2 includes step 4b:
[0132] step 4b. DU sends DU and CU related configuration to UE, using LLS carrying containers for DU configuration and CU configuration. For example, DU may use one container for DU configuration and another container for CU configuration.
[0133] Extended / enhanced PDU
[0134] In this disclosure, the existing PDU structure is extended or enhanced to accommodate the container introduced herein. Note that while the data units in the existing PDU are not encoded, the container introduced herein is encoded.
[0135] FIG. 11 shows an example extended PDU 1100, based on the MAC PDU format. The same underlying concepts and principles are applicable to other types of PDUs as well. As shown in FIG. 11, the extended PDU 1100 includes a MAC subPDU that encapsulates one or more containers.
[0136] As the PDU supports any combinations of various types of data segments (MAC CE, MAC Service Data Unit (SDU) , padding, and newly introduced container) , the extended / enhanced PDU 1100 may be referred to as Compound Data Unit (CDU) .
[0137] When the lower layer or the lower layer entity / node (e.g. the DU) has the encoding / decoding function, the layer lower may encode information (e.g., DU and / or CU configuration) and include the encoded information as container in an LLS (Lower layer signaling) or an LLCE (lower layer control element) . For example, the container may be sent as in a sub-PDU of a MAC PDU with a MAC sub-header.
[0138] This disclosure describes various options for MAC sub-PDUs incorporating a container.
[0139] Option 1: Each container has its own dedicated sub-header
[0140] FIG. 12A shows an example subPDU format, with each subPDU encapsulates one container. The subPDU may also be referred to as a Lower Layer (LL) subPDU.
[0141] In the Lower layer (LL) sub-header (e.g. MAC layer sub-header) , there is an Identifier to indicate subPDU content type (e.g. control element, container, padding) , the identifier may be a Logical Channel ID (LCID) or an extended LCID (eLCID) . The container may be from (or serve) different layers / function modules / entities / domains / targets / Msg types. These different layers / function modules / entities / domains / targets / Msg types may be generally referred to as container categories. For example, an LCID=100 indicates that the subPDU carries a container, and the container type is an RLC container; an LCID=100 indicates that the subPDU carries a container, and the container type is a PHY container.
[0142] In the sub-header, different identifiers (e.g. LCIDs or eLCIDs) may be used to indicate different types of containers (e.g., from, or serving different categories) , then the lower layer (e.g. MAC layer) in the recipient end (e.g., UE) may forward the containers to the corresponding categories based on the identifier.
[0143] Alternatively, two identifiers may be included in the sub-header: the first to indicate that the sub-PDU carries a container, and the second to specify the container’s category (e.g., layer / function module / entity / domain / target / Msg type) .
[0144] Alternatively, one identifier is used in the sub-header to indicate subPDU PDU carries a container, but no type information is given (i.e., the identifier does not differentiate container categories) . The container category information is embedded in the container itself. In this case, the recipient may decode the container, and from the uncovered content of the container, it may locate container category information (e.g., RLC, PHY, or RRC layer) . After the recipient decode the container, it may then forward the content to its corresponding category (e.g., layer / function module / entity / domain / target / Msg type) .
[0145] The sub-header may further carry at least one of:
[0146] ● A length indicator indicating the length of the container; or
[0147] ● A security information (e.g., security information block in the subPDU) associated with the container or the subPDU, used for cyphering (encryption) and / or integrity protection purposes.
[0148] Option 2: One sub-header for multiple containers
[0149] FIG. 12B shows an example subPDU format, with each subPDU encapsulates more than one containers. The subPDU may also be referred to as a Lower Layer (LL) subPDU.
[0150] In some implementations, in the LL sub-header (e.g. MAC layer sub-header) , there is an identifier to indicate subPDU content type (e.g. control element, container, padding) , the identifier may be a Logical Channel ID (LCID) or an extended LCID (eLCID) . All containers in the subPDU may share this identifier. The lower layer entity (e.g., MAC entity) may decode each container based on the number of containers and length of each container carried in the sub-header.
[0151] In some implementations, each container may have a corresponding identifier in the sub-header, which indicates the category of the container (e.g., one to one mapping of identifier and container) . On the recipient side, it may forward the containers to their corresponding categories based on the category information. Note that category information carries information on where the container is from and where the container should be dispatched to.
[0152] Alternatively, two identifiers may be included in the sub-header: the first identifier to indicate that the sub-PDU carries containers, and the second identifier to specify the container’s category (e.g., layer / function module / entity / domain / target / Msg type) . Note that the subPDU may only need to have one first identifier, but for each container in the subPDU, there may be a corresponding second identifier.
[0153] The sub-header may further carry at least one of:
[0154] ● A quantity indicator indicating a number of containers carried in the subPDU;
[0155] ● For each container: a length indicator indicating the length of the container; or
[0156] ● A security information (e.g., security information block in the subPDU) associated with the container or the subPDU, used for cyphering (encryption) and / or integrity protection purposes.
[0157] In some implementations, in a same subPDU, one container may correspond to DU (e.g., carrying DU configuration information) and one container may correspond to CU (e.g., carrying CU configuration information) .
[0158] In some implementations, in a same subPDU, containers may correspond to different categories (layer / function module / entity / domain / target / Msg type) .
[0159] FIG. 12C shows an example CDU (or extended PDU, enhanced PDU) , which includes two subPDUS. The subPDUs 1 and 2 (also noted as LL subPDUs) encapsulates containers from different categories (e.g., layer / entity / module / function / domain / target / Message type) . For example, subPDU 1 may encapsulate containers from the DU, while subPDU2 may encapsulate containers from the CU. An identifier (e.g., LCID / eLCID) in sub-header of each subPDU may indicate the container category.
[0160] In some implementations, the containers may have different security related configurations. For example, they may have different security keys / parameters / algorithms.
[0161] Not shown in FIG. 12C, the CDU may further include one or more: LL SDUs, or LL CEs (control elements) .
[0162] The encoding / decoding scheme for the container may include at least one of: TLV (Type-Length-Value) and ASN. 1 (Abstract Syntax Notation One) .
[0163] In some implementations, for container carrying a message, the message type may be encoded in the container itself or in the sub-header corresponding to the container.
[0164] FIG. 12D shows two example subPDUs each carrying one container. Each container has its own ID (e.g. different LCIDs) .
[0165] FIG. 12E shows two example subPDUs each carrying one container. The containers share a same first identifier (LCID1) , but each container has its own second ID (e.g. additional ID1, additional ID2) . For example, LCID1 indicates the content in the subPDU is container, and LCID2 indicates the container type (e.g., for what layer / entity / module / function / domain / target / Message type) .
[0166] FIG. 12F shows an example subPDU carrying two containers. Each container has its own identifier and length indicator (LCID1, length 1; LCID2, length 2) .
[0167] FIG. 12G shows an example subPDU carrying two containers. Each container has its own two identifiers and length indicator (LCID1, additional ID1, length 1; LCID2, additional ID2, length 2) .
[0168] Security processing
[0169] In this disclosure, security processing or security protection may generally refer to cyphering (encryption) and / or integrity protection.
[0170] In some embodiments, referring to FIG. 9A, for CU RRC signaling (e.g., CU configuration, or configuration from CU) , when the RRC signaling is sent as a MAC SDU, it may be sent with or without security protection, the upper layer (e.g. RRC / PDCP / RLC) may indicate the lower layer whether to add security or not
[0171] For DU signaling (e.g., DU configuration, or configuration from DU) , it may be sent as a lower layer container (e.g., MAC layer container sent in CDU, or enhanced MAC PDU) , the container be security protected (including integrity protection and / or ciphering) at the lower layer (e.g., MAC layer) .
[0172] In some embodiments, the CU signaling container may be sent to the DU without security protection, in which case security processing can be applied at the lower layer (e.g., MAC layer) . The MAC layer may apply integrity protection and ciphering to the DU configuration container and / or the CU configuration container, either jointly or separately. The CU can also indicate to the DU whether, and how, lower-layer security protection should be applied.
[0173] If the CU configuration is encoded and security-protected at the CU, it may include an indication of whether additional lower-layer protection is required. This means that double security protection is possible (by CU and DU, respectively) . Alternatively, if the CU configuration is encoded at the DU, or encoded at the CU without security protection, lower-layer security mechanisms may be applied.
[0174] In case of CDU being implemented as an extension / enhancement to existing PDU (e.g., MAC PDU) , the container sub-PDU (i.e., sub-PDU encapsulate container (s) ) may follow similar processing as a MAC SDU or MAC Control Element.
[0175] When the lower layer intends to apply security processing, two processing methods may be used:
[0176] Method 1: Apply security processing independently to each lower layer container, or lower layer SDU, or lower layer control element.
[0177] Method 2: Apply security processing jointly to at least one of: a lower layer container, a lower layer SDU, or a lower layer control element.
[0178] The determination of whether a lower layer SDU, control element, or container requires security processing may follow one of the following approaches:
[0179] Method 1: The upper layer protocol of the lower layer entity explicitly indicates whether security processing is required for a given SDU, control element, or container. For example, the upper layer may be an RRC layer, and the lower layer may be a MAC layer. In this case, RRC layer may indicated to MAC layer whether security processing is required.
[0180] Method 2: Security processing is applied to specific lower layer SDUs, control elements, or containers based on protocol agreements, predefined protocol, or signaling configurations.
[0181] FIG. 13A shows an example CDU (noted as LL subPDU in FIG. 13A as an example, may also be referred to as subPDU for simplicity) that is security processed. In the CDU, security processing is applied individually to a lower layer container, a lower layer SDU, or a lower layer control element. As shown in FIG. 13A, subPDUs 1 and 4 are security processed (e.g., with security information added, and / or data payload security processed / encrypted) . The sub-header may include security processing status of its corresponding container, MAC CE, or SDU. If the subPDU is security processed, it may also include a integrity protection information block.
[0182] FIG. 13B shows an example sub-header that may be used in FIG. 13A. The sub-header may include security related information, such as: key information, security algorithm information; and security processing input.
[0183] FIG. 14A shows another example CDU with security processing. In FIG. 14A, multiple data units (container, SDU, and control element, CE) may be security processed jointly. For example, “data1 after security processing” block may include two containers (after security processing) . There is also a security information block corresponding to data1 block. Optionally, for each security process data block, there may be corresponding integrity protection information block (or verification information block) .
[0184] FIG. 14B shows another example CDU with security processing. In FIG. 14B, a CDU includes MAC subPDU 1 and subPDU 2. SubPDU1 is a combination of two other subPDUs (which forms data 1 after security processing block) . In this example, multiple subPDUs (subPDU 1 and subPDU 2) may share a common security information block. This common security information block may be implemented as a LL sub-PDU containing a specific type of LL CE.
[0185] The security information block in FIGs. 14A-14B may include at least one of:
[0186] ● Security processing input parameters;
[0187] ● Key information; or
[0188] ● Algorithm information (for encryption and / or cyphering) .
[0189] The keys are applied to lower layer security processing of data and may be referred to as low-layer keys (LLK) . These keys include:
[0190] ● Encryption / decryption keys and integrity protection / verification keys
[0191] ○ Encryption / decryption keys may be used for encrypting / decrypting Lower layer SDU(s) or lower layer control element (s) or the lower layer container (s) , LL PDUs, or Transport Blocks (TBs) .
[0192] ○ Integrity protection / verification keys may be used for integrity protection / verification of Lower layer SDU (s) or lower layer control element (s) or the lower layer container (s) , LL PDUs, or Transport Blocks (TBs) .
[0193] ●Control-plane encryption / decryption keys, control-plane integrity protection / verification keys, user-plane encryption / decryption keys, and user-plane integrity protection / verification keys.
[0194] ○ Control-plane keys may be used for security processing of Lower layer SDU (s) or lower layer control element (s) or the lower layer container (s) , LL PDUs, or Transport Blocks (TBs) .
[0195] ○ User-plane keys may be used for security processing of Lower layer SDU (s) or lower layer control element (s) or the lower layer container (s) , LL PDUs, or Transport Blocks (TBs) .
[0196] In some embodiments, at the network side (e.g., CU and DU) , the CU may be responsible for make decision on: 1) whether security processing is required; and 2) security processing configuration information. In some implementations, CU may indicate to DU on such decision. In some implementations, the decision applies to a CDU level. That is, all containers under a same CDU may be security processed using a same security processing configuration. In some implementations, the decision applies to container level. That is, the granularity is at container level, and the CU may decide how each container is security protected (e.g., container 1 and container 2 may or may not have same security protection configurations) . In some implementations, the decision may be at a layer level. That is, all containers belonging to a same layer (or entity, module, domain, target, message type) may use a same security processing configuration. In some implementations, the decision applies to containers at different layers. In some implementations, the different layers are all in DU. In some implementations, the security protection configurations may be predefined or agreed between the network and the UE. In some implementations, the network may send the security protection configurations to the UE via, for example, an RRC signaling.
[0197] Note that in this disclosure, the lower layer may typically include a MAC layer, but it may also include other layer, such as PDCP / RLC / PHY layer at the UE or network side, or the DU (and layers in DU) at the network side. Take the network side as an example, if the base station employs a CU-DU split architecture, the CU may be considered as the higher layer, while the DU can be considered as the lower layer, and any layer in the DU (e.g., PDCP / RLC / MAC / PHY) can also be considered as the lower layer. From a DU perspective, if it includes PDCP / RLC / MAC / PHY from high layer to low layer, then the PDCP may be considered as the high layer while the at least one of RLC / MAC / PHY layers can be se considered as the lower layer, or at least one of PDCP / RLC layers can be considered as the high layer, while MAC / PHY can be considered as the lower layer.
[0198] With each subPDU encapsulates more than one containers. The subPDU may also be referred to as a Lower Layer (LL) subPDU. The resulting lower-layer PDU includes each independently security-processed SDU, control element, or container, along with its corresponding subheader. The subheader indicates the security processing status of the associated SDU, control element, or container. A single lower layer PDU may include one or more security-processed data blocks along with optional integrity protection information.
[0199] Transmit LLS, LLCE, or LL container to UE
[0200] As described above, the lower layer signaling (LLS) , lower layer control element (LLCE) , or lower layer container may be generated at, for example the DU's MAC layer (may also be generate at other layer) . However, this approach typically requires these elements to be transmitted in sequence. If segmentation or reordering is necessary, particularly in mobility scenarios where signals may be weak or data packets arriving out of order. In such cases, poor channel conditions may prevent the network from assigning a large uplink grant, making efficient handling essential.
[0201] In some embodiments, the container may be generated at the RLC layer. The RLC layer supports segmentation and reordering, which is beneficial under poor radio conditions.
[0202] There are three exemplary methods for delivering the LLS, LLCE, or lower-layer container from network side to the UE:
[0203] Method 1: Using RLC layer
[0204] The DU may encode the LLS, LLCE, or lower-layer container and forward it to the RLC layer (e.g., lower layer container may be treated as RLC container or a RLC SDU) . The MAC layer may process LLS or LLCE or LL container as an MAC SDU. Then the above method on “Extended / enhanced PDU” can be used at the RLC layer, e.g., by use the information in the sub-header to indicate it’s LLS or LLCE.
[0205] In some implementations, MAC layer may use the security processing method as described earlier to further add security protection for LLS, LLCE, or LL container. Then at the UE side, the MAC layer is responsible for the deciphering, and / or integrity checking, sending the MAC SDU to the RLC, and the decoding maybe done at the RRC layer.
[0206] Method 2: Using DU terminated Signaling Radio Bearer (SRB) or PDCP layer
[0207] In some implementations, a DU terminated SRB may be added. Additionally or alternatively, the DU may also implement or add a PDCP layer. The DU may encode the LLS, LLCE, or lower-layer container and forward it to the PDCP layer for security processing. The PDCP layer will then send the security processed LLS, LLCE, or lower-layer container to the RLC layer as an RLC SDU.
[0208] Method 3: Using MAC layer
[0209] In some implementations, the DU may encode the LLS, LLCE, or lower-layer container, and sent it as a MAC layer container. The MAC will send it one by one in sequence.
[0210] Interface implementation downlink
[0211] F1 interface and inter-layer interface
[0212] In some embodiments, as shown in FIGs. 9B and 9C, CU may forward a CU container to DU, and let DU send it to the UE. CU may indicate, via the F1 interface (e.g., F1-C or F1-U interface as shown in FIG. 4) , whether security processing at DU side is required.
[0213] In some implementations, the CU container is already security processed when sending to the DU. The CU may indicate whether lower-layer security processing (e.g., at the DU side) is required. If such processing is required, it results in two layers of security: one applied at the CU level and another at the DU level.
[0214] In some implementations, the CU container is not security processed when sending to the DU. The CU may indicate whether lower-layer security processing (e.g., at the DU side) is required, and may further indicate security protection information (e.g., keys, parameters, algorithms, etc., also referred to as security protection configuration) . In other words, the CU determines whether and how the CU container should be security protected. As a result, the security processing mechanisms (e.g., keys, parameters, algorithms) used for the CU container and the DU container may be the same or different. Alternatively, if CU does not specify the lower-layer security processing details, the DU may be in charge of choosing a security processing mechanism to protect CU container.
[0215] Note that F1 interface is used for exemplary and illustration purposes. The same principle and concept apply to other inter-layer interfaces (e.g., RLC layer to MAC layer interface, PHY layer to MAC layer interface, and so on) . For example, RLC layer, when passing RLC container to MAC layer, may notify similar information to MAC layer as described for the F1 interface.
[0216] Xn interface
[0217] The Xn interface is used for inter base station communication. In a base station with a CU / DU split architecture, at least one of following container types may be used: a CU container or a DU container. One base station may notify another base station about the configuration and security protection information for at least one of the container types.
[0218] In some implementations, Xn interface may include any interface between the upper layers of two wireless nodes (e.g., gNB) or any interface between the lower layers of two wireless nodes.
[0219] CU-DU based self-contained encoding / decoding scheme for uplink (e.g., UE capability reporting / UE request / UE indication)
[0220] This section generally describes uplink containers, which may be transmitted from a UE to a base station (e.g., a gNB) . The underlying principle and concept are similar to encoding / decoding scheme for downlink as described in previous sections.
[0221] For uplink containers, such as containers for UE Capability Reporting / UE request / UE indication, if the DU has the self-contained encoding and / or decoding capability, then such uplink containers (e.g., for UE capability / UE indication / UE request) for the DU may be encoded at the UE (e.g., a lower layer such as MAC) and decoded at the DU.
[0222] In the below examples, UE capability reporting is used for illustration purposes, the same underlying principle and concept may also been applied to other types of uplink containers, such as container for UE indication or UE request to the network.
[0223] In some embodiments, as shown in FIG. 15A, the UE Capability may be reported by RRC message with a DU level container and / or a CU level container.
[0224] In some embodiments, as shown in FIG. 15B, the UE Capability may be reported by a lower layer signaling (e.g., MAC layer) . There are 4 steps:
[0225] Step 1. UE high layer (e.g., RRC layer or above) encodes its signal (e.g., capability) into a corresponding high layer signal container, and sends it to UE lower layer for transmission. Alternatively, UE higher layer may send higher layer signal directly to UE lower layer, and let UE lower layer encode the signal to higher layer signal container.
[0226] Step 2. UE lower layer transmits the high layer signal container (may also transmit lower layer signal container (s) ) to the DU (e.g., using DU lower layer, such as MAC as a recipient) , using a lower layer signaling (LLS) .
[0227] Step 3. The DU is responsible for decoding the LLS and forward the decoded content to DU lower layer (e.g., RLC, MAC, PHY layers) . In other implementations, the lower layer signal containers may be distributed to their respective layers for decoding.
[0228] Step 3a. The DU may also be responsible for decoding the high layer container in the LLS and forward the decoded content (i.e., higher layer signal) to CU. In other implementations, the CU container may be distributed to CU for decoding.
[0229] Note that in some implementations, it is possible that LLS may carrying a container that carries mixed content. For example, it may carry signal for both higher layer (e.g., RRC) and lower layer (e.g., MAC, PHY) . In this case, the DU may decode the container, and pass signaling to its corresponding layer.
[0230] In some embodiments, as shown in FIG. 15C, two signalings are used. The UE higher layer may send higher layer capability to CU via a high layer signaling (e.g., RRC signaling) , and UE lower layer (e.g., MAC layer) may send lower layer capability using lower layer containers carried in lower layer signaling (LLS) . For example, the lower layer signaling may carry three lower layer containers: RLC layer container (for RLC layer capability) , MAC layer container (for MAC layer capability) , and PHY layer container (for PHY layer capability) .
[0231] In some embodiments, as shown in FIG. 15D, a peer to peer type communication is used between UE and base station. From UE side, each lower layer (e.g., RLC, MAC, and PHY) may encode its own container (e.g., capability information container) . UE may use an LLS to carry these containers and send the LLS to DU. DU may distribute these containers to their respective layers (e.g., RLC, MAC, and PHY) for decoding, and may further use the decoded content to configure these layers.
[0232] In some embodiments, as illustrated in FIG. 15E, a centralized scheme may be employed. The UE may encode a container comprising information associated with a combination of layers (e.g., RLC, MAC, and PHY) . For example, a single container may include capability information corresponding to both the RLC and MAC layers. The UE may transmit the container to the DU via an LLS. Upon reception, the DU may decode the container and distribute the capability information to the respective protocol layers.
[0233] FIG. 15F shows an exemplary scheme similar to that as showin FIG. 15E, but only includes containers for UE lower layer.
[0234] Note that for uplink communication, the extended / enhanced PDU as described in previous sections may be employed. Exemplarily, the CU may be considered as a higher layer (compared to DU) . DU itself may be considered as a lower layer, while DU may also be classified a including multiple layers.
[0235] It is noted that, for uplink communication, the extended / enhanced PDU as described in prior sections, may be utilized. In some embodiments, the CU may be regarded as a higher-layer entity relative to the DU. The DU may be considered a lower-layer entity; however, the DU may itself encompass multiple protocol layers. In some implementations, a container may have its dedicated sub-header. In some implementations, multiple containers may share a same sub-header. The multiple containers may include containers from different layers / entities / modules / functions / domains / targets / Message types. The multiple containers may include containers from a same layer / entity / module / function / domain / target / Message type. In some implementations, in a same PDU (or compound data unit, to be more general) , one subPDU may include only one container and its dedicated sub-header, another PDU may include multiple PDUs sharing a same sub-header.
[0236] It is noted that, for uplink communication, the security processing methods as described in prior sections, may be utilized.
[0237] In some embodiments, the DU may determine whether and how to do integrity protection check / deciphering.
[0238] In some embodiments, the DU may decode an uplink container (e.g., UE layer capability information container for various layers, CU, or DU) , and forward decoded information to its respective layer / entity for processing. For example, DU may forward the decoded information to CU in signaling format via F1 interface.
[0239] In some embodiments, the DU may forward an uplink container (e.g., UE layer capability information container for various layers, CU, or DU) to its destined (or corresponding) layer / entity / module / function / domain / target for decoding. For example, DU may for forward a CU container to CU via F1 interface, and the CU may decode the container
[0240] In some embodiments, DU may forward DU capability restriction information as a container to the CU, and CU may forward CU capability restriction information as a container to the DU.
[0241] In some embodiments, CU may indicate security related configuration to the DU. The security related configuration may include, for example, security key (e.g., root key) , algorithms, input parameters, and so on.
[0242] In some embodiments, the Xn interface may be used to transfer container based information between base stations. CU and / or DU container may be transferred from one base station to another. The containers may include, for example, capability restriction information, security related configuration, etc.
[0243] In some embodiments, the Ng interface may be used to transfer container based information between base station and core network.
[0244] In some embodiments, in UE or base station, a first layer may forward a container to a second layer for transmitting. The container may already be security protected by the first layer. The first layer may indicate to the second layer whether further security protection is required from the second layer. If the container is not security protected by the first layer, the first layer may indicate to the second layer whether further security protection is required from the second layer, and may further indicate security protection information (e.g., keys, parameters, algorithms, etc. ) . In other words, the first layer determines whether and how the first layer container should be security protected. For example, if the first layer indicates security protection is required for a first layer container, the second layer will add security protection to it, based on the security protection information indicated by the first layer.
[0245] As shown in FIGs. 9B and 9C, CU may forward a CU container to DU, and let DU send it to the UE. CU may indicate, via the F1 interface (e.g., F1-C or F1-U interface as shown in FIG. 4) , whether security processing at DU side is required.
[0246] In some implementations, the CU container is already security processed when sending to the DU. The CU may indicate whether lower-layer security processing (e.g., at the DU side) is required. If such processing is required, it results in two layers of security: one applied at the CU level and another at the DU level.
[0247] In some implementations, the CU container is not security processed when sending to the DU. The CU may indicate whether lower-layer security processing (e.g., at the DU side) is required, and may further indicate security protection information (e.g., keys, parameters, algorithms, etc. ) . In other words, the CU determines whether and how the CU container should be security protected. As a result, the security processing mechanisms (e.g., keys, parameters, algorithms) used for the CU container and the DU container may be the same or different. Alternatively, if CU does not specify the lower-layer security processing details, the DU may be in charge of choosing a security processing mechanism to protect CU container.
[0248] An exemplary method performed by a first network element according to embodiments in this disclosure may include a portion or all of the following steps: step 1: transmitting, by the first network element or by a first layer of the first network element, to a wireless device, a message comprising a Compound Data Unit (CDU) , the CDU comprising at least one container, wherein each of the at least one container comprises data encoded using a predefined encoding scheme.
[0249] In any portion or combination of the implementations above, the at least one container comprises a first container; or a second container.
[0250] In any portion or combination of the implementations above, the first container corresponds to the first layer, and wherein the second container corresponds to a second layer different from the first layer.
[0251] In any portion or combination of the implementations above, the first container is destined to a peer layer corresponding to the first layer, and wherein the second layer is destined to a peer layer corresponding to the second layer.
[0252] In any portion or combination of the implementations above, the method further comprising at least one of: receiving, from a second network element, a data payload or a signaling message comprising signaling payload; and encoding the data payload or the signaling payload in the signaling message to the second container.
[0253] In any portion or combination of the implementations above, the second container further encapsulates a data payload or a signaling payload from the first network element.
[0254] In any portion or combination of the implementations above, the signaling message further indicates whether a security protection is required for the signaling payload, the method further comprising: when the security protection is required, adding the security protection to the second container.
[0255] In any portion or combination of the implementations above, adding the security protection to the second container comprises at least one of: adding the security protection independently to the second container; or adding the security protection to the second container together with at least another container.
[0256] In any portion or combination of the implementations above, the method further comprising receiving the second container from at least one of: a second network element; or the second layer.
[0257] In any portion or combination of the implementations above, the method further comprising: adding a security protection to second container based on a security indicator sent from the second network element or the second layer.
[0258] In any portion or combination of the implementations above, when the second container are received from the second network element or the second layer: the second container is security protected; or the second container is not security protected.
[0259] In any portion or combination of the implementations above, each of the at least one container is carried in its dedicated sub Data Unit (subDU) in the CDU, and wherein the first container is carried in a first subDU in the CDU.
[0260] In any portion or combination of the implementations above, the first container and the second container are carried in a first subDU in the CDU.
[0261] In any portion or combination of the implementations above: the first subDU comprises a first subheader; and the first subheader comprises a first indicator indicating a type of the first subDU among a list of subDU types, the list of subPDU types comprising at least one of: a control element type; a container type; or a padding type, or a Service Data Unit (SDU) type.
[0262] In any portion or combination of the implementations above, the first indicator comprises at least one of: a Logical Channel ID (LCID) ; or an Extended LCID.
[0263] In any portion or combination of the implementations above, the first container and the second container each corresponds to a different target among a list of targets, the list of targets comprising at least one of: a layer; a module; an entity; a domain; or a message type.
[0264] In any portion or combination of the implementations above, the first indicator further indicates a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.
[0265] In any portion or combination of the implementations above, the first subheader further comprises a second indicator indicating a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.
[0266] In any portion or combination of the implementations above, the target comprises at least one of: a layer; a module; a function; an entity; a domain; or a message type.
[0267] In any portion or combination of the implementations above, the first subheader further comprises at least one of: a length indicator indicating a length of the first container; or a security information associated with the first container.
[0268] In any portion or combination of the implementations above: the at least one container corresponds to a Radio Link Control (RLC) layer of the first network element and is passed as a Service Data Unit (SDU) to a Medium Access Layer (MAC) of the first network element; the at least one container corresponds to a Packet Data Convergence Protocol (PDCP) layer of the first network element and is passed as an RLC SDU to the RLC layer of the first network element; or the at least one container corresponds to the MAC layer of the first network element.
[0269] In any portion or combination of the implementations above, the method further comprising: receiving, from a second network element, a security processing information carrying at least one of: an indication whether a security protection needs to be added for at least one of the first container; the second container; or the CDU; or a security processing configuration instructing a manner for adding the security protection.
[0270] In any portion or combination of the implementations above, the security processing configuration comprises at least one of: a security processing input parameter; key information; or algorithm information.
[0271] In any portion or combination of the implementations above, the first container and the second container correspond to different layers or different entities.
[0272] In any portion or combination of the implementations above, the first container and the second container correspond to different layers in the first network element or different entities in the first network element.
[0273] In any portion or combination of the implementations above, the predefined encoding scheme comprises at least one of: an Abstract Syntax Notation One (ASN. 1) scheme; or a Type-Length-Value (TLV) scheme.
[0274] In any portion or combination of the implementations above, the first layer comprises at least one of: a Medium Access Control (MAC) layer; a Radio Link Control (RLC) layer; a Packet Data Convergence Protocol (PDCP) layer, or a PHY layer.
[0275] In any portion or combination of the implementations above, the first network element comprises at least one of: a Distributes Unit (DU) of a base station; or a Central Unit (CU) of the base station.
[0276] In any portion or combination of the implementations above: the first network element comprises a DU of a base station, and the second network element comprises a CU of the base station; or the first network element comprises the CU of a base station, and the second network element comprises the DU of the base station.
[0277] An exemplary method performed by a wireless device according to embodiments in this disclosure may include a portion or all of the following steps: step 1: receiving, by the wireless device or a first layer of the wireless device, from a network element, a message comprising a Compound Data Unit (CDU) , the CDU comprising at least one container, wherein each of the at least one container comprises data encoded using a predefined encoding scheme.
[0278] In any portion or combination of the implementations above, the at least one container comprises a first container; or a second container.
[0279] In any portion or combination of the implementations above, the first container corresponds to the first layer, and wherein the second container corresponds to a second layer different from the first layer.
[0280] In any portion or combination of the implementations above, the first container is originated from a peer layer corresponding to the first layer, and wherein the second layer is originated from a peer layer corresponding to the second layer.
[0281] In any portion or combination of the implementations above, the method further comprising: decoding the first container at the first layer; and decoding the second container at the second layer.
[0282] In any portion or combination of the implementations above, the method further comprising: decoding, by one of: a predefined layer; a container processing module; or a container processing entity, the first container and the second container; and dispatching decoded first container and decoded second container to their respective layers.
[0283] In any portion or combination of the implementations above, the method further comprising: forwarding the firsts container and the second container to one of: the predefined layer; the container processing module; or the container processing entity.
[0284] In any portion or combination of the implementations above, the predefined layer comprises at least one of: a Medium Access Control (MAC) layer; a Radio Link Control (RLC) layer; a Packet Data Convergence Protocol (PDCP) layer; or a PHY layer.
[0285] In any portion or combination of the implementations above, at least one of following conditions is satisfied: the first container and the second container are individually security protected; the first container and the second container are jointly security protected; or the CDU is security protected.
[0286] In any portion or combination of the implementations above, the method further comprising performing security processing on at least one of following levels: an individual container level; a multiple containers level; or a CDU level.
[0287] In any portion or combination of the implementations above, each of the at least one container is carried in its dedicated sub Data Unit (subDU) in the CDU, and wherein the first container is carried in a first subDU in the CDU.
[0288] In any portion or combination of the implementations above, the first container and the second container are carried in a first subDU in the CDU.
[0289] In any portion or combination of the implementations above: the first subDU comprises a first subheader; and the first subheader comprises a first indicator indicating a type of the first subDU among a list of subDU types, the list of subPDU types comprising at least one of: a control element type; a container type; or a padding type, or a Service Data Unit (SDU) type.
[0290] In any portion or combination of the implementations above, the first indicator comprises at least one of: a Logical Channel ID (LCID) ; or an Extended LCID.
[0291] In any portion or combination of the implementations above, the first container and the second container each corresponds to a different target among a list of targets, the list of targets comprising at least one of: a layer; a module; an entity; a domain; or a message type.
[0292] In any portion or combination of the implementations above, the first indicator further indicates a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.
[0293] In any portion or combination of the implementations above, the first subheader further comprises a second indicator indicating a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.
[0294] In any portion or combination of the implementations above, the target comprises at least one of: a layer; a module; a function; an entity; a domain; or a message type.
[0295] In any portion or combination of the implementations above, the first subheader further comprises at least one of: a length indicator indicating a length of the first container; or a security information associated with the first container.
[0296] In any portion or combination of the implementations above, the predefined encoding scheme comprises at least one of: an Abstract Syntax Notation One (ASN. 1) scheme; or a Type-Length-Value (TLV) scheme.
[0297] In any portion or combination of the implementations above, the first layer comprises at least one of: a Medium Access Control (MAC) layer; a Radio Link Control (RLC) layer; a Packet Data Convergence Protocol (PDCP) layer; or a PHY layer.
[0298] In any portion or combination of the implementations above, the network element comprises a base station.
[0299] In this disclosure, a single container may carry information / instruction / command for one or more features.
[0300] In this disclosure, containers may correspond to various categories (e.g., (layer / function module / entity / domain / target / Msg type) . For example, there are 3 containers corresponding to RRC layer, RLC layer, and MAC layer, respectively. These containers may be transmitted / received in various manners. For example, they may be handled via a central unit handling containers (e.g., hub) , or they may be transmitted / received from a specific layer, such as a MAC layer.
[0301] In this disclosure, it is noted that the described embodiments may be implemented at both the network side (e.g., base station, CU and DU) and the UE side. For illustrative purposes, certain operations may be described as being performed by the network; however, it is understood that corresponding or complementary operations may be performed by the UE, and vice versa. For instance, if the network assembles containers according to a defined format, the UE may disassemble the containers using the same format. Similarly, if the network applies security processing, such as ciphering and / or integrity protection, to containers or CDUs, the UE may perform corresponding security processing, such as deciphering and / or integrity verification, to recover and validate the received content. The reverse direction (i.e., UE to network) may be handled in an analogous manner.
[0302] In this disclosure, the steps in each embodiment are for illustration purposes only and other alternatives may be derived based on the disclosed embodiments as desired. For example, only part of the steps may need to be performed. For another example, the sequence of the steps may be adjusted. For another example, several steps may be combined (e.g., several messages may be combined in one message) . For another example, a single step may be split (e.g., one message may be sent via two sub-messages) . For another example, based on practical need, the embodiment described in this disclosure may be split to form a sub-embodiment, therefore, not all steps in an embodiment are required.
[0303] The exemplary embodiments in this disclosure merely serve as examples and do not pose limitations. Any steps and / or operations in one same embodiment / implementation or more than one different embodiments / implementation in the present disclosure may be partially performed, combined, or arranged in any amount or order, as desired. Two or more of the steps and / or operations may be performed in parallel. Various embodiments and implementations in the disclosure may be used separately or combined in any order. Further, each of the methods (or embodiments) may be implemented by processing circuitry (e.g., one or more processors or one or more integrated circuits) .
[0304] The description and accompanying drawings above provide specific example embodiments and implementations. The described subject matter may, however, be embodied in a variety of different forms and, therefore, covered or claimed subject matter is intended to be construed as not being limited to any example embodiments set forth herein. A reasonably broad scope for claimed or covered subject matter is intended. Among other things, for example, subject matter may be embodied as methods, devices, components, systems, or non-transitory computer-readable media for storing computer codes. Accordingly, embodiments may, for example, take the form of hardware, software, firmware, storage media or any combination thereof. For example, the method embodiments described above may be implemented by components, devices, or systems including memory and processors by executing computer codes stored in the memory.
[0305] Throughout the specification and claims, terms may have nuanced meanings suggested or implied in context beyond an explicitly stated meaning. Likewise, the phrase “in one embodiment / implementation” as used herein does not necessarily refer to the same embodiment and the phrase “in another embodiment / implementation” as used herein does not necessarily refer to a different embodiment. It is intended, for example, that claimed subject matter includes combinations of example embodiments in whole or in part.
[0306] In general, terminology may be understood at least in part from usage in context. For example, terms, such as “and” , “or” , or “and / or, ” as used herein may include a variety of meanings that may depend at least in part on the context in which such terms are used. Typically, “or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein, depending at least in part upon context, may be used to describe any feature, structure, or characteristic in a singular sense or may be used to describe combinations of features, structures or characteristics in a plural sense. Similarly, terms, such as “a, ” “an, ” or “the, ” may be understood to convey a singular usage or to convey a plural usage, depending at least in part upon context. In addition, the term “based on” may be understood as not necessarily intended to convey an exclusive set of factors and may, instead, allow for the existence of additional factors not necessarily expressly described, again, depending at least in part on context.
[0307] Reference throughout this specification to features, advantages, or similar language does not imply that all of the features and advantages that may be realized with the present solution should be or are included in any single implementation thereof. Rather, language referring to the features and advantages is understood to mean that a specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the present solution. Thus, discussions of the features and advantages, and similar language, throughout the specification may, but do not necessarily, refer to the same embodiment.
[0308] Furthermore, the described features, advantages and characteristics of the present solution may be combined in any suitable manner in one or more embodiments. One of ordinary skill in the relevant art will recognize, in light of the description herein, that the present solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other instances, additional features and advantages may be recognized in certain embodiments that may not be present in all embodiments of the present solution. The embodiments in this disclosure are for illustration purposes. Various embodiments may be combined to form a new embodiment, to provide more comprehensive coverage.
Claims
A method for wireless communication, performed by a first network element, the method comprising:transmitting, by the first network element or by a first layer of the first network element, to a wireless device, a message comprising a Compound Data Unit (CDU) , the CDU comprising at least one container, wherein each of the at least one container comprises data encoded using a predefined encoding scheme.The method of claim 1, wherein the at least one container comprises a first container; or a second container.The method of claim 2, wherein the first container corresponds to the first layer, and wherein the second container corresponds to a second layer different from the first layer.The method of claim 3, wherein the first container is destined to a peer layer corresponding to the first layer, and wherein the second layer is destined to a peer layer corresponding to the second layer.The method of any one of claims 3-4, further comprising at least one of:receiving, from a second network element, a data payload or a signaling message comprising signaling payload; andencoding the data payload or the signaling payload in the signaling message to the second container.The method of claim 5, wherein the second container further encapsulates a data payload or a signaling payload from the first network element.The method of claim 5, wherein the signaling message further indicates whether a security protection is required for the signaling payload, the method further comprising:when the security protection is required, adding the security protection to the second container.The method of claim 7, wherein adding the security protection to the second container comprises at least one of:adding the security protection independently to the second container; oradding the security protection to the second container together with at least another container.The method of any one of claims 3-4, further comprising receiving the second container from at least one of: a second network element; or the second layer.The method of claim 9, further comprising:adding a security protection to second container based on a security indicator sent from the second network element or the second layer.The method of claim 10, wherein when the second container are received from the second network element or the second layer:the second container is security protected; orthe second container is not security protected.The method of claim 2, wherein each of the at least one container is carried in its dedicated sub Data Unit (subDU) in the CDU, and wherein the first container is carried in a first subDU in the CDU.The method of claim 2, wherein the first container and the second container are carried in a first subDU in the CDU.The method of any one of claim 12-13, wherein:the first subDU comprises a first subheader; andthe first subheader comprises a first indicator indicating a type of the first subDU among a list of subDU types, the list of subPDU types comprising at least one of: a control element type; a container type; or a padding type, or a Service Data Unit (SDU) type.The method of claim 14, wherein the first indicator comprises at least one of: a Logical Channel ID (LCID) ; or an Extended LCID.The method of claim 14, wherein the first container and the second container each corresponds to a different target among a list of targets, the list of targets comprising at least one of: a layer; a module; an entity; a domain; or a message type.The method of claim 16, wherein the first indicator further indicates a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.The method of claim 16, wherein the first subheader further comprises a second indicator indicating a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.The method of claim 18, wherein the target comprises at least one of: a layer; a module; a function; an entity; a domain; or a message type.The method of any one of claim 14, wherein the first subheader further comprises at least one of:a length indicator indicating a length of the first container; ora security information associated with the first container.The method of claim 1, wherein:the at least one container corresponds to a Radio Link Control (RLC) layer of the first network element and is passed as a Service Data Unit (SDU) to a Medium Access Layer (MAC) of the first network element;the at least one container corresponds to a Packet Data Convergence Protocol (PDCP) layer of the first network element and is passed as an RLC SDU to the RLC layer of the first network element; orthe at least one container corresponds to the MAC layer of the first network element.The method of any one of claims 3-4, further comprising:receiving, from a second network element, a security processing information carrying at least one of:an indication whether a security protection needs to be added for at least one of the first container; the second container; or the CDU; ora security processing configuration instructing a manner for adding the security protection.The method of claim 22, wherein the security processing configuration comprises at least one of:a security processing input parameter;key information; oralgorithm information.The method of claim 22, wherein the first container and the second container correspond to different layers or different entities.The method of claim 22, wherein the first container and the second container correspond to different layers in the first network element or different entities in the first network element.The method of any one of claims 1-25, wherein the predefined encoding scheme comprises at least one of: an Abstract Syntax Notation One (ASN. 1) scheme; or a Type-Length-Value (TLV) scheme.The method of any one of claims 1-25, wherein the first layer comprises at least one of:a Medium Access Control (MAC) layer; a Radio Link Control (RLC) layer; a Packet Data Convergence Protocol (PDCP) layer; or a PHY layer.The method of any one of claims 1-25, wherein the first network element comprises at least one of:a Distributes Unit (DU) of a base station; ora Central Unit (CU) of the base station.The method of any one of claims 5-26, wherein:the first network element comprises a DU of a base station, and the second network element comprises a CU of the base station; orthe first network element comprises the CU of a base station, and the second network element comprises the DU of the base station.A method for wireless communication, performed by a wireless device, the method comprising:receiving, by the wireless device or a first layer of the wireless device, from a network element, a message comprising a Compound Data Unit (CDU) , the CDU comprising at least one container, wherein each of the at least one container comprises data encoded using a predefined encoding scheme.The method of claim 30, wherein the at least one container comprises a first container; or a second container.The method of claim 31, wherein the first container corresponds to the first layer, and wherein the second container corresponds to a second layer different from the first layer.The method of claim 32, wherein the first container is originated from a peer layer corresponding to the first layer, and wherein the second layer is originated from a peer layer corresponding to the second layer.The method of any one of claims 32-33, further comprising:decoding the first container at the first layer; anddecoding the second container at the second layer.The method of any one of claims 32-33, further comprising:decoding, by one of: a predefined layer; a container processing module; or a container processing entity, the first container and the second container; anddispatching decoded first container and decoded second container to their respective layers.The method of claim 35, further comprising:forwarding the firsts container and the second container to one of: the predefined layer; the container processing module; or the container processing entity.The method of claim 35, wherein the predefined layer comprises at least one of: a Medium Access Control (MAC) layer; a Radio Link Control (RLC) layer; a Packet Data Convergence Protocol (PDCP) layer; or a PHY layer.The method of any one of claims 32-33, wherein at least one of following conditions is satisfied:the first container and the second container are individually security protected;the first container and the second container are jointly security protected; orthe CDU is security protected.The method of claim 38, further comprising performing security processing on at least one of following levels:an individual container level;a multiple containers level; ora CDU level.The method of claim 31, wherein each of the at least one container is carried in its dedicated sub Data Unit (subDU) in the CDU, and wherein the first container is carried in a first subDU in the CDU.The method of claim 31, wherein the first container and the second container are carried in a first subDU in the CDU.The method of any one of claim 40-41, wherein:the first subDU comprises a first subheader; andthe first subheader comprises a first indicator indicating a type of the first subDU among a list of subDU types, the list of subPDU types comprising at least one of: a control element type; a container type; or a padding type, or a Service Data Unit (SDU) type.The method of claim 42, wherein the first indicator comprises at least one of: a Logical Channel ID (LCID) ; or an Extended LCID.The method of claim 42, wherein the first container and the second container each corresponds to a different target among a list of targets, the list of targets comprising at least one of: a layer; a module; an entity; a domain; or a message type.The method of claim 44, wherein the first indicator further indicates a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.The method of claim 44, wherein the first subheader further comprises a second indicator indicating a target corresponding to the first container, and wherein the wireless device forwards the first container to its corresponding target for decoding.The method of claim 46, wherein the target comprises at least one of: a layer; a module; a function; an entity; a domain; or a message type.The method of any one of claim 42, wherein the first subheader further comprises at least one of:a length indicator indicating a length of the first container; ora security information associated with the first container.The method of any one of claims 30-48, wherein the predefined encoding scheme comprises at least one of: an Abstract Syntax Notation One (ASN. 1) scheme; or a Type-Length-Value (TLV) scheme.The method of any one of claims 30-48, wherein the first layer comprises at least one of:a Medium Access Control (MAC) layer; a Radio Link Control (RLC) layer; a Packet Data Convergence Protocol (PDCP) layer; or a PHY layer.The method of any one of claims 30-48, wherein the network element comprises a base station.A wireless device a network element for wireless communication comprising a memory for storing computer instructions and a processor in communication with the memory, wherein, when the processor executes the computer instructions, the processor is configured to implement a method in any one of claims 1-51.A computer program product comprising a non-transitory computer-readable program medium with computer code stored thereupon, the computer code, when executed by one or more processors, causing the one or more processors to implement a method of any one of claims 1-51.
