Dynamic management of a next-generation disaggregated nodes

Abstract

Methods and devices in a wireless communication network implement dynamic management of RAN units that form disaggregated RAN nodes to serve a user equipment. A wireless communication method (1000) performed by a first RAN unit (940A) includes establishing (1003) a first interface connection with a second RAN unit (940B). The first and the second RAN unit may be a centralized unit, a distributed unit or a radio unit. The method further includes receiving (1013), via the first interface connection, at least one of second RAN unit capability information or second RAN unit resource status of the second RAN unit. The first RAN unit and the second RAN unit may also exchange configuration information. This information exchange enables dynamically forming RAN nodes.

Description

Patent Application Attorney Docket Number 0683-123- WODYNAMIC MANAGEMENT OF A NEXT-GENERATION DISAGGREGATED NODESFIELD OF THE DISCLOSURE

[0001] This document generally describes methods and devices operating in wireless communication systems such as (but not limited to) similar to the ones described in Third Generation Partnership Project (3GPP) technical specifications (TSs). More specifically, this document describes methods and devices of a nextgeneration (i.e., after the fifth generation (5G)) wireless technology known as the sixth generation (6G) wireless technology.BACKGROUND

[0002] This background description is provided for the purpose of generally presenting the context of the disclosure. Work of the presently named inventors, to the extent it is described in this background section, as well as aspects of the description that may not otherwise qualify as prior art at the time of filing, are neither expressly nor impliedly admitted as prior art against the present disclosure.

[0003] The latest 3GPP TSs define features of a radio interface referred to as the 5G new radio (5G NR). A 5G NR wireless communication system includes a 5G core (5GC) network, a 5G radio access network (5G-RAN), a user equipment (5G UE), etc. The 5G NR systems provide increased data rates, decreased latency, and / or increased capacity compared to prior generations cellular communication systems (e.g., Long Term Evolution, (LTE)).

[0004] The International Telecommunication Union (ITU) has defined the framework for developing standards and radio interface technologies for 6G mobile systems. These networks rely on dependable computing resources and integrated artificial intelligence (Al) and / or machine learning (ML). The 6G infrastructure enables the rapid development and deployment of distributed applications and network functions. It also provides data and computing acceleration for services while ensuring end-to-end performance across the network.Patent Application Attorney Docket Number 0683-123- WO

[0005] The 5G-related 3GPP TSs 38.401 and 38.473 define a disaggregated RAN node with a centralized unit (CU) and distributed units (Dlls). However, a DU can connect only to one CU. Precluding a dynamic CU selection poses a significant limitation for data and computing acceleration desired in 6G. For example, if a DU initially connects a user equipment (UE) to a heavily loaded CU, the UE cannot benefit from a nearby, less loaded CU, thus not achieving the higher data rate and lower latency possible for the services the network provides to the UE.

[0006] The radio unit (RU) known as Open RU (O-RU) is defined in the Open Radio Access Network (O-RAN) Alliance specifications but currently there is no RU definition in the 3GPP TSs. As defined by O-RAN, the O-RU performs low physical (PHY) layer processing for NR protocols and manages uplink / downlink radio frequency signals. The O-RAN architecture incorporates Service Management and Orchestration (SMO), Non-Real Time RAN Intelligent Controller (RIC), and Near-Real Time RIC, which facilitate operations across the Open CU (O-CU), Open DU (O-DU), and O-RU. However, a critical gap in current O-RAN specifications is the absence of a defined control plane interface between the RU and the DU or CU.

[0007] Currently-known techniques support a CU connected to plural DUs and specialized control plane (CP) and user plane (UP) sub-units. Current techniques, however, do not support a DU connected to plural CUs, an RU connected to plural DUs or to a CU directly, or the real-time dynamic alternative-RAN-unit management.SUMMARY

[0008] The 6G wireless communication technology envisions dynamically selecting a CU, a DU, and an RU (called RAN units in this document) from plural connected CUs, DUs, and RUs. The selected CU, DU, and RU work together as a RAN node to serve a specific UE. In order to enable such a dynamic selection, CUs, DUs, and / or RUs exchange capability information and / or resource status information with other RAN units, whether of the same or different types, to which they are connected. This information exchange enables dynamic management of RAN units to form a disaggregated RAN node to optimize traffic, range, and quality of services (QoS) provided to UEs.Patent Application Attorney Docket Number 0683-123- WO

[0009] In some embodiments, after establishing an interface connection with a second RAN unit, a first RAN unit receives capability information and / or resource status of the second RAN unit. The first RAN unit may reciprocally provide its capability information and / or resource status to the second RAN unit. The resource status specifies a status (e.g., availability, occupancy, usage rate, and / or load) for each among one or more computing resources, radio resources, and / or AI / ML resources of the respective RAN unit. The RAN unit may periodically transmit an update of its resource status. Alternatively or additionally, the RAN unit may transmit an update of its resource status when triggered by the occurrence of a predetermined event.

[0010] When an RU receives a service request from a UE, it selects a DU from its connected DUs based on the respective DUs’ capabilities, configurations, and / or resource status. The RU may then choose a CU from its indirectly or directly connected CUs based on the CUs’ respective capabilities, configurations, and / or resource statuses.Alternatively, a DU (e.g., the RU-selected DU) connected to multiple CUs may select a CU based on the CUs’ respective capabilities, configurations, and / or resource statuses.Similarly, a CU connected to multiple DUs may select a DU based on the DUs’ respective capabilities, configurations, and resource statuses. A first DU connected to a second DU may generate configurations for UEs it serves by considering both DUs’ capabilities, configurations, and resource statuses.BRIEF DESCRIPTION OF THE DRAWINGS

[0011] The accompanying drawings, which are incorporated in and constitute a part of the specification, illustrate one or more embodiments and, together with the description, explain these embodiments.

[0012] Fig. 1 illustrates a wireless communication system configured to implement techniques according to various embodiments.

[0013] Fig. 2A illustrates a RAN with control plane and user plane specialized CUs.

[0014] Fig. 2B illustrates a RAN with control plane and user plane specialized DUs.

[0015] Fig. 2C illustrates another RAN with control plane and user plane CUs.Patent Application Attorney Docket Number 0683-123- WO

[0016] Fig. 2D illustrates a set of CUs, DUs, and RUs that are or can be connected for providing services to UEs.

[0017] Fig. 3 illustrates a protocol stack for a UE connected to an RU, a DU, and a CU.

[0018] Fig. 4 is a signal diagram illustrating resource management applied for a DU connected to two CUs.

[0019] Fig. 5 is a signal diagram illustrating resource management applied for two RUs connected to a DU.

[0020] Fig. 6 is a signal diagram illustrating resource management applied for an RU connected to a CU.

[0021] Fig. 7 is a signal diagram illustrating resource management applied for two connected DUs.

[0022] Figs. 8A and 8B are a signal diagram illustrating management of physical (PHY) layer and / or Layer 2 parameters for UE communications with a distributed RAN.

[0023] Fig. 9 is a signal diagram illustrating a DU selecting a CU based on capability information exchange and resource status for two CUs.

[0024] FIG. 10 is a flowchart of a DU method for exchanging capability information and resource status with a CU and an RU.

[0025] Fig. 11 is a flowchart of a DU method for generating one or more UE configurations based on DU and RU capabilities and resource status.

[0026] Figs. 12 and 13 are flowcharts of DU methods for exchanging capability information and resource status with a CU.

[0027] Fig. 14 is a flowchart of a DU method for generating UE configurations based on CU and RU capability information and resource status.

[0028] Fig 15 is a flowchart of a DU method for generating UE configurations based on DU capabilities and resource statuses of the DU and another DU connected to the DU.

[0029] Fig 16 is a flowchart of DU method for forwarding a configuration parameter received from an RU to a CU.

[0030] FIG. 17 is a flowchart of a CU method for transmitting configuration parameters received from an RU and a DU to a UE.

[0031] Figs. 18 and 19 are flowcharts of RU methods for reporting capabilities and resource statuses and transmitting a configuration parameter to a DU and to a CU, respectively.Patent Application Attorney Docket Number 0683-123- WO

[0032] Figs. 20 and 21 are flowcharts of DU methods for directing uplink (UL) protocol data unit (PDU) messages to a CU and one of two CUs, respectively, connected to the DU.

[0033] Figs. 22 and 23 are flowcharts of RU methods for directing physical uplink shared channel (PUSCH) transmissions to a DU and one of two DUs, respectively, connected to the RU.DETAILED DESCRIPTION

[0034] Methods and devices described in this section embody techniques related to RAN units (such as DUs, CUs, and RUs) that dynamically form RAN nodes for providing services to UEs. The embodiment descriptions in this section refer to the accompanying drawings. The same and similar reference numbers (e.g., with the same last couple of digits) in different figures identify the same or similar elements.

[0035] Fig. 1 illustrates a wireless communication system configured to implement techniques related to dynamic management of RAN units that form disaggregated RAN nodes for serving UEs according to various embodiments. The wireless communication system 100 includes a UE 102, a base station (BS) 104, a BS 106 and a core network (CN) 110. The CN 110 may be or include a 5G core (5GC) 111 and / or a 6G core (6GC) 121. Alternatively or additionally, the core 110 may be or include other core network devices associated with standardized or non-standardized communication technologies. The BS 104 includes plural RAN units (individual or combined RU(s), DU(s) and CU(s)). A combination of RAN units including an RU, a DU, and a CU, groups dynamically into a disaggregated RAN node for serving a UE within cell 103. Different UEs within the cell 103 may be served by different combinations of the BS 104’s RAN units. The RAN unit selection may be initiated by one of the RAN units in the combination (e.g., the RU upon receiving a service request from the UE) and may be updated as necessary seamlessly.

[0036] The BS 104 may support an NG interface for communicating with the 5GC 111, or a 6G BS-to-CN radio interface (e.g., N6G) for communicating with the 6GC 121 or the 5GC 111 (i.e. , an evolved 5GC). The BS 106 may be similar with BS 104. The BS 104 and 106 may support a BS-to-BS interface (e.g., Xn / X6G) to directly exchange messages with each other.Patent Application Attorney Docket Number 0683-123-WO

[0037] Among other components, the 5GC 111 typically includes an Access and Mobility Management (AMF) 112, a Session Management Function (SMF) 114, and a User Plane Function (UPF) 116 as defined in the 3GPP TSs. The AMF 112 is configured to manage authentication, registration, paging, and other related functions, the SMF 112 is configured to manage protocol data unit (PDU) sessions, and the UPF 116 is configured to transfer user-plane packets related to audio calls, video calls, Internet traffic, etc. The 5GC 111 typically includes other functions not shown in Fig. 1. The 6GC 121 includes a 6G AMF 122, 6G SMF 124, and a 6G UPF 126 which may be similar to (but enhanced versions of) the AMF 112, the SMF 114, and the UPF 116. The 5GC 111 may also include other functions not shown in Fig. 1.

[0038] As illustrated in Fig. 1, the BS 104 supports cell 103, and the BS 106 supports cell 107. The cells 103 and 107 can operate on the same carrier frequency or different carrier frequencies. The cells 103 and 107 partially overlap to enable service continuity when UE 102 is handed over. In general, a wireless communication system can include any suitable number of BSs supporting NR cells and / or 6G cells.

[0039] The BS 104 includes multiple RAN units (i.e., CU(s), DU(s), RU(s) and combinations thereof) that may be dynamically aggregated into a RAN node serving the UE 102 and other not shown UEs as later detailed. Each RAN unit is equipped with processing hardware. For example, the processing hardware 130 corresponds to a DU-RU combination and the processing hardware 131 corresponds to an RU. Each processing hardware includes one or more processors (e.g., central processing unit(s) and / or special-purpose processing units) and a non-transitory computer-readable memory (CRM) storing instructions that the one or more general-purpose processors execute. The processing hardware 130 includes a processor 132 to process data that the BS 104 transmits in the downlink (DL) direction (e.g., to the UE 102), or data that the BS 104 receives in the uplink (UL) direction (e.g., from the UE 102). The processing hardware 130 also includes a transceiver 134 (e.g., a receiver and a transmitter) configured to transmit the data in the DL direction and to receive data in the UL direction. The processing hardware 130 also includes a protocol controller 136 configured to manage configurations for operating protocols (later described). ThePatent Application Attorney Docket Number 0683-123-WOCRM (not shown) stores executable codes for the processor 132 to perform methods according to embodiments described in this section. The processing hardware 131 includes generally similar components. In particular, components 133, 135, and 137 of processing hardware 131 are similar to the components 132, 134, and 136, respectively of the processing hardware 130.

