WO2024253956A1 - Fourniture de politiques d'économies d'énergie o-ran - Google Patents

Fourniture de politiques d'économies d'énergie o-ran Download PDF

Info

Publication number
WO2024253956A1
WO2024253956A1 PCT/US2024/031830 US2024031830W WO2024253956A1 WO 2024253956 A1 WO2024253956 A1 WO 2024253956A1 US 2024031830 W US2024031830 W US 2024031830W WO 2024253956 A1 WO2024253956 A1 WO 2024253956A1
Authority
WO
WIPO (PCT)
Prior art keywords
policy
energy
saving
objective
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.)
Ceased
Application number
PCT/US2024/031830
Other languages
English (en)
Inventor
Pankaj Tanaji SHETE
Awn Muhammad
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.)
Rakuten Symphony Inc
Rakuten Symphony Usa LLC
Original Assignee
Rakuten Symphony Inc
Rakuten Symphony Usa LLC
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 Rakuten Symphony Inc, Rakuten Symphony Usa LLC filed Critical Rakuten Symphony Inc
Priority to EP24819816.0A priority Critical patent/EP4721359A1/fr
Priority to CN202480037605.XA priority patent/CN121241548A/zh
Priority to KR1020257040029A priority patent/KR20260005370A/ko
Publication of WO2024253956A1 publication Critical patent/WO2024253956A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/34—Signalling channels for network management communication
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/06—Management of faults, events, alarms or notifications
    • H04L41/0677—Localisation of faults
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H04L41/0833—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability for reduction of network energy consumption
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0894—Policy-based network configuration management
    • 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
    • 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 the provisioning of one or more energy-saving policies of the open radio access network (0-RAN).
  • a radio access network is an important component in a telecommunications system, as it connects end-user devices (or user equipment) to other parts of the network.
  • the RAN includes a combination of various network elements (NEs) that connect end-users to a core network.
  • NEs network elements
  • hardware and/or software of a particular RAN is vendor specific.
  • Open RAN Open RAN
  • CU central unit
  • DU distributed unit
  • RU radio unit
  • Example embodiments of the present disclosure provide systems, apparatuses, methods, and the like, that facilitate the provisioning of one or more energy-saving policies of the O-RAN
  • a system may include a non-real-time (Non- RT) radio access network intelligent controller (RIC).
  • the Non-RT RIC may be configured to obtain a policy schema and then generate at least one energy-saving policy based on the policy schema for execution by a near-real-time (Near-RT) RIC.
  • the at least one energy-saving policy may include at least one policy scope identifier specifying at least one node to which the energysaving policy is applied, at least one policy objective specifying an energy-saving target, and at least one policy resource specifying a condition for resource usage for the energy-saving policy.
  • the Non-RT RIC may be configured to provide, to the Near-RT RIC via an Al interface, the at least one energy-saving policy.
  • a method may include: obtaining a policy schema, generating at least one energy-saving policy based on the policy schema for execution by a near-real-time (Near-RT) radio access network intelligent controller (RIC), and providing the at least one energy-saving policy to the Near-RT RIC via an Al interface.
  • the at least one energy- saving policy may include at least one policy scope identifier specifying at least one node to which the energy-saving policy is applied, at least one policy objective specifying an energy-saving target, and at least one policy resource specifying a condition for resource usage for the energy-saving policy.
  • a non-transitory computer-readable recording medium may have recorded thereon instructions executable by a system that comprises a non-real- time (Non-RT) radio access network intelligent controller (RIC) to cause the Non-RT RIC to perform a method.
  • the method may include: obtaining a policy schema, generating at least one energy-saving policy based on the policy schema for execution by a near-real-time (Near-RT) RIC, and providing the at least one energy-saving policy to the Near-RT RIC via an Al interface.
  • the at least one energy-saving policy may include at least one policy scope identifier specifying at least one node to which the energy-saving policy is applied, at least one policy objective specifying an energy-saving target, and at least one policy resource specifying a condition for resource usage for the energy-saving policy.
  • FIG. 1 illustrates an 0-RAN architecture in which one or more example embodiments may be applied;
  • FIG. 2 illustrates a block diagram of an example energy-saving policy, according to one or more example embodiments;
  • FIG. 3 illustrates a block diagram of various types of energy-saving policies, according to one or more example embodiments
  • FIG. 4 illustrates a flow diagram of an example method for provisioning one or more energy-saving policies, according to one or more example embodiments.
  • FIG. 5 illustrates a diagram of example components of a device for implementing one or more example embodiments.
  • descriptions of example embodiments of the present disclosure may include terms and names defined in one or more standard organizations, such as the 3rd Generation Partnership Project (3GPP) standard organization, the European
  • the RAN may be disaggregated into multiple nodes or entities.
  • the RAN functions may be disaggregated into multiple logical nodes or entities, such as a central unit (CU), a distributed unit (DU), and a radio unit (RU).
  • the CU may be a logical node for hosting Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and/or Packet Data Convergence Protocol (PDCP) sublayers of the RAN.
  • RRC Radio Resource Control
  • SDAP Service Data Adaptation Protocol
  • PDCP Packet Data Convergence Protocol
  • the DU may be a logical node hosting Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers of the RAN.
  • RLC Radio Link Control
  • MAC Media Access Control
  • PHY Physical
  • a single DU may host or serve multiple network cells formed by multiple RUs.
  • the RU may be a physical node that converts radio signals from antennas to digital signals that can be transmitted over the Front Haul to a DU.
  • a network cell may correspond to one or more radio units responsible for providing wireless coverage and signal transmission within the network cell.
  • network energy-saving is an important aspect of 0-RAN in order to optimize energy efficiency, reduce operating costs, and minimize carbon footprint, while maintaining high network performance and ensuring high quality of service (QoS).
  • QoS quality of service
  • the concept of policy-based carrier and cell switch off/on for energy-saving has been introduced. Nevertheless, the specific contents of the policies involved, and the specific mechanisms for provisioning such policies, are not specified or defined in the related art.
  • entities from different vendors may be involved in the 0-RAN architecture, it is crucial to define and specify the policies for energy-saving in a standardized manner, such that entities from different vendors can understand the policies and operate accordingly for energysaving.
  • Example embodiments of the present disclosure provide a system, a method, a device, and the like, that facilitate the provisioning of one or more energy-saving policies, in a standardized manner.
  • example embodiments of the present disclosure introduce an energy-saving policy schema and leverage the non-real-time (Non-RT) radio access network intelligent controller (RIC) to generate various types of energy-saving policy based on the energysaving policy schema.
  • Non-RT radio access network intelligent controller
  • Each of the types of energy-saving policy contains novel attributes or parameters that satisfy different network requirements, scenarios and use cases in O-RAN.
  • the example embodiments of the present disclosure may also be implemented by any suitable modules or entities in the O-RAN, without departing from the scope of the present disclosure.
  • the Non-RT RIC may utilize the policy schema to generate and provide one or more energysaving policies to the near-real-time (Near-RT) RIC
  • any other suitable modules or entities in any suitable systems e.g., O-RAN systems, 3GPP systems, 5G systems, 6G systems, etc.
  • any suitable modules or entities in any suitable systems e.g., O-RAN systems, 3GPP systems, 5G systems, 6G systems, etc.
  • any suitable modules or entities in any suitable systems e.g., O-RAN systems, 3GPP systems, 5G systems, 6G systems, etc.
  • FIG. 1 illustrates an O-RAN architecture in which one or more example embodiments may be applied.
  • the system architecture may include at least one Service Management and Orchestration (SMO) framework 110 that includes at least one non- real-time RAN Intelligent Controller (Non-RT RIC) 120, at least one near-real-time RIC (Near- RT RIC) 130, at least one O-RAN Central Unit (O-CU) 140, at least open evolved NodeB (O-eNB) 150, at least one O-RAN Distributed Unit (O-DU) 160, a plurality of O-RAN Radio Units (O-RUs) 170, and at least one O-RAN Cloud (O-Cloud) 180.
  • SMO Service Management and Orchestration
  • the components may be communicatively coupled to another component(s) via a respective interface(s).
  • system may include more/fewer components than illustrated, and/or may be configured in a different manner, without departing from the scope of the present disclosure.
  • system architecture may include a plurality of O-DUs 160 each of which is communicatively coupled to the O-CU 140, and the like.
  • the RIC may be a software-defined component that implements modular applications to facilitate multivendor operability, as well as to automate and optimize RAN operations.
  • the RIC may be divided into two types, i.e., the Non-RT RIC 120 and the Near-RT RIC 130.
  • the Non-RT RIC 120 are provided, followed by the descriptions of the Near-RT RIC 130.
  • Non-RT RIC 120 may refer to a logical function within the SMO framework
  • the Al interface may refer to a logical interface between the Non-RT RIC 120 and the Near-RT RIC 130, which enables the Non-RT RIC 120 to provide policy-based guidance to the Near-RT RIC 130 and enables the Near-RT RIC 130 to provide one or more feedback to the Non-RT RIC 120 thereby enabling the Non-RT RIC 120 to monitor the status or implementation of one or more policies.
  • the Non-RT RIC 120 may be the control point of a non-real-time control loop and may operate on a timescale greater than 1 second within the SMO framework 110.
  • the functionalities of the Non-RT RIC 120 may include, for example, providing policy-based guidance and enrichment across the Al interface, performing data analytics, Artificial Intelligence/Machine Learning (AI/ML) models training and inference for RAN optimization, and/or recommending configuration management actions.
  • the Non-RT RIC 120 may also be configured to generate and provide one or more energy-saving policies to the Near-RT RIC 130. Further, the Non-RT RIC 120 may access or communicate with other SMO framework functionalities or components via Al interface, 01 interface, 02 interface, and one or more interfaces associated with one or more open fronthaul planes.
  • the functionalities of the Non-RT RIC 120 may be implemented through at least one modular, Non-RT RIC application, such as the rApp 121.
  • the rApp 121 may leverage the functionalities available in the SMO framework 110 and/or the Non-RT RIC 120 to provide value-added services related to RAN operation and optimization, such as policy management, radio resource management, data analytics, and providing enrichment information.
  • the Non-RT RIC 120 may implement a plurality of rApps 121 .
  • the Non-RT RIC 120 may be configured to generate and provide one or more policies to the Near- RT RIC 130 via the Al interface, and may be configured to manage one or more policies that are provided to the Near-RT RIC 130 over the Al interface.
  • Said policies may be referred to as “Al policies” herein, and are declarative policies that contain information applicable to one or more network nodes (e.g., one or more UEs, one or more network cells, etc.)
  • the one or more Al policies may consist of a scope identifier and one or more policy statements.
  • the scope identifier may specify or define the node(s) or entity(s) to which the policy is applied (e.g., cells, UEs, DUs, etc.)
  • the policy statements may define the targets, goals or objectives of the policy and may include information associated with one or more policy objectives and one or more policy resources.
  • at least a portion of the Al policies are associated with energy-saving operations (said policies may be referred to as “energy-saving policy” herein).
  • the Non-RT RIC 120 (or the rApp 121 associated therewith) may create and provide the one or more Al policies to the Near-RT RIC 130 for execution by the Near-RT RIC 130, thereby providing guidance to the Near-RT RIC 130 towards one or more objectives or goals defined in the RAN intent.
  • the RAN intent may refer to the high-level operational or business goal(s) to be achieved by the RAN, which may be defined by one or more desired service level agreements (SLAs) that the RAN is to fulfill for all users or for a subset of users in a given area over at least a predefined period of time.
  • SLAs service level agreements
  • the Non-RT RIC 120 (or the rApp 121 associated therewith) may be configured to perform one or more policy management operations to provide and manage one or more Al policies (e.g., energy-saving policy(s), etc.)
  • one or more Al policies e.g., energy-saving policy(s), etc.
  • Non-RT RIC 120 may be configured to generate, update, and delete one or more Al policies.
  • the Non-RT RIC 120 may manage the one or more Al policies to include information associated with energy-saving (examples of the information are further described below), and then provide the one or more Al policies to the Near-RT RIC 130 via the Al interface.
  • the Non-RT RIC 120 may be configured to receive, from the Near-RT RIC 130 viathe Al interface, one or more feedbacks associated with one or more Al policies (“Al policy feedback” herein).
  • the Non-RT RIC 120 may be configured to receive one or more observables (e.g., events, counters, etc.) provided by the O-CU 140, the O- eNB 150, the O-DU 160, and/or one or more of the O-RUs 170 over the 01 interface.
  • the Non-RT RIC 120 may be configured to continuously (or periodically) manage the one or more Al policies based on the Al policy feedback(s) and/or the observables provided over the 01 interface.
  • the Non-RT RIC 120 may continuously (or periodically) evaluate the impact or effectiveness of the one or more Al policies towards the fulfillment of the RAN intent and then configure or update the one or more Al policies accordingly.
  • the SMO framework 110 may communicate with the Near-RT RIC 130, the O-CU 140, the O-eNB 150, the O-DU 160, and the O-RU(s) 170 via the 01 interface.
  • the 01 interface may refer to a logical interface between the SMO framework 110, the Near-RT RIC 130, the O-CU 140, the O- eNB 150, the O-DU 160, and the O-RU(s) 170, which enables the SMO framework 110 (as well as the Non-RT RIC 120 and the rApp 121 implemented therein) to provide Fault, Configuration, Accounting, Performance, and Security (FCAPS) and other management operations, such as network monitoring, network discovery, and the like, to the Near-RT RIC 130, the O-CU 140, the O-eNB 150, the O-DU 160, and the O-RU(s) 170.
  • FCAPS Fault, Configuration, Accounting, Performance, and Security
  • the 01 interface enables the Near- RT RIC 130, the O-CU 140, the O-eNB 150, the O-DU 160, and the O-RU(s) 170 to provide information or observable(s) that may be utilized by the Non-RT RIC 120 (or the rApp 121 associated therewith) to manage one or more Al policies, to train one or more AI/ML models, and the like.
  • the SMO framework 110 (as well as the Non-RT RIC 120 and/or the rApp 121 implemented therein) may communicate with the O-Cloud 180 via the 02 interface.
  • the 02 interface may refer to a logical interface between the SMO framework 110 and the O-Cloud 180, which may be a collection of physical RAN nodes that host the Non-RT RIC 120, the Near-RT RIC 130, the O-CU 140, and the O-DU 160, the supporting software components (e g., the operating systems and runtime environments), and the SMO framework 110 itself.
  • the SMO framework 110 may manage the O-Cloud 180 from within, and the 02 interface may be the interface between the SMO framework 110 and the O-Cloud 180 it resides in.
  • the SMO framework 110 (as well as the Non-RT RIC 120 and/or the rApp 121 implemented therein) may provide infrastructure management services (IMS) and deployment management services (DMS) for the O-Cloud 180.
  • IMS infrastructure management services
  • DMS deployment management services
  • the SMO framework 110 (as well as the Non-RT RIC 120 and/or the rApp 121 implemented therein) may also communicate with the O-RU(s) 170 via an open fronthaul (O-FH) management plane (M-Plane) interface.
  • O-FH M-Plane may enable the SMO framework 110 (aswell as the Non-RT RIC 120 and/or the rApp 121 implemented therein) to perform one or more FCAPS operations on the O-RU(s) 170.
  • the Near-RT RIC 130 may refer to a logical function that enables near-real-time control and optimization of RAN elements and resources.
  • the Near-RT RIC 130 may provide near-real-time control and optimization via fine-grained (e.g., UE basis, Cell basis, etc.) data collection and actions over the E2 interface.
  • the Near-RT RIC 130 may operate on a timescale between 10 milliseconds and 1 second and may be coupled with the O-CU 140, the O- eNB 150, and the 0-DU 160 via the E2 interface.
  • the Near-RT RIC 130 may use the E2 interface to control the underlying RAN elements (E2 nodes/network functions (NFs)) over a near-real-time control loop.
  • E2 nodes/network functions (NFs) a near-real-time control loop.
  • the Near-RT RIC 130 may be configured to execute one or more Al policies provided by the Non-RT RIC 120 and then perform (based on the one or more Al policies) one or more energy-saving operations, such as switching a cell/carrier On/Off, handover a user from a cell to another cell, and the like. Further, the Near-RT RIC 130 may monitor, suspend/stop, override, and control the E2 nodes (e.g., O-CU 140, O-DU 160, etc.) via utilizing one or more Al policies.
  • the E2 nodes e.g., O-CU 140, O-DU 160, etc.
  • the Near-RT RIC 130 may receive the one or more Al policies (e.g., energy-saving policy(s), etc.) from the Non-RT RIC 120 (or the rApp 121 associated therewith), and then interpret the received Al policy(s) to determine one or more control operations (e.g., energy-saving operation(s), etc.) or one or more policy commands.
  • Al policies e.g., energy-saving policy(s), etc.
  • control operations e.g., energy-saving operation(s), etc.
  • the Near-RT RIC 130 may collect one or more measurement data from one or more E2 nodes (e.g., O-CU 140, O-eNB 150, O-DU 160, etc.) via the E2 interface, and then determine (e.g., by performing AI/ML inference based on the received Al policy(s) and the collected measurement data, etc.) the one or more control operations thereafter. Subsequently, the Near-RT RIC 130 may generate and send one or more control messages (e.g., Cell/Carrier Switch On/Off message, etc.) to one or more E2 nodes and/or one or more of the O-RUs 170. Accordingly, the E2 node(s) and/or the O-RU(s) may be configured to update their associated configurations to execute one or more operations to switch on/off the cell or carrier.
  • E2 node(s) and/or the O-RU(s) may be configured to update their associated configurations to execute one or more operations to switch on/off the cell or carrier.
  • the Near-RT RIC 130 may host or implement one or more applications, such as the xApp 131, to implement the associated functions or operations described herein.
  • the xApp 131 may consist of one or more microservices, which may be independent of the Near-RT RIC 130 and may be provided by any third party.
  • the E2 interface may enable a direct association between the xApp 131 and other RAN functionalities (e g., O-CU 140, O-eNB 150, O-DU 160, etc.), thereby enabling the xApp 131 to provide information or data to the RAN functionalities for further utilization.
  • the Near-RT RIC 130 may consist of multiple xApps 131 and a set of platform functions that are commonly used to support the specific functions hosted by the multiple xApps 131.
  • the Near-RT RIC platform may communicate with the xApp(s) 131 via one or more application programming interfaces (APIs). Further, the Near-RT RIC platform may be configured to route Al policy management messages to the registered xApps based on Al policy type and operator policies.
  • APIs application programming interfaces
  • the O-CU 140, the O-eNB 150, the O-DU 160, and the O- RU 170 may constitute a base station, such as a gNodeB (gNB) of 5G NR or a node in Next Generation Radio Access Network (NG-RAN), a base station of a 6G network, and the like.
  • gNB gNodeB
  • NG-RAN Next Generation Radio Access Network
  • the O-eNB the O-eNB
  • the communication between the O-CU 140 and the O-DU 160 may be performed via an Fl interface, while the communication between the O-DU 160 and the O-RU 170 may be performed via one or more O-FH Control (C), User (U), Synchronization (S), and Management (M) plane interfaces.
  • C O-FH Control
  • U User
  • S Synchronization
  • M Management
  • the C, U, and S planes may be consolidated and referred to as the “CUS-plane”.
  • the system may include a plurality of O-DUs 160, and the O-CU 140 may be communicatively coupled to the plurality of O-DUs via the Fl interface.
  • the system may include a plurality of O-RUs 170, and the O-DU(s) 160 may be communicatively coupled to the plurality of O-RUs via one or more of the O-FH C/U/S/M plane interfaces.
  • the O-CU 140 and the O-DU 160 may be defined in software form and may be deployed in one or more network nodes.
  • the O- CU 140 and the O-DU 160 may be deployed in one or more servers in the form of virtualized network function (VNF), containerized and/or cloud-native function (CNF), and the like.
  • VNF virtualized network function
  • CNF cloud-native function
  • the O-CU 140 and the O-DU 160 may be deployed in the same node (e.g., same server) and/or may be located at a similar geographical location (e.g., be deployed in different servers in the same data center).
  • the O-CU 140 and the O-DU 160 may be deployed in different nodes and/or may be located at different geographical locations.
  • the O-CU 140 may be deployed in one or more central servers (i.e., servers in one or more central data centers), and the O-DU 160 may be deployed in one or more edge servers (i.e., servers in one or more edge data centers).
  • the O-DU 160 may receive radio signals from an end user (via one or more UEs and one or more cells) and may provide operation or support for lower layers of protocol stacks
  • the O-DU 160 may perform one or more scheduling operations.
  • the O-CU 140 may communicatively couple the O-DU 160 to a core network (e.g., 4G Evolved Packet Core (EPC) network, 5G Core network, etc.) and may receive the radio signals from the O-DU 160, thereby providing operation or support for higher layers of protocol stacks (e g., PDCP layer, RRC layer, etc.) accordingly.
  • EPC Evolved Packet Core
  • the O-CU 140 may include an O-CU control plane (O-CU-CP) 141 and an O-CU user plane (O-CU-UP) 142.
  • the O-CU-CP 141 may refer to the logical node that hosts or implements the RRC and the control plane part of the PDCP protocol, and may be responsible for managing the signaling between the core network and the radio network, handling tasks such as session management, radio bearer control, and mobility management.
  • the O-CU-UP 142 may refer to the logical node that hosts or implements the user plane part of the PDCP protocol and the SDAP protocol, and may be responsible for managing the data traffic and the transmission of user data packets.
  • the O-CU-CP 141 and the O-CU-UP 142 may be coupled to each other via the El interface.
  • a single O-DU 160 may host or serve multiple network cells formed by multiple O-RUs 170.
  • the O-DU 160 may implement various radio technologies, such as massive multiple-input multiple-output (MIMO), beamforming, and the like, to optimize radio communication among the multiple cells and the O-CU 140.
  • MIMO massive multiple-input multiple-output
  • the O-DU 160 may concurrently host or serve hundreds (e.g., 512, etc.) of cells at a time.
  • the O-RU(s) 170 may be a physical node that converts radio signals from antennas to digital signals that can be transmitted over the Front Haul to the O-DU 160.
  • a network cell described herein may correspond to one or more radio units responsible for providing wireless coverage and signal transmission within the network cell.
  • the network cell may include a macro cell, a micro cell, a pi co cell, a femto cell, and/or any other suitable type of network cell.
  • Each of the cells may have an associated coverage area, in which at least one O-RU 170, at least one antenna system, and any other suitable type of transport network element (TNE), may be deployed therein.
  • TNE transport network element
  • the 0-DU 160 may be configured to control or instruct the associated O-RU(s) via one or more of the O-FH C/U/S/M plane interfaces.
  • the O-DU 160 may instruct the O-RU(s) 170 to shut down or enter sleep mode via the O-FH C/U/S plane interfaces.
  • the capability exchange between the SMO 110 and the O-RU(s) 170 may be performed via the O-FH M-plane interface.
  • the O- RU(s) 170 may inform the SMO 110 of the amount of time it requires to maintain in sleep mode (or off mode) in order to save an amount of energy, and the like.
  • example embodiments of the present disclosure introduce a mechanism for provisioning one or more energy-saving policies in the O-RAN architecture.
  • the Non-RT RIC 120 may be utilized to generate and provide various types of energysaving policies to the Near-RT RIC 130, and the Near-RT RIC 130 may utilize the energy-saving policies provided by the Non-RT RIC 120 to perform appropriate energy-saving operation(s). Further details of the energy-saving policies are provided in the following.
  • example embodiments of the present disclosure facilitate the provisioning of one or more energy-saving policies.
  • example embodiments provide a system that includes a Non-RT RIC (or an apparatus/device that implements the Non-RT RIC) configured to generate at least one energy-saving policy for execution by a Near-RT RIC and then provide the at least one energy-saving policy to the Near-RT RIC.
  • example embodiments introduce new attributes and parameters for defining and specifying various types of energy-saving policies. These new attributes and parameters supplement those specified for the Al policies in the current version of technical specifications provided by the standard organizations like the O-RAN Alliance (e g., 0-RAN.WG2.A1TD).
  • the Non-RT RIC may be configured to obtain a policy schema and then generate the at least one energy-saving policy based on the policy schema.
  • example embodiments introduce a new policy schema that include new attributes and parameters associated with energy-saving.
  • descriptions of the example energysaving policies and example policy schema, according to one or more example embodiments, are provided.
  • FIG. 2 illustrates a block diagram of an example energy-saving policy, according to one or more example embodiments.
  • the energy-saving policy includes information associated with at least one policy scope identifier, at least one policy objective, and at least one policy resource.
  • the policy objective and the policy resource may form a policy statement.
  • the information of the energy-saving policy may be represented in simple data types and structured data types.
  • the simple data types may refer to the basic data types that represent single parameters, such as integers, floating-point values, characters, and the like.
  • the structured data types may refer to a collection of data items that is organized in a structured manner.
  • the enumeration OperatorType (that represents the preference of a specific comparison operator) associated with the energy-saving policy may be defined in the following Table 2.
  • the scope identifier of the energy-saving policy may specify at least one node to which the energy-saving policy is applied or applicable.
  • the scope identifier may include information defining the target network entity or node such as one or more of a user equipment (UE) identifier (ID), a group ID associated with multiple UEs, a cell ID, a slice ID associated with a network slice, a network ID (e.g., public land mobile network (PLMN) ID, etc ), a gNodeB (gNB) ID, an O-RU ID, an O-DU ID, O-CU ID, a cell ID list comprises a plurality of cell IDs, a gNB ID list comprises a plurality of gNB IDs, an O-RU ID list comprises a plurality of O-RU IDs, an O-DU ID list comprises a plurality of O-DU IDs, an O-CU ID list comprises a plurality of O-CU IDs, a slice ID list comprises
  • the energy-saving policy may be specified and defined for optimizing energy efficiency in various network levels or layers (e.g., cell level, slice level, node level, network level, etc.)
  • the policy scope identifier may be defined in the form of structured data type and may be referred to as “Scopeidentifier”. It is contemplated that the policy scope identifier described herein may also be referred to or be defined in any other suitable terms, without departing from the scope of the present disclosure. In this regard, the policy scope identifier may contain one or more information or attributes as defined in the following Table 3.
  • condition “C” in Table 3 means that at least one attribute shall be included when the scope of the policy is defined.
  • the allowable combinations of attributes may depend on the policy statement (i.e., the policy objective and policy resource, etc.) that is combined with the scope identifier and may be policy type specific.
  • the policy objectives and policy resources may form one or more statements that define the targets, goals, or objectives of the energy-saving policy.
  • the definitions of structured data types or attributes that may be used in statements for policy objectives and/or statements for policy resources may be defined in the following Table 4.
  • condition “C” in Table 4 means that at least one attribute shall be included when the scope of the policy is defined.
  • condition “O” in Table 4 means that data type can be optionally included.
  • the policy objective may specify an energysaving target.
  • ES energy-saving objective
  • the EE objective may include one or more EE objectives associated with various network levels or layers, such as a PLMN level EE objective (may be referred to as “EEMN, Dvbits/j” herein), a slice level EE objective, a node level EE objective, and the like.
  • a PLMN level EE objective may be referred to as “EEMN, Dvbits/j” herein
  • a slice level EE objective may be referred to as “EEMN, Dvbits/j” herein
  • a node level EE objective may be referred to as “EEMN, Dvbits/j” herein.
  • the structured data types and attributes that may be used for defining the policy objectives may be defined in the following Table 5.
  • the policy resource may specify a condition for resource usage for the energy-saving policy.
  • the information associated with the policy resource may include one or more of: a condition list, an inclusion list, and an exclusion list.
  • the condition list may include one or more of: a network condition and a timing condition.
  • the inclusion list may include information of one or more nodes to which one or more energy-saving operations can be applicable.
  • the exclusion list may include information of one or more nodes that should be excluded from the one or more energy-saving operations.
  • the structured data types and attributes that may be used for defining the policy resources may be defined in the following Table 6.
  • EsResources The types, contents or attributes of the energy-saving resources (referred to as “EsResources” herein) may be further defined in the following Table 7.
  • An esResources statement may be defined in the following Table 8 as an array of the type EsResource defined in the above Table 7.
  • the cellldList when the value of the preference attribute is set to “PREFER” or “AVOID”, the cellldList contains cells in descending order of importance for how they should be preferred or avoided, e.g., the first entry is the most preferred or most avoided.
  • the preference value is set to “SHALL” or “FORBID”
  • the cellldList contains cells that are of equal importance.
  • the value of the primary attribute i.e., attribute of a primary cell
  • the value of the preference attribute is set to “SHALL”
  • a cell in the cellldList may be used as the primary cell.
  • the value of the primary attribute is set to “true”
  • the preference value is set to “AVOID” or “FORBID”
  • no cell in the cellldList is to be used as the primary cell.
  • an EsObjective statement may contain the attribute defined in the following Table 9:
  • the EsObjectives refer to a policy objective that includes attributes associated with the maximum number of user equipment (UE). This policy objective may help in triggering energy-saving operation(s) based on the number of UE (e.g., when UEs ⁇ 2).
  • the energy-saving policy may have a dedicated identifier.
  • the identifier may be referred to as “ORAN_EnergySavings_2.0.0”.
  • a traffic steering policy (TSP) statement may be combined with one or more information or contents of the energy-saving policy.
  • TSP statement may be applied together with Scopeidentifier containing different combinations of identifiers.
  • Example combinations of TSP statement with Scopeidentifier are presented in the following Table 10. Table 10: Example combinations of tspResources statement with Scopeidentifier
  • each row is listed with a combination of identifiers that is allowed for the indicated statement.
  • the notation is the same as for cardinality: "0" means the identifier shall not occur, "0..1” means the identifier may occur, and "1" means the identifier shall occur.
  • the parameters and characteristics of an energy-saving policy may be defined by a policy schema.
  • a policy schema may define or specify a structured format that outlies the attributes and contents of the energy-saving policy.
  • the policy schema may specifies the name, descriptions, statements, and data structure of the energy-saving policy, which may include the types of parameters, the associated values and settings, and the like.
  • the energy-saving policy may be defined in the format of JavaScript Object Notation (JSON).
  • JSON JavaScript Object Notation
  • the energy-saving policy may be generated or defined by the Non-RT RIC based on an associated JSON-based policy schema.
  • the JSON policy schema outlines the attributes or fields, the associated data types, and any other policy requirements that are required for defining an energy-saving policy, and may be obtained and utilized by the Non-RT RIC to define, generate, and configure the energysaving policy.
  • JSON schema associated with the energy-saving policy is presented in the following Table 11.
  • the portions that are associated with the energy-saving configurations are reflected in bold.
  • the Non-RT RIC may obtain the policy schema and then generate, based on the policy schema, various types of energy-saving policies for execution by the Near-RT RIC.
  • FIG. 3 illustrates a block diagram of various types of energy-saving policies, according to one or more example embodiments.
  • the energy-saving policy may be categorized into at least one of: an energy threshold-based energy-saving policy, a service assurance threshold-based energy-saving policy, a network condition-based energy-saving policy, a timing condition-based energy-saving policy, and a combination thereof.
  • These energy-saving policies may be generated and provided by the Non-RT RIC, and may be executed by the Near-RT RIC to perform one or more energy-saving operations.
  • examples of each of the aforesaid types of energy-saving policy are described.
  • This type of energy-saving policy establishes specific threshold(s) or limit(s) defined by energy-related criteria or parameters (e.g., energy consumption objective, energy efficiency objective, energy-saving objective, etc.) for triggering or initiating the execution of one or more energy-saving operations. For instance, when the energy-related criteria (e.g., energy usage) exceeds or falls below this threshold(s), the energy-saving policy may trigger one or more operations to optimize energy savings.
  • energy-related criteria e.g., energy usage
  • the policy scope identifier of the energy threshold-based policy may specify one or more nodes to which the energy threshold-based policy should be applied.
  • the policy scope identifier may include one or more of: a cell ID, a slice ID, a network ID, a gNB ID, an 0-RU ID, an 0-DU ID, an O-CU ID, a cell ID list that includes a plurality of cell IDs, a gNB ID list that includes a plurality of gNB IDs, an 0-RU ID list that includes a plurality of O-RU IDs, an 0-DU ID list that includes a plurality of 0-DU IDs, an O-CU ID list that includes a plurality of O-CU IDs, a slice ID list that includes a plurality of slice IDs, and a network ID list that includes a plurality of network IDs.
  • the policy objective of the energy threshold-based policy may specify one or more energy-saving targets.
  • the policy objective may include an energy parameter that associates with the energy-saving target and defines a threshold for initiating the execution of one or more energy-saving operations.
  • the policy objective of said policy may include one or more of: an energy-saving objective (ES), an energy efficiency objective (e.g., energy efficiency objective of a PLMN (EEMN,DVbits/j), etc ), a RAN energy consumption objective (ECNG- RAN), a gNB energy consumption objective (EC ⁇ NB), a network service energy consumption objective (EC ns ), and a network function energy consumption objective (ECNF).
  • the policy resource of the energy threshold-based policy may specific a condition for resource usage for the energy threshold-based policy.
  • the policy resource may include one or more of: an inclusion list, an exclusion list, and resources or preferences based on the scope identifier(s).
  • the inclusion list may include information of one or more nodes (e.g., cell ID, network ID, O-RU ID, etc.) to which the energysaving operation(s) can be applicable, while the exclusion list may include information of one or more nodes that should be excluded from the energy-saving operation(s).
  • the energy threshold-based policy may be applicable to different network levels or layers.
  • the energy threshold-based policy may be utilized for optimizing slice level energy efficiency, for optimizing node level (e.g., gNB/O-CU/O-DU/O-RU level) energy efficiency, for optimizing cell level energy efficiency, for optimizing PLMN level energy efficiency, and the like.
  • Table 12 Example slice level energy threshold-based policy
  • the scope identifier of the energy policy includes a slice ID that defines the specific network slice(s) to which the energy-saving policy is applicable and a PLMN ID that defines the PLMN associated with the target network slice.
  • the policy objective of the energy policy includes an energy efficiency objective defining a threshold for initiating the energy-saving operation(s).
  • the policy resources may include an exclusion list that specifies the cells that may be excluded from the energy-saving operation(s). Such cells may refer to cells of specific areas, such as a high-capacity zone, a hospital, and the like.
  • the Near-RT RIC can execute or trigger at least one energy-saving operation(s) on the associated cell(s), such as shutting down one or more cells among the network slice (cells other than those specified in the exclusion list), to achieve or maintain the energy efficiency objective.
  • Table 13 Example node level energy threshold-based policy
  • the energy-saving policy has the same policy resources as the energy-saving policy defined in above Table 12.
  • This energy-saving policy in Table 13 is different from the one in Table 12 in that, instead of a slice ID and PLMN ID, the associated scope identifier contains an ID of a specific node (e.g., gNB-DU ID of a DU) to which the energy-saving operations are applicable.
  • the associated policy objective contains an energy consumption objective (instead of an energy efficiency objective as in Table 12) defining a threshold for initiating the energy-saving operation(s).
  • the Near-RT RIC can perform or execute the energy-saving operation(s) to maintain the energy consumption of the associated node to satisfy the energy consumption objective.
  • Table 14 Example network level energy threshold-based policy
  • the scope identifier of the energy-saving policy includes a PLMN ID that defines the specific PLMN to which the energy-saving policy is applicable.
  • the policy objective of the energy policy includes an energy efficiency objective (EEMN.DV) that defines a threshold for initiating the energy-saving operation(s).
  • the policy resources include an inclusion list that specifies the O-RUs to which the energy-saving operation(s) is applicable and an exclusion list that specifies the O-RUs that may be excluded from the energysaving operation(s).
  • the Near-RT RIC can perform or execute the energy-saving operation(s) to maintain the energy efficiency of the associated PLMN to satisfy the energy efficiency objective.
  • an energy threshold-based energy-saving policy enables the establishment of one or more energy-saving objectives in the form of measurable thresholds, encompassing factors like energy efficiency and energy consumption.
  • These energy-saving objectives can be implemented with or without the allocation of policy resources, allowing for the creation of inclusion or exclusion lists
  • This type of energy-saving policy includes or prioritizes service assurance criteria or parameters that define the threshold for initiating or triggering the execution of one or more energy-saving operations.
  • the policy objective of the service assurance thresholdbased energy-saving policy may include at least one QoS objective that defines a threshold for initiating the execution of the one or more energy-saving operations.
  • the policy objective of the service assurance threshold-based energy-saving policy may include both QoS objective(s) and energy-related objective(s) (e.g., energy efficiency objective, energy consumption objective, energy-saving objective, etc.), thereby facilitating energy efficiency while maintaining a specified level of QoS.
  • QoS Objectives can be set along with one or more energy-related objectives to achieve a certain level of service assurance. By integrating both types of objectives, energy consumption may be optimized without compromising on the desired QoS.
  • the service assurance threshold-based energy-saving policy may include one or more policy scope identifiers and one or more policy resources that are similar to those described above with reference to the energy threshold-based energy-saving policy, without departing from the scope of the present disclosure.
  • the service assurance threshold-based energy-saving policy may be applicable to different network levels or layers.
  • the service assurance threshold-based energy-saving policy may be utilized for optimizing slice level energy efficiency, for optimizing node level (e.g., gNB/O-CU/O-DU/O- RU level) energy efficiency, for optimizing cell level energy efficiency, for optimizing PLMN level energy efficiency, and the like.
  • An example of a service assurance threshold-based policy for optimizing network level energy-saving is defined in the following Table 15.
  • Table 15 Example network level service assurance threshold-based policy
  • the scope identifier of the energy-saving policy includes a PLMN ID that defines the specific PLMN to which the energy-saving policy is applicable, and a QoS ID that defines the QoS to which the energy-saving policy is applicable.
  • the policy objective of the energy policy includes an energy-saving objective and a plurality of QoS objectives that define one or more thresholds for initiating the energy-saving operation(s).
  • the policy resources include a cell-wise inclusion list that specifies the cells to which the energy-saving operation(s) is applicable and a cell-wise exclusion list that specifies the cells that may be excluded from the energy-saving operation(s).
  • the Near-RT RIC can trigger or perform the energy-saving operation(s) to the cells defined in the inclusion list while avoiding performing the energy-saving operation(s) to the cells defined in the exclusion list, thereby achieving the energy efficiency objective while ensuring the QoS objectives for the specific QoS.
  • Table 16 Example network level service assurance threshold-based policy
  • the energy-saving policy has the policy scope identifiers and policy objectives similar to the energy-saving policy in Table 15.
  • the energy-saving policy in Table 16 is different from the one in Table 15 in that, the associated policy resources include a node level inclusion list that specifies the O-DUs to which the energy-saving operation(s) is applicable.
  • the Near-RT RIC can trigger or perform the energy-saving operation(s) to the O-DUs defined in the inclusion list while avoiding triggering or performing the energy-saving operation(s) to the cells defined in the exclusion list, thereby achieving the energy efficiency objective while ensuring the QoS objectives for the specific QoS.
  • Table 17 Example network level and cell level service assurance threshold-based policy
  • the scope identifier of the energy-saving policy may include a slice ID that defines the network slice to which the energy-saving policy is applicable and a cell ID that defines the network cell to which the energy-saving policy is applicable.
  • the policy objective of the energy policy includes an energy-saving objective and a plurality of QoS objectives that define one or more thresholds for initiating the energy-saving operation(s).
  • the policy resources include an inclusion list that specifies the cells to which the energy-saving operation(s) is applicable and an exclusion list that specifies the cells that may be excluded from the energy-saving operation(s).
  • the Near-RT RIC can trigger or perform the energy-saving operation(s) to the cells defined in the inclusion list while avoiding triggering or performing the energy-saving operation(s) to the cells defined in the exclusion list, thereby achieving the energy efficiency objective while ensuring the QoS objectives for the specific QoS.
  • the Near-RT RIC can also trigger handovers of low-priority users from target cells to neighboring cells. In such scenarios, the Near-RT RIC is responsible for maintaining the specified QoS for those users within the defined scope identifiers. This ensures a seamless transition for users while optimizing energy consumption.
  • This type of energy-saving policy includes or prioritizes network criteria or parameters for initiating the execution of one or more energy-saving operations.
  • the network condition-based energy-saving policy involves the activation of policy objective(s) after a specific network condition(s) is met, as determined by the Near-RT RIC. This approach allows the implementation of energy-saving measures when the predefined network conditions are satisfied, optimizing overall energy efficiency.
  • the policy resource of the network conditionbased energy-saving policy may include at least one network condition for triggering or initiating the execution of the one or more energy-saving operations.
  • the network condition may include one or more of network traffic, number of users in RRC state, number of active users, physical resource block (PRB) usage, and energy-related criteria (e.g., energy efficiency, energy consumption, etc.)
  • PRB physical resource block
  • energy-related criteria e.g., energy efficiency, energy consumption, etc.
  • the network condition-based energy-saving policy may include one or more policy scope identifiers and one or more policy objectives that are similar to those described above with reference to the energy threshold-based energy-saving policy and the service assurance threshold-based energy-saving policy, without departing from the scope of the present disclosure.
  • the network condition-based energy-saving policy may be applicable to different network levels or layers.
  • the network condition-based energy-saving policy may be utilized for optimizing slice level energy efficiency, optimizing node level (e.g., gNB/O- CU/O-DU/O-RU level) energy efficiency, optimizing cell level energy efficiency, optimizing PLMN level energy efficiency, and the like.
  • Table 18 Example network level network condition-based policy
  • the scope identifier of the energy-saving policy may include a PLMN ID that defines the PLMN to which the energy-saving policy is applicable.
  • the policy objective of the energy policy includes an energy efficiency objective.
  • the policy resources includes a condition list that includes a plurality of network conditions, an inclusion list that specifies the cells to which the energy-saving operation(s) is applicable when one or more of the network conditions in the condition list is satisfied, and an exclusion list that specifies the cells that may be excluded from the energy-saving operation(s).
  • the Near-RT RIC may determine whether or not the one or more network conditions are satisfied.
  • the Near-RT RIC can trigger or perform the energy-saving operation(s) to the cells defined in the inclusion list while avoiding triggering or performing the energy-saving operation(s) to the cells defined in the exclusion list, thereby achieving the energy efficiency objective.
  • the inclusion of the network condition(s) in the energy-saving policy allows Near-RT RIC to initiate or execute energy-saving operation(s) (e.g., cell/carrier shutdown, users handover, etc.) when the specified network condition(s) is satisfied.
  • energy-saving operation(s) e.g., cell/carrier shutdown, users handover, etc.
  • the Near-RT RIC can swiftly implement and recover appropriate operation(s), leveraging a more efficient control loop.
  • the configuration or selection of the network conditions of the energy-saving policy can be decided based on a specific preference or priority.
  • specifying the network conditions provides the network operator with the ability to trigger the energy-saving operation(s) when complexities in xApp are unexpected or when rApp dictates terms, especially when using xApps from different providers. Timins Condition-based Energy-Savins Policy
  • This type of energy-saving policy includes or prioritizes timing criteria or parameters for initiating the execution of one or more energy-saving operations. Specifically, the energy-saving operation(s) may be initiated based on specific time intervals or schedules (e.g., off- peak hours or periods of low network activity, etc.) defined in the policy.
  • the policy resource of the timing conditionbased energy-saving policy may include at least one timing condition for initiating the execution of the one or more energy-saving operations.
  • the timing condition may include one or more of: an energy-saving allowed time period (esAllowedTimePeriod) and an energy-saving not allowed time period (esNotAllowedTimePeriod). These time periods may include timing information such as period of day, days of week, and the like.
  • the network condition-based energy-saving policy may include one or more policy scope identifiers and one or more policy objectives that are similar to those described above with reference to the energy threshold-based energy-saving policy, the service assurance threshold-based energy-saving policy, and the network condition-based energysaving policy, without departing from the scope of the present disclosure.
  • the timing condition-based energy-saving policy may be applicable to different network levels or layers.
  • the timing condition-based energy-saving policy may be utilized for optimizing slice level energy efficiency, for optimizing node level (e.g., gNB/O-CU/O-DU/O-RU level) energy efficiency, for optimizing cell level energy efficiency, for optimizing PLMN level energy efficiency, and the like.
  • the scope identifier of the energy-saving policy may include a PLMN ID that defines the PLMN to which the energy-saving policy is applicable.
  • the policy objective of the energy policy includes an energy efficiency objective.
  • the policy resources include a condition list that includes a plurality of timing conditions (e.g., esNotAllowedTimePeriod, esAllowedTimePeriod, etc.) and an inclusion list that specifies the cells to which the energy-saving operation(s) is applicable when one or more of the timing conditions in the condition list is satisfied.
  • the Near-RT RIC may trigger or perform the energy-saving operation(s) to the cells defined in the inclusion list, thereby achieving the energy efficiency objective.
  • the Near-RT RIC will not utilize the specific energy-saving policy to initiate or perform the energysaving operation(s).
  • the timing condition-based energy-saving policy entails the activation of an energy-saving policy for designated time periods while excluding the same during specified times. This approach enables adjustment of energy consumption, particularly during off- peak hours or periods of low network activity.
  • the network operator can optimize energy usage based on the fluctuating demands of the network, promoting efficient resource utilization.
  • the Non-RT RIC may also be configured to generate and provide one or more energy-saving policies that include multi-types of the aforementioned energy-saving policies.
  • Table 20 Example combination of netw ork condition-based policy and timing condition-based policy
  • the scope identifier of the energy-saving policy may include a slice ID that defines the network slice to which the energy-saving policy is applicable and a cell ID that defines the network cell to which the energy-saving policy is applicable.
  • the policy objective of the energy policy includes an energy-saving cell shutdown objective.
  • the cell shutdown objective may be an action oriented objective that may be enforced or initiated by the Near-RT RIC according to the conditions defined in the energy-saving policy (e.g., shutdown a specific cell when a specific timing condition is satisfied, etc.)
  • the policy resources includes a condition list that includes a timing condition (e.g., esNotAllowedTimePeriod) and a plurality of network conditions (e.g., prbusage, rrcusers, etc.), an inclusion list that specifies the cells to which the energy-saving operation(s) is applicable when one or more conditions in the condition list are satisfied, and an exclusion list that specifies the cells that may be excluded from the energy-saving operation(s).
  • a timing condition e.g., esNotAllowedTimePeriod
  • a plurality of network conditions e.g., prbusage, rrcusers, etc.
  • an inclusion list specifies the cells to which the energy-saving operation(s) is applicable when one or more conditions in
  • the Near-RT RIC will only implement the energy-saving policy when the timing condition is satisfied (i.e., outside of the time period defined by the esNotAllowedTimePeriod).
  • the Near-RT RIC may further determine whether or not the network condition(s) is satisfied. Accordingly, the Near-RC RIC may shut down the cells defined in the inclusion list (or trigger an operation to shutdown said cells) while avoiding shutting down the cells defined in the exclusion list, thereby achieving the energy-saving cell shutdown objective.
  • any other suitable combination is applicable for provisioning the multi-type energy-saving policy, such as the combination of three types or all types of energysaving policies, without departing from the disclosure of the present disclosure.
  • example embodiments of the present disclosure efficiently and effectively facilitate the provisioning of energy policies that comply with the dynamic and complex nature of policy requirements in O-RAN.
  • energy policies in Tables 12-20
  • said energy policies may include more or less information and/or the contents therein may be arranged in a different manner, without departing from the scope of the present disclosure.
  • example embodiments of the present disclosure facilitate the provisioning of one or more energy-saving policies.
  • Example operations associated therewith are described in the following.
  • FIG. 4 illustrates a flow diagram of an example method 400 for provisioning one or more energy-saving policies, according to one or more example embodiments.
  • One or more operations of the method 400 may be performed by a Non-RT RIC included in a system (e.g., the Non-RT RIC 120 in an O-RAN system as described above with reference to FIG. 1, etc.)
  • a hardware e.g., a server
  • one or more operations of the method 400 may be performed by a component of the hardware (e.g., a processor of the server) upon executing computer-readable instruction (stored in a memory of the server, etc.)
  • the Non-RT RIC may be configured to obtain a policy schema.
  • the policy schema may be obtained from a memory or a storage component of the hardware (e.g., server) in which the Non-RT RIC is implemented, or may be obtained from a different storage medium (e.g., another server, etc.) Further, the policy schema may be obtained from any suitable components or entities in the O-RAN system.
  • the policy schema may include a JSON schema (an example associated therewith has been described above with reference to Table 11).
  • the method 400 may proceed to operation S420, at which the Non-RT RIC may be configured to generate, based on the policy schema, at least one energy-saving policy for execution by a Near-RT RIC.
  • the at least one energy-saving policy may include at least one of: an energy threshold-based energysaving policy, a service assurance threshold-based energy-saving policy, a network conditionbased energy-saving policy, and a timing condition-based energy-saving policy.
  • an energy-saving policy may include information associated with at least one policy scope identifier specifying at least one node to which the energysaving policy is applied, at least one policy objective specifying an energy-saving target, and at least one policy resource specifying a condition for resource usage for the energy-saving policy.
  • the at least one policy objective of the energy threshold-based energy-saving policy may include an energy parameter that defines a threshold for initiating the execution of one or more energy-saving operations
  • the at least one policy objective of the service assurance thresholdbased energy-saving policy may include a QoS objective that defined a threshold for initiating the execution of the one or more energy-saving operations
  • the at least one policy resource of the network condition-based energy-saving policy may include a network condition for initiating the execution of the one or more energy-saving operations
  • the at least one policy resource of the timing condition-based energy-saving policy may include a timing for initiating the execution of the one or more energy-saving operation.
  • the at least one policy scope identifier may include one or more of: a cell ID, a slice ID, a network ID, a gNB ID, an 0-RU ID, an 0-DU ID, an O-CU ID, a cell ID list that includes a plurality of cell IDs, a gNB ID list that includes a plurality of gNB IDs, an 0-RU ID list that includes a plurality of 0-RU IDs, an 0-DU ID list that includes a plurality of 0-DU IDs, an O-CU ID list comprises a plurality of O-CU IDs, a slice ID list that includes a plurality of slice IDs, and a network ID list that includes a plurality of network IDs.
  • the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • the at least one policy resource may include one or more of: a condition list, an inclusion list and an exclusion list.
  • the condition list may include one or more of: a network condition and a timing condition.
  • the inclusion list may include information of one or more nodes to which one or more energy-saving operations can be applicable.
  • the exclusion list may include information of one or more nodes that should be excluded from the one or more energy-saving operations
  • the method 400 may proceed to operation S430, at which the Non-RT RIC may be configured to provide the at least one energysaving policy to the Near-RT RIC via the Al interface. Accordingly, the Near-RT RIC may be configured to execute the at least one energy-saving policy to perform one or more energy-saving operations (e.g., cell switch On/Off, handover of users to another cell, etc.) [0130]
  • the Non-RT RIC may be configured to execute the at least one energy-saving policy to perform one or more energy-saving operations (e.g., cell switch On/Off, handover of users to another cell, etc.)
  • one or more energy-saving operations e.g., cell switch On/Off, handover of users to another cell, etc.
  • One or more components of the system of the example embodiments may be implemented in one or more systems, devices, or hardware components, such as one or more servers, and the like.
  • the operations associated therewith e.g., one or more operations in FIG. 4, one or more energy-saving operations, etc.
  • the devices may be implemented in one or more systems, devices, or hardware components, such as one or more servers, and the like.
  • descriptions of a device in which the systems or components of the example embodiments may be implemented are provided. It is contemplated that one or more operations or methods described above with reference to FIG. 1 to FIG. 4 may be performed by the device.
  • the one or more operations or methods may be performed by at least one processor of the device upon executing machine-readable instructions or computer-readable instructions (e.g., instructions for implementing the Non-RT RIC, etc.) stored in a memory or a storage component of the device.
  • machine-readable instructions or computer-readable instructions e.g., instructions for implementing the Non-RT RIC, etc.
  • FIG. 5 illustrates an embodiment of a device 500.
  • the device 500 may include a processor 510, a memory 520, a storage component 530, an input component 540, an output component 550, a communication interface 560, and a bus 570.
  • the processor 510 means any type of computational circuit that may comprise hardware elements and software elements.
  • the processor 510 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and/or one or more single core processors, a distributed processing system, or the like.
  • the processor 510 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.
  • CPU Central Processing Unit
  • GPU graphics processing unit
  • APU accelerated processing unit
  • ASIC application-specific integrated circuit
  • Memory 520 includes a non-transitory computer readable medium.
  • Memory 520 includes a random-access memory (RAM), a read only memory (ROM), and/or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and/or an optical memory) that stores information and/or instructions for use by processor 510.
  • the memory 520 comprises machine-readable instructions which are executable by the processor 510. These machine-readable instructions when executed by the processor 510 cause the processor 510 to perform one or more method steps of an embodiment described above.
  • Storage component 530 stores information and/or software related to the operation and use of the device 500.
  • storage component 530 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optic disk, and/or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and/or another type of non-transitory computer-readable medium, along with a corresponding drive.
  • Input component 540 is configured to receive information, such as user input.
  • the input component 540 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and/or a microphone.
  • the input component 540 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and/or an actuator).
  • GPS global positioning system
  • Output component 550 is configured to provide output information from the device
  • Communication interface 560 is an interface that provides a communication connection to other devices, such as external devices and internal devices.
  • the connection by the communication interface 560 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 500 and other devices.
  • the standard of the communication interface 560 is not limited.
  • the bus 570 acts as an interconnect between the processor 510, the memory 520, the storage component 530, the input component 540, the output component 550, and the communication interface 560 of the device 500.
  • the bus 570 may include a wired interconnection or a wireless interconnection.
  • device 500 may include additional components, fewer components, different components, or differently arranged components than those shown in FIG. 5. Additionally, or alternatively, a set of components (e.g., one or more components) of device 500 may perform one or more functions described as being performed by another set of components of device 500. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 500 in communication with one another.
  • Some embodiments may relate to a device (e.g., node, etc.), a system, a method, and/or a computer-readable medium at any possible technical detail level of integration. Further, one or more of the above components described above may be implemented as instructions stored on a computer-readable medium and executable by at least one processor (and/or may include at least one processor).
  • the computer-readable medium may include a computer-readable non- transitory storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out operations.
  • the computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device.
  • the computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing.
  • a non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), electrically erasable programmable read-only memory (EEPROM), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing.
  • RAM random access memory
  • ROM read-only memory
  • EPROM or Flash memory erasable programmable read-only memory
  • EEPROM electrically erasable programmable read-only memory
  • SRAM static random access memory
  • CD-ROM compact disc read-only memory
  • DVD digital versatile disk
  • memory stick a floppy disk
  • a computer-readable storage medium is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.
  • Computer-readable program instructions described herein can be downloaded to respective computing/processing devices from a computer-readable storage medium or to an external computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and/or a wireless network.
  • the network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and/or edge servers.
  • a network adapter card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing/processing device.
  • Computer-readable program code/instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the "C" programming language or similar programming languages.
  • ISA instruction-set-architecture
  • machine instructions machine-dependent instructions
  • microcode firmware instructions
  • state-setting data configuration data for integrated circuitry
  • configuration data for integrated circuitry or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the "C" programming language or similar programming languages.
  • the computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server.
  • the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider).
  • LAN local area network
  • WAN wide area network
  • Internet Service Provider for example, AT&T, MCI, Sprint, EarthLink, MSN, GTE, etc.
  • electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instructions by utilizing state information of the computer- readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.
  • FPGA field-programmable gate arrays
  • PLA programmable logic arrays
  • These computer-readable program instructions may be provided to a processor of a general-purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • These computer- readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and/or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function/act specified in the flowchart and/or block diagram block or blocks.
  • the computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions/acts specified in the flowchart and/or block diagram block or blocks.
  • each block in the flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s).
  • the method, computer system, and computer-readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures.
  • the functions noted in the blocks may occur out of the order noted in the Figures.
  • Non-RT radio access network intelligent controller
  • Item [2] The system according to item [1], wherein the at least one energy-saving policy may include at least one of: an energy threshold-based energy-saving policy, a service assurance threshold-based energy-saving policy, a network condition-based energy-saving policy, and a timing condition-based energy-saving policy.
  • Item [3] The system according to item [2], wherein the at least one policy objective of the energy threshold-based energy-saving policy may include an energy parameter that defines a threshold for initiating the execution of one or more energy-saving operations, wherein the at least one policy objective of the service assurance threshold-based energysaving policy may include a quality of service (QoS) objective that defined a threshold for initiating the execution of the one or more energy-saving operations, wherein the at least one policy resource of the network condition-based energy-saving policy may include a network condition for initiating the execution of the one or more energy-saving operations, and wherein the at least one policy resource of the timing condition-based energy-saving policy may include a timing for initiating the execution of the one or more energy-saving operation.
  • QoS quality of service
  • Item [4] The system according to any one of items [l]-[3], wherein the at least one policy scope identifier may include one or more of: a cell identifier (ID), a slice ID, a network ID, a gNodeB (gNB) ID, an open radio access network (O-RAN) radio unit ORU) ID, an O-RAN distributed unit (O-DU) ID, an O-RAN central unit (O-CU) ID, a cell ID list that may include a plurality of cell IDs, a gNB ID list that may include a plurality of gNB IDs, an O-RU ID list that may include a plurality of O-RU IDs, an O-DU ID list that may include a plurality of O-DU IDs, an O-CU ID list that may include a plurality of O-CU IDs, a slice ID list that may include a plurality of slice IDs, and a network ID list that may include a plurality of network IDs.
  • ID cell identifier
  • Item [5] The system according to any one of items [l]-[4], wherein the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • Item [6] The system according to any one of items [l]-[5], wherein the at least one policy resource may include one or more of: a condition list, an inclusion list and an exclusion list, wherein the condition list may include one or more of: a network condition and a timing condition, wherein the inclusion list may include information of one or more nodes to which one or more energy-saving operations can be applicable, and wherein the exclusion list may include information of one or more nodes that should be excluded from the one or more energy-saving operations.
  • the condition list may include one or more of: a network condition and a timing condition
  • the inclusion list may include information of one or more nodes to which one or more energy-saving operations can be applicable
  • the exclusion list may include information of one or more nodes that should be excluded from the one or more energy-saving operations.
  • Item [7] The system according to any one of items [l]-[6], wherein the policy schema may include a JavaScript Object Notation (JSON) schema.
  • Near-RT near-real-time radio access network intelligent controller
  • Item [9] The method according to item [8], wherein the at least one energy-saving policy may include at least one of: an energy threshold-based energy-saving policy, a service assurance threshold-based energy-saving policy, a network condition-based energy-saving policy, and a timing condition-based energy-saving policy.
  • the at least one policy objective of the energy threshold-based energy-saving policy may include an energy parameter that defines a threshold for initiating the execution of one or more energy-saving operations
  • the at least one policy objective of the service assurance thresholdbased energy-saving policy may include a quality of service (QoS) objective that defined a threshold for initiating the execution of the one or more energy-saving operations
  • the at least one policy resource of the network condition-based energy-saving policy may include a network condition for initiating the execution of the one or more energy-saving operations
  • the at least one policy resource of the timing condition-based energy-saving policy may include a timing for initiating the execution of the one or more energy-saving operation.
  • Item [11] The method according to any one of items [8]-[l 0], wherein the at least one policy scope identifier may include one or more of a cell identifier (ID), a slice ID, a network ID, a gNodeB (gNB) ID, an open radio access network (O-RAN) radio unit ORU) ID, an O-RAN distributed unit (O-DU) ID, an O-RAN central unit (O-CU) ID, a cell ID list that may include a plurality of cell IDs, a gNB ID list that may include a plurality of gNB IDs, an O-RU ID list that may include a plurality of O-RU IDs, an O-DU ID list that may include a plurality of O-DU IDs, an O-CU ID list that may include a plurality of O-CU IDs, a slice ID list that may include a plurality of slice IDs, and a network ID list that may include a plurality of network IDs.
  • ID cell identifier
  • Item [12] The method according to any one of items [8]-[l 1], wherein the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • Item [13] The method according to any one of items [8]-[ 12], wherein the at least one policy resource may include one or more of: a condition list, an inclusion list and an exclusion list, wherein the condition list may include one or more of: a network condition and a timing condition, wherein the inclusion list may include information of one or more nodes to which one or more energy-saving operations can be applicable, and wherein the exclusion list may include information of one or more nodes that should be excluded from the one or more energy-saving operations.
  • the condition list may include one or more of: a network condition and a timing condition
  • the inclusion list may include information of one or more nodes to which one or more energy-saving operations can be applicable
  • the exclusion list may include information of one or more nodes that should be excluded from the one or more energy-saving operations.
  • Item [14] The method according to any one of items [8]-[ 13], wherein the policy schema may include a JavaScript Object Notation (JSON) schema.
  • Item [16] The non-transitory computer-readable recording medium according to item [15], wherein the at least one of: an energy threshold-based energy-saving policy, a service assurance threshold-based energy-saving policy, a network condition-based energy-saving policy, and a timing condition-based energy-saving policy.
  • QoS quality of service
  • Item [18] The non-transitory computer-readable recording medium according to any one of items [15]-[17], wherein the at least one policy scope identifier may include one or more of: a cell identifier (ID), a slice ID, a network ID, a gNodeB (gNB) ID, an open radio access network (O-RAN) radio unit (O-RU) ID, an O-RAN distributed unit (O-DU) ID, an O-RAN central unit (O-CU) ID, a cell ID list that may include a plurality of cell IDs, a gNB ID list that may include a plurality of gNB IDs, an O-RU ID list that may include a plurality of O-RU IDs, an O-DU ID list that may include a plurality of O-DU IDs, an O- CU ID list that may include a plurality of O-CU IDs, a slice ID list that may include a plurality of slice IDs, and a network ID list that may include a plurality of
  • Item [19] The non-transitory computer-readable recording medium according to any one of items [15]-[18], wherein the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • the at least one policy objective may include one or more of: an energy-saving objective, an energy efficiency objective, a RAN energy consumption objective, a gNB energy consumption objective, a network service energy consumption objective, a network function energy consumption objective, and a QoS objective.
  • Item [20] The non-transitory computer-readable recording medium according to any one of items [ 15]-[19], wherein the at least one policy resource may include one or more of: a condition list, an inclusion list and an exclusion list, wherein the condition list may include one or more of: a network condition and a timing condition, wherein the inclusion list may include information of one or more nodes to which one or more energysaving operations can be applicable, and wherein the exclusion list may include information of one or more nodes that should be excluded from the one or more energysaving operations.
  • the at least one policy resource may include one or more of: a condition list, an inclusion list and an exclusion list
  • the condition list may include one or more of: a network condition and a timing condition
  • the inclusion list may include information of one or more nodes to which one or more energysaving operations can be applicable
  • the exclusion list may include information of one or more nodes that should be excluded from the one or more energysaving operations.

