Supporting multiple radio units on a single distributed unit

Abstract

In general, the present subject matter relates to supporting multiple radio units (RUs) on a single distributed unit (DU). In some implementations, supporting multiple RUs on a single DU may include receiving, by a DU in an open radio access network, an identifier identifying the RU from an RU in the open radio access network, identifying, by the DU, communication information associated with the RU based on the identifier identifying the RU, determining, by the DU, communication characteristics for data transmission to the RU using a particular carrier of the DU, and transmitting data from the DU to the RU using the particular carrier according to the communication information and the communication characteristics.

Description

[Technical Field]

[0001] In some implementations, the present subject matter relates to telecommunications systems, and in particular to supporting multiple radio units (RUs) on a single distributed unit (DU). [Background technology]

[0002] In today's world, cellular networks provide on-demand communication capabilities to individuals and businesses. Typically, cellular networks are wireless networks that can be distributed over a terrestrial area called a cell. Each such cell is served by at least one fixed-location transceiver called a cell site or base station. Each cell may use a different set of frequencies from its neighboring cells to avoid interference and provide improved service within each cell. When cells are combined, they provide wireless coverage over a wide geographic area, allowing numerous mobile phones and / or other wireless devices or portable transceivers to communicate with each other and with fixed transceivers and phones anywhere in the network. Such communication is performed through base stations and is achieved even when a mobile transceiver is moving through two or more cells during transmission. Major wireless communication providers have deployed such cell sites worldwide, allowing communicating mobile phones and mobile computing devices to connect to the public switched telephone network and the public Internet.

[0003] A mobile phone is a portable telephone that can receive and / or make telephone and / or data communications through a cell site or transmission tower by using radio waves to transfer signals to and from the mobile phone. Given the large number of mobile phone users, current mobile phone networks offer limited shared resources. In that regard, cell sites and handsets may change frequencies and use low-power transmitters to allow simultaneous use of the network by many callers with less interference. Cell site coverage may depend on the particular geographic location and / or the number of users that can potentially use the network. For example, in cities, cell sites may have a range of up to about 1 / 2 mile, while in rural areas, the range may be as long as 5 miles, and in some areas, users may receive signals from cell sites as far as 25 miles away.

[0004] The following are some examples of digital cellular technologies used by communication providers: Global System for Mobile Communications ("GSM"), General Packet Radio Service ("GPRS"), cdmaOne, CDMA2000, Evolution Data Optimized ("EV-DO"), Enhanced Data Rates for GSM Evolution ("EDGE"), Universal Mobile Telecommunications System ("UMTS"), Digital Enhanced Cordless Communications ("DECT"), Digital AMPS ("IS-136 / TDMA"), and Integrated Digital Enhanced Network ("iDEN"). 4G LTE, developed by the Long Term Evolution, or 3rd Generation Partnership Project ("3GPP®") standards organization, is a standard for high-speed data wireless communication for mobile phones and data terminals. 5G standards are currently being developed and deployed. 3GPP cellular technologies such as LTE and 5G NR are an evolution of earlier generations of 3GPP technologies such as GSM / EDGE and UMTS / HSPA digital cellular technologies, and allow for increased capacity and speeds by using different air interfaces along with improvements to the core network.

[0005] A cellular network may be divided into a radio access network and a core network. The radio access network (RAN) may include network functions capable of handling radio layer communication processing. The core network may include network functions capable of handling higher layer communications, such as Internet Protocol (IP), transport layer, and application layer. In some cases, the RAN function may be divided into baseband unit function and radio unit function; for example, a radio unit connected to a baseband unit via a fronthaul network may be responsible for lower layer processing of the radio physical layer, and the baseband unit may be responsible for higher layer radio protocols, such as MAC, RLC, etc.

[0006] In an open radio access network (open RAN), communications over the fronthaul network can be synchronized in time and frequency by synchronizing the clocks of the distributed units (O-DUs) and radio units (O-RUs) that communicate over the fronthaul network. Synchronization can enable messages communicated over the fronthaul network to be properly sent and received within predetermined time windows for such messages. However, conventional O-DUs cannot support multiple O-RUs because there is no method defined as part of the standards currently available by the Open RAN (O-RAN) Alliance or 3GPP that allows a single O-DU to support multiple O-RUs, each with different fronthaul message requirements. Summary of the Invention [Means for solving the problem]

[0007] In some implementations, the subject matter relates to a computer-implemented method that can include receiving, by a distributed unit (DU) in an open radio access network, from a radio unit (RU) in the open radio access network, an identifier that identifies the RU. The method can also include identifying, by the DU, communication information associated with the RU based on the identifier that identifies the RU, determining, by the DU, communication features for data transmission to the RU using a specific carrier of the DU, and transmitting data from the DU to the RU using the specific carrier according to the communication information and the communication features.

[0008] The method can enable a DU to support multiple RUs in an open radio access network.

[0009] In some implementations, the present subject matter can include one or more of the following optional features.

[0010] In some implementations, the communication information can include an interoperability (IOT) profile, and the communication characteristics can include a delay window for data transmission. Further, identifying can include looking up the identifier in a lookup table stored in at least one non-transitory storage medium, where the lookup table can uniquely associate each of the multiple RU identifiers with the IOT profile, and / or the data can be transmitted over a fronthaul network and can include control plane (C-plane) data and user plane (U-plane) data.

[0011] In some implementations, the communication information may include an extended antenna carrier identifier (eAxC_ID) including a DU PORT ID, and determining the communication characteristics may include modifying the DU PORT ID. Further, the data may be transmitted over a fronthaul network and may include U-plane data. Furthermore, the method may also further include transmitting the modified DU PORT ID on the U-plane from the DU to the RU, and the RU may be configured to loop the received modified DU PORT ID to the C-plane.

[0012] In some implementations, identifying the communication information can include forming a beamforming profile and assigning a deployment ID to the RU, and the communication characteristics can include beamforming weights. Further, transmitting data can include transmitting beamforming weights from the DU to the RU, and / or determining the communication characteristics can include identifying which beamforming weights of a plurality of pre-defined beamforming weights correlate with the assigned deployment ID.

[0013] In some implementations, the method may also include transmitting the identified communication information from Layer 3 of the DU to Layer 1 of the DU, where Layer 1 of the DU may perform the determining.

[0014] In some implementations, the DU may receive the identifier from the RU in an initial handshake process between the DU and the RU.

[0015] In some implementations, the DU may be a single DU, and the method may also include receiving, by the DU, from a second RU in the open radio access network, an identifier identifying the second RU, and the method may also include identifying, by the DU, communication information associated with the second RU based on the identifier identifying the second RU, and the method may also include determining, by the DU, communication characteristics related to data transmission to the second RU using a second particular carrier of the DU, and the method may also include transmitting data from the DU to the second RU using the second particular carrier in accordance with the communication information associated with the second RU and the communication characteristics related to the data transmission to the second RU.

[0016] In some implementations, a base station may include at least one processor and at least one non-transitory storage medium that stores instructions that, when executed by the at least one processor, cause the at least one processor to perform operations, and the base station may be configured to communicate in a wireless communication network, and the operations may include the method. Further, the base station may include an eNodeB or a gNodeB.

[0017] Non-transitory computer program products (i.e., physically embodied computer program products) that store instructions that, when executed by one or more data processors of one or more computing systems, cause at least one data processor to perform the operations described herein are also described. Similarly, computer systems that may include one or more data processors and memory coupled to the one or more data processors are also described. The memory may store, on a temporary or permanent basis, instructions that cause at least one processor to perform one or more of the operations described herein. Furthermore, methods may be implemented by one or more data processors within a single computing system or distributed across two or more computing systems. Such computing systems may be connected via one or more connections and may exchange data and / or commands or other instructions, etc., including, but not limited to, connections over a network (e.g., the Internet, a wireless wide area network, a local area network, a wide area network, a wired network, etc.), such as via a direct connection between one or more of the computing systems.

[0018] The details of one or more variations of the subject matter described herein are set forth in the accompanying drawings and the description below. Other features and advantages of the subject matter described herein will be apparent from the description and drawings, and from the claims. [Brief explanation of the drawings]

[0019] The accompanying drawings, which are incorporated in and constitute a part of this specification, illustrate certain aspects of the subject matter disclosed herein and, together with the description, serve to explain some of the principles associated with the disclosed implementations.

[0020] [Figure 1a] FIG. 1 illustrates an exemplary conventional Long Term Evolution (“LTE”) communication system.

[0021] [Figure 1b] FIG. 1b illustrates further details of the exemplary LTE system shown in FIG. 1a.

[0022] [Figure 1c] FIG. 1b illustrates further details of the evolved packet core of the exemplary LTE system shown in FIG. 1a.

[0023] [Figure 1d] FIG. 1B illustrates an exemplary evolved Node B for the exemplary LTE system shown in FIG. 1a.

[0024] [Figure 2] FIG. 2 shows further details of the evolved Node B shown in FIGS. 1a-1d.

[0025] [Figure 3] FIG. 1 illustrates an exemplary virtual radio access network, in accordance with some implementations of the present subject matter.

[0026] [Figure 4] FIG. 1 illustrates an exemplary 3GPP split architecture for providing use of higher frequency bands to its users.