[0040] Fig. 2A illustrates a RAN node 204 with specialized control plane (CP) and user plane (UP) CUs. A RAN node with specialized CP and UP CUs has a fixed configuration conventionally but may be dynamically setup from RAN units in a BS (e.g., the BS 104). The RAN node 204 includes a CU 240 and a DU 243. The CU 240 is made of a CU-CP 241 configured to manage CP communications between the UE 102 and the CN 110 and a CU-UP 242 configured to manage UP communications between the UE 102 and the CN 110. The CU-CP 241 and the CU-UP 242 communicate via an E1 interface (e.g., as defined in 3GPP TSs). The DU 243 communicates with the CU-CP 241 and the CU-UP 242 via a respective F1 or W1 interface (e.g., as defined in the 3GPP TSs), that is, F1-C / W1-C and F1-U / W1-U, respectively.

[0041] Fig. 2B illustrates a RAN node 206 with specialized CP and UP DUs. A RAN node with specialized CP and UP DUs has a fixed configuration conventionally but may be dynamically setup from RAN units in a BS (e.g., the BS 104). The RAN node 206 includes a DU 244 and an RU 247. The DU 244 is made of a DU-CP 245 configured to manage CP communications between the UE 102 and the CN 110 and a DU-UP 246 configured to manage UP communications between the UE and the CN 110. The DU-CP 245 and the DU-UP 246 communicate via a D1 interface. The RU 247 communicates with DU-CP 245 and the DU-UP 246 via an interface (called H1 interface), that is, H1-C and H1-U, respectively. In some embodiments, the DU-CP 245 and the RU 247 may communicate information with each other via the H1-C. For example, the information includes UE-specific configuration parameters, non-UE-specific configuration parameters, cell-specific configuration parameters, DU-specific information, and / or RU-specific information as described for Fig. 5.

[0042] Fig. 2C illustrates another RAN node 208 with specialized control plane and user plane CUs. As above, a RAN node like this has a fixed configurationPatent Application Attorney Docket Number 0683-123-WOconventionally but may be dynamically setup from RAN units in a BS (e.g., BS 104). The RAN node 208 includes the CU 240 and the DU 243 as in Fig. 2A and the RU 247 as in Fig. 2B. The CU-CP 241 and the CU-UP 242 communicate via an E1 interface and the DU 243 communicates with the CU-CP 241 and the CU-UP 242 via a respective F1 or W1 interface. Here, the RU 247 communicates UP traffic with DU 243 via an H1 interface (H1-U) and communicates CP traffic with the CU-CP 241 via another H1 interface (H1-C). Alternatively, the RU 247 communicates UP traffic and CP traffic with the DU 243 via the H1 -U. In some embodiments, the CU-CP 241 and the RU 247 may communicate information with each other via the H1-C. For example, the information includes UE-specific configuration parameters, non-UE-specific configuration parameters, cell-specific configuration parameters, CU-specific information, and / or RU-specific information as described for Fig. 6.

[0043] Fig. 2D illustrates a set of RAN units (CUs, DUs, and RUs) that are or can be connected for providing services to UEs. These RAN units may be collocated or located in nearby BSs. The CU 240A connects to the CU 240B via an X6G interface. The DU 243A connects to the CU 240A and to CU 240B via respective F1 interfaces and may connect to DU 243B via a G1 interface (as suggested by the dashed line, the connection is possible although not currently active). The DU 243B connects to the CU 240B via an F1 interface and may connect to CU 240A via an F1 interface (as suggested by the dashed line). The F1 interface can be called a flexible or enhanced F1 interface that enables or supports multiple connections from a single DU to multiple CUs. The RU 247A connects to DU 243A via an H1 interface, and may connect to DU 243B via another H1 interface and to CU 240A via yet another H1 interface (H1-C) to exchange control plane information directly not via a DU. Similarly, the RU 247B connects to DU 243B via an H1 interface and may connect to DU 243A via another H1 interface and to CU 240B via yet another H1 interface (H1-C). Interfaces H1 and G1 are not yet defined in 3GPP TSs and may have different names than the ones used in this document, but they are interfaces between RAN units as illustrated in the figures (i.e. , H1 interfaces connect RUs to DUs or CUs, and G1 is an interface between DUs).

[0044] In some embodiments, the CU-CP(s), the CU-UP(s), and / or the DU(s) described above may be collocated or implemented in a cloud system.Patent Application Attorney Docket Number 0683-123-WO

[0045] Fig. 3 illustrates, in a simplified manner, a protocol stack 300 according to which the UE 102 can communicate with a 6G RAN node made by aggregating a CU 340, a DU 343, and an RU 347. The physical (PHY) layer functionality is split between a Low PHY sublayer 302-1 between the UE 102 and the RU 347, and a High PHY layer 302-2 between the UE 102 and the DU 343 via the RU 347. The PHY layer provides transport channels to a medium access control (MAC) layer 304, which in turn provides logical channels to a radio link control (RLC) layer 306, both MAC and RLC layers operating between the UE 102 and the DU 343 via RU 347. The RLC layer 306 in turn provides data transfer services to a Packet Data Convergence Protocol (PDCP) layer 308 between UE 102 and CU 340. The PDCP layer 308 may provide data transfer services to a Service Data Adaptation Protocol (SDAP) layer 310 and to a radio resource control (RRC) layer 312. Thus, the CU 340 (e.g., of BS 104 or 106) performs the control and upper layer operations (e.g., RRC 314, SDAP 312, PDCP 310), while the DU 343 performs the lower layer operations (e.g., RLC 306, MAC 304, and PHY 302-2). To support connection to a core network (e.g., 5GC or 6GC), PDCP 310 provides data radio bearers to SDAP 312 and signal radio bearers to RRC 314. These layers may be implemented according to 5G, 6G or another wireless communication technology.

[0046] Next, several example scenarios in which a disaggregated RAN node made of RAN units of a BS operating in a wireless communication system (e.g., the system 100 illustrated in Fig. 1) transmits a configuration to a UE (e.g., 102 in Fig. 1) and later activates the configuration to enable communication between the UE and the core network (e.g., 121 ). Items in Figs. 4-23 that are similar are labeled with similar reference numbers (e.g., procedures 403A and 403B of Fig. 4, 403 in Fig. 6, etc.), with differences discussed where appropriate. With the exception of the differences shown in the figures and discussed below, any of the alternative implementations discussed with respect to a particular event (e.g., an action or signal / message) may apply to events labeled with similar reference numbers in other figures. The time flows from the top to the bottom of each figure, events illustrated higher occurring earlier than the ones illustrated lower in a figure.Patent Application Attorney Docket Number 0683-123- WO

[0047] Referring to Fig. 4, in a scenario 400, the DU 443 and the CU 440A initially perform an F1 interface setup procedure 403A to set up an F1 interface. The DU 443, the CU 440A, and the CU 440B (which may be collocated or located in nearby BSs) use respective processing hardware such as the processing hardware 130 and 131 illustrated in Fig. 1. The DU 443 first transmits 402 an F1 Setup Request message to the CU 440A. In response to the F1 Setup Request message, the CU 440A transmits 404 an F1 Setup Response message to the DU 443. The DU 443 may include a DU identifier (ID) in the F1 Setup Request message. This DU ID uniquely identifies the DU 443. Alternatively or additionally, the DU 443 may include a first protocol version in the F1 Setup Request message, the first protocol version indicating a version of a first protocol (e.g., an RRC protocol). The CU 440A may include a second protocol version in the F1 Setup Response message, the second protocol version indicating a version of the first protocol. The first protocol version may be a newer version, the same version, or an older version than the second protocol version. In some embodiments, when the second protocol version is a newer version than the first protocol version, the CU 440A uses a version of the first protocol equal to or older than the first protocol version to communicate with the DU 443. In some embodiments, when the first protocol version is a newer version than the second protocol version, the DU 443 uses a version of the first protocol equal to or older than the second protocol version to communicate with the CU 440A. The DU 443 may also include a third protocol version in the F1 Setup Request message, the third protocol version indicating a version of a second protocol (e.g., an interface application protocol such as an F1 application protocol). The CU 440A may include a fourth protocol version in the F1 Setup Response message, the fourth protocol version indicating a version of the second protocol. The third protocol version may be a newer version, the same version, or an older version than the fourth protocol version. If the fourth protocol version is a newer version than the third protocol version, the CU 440A may use a version of the second protocol equal to or older than the third protocol version to communicate with the DU 443. If the third protocol version is a newer version than the fourth protocol version, the DU 443 may use a version of the second protocol equal to or older than the fourth protocol version to communicate with the CU 440A.Patent Application Attorney Docket Number 0683-123-WO

[0048] After completing the F1 interface setup procedure 403A, the DU 443 is connected to the CU 440A via the F1 interface. The DU 443 may then transmit 406 DU capabilities 1 , , N (with N a positive integer) to the CU 440A in a first DU-to-CU message. Note that when a signal (i.e. , a message transmitted from one RAN unit to another) is represented using a dashed line (e.g., the line labeled 406), the signal is optional, that is, it occurs in some embodiments and not in others. The first DU-to-CU message may be a dedicated DU capability information message. The DU 443 may proactively transmit the first DU-to-CU message to the CU 440A or may transmit the first DU-to-CU message in response to receiving a CU-to-DU message (e.g., a request for capability information or a message reporting CU’s capabilities) from the CU 440A. Alternatively, the DU 443 may transmit the DU capabilities concurrently with transmitting 402 the F1 Setup Request message (i.e., the F1 Setup Request message may include the DU capabilities 1, ..., N).

[0049] The DU capabilities 1 , ... , N include one or more 6G-related capability / capabilities (e.g., features and / or functions), AI / ML-related capability / capabilities for one or more corresponding AI / ML functionalities,sensing-related capability / capabilities for one or more corresponding sensing functionalities, Transmission-Reception Point (TRP) related capability / capabilities for one or more TRP-related functionalities, multiple input multiple output (MIMO) related capability / capabilities for one or more MIMO functionalities, radio frequency or spectrum related capability / capabilities (e.g., including a maximum DL bandwidth and / or a maximum UL bandwidth), coverage-related capability / capabilities, positioning-related capability / capabilities, connection-related capability / capabilities, and / or communication protocol-related capability / capabilities for operation of protocol(s). In some embodiments, the positioning-related capability / capabilities indicate which positioning methods are supported and / or which reference signal(s) for positioning are supported. The protocol(s) may include a physical sub-layer (e.g., PHY 302-2), an MAC layer (e.g., MAC 304), and / or an RLC layer (e.g., RLC 306). The connection-related capability / capabilities include radio bearer-related capability / capabilities, latency-related capability / capabilities, and / or quality of service-related capability / capabilities. The DUPatent Application Attorney Docket Number 0683-123-WOcapabilities 1 , , N may include computing-related capabilities and / or transport layer-related capabilities. The computing-related capabilities may include a Tera Operations Per Second (TOPS) value or indication, a Million instructions per second (MIPS) value or indication, a memory speed, and / or a memory size. The transport layer-related capability / capabilities may indicate support of protocol(s) for communication between the CU and the DU. For example, the protocol(s) may include a transport layer protocol(s) and / or a security protocol(s). The transport layer protocol(s) may include a Transmission Control Protocol (TCP), a User Datagram Protocol (UDP), a Datagram Congestion Control Protocol (DCCP), a Stream Control Transmission Protocol (SCTP), a Quick UDP Internet Connections (QUIC) protocol, and / or a multipath QUIC protocol. The security protocol(s) may include a Transport Layer Security (TLS) protocol and / or an Internet Security Protocol (IPSec). The transport layer-related capability / capabilities may indicate version(s) of the protocol(s). One of the DU capabilities may indicate the first protocol version and another of the DU capabilities may indicate the third protocol version.