Landscapes

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

Abstract

Des modes de réalisation donnés à titre d'exemple de la présente divulgation concernent la fourniture d'une ou de plusieurs politiques d'économies d'énergie O-RAN. Selon des modes de réalisation donnés à titre d'exemple, un système peut comprendre un contrôleur intelligent de réseau d'accès radio (RIC) en temps différé (Non-RT). Le RIC Non-RT peut être conçu pour obtenir un schéma de politique et pour générer ensuite au moins une politique d'économies d'énergie sur la base du schéma de politique en vue d'une exécution par un RIC en temps quasi réel (Near-RT). Ladite politique d'économies d'énergie peut comprendre un identifiant de portée de politique spécifiant un nœud de réseau auquel la politique d'économies d'énergie est appliquée, un objectif de politique spécifiant une cible d'économies d'énergie, et une ressource de politique spécifiant une condition d'utilisation de ressources pour la politique d'économies d'énergie. Le RIC Non-RT peut ainsi être conçu pour fournir, au RIC Near-RT par l'intermédiaire d'une interface A1, ladite politique d'économies d'énergie.
PCT/US2024/031830 2023-06-05 2024-05-31 Fourniture de politiques d'économies d'énergie o-ran Ceased WO2024253956A1 (fr)

Priority Applications (3)