[0027] [Figure 5a] FIG. 1 illustrates an exemplary 5G wireless communication system.

[0028] [Figure 5b] A diagram illustrating an example layer architecture of a split gNB and / or a split ng-eNB (e.g., a next-generation eNB that may be connected to 5GC).

[0029] [Figure 5c] A diagram illustrating an exemplary functional division in the gNB architecture shown in Figures 5a-5b.

[0030] [Figure 6]FIG. 1 illustrates an exemplary system including open wireless access network components.

[0031] [Figure 7] 1 is a graph showing an example of fronthaul throughput over time.

[0032] [Figure 8a] FIG. 2 illustrates a first portion of an exemplary time transmission window.

[0033] [Figure 8b] 8b shows a second portion of the exemplary time transmission window of FIG. 8a.

[0034] [Figure 9] FIG. 1 illustrates an exemplary method according to some implementations of the present subject matter.

[0035] [Figure 10] FIG. 1 illustrates another exemplary method, according to some implementations of the present subject matter.

[0036] [Figure 11] 11 illustrates an exemplary system in which the method of FIG. 10 is implemented, according to some implementations of the present subject matter.

[0037] [Figure 12] FIG. 10 illustrates yet another exemplary method according to some implementations of the present subject matter.

[0038] [Figure 13] 13 illustrates an exemplary system in which the method of FIG. 12 is implemented, according to some implementations of the present subject matter.

[0039] [Figure 14] FIG. 10 illustrates yet another exemplary method according to some implementations of the present subject matter.

[0040] [Figure 15] 15 illustrates an exemplary system in which the method of FIG. 14 is implemented, according to some implementations of the present subject matter.

[0041] [Figure 16] FIG. 1 illustrates an exemplary system, in accordance with some implementations of the present subject matter.

[0042] [Figure 17] FIG. 1 illustrates an exemplary method according to some implementations of the present subject matter. DETAILED DESCRIPTION OF THE INVENTION

[0043] The present subject matter may provide systems and methods that may be implemented in wireless communication systems, including various wireless communication systems, including 5G new wireless communication systems, long-term evolution communication systems, etc.

[0044] Generally, the present subject matter relates to supporting multiple radio units (RUs) on a single distributed unit (DU).

[0045] In some implementations of the present subject matter, DUs in an open radio access network ("open RAN" or "ORAN") can be configured to support multiple RUs in the open RAN. Thus, fewer DUs may need to be deployed to support multiple RUs, reducing costs. Traditional DUs in an open radio access network cannot support multiple RUs in an open radio access network because there is no method defined as part of the standard specifications currently available by the O-RAN Alliance that allows a single DU to support multiple RUs, each with different fronthaul message requirements.

[0046] O-RAN Alliance standards that define one or more aspects that may be related to the present subject matter include O-RAN Working Group (WG) 4 (Open Fronthaul Interface WG) "Control, User and Synchronization Plane Specification." 3GPP standards may also be related to one or more aspects of the present subject matter.

[0047] One or more aspects of the present subject matter may be incorporated into transmitter and / or receiver components of base stations (e.g., gNodeBs, eNodeBs, etc.) within such communication systems. The following is a general discussion of Long Term Evolution and 5G New Radio communication systems. I. Long Term Evolution Communication System

[0048] 1a-1c and 2 illustrate an exemplary conventional Long Term Evolution ("LTE") communication system 100 along with its various components. The LTE system, or 4G LTE, as it is commercially known, is governed by a standard for high-speed data wireless communication for mobile phones and data terminals. The standard is an evolution of GSM / EDGE ("Global System for Mobile Communications" / "Enhanced Data Rates for GSM Evolution") and UMTS / HSPA ("Universal Mobile Telecommunications System" / "High-Speed ​​Packet Access") network technologies. The standard was developed by 3GPP ("3rd Generation Partnership Project").

[0049] As shown in FIG. 1a, system 100 may include an Evolved Universal Terrestrial Radio Access Network (“EUTRAN”) 102, an Evolved Packet Core (“EPC”) 108, and a Packet Data Network (“PDN”) 101, where EUTRAN 102 and EPC 108 provide communications between user equipment 104 and PDN 101. EUTRAN 102 may include multiple Evolved Node Bs (“eNodeB” or “ENODEB” or “enodeb” or “eNB”) or base stations 106(a, b, c) (as shown in FIG. 1b) that provide communications capabilities to multiple user equipment 104(a, b, c). User equipment 104 may be a mobile phone, a smartphone, a tablet, a personal computer, a personal digital assistant (“PDA”), a server, a data terminal, and / or any other type of user equipment, and / or any combination thereof. User equipment 104 can connect to the EPC 108 and ultimately to the PDN 101 via any eNodeB 106. Typically, user equipment 104 can connect to the nearest eNodeB 106 in terms of distance. In the LTE system 100, the EUTRAN 102 and the EPC 108 cooperate to provide connectivity, mobility, and services for user equipment 104.

[0050] Figure 1b shows further details of the network 100 shown in Figure 1a. As mentioned above, the EUTRAN 102 includes multiple eNodeBs 106, also known as cell sites. The eNodeBs 106 provide radio functionality and perform important control functions, including air link resource scheduling or radio resource management, active mode mobility or handover, and admission control for services. The eNodeBs 106 are responsible for selecting which mobility management entity (MME, as shown in Figure 1c) will serve the user equipment 104, as well as protocol features such as header compression and encryption. The eNodeBs 106 that make up the EUTRAN 102 cooperate with each other for radio resource management and handover.

[0051] Communication between the user equipment 104 and the eNodeB 106 occurs over an air interface 122 (also known as the "LTE-Uu" interface). As shown in FIG. 1b, the air interface 122 provides communication between the user equipment 104b and the eNodeB 106a. The air interface 122 uses orthogonal frequency division multiple access ("OFDMA") and single-carrier frequency division multiple access ("SC-FDMA"), an OFDMA variant, on the downlink and uplink, respectively. OFDMA allows the use of multiple known antenna technologies, such as multiple-input multiple-output ("MIMO").

[0052] The air interface 122 uses various protocols, including radio resource control ("RRC") for signaling between the user equipment 104 and the eNodeB 106 and non-access stratum ("NAS") for signaling between the user equipment 104 and the MME (as shown in FIG. 1c). In addition to signaling, user traffic is transferred between the user equipment 104 and the eNodeB 106. Both signaling and traffic in the system 100 are carried by physical layer ("PHY") channels.

[0053] Multiple eNodeBs 106 may be interconnected with each other using X2 interfaces 130(a, b, c). As shown in FIG. 1b, X2 interface 130a provides interconnection between eNodeB 106a and eNodeB 106b, X2 interface 130b provides interconnection between eNodeB 106a and eNodeB 106c, and X2 interface 130c provides interconnection between eNodeB 106b and eNodeB 106c. The X2 interfaces may be established between two eNodeBs to provide for the exchange of signals, which may include information related to loading or interference, as well as information related to handover. The eNodeBs 106 communicate with the evolved packet core 108 via S1 interfaces 124(a, b, c). The S1 interface 124 can be divided into two interfaces, one for the control plane (shown in FIG. 1c as control plane interface (S1-MME interface) 128) and the other for the user plane (shown in FIG. 1c as user plane interface (S1-U interface) 125).

[0054] The EPC 108 establishes and enforces quality of service ("QoS") for user services and allows the user equipment 104 to maintain a consistent Internet Protocol ("IP") address while moving. Note that each node in the network 100 has its own IP address. The EPC 108 is designed to interwork with legacy wireless networks. The EPC 108 is also designed to separate the control plane (i.e., signaling) and user plane (i.e., traffic) in the core network architecture, which allows for more flexibility in implementation and independent scalability of control and user data functions.

[0055] The EPC 108 architecture is dedicated to packet data and is shown in more detail in Figure 1c. The EPC 108 includes a Serving Gateway (S-GW) 110, a PDN Gateway (P-GW) 112, a Mobility Management Entity ("MME") 114, a Home Subscriber Server ("HSS") 116 (a subscriber database for the EPC 108), and a Policy Control and Charging Rules Function ("PCRF") 118. Some of these (such as the S-GW, P-GW, MME, and HSS) are often combined into nodes according to manufacturer implementations.

[0056] The S-GW 110 functions as an IP packet data router and is the bearer path anchor for user equipment within the EPC 108. Thus, when a user equipment moves from one eNodeB 106 to another during mobility operation, the S-GW 110 remains the same, and the bearer path towards the EUTRAN 102 is switched to communicate with the new eNodeB 106 serving the user equipment 104. If the user equipment 104 moves to the domain of a different S-GW 110, the MME 114 will forward all of the user equipment's bearer path to the new S-GW. The S-GW 110 establishes a bearer path for the user equipment to one or more P-GWs 112. When downstream data is received for an idle user equipment, the S-GW 110 buffers the downstream packets and requests the MME 114 to identify and re-establish the bearer path to and through the EUTRAN 102.