[0050] The CU 440A may transmit 408 CU capabilities 1, ..., M to the DU 443, in a second CU-to-DU message (with M being a positive integer). The second CU-to-DU message may be a dedicated CU capability information message. The CU 440A may proactively transmit the second CU-to-DU message to the DU 443, may transmit the second CU-to-DU message in response to receiving the first DU-to-CU message or in response to a CU capability inquiry message from the DU 443. The message 408 may be combined with message 404 and / or with the F1 Setup Response message.

[0051] The CU capabilities 1, ..., M include one or more 6G-related functionalities (e.g., features and / or functions), AI / ML-related capability / capabilities for one or more corresponding AI / ML functionalities, sensing-related capability / capabilities for one or more corresponding sensing functionalities, connection-related capability / capabilities, and / or communication protocol-related capabilities for operation of protocols. In some implementations, the protocol(s) include PDCP layer and / or SDAP layer. The connection-related capability / capabilities include radio bearer-related capability / capabilities, latency-related capability / capabilities, and / or quality ofPatent Application Attorney Docket Number 0683-123-WOservice-related capability / capabilities. The CU capabilities 1, M may include computing-related capabilities and / or transport layer-related capabilities. In some implementations, the computing-related capabilities include a TOPS value or indication, a MIPS value or indication, a memory speed, and / or a memory size. The transport layer-related capabilities may indicate supported protocols for user plane connection(s) between the CU and the DU. For example, the protocols may include transport layer protocol(s) and / or security protocol(s). The transport layer protocol(s) may include TCP, UDP, DCCP, SCTP, QUIC protocol, and / or multipath QUIC protocol. The security protocol(s) may include TLS protocol and / or IPSec. One of the CU capabilities may indicate the second protocol version and one of the DU capabilities may indicate the fourth protocol version.

[0052] The capabilities information exchange 407A is optional (as suggested by the dashed line box surrounding 406 and 408). However, at least one of the procedures 407A, 411 A, 414A, and 416A is performed during the information exchange procedure 411A following the set up procedure 403A. Note that the procedures 407A, 411 A, 414A, and 416A may be performed in a different order than the order illustrated in Fig.4. The CU 440A (and / or the CU 440B) may include CP and UP dedicated RAN subunits as illustrated in Fig. 2A and 2C, the DU 443 may include CP and UP dedicated RAN sub-units as illustrated in Fig. 2B.

[0053] The DU 443 may then transmit 410 DU configuration information to the CU 440A using a third DU-to-CU message. The third DU-to-CU message may be a dedicated DU Configuration Update message. The DU 443 may receive a third CU-to-DU message from the CU 440A, in response to the third DU-to-CU message. The third CU-to-DU message may be a DU Configuration Update Acknowledgement. The message 410, which may be combined with the F1 Setup Request message 403 or with the message 406, includes the DU configuration information.

[0054] The DU configuration information may include cell information, cell status, system information, a Public Land Mobile Network (PLMN) list, a Standalone NonPublic Network (SNPN) ID list, cell configuration, application level configuration data, Time Division Duplex (TDD) UL-DL configuration, Bandwidth Part (BWP) configuration,Patent Application Attorney Docket Number 0683-123-WOsub-band full duplex (SBFD) configuration, waveform configuration, synchronization signal configuration, SSB configuration, reference signal configuration, and / or MIMO related configuration. The cell information may include cell information 1, ..., P for cell(s) 1, ..., P (with P is a positive integer). For example, each of the cell information 1, ..., P includes a cell global identity (CGI), a physical cell identity (PCI), a tracking area code, an RAN area code, served PLMN identity / identities, non-public network information, slice information, UL frequency information, DL frequency information, UL transmission bandwidth, DL transmission bandwidth, measurement timing configuration, a DU identity / identifier, information of synchronization signal and / or physical broadcast channel (SSB) positions in burst, barring configuration, device-type related information, TDD UL-DU configuration, SBFD configuration, and / or emergency call information. The DU configuration information may include Transport Network Layer (TNL) association information and / or transport layer address information. The device-type related information may include Internet of Thing (loT) related information, reduced capability (RedCap) related information, enhanced RedCap (eRedCap) related information, and / or extended Reality (XR) related information. The loT related information may include loT broadcast information and / or loT UE support information indicating support of loT UEs and / or which type(s) of loT UEs. The RedCap related information may include RedCap broadcast information and / or RedCap UE support information indicating support of RedCap UEs. The eRedCap related information may include eRedCap broadcast information and / or eRedCap UE support information indicating support of eRedCap UEs. The XR related information may include XR broadcast information and / or eRedCap UE support information indicating support of XR UEs and / or which type(s) of XR UE(s). The DU 443 may broadcast a portion of the cell information 1 on the cell 1 , ..., a portion of the cell information P on the cell P, respectively. The cell status may indicate a status (e.g., in-service or out-of-service) of the cell(s) 1, ..., P. The system information may include one or more system information blocks (SIBs) broadcast on each of the cell(s) 1 , ... , P.

[0055] The CU 440A may then respond by transmitting 412 CU configuration information to the DU 443 in a fourth CU-to-DU message. The fourth CU-to-DUPatent Application Attorney Docket Number 0683-123-WOmessage may be a dedicated CU Configuration Update message. In response to the fourth CU-to-DU message, the DU 443 may transmit a fourth DU-to-CU message to the CU 440A, for example, a CU Configuration Update Acknowledgement. The message transmitted at 412, which may be combined with the message transmitted at 408 and / or the F1 Setup Response transmitted at 404, includes the CU configuration information.

[0056] The CU configuration information includes cell information, SSB information, application level configuration data, system information, a PLMN list, and / or a SNPN ID list. The CU configuration information includes TNL association information and / or transport layer address information. The cell information may include a cells-to-be-activated list, a cells-to-be-deactivated list, and / or acells-allowed-to-be-deactivated list. The DU 443 may activate cell(s) indicated in the cells-to-be-activated list and / or deactivate cell(s) indicated in the cells-to-be-deactivated list and / or the cells allowed to be deactivated list. The SSB information may indicate SSB(s) to be activated on cell(s) indicated in the cells-to-be-activated list. In response to or in accordance with the SSB information, the DU 443 may activate transmission of the SSB(s) on the cell(s) indicated in the cells-to-be-activated list. The system information may include one or more system information blocks (SIBs) to be broadcast on one or more cells, which the DU 443 then broadcasts these one or more SIBs. The system information may include a list of UEs that are unable to receive system information from broadcast, and the DU 443 may transmit at least one SIB to the UEs via dedicated signaling. Generally, the DU 443 applies configuration(s) and / or information received in the CU configuration information. Events 410 and 412 form a DU / CU configuration information procedure(s) 411 A. The CU configuration information may include configuration parameters configuring operation of the DU 443.

[0057] The DU 443 may then transmit 414A DU resource status 1 , ... , L (with L a positive integer) to the CU 440A. The DU 443 may transmit 414A the DU resource status periodically with a fixed transmission periodicity (i.e., at equal time intervals). The DU 443 may receive the periodicity from the CU 440A or an Operation, Administration, and Maintenance (0AM) node, or the periodicity is predetermined or preconfigured. Alternatively or additionally, the DU 443 may transmit the DU resource status when anPatent Application Attorney Docket Number 0683-123- WOevent occurs. The DU 443 may receive a configuration of the event from the CU 440A or the OAM node, or the event is predetermined or preconfigured. The event may be a change in DU resource status above a threshold. The configuration of the event may configure the threshold, or the threshold is predetermined or preconfigured. For example, the DU 443 may transmit DU resource status X to update DU resource status X-1 (X being an integer and 1 < X < L) when a change in the DU resource status X above the threshold has occurred (e.g., since previously reporting resource status). The DU 443 may transmit, to the CU 440A, L DU-to-CU messages (e.g., DU resource status update messages 1, ..., L) including the DU resource status 1, ..., L, respectively. The DU resource status 1, .... L indicate status (e.g., availability, occupancy, usage rate, load, etc.) of DU resources of the DU 443. The DU resources may include computing resources and / or radio resources. The computing resources may include AI / ML resources memory (e.g., random access memory), storage, neural processing units, graphic processing units, tensor processing units, and / or CPUs. The computing resources may be quantified based on a storage size, a memory size, and / or the number(s) of neural processing units, graphic processing units, tensor processing units, and / or CPUs. The AI / ML resources may include neural processing units, graphic processing units, and / or tensor processing units. The radio resources may include DL bandwidth, UL bandwidth, DL physical resource blocks, UL physical resource blocks, DL slots, UL slots, Hybrid Automatic Repeat reQuest (HARQ) processes, beams, synchronization signals, and / or reference signals.

[0058] The CU 440A may then determine whether to configure, reconfigure, release, enable, disable, activate, or deactivate a functionality for a UE based on CU resource status, at least a portion of the DU resources 1, ..., L, and / or the most-recently received DU resource status. The CU 440A may determine whether to configure, reconfigure, release, enable, disable, activate, or deactivate a functionality (e.g., AI / ML or career aggregation (CA) functionality) for a UE (e.g., the UE 102), based on the status of computing resources, AI / ML resources, and / or radio resources at the DU 443. In this scenario 400, the CU 440A determines that the DU 443 has sufficient resources (e.g., computing resources, AI / ML resources and / or radio resources) for the AI / MLPatent Application Attorney Docket Number 0683-123- WOand / or CA functionality for the UE, and, therefore, the CU 440A configures, enables, or activates the respective functionality for the UE. In a different scenario, the CU 440A determines that the DU 443 does not have sufficient resources (e.g., computing resources, AI / ML resources and / or radio resources) for the AI / ML or CA functionality for the UE, and, therefore, the CU 440A does not configure, enable, or activate the AI / ML or CA functionality for the UE. In a different scenario, the CU 440A determines that the DU 443 does not have sufficient resources (e.g., computing resources, AI / ML resources and / or radio resources) for the AI / ML or CA functionality for the UE, and, therefore, the CU 440A reconfigures, releases, disables, or deactivates the AI / ML or CA functionality for the UE. The CU 440A may transmit the DU resource status 1, ... , L to a data collection node or an Operation, Administration, and Maintenance (OAM) node. The data collection node or the OAM may then generate a DU resources usage report or dashboard for the DU 443 based on the DU resource status 1 , ... , L. Alternatively or additionally, the CU 440A stores the DU resource status 1 , ... , L and generates a DU resources usage report or dashboard based on the stored DU resource status 1, ..., L. Based on the usage report or dashboard, an operator may determine whether to upgrade the DU 443 to increase DU’s capability and / or capacity.

[0059] The CU 440A may then transmit 416A CU resource status 1 , ... , K (with K a positive integer) to the DU 443. The CU 440A may transmit the CU resource status periodically with a fixed transmission periodicity (i.e., with equal time intervals). The CU 440A may receive the periodicity from the DU 443 or OAM node, or the periodicity is predetermined or preconfigured. Alternatively or additionally, the CU 440A may transmit the CU resource status when a event occurs. The CU 440A may receive a configuration of the event from the DU 440A or OAM node, the event is predetermined or preconfigured. The event may be a change in CU resource status above a threshold. The configuration of the event may configure the threshold, or the threshold is predetermined or preconfigured. For example, the CU 440A may transmit CU resource status Y to update CU resource status Y-1 (Y being an integer and 1 < Y < K) because a change above the threshold has occurred (e.g., since previously reporting the resource status) in the status of the CU resource status Y-1. The CU 440A mayPatent Application Attorney Docket Number 0683-123- WOtransmit, to the DU 443, K CU-to-DU messages (e.g., CU resource status update messages) including the CU resource status 1, ..., K, respectively. The CU resource status 1, ..., K indicate status (e.g., availability, occupancy, usage rate, load, etc.) of CU resources at the CU 440A. The CU resources may include computing resources. The computing resources may include AI / ML resources, memory (e.g., random access memory), storage, neural processing units, graphic processing units, tensor processing units, and / or CPUs. The computing resources may be quantified based on a storage size, a memory size, and / or the number(s) of neural processing units, graphic processing units, tensor processing units, and / or CPUs. The AI / ML resources may include neural processing units, graphic processing units, and / or tensor processing units.