Application Number Priority Date Filing Date Title
EP24819816.0A EP4721359A1 (fr) 2023-06-05 2024-05-31 Fourniture de politiques d'économies d'énergie o-ran
CN202480037605.XA CN121241548A (zh) 2023-06-05 2024-05-31 O-ran节能策略的预配置
KR1020257040029A KR20260005370A (ko) 2023-06-05 2024-05-31 O-ran 에너지 절약 정책들의 프로비저닝

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US202363471053P 2023-06-05 2023-06-05
US63/471,053 2023-06-05
US202363472096P 2023-06-09 2023-06-09
US63/472,096 2023-06-09

Publications (1)

Publication Number Publication Date
WO2024253956A1 true WO2024253956A1 (fr) 2024-12-12

Family

ID=93796384

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/US2024/031830 Ceased WO2024253956A1 (fr) 2023-06-05 2024-05-31 Fourniture de politiques d'économies d'énergie o-ran

Country Status (4)

Country Link
EP (1) EP4721359A1 (fr)
KR (1) KR20260005370A (fr)
CN (1) CN121241548A (fr)
WO (1) WO2024253956A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2635001A (en) * 2023-09-08 2025-04-30 Samsung Electronics Co Ltd Improvements in and relating to a telecommunication network

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200252142A1 (en) * 2018-09-27 2020-08-06 Nokia Solutions And Networks Oy SCell Selection and Optimization for Telecommunication Systems
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
WO2023007417A1 (fr) * 2021-07-29 2023-02-02 Jio Platforms Limited Systèmes et procédés d'économie d'énergie dans un réseau

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20200252142A1 (en) * 2018-09-27 2020-08-06 Nokia Solutions And Networks Oy SCell Selection and Optimization for Telecommunication Systems
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
WO2023007417A1 (fr) * 2021-07-29 2023-02-02 Jio Platforms Limited Systèmes et procédés d'économie d'énergie dans un réseau