[0057] The P-GW 112 is the gateway between the EPC 108 (and user equipment 104 and EUTRAN 102) and the PDN 101 (shown in FIG. 1a). The P-GW 112 acts as a router for user traffic and performs functions on behalf of the user equipment. These include IP address allocation for the user equipment, packet filtering of downstream user traffic to ensure that it is placed on the appropriate bearer path, and enforcement of downstream QoS, including data rate. Depending on the services a subscriber is using, there may be multiple user data bearer paths between the user equipment 104 and the P-GW 112. A subscriber may use services on PDNs served by different P-GWs, in which case the user equipment has at least one bearer path established to each P-GW 112. During handover of a user equipment from one eNodeB to another, if the S-GW 110 is also changing, the bearer path from the P-GW 112 is switched to the new S-GW.

[0058] The MME 114 manages user equipment 104 within the EPC 108, including managing subscriber authentication, maintaining context for authenticated user equipment 104, establishing a data bearer path within the network for user traffic, and tracking the location of idle mobiles that have not detached from the network. In the case of an idle user equipment 104 that needs to reconnect to the access network to receive downstream data, the MME 114 initiates paging to locate the user equipment and reestablishes a bearer path to and through the EUTRAN 102. The MME 114 for a particular user equipment 104 is selected by the eNodeB 106 through which the user equipment 104 initiates system access. The MME is typically part of a collection of MMEs within the EPC 108 for load sharing and redundancy purposes. In establishing a user's data bearer path, the MME 114 is responsible for selecting the P-GW 112 and S-GW 110 that constitute the termination of the data path through the EPC 108.

[0059] The PCRF 118 is responsible for controlling policy control decision-making and flow-based charging functionality within the Policy Control Enforcement Function ("PCEF") residing within the P-GW 110. The PCRF 118 provides QoS authorization (QoS Class Identifier ("QCI") and bit rate), which determines how a data flow is treated within the PCEF and ensures that this is in accordance with the user's subscription profile.

[0060] As mentioned above, IP services 119 are provided by PDN 101 (as shown in FIG. 1a).

[0061] 1d shows an example structure of an eNodeB 106. The eNodeB 106 may include at least one remote radio head (“RRH”) 132 (typically, there may be three RRHs 132) and a baseband unit (“BBU”) 134. The RRHs 132 may be connected to an antenna 136. The RRHs 132 and BBU 134 may be connected using an optical interface that conforms to the Common Public Radio Interface (“CPRI”) / enhanced CPRI (“eCPRI”) 142 standard specification, either using RRH-specific custom control and user plane framing methods or using O-RAN Alliance compliant control and user plane framing methods. The operation of the eNodeB 106 can be characterized using the following standard parameters (and specifications): radio frequency band (Band 4, Band 9, Band 17, etc.), bandwidth (5, 10, 15, 20 MHz), access method (downlink: OFDMA, uplink: SC-OFDMA), antenna technology (single-user and multi-user MIMO, uplink: single-user and multi-user MIMO), number of sectors (up to 6), maximum transmission rate (downlink: 150 Mb / s, uplink: 50 Mb / s), S1 / X2 interface (1000Base-SX, 1000Base-T), and mobile environment (up to 350 km / h). The BBU 134 can be responsible for digital baseband signal processing, S1 line termination, X2 line termination, call processing, and monitoring and control processing. IP packets received from the EPC 108 (not shown in FIG. 1d) can be modulated into digital baseband signals and transmitted to the RRH 132. Conversely, digital baseband signals received from the RRH 132 may be demodulated into IP packets for transmission to the EPC 108.

[0062] The RRH 132 can transmit and receive wireless signals using the antenna 136. The RRH 132 can convert (using a converter (“CONV”) 140) digital baseband signals from the BBU 134 to radio frequency (“RF”) signals and power amplify them (using an amplifier (“AMP”) 138) for transmission to the user equipment 104 (not shown in FIG. 1d). Conversely, RF signals received from the user equipment 104 are amplified (using AMP 138) and converted (using CONV 140) to digital baseband signals for transmission to the BBU 134.

[0063] Figure 2 shows additional details of an exemplary eNodeB 106. The eNodeB 106 includes multiple layers: LTE Layer 1 202, LTE Layer 2 204, and LTE Layer 3 206. LTE Layer 1 includes the physical layer ("PHY"). LTE Layer 2 includes medium access control ("MAC"), radio link control ("RLC"), and packet data convergence protocol ("PDCP"). LTE Layer 3 includes various functions and protocols, including radio resource control ("RRC"), dynamic resource allocation, eNodeB measurement configuration and provisioning, radio admission control, connection mobility control, and radio resource management ("RRM"). The RLC protocol is an automatic repeat request ("ARQ") fragmentation protocol used over the cellular air interface. The RRC protocol handles LTE Layer 3 control plane signaling between user equipment and the EUTRAN. The RRC includes functions for connection establishment and release, system information broadcast, radio bearer establishment / reconfiguration and release, RRC connection mobility procedures, paging notification and release, and outer loop power control. The PDCP performs IP header compression and decompression, user data transfer, and radio bearer sequence number maintenance. The BBU 134 shown in FIG. 1d may include LTE layers L1-L3.

[0064] One of the primary functions of the eNodeB 106 is radio resource management, including scheduling of both uplink and downlink air interface resources for the user equipment 104, control of bearer resources, and admission control. As an agent for the EPC 108, the eNodeB 106 is responsible for forwarding paging messages used to locate a mobile when it is idle. The eNodeB 106 also communicates common control channel information over the air, performs header compression, encryption and decryption of user data sent over the air, and establishes handover reporting and trigger criteria. As mentioned above, the eNodeB 106 can cooperate with other eNodeBs 106 via the X2 interface for handover and interference management purposes. The eNodeB 106 communicates with the MME of the EPC via the S1-MME interface and with the S-GW using the S1-U interface. Additionally, the eNodeB 106 exchanges user data with the S-GW via the S1-U interface. The eNodeBs 106 and the EPC 108 have a many-to-many relationship to support load sharing and redundancy between MMEs and S-GWs. The eNodeB 106 selects an MME from a group of MMEs so that the load can be shared by multiple MMEs to avoid congestion. II. 5G NR wireless communication network

[0065] In some implementations, the present subject matter relates to 5G New Radio ("NR") communication systems. 5G NR is the next communication standard beyond the 4G / IMT-Advanced standard. 5G networks offer higher capacity than current 4G, allowing for a larger number of mobile broadband users per unit area, and allowing for consumption of more and / or unlimited data amounts in gigabytes per month and per user. This may allow users to stream high-definition media for many hours per day using their mobile devices, even when Wi-Fi networks do not allow for this. 5G networks have improved support for device-to-device communications, lower costs, lower latency and lower battery consumption than 4G equipment, etc. Such a network would have data rates of tens of megabits per second for many users, data rates of 100 Mb / s for metropolitan areas, 1 Gb / s simultaneously to users within a limited area (e.g., an office floor), many simultaneous connections for wireless sensor networks, increased spectral efficiency, improved coverage, increased signaling efficiency, 1-10 ms latency, and reduced latency compared to existing systems.

[0066] 3 illustrates an exemplary virtual radio access network 300. The network 300 can provide communication between various components, including a base station (e.g., eNodeB, gNodeB) 301, radio equipment 303, a centralized unit 302, a digital unit 304, and a wireless device 306. The components in the system 300 can be communicatively coupled to a core using a backhaul link 305. The centralized unit ("CU") 302 can be communicatively coupled to a distributed unit ("DU") 304 using a midhaul connection 308. The radio frequency ("RU") component 306 can be communicatively coupled to the DU 304 using a fronthaul connection 310.

[0067] In some implementations, the CU 302 can provide intelligent communication capabilities to one or more DU units 304. The units 302, 304 can include one or more base stations, macro base stations, micro base stations, remote radio heads, etc., and / or any combination thereof.

[0068] In a lower layer split architecture environment, the CPRI bandwidth requirement for NR can be several hundred Gb / s. CPRI compression can be implemented in the DU and RU (as shown in Figure 3). In 5G communication systems, compressed CPRI over Ethernet frames is referred to as eCPRI and is the recommended fronthaul network. This architecture can enable standardization of fronthaul / midhaul, which can include upper layer splitting (e.g., Option 2 or Option 3-1 (upper / lower RLC split architecture)) and fronthaul using an L1 split architecture (Option 7).

[0069] In some implementations, a lower layer split architecture (e.g., Option 7) may include receiver in the uplink and joint processing across multiple transmission points (TPs) for both DL / UL and transport bandwidth and latency requirements to facilitate deployment. Additionally, the subject lower layer split architecture may include splitting between cell-level processing and user-level processing, which may include cell-level processing in a remote unit ("RU") and user-level processing in a DU. Additionally, using the subject lower layer split architecture, frequency-domain samples may be transported over the Ethernet fronthaul, and the frequency-domain samples may be compressed for reduced fronthaul bandwidth.

[0070] 4 illustrates an example communication system 400 that can implement 5G technology and provide its users with access to higher frequency bands (e.g., greater than 10 GHz). The system 400 can include a macro cell 402 and small cells 404, 406.