[0060] The DU 443 is enabled to determine whether to configure, reconfigure, release, enable, disable, activate, or deactivate a functionality for a UE based on DU resource status, at least a portion of the CU resource status 1 , ... , K, and / or the most-recently received CU resource status. The DU 443 may obtain status of the computing resources (or the AI / ML resources) at the CU 440A from at least a portion of the CU resource status 1 , ... , K, and / or the most-recently received CU resource status. The DU 443 then determines whether to configure, enable, or activate a functionality (e.g., an AI / ML functionality) for a UE (e.g., the UE 102), based on status of the computing resources (or AI / ML resources) at the CU 440A. When the DU 443 determines that the CU 440A has sufficient computing (e.g., AI / ML resources) to provide the functionality for the UE, the DU 443 configures, enables, or activates the functionality for the UE.Otherwise, when the DU 443 determines that the CU 440A does not have sufficient computing resources (or AI / ML resources) for the functionality for the UE, the DU 443 does not configure, enable, or activate the functionality for the UE or reconfigures, releases, disables, or deactivates the functionality for the UE. The CU 440A may transmit the CU resource status 1 , ... , K to a data collection node or an 0AM node. The data collection node or the 0AM generates a CU resources usage report or dashboard for the CU 440A based on the CU resource status 1, ... , K. Alternatively or additionally, the CU 440A stores the CU resource status 1 , ... , K and generates a CU resourcesPatent Application Attorney Docket Number 0683-123- WOusage report or dashboard based on the CU resource status 1 , , K. Based on the usage report or dashboard, an operator may determine whether to upgrade the CU 440A to increase capability and / or capacity.

[0061] The DU 443 may transmit one or more additional DU configuration information to the CU 440A to update the DU configuration information. Alternatively or additionally, the CU 440A may transmit one or more additional CU configuration information to the DU 443 to update the CU configuration information.

[0062] The DU 443 then performs 403B an F1 Setup procedure (as described above relative to the CU 440A) with a CU 440B. The DU 443 and the CU 440B may then perform 407B a DU / CU capability information exchange procedure, 411B a DU / CU configuration information exchange procedure, 414B resource status update procedure(s), and / or 416B CU to DU resource status update procedure(s). The procedures 407B, 411B, 414B, 416B, and 413B are similar to the procedures 407A, 411A, 414A, 416A, and 413A, respectively, so the descriptions above apply and are not repeated. The capability information, configuration and / or resource status exchange enables the CU 440A, DU 443, and CU 440B to select or be selected as part of a dynamically formed RAN node serving a specific UE.

[0063] The DU 443 may employ one or more RUs. Fig. 5 illustrates a scenario 500 with a DU 543 connected to more than one RU. In this scenario, an RU 547A and a DU 543 initially perform a connection setup procedure 519A to set up one or more H1 interfaces (or connections). The DU 543 may be the same or similar with the DU 443 and may be made of CP and UP dedicated RAN sub-units as illustrated in Fig. 2B. The one or more H1 interfaces may include H1-C and H1-U as illustrated in Fig. 2B. The DU 547, the RU 547A, and the RU 547B use respective processing hardware such as the processing hardware 130 and 131 illustrated in Fig. 1. The RU 547A transmits 518 a H1 Setup Request message to the DU 543. In response to the H1 Setup Request message, the DU 543 transmits 520 a H1 Setup Response message to the RU 547A. The RU 547A may include an RU ID in the H1 Setup Request message. The RU ID uniquely identifies the RU 547A. The DU 543 may include a DU ID in the H1 Setup Response message. The DU ID uniquely identifies the DU 543. The RU 547A mayPatent Application Attorney Docket Number 0683-123- WOinclude a first protocol version in the H1 Setup Request message, the first protocol version indicating a version of a first protocol (e.g., an RRC protocol). The DU 543 includes a second protocol version in the H1 Setup Response message, indicating a version of the first protocol. The first protocol version may be a newer version, the same version, or an older version than the second protocol version. In some embodiments, when the second protocol version is a newer version than the first protocol version, the DU 543 uses a version of the first protocol equal to or older than the first protocol version to communicate with the RU 547A. In some embodiments, when the first protocol version is a newer version than the second protocol version, the RU 547A uses a version of the first protocol equal to or older than the second protocol version to communicate with the DU 543. The RU 547A may include a third protocol version in the H1 Setup Request message, the third protocol version indicating a version of a second protocol (e.g., an interface application protocol such as an H1 application protocol). The DU 543 may include a fourth protocol version in the H1 Setup Response message, the fourth protocol version indicating a version of the second protocol. The third protocol version may be a newer version, the same version, or an older version than the fourth protocol version. In some embodiments, when the fourth protocol version is a newer version than the third protocol version, the DU 543 uses a version of the second protocol equal to or older than the third protocol version to communicate with the RU 547A. In some embodiments, when the third protocol version is a newer version than the fourth protocol version, the RU 547A may use a version of the second protocol equal to or older than the fourth protocol version to communicate with the DU 543.

[0064] After completing the H1 setup interface procedure 519A, the DU 543 and the RU 547A perform procedure 525A that includes at least one of a capability information exchange procedure 523A (including steps 522 and 524), a configuration information exchange procedure 527A (including steps 526 and 528), an RU resource status transmission 530A and a DU resource status transmission 532A. The order of procedures 523A, 527A, 530A, and 532A is exemplary, not intended to be limiting.

[0065] Within the capability information exchange procedure 523A, the RU 547A transmits 522 RU capabilities 1, ..., P (P being a positive integer) to the DU 543 using aPatent Application Attorney Docket Number 0683-123-WOfirst RU-to-DU message. The first RU-to-DU message may be a dedicated RU capability information message. The RU 547 A may proactively transmit the first RU-to-DU message to the DU 543 or may transmit the first RU-to-DU message in response to receiving a DU-to-RU message (e.g., a request for capability information or a message reporting RU’s capabilities) from the DU 543. Alternatively, the RU 547A may transmit the RU capabilities concurrently with transmitting the H1 Setup Request message.

[0066] The RU capabilities 1, ..., P include one or more corresponding 6G-related capability / capabilities (e.g., features and / or functions), AI / ML-related capability / capabilities for one or more corresponding AI / ML functionalities,sensing-related capability / capabilities for one or more corresponding sensing functionalities, TRP related capability / capabilities for one or more TRP-related functionalities, MIMO-related capability / capabilities for one or more MIMO functionalities, radio frequency or spectrum related capability / capabilities (e.g., including maximum DL bandwidth and / or maximum UL bandwidth), coverage-related capability / capabilities, positioning-related capability / capabilities, and / or communication protocol related capabilities for operation of protocol(s). In some embodiments, the positioning-related capability / capabilities indicate which positioning methods are supported and / or which reference signal(s) for positioning are supported. The protocol(s) may include a physical sub-layer (e.g., PHY 302-1). The RU capabilities 1, ..., P may include computing-related capability / capabilities and / or transport layer-related capability / capabilities. The computing related capability / capabilities may include a TOPS value or indication, a MIPS value or indication, a memory speed, and / or a memory size. The transport layer-related capability / capabilities may indicate support of protocol(s) for communication between the RU 547A and the DU 543. The protocol(s) may include Ethernet protocol, Internet Protocol (IP) v4, and / or IP v6. One of the RU capabilities may indicate the first protocol version and another of the RU capabilities may indicate the third protocol version.

[0067] Further within the capability information exchange procedure 523A, the DU 543 may transmit 524 DU capabilities 1, ..., N (N being a positive integer which may be the same as in Fig. 4) to the RU 547A using a second DU-to-RU message. ThePatent Application Attorney Docket Number 0683-123-WOsecond DU-to-RU message may be a dedicated DU capability information message. The DU 543 may proactively transmit the second DU-to-RU message to the RU 547A or may transmit the second DU-to-RU message in response to receiving a second RU-to-DU message (e.g., a request for DU capability information) from the RU 547A. In some embodiments, The DU 543 includes the capabilities information in the H1 Setup Response message.

[0068] The DU capabilities may include one or more corresponding 6G-related capability / capabilities (e.g., features and / or functions), AI / ML-related capability / capabilities for one or more corresponding AI / ML functionalities,sensing-related capability / capabilities for one or more corresponding sensing functionalities, TRP-related capability / capabilities for one or more TRP-related functionalities, MIMO-related capability / capabilities for one or more MIMO functionalities, coverage-related capability / capabilities, positioning-related capability / capabilities, and / or communication protocol-related capabilities for operation of protocol(s). The protocol(s) may include physical sub-layer (e.g., PHY 302-2). In some embodiments, the positioning-related capability / capabilities indicate which positioning methods are supported and / or which reference signal(s) for positioning are supported. The DU capabilities may include computing-related capabilities and / or transport layer-related capabilities. The computing-related capabilities may include a TOPS value or indication, a MIPS value or indication, a memory speed, and / or a memory size. The transport layer-related capabilities may indicate supported protocols for one or more user plane connections between the RU and the DU. For example, the protocols include Ethernet protocol, Internet Protocol (IP) v4, and / or IP v6. One of the DU capabilities may indicate the second protocol version and another of the DU capabilities may indicate the fourth protocol version.

[0069] Within the configuration information exchange procedure 527A, the RU 547A may transmit 526 RU configuration information to the DU 543 using a third RU-to-DU message. The third RU-to-DU message may be a dedicated RU Configuration Update message. The RU 547A may receive a third DU-to-RU message (e.g., DU Configuration Update Acknowledgement) a from the DU 543, in response to the thirdPatent Application Attorney Docket Number 0683-123-WORU-to-DU. The third RU-to-DU message may be combined with the second RU-to-DU message (i.e. , the second RU-to-DU message includes also the RU configuration information). In some embodiments, the RU 547A includes the configuration information in the H1 Setup Request message.

[0070] The RU configuration information may include UL frequency information, DL frequency information, UL transmission bandwidth information, DL transmission bandwidth information, a RU identity / identifier, antenna configuration information, beam configuration information, subcarrier spacing configuration information, MIMO-related configuration information, slot configuration information, waveform configuration information, synchronization signal configuration information, reference signal configuration information, SSB configuration information, bandwidth part (BWP) configuration information, TDD UL-DL configuration information, SBFD configuration information, and / or TRP configuration information. The RU configuration information may include Ethernet information and / or IP address information. The RU configuration may include cell information for one or more cells as described above.

[0071] Further within the configuration information exchange procedure 527A, the DU 543 then transmits 528 DU configuration information to the RU 547A using a fourth DU-to-RU message. The fourth DU-to-RU message may be a dedicated DU Configuration Update message. The RU 547A may transmit the fourth RU-to-DU message to the DU 543 in response to the fourth DU-to-RU message. The fourth RU-to-DU message may be a DU Configuration Update Acknowledgement. In some alternative embodiments, the DU may include the DU configuration information in the second DU-to-RU message or in the H1 Setup Response message. Details and examples for the DU configuration information set forth when describing Fig. 4 can apply to the DU configuration information transmitted by the DU 543 to RU 547A and are not repeated. The DU configuration information may include Ethernet information and / or IP address information.

[0072] The RU 547A typically applies configuration(s) and / or information in the DU configuration information. The DU configuration information may include a configuration and / or information to replace a configuration and / or information included inPatent Application Attorney Docket Number 0683-123- WOthe RU configuration information. For example, if the DU configuration information includes a MIMIO-related configuration, the RU 547A applies the received MIMO-related configuration.

