[go: up one dir, main page]

WO2025118635A1 - Configuration et commande de o-ru dans un o-ran - Google Patents

Configuration et commande de o-ru dans un o-ran Download PDF

Info

Publication number
WO2025118635A1
WO2025118635A1 PCT/CN2024/107980 CN2024107980W WO2025118635A1 WO 2025118635 A1 WO2025118635 A1 WO 2025118635A1 CN 2024107980 W CN2024107980 W CN 2024107980W WO 2025118635 A1 WO2025118635 A1 WO 2025118635A1
Authority
WO
WIPO (PCT)
Prior art keywords
configuration
network entity
transceiver
cell
network
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
PCT/CN2024/107980
Other languages
English (en)
Inventor
Shuigen Yang
Mingzeng Dai
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Lenovo Beijing Ltd
Original Assignee
Lenovo Beijing Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Lenovo Beijing Ltd filed Critical Lenovo Beijing Ltd
Priority to PCT/CN2024/107980 priority Critical patent/WO2025118635A1/fr
Publication of WO2025118635A1 publication Critical patent/WO2025118635A1/fr
Pending legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0203—Power saving arrangements in the radio access network or backbone network of wireless communication networks
    • H04W52/0206—Power saving arrangements in the radio access network or backbone network of wireless communication networks in access points, e.g. base stations
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H04W24/02—Arrangements for optimising operational condition
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0225—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal
    • H04W52/0229—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal
    • H04W52/0235—Power saving arrangements in terminal devices using monitoring of external events, e.g. the presence of a signal where the received signal is a wanted signal where the received signal is a power saving command
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W52/00—Power management, e.g. Transmission Power Control [TPC] or power classes
    • H04W52/02—Power saving arrangements
    • H04W52/0209—Power saving arrangements in terminal devices
    • H04W52/0261—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level
    • H04W52/0274—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof
    • H04W52/028—Power saving arrangements in terminal devices managing power supply demand, e.g. depending on battery level by switching on or off the equipment or parts thereof switching on or off only a part of the equipment circuit blocks
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/08—Access point devices
    • H04W88/085—Access point devices with remote components
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
    • Y02D30/00—Reducing energy consumption in communication networks
    • Y02D30/70—Reducing energy consumption in communication networks in wireless communication networks