[0071] The mobile device 408 may be configured to communicate with one or more of the small cells 404, 406. The system 400 may enable splitting of the control plane (C-plane) and user plane (U-plane) between the macrocell 402 and the small cells 404, 406, with the C-plane and U-plane utilizing different frequency bands. Specifically, the small cells 404, 406 may be configured to utilize higher frequency bands when communicating with the mobile device 408. The macrocell 402 may utilize existing cellular bands for C-plane communications. The mobile device 408 may be communicatively coupled via the U-plane 412, where the small cell (e.g., the small cell 406) may provide higher data rates and more flexible / cost / energy-efficient operation. The macrocell 402 may maintain good connectivity and mobility via the C-plane 410. Furthermore, in some cases, LTE and NR may be transmitted on the same frequency.

[0072] 5a illustrates an exemplary 5G wireless communication system 500 according to some implementations of the present subject matter. The system 500 may be configured to have a lower layer split architecture according to Option 7-2. The system 500 may include a core network 502 (e.g., 5G Core) and one or more gNodeBs (or gNBs), where the gNBs may have a centralized unit gNB-CU. The gNB-CU may be logically divided into a control plane portion gNB-CU-CP 504 and one or more user plane portions gNB-CU-UP 506. The control plane portion 504 and the user plane portion 506 may be configured to be communicatively coupled using an E1 communication interface 514 (as defined in the 3GPP standard). The control plane portion 504 may be configured to be responsible for executing the RRC and PDCP protocols of the radio stack.

[0073] The control plane portion 504 and user plane portion 506 of the centralized unit of the gNB may be configured to be communicatively coupled to one or more distributed units (DUs) 508, 510 according to an upper layer split architecture. The distributed units 508, 510 may be configured to execute upper portions of the RLC, MAC, and PHY layer protocols of the radio stack. The control plane portion 504 may be configured to be communicatively coupled to the distributed units 508, 510 using an F1-C communication interface 516, and the user plane portion 506 may be configured to be communicatively coupled to the distributed units 508, 510 using an F1-U communication interface 518. The distributed units 508, 510 may be coupled to one or more remote radio units (RUs) 512 via a fronthaul network 520 (which may include one or more switches, links, etc.), which in turn communicate with one or more user equipment (not shown in FIG. 5a). The remote radio unit 512 may be configured to execute lower portions of the PHY layer protocol and provide antenna capabilities to the remote unit for communication with user equipment (similar to the description above in connection with Figures 1a-2).

[0074] Figure 5b shows an example layer architecture 530 for a split gNB. The architecture 530 can be implemented within the communication system 500 shown in Figure 5a, which can be configured as a virtualized disaggregated radio access network (RAN) architecture, whereby layers L1, L2, L3 and radio processing can be virtualized and disaggregated within centralized, distributed, and radio units. As shown in Figure 5b, the gNB-DU 508 can be communicatively coupled to the gNB-CU-CP control plane portion 504 (also shown in Figure 5a) and the gNB-CU-UP user plane portion 506. Each of the components 504, 506, 508 can be configured to include one or more layers.

[0075] The gNB-DU 508 may include RLC, MAC, and PHY layers, as well as various communication sublayers. These may include an F1-Application Protocol (F1-AP) sublayer, a GPRS Tunneling Protocol (GTPU) sublayer, a Stream Control Transmission Protocol (SCTP) sublayer, a User Datagram Protocol (UDP) sublayer, and an Internet Protocol (IP) sublayer. As described above, the distributed unit 508 may be communicatively coupled to the control plane portion 504 of the centralized unit, which may also include the F1-AP, SCTP, and IP sublayers, as well as the Radio Resource Control and PDCP Control (PDCP-C) sublayer. Furthermore, the distributed unit 508 may also be communicatively coupled to the user plane portion 506 of the centralized unit of the gNB. The user plane portion 506 may include a Service Data Adaptation Protocol (SDAP), a PDCP User (PDCP-U), a GTPU, a UDP, and an IP sublayer.

[0076] Figure 5c shows an example functional division in the gNB architecture shown in Figures 5a-5b. As shown in Figure 5c, the gNB-DU 508 may be communicatively coupled to the gNB-CU-CP 504 and the gNB-CU-UP 506 using an F1-C communication interface. The gNB-CU-CP 504 and the gNB-CU-UP 506 may be communicatively coupled using an E1 communication interface. An upper portion of the PHY layer (or Layer 1) may be performed by the gNB-DU 508, and a lower portion of the PHY layer may be performed by the RU (not shown in Figure 5c). As shown in Figure 5c, the RRC and PDCP-C portions may be performed by the control plane portion 504, and the SDAP and PDCP-U portions may be performed by the user plane portion 506.

[0077] Some of the functions of the PHY layer in a 5G communication network may include error detection on transport channels and indication to higher layers, FEC encoding / decoding of transport channels, hybrid ARQ soft combining, rate matching of coded transport channels to physical channels, mapping of coded transport channels to physical channels, power weighting of physical channels, modulation and demodulation of physical channels, frequency and time synchronization, radio characteristic measurements and indication to higher layers, MIMO antenna processing, digital and analog beamforming, RF processing, and other functions.

[0078] The MAC sublayer of Layer 2 may perform beam management, random access procedures, mapping between logical channels and transport channels, concatenation of multiple MAC service data units (SDUs) belonging to one logical channel into transport blocks (TBs), multiplexing / demultiplexing of SDUs belonging to logical channels to / from TBs passed to / from the physical layer on transport channels, scheduling information reporting, error correction using HARQ, priority handling between logical channels for one UE, priority handling between UEs using dynamic scheduling, transport format selection, and other functions. The RLC sublayer's functions may include forwarding upper layer packet data units (PDUs), error correction using ARQ, reordering of data PDUs, duplication and protocol error detection, reestablishment, etc. The PDCP sublayer may be responsible for forwarding user data, various functions during reestablishment procedures, retransmission of SDUs, discarding SDUs in the uplink, forwarding of control plane data, etc.

[0079] The RRC sublayer of Layer 3 may perform the following functions: broadcasting system information to the NAS and AS, establishing, maintaining, and releasing RRC connections, security, establishing, configuring, maintaining, and releasing point-to-point radio bearers, mobility functions, reporting, and other functions. III. Supporting Multiple Radio Units on a Single Distributed Unit

[0080] In some implementations of the present subject matter, a DU in an open RAN can be configured to support multiple RUs in the open RAN. The DU can include multiple carriers, each of which can have a configuration customized to a particular one of the RUs. Thus, the DU may be able to support multiple RUs, even though one or more of the RUs may have different fronthaul message requirements than one or more of the other RUs.

[0081] FIG. 6 illustrates an example system 600 configured to enable support of multiple RUs on a single DU. The system 600 includes a base station 624, e.g., an eNodeB configured in an LTE wireless communication system (e.g., eNB 106 in FIGS. 1b-2, eNB 301 in FIG. 3, etc.), a gNodeB configured in a 5G wireless communication system (e.g., gNB in ​​FIG. 5a, etc.), a base station configured in a 6G or later generation wireless communication system, etc. In the illustrated implementation of FIG. 6, the system 600 implements an open RAN architecture. Accordingly, the base station 624 includes an O-RAN compliant CU (O-CU or OCU) 615 that includes an O-RAN compliant CU-CP (O-CU-CP or OCUCP) 604 and an O-RAN compliant CU-UP (O-CU-UP or OCUCP) 606. The O-CU-CP 604 is configured to be communicatively coupled to the O-CU-UP 606 using an E1 communication interface 614. The O-CU 615 is configured to be communicatively coupled to a core network (not shown in FIG. 6), such as the EPC 108 of FIGS. 1a-1c and 2, or the 5GC 502 of FIG. 5a.

[0082] The base station 624 also includes multiple O-RAN compliant DUs (O-DUs or ODUs) 608, 610. The base station 624 includes two O-DUs 608, 610 in this illustrated implementation, but may include multiple other O-DUs. The O-CU-CP 604 is configured to be communicatively coupled to the O-DUs 608, 610 using an F1-C communication interface 616. The O-CU-UP 606 is configured to be communicatively coupled to the O-DUs 608, 610 using an F1-U communication interface 618. Each of the O-DUs 608, 610 is configured to support two or more O-RUs 612, as described herein. In other implementations, not all of the O-DUs of a base station may be configured to support two or more O-RUs.

[0083] The base station 624 also includes multiple O-RAN-compliant RUs (O-RUs or ORUs) 612 a, 612 b, 612 c, 612 d, and 612 e, collectively referred to as O-RUs 612. The base station 624 includes five O-RUs 612 in this illustrated implementation, but may include multiple other O-RUs 612. The O-RUs 612 are configured to be communicatively coupled to the O-DUs 608, 610 via a fronthaul network 620. Furthermore, each of the O-RUs 612 is configured to be communicatively coupled to one or more UEs 622. In this illustrated implementation, the first and fourth RUs of RUs 612a, 612d are shown communicatively coupled to one UE 622, the second and fifth RUs of O-RUs 612b, 612e are shown communicatively coupled to two UEs 622, and the second RU of O-RU 612b is shown communicatively coupled to three UEs 622. However, each of the O-RUs 612 may be coupled to another number of UEs, the same or different from any of the other O-RUs 612.