[0073] The RU 547A may transmit 530A RU resource status 1 , ... , Q (Q being a positive integer) to the DU 543. The RU 547A may transmit the RU resource status periodically with a fixed transmission periodicity (i.e., at equal time intervals). The RU 547A may receive the periodicity from the DU 543, a CU or an 0AM node, or the periodicity is predetermined or preconfigured. Alternatively or additionally, the RU 547A may transmit the RU resource status when an event occurs. The RU 547A may receive a configuration of the event from the DU 543, the CU or the 0AM node, or the event is predetermined or preconfigured. The event may be a change in RU resource status above a threshold. The configuration of the event may configure the threshold, or the threshold is predetermined or preconfigured. For example, the RU 547A may transmit the RU resource status X to update RU resource status X-1 , (X being an integer and 1 < X < L) when a change in the DU resource status X above the threshold has occurred (e.g., since previously reporting resource status). The RU 547A may transmit, to the DU 543, RU-to-DU messages (e.g., RU resource status update messages) 1, ..., Q including the RU resource status 1, ..., Q, respectively. The RU resource status 1, ..., Q indicate status (e.g., availability, occupancy, usage rate, load, etc.) of respective RU resources of the RU 547A. The RU resources may include computing resources and / or radio resources. The computing resources may include AI / ML resources, memory (e.g., random access memory), storage, neural processing units, graphic processing units, tensor processing units, and / or CPUs. The computing resources may be quantified based on a storage size, a memory size, and / or the number(s) of neural processing units, graphic processing units, tensor processing units, and / or CPUs. The AI / ML resources may include neural processing units, graphic processing units, and / or tensor processing units. The radio resources may include a DL bandwidth, a UL bandwidth, DL physical resource blocks, UL physical resource blocks, DL slots, UL slots, Hybrid Automatic Repeat reQuest (HARQ) processes, beams, synchronization signals, and / or reference signals.Patent Application Attorney Docket Number 0683-123- WO

[0074] The DU 543 determines whether to configure, reconfigure, release, enable, disable, activate, or deactivate a functionality for a UE based on DU resource status, at least a portion of the RU resource status 1 , ... , Q, and / or the latest received RU resource status (e.g., the RU resource status Q). The DU 543 may determine the DU resource status as described above relative to Fig. 4 or as described below. In some implementations, the DU 543 obtains status of the computing resources (or the AI / ML resources) at the RU 547A from at least a portion of the RU resource status 1 , ... , Q, and / or the latest-received RU resource status (e.g., the RU resource status Q). The DU 547 determines whether to configure, reconfigures, release, enable, disable, activate, or deactivate a functionality for a UE (e.g., the UE 102), based on the status of computing resources, AI / ML resources, and / or radio resources at the RU 547A. For example, the functionality is an AI / ML functionality, a MIMO functionality, or a CA functionality. If the DU 543 determines that the RU 547A has sufficient resources (e.g., computing resources, AI / ML resources and / or radio resources) for the functionality for the UE, the DU 543 configures, enables, or activates the functionality for the UE.Otherwise, if the DU 543 determines that the RU 547A does not have sufficient resources (e.g., computing resources, AI / ML resources and / or radio resources) for the functionality for the UE, the DU 543 does not configure, enable, or activate or reconfigures, releases, disables, or deactivates the functionality for the UE. The DU 543 may transmit the RU resource status 1 , ... , Q to a data collection node or an 0AM node. The data collection node or the 0AM generates a RU resources usage report or dashboard for the RU 547A based on the RU resource status 1, ..., Q. Alternatively or additionally, the DU 543 stores the RU resource status 1, ..., Q and generates a RU resources usage report or dashboard based on the stored RU resource status 1, ..., Q. Based on the usage report or dashboard, an operator may determine whether to upgrade the RU 547A to increase its capability and / or capacity.

[0075] Further, the DU 543 may transmit 532A DU resource status 1, ..., L (L being a positive integer which may be the same as in Fig. 4) to the RU 547A. The DU 543 may transmit the DU resource status periodically with a fixed transmission periodicity (i.e., at equal time intervals). The DU 543 may receive the periodicity fromPatent Application Attorney Docket Number 0683-123- WOthe RU 547A, CU, or OAM node, or the periodicity is predetermined or preconfigured. Alternatively or additionally, the DU 543 transmits the DU resource status when an event occurs. The DU 543 may receive a configuration of the event from the RU 547A, CU, or OAM node, or the event is predetermined or preconfigured. The event may be a change in DU resource status above a threshold. The configuration of the event may configure the threshold, or the threshold is predetermined or preconfigured. For example, the DU 543 transmits DU resource status Y to update DU resource status Y-1 (where Y being an integer and 1 < Y < L) when a change in the DU resource status Y above the threshold has occurred (e.g., since previously reporting resource status). The DU 543 may transmit, to the RU 547A, DU-to-RU messages (e.g., DU resource status update messages) 1, ..., L including the DU resource status 1, ..., L, respectively. The DU resource status indicates status (e.g., availability, occupancy, usage rate, load, etc.) of a respective DU resource of the DU 543. Examples and details for the DU resource status may be as described above relative to Fig. 4.

[0076] The RU 547A may determine whether to configure, reconfigure, release, enable, disable, activate, or deactivate a functionality for a UE based on RU resource status, at least a portion of the DU resource status 1 , ... , L, and / or the latest received DU resource status (e.g., the DU resource status L). The RU 547A may determine the RU resource status as described above. The RU 547A may obtain status of the computing resources (or the AI / ML resources) at the DU 543 from at least a portion of the DU resource status, and / or the latest-received DU resource status (e.g., the DU resource status L). The RU 547A determines whether to configure, reconfigure, release, enable, disable, activate, or deactivate a functionality (e.g., AI / ML functionality) for a UE (e.g., the UE 102), based on status of the computing resources (or AI / ML resources) at the DU 543. If the RU 547A determines that the DU 543 has sufficient computing (or AI / ML resources) for the functionality for the UE, the RU 547A configures, enables, or activates the functionality for the UE. Otherwise, if the RU 547A determines that the DU 543 does not have sufficient computing resources (or AI / ML resources) for the functionality for the UE, the RU 547A does not configure, enable, or activate the functionality for the UE or reconfigures, releases, disables, or deactivates thePatent Application Attorney Docket Number 0683-123- WOfunctionality for the UE. The DU 543 may forward the DU resource status 1 , , L to a data collection node or an OAM node. The data collection node or the 0AM generates a DU resources usage report or dashboard for the DU 543 based on the DU resource status. Alternatively or additionally, the DU 543 stores the DU resource status and generates a DU resources usage report or dashboard based on the DU resource status. Based on the usage report or dashboard, an operator may determine whether to upgrade the DU 543 to increase its capability and / or capacity.

[0077] The DU 543 and the RU 547B then perform an H1 Setup procedure 529B. The procedure 519B is similar to the procedure 519A. After procedure 519B, the DU 543 and the RU 547B perform procedure 525B which is similar to procedure 525A. That is, the procedure 525B includes at least one of: (i) an RU 547B and DU capability information exchange procedure 523B, (ii) an RU 547B and DU configuration information exchange 527B, (iii) an RU resource status transmission 530B, and a DU resource status transmission 532B. The procedures 525B, 523B, 527B, 530B, and 532B are similar to the procedures 525A, 523A, 527A, 530A, and 532A, respectively. The above descriptions of 525A, 523A, 527A, 530A, and 532A therefore apply and are not repeated. The capability information, configuration and / or resource status exchange as illustrated in Fig. 5 enables the RU 547A, DU 543, and RU 547B to select or be selected as part of a dynamically formed RAN node serving a specific UE.

[0078] Fig. 6 illustrates a scenario 600, similar to scenarios 400 and 500 in Figs.4 and 5, but in scenario 600 the CU 640 (which is similar to CU 440A and CU 440B) connects to DU 643 (which is similar to DU 543 and DU 443) and RU 647 (which is similar to RU 547A and RU 547B). The CU 640 and the DU 643 perform 603 an H1 Setup procedure, and then procedure 613 (which is similar to 413A and 413B). That is the procedure 613 includes (i) a DU and CU capability information exchange procedure 607, (ii) a DU and CU configuration information exchange procedure 611, (iii) a DU resource status transmission 614, and (iv) a CU resource status transmission 616. The above descriptions related to similar events and procedures illustrated in Fig. 4 are not repeated.Patent Application Attorney Docket Number 0683-123- WO

[0079] Further, the RU 647 and the CU 640 set up 635 an H1 interface (e.g., H1-C interface as illustrated in Fig. 2C), and then perform procedure 653 that includes (i) a CU and RU capability information exchange procedure 638, (ii) a CU and RU configuration information exchange procedure 651, (iii) an RU resource status transmission 654, and (iv) a CU resource status transmission 656. In the procedure 635, the RU 647 transmits 643 a H1 Setup Request message to the CU 640. In response to the H1 Setup Request message, the CU 640 transmits 636 a H1 Setup Response message to the RU 647. The RU 647 may include an RU ID in the H1 Setup Request message. The RU ID uniquely identifies the RU 647. The CU 640 may include a CU ID in the H1 Setup Response message. The CU ID uniquely identifies the CU 640. The RU 647 may include a first protocol version in the H1 Setup Request message, the first protocol version indicating a version of a first protocol (e.g., an RRC protocol). The CU 640 includes a second protocol version in the H1 Setup Response message, indicating a version of the first protocol. The first protocol version may be a newer version, the same version, or an older version than the second protocol version. In some embodiments, when the second protocol version is a newer version than the first protocol version, the CU 640 uses a version of the first protocol equal to or older than the first protocol version to communicate with the RU 647. In some embodiments, when the first protocol version is a newer version than the second protocol version, the RU 647 uses a version of the first protocol equal to or older than the second protocol version to communicate with the CU 640. The RU 647 may include a third protocol version in the H1 Setup Request message, the third protocol version indicating a version of a second protocol (e.g., an interface application protocol such as an H1 application protocol). The CU 640 may include a fourth protocol version in the H1 Setup Response message, the fourth protocol version indicating a version of the second protocol. The third protocol version may be a newer version, the same version, or an older version than the fourth protocol version. In some embodiments, when the fourth protocol version is a newer version than the third protocol version, the CU 640 uses a version of the second protocol equal to or older than the third protocol version to communicate with the RU 647. In some embodiments, when the third protocol version is a newer version than the fourth protocol version, the RU 647 may use a version of thePatent Application Attorney Docket Number 0683-123-WOsecond protocol equal to or older than the fourth protocol version to communicate with the CU 640.

[0080] The descriptions for the procedure 525A in Fig. 5 can apply to the procedure 653, and the descriptions for the RU 547A and the DU 543 can apply to the RU 647 and the CU 640 respectively. For example, the descriptions for events 522, 526, and 530A can apply to events 639, 652, and 654 respectively. Similarly, the descriptions for the procedure 413A can apply to the procedure 653, and the descriptions for the DU 443 and the CU 440A can apply to the RU 647 and the CU 640 respectively. For example, the descriptions for events 408, 412, and 416A can apply to events 637, 650, and 656 respectively.

[0081] In some implementations, the CU 640 may transmit the RU capabilities 1 , ... , P to the DU 643 in a CU-to-DU message. The CU-to-DU message may be any CU-to-DU message described above. In some implementations, the CU 640 may transmit the RU resource status 1, ... , Q, to the DU 643 in CU-to-DU messages 1, ..., Q, respectively. In other implementations, the CU 640 may select a portion of the RU resource status 1, ..., Q and transmit the portion in one or more CU-to-DU messages to the DU 643. The capability information, configuration and / or resource status exchange enables the RU 647, DU 643, and CU 640 to select or be selected as part of a dynamically formed RAN node serving a specific UE.