Non-Patent Citations (2)

* Cited by examiner, † Cited by third party
Title
ADAM SAMORZEWSKI: "Policy-based Traffic Steering xApp implementation within O-RAN", RIMEDO LABS, 1 April 2022 (2022-04-01), XP009559337, Retrieved from the Internet <URL:https://rimedolabs.com/blog/policy-based-traffic-steering-xapp-implementation-within-o-ran> *
POLESE MICHELE; BONATI LEONARDO; D'ORO SALVATORE; BASAGNI STEFANO; MELODIA TOMMASO: "Understanding O-RAN: Architecture, Interfaces, Algorithms, Security, and Research Challenges", IEEE COMMUNICATIONS SURVEYS & TUTORIALS, IEEE, vol. 25, no. 2, 21 January 2023 (2023-01-21), pages 1376 - 1411, XP011941195, DOI: 10.1109/COMST.2023.3239220 *

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
GB2635001A (en) * 2023-09-08 2025-04-30 Samsung Electronics Co Ltd Improvements in and relating to a telecommunication network

Also Published As

Publication number Publication date
EP4721359A1 (fr) 2026-04-08
KR20260005370A (ko) 2026-01-09
CN121241548A (zh) 2025-12-30

Similar Documents

Publication Publication Date Title
US20240305533A1 (en) Radio resource planning and slice-aware scheduling for intelligent radio access network slicing
US12342223B2 (en) Resilient radio resource provisioning for network slicing
US12323319B2 (en) Reliability enhancements for multi-access traffic management
US20250016567A1 (en) Technologies for radio equipment cybersecurity and multiradio interface testing
US12375968B2 (en) Graph neural network and reinforcement learning techniques for connection management
US20220224776A1 (en) Dynamic latency-responsive cache management
US11924060B2 (en) Multi-access edge computing (MEC) service contract formation and workload execution
CN117897980A (zh) 无线接入网智能应用管理器
CN115119331A (zh) 用于多接入通信量管理的强化学习
WO2023069757A1 (fr) Ingénierie de trafic dans des topologies de matrices avec des services déterministes
KR20220092366A (ko) 하이브리드 에지 컴퓨팅 플랫폼에서의 보안 듀얼 모드 에지 애플리케이션 프로그래밍 인터페이스 소비를 위한 상호운용가능한 프레임워크
DE112020001183T5 (de) Multi-slice-unterstützung für mec-fähige 5g-implementierungen
US11838838B2 (en) Method and system for application service management
AU2020428669B2 (en) Communication method, apparatus, and system
US12489685B2 (en) Method and system for deployment and management of composite applications
WO2024253956A1 (fr) Fourniture de politiques d&#39;économies d&#39;énergie o-ran
WO2025038919A1 (fr) Économie d&#39;énergie de réseau commandée par orchestration de gestion de service à l&#39;aide d&#39;une interface o1
WO2025136453A1 (fr) Résolution de conflit xapp/rapp de ric o-ran
EP4161020A1 (fr) Appareil, procédés et programmes informatiques
WO2025188337A1 (fr) Fourniture de politiques d&#39;économies d&#39;énergie o-ran
WO2025174414A1 (fr) Coordination entre la consommation d&#39;énergie o-ru et la source d&#39;alimentation externe dans un réseau
WO2026075680A1 (fr) Fourniture d&#39;amélioration de politique a1
WO2026039031A1 (fr) Interface de programmation d&#39;application (api) pour une gestion de configuration (cm) dans un réseau d&#39;accès radio ouvert (o-ran)
WO2025075727A1 (fr) Orchestration de gestion de service et économie d&#39;énergie de réseau de commande directe d&#39;unité distribuée à l&#39;aide d&#39;une interface o1
CA3170870C (fr) Procede, appareil et systeme de communication

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: 24819816

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2025569083