[0084] Examples of UEs that may be used as any one or more of the UEs 622 include a mobile phone, a smartphone, a tablet, a personal computer, a PDA, a server, a data terminal, a Session Initiation Protocol (SIP) phone, a satellite radio, a Global Positioning System (GPS), a multimedia device, a video device, a digital audio player (e.g., an MP3 player, etc.), a camera, a game console, a smart device (which may be wearable or non-wearable), a vehicle, an electric meter, a gas pump, a large or small kitchen appliance, a healthcare device, an implant, a sensor / actuator, a display, and / or any other type of user equipment, and / or any combination thereof. One or more of the UEs 622 may be referred to as an Internet of Things device (e.g., a parking meter, a gas pump, a toaster, a vehicle, a heart monitor, etc.).

[0085] 6 includes standalone DUs 608, 610 and a standalone CU 615. However, another implementation of a system configured to enable support of multiple RUs on a single DU may include a combined DU-CU such that multiple RUs may be supported on the combined DU-CU.

[0086] The O-RAN Alliance standard specifies at least four planes: the user plane (U-plane), the control plane (C-plane), the synchronization plane (S-plane), and the management plane (M-plane). C-plane messages may contain data-related control information (e.g., scheduling commands and beamforming commands) required for processing user data. C-plane messages may be sent separately for downlink (DL) and uplink (UL) related commands.

[0087] To support C-plane and U-plane timing coordination, the O-RAN interface may specify that a C-plane or U-plane message must arrive at the O-RU by the time that the C-plane or U-plane message falls into its respective window.

[0088] The U-plane O-DU transmission window may be defined by the above relationship based on the O-RU receive window and the maximum transport variation. In some implementations, this transmission window may not define the exact timing of transmissions from the O-DU to the O-RU, but instead define the boundaries within which the U-plane O-DU transmission operates. The transmission window may represent a mathematical boundary imposed on the O-DU as a result of O-RU, fronthaul delay, and transport constraints. Constraints may be defined for any one of the O-DU, transport, and O-RU based on knowledge of the other two. However, O-RU constraints may be predefined based on equipment, transport, and overall network goals.

[0089] The C-plane O-DU transmission window may follow the same concept as the U-plane O-DU transmission window. However, the C-plane O-DU transmission window may be larger in size and therefore may start much earlier in time than the U-plane O-DU transmission window. In certain scenarios, such as transmitting beamforming (BF) weights in real time for MIMO applications, C-plane messages may be distributed over time to avoid peak throughput. FIG. 7 shows a chart 700 illustrating an example of fronthaul (FH) throughput 702 where C-plane messages are transmitted at once in the same symbol unit and an example of FH throughput 704 where C-plane messages are distributed over time. As shown in FIG. 7, when C-plane messages are distributed over time (example 704), the FH throughput decreases compared to transmitting C-plane messages at once in the same symbol unit (example 702).

[0090] 8A and 8B show implementations of a transmission time window between an O-RU (e.g., the O-RU 612 in FIG. 6 ) and an O-DU (e.g., the O-DUs 608, 610 in FIG. 6 ). As shown in the implementations of FIGS. 8A and 8B , the transmission time window has a length of T1aMax. The transmission time window includes a transmission time interval (TTI) 810. The transmission time window also includes an FH processing interval 820, which represents the time for data (e.g., packets) to travel from the O-DU to the O-RU through the FH network. The transmission time window also includes an O-RU processing time T1aMin 830, which represents the time for processing data received at the O-RU from the O-DU. Upon expiration of the time T1aMin 830, the O-RU may transmit the received data via a wireless communication network including the O-RU and the O-DU. For example, at the expiration of time T1aMin 830, the O-RU may transmit data to one or more UEs (e.g., UE 622 in FIG. 6) via a wireless communication network. Thus, if the O-DU transmits a U-plane or C-plane packet at a time such that the O-RU cannot process the received packet within O-RU processing time T1aMin 830, the O-RU cannot transmit the packet at a time that complies with the O-RAN standard.

[0091] The present subject matter describes various implementations for supporting multiple RUs on a single DU. Figure 9 shows an example method 900 for supporting multiple RUs on a single DU according to some implementations of the present subject matter. As shown in Figure 9, each of the RUs may be an ORU (e.g., O-RU 612 in Figure 6, etc.), and the DUs may be ODUs (e.g., O-DUs 608, 610 in Figure 6, etc.).

[0092] The method 900 includes performing 902 an initial handshake between an ODU and an ORU in accordance with O-RAN and 3GPP standards, where the ODU receives an identifier from the ORU that identifies the ORU. Examples of the identifier include a serial number, a model number, an identification code assigned to the ORU by a vendor of the ORU, and other types of identifiers.

[0093] Upon receiving the identifier identifying the ORU, the ODU looks up communication information based on the identifier 904. A memory in the ODU or otherwise accessible to the ODU can store correlation information correlating communication information with each of multiple identifiers identifying different ORUs. Thus, by looking up the ORU's identifier in the correlation information 904, the ODU can identify communication information associated with that particular ORU. The communication information for any one ORU may be different or the same as any of the other ORUs. At least some of the ORUs typically have communication information that is different from at least some of the other ORUs. The communication information may include profile information for the ORU according to O-RAN and 3GPP. Examples of profile information include, for example, an interoperability (IOT) profile, an extended antenna carrier identifier (eAxC_ID) profile, and a predefined beamforming profile.

[0094] The ODU also determines, for each carrier, communication characteristics for data transmission to the ORUs for which it has received identifiers 906. The communication characteristics may include data to be transmitted from the ODU to the ORU and / or may define parameters of communication from the ODU to the ORU. Examples of communication characteristics include a delay window (e.g., a transmission time window) for data transmission, a DU PORT ID (which may be modified as described below), and beamforming weights.

[0095] Upon determining 908 the communication characteristics, the ODU transmits 908 the data to the ORU according to the communication characteristics.

[0096] Method 900 can be performed with respect to a single ODU and multiple ORUs. Thus, a single ODU can be configured to support multiple ORUs, each with its own communication information and associated communication characteristics. Thus, a carrier in the ODU can communicate with a particular one of the ORUs according to the communication parameters of that particular ORU, even if those communication parameters differ from one or more other ORUs.

[0097] An example implementation of the method 900 of FIG. 9 is described below with respect to FIGS.

[0098] In some implementations, supporting multiple RUs on a single DU may include supporting multiple Fronthaul Interoperability (IOT) profiles on a single DU, where one or more of the multiple Fronthaul IOT profiles may be the same as or distinct from any of the other Fronthaul IOT profiles.

[0099]

[0013] Figure 10 illustrates an example method 1000 for supporting multiple fronthaul IOT profiles on a single DU in accordance with some implementations of the present subject matter. The method 1000 of Figure 10 is described with respect to the example system 1100 shown in Figure 11, but may be implemented in other systems as well.

[0100] The system 1100 of FIG. 11 includes an ODU (e.g., ODU 608 of FIG. 6 , ODU 610 of FIG. 6 , etc.) and multiple RUs 1102, 1104 (e.g., ORU 612 of FIG. 6 ). Although a first RU 1102 and a second RU 1104 are shown in FIG. 11 (labeled “ORU A” and “ORU B,” respectively, in FIG. 11 ), the system 1100 may include multiple other ORUs, each configured to communicate with the ODU. The ODU in this illustrated implementation includes three carriers: a first carrier 1106 (labeled “Carrier 0” in FIG. 11 ), a second carrier 1108 (labeled “Carrier 1” in FIG. 11 ), and a third carrier 1110 (labeled “Carrier 2” in FIG. 11 ). However, the ODU may include a different number of carriers, each configured to communicate with one or more ORUs.

[0101] The system 1100 can be implemented in another wireless communication system, such as a 5G wireless communication system, an LTE wireless communication system, or a 6G or later generation wireless communication system.

[0102] The method 1000 includes performing 1002 an initial handshake between the ODU and each of the ORUs 1102, 1104 in accordance with O-RAN and 3GPP standards. This performing 1002 of the initial handshake corresponds to performing 902 in Figure 9. In the initial handshake process, the ODU receives a first identifier from the first ORU 1102 that identifies the first ORU 1102, and the ODU receives a second identifier from the second ORU 1102 that identifies the second ORU 1104. As shown in Figure 11, an initial handshake is performed between a first carrier 1106 of the ODU and the first ORU 1102, an initial handshake is performed between a second carrier 1108 of the ODU and the first ORU 1102, and an initial handshake is performed between a third carrier 1110 of the ODU and the second ORU 1104.

[0103] Upon receiving the identifier identifying the ORU, the ODU looks up communication information based on the identifier 1004. This lookup 1004 corresponds to lookup 904 in Figure 9. As shown in Figures 10 and 11, the communication information in this implementation includes an IOT profile. Thus, the ODU can look up the IOT profile of the first RU 1102 based on the first identifier 1004 and the IOT profile of the second RU 1104 based on the second identifier 1004.

[0104] Similar to that described above with respect to FIG. 9, a memory at or otherwise accessible to the ODU can store correlation information correlating each of a plurality of IOT profiles with each of a plurality of identifiers that identify different ORUs, including the first RU 1102 and the second RU 1104. The IOT profiles are, for example, profiles defined per O-RAN. Thus, by looking up 1004 the identifier of the first ORU in the correlation information, the ODU can identify the IOT profile associated with the first RU 1102, and by looking up 1004 the identifier of the second ORU in the correlation information, the ODU can identify the IOT profile associated with the second RU 1104. Although FIG. 11 illustrates the correlation information as an XML file, the correlation information may be in other formats.