[0082] Next Fig. 7 illustrates a scenario 700 in which DU 743A and DU 743B (which are similar to DU 443, 543, and 643 and similarly use processing hardware such as 130 or 131) establish an interface and then exchange information (i.e. , capabilities information, configuration information, and / or resource status) via this interface. In the G1 setup procedure 761 , the DU 743A first transmits 760 a G1 Setup Request message to the DU 743B to request to set up an interface (e.g., called G1 interface or connection). In response, the DU 743B transmits 762 a G1 Setup Response message to the DU 743A. The DU 743A may include a first DU ID in the G1 Setup Request message, the first DU ID uniquely identifying the DU 743A. The DU 743A may also include a first protocol version in the G1 Setup Request message, the first protocol version indicating a version of the first protocol. The DU 743B may include a secondPatent Application Attorney Docket Number 0683-123- WODU ID in the G1 Setup Response message, the second DU ID uniquely identifying the DU 743B. The DU 743B may also include a second protocol version in the G1 Setup Response message, the second protocol version indicating a version of the first protocol. The first protocol version may be a newer version, the same version, or an older version than the second protocol version. In some embodiments, if the second protocol version is a newer version than the first protocol version, the DU 743B may use a version of the first protocol equal to or older than the first protocol version to communicate with the DU 743A. In some embodiments, if the first protocol version is a newer version than the second protocol version, the DU 743A may use a version of the first protocol equal to or older than the second protocol version to communicate with the DU 743B. The DU 743A may include a third protocol version in the G1 Setup Request message, indicating a version of a second protocol (e.g., an interface application protocol such as a G1 application protocol). The DU 743B may also include a fourth protocol version in the G1 Setup Response message, the fourth protocol version indicating a version of the second protocol. The third protocol version may be a newer version, the same version, or an older version than the fourth protocol version. In some embodiments, if the fourth protocol version is a newer version than the third protocol version, the DU 743B may use a version of the second protocol equal to or older than the third protocol version to communicate with the DU 743A. In some embodiments, if the third protocol version is a newer version than the fourth protocol version, the DU 743A may use a version of the second protocol equal to or older than the fourth protocol version to communicate with the DU 743B. In some embodiments, the G1 interface includes or is a G1-C interface for exchanging DU-to-DU messages between the DU 743A and the DU 743B.

[0083] After setting up the G1 interface, the DU 743A and the DU 743B perform procedure 765 that includes at least one of (i) a capabilities information exchange (i.e. , 764A, 764B), (ii) a configuration information exchange procedure (i.e., 766A, 766B), (iii) a first DU resource status transmission 768A, and (iv) a second DU resource status transmission 768B. Thus, the DU 743A may transmit 764A first DU capabilities 1, ..., N1 (N1 being a positive integer that may be the same or different from N in Fig. 4, 5,Patent Application Attorney Docket Number 0683-123-WOand 6) to the DU 743B using a first DUA-to-DUB message (i.e. , a message from the DU 743A to the DU 743B). The first DUA-to-DUB message may be a dedicated DU capability information message. The DU 743A may proactively transmit the first DUA-to-DUB message to the DU 743B. Alternatively or additionally, the DU 743A may transmit the first DUA-to-DUB message in response to receiving a first additional DUB-to-DUA message (i.e., a message from the DU 743B to the DU 743A). The first additional DUB-to-DUA message may be a request for capability information. In some alternative embodiments, event 764A is combined with event 760, the G1 Setup Request message including the capability information. Similar to step 764A, the DU 743B may transmit 764B second DU capabilities 1, ..., N2 (N2 being a positive integer that may be the same or different from N1 and / or from N in Figs. 4, 5, and 6) to the DU 743A using a first DUB-to-DUA message.

[0084] Within the configuration information exchange procedure, the DU 743A may transmit 766A first DU configuration information to the DU 743B using a second DUA-to-DUB message. The second DUA-to-DUB message may be a dedicated DU Configuration Update message. The DU 743A may receive a second additional DUB-to-DUA message from the DU 743B, in response to the second DUA-to-DUB message. The second additional DUB-to-DUA message may be a DU Configuration Update Acknowledgement. In some alternative embodiments, event 766A is combined with event 764A and / or event 760 so that the G1 Setup Request message includes the first DU configuration information. Similar to step 766A, the DU 743B may transmit 766B second DU configuration information to the DU 743A using a second DUB-to-DUA message.

[0085] The DU 743A may then transmit 768A first DU resource status 1 , ... , L1 (L1 being a positive integer that may be the same as L in Figs, 4, 5, and 6) to the DU 743B. The DU 743A may transmit the first DU resource status periodically with a fixed transmission periodicity (as previously discussed). The DU 743A may receive the periodicity from the DU 743B, a CU or an 0AM node, or the periodicity is predetermined or preconfigured. Alternatively or additionally, the DU 743A may transmit the first DU resource status when an event occurs (as previously discussed). The DU 743A mayPatent Application Attorney Docket Number 0683-123- WOreceive a configuration of the event from the DU 743B, CU, or OAM node, or the event is predetermined or preconfigured. The event may be a change in DU resource status above a threshold. The configuration of the event may configure the threshold, or the threshold is predetermined or preconfigured. The DU 743A transmits, to the DU 743B, DU resource status update messages 1, ..., L1 including the first DU resource status 1, ..., L1, respectively. Similarly, the DU 743B may then transmit 768B second DU resource status 1 , ... , L2 (L2 being a positive integer that may be the same as L1 and / or L in Figs, 4, 5, and 6) to the DU 743A.

[0086] After completing the procedure 765, the DU 743A generates 770A one or more configurations, based on the first DU capabilities, the second DU capabilities, the first DU configuration information, the second DU configuration information, the first DU resource status, and / or the second DU resource status. The DU 743A then transmits 772A the one or more configurations to a UE 102A it serves. In some embodiments, the DU 743A broadcasts one or more broadcast messages (e.g., system information blocks) including the one or more configurations via a cell to the UE 102A. In other embodiments, DU 743A transmits the one or more configurations to a CU (not shown) for the UE 102A. The CU may transmit one or more dedicated messages (e.g., RRC reconfiguration messages) including the one or more configurations to the UE 102A. In yet other embodiments, the DU 743A broadcasts some of the configurations via the cell and transmits the other of the configurations to the CU. The CU transmits one or more dedicated messages (e.g., RRC reconfiguration messages) including the other of the configurations to the UE 102A directly or via a network node. The network node may be a CN element (e.g., an AMF), a base station, or an additional DU. In some implementations, the UE 102A uses the one or more configurations to communicate with the DU 743A. In other implementations, the UE 102A uses the one or more configurations to measure and / or select or reselect a cell operated by the DU 743B.

[0087] Similarly, the DU 743B generates 770B one or more configurations and transmits 772B the one or more configurations to a UE 102B it serves. Events 770B and 772B are similar to events 770A and 770B, respectively. The UE 102B may usePatent Application Attorney Docket Number 0683-123-WOthe one or more configurations to communicate with the DU 743B or to measure and / or select or reselect a cell operated by the DU 743A.

[0088] Examples and descriptions described for the DU capabilities, DU configuration information, and resource status set forth relative to Fig. 4 are pertinent for DU 743A and DU 743B and are not repeated.

[0089] Fig. 8A illustrates a scenario 800A showing the manner in which the UE receives PHY and / or layer 2 parameters, in which the A CU 840 (similar to CU 440A, 440B, and / or 640) and a DU 843 (similar to DU 443, 543, and / or 643) perform 805 procedures 403 and 413 similar to procedure 403A and 413A illustrated in Fig. 4 and described above. The DU 843 and RU 847 (similar to RU 547A, 547B and / or 647) perform procedures 519 and 525 (similar to 519A and 525A in Fig. 5). The CU 840 is then able to communicate 874 with the UE 102 via the DU 843 and the RU 847. The CU 840 transmits 876 a UE Context Request message to the DU 843. After receiving the UE Context Request message, the DU 843 transmits 877 a DU-to-RU message to the RU 847, requesting physical layer (PHY) configuration parameters. In response, the RU 847 generates first PHY configuration parameters and transmits 878 an RU-to-DU message including the first PHY configuration parameters to the DU 843. The DU 843 then retrieves the first PHY configuration parameters from the RU-to-DU message and transmits 879 a UE Context Response message including the first PHY configuration parameters to the CU 840. The RU 847 may configure the first PHY configuration parameters for protocol operation (e.g., for PHY 302-1) between the RU 847 and the UE 102. The DU 843 may include second PHY configuration parameters in the UE Context Response message. The DU 843 may generate layer 2 configuration parameters and include the layer 2 configuration parameters in the UE Context Response message. The layer 2 configuration parameters may include MAC layer configuration parameters and / or RLC configuration parameters. The DU 843 may configure the second PHY configuration parameters for protocol operation (e.g., for PHY 302-2) between the DU 843 and the UE 102.

[0090] The UE Context Request message and the UE Context Response message may be a UE Context Setup Request message and a UE Context SetupPatent Application Attorney Docket Number 0683-123- WOResponse message, respectively (e.g., as defined in 3GPP TSs). The UE Context Request message and the UE Context Response message may also be a UE Context Modification Request message and a UE Context Modification Response message, respectively (e.g., as defined in 3GPP TSs). The DU-to-RU message and the RU-to-DU message may be interface application protocol messages.

[0091] The CU 840 then transmits 880 a DL message including the first PHY configuration parameters, the second PHY configuration parameters, and / or the Layer 2 configuration parameters to the UE 102. The DL message may be a message (e.g., RRC setup message) to set up a connection with the UE 102, a message (e.g., RRC resume message) to resume a suspended connection with the UE 102, a message (e.g., RRC reestablishment message) to reestablish a connection with the UE 102, or a message (e.g., RRC reconfiguration message) to set up or modify radio resources for the UE 102. The CU 840 transmit the DL message to the UE 102 via the DU 843 and the RU 847 or via another network node (e.g., a CN node housing an AMF, a base station, or an additional DU). In response, the CU 840 may receive a DL response message from the UE 102 via the RU 847 and the DU 843 or via the network node. The DL response message may be a message (e.g., RRC setup complete message) to indicate completion of setting up the connection, a message (e.g., a RRC resume complete message) to indicate completion of resuming the connection, a message (e.g., a RRC reestablishment complete message) to indicate completion of reestablishing the connection, or a message (e.g., RRC reconfiguration complete message) indicating completion of setting up or modifying the radio resources.

[0092] The CU 840 then communicates 882 with the UE 102 via the DU 843 and RU 847, the DU 843 communicating with the UE 102 using the second PHY parameters and / or Layer 2 parameters and the RU 847 communicating with the UE 102 using the first PHY parameters.

[0093] Fig. 8B illustrates a scenario 800B similar to scenario 800A in Fig. 8A. In the scenario 800B, the CU 840 and the DU 843 perform 805 as in the scenario 800A, but then the CU 840 and the RU 847 perform 825 procedures 635 and 653 illustrated in Fig. 6. The CU 840 is thus enabled to communicate with the UE via the DU 843 and thePatent Application Attorney Docket Number 0683-123- WORU 847. In response to receiving 876 the UE Context Request message, the DU 843 transmits 879 a UE Context Response message including the second PHY configuration parameters and / or the layer 2 configuration parameters to the CU 840. The CU 840 also transmits 883 a CU-to-RU message to the RU 847, requesting physical layer (PHY) configuration parameters. In response, the RU 847 generates first PHY configuration parameters and transmits 884 a RU-to-CU message including the first PHY configuration parameters to the DU 840. In some embodiments, the UE Context procedure (i.e. , events 876 and 879) is performed before, in parallel with, or after the CU-RU procedure (events 883 and 884).