Definitions

  • the present disclosure relates to wireless communications, and more specifically to user equipment (UE) , network nodes and methods for supporting an open radio access network radio unit (O-RU) configuration and control in an open radio access network (O-RAN) .
  • UE user equipment
  • OFDRU open radio access network radio unit
  • a wireless communications system may include one or multiple network communication devices, such as base stations, which may be otherwise known as an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • Each network communication devices such as a base station may support wireless communications for one or multiple user communication devices, which may be otherwise known as user equipment (UE) , or other suitable terminology.
  • the wireless communications system may support wireless communications with one or multiple user communication devices by utilizing resources of the wireless communication system (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) .
  • the wireless communications system may support wireless communications across various radio access technologies including third generation (3G) radio access technology, fourth generation (4G) radio access technology, fifth generation (5G) radio access technology, among other suitable radio access technologies beyond 5G (e.g., sixth generation (6G) ) .
  • 3G third generation
  • 4G fourth generation
  • 5G fifth generation
  • 6G sixth generation
  • radio resource management (RRM) function may be typically located at a near-real-time radio access network intelligent controller (Near-RT RIC) by means of an E2 service model (E2SM) over an E2 interface.
  • the E2SM describes the functions in an E2 node which may be controlled by the Near-RT RIC and the related procedures.
  • the Near-RT RIC may, for example, monitor, suspend, stop, override or control the behavior of the E2 node.
  • E2SM-CCC E2SM cell configuration and control
  • E2SM-CCC E2SM cell configuration and control
  • E2 REPORT services used to expose node level and cell level configuration information
  • E2 CONTROL services used to initiate control and/or configuration of node level and cell level parameters.
  • the Near-RT RIC may need to configure or control certain O-RU components for better network optimization. Thus, there is need to study how to support the O-RU configuration and control.
  • the present disclosure relates to network entities and methods that support O-RU configuration and control in an O-RAN.
  • O-RU configuration and control in an O-RAN may be achieved.
  • Some implementations of a first network entity described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: receive a guide configuration for an O-RU via the transceiver from a second network entity, wherein the guide configuration is used to save energy of the O-RU;and transmit, based on the guide configuration for the O-RU, a command via the transceiver to the O-RU to save energy of the O-RU.
  • the guide configuration for the O-RU comprises at least one of the following: at least one sleep mode for at least one transceiver array of the O-RU to be applied, wherein the transceiver array is a transmitter array or a receiver array, or an indication indicating at least one antenna array element of the O-RU is to be switched off during a period.
  • the guide configuration for the O-RU further comprises at least one of the following: information about time when the at least one sleep mode for the at least one transceiver array of the O-RU is to be applied, or at least one condition for the at least one sleep mode for the at least one transceiver array of the O-RU to be applied.
  • the command indicates one of the following: to disable a carrier in the O-RU, to disable a transceiver array in the O-RU, or to disable the O-RU.
  • the processor is further configured to: transmit, via the transceiver to the second network entity, an O-RU configuration for the O-RU using an E2 service model cell configuration and control (E2SM-CCC) function of the first network entity.
  • E2SM-CCC E2 service model cell configuration and control
  • the processor is configured to transmit the O-RU configuration by: transmitting, via the transceiver to the second network entity, an open radio access network distributed unit (O-DU) cell level configuration using the E2SM-CCC function, wherein the O-DU cell level configuration comprises the O-RU configuration.
  • O-DU open radio access network distributed unit
  • the processor is configured to transmit the O-RU configuration by: transmitting, via the transceiver to the second network entity, a cell level configuration using the E2SM-CCC function, wherein the cell level configuration comprises the O-RU configuration.
  • the processor is configured to transmit the O-RU configuration by: transmitting, via the transceiver to the second network entity, an O-DU level configuration using the E2SM-CCC function, wherein the O-DU level configuration comprises the O-RU configuration.
  • the O-RU configuration comprises at least one of the following: a radio frequency (RF) channel configuration, or a sleep mode configuration.
  • RF radio frequency
  • the RF channel configuration comprises a transceiver control configuration, wherein the transceiver control configuration comprises a mask name for at least one antenna array element and an antenna mask for the at least one antenna array element, each of bits in the antenna mask is associated with one of the at least one antenna array element and indicates whether a respective one of the at least one antenna array element is active or inactive.
  • the sleep mode configuration comprises at least one of the following: a sleep mode type indicating a sleep mode supported by the O-RU for a transceiver array, and a wakeup duration indicating wakeup time for the sleep mode for the transceiver array.
  • the O-RU configuration is associated with an identifier of a cell, wherein the identifier of the cell identifies the cell when the O-RU is configured to operate with multiple cells, the multiple cells comprise the cell.
  • the O-RU configuration is associated with an identifier of the O-RU, wherein the identifier of the O-RU identifies the O-RU when a cell is realized by multiple O-RUs, the multiple O-RUs comprise the O-RU.
  • the identifier of the O-RU comprises at least one of the following: an identifier of an O-RU instance, wherein the identifier of the O-RU instance is configured by a controller of the O-RU; an identifier of a component carrier, wherein the O-RU is associated with the component carrier for a cell; or information about a first port of the first network entity connected to a second port of the O-RU.
  • a second network entity described herein may include a processor and a transceiver coupled to the processor, wherein the processor is configured to: receiving an O-RU configuration for the O-RU using an E2SM-CCC function of a first network entity via the transceiver from the first network entity, wherein the first network entity is connected to the O-RU; and transmit a guide configuration for the O-RU via the transceiver to the first network entity, wherein the guide configuration is used to save energy of the O-RU.
  • the guide configuration for the O-RU comprises at least one of the following: at least one sleep mode for at least one transceiver array of the O-RU to be applied, wherein the transceiver array is a transmitter array or a receiver array, or an indication indicating at least one antenna array element of the O-RU is to be switched off during a period.
  • the guide configuration for the O-RU further comprises at least one of the following: information about time when the at least one sleep mode for the at least one transceiver array of the O-RU is to be applied, or at least one condition for the at least one sleep mode for the at least one transceiver array of the O-RU to be applied.
  • the processor is configured to receive the O-RU configuration by: receiving, via the transceiver from the first network entity, an O-DU cell level configuration using the E2SM-CCC function, wherein the O-DU cell level configuration comprises the O-RU configuration.
  • the processor is configured to receive the O-RU configuration by: receiving, via the transceiver from the first network entity, a cell level configuration using the E2SM-CCC function, wherein the cell level configuration comprises the O-RU configuration.
  • the processor is configured to receive the O-RU configuration by: receiving, via the transceiver from the first network entity, an O-DU level configuration using the E2SM-CCC function, wherein the O-DU level configuration comprises the O-RU configuration.
  • the O-RU configuration comprises at least one of the following: an RF channel configuration, or a sleep mode configuration.
  • the RF channel configuration comprises a transceiver control configuration, wherein the transceiver control configuration comprises a mask name for at least one antenna array element and an antenna mask for the at least one antenna array element, each of bits in the antenna mask is associated with one of the at least one antenna array element and indicates whether a respective one of the at least one antenna array element is active or inactive.
  • the sleep mode configuration comprises at least one of the following: a sleep mode type indicating a sleep mode supported by the O-RU for a transceiver array, and a wakeup duration indicating wakeup time for the sleep mode for the transceiver array.
  • the O-RU configuration is associated with an identifier of a cell, wherein the identifier of the cell identifies the cell when the O-RU is configured to operate with multiple cells, the multiple cells comprise the cell.
  • the O-RU configuration is associated with an identifier of the O-RU, wherein the identifier of the O-RU identifies the O-RU when a cell is realized by multiple O-RUs, the multiple O-RUs comprise the O-RU.
  • the identifier of the O-RU comprises at least one of the following: an identifier of an O-RU instance, wherein the identifier of the O-RU instance is configured by a controller of the O-RU; an identifier of a component carrier, wherein the O-RU is associated with the component carrier for a cell; or information about a first port of the first network entity connected to a second port of the O-RU.
  • Some implementations of a method described herein may include: receiving a guide configuration for an O-RU from a second network entity, wherein the guide configuration is used to save energy of the O-RU; and transmitting, based on the guide configuration for the O-RU, a command to the O-RU to save energy of the O-RU.
  • Some implementations of a method described herein may include: receiving an O-RU configuration for the O-RU using an E2 service model cell configuration and control (E2SM-CCC) function of a first network entity from the first network entity, wherein the first network entity is connected to the O-RU; and transmitting a guide configuration for the O-RU via the transceiver to the first network entity, wherein the guide configuration is used to save energy of the O-RU.
  • E2SM-CCC E2 service model cell configuration and control
  • Fig. 1 illustrates an example of a wireless communications system that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure
  • Fig. 2 illustrates another example of a wireless communications system that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure
  • Fig. 3A illustrates an example of a deployment scenario of an O-RU in accordance with aspects of the present disclosure
  • Fig. 3B illustrates another example of a deployment scenario of an O-RU in accordance with aspects of the present disclosure
  • Fig. 4 illustrates a further example of a wireless communications system that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure
  • Figs. 5 and 6 illustrate a signaling diagram illustrating an example process that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure, respectively;
  • Fig. 7 illustrates an example of connections between the first network entity and O-RUs in accordance with aspects of the present disclosure
  • Figs. 8 and 9 illustrate a signaling diagram illustrating an example process that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure, respectively;
  • Fig. 10 illustrates an example of a device that supports O-RU configuration and control in an O-RAN in accordance with some aspects of the present disclosure
  • Figs. 11 and 12 illustrate a flowchart of a method that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure, respectively.
  • references in the present disclosure to “one embodiment, ” “an example embodiment, ” “an embodiment, ” “some embodiments, ” and the like indicate that the embodiment (s) described may include a particular feature, structure, or characteristic, but it is not necessary that every embodiment includes the particular feature, structure, or characteristic. Moreover, such phrases do not necessarily refer to the same embodiment (s) . Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is submitted that it is within the knowledge of one skilled in the art to affect such feature, structure, or characteristic in connection with other embodiments whether or not explicitly described.
  • first and second or the like may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, a first element could also be termed as a second element, and similarly, a second element could also be termed as a first element, without departing from the scope of embodiments. As used herein, the term “and/or” includes any and all combinations of one or more of the listed terms.
  • the Near-RT RIC may need to configure or control certain O-RU components for better network optimization.
  • the Near-RT RIC can play important roles to create more sleeping opportunities, such as power off certain O-RU components (e.g., power amplifier, low noise amplifier and baseband etc) during blank orthogonal frequency division multiplexing symbols and slots, or dynamically reconfigure the number of active transmitting or receiving antenna array elements.
  • the present disclosure provides a solution that supports O-RU configuration and control in an O-RAN.
  • a first network entity receives a guide configuration for an O-RU from a second network entity.
  • the guide configuration is used to save energy of the O-RU.
  • the first network entity transmits, based on the guide configuration for the O-RU, a command to the O-RU to save energy of the O-RU.
  • Fig. 1 illustrates an example of a wireless communications system 100 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the wireless communications system 100 may include one at least one of network entities 102 (also referred to as network equipment (NE) ) , one or more terminal devices or UEs 104, a core network 106, and a packet data network 108.
  • the wireless communications system 100 may support various radio access technologies.
  • the wireless communications system 100 may be a 4G network, such as an LTE network or an LTE-advanced (LTE-A) network.
  • LTE-A LTE-advanced
  • the wireless communications system 100 may be a 5G network, such as an NR network.
  • the wireless communications system 100 may be a combination of a 4G network and a 5G network, or other suitable radio access technology including institute of electrical and electronics engineers (IEEE) 802.11 (Wi-Fi) , IEEE 802.16 (WiMAX) , IEEE 802.20.
  • IEEE institute of electrical and electronics engineers
  • Wi-Fi Wi-Fi
  • WiMAX IEEE 802.16
  • IEEE 802.20 The wireless communications system 100 may support radio access technologies beyond 5G. Additionally, the wireless communications system 100 may support technologies, such as time division multiple access (TDMA) , frequency division multiple access (FDMA) , or code division multiple access (CDMA) , etc.
  • TDMA time division multiple access
  • FDMA frequency division multiple access
  • CDMA code division multiple access
  • the network entities 102 may be dispersed throughout a geographic region to form the wireless communications system 100.
  • One or more of the network entities 102 described herein may be or include or may be referred to as a network node, a base station (BS) , a network element, a radio access network (RAN) node, a base transceiver station, an access point, a NodeB, an eNodeB (eNB) , a next-generation NodeB (gNB) , or other suitable terminology.
  • a network entity 102 and a UE 104 may communicate via a communication link 110, which may be a wireless or wired connection.
  • a network entity 102 and a UE 104 may perform wireless communication (e.g., receive signaling, transmit signaling) over a Uu interface.
  • the network entities 102 may be collectively referred to as network entities 102 or individually referred to as a network entity 102.
  • a network entity 102 may be used interchangeably with the gNB 102.
  • a network entity 102 may provide a geographic coverage area 112 for which the network entity 102 may support services (e.g., voice, video, packet data, messaging, broadcast, etc. ) for one or more UEs 104 within the geographic coverage area 112.
  • a network entity 102 and a UE 104 may support wireless communication of signals related to services (e.g., voice, video, packet data, messaging, broadcast, etc. ) according to one or multiple radio access technologies.
  • a network entity 102 may be moveable, for example, a satellite associated with a non-terrestrial network.
  • different geographic coverage areas 112 associated with the same or different radio access technologies may overlap, but the different geographic coverage areas 112 may be associated with different network entities 102.
  • Information and signals described herein may be represented using any of a variety of different technologies and techniques.
  • data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.
  • the one or more UEs 104 may be dispersed throughout a geographic region of the wireless communications system 100.
  • a UE 104 may include or may be referred to as a mobile device, a wireless device, a remote device, a remote unit, a handheld device, or a subscriber device, or some other suitable terminology.
  • the UE 104 may be referred to as a unit, a station, a terminal, or a client, among other examples.
  • the UE 104 may be referred to as an internet-of-things (IoT) device, an internet-of-everything (IoE) device, or machine-type communication (MTC) device, among other examples.
  • IoT internet-of-things
  • IoE internet-of-everything
  • MTC machine-type communication
  • a UE 104 may be stationary in the wireless communications system 100.
  • a UE 104 may be mobile in the wireless communications system 100.
  • the one or more UEs 104 may be devices in different forms or having different capabilities. Some examples of UEs 104 are illustrated in Fig. 1.
  • a UE 104 may be capable of communicating with various types of devices, such as the network entities 102, other UEs 104, or network equipment (e.g., the core network 106, the packet data network 108, a relay device, an integrated access and backhaul (IAB) node, or another network equipment) , as shown in Fig. 1.
  • a UE 104 may support communication with other network entities 102 or UEs 104, which may act as relays in the wireless communications system 100.
  • a UE 104 may also be able to support wireless communication directly with other UEs 104 over a communication link 114.
  • a UE 104 may support wireless communication directly with another UE 104 over a device-to-device (D2D) communication link.
  • D2D device-to-device
  • the communication link 114 may be referred to as a sidelink.
  • a UE 104 may support wireless communication directly with another UE 104 over a PC5 interface.
  • a network entity 102 may support communications with the core network 106, or with another network entity 102, or both.
  • a network entity 102 may interface with the core network 106 through one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the network entities 102 may communicate with each other over the backhaul links 116 (e.g., via an X2, Xn, or another network interface) .
  • the network entities 102 may communicate with each other directly (e.g., between the network entities 102) .
  • the network entities 102 may communicate with each other or indirectly (e.g., via the core network 106) .
  • one or more network entities 102 may include subcomponents, such as an access network entity, which may be an example of an access node controller (ANC) .
  • An ANC may communicate with the one or more UEs 104 through one or more other access network transmission entities, which may be referred to as a radio heads, smart radio heads, or transmission-reception points (TRPs) .
  • TRPs transmission-reception points
  • a network entity 102 may be configured in a disaggregated architecture, which may be configured to utilize a protocol stack physically or logically distributed among two or more network entities 102, such as an integrated access backhaul (IAB) network, an open radio access network (O-RAN) (e.g., a network configuration sponsored by the O-RAN Alliance) , or a virtualized RAN (vRAN) (e.g., a cloud RAN (C-RAN) ) .
  • IAB integrated access backhaul
  • O-RAN open radio access network
  • vRAN virtualized RAN
  • C-RAN cloud RAN
  • a network entity 102 may include one or more of a CU, a DU, a radio unit (RU) , a RAN intelligent controller (RIC) (e.g., a Near-RT RIC, a non-real time RIC (Non-RT RIC) ) , a service management and orchestration (SMO) system, or any combination thereof.
  • RIC RAN intelligent controller
  • SMO service management and orchestration
  • An RU may also be referred to as a radio head, a smart radio head, a remote radio head (RRH) , a remote radio unit (RRU) , or a transmission reception point (TRP) .
  • One or more components of the network entities 102 in a disaggregated RAN architecture may be co-located, or one or more components of the network entities 102 may be located in distributed locations (e.g., separate physical locations) .
  • one or more network entities 102 of a disaggregated RAN architecture may be implemented as virtual units (e.g., a virtual CU (VCU) , a virtual DU (VDU) , a virtual RU (VRU) ) .
  • VCU virtual CU
  • VDU virtual DU
  • VRU virtual RU
  • Split of functionality between a CU, a DU, and an RU may be flexible and may support different functionalities depending upon which functions (e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof) are performed at a CU, a DU, or an RU.
  • functions e.g., network layer functions, protocol layer functions, baseband functions, radio frequency functions, and any combinations thereof
  • a functional split of a protocol stack may be employed between a CU and a DU such that the CU may support one or more layers of the protocol stack and the DU may support one or more different layers of the protocol stack.
  • the CU may host upper protocol layer (e.g., an L3, an L2) functionality and signaling (e.g., radio resource control (RRC) , service data adaption protocol (SDAP) , packet data convergence protocol (PDCP) ) .
  • the CU may be connected to one or more DUs or RUs, and the one or more DUs or RUs may host lower protocol layers, such as an L1 (e.g., physical (PHY) layer) or an L2 (e.g., radio link control (RLC) layer, medium access control (MAC) layer) functionality and signaling, and may each be at least partially controlled by the CU.
  • L1 e.g., physical (PHY) layer
  • L2 e.g., radio link control (RLC) layer, medium access control (MAC) layer
  • a functional split of the protocol stack may be employed between a DU and an RU such that the DU may support one or more layers of the protocol stack and the RU may support one or more different layers of the protocol stack.
  • the DU may support one or multiple different cells (e.g., via one or more RUs) .
  • a functional split between a CU and a DU, or between a DU and an RU may be within a protocol layer (e.g., some functions for a protocol layer may be performed by one of a CU, a DU, or an RU, while other functions of the protocol layer are performed by a different one of the CU, the DU, or the RU) .
  • a CU may be functionally split further into CU control plane (CU-CP) and CU user plane (CU-UP) functions.
  • a CU may be connected to one or more DUs via a midhaul communication link (e.g., F1, F1-c, F1-u)
  • a DU may be connected to one or more RUs via a fronthaul communication link (e.g., open fronthaul (FH) interface)
  • FH open fronthaul
  • a midhaul communication link or a fronthaul communication link may be implemented in accordance with an interface (e.g., a channel) between layers of a protocol stack supported by respective network entities 102 that are in communication via such communication links.
  • the core network 106 may support user authentication, access authorization, tracking, connectivity, and other access, routing, or mobility functions.
  • the core network 106 may be an evolved packet core (EPC) , or a 5G core (5GC) , which may include a control plane entity that manages access and mobility (e.g., a mobility management entity (MME) , an access and mobility management functions (AMF) ) and a user plane entity that routes packets or interconnects to external networks (e.g., a serving gateway (S-GW) , a packet data network (PDN) gateway (P-GW) , or a user plane function (UPF) ) .
  • EPC evolved packet core
  • 5GC 5G core
  • MME mobility management entity
  • AMF access and mobility management functions
  • S-GW serving gateway
  • PDN gateway packet data network gateway
  • UPF user plane function
  • control plane entity may manage non-access stratum (NAS) functions, such as mobility, authentication, and bearer management (e.g., data bearers, signal bearers, etc. ) for the one or more UEs 104 served by the one or more network entities 102 associated with the core network 106.
  • NAS non-access stratum
  • the core network 106 may communicate with the packet data network 108 over one or more backhaul links 116 (e.g., via an S1, N2, N2, or another network interface) .
  • the packet data network 108 may include an application server 118.
  • one or more UEs 104 may communicate with the application server 118.
  • a UE 104 may establish a session (e.g., a protocol data unit (PDU) session, or the like) with the core network 106 via a network entity 102.
  • the core network 106 may route traffic (e.g., control information, data, and the like) between the UE 104 and the application server 118 using the established session (e.g., the established PDU session) .
  • the PDU session may be an example of a logical connection between the UE 104 and the core network 106 (e.g., one or more network functions of the core network 106) .
  • the network entities 102 and the UEs 104 may use resources of the wireless communications system 100 (e.g., time resources (e.g., symbols, slots, subframes, frames, or the like) or frequency resources (e.g., subcarriers, carriers) ) to perform various operations (e.g., wireless communications) .
  • the network entities 102 and the UEs 104 may support different resource structures.
  • the network entities 102 and the UEs 104 may support different frame structures.
  • the network entities 102 and the UEs 104 may support a single frame structure.
  • the network entities 102 and the UEs 104 may support various frame structures (i.e., multiple frame structures) .
  • the network entities 102 and the UEs 104 may support various frame structures based on one or more numerologies.
  • One or more numerologies may be supported in the wireless communications system 100, and a numerology may include a subcarrier spacing and a cyclic prefix.
  • a first subcarrier spacing e.g., 15 kHz
  • a normal cyclic prefix e.g. 15 kHz
  • the first numerology associated with the first subcarrier spacing (e.g., 15 kHz) may utilize one slot per subframe.
  • a time interval of a resource may be organized according to frames (also referred to as radio frames) .
  • Each frame may have a duration, for example, a 10 millisecond (ms) duration.
  • each frame may include multiple subframes.
  • each frame may include 10 subframes, and each subframe may have a duration, for example, a 1 ms duration.
  • each frame may have the same duration.
  • each subframe of a frame may have the same duration.
  • a time interval of a resource may be organized according to slots.
  • a subframe may include a number (e.g., quantity) of slots.
  • the number of slots in each subframe may also depend on the one or more numerologies supported in the wireless communications system 100.
  • Each slot may include a number (e.g., quantity) of symbols (e.g., OFDM symbols) .
  • the number (e.g., quantity) of slots for a subframe may depend on a numerology.
  • a slot For a normal cyclic prefix, a slot may include 14 symbols.
  • a slot For an extended cyclic prefix (e.g., applicable for 60 kHz subcarrier spacing) , a slot may include 12 symbols.
  • an electromagnetic (EM) spectrum may be split, based on frequency or wavelength, into various classes, frequency bands, frequency channels, etc.
  • the wireless communications system 100 may support one or multiple operating frequency bands, such as frequency range designations FR1 (410 MHz –7.125 GHz) , FR2 (24.25 GHz –52.6 GHz) , FR3 (7.125 GHz –24.25 GHz) , FR4 (52.6 GHz –114.25 GHz) , FR4a or FR4-1 (52.6 GHz –71 GHz) , and FR5 (114.25 GHz –300 GHz) .
  • FR1 410 MHz –7.125 GHz
  • FR2 24.25 GHz –52.6 GHz
  • FR3 7.125 GHz –24.25 GHz
  • FR4 (52.6 GHz –114.25 GHz)
  • FR4a or FR4-1 52.6 GHz –71 GHz
  • FR5 114.25 GHz
  • the network entities 102 and the UEs 104 may perform wireless communications over one or more of the operating frequency bands.
  • FR1 may be used by the network entities 102 and the UEs 104, among other equipment or devices for cellular communications traffic (e.g., control information, data) .
  • FR2 may be used by the network entities 102 and the UEs 104, among other equipment or devices for short-range, high data rate capabilities.
  • FR1 may be associated with one or multiple numerologies (e.g., at least three numerologies) .
  • FR2 may be associated with one or multiple numerologies (e.g., at least 2 numerologies) .
  • Fig. 2 illustrates another example of a wireless communications system 200 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the wireless communications system 200 may be implemented as an O-RAN. In such implementations, the wireless communications system 200 is also referred to as an O-RAN 200.
  • the O-RAN 200 may comprise a Near-RT RIC 220, E2 nodes 210, 240-1, 240-2 and 240-3, an O-RU 230, an O-Cloud 250 as well as a non-real-time RIC (Non-RT RIC) 260.
  • Non-RT RIC non-real-time RIC
  • the Near-RT RIC 220 may be a logical function that enables near-real-time control and optimization of RAN elements and resources via fine-grained data collection and actions over E2 interface.
  • An E2 interface is an interface connecting a Near-RT RIC and one or more O-CU-CPs, one or more O-CU-UPs, or one or more O-DUs.
  • the Near-RT RIC 220 may be implemented as the network entity 102 or part of the network entity 102 in Fig. 1.
  • Each of the E2 nodes 210, 240-1, 240-2 and 240-3 may be a logical node terminating E2 interface.
  • each of the E2 nodes 210, 240-1, 240-2 and 240-3 may be implemented as the network entity 102 or part of the network entity 102 in Fig. 1.
  • the E2 node 210 may be an O-RAN distributed unit (O-DU) .
  • the O-DU may be a logical node hosting radio link control (RLC) , medium access control (MAC) and high-physical (PHY) layers based on a lower layer functional split.
  • RLC radio link control
  • MAC medium access control
  • PHY high-physical
  • the E2 node 240-1 may be an O-RAN eNB (O-eNB) .
  • the O-eNB may be an eNB or ng-eNB that supports E2 interface.
  • the E2 node 240-2 may be an O-RAN central unit -control plane (O-CU-CP) .
  • the O-CU-CP may be a logical node hosting the radio resource control (RRC) and the control plane part of the packet data convergence protocol (PDCP) protocol.
  • RRC radio resource control
  • PDCP packet data convergence protocol
  • the E2 node 240-3 may be an O-RAN central unit -user plane (O-CU-UP) .
  • O-CU-UP may be a logical node hosting the user plane part of the PDCP protocol and the service data adaption protocol (SDAP) protocol.
  • SDAP service data adaption protocol
  • the O-RU 230 may be a logical node hosting Low-PHY layer and radio frequency (RF) processing based on a lower layer functional split.
  • RF radio frequency
  • one or more of the E2 nodes 210, 240-1, 240-2 and 240-3 may be any combination of the above logical nodes.
  • an E2 node is a combination of the E2 nodes 210, 240-2 and 240-3.
  • the Near-RT RIC 220 may be connected to the E2 nodes 210, 240-1, 240-2 and 240-3 via respective E2 interfaces.
  • the Near-RT RIC 220 may be also connected to Y1 consumers 270.
  • An E2 node is connected to only one Near-RT RIC, while a Near-RT RIC can be connected to multiple E2 nodes.
  • each of the E2 nodes 210, 240-1, 240-2 and 240-3 is connected to only the Near-RT RIC 220, while the Near-RT RIC 220 can be connected to the E2 nodes 210, 240-1, 240-2 and 240-3.
  • the Near-RT RIC 220, the E2 nodes 210, 240-1, 240-2 and 240-3 as well as the O-RU 230 may be implemented in a single network entity 102.
  • the Near-RT RIC 220, the E2 nodes 210, 240-1, 240-2 and 240-3 as well as the O-RU 230 may be implemented in multiple network entities 102.
  • the Near-RT RIC 220 may use at least one of the following RIC services provided by any of the E2 nodes 210, 240-1, 240-2 and 240-3 via the E2 interface: REPORT service, CONTROL service, INSERT service, or QUERY service.
  • the Near-RT RIC 220 uses a RIC Subscription and/or RIC Subscription Modification procedures to request that any of the E2 nodes 210, 240-1, 240-2 and 240-3 sends a REPORT message to the Near-RT RIC 220 and the associated procedure continues in the E2 node after each occurrence of a defined RIC Subscription procedure Event Trigger.
  • the Near-RT RIC 220 sends a CONTROL message to any of the E2 nodes 210, 240-1, 240-2 and 240-3 to initiate a new associated procedure or resume a previously suspended associated procedure in the E2 Node.
  • the Near-RT RIC 220 uses a RIC Subscription and/or RIC Subscription Modification procedures to request that any of the E2 nodes 210, 240-1, 240-2 and 240-3 sends an INSERT message to the Near-RT RIC 220 and suspends the associated procedure in the E2 Node after each occurrence of a defined RIC Subscription procedure Event Trigger.
  • the Near-RT RIC 220 sends a QUERY message to any of the E2 nodes 210, 240-1, 240-2 and 240-3 to retrieve RAN-related and/or UE-related information from the E2 Node.
  • the O-RAN 200 may include any suitable number of the Near-RT RIC and the E2 Nodes adapted for implementing implementations of the present disclosure.
  • Fig. 3A illustrates an example of a deployment scenario 300A of an O-RU in accordance with aspects of the present disclosure.
  • the deployment scenario 300A is a shared O-RU scenario where the O-RU 230 is implemented as a shared O-RU.
  • the O-RU 230 is configured to operate with multiple O-DUs, where the multiple O-DUs can belong to a single operator and/or multiple operators.
  • the O-RU 230 is configured to operate with the O-DU 210 in Fig. 2 and an O-DU 212 which is not shown in Fig. 2.
  • Fig. 3B illustrates another example of a deployment scenario 300B of an O-RU in accordance with aspects of the present disclosure.
  • the deployment scenario 300B is a shared cell scenario where a cell is realized by several O-RUs, where the cell can have multiple component carriers. That is, the shared cell is defined as the operation for the same cell by several O-RUs.
  • a cell #1 is realized by the O-RU 230 in Fig. 2 and an O-RU 232 which is not shown in Fig. 2
  • a cell #M is realized by an O-RU 234 and an O-RU 236 which are not shown in Fig. 2.
  • a cell is realized by an O-RU, and the O-RU is configured to operate with an O-DU.
  • the O-RU 230 is configured to operate with the O-DU 210 in Fig. 2.
  • Fig. 4 illustrates a further example of a wireless communications system 400 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the wireless communications system 400 may comprise a first network entity 410, a second network entity 420 and the O-RU 230 in Fig. 2.
  • the second network entity 420 is connected to the first network entity 410, and the first network entity 410 is connected to the O-RU 230.
  • the first network entity 410 may be implemented as the O-DU 210 in Fig. 2
  • the second network entity 420 may be implemented as the Near-RT RIC 220 in Fig. 2.
  • Fig. 5 illustrates a signaling diagram of an example process 500 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the process 500 may implement aspects of the wireless communications systems as described herein with reference to Figs. 1 through 3B, respectively.
  • the process 500 may involve the first network entity 410, the second network entity 420 and the O-RU 230 in Fig. 4.
  • the second network entity 420 transmits 520 a guide configuration for the O-RU 230 to the first network entity 410.
  • the guide configuration is used to save energy of the O-RU 230.
  • the first network entity 410 transmits 530, based on the guide configuration for the O-RU 230, a command to the O-RU 230 to save energy of the O-RU 230.
  • the first network entity 410 may transmit 510, to the second network entity 420, an O-RU configuration for the O-RU 230 using an E2SM-CCC function of the first network entity 410.
  • the first network entity 410 may transmit, to the second network entity 420, an O-DU cell level configuration using the E2SM-CCC function.
  • the O-DU cell level configuration may comprise the O-RU 230 configuration. This will be described with reference to Fig. 6 later.
  • the first network entity 410 may transmit, to the second network entity 420, a cell level configuration using the E2SM-CCC function.
  • the cell level configuration may comprise the O-RU 230 configuration. This will be described with reference to Fig. 8 later.
  • the first network entity 410 may transmit, to the second network entity 420, an O-DU level configuration using the E2SM-CCC function.
  • the O-DU level configuration comprises the O-RU 230 configuration. This will be described with reference to Fig. 9 later.
  • Fig. 6 illustrates a signaling diagram of an example process 600 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the process 600 may be considered as an example implementation of the process 500.
  • the process 600 may implement aspects of the wireless communications systems as described herein with reference to Figs. 1 through 3B, respectively.
  • the process 600 may involve the first network entity 410, the second network entity 420 and the O-RU 230 in Fig. 4.
  • an indicator is introduced in an O-NRCellDU RAN configuration structure to represent the O-RU configuration.
  • the first network entity 410 may transmit, to the second network entity 420, an O-DU cell level configuration using the E2SM-CCC function.
  • the O-DU cell level configuration may comprise the O-RU 230 configuration.
  • the first network entity 410 may be implemented as the first network entity 410 210 in Fig. 2, and the second network entity 420 may be implemented as the Near-RT RIC 220 in Fig. 2.
  • the first network entity 410 may transmit 610 an O-RU information retrieval request to the O-RU 230 so as to obtain the O-RU configuration.
  • the O-RU 230 may transmit 615 an O-RU information retrieval reply to the first network entity 410.
  • the O-RU information retrieval reply may comprise the O-RU configuration for the O-RU 230.
  • the first network entity 410 may transmit 620 the O-RU configuration for the O-RU 230 to the second network entity 420.
  • the O-RU configuration for the O-RU 230 may comprise at least one of the following: an RF channel configuration, or a sleep mode configuration.
  • the sleep mode configuration is also referred to as an advanced sleep mode configuration.
  • the RF channel configuration may comprise a transceiver (TRX) control configuration.
  • TRX refers to the specific processing chain in the O-RU 230 associated with digital-to-analog (D/A) or analog-to-digital (A/D) converters.
  • the TRX control configuration may comprise a mask name for at least one antenna array element and an antenna mask for the at least one antenna array element.
  • the antenna array element also refers to array element.
  • the antenna mask has as many bits as there is the at least one antenna array element.
  • Each of bits in the antenna mask is associated with one of the at least one antenna array element and indicates whether a respective one of the at least one antenna array element is active or inactive. For example, a value of 1 of a bit in the antenna mask for an antenna array element indicates the antenna array element is active while a value of 0 of the bit in the antenna mask for the antenna array element indicates the antenna array element is inactive.
  • the sleep mode configuration may comprise at least one of the following: a sleep mode type indicating a sleep mode supported by the O-RU 230 for a TRX array, and a wakeup duration indicating wakeup time for the sleep mode for the TRX array.
  • the TRX array is a transmitter array or a receiver array, both of which are logical constructs used for data routing and there is a relationship to physical antennas.
  • the wakeup time for the sleep mode for the TRX array may be in microseconds.
  • the first network entity 410 may transmit a RAN Function Definition for O-NRCellDU including O-RU attributes to the second network entity 420 by transmitting an E2 SETUP REQUEST message.
  • the O- NRCellDU represents the NR cell attributes in the O-DU, such as cell local ID, physical cell ID, tracking area code, absolute radio frequency channel number in the downlink or uplink.
  • the RAN Function Definition for O-NRCellDU may comprise an O-RUConfigList information element (IE) .
  • the O-RUConfigList IE may comprise attributes of one or more O-RU configurations associated with a cell.
  • the O-RUConfigList IE may comprise attributes of the O-RU configuration for the O-RU 230 associated with the cell #1.
  • the O-RUConfigList IE may comprise attributes of the O-RU configuration for the O-RU 230 and attributes of the O-RU configuration for the O-RU 232 associated with the cell #1.
  • Table 1 gives an example of the O-RUConfigList IE.
  • the O-RUConfigList IE is used to represent a list of O-RUConfig IE, and the O-RUConfig IE comprises the O-RU configuration for the O-RU 230.
  • Table 2 gives an example of the O-RUConfig IE.
  • each O-RU configuration may be associated with an identifier of an O-RU.
  • the identifier of the O-RU identifies the O-RU when a cell is realized by multiple O-RUs.
  • the cell #1 is realized by the O-RU 230 and the O-RU 232.
  • the O-RU configuration for the O-RU 230 may be associated with an identifier of the O-RU 230
  • the O-RU configuration for the O-RU 232 may be associated with an identifier of the O-RU 232.
  • some implementations will be described by taking a single O-RU configuration for the O-RU 230 for example. The scope of the present disclosure is not limited in this regard.
  • the O-RU 230 may provide the first network entity 410 with the identifier of the O-RU 230 to identify the O-RU 230 in the cell #1.
  • the identifier of the O-RU 230 may comprise an identifier of an O-RU instance.
  • the identifier of the O-RU instance is configured by a controller of the O-RU 230.
  • the controller of the O-RU 230 is a network function that is permitted to control the configuration of an O-RU, e.g., SMO.
  • the identifier of the O-RU 230 may comprise an identifier of a component carrier.
  • the O-RU 230 is associated with the component carrier for a cell.
  • the identifier of the component carrier may comprise one of the following: a sector carrier ID, a sector ID, or a transmission point ID.
  • the identifier of the O-RU 230 may comprise information about a first port of the first network entity 410 connected to a second port of the O-RU 230.
  • the first port of the first network entity 410 is the end of a transport link in the first network entity 410, and it is connected to a dedicated port of an O-RU.
  • the information about the first port of the first network entity 410 may comprise at least one of the following: Ethernet address, virtual local area network (VLAN) ID, or internet protocol (IP) address.
  • Ethernet address virtual local area network
  • IP internet protocol
  • Fig. 7 illustrates an example of connections between the first network entity 410 and O-RUs in accordance with aspects of the present disclosure.
  • the first port of the first network entity 410 with an Ethernet address (e.g., MAC address) of eth0 is connected to the second port of the O-RU 230 with an Ethernet address (e.g., MAC address) of eth20.
  • an Ethernet address e.g., MAC address
  • the first network entity 410 may also provide mapping between an identifier of a cell and the identifier of the O-RU 230.
  • the cell is realized by the multiple O-RUs comprising the O-RU 230.
  • the second network entity 420 may reply 625 with an E2 SETUP RESPONSE message.
  • the second network entity 420 may transmit 630 a RIC SUBSCRIPTION REQUEST message to the first network entity 410.
  • the RIC SUBSCRIPTION REQUEST message may comprise the RIC Action Definition for O-NRCellDU, wherein the RIC Action Definition for O-NRCellDU comprises the attributes of the O-RU 230.
  • the RIC SUBSCRIPTION REQUEST message may also comprise the identifier of the O-RU 230.
  • Table 3 gives an example of the RIC Action Definition for O-NRCellDU comprising the attributes of the O-RU 230.
  • the RIC Action Definition for O-NRCellDU comprises the O-RUConfigList IE
  • the O-RUConfigList IE is used to represent a list of O-RUConfig.
  • the O-RUConfigList IE may comprise the information as shown in Table 1.
  • the O-RUConfig IE may comprise the information as shown in Table 2.
  • the O-RU configuration for the O-RU 230 included in the RIC SUBSCRIPTION REQUEST message comprises the RF channel configuration
  • the RF channel configuration comprises the TRX control configuration
  • the TRX control configuration comprises a mask name for antenna array elements and an antenna mask for the antenna array elements.
  • the O-RU configuration for the O-RU 230 included in the RIC SUBSCRIPTION REQUEST message comprises the sleep mode configuration
  • the sleep mode configuration comprises the sleep mode type and the wakeup duration for the sleep mode type. This means that the first network entity 410 wants to obtain values of the sleep mode type and the wakeup duration for the sleep mode type.
  • the first network entity 410 may transmit 635 a RIC SUBSCRIPTION RESPONSE message back to the second network entity 420.
  • the first network entity 410 detects 640 a RIC Event Trigger. For example, if the first network entity 410 detects that the RIC SUBSCRIPTION REQUEST message comprises the O-RU configuration, the first network entity 410 may determine that the RIC Event Trigger is detected. In one example, if a configuration change on the O-RU occurs, the RIC Event Trigger is detected. In another example, the RIC Event Trigger is detected in a specified period of time.
  • the first network entity 410 may transmit 645 a RIC INDICATION message to the second network entity 420.
  • the RIC INDICATION message may comprise the value of the O-RU configuration for the O-RU 230.
  • the O-RU configuration for the O-RU 230 included in the RIC SUBSCRIPTION REQUEST message in the action 630 comprises the RF channel configuration
  • the RF channel configuration comprises the TRX control configuration
  • the TRX control configuration comprises a mask name for antenna array elements and an antenna mask for the antenna array elements.
  • the first network entity 410 wants to obtain values of the mask name and the antenna mask for the antenna array elements.
  • the RIC INDICATION message comprises the values of the mask name and the antenna mask for the antenna array elements.
  • the O-RU configuration for the O-RU 230 included in the RIC SUBSCRIPTION REQUEST message in the action 630 comprises the sleep mode configuration
  • the sleep mode configuration comprises the sleep mode type and the wakeup duration for the sleep mode type.
  • the first network entity 410 wants to obtain values of the sleep mode type and the wakeup duration for the sleep mode type.
  • the RIC INDICATION message comprises the values of the sleep mode type and the wakeup duration for the sleep mode type.
  • the RIC INDICATION message may also contain the mapping between the cell ID and the identifier of the O-RU 230 if the RIC SUBSCRIPTION REQUEST message in the action 630 does not include the identifier of the O-RU 230.
  • the second network entity 420 may transmit 650 a RIC CONTROL REQUEST message to the first network entity 410.
  • the RIC CONTROL REQUEST message may comprise the guide configuration for the O-RU 230.
  • the guide configuration for the O-RU 230 may comprise at least one sleep mode for at least one TRX array of the O-RU 230 to be applied.
  • the TRX array is a transmitter array or a receiver array.
  • the guide configuration for the O-RU 230 may further comprise information about time when the at least one sleep mode for the at least one TRX array of the O-RU 230 is to be applied.
  • the information about time comprise slot numbers and symbol numbers.
  • the guide configuration for the O-RU 230 may further comprise at least one condition for the at least one sleep mode for the at least one TRX array of the O-RU 230 to be applied.
  • the guide configuration for the O-RU 230 may comprise an indication indicating at least one antenna array element of the O-RU 230 is to be switched off during a period.
  • the first network entity 410 Upon receiving the guide configuration for the O-RU 230, the first network entity 410 transmits 655, based on the guide configuration, a command to the O-RU 230 to save energy of the O-RU 230. For example, the first network entity 410 may transmit the command by transmitting a section type 4 command to the O-RU 230.
  • the command may be a CARRIER-COMMAND to disable a carrier in the O-RU 230.
  • the command may be an ARRAY-COMMAND to disable a TRX array (tx-array or rx-array) in the O-RU 230.
  • the command may be an O-RU-COMMAND to disable the O-RU 230, i.e., all TRX arrays (tx-arrays or rx-arrays) in the O-RU 230.
  • the first network entity 410 may transmit 660 an O-RU information retrieval request to the O-RU 230.
  • the O-RU 230 may transmit 665 an O-RU information retrieval reply to the first network entity 410.
  • the O-RU information retrieval reply comprises the latest O-RU configuration for the O-RU 230.
  • the first network entity 410 may transmit 670 a RIC CONTROL ACKNOWLEDGE message to the second network entity 420.
  • the RIC CONTROL ACKNOWLEDGE message comprises the latest O-RU configuration for the O-RU 230, i.e., the current value of the O-RU configuration for the O-RU 230.
  • the actions 610 and 615 are optional. That is, the actions 610 and 615 may not be performed.
  • the first network entity 410 may obtain the O-RU configuration and the identifier of the O-RU 230 from the SMO.
  • Fig. 8 illustrates a signaling diagram of an example process 800 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the process 800 may be considered as another example implementation of the process 500.
  • the process 800 may implement aspects of the wireless communications systems as described herein with reference to Figs. 1 through 3B, respectively.
  • the process 800 may involve the first network entity 410, the second network entity 420 and the O-RU 230 in Fig. 4.
  • a new cell-level RAN configuration structure is defined to represent the O-RU configuration.
  • the first network entity 410 may transmit, to the second network entity 420, a cell level configuration using the E2SM-CCC function.
  • the cell level configuration may comprise the O-RU configuration for the O-RU 230.
  • the first network entity 410 may be implemented as the first network entity 410 210 in Fig. 2, and the second network entity 420 may be implemented as the Near-RT RIC 220 in Fig. 2.
  • an identifier of a cell is associated with the O-RU configuration.
  • the actions 610, 615, 625, 635, 640, 645, 650, 655, 660, 665 and 670 in the process 800 are the same as those in the process 600. Details of such actions are omitted for brevity.
  • actions 620 and 630 in the process 600 are not performed in the process 800. Instead, actions 810 and 820 are performed in the process 800.
  • the first network entity 410 may transmit 810 a RAN Function Definition for cell level RAN Configuration Structure comprising O-RU attributes to the second network entity 420 by transmitting an E2 SETUP REQUEST message.
  • the RAN Function Definition for cell level RAN Configuration Structure may comprise attributes of one or more O-RU configurations.
  • Each O-RU configuration may be associated with an identifier of a cell and/or an identifier of an O-RU.
  • the identifier of the O-RU is used to identify the O-RU in the shared cell scenario.
  • the implementations of the O-RU configuration and the identifier of the O-RU have described with reference to Fig. 6. Details of such implementations are omitted for brevity.
  • the identifier of the cell is used to identify the cell in the shared O-RU scenario.
  • the O-DU 210 provides a first cell and the O-DU 212 provides a second cell
  • the O-RU 230 is configured to operate with the O-DUs 210 and 212.
  • the O-RU configuration for the O-RU 230 may be associated with an identifier of the first cell to identify the RAN Function Definition for cell level RAN Configuration Structure is for the first cell.
  • the O-RU configuration for the O-RU 230 may be associated with an identifier of the second cell to identify the RAN Function Definition for cell level RAN Configuration Structure is for the second cell.
  • the second network entity 420 may transmit 820 a RIC SUBSCRIPTION REQUEST message to the first network entity 410.
  • the RIC SUBSCRIPTION REQUEST message may comprise a RIC Action Definition for cell level RAN Configuration Structure including an O-RU IE.
  • the RIC SUBSCRIPTION REQUEST message may also comprise the identifier of the O-RU 230 and/or the identifier of the cell ID.
  • Table 4 gives an example of the RIC Action Definition for cell level RAN Configuration Structure.
  • the cell level RAN Configuration Structure comprises an O-RU IE and the O-RU IE comprises attributes of an O-RU.
  • Table 5 gives an example of the O-RU IE.
  • the O-RU IE comprises an O-RUConfig IE and the O-RUConfig IE comprises the O-RU configuration.
  • the O-RU configuration included in Table 5 are similar to those in Table 2. Details of the O-RU configuration are omitted for brevity.
  • Fig. 9 illustrates a signaling diagram of an example process 900 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the process 900 may be considered as another example implementation of the process 500.
  • the process 900 may implement aspects of the wireless communications systems as described herein with reference to Figs. 1 through 3B, respectively.
  • the process 900 may involve the first network entity 410, the second network entity 420 and the O-RU 230 in Fig. 4.
  • a new E2SM-CCC REPORT service style is defined to report O-RU level configuration information
  • a new RAN Function Definition is introduced to provide a complete list of all supported O-RU level RAN configuration structures and associated attributes.
  • the first network entity 410 may transmit, to the second network entity 420, an O-DU level configuration using the E2SM-CCC function.
  • the O-DU level configuration may comprise the O-RU configuration for the O-RU 230.
  • the first network entity 410 may be implemented as the first network entity 410 210 in Fig. 2
  • the second network entity 420 may be implemented as the Near-RT RIC 220 in Fig. 2.
  • the actions 610, 615, 625, 635, 640, 650, 655, 660, 665 and 670 in the process 900 are the same as those in the process 600. Details of such actions are omitted for brevity.
  • actions 620, 630 and 645 in the process 600 are not performed in the process 900. Instead, actions 910, 920 and 930 are performed in the process 900.
  • the first network entity 410 may transmit 910 a RAN Function Definition for O-RU to the second network entity 420 by transmitting an E2 SETUP REQUEST message.
  • the RAN Function Definition for O-RU may comprise attributes of one or more O-RU configurations.
  • Each O-RU configuration may be associated with an identifier of a cell and/or an identifier of an O-RU.
  • the identifier of the O-RU is used to identify the O-RU in the shared cell scenario, and the identifier of the cell is used to identify the cell in the shared O-RU scenario.
  • the implementations of the O-RU configuration and the identifier of the O-RU have described with reference to Fig. 6. Details of such implementations are omitted for brevity.
  • the second network entity 420 may transmit 920 a RIC SUBSCRIPTION REQUEST message to the first network entity 410.
  • the RIC SUBSCRIPTION REQUEST message may comprise a RIC Action Definition for O-RU.
  • the RIC SUBSCRIPTION REQUEST message may also comprise the identifier of the O-RU 230 and/or the identifier of the cell.
  • Table 6 gives an example of the RIC Action Definition for O-RU.
  • the RIC Action Definition for O-RU comprises the O-RU configuration.
  • the O-RU configuration included in Table 6 are similar to those in Table 2. Details of the O-RU configuration are omitted for brevity.
  • the first network entity 410 may transmit 930 a RIC INDICATION message to the second network entity 420.
  • the RIC INDICATION message may comprise the value of O-RU configuration.
  • the RIC INDICATION message may also comprise the mapping between the identifier of the cell and the identifier of the O-RU 230 if the RIC SUBSCRIPTION REQUEST message in the action 920 does not include the identifier of the O-RU 230.
  • Table 7 gives an example of the RIC INDICATION message for O-RU configuration report.
  • the RIC INDICATION message comprises an “Values of Attributes” IE and the “Values of Attributes” IE may comprise the value of O-RU configuration for the O-RU 230.
  • the O-RU configuration for the O-RU 230 included in the RIC SUBSCRIPTION REQUEST message in the action 920 comprises the RF channel configuration
  • the RF channel configuration comprises the TRX control configuration
  • the TRX control configuration comprises a mask name for antenna array elements and an antenna mask for the antenna array elements.
  • the first network entity 410 wants to obtain values of the mask name and the antenna mask for the antenna array elements.
  • the “Values of Attributes” IE comprises the values of the mask name and the antenna mask for the antenna array elements.
  • Fig. 10 illustrates an example of a device 1000 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the device 1000 may be an example of the first network entity 410 or the second network entity 420 as described herein.
  • the device 1000 may support wireless communication with one or more network entities 102, UEs 104, or any combination thereof.
  • the device 1000 may include components for bi-directional communications including components for transmitting and receiving communications, such as a processor 1002, a memory 1004, a transceiver 1006, and, optionally, an I/O controller 1008. These components may be in electronic communication or otherwise coupled (e.g., operatively, communicatively, functionally, electronically, electrically) via one or more interfaces (e.g., buses) .
  • the processor 1002, the memory 1004, the transceiver 1006, or various combinations thereof or various components thereof may be examples of means for performing various aspects of the present disclosure as described herein.
  • the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may support a method for performing one or more of the operations described herein.
  • the processor 1002, the memory 1004, the transceiver 1006, or various combinations or components thereof may be implemented in hardware (e.g., in communications management circuitry) .
  • the hardware may include a processor, a digital signal processor (DSP) , an application-specific integrated circuit (ASIC) , a field-programmable gate array (FPGA) or other programmable logic device, a discrete gate or transistor logic, discrete hardware components, or any combination thereof configured as or otherwise supporting a means for performing the functions described in the present disclosure.
  • the processor 1002 and the memory 1004 coupled with the processor 1002 may be configured to perform one or more of the functions described herein (e.g., executing, by the processor 1002, instructions stored in the memory 1004) .
  • the processor 1002 may support wireless communication at the device 1000 in accordance with examples as disclosed herein.
  • the processor 1002 may be configured to operable to support a means for performing the following: receiving a guide configuration for an O-RU from a second network entity, wherein the guide configuration is used to save energy of the O-RU; and transmitting, based on the guide configuration for the O-RU, a command to the O-RU to save energy of the O-RU.
  • the processor 1002 may be configured to operable to support a means for performing the following: receiving an O-RU configuration for the O-RU using an E2 service model cell configuration and control (E2SM-CCC) function of a first network entity from the first network entity, wherein the first network entity is connected to the O-RU; and transmitting a guide configuration for the O-RU via the transceiver to the first network entity, wherein the guide configuration is used to save energy of the O-RU.
  • E2SM-CCC E2 service model cell configuration and control
  • the processor 1002 may include an intelligent hardware device (e.g., a general-purpose processor, a DSP, a CPU, a microcontroller, an ASIC, an FPGA, a programmable logic device, a discrete gate or transistor logic component, a discrete hardware component, or any combination thereof) .
  • the processor 1002 may be configured to operate a memory array using a memory controller.
  • a memory controller may be integrated into the processor 1002.
  • the processor 1002 may be configured to execute computer-readable instructions stored in a memory (e.g., the memory 1004) to cause the device 1000 to perform various functions of the present disclosure.
  • the memory 1004 may include random access memory (RAM) and read-only memory (ROM) .
  • the memory 1004 may store computer-readable, computer-executable code including instructions that, when executed by the processor 1002 cause the device 1000 to perform various functions described herein.
  • the code may be stored in a non-transitory computer-readable medium such as system memory or another type of memory.
  • the code may not be directly executable by the processor 1002 but may cause a computer (e.g., when compiled and executed) to perform functions described herein.
  • the memory 1004 may include, among other things, a basic I/O system (BIOS) which may control basic hardware or software operation such as the interaction with peripheral components or devices.
  • BIOS basic I/O system
  • the I/O controller 1008 may manage input and output signals for the device 1000.
  • the I/O controller 1008 may also manage peripherals not integrated into the device M02.
  • the I/O controller 1008 may represent a physical connection or port to an external peripheral.
  • the I/O controller 1008 may utilize an operating system such as or another known operating system.
  • the I/O controller 1008 may be implemented as part of a processor, such as the processor 1002.
  • a user may interact with the device 1000 via the I/O controller 1008 or via hardware components controlled by the I/O controller 1008.
  • the device 1000 may include a single antenna 1010. However, in some other implementations, the device 1000 may have more than one antenna 1010 (i.e., multiple antennas) , including multiple antenna panels or antenna arrays, which may be capable of concurrently transmitting or receiving multiple wireless transmissions.
  • the transceiver 1006 may communicate bi-directionally, via the one or more antennas 1010, wired, or wireless links as described herein.
  • the transceiver 1006 may represent a wireless transceiver and may communicate bi- directionally with another wireless transceiver.
  • the transceiver 1006 may also include a modem to modulate the packets, to provide the modulated packets to one or more antennas 1010 for transmission, and to demodulate packets received from the one or more antennas 1010.
  • the transceiver 1006 may include one or more transmit chains, one or more receive chains, or a combination thereof.
  • a transmit chain may be configured to generate and transmit signals (e.g., control information, data, packets) .
  • the transmit chain may include at least one modulator for modulating data onto a carrier signal, preparing the signal for transmission over a wireless medium.
  • the at least one modulator may be configured to support one or more techniques such as amplitude modulation (AM) , frequency modulation (FM) , or digital modulation schemes like phase-shift keying (PSK) or quadrature amplitude modulation (QAM) .
  • the transmit chain may also include at least one power amplifier configured to amplify the modulated signal to an appropriate power level suitable for transmission over the wireless medium.
  • the transmit chain may also include one or more antennas 1010 for transmitting the amplified signal into the air or wireless medium.
  • a receive chain may be configured to receive signals (e.g., control information, data, packets) over a wireless medium.
  • the receive chain may include one or more antennas 1010 for receive the signal over the air or wireless medium.
  • the receive chain may include at least one amplifier (e.g., a low-noise amplifier (LNA) ) configured to amplify the received signal.
  • the receive chain may include at least one demodulator configured to demodulate the receive signal and obtain the transmitted data by reversing the modulation technique applied during transmission of the signal.
  • the receive chain may include at least one decoder for decoding the processing the demodulated signal to receive the transmitted data.
  • Fig. 11 illustrates a flowchart of a method 1100 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the operations of the method 1100 may be implemented by a device or its components as described herein.
  • the operations of the method 1100 may be performed by the first network entity 410 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving a guide configuration for an O-RU from a second network entity, wherein the guide configuration is used to save energy of the O-RU.
  • the operations of 1110 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1110 may be performed by a device as described with reference to Fig. 1, 2, 3A or 3B.
  • the method may include transmitting, based on the guide configuration for the O-RU, a command to the O-RU to save energy of the O-RU.
  • the operations of 1120 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1120 may be performed by a device as described with reference to Fig. 1, 2, 3A or 3B.
  • Fig. 12 illustrates a flowchart of a method 1200 that supports O-RU configuration and control in an O-RAN in accordance with aspects of the present disclosure.
  • the operations of the method 1200 may be implemented by a device or its components as described herein.
  • the operations of the method 1200 may be performed by the second network entity 420 as described herein.
  • the device may execute a set of instructions to control the function elements of the device to perform the described functions. Additionally, or alternatively, the device may perform aspects of the described functions using special-purpose hardware.
  • the method may include receiving an O-RU configuration for the O-RU using an E2 service model cell configuration and control (E2SM-CCC) function of a first network entity from the first network entity, wherein the first network entity is connected to the O-RU.
  • E2SM-CCC E2 service model cell configuration and control
  • the operations of 1210 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1210 may be performed by a device as described with reference to Fig. 1, 2, 3A or 3B.
  • the method may include transmitting a guide configuration for the O-RU via the transceiver to the first network entity, wherein the guide configuration is used to save energy of the O-RU.
  • the operations of 1220 may be performed in accordance with examples as described herein. In some implementations, aspects of the operations of 1220 may be performed by a device as described with reference to Fig. 1, 2, 3A or 3B.
  • a general-purpose processor may be a microprocessor, but in the alternative, the processor may be any processor, controller, microcontroller, or state machine.
  • a processor may also be implemented as a combination of computing devices (e.g., a combination of a DSP and a microprocessor, multiple microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.
  • the functions described herein may be implemented in hardware, software executed by a processor, firmware, or any combination thereof. If implemented in software executed by a processor, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium. Other examples and implementations are within the scope of the disclosure and appended claims. For example, due to the nature of software, functions described herein may be implemented using software executed by a processor, hardware, firmware, hardwiring, or combinations of any of these. Features implementing functions may also be physically located at various positions, including being distributed such that portions of functions are implemented at different physical locations.
  • Computer-readable media includes both non-transitory computer storage media and communication media including any medium that facilitates transfer of a computer program from one place to another.
  • a non-transitory storage medium may be any available medium that may be accessed by a general-purpose or special-purpose computer.
  • non-transitory computer-readable media may include RAM, ROM, electrically erasable programmable ROM (EEPROM) , flash memory, compact disk (CD) ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other non-transitory medium that may be used to carry or store desired program code means in the form of instructions or data structures and that may be accessed by a general-purpose or special-purpose computer, or a general-purpose or special-purpose processor.
  • an article “a” before an element is unrestricted and understood to refer to “at least one” of those elements or “one or more” of those elements.
  • the terms “a, ” “at least one, ” “one or more, ” and “at least one of one or more” may be interchangeable.
  • a list of items indicates an inclusive list such that, for example, a list of at least one of A, B, or C means A or B or C or AB or AC or BC or ABC (i.e., A and B and C) .
  • the phrase “based on” shall not be construed as a reference to a closed set of conditions. For example, an example step that is described as “based on condition A” may be based on both a condition A and a condition B without departing from the scope of the present disclosure.
  • a “set” may include one or more elements.

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

Divers aspects de la présente divulgation concernent la configuration et la commande d'une O-RU dans un O-RAN. Selon un aspect, une première entité réseau reçoit une configuration de guidage pour une O-RU depuis une seconde entité réseau. La configuration de guidage est utilisée pour économiser l'énergie de l'O-RU. À son tour, la première entité réseau transmet, sur la base de la configuration de guidage pour l'O-RU, une instruction à l'O-RU pour économiser de l'énergie de l'O-RU.
PCT/CN2024/107980 2024-07-26 2024-07-26 Configuration et commande de o-ru dans un o-ran Pending WO2025118635A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/107980 WO2025118635A1 (fr) 2024-07-26 2024-07-26 Configuration et commande de o-ru dans un o-ran

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/CN2024/107980 WO2025118635A1 (fr) 2024-07-26 2024-07-26 Configuration et commande de o-ru dans un o-ran

Publications (1)

Publication Number Publication Date
WO2025118635A1 true WO2025118635A1 (fr) 2025-06-12

Family

ID=95981481

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2024/107980 Pending WO2025118635A1 (fr) 2024-07-26 2024-07-26 Configuration et commande de o-ru dans un o-ran

Country Status (1)

Country Link
WO (1) WO2025118635A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220407664A1 (en) * 2021-06-10 2022-12-22 Samsung Electronics Co., Ltd. Method and apparatus for energy saving in a wireless communication system using an open radio access network
WO2023157334A1 (fr) * 2022-02-15 2023-08-24 楽天モバイル株式会社 Notification d'informations d'économie d'énergie d'o-ru
WO2024072441A1 (fr) * 2022-09-27 2024-04-04 Rakuten Mobile, Inc. Système et procédé d'optimisation de reconfiguration de canal radiofréquence dans un réseau de télécommunications
CN118285147A (zh) * 2021-11-12 2024-07-02 瑞典爱立信有限公司 无线电接入网（ran）节点的功耗管理
WO2024145425A1 (fr) * 2022-12-28 2024-07-04 Rakuten Mobile Usa Llc Mise en œuvre d'un mode veille et/ou d'un procédé de commande de trx dans une unité radio dans un réseau de télécommunication

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20220407664A1 (en) * 2021-06-10 2022-12-22 Samsung Electronics Co., Ltd. Method and apparatus for energy saving in a wireless communication system using an open radio access network
CN118285147A (zh) * 2021-11-12 2024-07-02 瑞典爱立信有限公司 无线电接入网（ran）节点的功耗管理
WO2023157334A1 (fr) * 2022-02-15 2023-08-24 楽天モバイル株式会社 Notification d'informations d'économie d'énergie d'o-ru
WO2024072441A1 (fr) * 2022-09-27 2024-04-04 Rakuten Mobile, Inc. Système et procédé d'optimisation de reconfiguration de canal radiofréquence dans un réseau de télécommunications
WO2024145425A1 (fr) * 2022-12-28 2024-07-04 Rakuten Mobile Usa Llc Mise en œuvre d'un mode veille et/ou d'un procédé de commande de trx dans une unité radio dans un réseau de télécommunication

Similar Documents

Publication Publication Date Title
CN115245026B (zh) 在非活跃状态中至分解式基站的小数据传输
WO2024169800A1 (fr) Établissement de session pdu
US20240214923A1 (en) Dynamic adaptation of a sleep cycle for a cell
EP4378270B1 (fr) Sélection de terminaison assistée par équipement utilisateur (ue) pour une connectivité non autonome ou double
WO2025118635A1 (fr) Configuration et commande de o-ru dans un o-ran
CN119605101A (zh) 非陆地网络中的寻呼早期指示
CN119014059A (zh) 用于绿色网络的用户装备辅助信息和缓冲区状态报告扩展
WO2025060462A1 (fr) Continuité de support d'une tâche d'ia initiée par un nœud ran pendant la mobilité
WO2024093370A1 (fr) Obtention de rapport d'accès aléatoire pour noeud secondaire
WO2024212558A1 (fr) Rejet basé sur l'importance d'un ensemble d'unités de données de protocole
WO2025175845A1 (fr) Contrôle de la consommation d'énergie
WO2024169553A1 (fr) Détermination de signal de liaison descendante
WO2025246425A1 (fr) Gestion de ressource
WO2024198604A1 (fr) Alimentation en énergie pour dispositif sans batterie
WO2024230254A1 (fr) Procédé de demande de signal de liaison descendante
WO2024207740A1 (fr) Mobilité déclenchée de couche 1 ou de couche 2
US20250351219A1 (en) Techniques to support network-controlled repeater functionality for discontinuous communications
WO2024159839A1 (fr) Commande de puissance de transmissions psfch
WO2025241073A1 (fr) Économie d'énergie de faisceau de satellite dans un ntn
WO2024212567A1 (fr) Transmission de préambule prach déclenchée par une instruction de commutation de cellules
WO2024222051A1 (fr) Détermination de nœud d'onde porteuse
WO2024094228A1 (fr) Procédure de défaillance de trajet indirect en multi-trajet
WO2024093341A1 (fr) Prise en charge d'assurance de sla pour tranche de ran
WO2025236737A1 (fr) Communication de lp-wus
WO2024234751A1 (fr) Rejet basé sur fec

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 24899285

Country of ref document: EP

Kind code of ref document: A1