[0105] As shown in Figure 11, by looking up the IOT profile of the ORU based on the identifier of the ORU 1004, the ODU can identify the eAxC_ID profile of the ORU, which is, for example, a profile defined per O-RAN.

[0106] The lookup 1004 can be performed at Layer 3 of the ODU according to Layer 3's standardized capabilities. Thus, the IOT profile retrieved for a particular ORU can be transmitted 1006 from Layer 3 of the ODU to Layer 1 of the ODU. Because there are three carriers 1106, 1108, 1110 in this illustrated implementation, FIG. 11 shows three arrows for transmission 1006 to Layer 1 (labeled L1-SW in FIG. 11 to reflect that the ODU's Layer 1 (L1) software (SW) is processing the data). As also shown in FIG. 11, each of the IOT profiles can be associated with its associated carrier 1106, 1108, 1110 using an absolute carrier identifier (ID), for example, "0" for carrier 0 1106, "1" for carrier 1 1108, and "2" for carrier 2 1110.

[0107] Upon receiving the IOT profile for a particular ORU, the ODU, e.g., its Layer 1, determines 1008 the downlink (DL) and uplink (UL) transmission time windows for the associated carrier, e.g., as indicated by the absolute carrier ID. This determining 1008 corresponds to determining communication characteristics 906 in Figure 9. Thus, the ODU can determine 1008 the DL and UL transmission time windows that a particular carrier should use for a particular ORU. Thus, the ODU can support different transmission time windows for different ORUs. As described above and shown in FIG. 11, the downlink (DL) and uplink (UL) transmission time windows for a particular carrier and a particular ORU may include T1_max_cp_dl / ul, which represents the window start (in terms of symbol duration) for C-plane data in the downlink / uplink direction based on an over-the-air (OTA) boundary; T1_min_cp_dl / ul, which represents the window end (in terms of symbol duration) for C-plane data in the downlink / uplink direction based on the OTA boundary; T1_max_up_dl, which represents the window start (in terms of symbol duration) for U-plane data in the downlink direction based on the OTA boundary; and T1_min_up_dl, which represents the window end (in terms of symbol duration) for U-plane data in the downlink direction based on the OTA boundary.

[0108] 11, determining 1008 may include looking up the DL and UL transmission time windows in a lookup table that associates DL and UL transmission time windows with eAxC_ID profiles. The lookup table may be stored in a memory at or otherwise accessible to the ODU. An ODU, e.g., its L1, may look up the eAxC_ID profile of a particular ORU and identify its associated DL and UL transmission time windows.

[0109] Once a particular carrier has determined 1008 the DL and UL transmission time windows to be used for a particular ORU, the ODU may perform C-plane and U-plane transmissions with that particular ORU via the FH network (labeled "FH link" in FIG. 11), for example, via that particular carrier 1010.

[0110] 11 should not be interpreted to indicate that all initial handshakes occur at the same time, that all IOT profiles are looked up at the same time 1004, that all IOT profiles are sent to Layer 1 at the same time 1006, or that all decisions 1008 are made at the same time. Instead, the timing of the initial handshake, which may be triggered according to 3GPP and O-RAN when a carrier is activated, including a particular carrier and a particular ORU, determines when subsequent portions of method 1000 are performed.

[0111] In some implementations, supporting multiple RUs on a single DU may include supporting multiple carriers on a single DU.

[0112]

[0013] Figure 12 illustrates an example method 1200 for supporting multiple carriers on a single DU in accordance with some implementations of the present subject matter. The method 1200 of Figure 12 is described with respect to an example system 1300 shown in Figure 13, but may be implemented in other systems as well.

[0113] The system 1300 of FIG. 13 includes an ODU (e.g., the ODU 608 of FIG. 6 , the ODU 610 of FIG. 6 , etc.) and multiple RUs 1302, 1304 (e.g., the ORU 612 of FIG. 6 ). While a first RU 1302 and a second RU 1304 are shown in FIG. 13 (labeled “ORU A” and “ORU B,” respectively, in FIG. 13 ), the system 1300 may include multiple other ORUs, each configured to communicate with the ODU. The ODU in this illustrated implementation includes three carriers: a first carrier 1306 (labeled “Carrier 0” in FIG. 13 ), a second carrier 1308 (labeled “Carrier 1” in FIG. 13 ), and a third carrier 1310 (labeled “Carrier 2” in FIG. 13 ). However, the ODU may include a different number of carriers, each configured to communicate with one or more ORUs.

[0114] The system 1300 can be implemented in another wireless communication system, such as a 5G wireless communication system, an LTE wireless communication system, or a 6G or later generation wireless communication system.

[0115] The method 1200 includes performing 1202 an initial handshake between the ODU and each of the ORUs 1302, 1304, the ODU looking up communication information based on the identifier 1204, and transmitting 1206 the communication information from Layer 3 of the ODU to Layer 1 of the ODU. Performing 1202, looking up 1204, and transmitting 1206 of FIG. 12 correspond to performing 1002, looking up 1004, and transmitting 1006 of FIG. 10, and therefore will not be specifically described again. Thus, as described above with respect to FIG. 10 and shown in FIG. 13, the communication information in the illustrated implementation of FIG. 12 includes an IOT profile. Furthermore, as described above and shown in FIG. 13, looking up the IOT profile of the ORU based on the identifier of the ORU enables the ODU to identify the eAxC_ID profile of the ORU.

[0116] Upon receiving an IOT profile for a particular carrier, ODU, e.g., a particular ORU associated with its Layer 1, the ODU is receiving a distributed unit identifier ("DU PORT ID" or "DU_Port_ID") since the eAxC_ID profile is defined to include a DU PORT ID field. As noted above, an IOT profile is associated with a particular carrier with an absolute carrier ID, e.g., "0" for carrier 0 1306, "1" for carrier 1 1308, and "2" for carrier 2 1310.

[0117] The method 1200 includes the ODU, e.g., Layer 1 thereof, modifying 1208 the DU PORT ID to account for the particular carrier. This modifying 1208 corresponds to determining communication characteristics 906 in Figure 9. As shown in Figure 13, modifying 1208 the DU PORT ID may include modifying the DU PORT ID to be the absolute carrier ID of the particular carrier, such as by replacing the value of the DU PORT ID with the value of the absolute carrier ID. Because the ORU does not operate or modify the DU PORT ID field per 3GPP and O-RAN, the DU PORT ID can be modified and transmitted as modified to the ORU without affecting the proper functioning of the ORU.

[0118] Once the DU PORT ID is modified 1208, the ODU can perform C-plane and U-plane transmission with that particular ORU via the FH network (labeled "FH link" in Figure 13) 1210. As shown in Figure 13, the UL and DL C-plane data and DL U-plane data can be tagged with the modified DU PORT ID. Thus, from the modified DU PORT ID, the ODU can recognize the particular carrier among carriers 1300, 1302, 1304 associated with a particular transmission. For UL U-plane data, as also shown in Figure 13, the ORU loops back the modified DU PORT ID from the C-plane data received from the ODU to the U-plane data to be transmitted to the ORU in the uplink direction. Thus, the ODU can receive the modified DU PORT ID with the U-plane data transmitted from the ORU to the ODU, thereby identifying the appropriate carrier for the ODU.

[0119] 13 should not be interpreted to indicate that all initial handshakes occur simultaneously, that all IOT profiles are looked up simultaneously 1204, that all IOT profiles are sent to Layer 1 simultaneously 1206, or that all modifications 1208 are performed simultaneously. Instead, the timing of the initial handshake, which may be triggered according to 3GPP and O-RAN when a carrier is activated, including a particular carrier and a particular ORU, determines when subsequent portions of method 1200 are performed.

[0120] In some implementations, supporting multiple RUs on a single DU may include supporting multiple beamforming profiles for a single or multiple massive MIMO RUs.

[0121] 14 illustrates an example method 1400 for supporting multiple beamforming profiles for a single or multiple Massive MIMO RUs in accordance with some implementations of the present subject matter. The method 1400 of FIG. 14 is described with respect to the example system 1500 shown in FIG. 15, but may be implemented in other systems as well.

[0122] The system 1500 of FIG. 15 includes an ODU (e.g., the ODU 608 of FIG. 6 , the ODU 610 of FIG. 6 , etc.) and multiple RUs 1502, 1504 (e.g., the ORU 612 of FIG. 6 ). Although a first RU 1502 and a second RU 1504 are shown in FIG. 15 (labeled “ORU A” and “ORU B,” respectively, in FIG. 15 ), the system 1500 may include multiple other ORUs, each configured to communicate with the ODU. The ODU in this illustrated implementation includes three carriers: a first carrier 1506 (labeled “Carrier 0” in FIG. 15 ), a second carrier 1508 (labeled “Carrier 1” in FIG. 15 ), and a third carrier 1510 (labeled “Carrier 2” in FIG. 15 ). However, the ODU may include a different number of carriers, each configured to communicate with one or more ORUs.

[0123] The system 1500 can be implemented in another wireless communication system, such as a 5G wireless communication system, an LTE wireless communication system, or a 6G or later generation wireless communication system.