[0094] Fig. 9 illustrates a scenario 900 similar to the previously described scenarios. The DU 943 (which is similar to DU 443, 543, 643, 743A or 743B, 843) and the CU 940A (which is similar to CU 440 A, 640 and 840) perform 905A procedures 403A and 413A. Similarly, the DU 943 and the CU 940B perform 905B procedures 403B and 413B. The DU 943 then receives 986 a UL PDU from the UE 102. When or in response to receiving the UL PDU, the DU 943 performs 987 a CU selection and, in scenario 900, selects the CU 940A. The DU 943 then transmits 990 a DU-to-CU message including the UL PDU to the selected CU 940A. After receiving the UL PDU, the CU 940A may transmit 976 a UE Context Request message to the DU 943 (similar to 876). The CU 940A may then receive 979 (which is similar to 978) a UE Context Response message including PHY configuration parameters and / or layer 2 configuration parameters from the DU 943. The CU 940A generates a DL message including the PHY configuration parameters and / or the layer configuration parameters and transmits 992 a CU-to-DU message including the DL message to the DU 943. The DU 943 in turn transmits 988 the DL message to the UE 102. The DU 943 may transmit the DL message to the UE 102 via an RU (not shown). In some embodiments, the DU 943 communicates with the UE 102 using the PHY configuration parameters and / or the layer 2 configuration parameters and communicates data for the UE 102 with the CU 440A.

[0095] The DU 943 may select the CU 940A because the CU 940A is less loaded than the CU 940B or because the CU 940A provides a better quality of service than thePatent Application Attorney Docket Number 0683-123-WOCU 940B (otherwise it may select the CU 940B). Alternatively or additionally, the DU 943 selects the CU 940A because the DU 943 determines that the UL PDU is transmitted by the UE 102 for a particular service (e.g., emergency service, data service, voice call, video call, short message service, high priority service, multimedia priority service (MPS), or mission critical service (MCS)). In some embodiments, the DU 943 determines to select the CU 940A because the CU 940A supports the particular service or provides a better quality of service for the particular service. In other embodiments, the DU 943 determines to select the CU 940A because the particular service requires particular resources owned by the CU 940A. In yet other embodiments, the DU 943 determines to select the CU 940A because the CU 940A is primarily located near an edge server that provides the particular service. If the UL PDU is transmitted by the UE 102 for a service other than the service described above, the DU 943 may select the CU 940B.

[0096] In the CU selection, the DU 943 uses information included in the UL PDU (first UL PDU). The first UL PDU may be an RRC PDU including an RRC message. For example, the RRC message is an RRC request message such as an RRC setup request message, an RRC resume request message, or an RRC reestablishment request message. The information may be a cause value. For example, the cause value may indicate “emergency” for an emergency service, “high priority access” for a high priority service, “mobile originating data” for a mobile originating data service, “mobile originating voice call”, “mobile originating video call”, “mobile originating short message service”, “MPS priority access” for an MPS, “MCS priority access” for an MCS, etc. If the cause value is a first value indicating a first service, the DU 943 selects the CU 943A. Otherwise, if the cause value is a second value indicating a second service, the DU 943 selects the CU 943B. The information may include a first identity or identifier (ID), and then the DU 943 selects the CU 940A based on this first identity or ID. The first identity of ID may include a first portion and a second portion, with the first portion indicating a RAN-related ID is or includes a RAN-related ID, and the second portion indicating a UE-specific ID. The DU 943 then selects the CU based on the RAN-related ID that is or includes a RAN node ID indicating the CU 940A. If the RAN-related ID is orPatent Application Attorney Docket Number 0683-123-WOincludes a RAN node ID indicating the CU 940B, the DU 943 selects the CU 940B. Alternatively, the first portion indicates a CN-related ID, and the DU 943 selects the CU 940A based on the CN-related ID. If the CN-related ID is or includes a first value, the DU 943 selects the CU 940A. Otherwise if the CN-related ID is or includes a second value, the DU 943 selects the CU 940B. The CN-related ID may be or include at least one CN node ID. The at least one CN node ID may include an AMF region ID, an AMF set ID and / or an AMF pointer. In such cases, the UE-specific ID is a 5G Temporary Mobile Subscriber Identity. In another implementation, the at least one CN node ID includes an MME group ID and an MME code. In such cases, the UE-specific ID is a Temporary Mobile Subscriber Identity. In other implementations, the first ID is the RAN-related ID or the CN-related ID.

[0097] The DU 943 may receive a second UL PDU including the first UL PDU from the UE 102. The DU 943 may then select the CU 940A based on information included in the second UL PDU. The information may be or include the cause value or the first ID as described above. In some implementations, the second UL PDU is a MAC PDU and the information is included in a MAC control element (CE) included in the MAC PDU.

[0098] Figs. 10-23 are flowcharts of methods performed by RAN units (CU, DU or RU). Descriptions and examples described for Figs. 4-9 can apply to Figs. 10-23.