Country of ref document: JP

Kind code of ref document: A

WWE Wipo information: entry into national phase

Ref document number: 2025569083

Country of ref document: JP

ENP Entry into the national phase

Ref document number: 1020257040029

Country of ref document: KR

Free format text: ST27 STATUS EVENT CODE: A-0-1-A10-A15-NAP-PA0105 (AS PROVIDED BY THE NATIONAL OFFICE)

WWE Wipo information: entry into national phase

Ref document number: 202517123484

Country of ref document: IN

WWP Wipo information: published in national office

Ref document number: 202517123484

Country of ref document: IN

ENP Entry into the national phase

Ref document number: 2024819816

Country of ref document: EP

Effective date: 20260105

WWE Wipo information: entry into national phase

Ref document number: 2024819816

Country of ref document: EP

NENP Non-entry into the national phase

Ref country code: DE

ENP Entry into the national phase

Ref document number: 2024819816

Country of ref document: EP

Effective date: 20260105

ENP Entry into the national phase

Ref document number: 2024819816

Country of ref document: EP

Effective date: 20260105

ENP Entry into the national phase

Ref document number: 2024819816

Country of ref document: EP

Effective date: 20260105

ENP Entry into the national phase

Ref document number: 2024819816

Country of ref document: EP

Effective date: 20260105

ENP Entry into the national phase

Ref document number: 2024819816

Country of ref document: EP

Effective date: 20260105

WWP Wipo information: published in national office

Ref document number: 2024819816

Country of ref document: EP