[0124] The method 1400 includes performing 1402 an initial handshake between the ODU and each of the ORUs 1502, 1504. Performing 1402 in Figure 14 corresponds to performing 1002 in Figure 10, and therefore will not be described in detail again.

[0125] Upon receiving the identifier identifying the ORU, the ODU forms 1404 a beam profile based on the identifier and assigns a deployment ID. This forming 1404 corresponds to the lookup 904 in Figure 9. As shown in Figures 14 and 15, the communication information in this implementation includes a beam profile. The beam profile includes beamforming weights.

[0126] Similar to that described above with respect to FIG. 9 , a memory in or otherwise accessible to the ODU can store correlation information correlating each of a plurality of predetermined beam profiles with each of a plurality of identifiers that identify different ORUs, including the first RU 1502 and the second RU 1504. The beam profiles are parameters defined per 3GPP, for example. Thus, by looking up the identifier of the first ORU in the correlation information, the ODU can identify the beam profile associated with the first RU 1502, and by looking up the identifier of the second ORU in the correlation information, the ODU can identify the beam profile associated with the second RU 1504. Thus, the ODU can look up the beam profile of the first RU 1502 based on the first identifier and can look up the beam profile of the second RU 1504 based on the second identifier.

[0127] As described above, the ODU assigns a deployment ID to a beam profile. As shown in Figure 15, the deployment ID may be an ORU vendor tag (radio vendor tag) that identifies the vendor of the ORU, for example, ORUMODEL_DEPLOYMENTID. Thus, the deployment ID may correspond to an identifier received from a particular ORU.

[0128] The formation of the beam profile 1404 and the assignment of deployment IDs may be performed at Layer 3 of the ODU according to the standardized capabilities of Layer 3. Thus, the beam profile and assigned deployment ID for a particular ORU may be transmitted 1406 from Layer 3 of the ODU to Layer 1 of the ODU. Because there are three carriers 1506, 1508, 1510 in this illustrated implementation, FIG. 15 shows three arrows for transmission to Layer 1 1406 (labeled L1-SW in FIG. 15 to reflect that the L1 SW of the ODU is processing the data).

[0129] Upon receiving the beam profile and assigned deployment ID of the particular ORU, the ODU, e.g., its Layer 1, determines 1408 beamforming weights for the particular ORU based on the beam profile and assigned deployment ID. This determining 1408 corresponds to determining communication characteristics 906 in Figure 9. Thus, the ODU can determine 1408 beamforming weights for the C-plane that the particular carrier should transmit to the particular ORU.

[0130] As shown in the illustrated implementation of FIG. 15 , determining 1408 may include looking up the deployment ID in a lookup table that associates deployment IDs with beamforming weights. The lookup table may be stored in a memory in the ODU or otherwise accessible to the ODU. The ODU, for example, its L1, may look up the deployment ID of a particular ORU and identify its associated beamforming weights. Because different vendors of ORUs may require different beamforming weights, the use of the deployment ID may enable selection of appropriate beamforming weights for a particular ORU among multi-vendor ORUs that may all be supported by the ODU. Also, different bandwidths and carrier frequencies may result in different beamforming weights being required for use with the same ORU model, allowing a single model of ORU to be used. It may also be possible to use a subset of beamforming weights depending on the deployment scenario, such as indoors or outdoors, a particular street, etc.

[0131] Upon determining the beamforming weights 1408, the ODU may transmit the beamforming weights to a particular ORU via the FH network (labeled "FH link" in FIG. 15) 1410. In some implementations, the beamforming weights may be transmitted to a particular ORU for several Tx antennas, several Rx antennas, and several beams.

[0132] 15 should not be interpreted to indicate that all initial handshakes occur simultaneously, that beam profiles are all formed 1404, that all deployment IDs are assigned simultaneously, that beam profiles and deployment IDs are all sent to Layer 1 simultaneously 1406, that beamforming weights are all determined simultaneously 1408, or that beamforming weights are sent simultaneously 1410 to all ORUs 1502, 1504. Instead, the timing of the initial handshake, which may be triggered according to 3GPP and O-RAN when a carrier is activated, including a particular carrier and a particular ORU, determines when subsequent portions of method 1400 are performed.

[0133] In some implementations, two or more of the methods 1000, 1200, 1400 may be performed within a system. In some implementations, only one of the methods 1000, 1200, 1400 may be performed within a system.

[0134] In some implementations, the present subject matter can be configured to be implemented in a system 1600, as shown in FIG. 16 . The system 1600 can include one or more of a processor 1610, a memory 1620, a storage device 1630, and an input / output device 1640. Each of the components 1610, 1620, 1630, and 1640 can be interconnected using a system bus 1650. The processor 1610 can be configured to process instructions for execution within the system 1600. In some implementations, the processor 1610 can be a single-threaded processor. In alternative implementations, the processor 1610 can be a multi-threaded processor. The processor 1610 can be further configured to process instructions stored in the memory 1620 or the storage device 1630, including receiving or sending information through the input / output device 1640. The memory 1620 can store information within the system 1600. In some implementations, the memory 1620 can be a computer-readable medium. In alternative implementations, memory 1620 may be a volatile memory unit. Further, in some implementations, memory 1620 may be a non-volatile memory unit. Storage device 1630 may be capable of providing mass storage to system 1600. In some implementations, storage device 1630 may be a computer-readable medium. In alternative implementations, storage device 1630 may be a floppy disk device, a hard disk device, an optical disk device, a tape device, a non-volatile solid-state memory, or any other type of storage device. Input / output device 1640 may be configured to provide input / output operations to system 1600. In some implementations, input / output device 1640 may include a keyboard and / or a pointing device. In alternative implementations, input / output device 1640 may include a display unit for displaying a graphical user interface.

[0135] 17 illustrates an example method 1700 for supporting multiple RUs on a single UE in accordance with some implementations of the present subject matter. Method 1700 can be implemented, for example, using the implementations shown in and described with respect to FIGS.

[0136] The method 1700 includes receiving, by a DU in the open wireless access network (e.g., ODU 608 of FIG. 6, ODU 610 of FIG. 6, ODU of FIG. 11, ODU of FIG. 13, ODU of FIG. 15, etc.), an identifier identifying the RU from an RU in the open wireless access network (e.g., RU 612a of FIG. 6, RU 612b of FIG. 6, RU 612c of FIG. 6, RU 612d of FIG. 6, RU 612e of FIG. 6, ORU A 1102 of FIG. 11, ORU B 1104 of FIG. 11, ORU A 1302 of FIG. 13, ORU B 1304 of FIG. 13, ORU A 1502 of FIG. 15, ORU B 1504 of FIG. 15, etc.). The method may also include: identifying, by the DU, communication information associated with the RU based on an identifier that identifies the RU; determining, by the DU, communication characteristics for transmitting data to the RU using a particular carrier of the DU (e.g., carrier 0 in Figure 11, Figure 13, or Figure 15; carrier 1 in Figure 11, Figure 13, or Figure 15; carrier 2 in Figure 11, Figure 13, or Figure 15, etc.); and transmitting data from the DU to the RU using the particular carrier according to the communication information and the communication characteristics.

[0137] In some implementations, the present subject matter can include one or more of the following optional features.

[0138] In some implementations, the communication information can include an IOT profile, and the communication characteristics can include a delay window for data transmission. Further, identifying can include looking up an identifier in a lookup table stored in at least one non-transitory storage medium, where the lookup table can uniquely associate each of a plurality of RU identifiers with the IOT profile, and / or the data can be transmitted over a fronthaul network and can include control plane (C-plane) data and user plane (U-plane) data. See, for example, Figures 10 and 11.

[0139] In some implementations, the communication information may include an extended antenna carrier identifier (eAxC_ID) including a DU PORT ID, and determining the communication characteristics may include modifying the DU PORT ID. Further, the data may be transmitted over a fronthaul network and may include U-plane data. Furthermore, the method may also further include transmitting the modified DU PORT ID on the U-plane from the DU to the RU, and the RU may be configured to loop the received modified DU PORT ID to the C-plane. See, for example, Figures 12 and 13.

[0140] In some implementations, identifying the communication information can include forming a beamforming profile and assigning a deployment ID to the RU, and the communication characteristics can include beamforming weights. Further, transmitting data can include transmitting beamforming weights from the DU to the RU, and / or determining the communication characteristics can include identifying which beamforming weights of a plurality of pre-defined beamforming weights correlate with the assigned deployment ID. See, for example, Figures 14 and 15.

[0141] In some implementations, the method may also include transmitting the identified communication information from Layer 3 of the DU to Layer 1 of the DU, where Layer 1 of the DU may perform the determining. See, for example, FIGS. 10 to 15.

[0142] In some implementations, the DU may receive the identifier from the RU during the initial handshake process between the DU and the RU, see, for example, Figures 10-15.

[0143] In some implementations, the DU may be a single DU, and the method may also include receiving, by the DU, from a second RU in the open radio access network, an identifier identifying the second RU, the method may also include identifying, by the DU, communication information associated with the second RU based on the identifier identifying the second RU, the method may also include determining, by the DU, communication characteristics related to data transmission to the second RU using a second particular carrier of the DU, and the method may also include transmitting data from the DU to the second RU using the second particular carrier according to the communication information associated with the second RU and the communication characteristics related to the data transmission to the second RU. See, for example, Figures 10 to 15.