[0099] Fig. 10 illustrates a method 1000 performed by a DU (e.g., 843 in Fig. 8A). Method 1000 starts with the DU establishing 1003 (corresponding to 403A, 403B) an interface connection with a CU (e.g., 440A, 440B, 840). Method 1000 then includes 1013 at least one of (i) transmitting 1006 DU capabilities of the DU to the CU (corresponding to 406), (ii) transmitting 1010 DU configuration information of the DU to the CU (corresponding to 410), and (iii) transmitting 1014 DU resource status to the CU (corresponding to 414). Method 1000 then includes establishing 1019 (corresponding to 519) an interface connection with an RU (e.g., RU 547A, 547B, 647, 847, 947). The method then includes 1025 at least one of (i) receiving 1022 the RU capabilities from the RU (corresponding to 522), (ii) receiving RU configuration information from the RUPatent Application Attorney Docket Number 0683-123-WO(corresponding to 526, and (iii) receiving RU resource status from the RU (corresponding to 532).

[0100] Fig. 11 is a flowchart of a method 1100 performed by a DU (e.g., DU 743A or DU 743B). Method 1100 starts with performing 1109 the steps 1003 and 1013, followed (or preceded) by the steps 1019 and 1025. Method 1100 continues with establishing 1161 an interface connection with an other DU (corresponding to 761). Method 1100 further includes 1165 at least one of (i) receiving 1164 the other DU’s capabilities from the other DU (corresponding to 764), (ii) receiving 1166 the other DU’s configuration information from the other DU (corresponding to 766), and (iii) receiving 1168 the other DU’s resources status from the other DU (corresponding to 768). The DU may perform 1109 and / or 1129 before, in parallel with, or after 1165. Method 1100 then includes generating 1170 one or more configuration parameters based on one or more configuration parameters for a UE based on the DU capabilities, the DU resources status, the RU capabilities, the RU resources status, the CU capabilities, the CU resource status, the other DU’s capabilities and / or the other DU’s resource status (corresponding to 770). Further, the method includes transmitting 1172 the one or more configuration parameters to the UE (corresponding to 772).

[0101] Fig. 12 is a flowchart of a method 1200 performed by a DU (as any DU in Figs 4-9). Method 1200 starts with receiving 1294 a CU-to-DU message from a CU, querying DU capabilities. Method 1200 then includes transmitting 1210 a DU-to-CU message including DU capabilities 1, ..., N to the CU, in response to the CU-to-DU message, where N is a positive integer (corresponding, e.g., to 410A).

[0102] Fig. 13 is a flowchart of a method 1300 performed by a DU (as any DU in Figs 4-9). Method 1300 starts with receiving 1308 CU capabilities 1, ..., M, where M is a positive integer (corresponding, e.g., to step 408). Method 1300 continues with determining 1313 DU capabilities 1, ..., N (with N a positive integer) based on the CU capabilities 1, ..., M. Method 1300 the includes transmitting 1306 a DU-to-CU message including the DU capabilities 1, ..., N to the CU (corresponding, e.g., to step 406).Patent Application Attorney Docket Number 0683-123- WO

[0103] At least one of the CU capabilities 1 , ... , M may indicate that the CU supports AI / ML. For example, the CU capabilities 1, M include AI / ML-related capability / capabilities as described above. The DU may then indicate that the DU supports AI / ML in at least one of the DU capabilities 1 , , N based on the at least one CU capability. In another example, at least one of the CU capabilities 1, ..., M indicates that the CU supports sensing. In yet another example, the CU capabilities 1, ..., M include sensing capability / capabilities as described above. The DU may then indicate that the DU supports sensing in at least one of the DU capabilities 1 , ... , N based on the at least one CU capability. One of the CU capabilities 1 , ... , M may indicate a first protocol version of a protocol. The DU may then indicate a second protocol version of the protocol based on the first protocol version. The second protocol version may be the same version as the first protocol version or older than the first protocol version.

[0104] Fig. 1 illustrates a method 1400 performed by a DU (as any DU in Figs 4-9). Method 1400 starts with receiving 1408 CU capabilities followed by receiving 1422 RU capabilities. The method 1400 then continues with generating 1470 one or more configuration parameters based on the CU capabilities 1, ..., M and / or the RU capabilities 1, ..., N and then transmitting 1472 the one or more configuration parameters to the UE.

[0105] Fig. 15 illustrates a method 1500 performed by a DU1 (e.g., DU 743A or 743B). Method 1500 starts with receiving 1565 DU2’s capabilities and / or resource status, followed by optionally transmitting 1567 DUTs capabilities and resource status to DU2. Method 1500 continues with generating 1570 one or more UE configurations, based on the DU1 and DU2 capabilities, configuration information, and / or resources statuses, and transmitting 1572 the one or more configurations to a UE served by DU1.

[0106] The DU may generate the one or more configurations based on DU capabilities, the CU capabilities and / or the RU capabilities. The DU may generate a first portion and a second portion of the one or more configurations based on the RU capabilities and the DU capability / capabilities, respectively. The DU may generate a first portion and a second portion of the one or more configurations based on the RU capabilities and the CU capabilities, respectively. The DU may generate a first portion,Patent Application Attorney Docket Number 0683-123-WOa second portion, and a third portion of the one or more configurations based on the RU capabilities, the DU capabilities, and the CU capabilities, respectively.

[0107] Fig. 16 is a flowchart of a method 1600 performed by a DU (e.g., as in any of Figs. 4-9). Method 1600 starts with establishing 1603 an interface connection with a CU, followed, preceded or concurrent with establishing 1619 an interface connection with an RU. Method 1600 continues with receiving 1631 at least one first configuration parameter from the RU. Method 1600 may also include generating 1633 at least one second configuration parameter. The method 1600 then includes transmitting 1641 the at least one first configuration parameter and, when available, also the at least one second configuration parameter to the CU.

[0108] Fig. 17 is a flowchart of a method 1700 performed by a CU (e.g., 640). Method 1700 starts with establishing 1703 an interface connection with a DU followed by establishing 1735 a connection with an RU. Method 1700 continues with receiving 1752 at least one first configuration parameter from the RU followed by receiving 1710 at least one second configuration parameter from the DU. Method 1700 then includes transmitting 1742 the at least one first configuration parameter and the at least one second configuration parameter to the UE.

[0109] Figs. 18 and 19 are flowcharts of methods 1800 and 1900 respectively performed by an RU (as any of the RUs in Figs 4-9). Method 1800 starts with establishing 1819 an interface connection with a DU followed by performing 1825 at least one of steps 1822, 1826 and 1830. Method 1800 thus may include (i) transmitting 1822 RU capabilities to the DU (corresponding, e.g., to 522), transmitting 1826 RU configuration information to the DU (corresponding, e.g., to 526), and / or transmitting 1830 RU resource status to the DU (corresponding, e.g., to 530). The method then includes transmitting 1831 at least one first configuration parameter to the DU.

[0110] Method 1900 starts with establishing 1935 an interface connection with a CU followed by performing 1953 at least one of steps 1939, 1952, and 1964. Method 1900 thus may include (i) transmitting 1939 RU capabilities to the CU, (ii) transmitting 1952 RU configuration information to the CU, and / or (iii) transmitting 1954 RU resourcePatent Application Attorney Docket Number 0683-123-WOstatus to the CU. Method 1900 concludes with transmitting 1945 at least one first configuration parameter to the CU.

[0111] Fig. 20 is a flowchart of a method 2000 performed by a DU (e.g., any of the DUs in Figs. 4-9). Method 2000 starts with establishing 2003A an interface connection with a first CU and establishing 2003B an interface connection with a second CU. Method 2000 continues with receiving 2086 a UL PDU from a UE followed by determining 2087 whether to transmit the UL PDU to the first CU or to the second CU. Based on the result of the determining, the next step of method 2000 is transmitting 2088 the UL PDU to the first CU or transmitting 2089 the UL PDU to the second CU. The examples and embodiments described with respect to determining a CU as described in FIG. 19 may apply to FIG. 20.

[0112] Fig. 21 is a flowchart of a method 2100 similar to the method 2000.Method 2100 starts with steps 2103A and 2103B that are similar to 2003A and 2003B. Method 2100 continues with receiving 2187-1 a first UL PDU and receiving 2187-2 a second UL PDU from a first UE and a second UE, respectively. Method 2100 then includes transmitting 2188-1 the first UL PDU to the first CU and transmitting 2188-2 the second UL PDU to the second CU.

[0113] Fig. 22 is a flowchart of a method 2200 performed by an RU. Method 2200 starts with establishing 2219A an interface connection with a first DU and establishing 2219B an interface connection with a second DU. Method 2200 continues with receiving 2294 a PUSCH transmission from a UE followed by determining 2296 whether to transmit the PUSCH transmission to the first DU or to the second DU.Method 2200 concludes with transmitting 2298-1 the PUSCH transmission to the first DU or transmitting 2298-2 the PUSCH transmission to the second DU. The result of the determining step may be based on UL resources assigned for the PUSCH transmission. In some embodiments, the RU transmits a downlink control information (DCI) to the UE, configuring the UL resources. The UE then transmits (so the RU receives) the PUSCH transmission on the UL resources specified in the DCI. If the UL resources are configured by or for the first DU, the RU transmits the PUSCH transmission to the firstPatent Application Attorney Docket Number 0683-123-WODU. Otherwise, if the UL resources are configured by or for the second DU, the RU transmits the PUSCH transmission to the second DU.

[0114] Fig. 23 is a flowchart of a method 2300 similar to method 2200. Method 2300 starts with establishing 2319A an interface connection with a first DU and establishing 2319B an interface connection with a second DU (similar to 2219A and 2219B). Method 2300 further includes receiving 2395-1 a first PUSCH transmission from a first UE, transmitting 2397-1 the first PUSCH transmission to the first CU, receiving 2395-2 a second PUSCH transmission from a second UE, and transmitting 2397-2 the second PUSCH transmission to the second CU. The RU may determine to transmit the first PUSCH transmission to the first DU based on first UL resources assigned for the first PUSCH transmission as described for Fig. 22. Similarly, the RU may determine to transmit the second PUSCH transmission to the second DU based on second UL resources assigned for the second PUSCH transmission as described for Fig. 22.

[0115] The descriptions and example implementations described in an earlier figure can apply to a later figure or vice versa, if applicable. Generally speaking, description for one of the above figures can apply to another of the above figures.Examples, implementations and methods described above can be combined, if there is no conflict. An event or block described above can be optional or omitted. For example, an event or block with dashed lines in the figures can be optional. The description described from the perspective of the receiving node also applies to the sending node. For example, a description that a receiving node (e.g., DU) receives a message from a sending node (e.g., CU) may be replaced by the sending node sending a message to the receiving node. Similarly, a description that a receiving node (e.g., CU) receives a message from a sending node (e.g., DU) may be replaced by the sending node sending a message to the receiving node.

[0116] In some implementations, “message” is used and can be replaced by “information element (IE)”, and vice versa. In some implementations, “IE” is used and can be replaced by “field”, and vice versa. In some implementations, “configuration” can be replaced by “configurations” or “configuration parameters”, and vice versa. InPatent Application Attorney Docket Number 0683-123- WOsome implementations, “configures” or “configuring” can be replaced by “enables” or “enabling”. In some implementations, “requests” or “requesting” can be replaced by “indicates” or “indicating”. In some implementations, “indicates” or “indicating” can be replaced by “commands” or “commanding”. In some implementations, the “Al functionality” or “Al functionalities” can be replaced by “AI / ML functionality” or “AI / ML functionalities”. In some implementations, “functionalities” can be replaced by “functionality”. In some implementations, CUs and Dlls are implemented in a cloud system. In such cases, communication between the CUs and DUs as described above may be via remote procedure calls, shared memory, or inter-process communication.

[0117] A user device in which the techniques of this disclosure can be implemented (e.g., the UE 102) can be any suitable device capable of wireless communications such as a smartphone, a tablet computer, a laptop computer, a mobile gaming console, a point-of-sale (POS) terminal, a health monitoring device, a drone, a camera, a media-streaming dongle or another personal media device, a wearable device such as a smartwatch, a wireless hotspot, a femtocell, or a broadband router. Further, the user device in some cases may be embedded in an electronic system such as the head unit of a vehicle or an advanced driver assistance system (ADAS). Still further, the user device can operate as an internet-of-things (loT) device or a mobile-internet device (MID). Depending on the type, the user device can include one or more general-purpose processors, a computer-readable memory, a user interface, one or more network interfaces, one or more sensors, etc.

[0118] Certain embodiments are described in this disclosure as including logic or a number of components or modules. Modules may be software modules (e.g., code, or machine-readable instructions stored on non-transitory machine-readable medium) or hardware modules. A hardware module is a tangible unit capable of performing certain operations and may be configured or arranged in a certain manner. A hardware module can comprise dedicated circuitry or logic that is permanently configured (e.g., as a special-purpose processor, such as a field programmable gate array (FPGA) or an application-specific integrated circuit (ASIC), a digital signal processor (DSP), etc.) to perform certain operations. A hardware module may also comprise programmable logicPatent Application Attorney Docket Number 0683-123-WOor circuitry (e.g., as encompassed within a general-purpose processor or other programmable processor) that is temporarily configured by software to perform certain operations. The decision to implement a hardware module in dedicated and permanently configured circuitry, or in temporary configured circuitry (e.g., configured by software) may be driven by cost and time considerations.

[0119] When implemented in software, the techniques can be provided as part of the operating system, a library used by multiple applications, a particular software application, etc. The software can be executed by one or more general-purpose processors or one or more special-purpose processors.

[0120] Upon reading this disclosure, those of skill in the art will appreciate still additional and alternative structural and functional designs for handling mobility between base stations through the principles disclosed herein. Thus, while particular embodiments and applications have been illustrated and described, it is to be understood that the disclosed embodiments are not limited to the precise construction and components disclosed herein. Various modifications, changes and variations, which will be apparent to those of ordinary skill in the art, may be made in the arrangement, operation and details of the method and apparatus disclosed herein without departing from the spirit and scope defined in the appended claims.

[0121] The detailed descriptions do not preclude other embodiments within the scope of the appended claims. The embodiments are not limited to the above-described configurations but may be extended to other arrangements.

[0122] Reference throughout this section to “one embodiment” or “an embodiment” means that a particular feature, structure, or characteristic described in connection with an embodiment is included in at least one embodiment. Thus, the appearances of the phrases “in one embodiment” or “in an embodiment” in various places throughout the specification are not necessarily all referring to the same embodiment. Further, the particular features, structures or characteristics may be combined in any suitable manner in one or more embodiments.

[0123] Numerical adjectives “first”, “second”, and “third” do not imply any order (are not ordinals) but are markers to distinguish separate instances of similar elements.Patent Application Attorney Docket Number 0683-123- WOReferences to the singular (e.g., “a” or “an”, “the”) should include the plural unless clearly indicated otherwise.

[0124] As used herein, a phrase referring to “at least one of’ or “one or more of’ a list of items refers to any combination of those items, including single members. For example, “at least one of: a, b, or c” is intended to cover the possibilities of: a only, b only, c only, a combination of a and b, a combination of a and c, a combination of b and c, and a combination of a and b and c.

[0125] Although the features and elements of the present embodiments are described in the embodiments in particular combinations, each feature or element can be used alone without the other features and elements of the embodiments or in various combinations with or without other features and elements disclosed herein. The methods or flowcharts may be implemented in a computer program, software or firmware tangibly embodied in a computer-readable storage medium for execution by a specifically programmed computer or processor.

Claims

Patent Application Attorney Docket Number 0683-123- WOWHAT IS CLAIMED IS:

1. A wireless communication method (1000, 1100) performed by a first radio access network, RAN, unit (340, 343, 347) of a disaggregated RAN node (104), the method comprising:establishing (1003, 1161) a first interface connection with a second RAN unit (340, 343, 347) of the disaggregated RAN node;receiving (1013, 1165), via the first interface connection, at least one of second RAN unit capability information or second RAN unit resource status of the second RAN unit; andgenerating (1170) a UE configuration for a UE served by the disaggregated RAN node based on the second RAN unit capability information or the second RAN unit resource status.

2. The method of claim 1 , further comprising:transmitting, via the first interface connection, at least one of first RAN unit capability information or a first RAN unit resource status.

3. The method of claim 1 or 2, further comprising:establishing a second interface connection with a third RAN unit of the disaggregated RAN node; andreceiving, via the second interface connection, at least one of third RAN unit capability information or third RAN unit resource status from the third RAN unit.

4. The method of claim 3, further comprising:selecting the second RAN unit or the third RAN unit for serving the UE based on the second RAN unit capability information, the second RAN unit resource status, the third RAN unit capability information, and / or the third RAN unit resource status.Patent Application Attorney Docket Number 0683-123- WO5. The wireless communication method of claim 3 or 4, wherein the first RAN unit is a distributed unit, DU, the second RAN unit is a first centralized unit, CU and the third RAN unit is a second CU.

6. The wireless communication method of claim 3 or 4, wherein the first RAN unit is a radio unit, RU, the second RAN unit is a first distributed unit, DU and the third RAN unit is a second DU.

7. The wireless communication method of claim 3, wherein the first RAN unit, the second RAN unit and the third RAN unit form the disaggregated RAN serving a specific UE.

8. The wireless communication method of any of claims 1 to 7, wherein the second RAN unit resource status specifies a status for each among one or more computing resources, radio resources, and / or AI / ML resources of the second RAN unit.

9. The wireless communication method of claim 8, wherein the status indicates availability, occupancy, usage rate, and / or load of a respective resource.

10. The wireless communication method of any of claims 1 to 9, further comprising:receiving an update of the second RAN unit resource status periodically.

11. The wireless communication method of any of claims 2 to 10, further comprising:periodically transmitting an update of the first RAN unit resource status.

12. The wireless communication method of any of claims 2 to 11 , further comprising:sending an update of the first RAN unit resource status when a predetermined trigger event occurs.Patent Application Attorney Docket Number 0683-123- WO13. The wireless communication method of claim 12, wherein the predetermined trigger event includes at least one of:a change in the first RAN unit resource status that achieves a threshold criterion; orreceiving a request from the second RAN unit.

14. The wireless communication method of any of claims 1 to 13, wherein the second RAN unit is a radio unit, Rll, or a distributed unit, DU, or a central unit, CU, and the second RAN unit capability information includes at least one of:a capability that is related to sixth generation, 6G, features or functions, an artificial intelligence, Al, or machine learning, ML, capability,a sensing-related capability,a transmission reception point, TRP, related capability,a multiple input multiple output, MIMO, related capability,a coverage-related capability,a positioning-related capability,a connection-related capability,a transport layer-related capability information,a communication protocol related capability,a computing-related capability, ora transport layer-related capability.

15. The wireless communication method of claim 14, wherein the connection-related capability includes a radio bearer related capability, a latency related capability, and / or a quality of service related capability.

16. The wireless communication method of any of claims 1 to 15, further comprising:transmitting the UE configuration to the UE.Patent Application Attorney Docket Number 0683-123- WO17. A wireless communication device (130, 340, 343, 347) operating as a unit of a distributed radio access network node and comprising a processor (132) and a transceiver (134) cooperatively performing a method as recited in any of claims 1 to 16.

Images