[0144] In some implementations, a base station may include at least one processor and at least one non-transitory storage medium that stores instructions that, when executed by the at least one processor, cause the at least one processor to perform operations, and the base station may be configured to communicate in a wireless communication network, and the operations may include the method. Further, the base station may include an eNodeB or a gNodeB.

[0145] The systems and methods disclosed herein may be embodied in various forms, including, for example, a data processor such as a computer, including a database, digital electronic circuitry, firmware, software, or any combination thereof. Furthermore, the above-described features and other aspects and principles of the implementations of the present disclosure may be implemented in a variety of environments. Such environments and associated applications may be specially constructed to perform the various processes and operations in accordance with the disclosed implementations, or they may comprise general-purpose computers or computing platforms selectively activated or reconfigured by code to provide the required functionality. The processes disclosed herein are not inherently related to any particular computer, network, architecture, environment, or other apparatus, but may be implemented by any suitable combination of hardware, software, and / or firmware. For example, various general-purpose machines may be used with programs written in accordance with the teachings of the disclosed implementations, or it may be more convenient to construct specialized apparatus or systems to perform the required methods and techniques.

[0146] The systems and methods disclosed herein can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., a machine-readable storage device or a propagated signal, for execution by or to control the operation of a data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. The computer program can be written in any type of programming language, including compiled or interpreted languages, and can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. The computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communications network.

[0147] As used herein, the term "user" can refer to any entity, including a person or a computer.

[0148] Although ordinal numbers such as first, second, etc. may relate to order in some circumstances, as used in this document, ordinal numbers do not necessarily imply order. For example, ordinal numbers may be used simply to distinguish one item from another. For example, distinguishing a first event from a second event need not imply any chronological order or fixed frame of reference (just as a first event in one paragraph of description may differ from a first event in another paragraph of description).

[0149] The foregoing description is intended to illustrate, but not to limit, the scope of the invention, which is defined by the appended claims. Other implementations are within the scope of the following claims.

[0150] These computer programs, which may also be referred to as programs, software, software applications, applications, components, or code, include machine instructions for a programmable processor and may be implemented in a high-level procedural and / or object-oriented programming language and / or in assembly / machine language. As used herein, the term “machine-readable medium” refers to any computer program product, apparatus, and / or device used to provide machine instructions and / or data to a programmable processor, including a machine-readable medium that receives machine instructions as a machine-readable signal, such as, for example, a magnetic disk, an optical disk, a memory, and a programmable logic device (PLD). The term “machine-readable signal” refers to any signal used to provide machine instructions and / or data to a programmable processor. A machine-readable medium may non-transitory store such machine instructions, such as, for example, a non-transitory solid-state memory or a magnetic hard drive or any equivalent storage medium. Alternatively or additionally, a machine-readable medium may temporarily store such machine instructions, such as, for example, a processor cache or other random access memory associated with one or more physical processor cores.

[0151] To provide for user interaction, the subject matter described herein can be implemented on a computer having a display device, such as a cathode ray tube (CRT) or liquid crystal display (LCD) monitor, for displaying information to the user, and a keyboard and pointing device, such as a mouse or trackball, by which the user can provide input to the computer. Other types of devices can also be used to provide for user interaction. For example, feedback provided to the user can be any form of sensory feedback, such as, for example, visual feedback, auditory feedback, or tactile feedback, and input from the user can be received in any form, including, but not limited to, acoustic, speech, or tactile input.

[0152] The subject matter described herein may be implemented in a computing system that includes back-end components, such as, for example, one or more data servers, or that includes middleware components, such as, for example, one or more application servers, or that includes front-end components, such as, for example, one or more client computers having a graphical user interface or web browser through which a user can interact with an implementation of the subject matter described herein, or any combination of such back-end, middleware, or front-end components. The components of the system may be interconnected by any form or medium of digital data communication, such as, for example, a communications network. Examples of communications networks include, but are not limited to, a local area network ("LAN"), a wide area network ("WAN"), and the Internet.

[0153] A computing system may include clients and servers. Clients and servers are generally, but not exclusively, remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

[0154] The implementations described in the foregoing description do not represent all implementations consistent with the subject matter described herein. Rather, they are merely some examples consistent with aspects related to the described subject matter. While several variations have been described in detail above, other modifications or additions are possible. In particular, additional features and / or variations may be provided in addition to those described herein. For example, the implementations described above may be directed to various combinations and subcombinations of the disclosed features and / or combinations and subcombinations of certain additional features disclosed above. Additionally, the logic flow illustrated in the accompanying figures and / or described herein does not necessarily require the particular order shown, or sequential order, to achieve desirable results. Other implementations may be within the scope of the following claims.

Claims

1. at least one processor; at least one non-transitory storage medium storing instructions that, when executed by the at least one processor, cause the at least one processor to perform operations, the operations including: receiving, by a distributed unit (DU) in an open radio access network, from a radio unit (RU) in the open radio access network, an identifier identifying the RU; identifying, by the DU, communication information associated with the RU based on the identifier that identifies the RU; determining, by the DU, communication characteristics for data transmission to the RU using the DU's particular carrier; transmitting data from the DU to the RU using the specific carrier according to the communication information and the communication characteristics; at least one non-transitory storage medium, An apparatus comprising:

2. the communication information includes an interoperability (IOT) profile; The apparatus of claim 1 , wherein the communication characteristics include a delay window for data transmission.

3. 3. The apparatus of claim 2, wherein the identifying includes looking up the identifier in a lookup table stored on the at least one non-transitory storage medium, the lookup table uniquely associating each of a plurality of RU identifiers with an IOT profile.

4. 3. The apparatus of claim 2, wherein the data is transmitted over a fronthaul network and includes control plane (C-plane) data and user plane (U-plane) data.

5. the communication information includes an extended antenna carrier identifier (eAxC_ID) including a DU PORT ID; The apparatus of claim 1 , wherein determining the communication characteristics includes modifying the DU PORT ID.

6. The apparatus of claim 5 , wherein the data is transmitted over a fronthaul network and comprises user plane (U-plane) data.

7. the operations further include transmitting the modified DU PORT ID from the DU to the RU over the U-plane; The apparatus of claim 6 , wherein the RU is configured to loop the received modified DU PORT ID to a control plane (C-plane).

8. identifying the communication information includes forming a beamforming profile and assigning a deployment ID to the RU; The apparatus of claim 1 , wherein the communication features include beamforming weights.

9. The apparatus of claim 8 , wherein transmitting the data includes transmitting the beamforming weights from the DU to the RU.

10. The apparatus of claim 8 , wherein determining the communication characteristic comprises identifying which beamforming weight of a plurality of predetermined beamforming weights correlates with the assigned deployment ID.

11. the operations further include transmitting the identified communication information from Layer 3 of the DU to Layer 1 of the DU; The apparatus of claim 1 , wherein Layer 1 of the DU performs the determining.

12. The apparatus of claim 1 , wherein the DU receives the identifier from the RU during an initial handshake process between the DU and the RU.

13. the DU is a single DU, The operation is receiving, by the DU, from a second RU in the open wireless access network, an identifier identifying the second RU; identifying, by the DU, communication information associated with the second RU based on the identifier that identifies the second RU; determining, by the DU, communication characteristics for data transmission to the second RU using a second particular carrier of the DU; transmitting data from the DU to the second RU using the second particular carrier in accordance with the communication information associated with the second RU and the communication characteristics related to transmitting data to the second RU; The apparatus of claim 1 further comprising:

14. a base station including the at least one processor and the at least one non-transitory storage medium; The apparatus of claim 1 , wherein the base station is configured to communicate in a wireless communication network.

15. The apparatus of claim 14 , wherein the base station comprises an eNodeB or a gNodeB.

16. receiving, by a distributed unit (DU) in an open radio access network, from a radio unit (RU) in the open radio access network, an identifier identifying the RU; identifying, by the DU, communication information associated with the RU based on the identifier that identifies the RU; determining, by the DU, communication characteristics for data transmission to the RU using the DU's particular carrier; transmitting data from the DU to the RU using the specific carrier according to the communication information and the communication characteristics; 11. A computer-implemented method comprising:

17. the communication information includes an interoperability (IOT) profile; The method of claim 16 , wherein the communication characteristics include a delay window for data transmission.

18. the communication information includes an extended antenna carrier identifier (eAxC_ID) including a DU PORT ID; The method of claim 16 , wherein determining the communication characteristics includes modifying the DU PORT ID.

19. identifying the communication information includes forming a beamforming profile and assigning a deployment ID to the RU; The method of claim 16 , wherein the communication features include beamforming weights.

20. at least one non-transitory storage medium storing instructions that, when executed by at least one processor, cause the at least one processor to perform operations, the operations including: receiving, by a distributed unit (DU) in an open radio access network, from a radio unit (RU) in the open radio access network, an identifier identifying the RU; identifying, by the DU, communication information associated with the RU based on the identifier that identifies the RU; determining, by the DU, communication characteristics for data transmission to the RU using the DU's particular carrier; transmitting data from the DU to the RU using the specific carrier according to the communication information and the communication characteristics; At least one non-transitory storage medium, including:

Images