System and method for cloud node shutdown

Abstract

A method and system for shutting down an Open Radio Access Network (O-RAN) Cloud (O-Cloud) node is provided. The method may include receiving, by a Service Management and Orchestration Framework (SMO) function, a first request to shut down at least one O-Cloud node, the first request being received from a user terminal or an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC); sending, by the SMO function, a second request to shut down the at least one O-Cloud node via an O2 interface to an Infrastructure Management Service (IMS) and / or a Deployment Management Service (DMS) based on the received first request; and receiving a first notification from the IMS / DMS that the at least one O-Cloud node has been shut down, wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and a Network Function Orchestration (NFO).

Description

[Technical Field]

[0001] Systems and methods consistent with example embodiments of the present disclosure relate to blocking open radio access network (O-RAN Cloud) nodes to prevent a scheduler from placing new deployments on the O-Cloud nodes. [Background technology]

[0002] The radio access network (RAN) is a critical component in telecommunications systems because it connects end-user devices (or user equipment) to the rest of the network. The RAN includes a combination of various network elements (NEs) that connect end-user devices to the core network. Traditionally, the hardware and / or software of a particular RAN is vendor-specific.

[0003] Open RAN (O-RAN) technology has emerged to enable multiple vendors to provide hardware and / or software for telecommunication systems. To this end, O-RAN divides RAN functions into a centralized unit (CU), a distributed unit (DU), and a radio unit (RU). The CU is a logical node for hosting the Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet Data Convergence Protocol (PDCP) sublayers of the RAN. The DU is a logical node for hosting the Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers of the RAN. The RU is a physical node that converts radio signals from the antenna into digital signals that can be transmitted to the DU via the fronthaul. These entities have open protocols and interfaces between them, allowing them to be developed by different vendors.

[0004] Figure 1 shows the O-RAN architecture of related technology. Referring to Figure 1, RAN functions in the O-RAN architecture are controlled and optimized by RICs. RICs are software-defined components that implement modular applications to facilitate multi-vendor operability required in O-RAN systems and to automate and optimize RAN operations. RICs are divided into two types: non-real-time RICs (Non-RT RICs) and near-real-time RICs (Near-RT RICs).

[0005] The non-RT RIC is the control point for non-real-time control loops and operates on sub-second timescales within a Service Management and Orchestration (SMO) framework. Its functionality is implemented via modular applications called rApps (rApp1, ..., rAppN) and includes providing policy-based guidance and reinforcement over the A1 interface, which is an interface that enables communication between non-RT RICs and quasi-RT RICs; performing data analytics; artificial intelligence / machine learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management actions over the O1 interface, which is an interface that connects the SMO to RAN managed elements (e.g., quasi-RT RICs, O-RAN centralized units (O-CUs), O-RAN distributed units (O-DUs), etc.).

[0006] The quasi-RT RIC operates on a timescale between 10 milliseconds and 1 second and connects to the O-DU, O-CU (split into the O-CU control plane (O-CU-CP) and the O-CU user plane (O-CU-UP)), and open evolved NodeB (O-eNB) via the E2 interface. The quasi-RT RIC uses the E2 interface to control the underlying RAN elements (E2 nodes / network functions (NFs)) through near-real-time control loops. The quasi-RT RIC monitors, suspends / suspends, overrides, and controls E2 nodes (O-CU, O-DU, and O-eNB) through policies. For example, the quasi-RT RIC sets policy parameters for activated functions of the E2 nodes. Additionally, the quasi-RT RIC hosts xApps to implement functions such as quality of service (QoS), mobility optimization, slicing optimization, interference mitigation, load balancing, and security. The two types of RICs collaborate to optimize the O-RAN. For example, the non-RT RIC provides policies, data, and AI / ML models over the A1 interface that are executed and used by the quasi-RT RIC for RAN optimization, and the quasi-RT returns policy feedback (i.e., how the policies set by the non-RT RIC are performing).

[0007] The SMO framework, where the non-RT RIC is located, manages and orchestrates RAN elements. Specifically, the SMO includes the Federated O-Cloud Orchestration and Management (FOCOM), the Network Function Orchestrator (NFO) that manages Virtual Machine (VM)-based Virtual Network Functions (VNFs) and container (i.e., instance)-based VNFs, and the OAM as part of the SMO that manages and orchestrates what is called the O-RAN Cloud (O-Cloud). The O-Cloud is a collection of physical RAN nodes that host the RIC, O-CU, and O-DU, supporting software components (e.g., operating systems and runtime environments), and the SMO itself. In other words, the SMO manages the O-Cloud from within. The O2 interface is the interface between the SMO and the O-Cloud on which it resides. Through the O2 interface, SMO provides Infrastructure Management Services (IMS) and Deployment Management Services (DMS), which can also transmit O2 telemetry data to SMO, such as O Cloud configuration or any logical function data, energy consumption, node health status, etc.

[0008] In the related art, an O Cloud node may be released for various reasons, for example, an O Cloud node may be released to perform hardware upgrades, software upgrades, kernel upgrades, energy efficiency or optimization processes, etc., before node shutdown. However, a scheduler in the SMO, which may be responsible for instantiating network functions in the O Cloud node, may not be aware that the node is released, which may inadvertently cause an error if the scheduler attempts to instantiate a network function in the released O Cloud node. Therefore, an O Cloud node needs to be able to indicate that it should no longer be able to be scheduled (i.e., is in an unschedulable state). Summary of the Invention

[0009] Exemplary embodiments of the present disclosure provide a method and system for shutting down an O cloud node to mark it as unschedulable. In particular, before the O cloud node is released, the SMO function (e.g., FOCOM and / or NFO) can request the IMS / DMS to shut down the O cloud node, thereby marking it as unschedulable by the SMO scheduler (i.e., in an unschedulable state).

[0010] Thus, example embodiments of the present disclosure may avoid scheduling errors (e.g., scheduling the instantiation of a network function when a cloud node is free).

[0011] According to an embodiment, there may be provided a method for shutting down one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes. The method may include receiving, by a Service Management and Orchestration Framework (SMO) function, a first request to shut down at least one O-Cloud node, the first request being received from a user terminal or from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC); sending, by the SMO function, a second request to shut down the at least one O-Cloud node via an O2 interface to an Infrastructure Management Service (IMS) and / or a Deployment Management Service (DMS) based on the received first request; and receiving a first notification from the IMS / DMS that the at least one O-Cloud node has been shut down, wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and a Network Function Orchestration (NFO).

[0012] The second request may be an instruction to block a first O cloud node of the at least one O cloud node, and the first notification indicates that the first O cloud node has been blocked, and the method may further include sending, by the SMO function, a third request to the IMS / DMS via the O2 interface to block a second O cloud node of the at least one O cloud node based on the received first request, and receiving a second notification from the IMS / DMS that the second O cloud node has been blocked.

[0013] The first request may be triggered by an rApp in a non-RT RIC or by a manual request submitted via the Service Management and Orchestration Framework (SMO).

[0014] The second request may be sent to the IMS / DMS solely by the SMO function based on determining, by the SMO function, that the first request to shut down at least one O cloud node is valid.

[0015] The method may further include controlling, by the IMS / DMS, to block at least one O cloud node based on the second request and mark the O cloud node as unschedulable.

[0016] Receiving the first notification that the O cloud node has been blocked may further include receiving, by the SMO function, the first notification from the IMS / DMS via the O2 interface that at least one O cloud node has been blocked.

[0017] Receiving the first notification that the O cloud node has been blocked may further include receiving, by an rApp of the non-RT RIC, a first notification from the SMO function that at least one O cloud node has been blocked.

[0018] According to an embodiment, an apparatus for shutting down one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes may be provided. The apparatus may include at least one processor configured to execute computer-executable instructions to receive, via a Service Management and Orchestration Framework (SMO) function, a first request to shut down at least one O-Cloud node, the first request being received from a user terminal or from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC), send, via the SMO function, a second request to shut down the at least one O-Cloud node based on the received first request to an Infrastructure Management Service (IMS) and / or a Deployment Management Service (DMS) via an O2 interface, and receive a first notification from the IMS / DMS that the at least one O-Cloud node has been shut down, where the SMO function is at least one of Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).

[0019] The second request may be an instruction to block a first O cloud node of the at least one O cloud node, and the first notification indicates that the first O cloud node has been blocked, and the at least one processor may be further configured to execute computer-executable instructions to send, by the SMO function, a third request to the IMS / DMS via the O2 interface to block a second O cloud node of the at least one O cloud node based on the received first request, and receive a second notification from the IMS / DMS that the second O cloud node has been blocked.

[0020] The first request may be triggered by an rApp in a non-RT RIC or by a manual request submitted via the Service Management and Orchestration Framework (SMO).

[0021] The second request may be sent to the IMS / DMS solely by the SMO function based on determining, by the SMO function, that the first request to shut down at least one O cloud node is valid.

[0022] The at least one processor may be further configured to execute computer-executable instructions for controlling, by the IMS / DMS, blocking of at least one O cloud node based on the second request to mark the O cloud node as unschedulable.

[0023] The at least one processor may be further configured to execute computer-executable instructions for receiving, by the SMO function, a first notification that the O cloud node has been blocked by receiving, via the O2 interface, from the IMS / DMS, a first notification that the at least one O cloud node has been blocked.

[0024] The at least one processor may be further configured to execute computer-executable instructions for receiving, by an rApp of the non-RT RIC, a first notification from the SMO function that at least one O cloud node has been blocked, thereby receiving a first notification that the O cloud node has been blocked.

[0025] Additional aspects will be set forth in part in the description that follows, and in part will be apparent from the description, or may be learned by practice of presented embodiments of the present disclosure. [Brief explanation of the drawings]

[0026] Features, aspects, and advantages of certain exemplary embodiments of the present disclosure are described below with reference to the accompanying drawings, in which like reference numerals refer to like elements.

[0027] [Figure 1] FIG. 1 illustrates an O-RAN architecture according to the prior art.

[0028] [Figure 2] 1 is a flowchart of a method for shutting down an O Cloud node using an O2 interface between an SMO function and the O Cloud, according to one embodiment.

[0029] [Figure 3] FIG. 1 is a diagram of an exemplary environment in which the system described herein for blocking cloud nodes may be implemented, according to one embodiment.

[0030] [Figure 4] FIG. 1 is a diagram of an example environment in which the systems and / or methods described herein may be implemented.

[0031] [Figure 5] FIG. 2 is a diagram of exemplary components of a device, according to one embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0032] The following detailed description of the exemplary embodiments refers to the accompanying drawings, in which the same reference numbers in different drawings may identify the same or similar elements.

[0033] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementations to the precise form disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of implementations. Moreover, one or more features or components of one embodiment may be incorporated into or combined with another embodiment (or one or more features of another embodiment). Additionally, in the flowcharts and descriptions of operations provided below, it is understood that one or more operations may be omitted, one or more operations may be added, one or more operations may be performed (at least partially) concurrently, and the order of one or more operations may be permuted.

[0034] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not limiting of the implementation. Thus, the operation and behavior of the systems and / or methods will be described herein without reference to specific software code. It will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0035] Although particular combinations of features are recited in the claims and / or disclosed herein, these combinations are not intended to limit the disclosure of possible implementations. Indeed, many of these features can be combined in ways not specifically recited in the claims and / or disclosed herein. Although each dependent claim listed below may depend directly on only one claim, the disclosure of possible implementations includes each dependent claim in combination with all other claims in the claim set.

[0036] No element, act, or instruction used herein should be construed as critical or required unless explicitly described as such. Also, as used herein, the articles "a" and "an" are intended to include one or more items and may be used interchangeably with "one or more." Where only one item is intended, the term "one" or similar language is used. Also, as used herein, terms such as "has," "have," "having," "include," and "including" are intended to be open-ended terms. Furthermore, the phrase "based on" is intended to mean "based at least in part on," unless expressly stated otherwise. Furthermore, phrases such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include A only, B only, or both A and B.

[0037] Exemplary embodiments of the present disclosure provide a method and system for shutting down an O cloud node to mark it as unschedulable. In particular, before the O cloud node is released, an SMO function (e.g., FOCOM and / or NFO) can request the IMS / DMS to shut down the O cloud node, thereby marking it as unschedulable by the SMO scheduler (i.e., in an unschedulable state). Thus, embodiments of the present disclosure can avoid scheduling errors (e.g., scheduling the instantiation of a network function when the O cloud node is released).

[0038] 2 is a flowchart of a method for shutting down an O-cloud node according to one embodiment. The method in operation S201 of FIG. 2 may be performed by a user terminal or an rApp, operations S202-S203 may be performed by an SMO function (e.g., NFO and / or FOCOM), and operations S204-S205 may be performed by an IMS / DMS.

[0039] Referring to Figure 2, the shutdown of the O-Cloud node(s) may be initiated in S201 by a user via a user terminal (e.g., including an application for managing network functions and / or subscribing to receive alarm events, notifications, etc. from the SMO) or by one or more rApps in a non-RT RIC in the SMO. The components of the O-RAN architecture in Figures 2 and 3 are similar to those in Figure 1.

[0040] As shown in FIGS. 2 and 3, before the shutdown of the O Cloud node(s) is initiated, the availability of the SMO and the O Cloud are assumed. In some exemplary embodiments, it may also be assumed that the O Cloud node(s) is / are in an idle state. It may also be assumed that there is network connectivity between the SMO and the O Cloud, that there are no active deployments (network functions) on the O Cloud node(s), and that the user terminal or rApp is / are subscribed to O1 and O2 events. Furthermore, the non-RT RIC or the above-mentioned user terminal is configured to subscribe to receive notifications from the SMO. According to one embodiment, the request may be in the form of a trigger from the user terminal or rApp to the NFO / FOCOM. The request may also include an identifier of the O Cloud node(s) to be shut down.

[0041] In operation S202, the NFO / FOCOM receives the request (first request) to shut down one or more O cloud node(s) sent in operation S201. According to one embodiment, upon receiving the request, the NFO / FOCOM can determine whether the request is valid (e.g., the NFO / FOCOM can determine whether it can shut down the O cloud node(s) requested to be shut down).

[0042] In operation S203, the NFO / FOCOM requests the IMS / DMS to block one or more O-Cloud nodes based on the received first request (second request), where the NFO / FOCOM can request the IMS / DMS to block one or more O-Cloud nodes via the O2 interface, for example, using the O2ims service or the O2dms service.

[0043] In operation S204, the IMS / DMS receives the request sent by the NFO / FOCOM in operation S203 and performs an operation to mark one or more O cloud node(s) as unschedulable, thereby blocking said one or more O cloud node(s).

[0044] In operation S205, the IMS / DMS may notify the NFO / FOCOM indicating the status of the isolation request, e.g., indicating that the isolation request is completed. The user terminal and / or non-RT RIC (i.e., rApp) may also receive this status update notification.

[0045] Operations S203, S204, and S205 may be looped or repeatedly performed for each of the one or more O cloud nodes identified in the first request. Further, the NFO / FOCOM may determine an order for blocking one or more O cloud nodes according to a predetermined criterion or randomly, and may send second requests corresponding to the one or more O cloud nodes, respectively, according to the determined order.

[0046] Figure 3 illustrates a detailed method for implementing a shutdown procedure 300 for an O-cloud node(s), according to one embodiment. The method of Figure 3 is performed by a user terminal (i.e., an application installed thereon) and / or a non-RT RIC (rApp), as well as NFO / FOCOM and IMS / DMS.

[0047] Referring to FIG. 3 , a method for implementing an O-cloud node shutdown procedure 300 may be triggered by or based on input from an O2 interface (e.g., O2 telemetry data). According to another embodiment, the method may consider both O2 telemetry data received via the O2 interface and O1 telemetry data received via the O1 interface. For example, in the case of NF load (e.g., compute, memory usage, etc.), an rApp can ingest historical load data metrics, correlate the metrics with other sources (e.g., O2 and / or O1 telemetry data), and use AI / ML algorithms to predict a period of very high (e.g., greater than a predetermined threshold or metric) load (e.g., the next four hours) and provide predictive guidance to the NFO / FOCOM to avoid placing critical performance-sensitive workloads on a particular node hosting the NF load. In this example, based on the rApp guidance, the NFO / FOCOM can determine not to schedule workloads of a particular application to the node and / or not to schedule new workloads to that node in a scale-out operation during that period.

[0048] In operation 301, a user terminal or a non-RT RIC sends a first request to NFO / FOCOM to block O cloud node(s). The first request may include an identifier of the O cloud node(s). This may be similar to operation S201 described in FIG. 2 above.

[0049] In operation 302, the NFO / FOCOM receives a first request from a non-RT RIC or a user terminal to release an O cloud node(s), which may be similar to operation S202 described in FIG.

[0050] In operation 303, the NFO / FOCOM sends a second request to the IMS / DMS via the O2 interface to block the O cloud node(s) based on the received first request, which may be similar to operation S203 described in FIG.

[0051] In operation 304, the IMS / DMS shuts down each specified node. To this end, the IMS / DMS may mark the O cloud node as "unschedulable" so that the scheduler in the SMO does not instantiate any new deployments (i.e., network functions) on the O cloud node. This may be similar to operation S204 described in FIG. 2 above.

[0052] In operation 305, in an exemplary embodiment, the IMS / DMS sends a confirmation notification of the completed shutdown procedure to the NFO / FOCOM via the O2 interface. In operation S306, the IMS / DMS may also (or instead) send notifications to, for example, non-RT RICs (rApps) and / or user terminals (applications) based on whether they are subscribed to notifications from the IMS / DMS. Operations 305 and 306 may be similar to operation S205 described in FIG. 2 above.

[0053] In one embodiment, operations 303-306 may be looped or repeatedly performed for each of the one or more cloud nodes identified in the first request.

[0054] According to an exemplary embodiment, the process of shutting down an O cloud node can be easily performed upon receiving a trigger from a user terminal or a non-RT RIC (rApp), thus avoiding scheduling errors (e.g., scheduling the instantiation of a network function when the O cloud node is released).

[0055] 4 is a diagram of an example environment 400 in which the systems and / or methods described herein may be implemented. As shown in FIG. 4, environment 400 may include a user device 410, a platform 420, and a network 430. The devices in environment 400 may be interconnected via wired connections, wireless connections, or a combination of wired and wireless connections. In embodiments, any of the functions and operations described with reference to FIGS. 2-3 above may be performed by any combination of elements shown in FIG. 4.

[0056] User device 410 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information related to platform 420. For example, user device 410 may include a computing device (e.g., a desktop computer, a laptop computer, a tablet computer, a handheld computer, a smart speaker, a server, etc.), a mobile phone (e.g., a smartphone, a wireless phone, etc.), a wearable device (e.g., smart glasses or a smart watch), or similar device. In some implementations, user device 410 can receive information from and / or transmit information to platform 420.

[0057] Platform 420 includes one or more devices capable of receiving, generating, storing, processing, and / or providing information. In some implementations, platform 420 may include a cloud server or a collection of cloud servers. In some implementations, platform 420 may be designed to be modular, such that certain software components can be swapped in or out depending on particular needs. Thus, platform 420 can be easily and / or quickly reconfigured for different uses.

[0058] In some implementations, as shown, platform 420 may be hosted in a cloud computing environment 422. Notably, although the implementations described herein describe platform 420 as being hosted within cloud computing environment 422, in some implementations platform 420 may not be cloud-based (i.e., may be implemented outside of a cloud computing environment) or may be partially cloud-based.

[0059] Cloud computing environment 422 includes an environment that hosts platform 520. Cloud computing environment 422 may provide services such as computing, software, data access, storage, etc. that do not require end-user (e.g., user device 410) knowledge of the physical location and configuration of the system(s) and / or device(s) that host platform 420. As shown, cloud computing environment 422 may include a collection of computing resources 424 (collectively referred to as “computing resources 424” and individually referred to as “computing resource 424”).

[0060] Computing resources 424 include one or more personal computers, clusters of computing devices, workstation computers, server devices, or other types of computing and / or communication devices. In some implementations, computing resources 424 may host platform 420. Cloud resources may include compute instances running within computing resources 424, storage devices provided within computing resources 424, data transfer devices provided by computing resources 424, etc. In some implementations, computing resources 424 may communicate with other computing resources 424 via wired connections, wireless connections, or a combination of wired and wireless connections.

[0061] As further shown in FIG. 4, computing resources 424 include a group of cloud resources such as one or more applications ("Applications": APPs) 424-1, one or more virtual machines ("Virtual Machines": VMs) 424-2, virtualized storage ("Virtualized Storage": VSs) 424-3, and one or more hypervisors ("Hypervisors": HYPs) 424-4.

[0062] Applications 424-1 include one or more software applications that may be provided to or accessed by user device 410. Applications 424-1 may eliminate the need to install and run software applications on user device 410. For example, applications 424-1 may include software associated with platform 420 and / or any other software that may be provided via cloud computing environment 422. In some implementations, one application 424-1 may send information to or receive information from one or more other applications 424-1 via virtual machine 424-2.

[0063] Virtual machine 424-2 includes a software implementation of a machine (e.g., a computer) that executes programs like a physical machine. Virtual machine 424-2 can be either a system virtual machine or a process virtual machine, depending on the intended use and the closeness of virtual machine 424-2 to any actual machine. A system virtual machine may provide a complete system platform that supports the execution of a complete operating system ("OS"). A process virtual machine may execute a single program and support a single process. In some implementations, virtual machine 424-2 may run on behalf of a user (e.g., user device 410) and manage the infrastructure of cloud computing environment 422, such as data management, synchronization, or long-term data transfer.

[0064] Virtualized storage 424-3 includes one or more storage systems and / or one or more devices that use virtualization techniques within the storage systems or devices of computing resources 424. In some implementations, types of virtualization in the context of storage systems may include block virtualization and file virtualization. Block virtualization may refer to the abstraction (or separation) of logical storage from physical storage so that the storage system can be accessed regardless of the physical storage or heterogeneous structure. Separation allows storage system administrators flexibility in how they manage storage for end users. File virtualization can eliminate dependencies between data accessed at the file level and where the file is physically stored. This may enable performance optimization of storage usage, server consolidation, and / or non-disruptive file migration.

[0065] Hypervisor 424-4 may provide hardware virtualization technology that allows multiple operating systems (e.g., "guest operating systems") to run simultaneously on a host computer, such as computing resource 424. Hypervisor 424-4 may provide a virtual operating platform for the guest operating systems and may manage the execution of the guest operating systems. Multiple instances of different operating systems may share virtualized hardware resources.

[0066] Network 430 may include one or more wired and / or wireless networks. For example, network 430 may include a cellular network (e.g., a Fifth Generation (5G) network, a Long-Term Evolution (LTE) network, a Third Generation (3G) network, a Code Division Multiple Access (CDMA) network, etc.), a Public Land Mobile Network (PLMN), a Local Area Network (LAN), a Wide Area Network (WAN), a Metropolitan Area Network (MAN), a telephone network (e.g., a Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, an optical fiber-based network, etc., and / or a combination of these or other types of networks.

[0067] The number and arrangement of devices and networks shown in Figure 4 are provided as an example. In practice, there may be additional, fewer, different, or differently located devices and / or networks than those shown in Figure 4. Furthermore, two or more devices shown in Figure 4 may be implemented within a single device, or a single device shown in Figure 4 may be implemented as multiple distributed devices. Additionally, or instead, a set of devices (e.g., one or more devices) in environment 400 may perform one or more functions that are described as being performed by another set of devices in environment 400.

[0068] 5 is a diagram of example components of a device 500. The device 500 may correspond to a user device 410 and / or a platform 420. As shown in FIG. 5, the device 500 may include a bus 510, a processor 520, a memory 530, a storage component 540, an input component 550, an output component 560, and a communication interface 570.

[0069] The bus 510 includes components that enable communication between the components of the device 500. The processor 520 may be implemented in hardware, firmware, or a combination of hardware and software. The processor 520 may be a central processing unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), a microprocessor, a microcontroller, a digital signal processor (DSP), a field-programmable gate array (FPGA), an application-specific integrated circuit (ASIC), or another type of processing component. In some implementations, the processor 520 includes one or more processors that can be programmed to perform functions. Memory 330 may comprise random access memory (RAM), read only memory (ROM), and / or another type of dynamic or static storage device (e.g., flash memory, magnetic memory, and / or optical memory) that stores information and / or instructions used by processor 520.

[0070] The storage component 540 stores information and / or software related to the operation and use of the device 500. For example, the storage component 540 may include a hard disk (e.g., a magnetic disk, an optical disk, an optical-magnetic 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. The input component 550 includes components that enable the device 500 to receive information, such as via user input (e.g., a touchscreen display, a keyboard, a keypad, a mouse, buttons, switches, and / or a microphone). Additionally or alternatively, the input component 550 may include sensors for sensing information (e.g., a Global Positioning System (GPS) component, an accelerometer, a gyroscope, and / or an actuator). Output components 560 include components that provide output information from device 500 (eg, a display, a speaker, and / or one or more Light-Emitting Diodes (LEDs)).

[0071] Communications interface 570 includes transceiver-like components (e.g., a transceiver and / or a separate receiver and transmitter) that enable device 500 to communicate with other devices, such as via a wired connection, a wireless connection, or a combination of wired and wireless connections. Communications interface 570 may enable device 500 to receive information from and / or provide information to another device. For example, communications interface 570 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, a Universal Serial Bus (USB) interface, a Wi-Fi interface, a cellular network interface, etc.

[0072] Device 500 may perform one or more processes described herein. Device 500 may perform these processes in response to processor 520 executing software instructions stored by a non-transitory computer-readable medium, such as memory 530 and / or storage component 540. A computer-readable medium is defined herein as a non-transitory memory device. A memory device includes memory space within a single physical storage device or memory space spread across multiple physical storage devices.

[0073] The software instructions may be loaded into memory 530 and / or storage component 540 from another computer-readable medium or from another device via communication interface 570. When executed, the software instructions stored in memory 530 and / or storage component 540 may cause processor 520 to perform one or more processes described herein.

[0074] Additionally, or instead, hardwired circuitry may be used in place of or in combination with software instructions to implement one or more processes described herein. Thus, implementations described herein are not limited to any specific combination of hardware circuitry and software.

[0075] The number and arrangement of components shown in Figure 5 are provided as an example. In practice, device 500 may include more, fewer, different, or differently arranged components than those shown in Figure 5. Additionally or alternatively, a set of components (e.g., one or more components) of device 500 may perform one or more functions that are described as being performed by another set of components of device 500.

[0076] In embodiments, any of the operations or processes of Figures 2 and 3 may be performed by or using any one of the elements shown in Figures 4 and 5. It is understood that other embodiments may be implemented in a variety of different architectures (e.g., without limitation, a bare metal architecture or any cloud-based or deployment architecture such as Kubernetes, Docker, OpenStack, etc.).

[0077] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit the implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of the implementations.

[0078] Some embodiments may relate to systems, methods, and / or computer-readable media at any possible level of technical detail. Furthermore, 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 for causing a processor to perform operations.

[0079] A computer-readable storage medium may be a tangible device capable of retaining and storing instructions for use by an instruction-execution device. A computer-readable storage medium may be, for example, but 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 computer-readable storage media includes portable computer diskettes, hard disks, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM, or flash memory), static random access memory (SRAM), portable compact disc read-only memory (CD-ROM), digital versatile disks (DVDs), memory sticks, floppy disks, mechanically encoded devices such as punch cards or ridge-in-groove structures with instructions recorded thereon, and any suitable combination of the foregoing. As used herein, computer-readable storage media should not 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 medium (e.g., light pulses passing through a fiber optic cable), or electrical signals transmitted through wires.

[0080] The computer-readable program instructions described herein may be downloaded from a computer-readable storage medium to each computing / processing device or to an external computer or external storage device via a network, such as the Internet, a local area network, a wide area network, and / or a wireless network. The network may include transmission copper cables, transmission optical fiber, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface within each computing / processing device receives the 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.

[0081] The computer-readable program code / instructions for carrying out operations may be either source code or object code written in any combination of one or more programming languages, including assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, integrated circuit configuration data, or object-oriented programming languages ​​such as Smalltalk, C++, 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, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, a programmable logic circuit, a field programmable gate array (FPGA), or a programmable logic array (PLA) can execute computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry to perform aspects or operations.

[0082] 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 create a machine, whereby the instructions, executed by the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams. These computer-readable program instructions also include articles of manufacture stored on a computer-readable storage medium that can instruct a computer, programmable data processing apparatus, and / or other device to function in a particular manner, whereby the computer-readable storage medium having instructions stored therein contains instructions that implement aspects of the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0083] These computer-readable program instructions may also be loaded into a computer, other programmable data processing apparatus, or other device to cause the computer, other programmable apparatus, or other device to perform a series of operational steps to create a computer-implemented process, such that the instructions executing on the computer, other programmable apparatus, or other device perform the functions / acts specified in one or more blocks of the flowcharts and / or block diagrams.

[0084] The flowcharts and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer-readable media according to various embodiments. In this regard, each block in the flowcharts or block diagrams may represent a portion of a microservice(s), module, segment, or instruction set, which comprises one or more executable instructions for implementing the specified logical function(s). The methods, computer systems, and computer-readable media may include more, fewer, different, or differently arranged blocks than those shown in the figures. In some alternative implementations, the functions noted in the blocks may occur out of the order noted in the figures. For example, two blocks shown in succession may actually be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the functionality involved. It should also be noted that each block in the block diagrams and / or flowchart diagrams, and combinations of blocks in the block diagrams and / or flowchart diagrams, may be implemented by a special-purpose hardware-based system that performs the specified functions or operations or executes a combination of special-purpose hardware and computer instructions.

[0085] It will be apparent that the systems and / or methods described herein may be implemented in various forms of hardware, firmware, or a combination of hardware and software. The actual dedicated control hardware or software code used to implement these systems and / or methods is not intended to limit the implementation. Thus, the operation and behavior of the systems and / or methods are described herein without reference to specific software code, and it will be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.

[0086] Various aspects of the embodiments

[0087] Various further respective aspects and features of embodiments of the present disclosure can be defined by the following clauses. Item [1]: A method for shutting down one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes, the method including: receiving, by a Network Function Orchestration (NFO) and / or Federated O-Cloud Orchestration and Management (FOCOM), a first request to shut down at least one O-Cloud node, wherein the first request is received from a user terminal or a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC); sending, by the NFO / FOCOM, a second request to shut down the at least one O-Cloud node based on the received first request to an Infrastructure Management Service (IMS) and / or Deployment Management Service (DMS) via an O2 interface; and receiving, from the IMS / DMS, a first notification that the at least one O-Cloud node has been shut down. Item [2]: The second request is an instruction to block a first O cloud node of the at least one O cloud node, and the first notification indicates that the first O cloud node has been blocked, and the method includes sending, by the NFO / FOCOM, a third request to block a second O cloud node of the at least one O cloud node via an O2 interface to the IMS / DMS based on the received first request; receiving a second notification from the IMS that a second O cloud node has been blocked; Item 1, the method of claim 1 further comprising: Item [3]: The method described in item [1] or [2], wherein the first request is triggered by a modular application (rApp) of a non-RT RIC or by a manual request submitted via a service management and orchestration framework (SMO). Item [4]: ​​A method according to any one of items [1] to [3], wherein the second request is sent to the IMS / DMS only by the NFO / FOCOM based on the NFO / FOCOM determining that the first request to block at least one O cloud node is valid. Item [5]: A method according to any one of items [1] to [4], further comprising controlling, by the IMS / DMS, to block at least one O cloud node based on a second request to mark the O cloud node as unschedulable. Item [6]: The method according to any one of items [1] to [4], wherein receiving a first notification that an O cloud node has been blocked further includes receiving, by NFO / FOCOM, from an IMS / DMS via an O2 interface, a first notification that at least one O cloud node has been blocked. Item [7]: The method of item [6], wherein receiving a first notification that an O cloud node has been blocked further includes receiving, by a non-RT RIC, a first notification from an NFO / FOCOM that at least one O cloud node has been blocked. Item [8]: An apparatus for shutting down one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes, the apparatus comprising at least one processor configured to execute computer-executable instructions to receive, by a Service Management and Orchestration Framework (SMO) function, a first request to shut down at least one O-Cloud node, the first request being received from a user terminal or from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC); send, by the SMO function, a second request to shut down the at least one O-Cloud node based on the received first request to an Infrastructure Management Service (IMS) and / or Deployment Management Service (DMS) via an O2 interface; and receive a first notification from the IMS / DMS that the at least one O-Cloud node has been shut down, wherein the SMO function is at least one of Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO). Item [9]: The device described in Item [8], further configured to execute computer-executable instructions for: the second request being an instruction to block a first O cloud node of the at least one O cloud node; the first notification indicating that the first O cloud node has been blocked; and the at least one processor, via the SMO function, sending a third request to the IMS / DMS via the O2 interface to block a second O cloud node of the at least one O cloud node based on the received first request; and receiving a second notification from the IMS / DMS that the second O cloud node has been blocked. Item

[10] : The device described in Item [8] or [9], wherein the first request is triggered by an rApp of a non-RT RIC or by a manual request submitted via a service management and orchestration framework (SMO). Item

[11] : The device described in any one of items [8] to

[10] , wherein the second request is sent to the IMS / DMS only by the SMO function based on determining by the SMO function that the first request to block at least one O cloud node is valid. Item

[12] : The device described in any one of items [8] to

[11] , wherein at least one processor is further configured to execute computer-executable instructions to control the IMS / DMS to block at least one O cloud node based on a second request to mark the O cloud node as unschedulable. Item

[13] : The device described in any one of items [8] to

[11] , wherein at least one processor is further configured to execute computer-executable instructions for receiving a first notification that an O cloud node has been blocked by receiving, via the SMO function, a first notification from the IMS / DMS via the O2 interface that at least one O cloud node has been blocked. Item

[14] : The device described in Item

[13] , wherein at least one processor is further configured to execute computer-executable instructions for receiving a first notification that an O cloud node has been blocked by receiving, by an rApp of a non-RT RIC, a first notification from an SMO function that at least one O cloud node has been blocked. Item

[15] : A non-transitory computer-readable storage medium having stored thereon instructions executable by at least one processor to cause at least one processor to perform a method including: receiving, by a service management and orchestration framework (SMO) function, a first request to shut down at least one O cloud node, where the first request is received from a user terminal or from an rApp of a non-real-time (Non-RT) RAN intelligent controller (RIC); sending, by the SMO function, a second request to shut down at least one O cloud node based on the received first request to an infrastructure management service (IMS) and / or deployment management service (DMS) via an O2 interface; and receiving a first notification from the IMS / DMS that the at least one O cloud node has been shut down, wherein the SMO function is at least one of a federated O cloud orchestration and management (FOCOM) and a network function orchestration (NFO). Item

[16] : The non-transitory computer-readable storage medium of Item

[15] , wherein the second request is an instruction to block a first O cloud node of the at least one O cloud node, and the first notification indicates that the first O cloud node has been blocked, and the method further includes: sending, by the SMO function, a third request to the IMS / DMS via the O2 interface to block a second O cloud node of the at least one O cloud node based on the received first request; and receiving a second notification from the IMS / DMS that the second O cloud node has been blocked. Item

[17] : A non-transitory computer-readable storage medium according to item

[15] or

[16] , wherein the first request is triggered by an rApp of a non-RT RIC or by a manual request submitted via a service management and orchestration framework (SMO). Item

[18] : A non-transitory computer-readable storage medium described in any one of items

[15] to

[17] , wherein the second request is sent to the IMS / DMS only by the SMO function based on the SMO function determining that the first request to block at least one O cloud node is valid. Item

[19] : A non-transitory computer-readable storage medium described in any one of items

[15] to

[18] , further comprising controlling, by the IMS / DMS, to block at least one O cloud node based on a second request to mark the O cloud node as unschedulable. Item

[20] : A non-transitory computer-readable storage medium described in any one of items

[15] to

[18] , wherein receiving a first notification that an O cloud node has been blocked further includes receiving, by the SMO function, a first notification from the IMS / DMS via the O2 interface that at least one O cloud node has been blocked.

[0088] It will be appreciated that many modifications and variations of the present disclosure are possible in light of the above teachings. It will be apparent that, within the scope of the appended clauses, the present disclosure may be practiced otherwise than as specifically described herein.

Claims

1. 1. A method for blocking one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes, comprising: receiving, by a service management and orchestration framework (SMO) function, a first request to shut down at least one O-cloud node, the first request being received from a user terminal or from an rApp of a non-real-time (Non-RT) RAN intelligent controller (RIC); sending, by the SMO function, a second request to an Infrastructure Management Service (IMS) and / or a Deployment Management Service (DMS) via an O2 interface to shut down the at least one O cloud node based on the received first request; receiving a first notification from the IMS / DMS that the at least one O cloud node has been blocked; Including, The method, wherein the SMO function is at least one of Federated Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).

2. the second request is an instruction to shut down a first O cloud node of the at least one O cloud node, the first notification indicates that the first O cloud node has been shut down, and the method further comprises: sending, by the SMO function, via an O2 interface to the IMS / DMS, a third request to block a second O cloud node of the at least one O cloud node based on the received first request; receiving a second notification from the IMS / DMS that the second O cloud node has been blocked; The method of claim 1 further comprising:

3. The method of claim 1 , wherein the first request is triggered by an rApp of the non-RT RIC or by a manual request submitted via a Service Management and Orchestration Framework (SMO).

4. 2. The method of claim 1, wherein the second request is sent to the IMS / DMS only by the SMO function based on determining, by the SMO function, that the first request to block the at least one O cloud node is valid.

5. 2. The method of claim 1, further comprising: controlling, by the IMS / DMS, to block the at least one O cloud node based on the second request to mark the O cloud node as unschedulable.

6. receiving the first notification that the O cloud node has been blocked; receiving, by the SMO function, the first notification from the IMS / DMS via the O2 interface that the at least one O cloud node has been blocked; The method of claim 1 further comprising:

7. receiving the first notification that the O cloud node has been blocked; receiving, by the rApp of the non-RT RIC, the first notification from the SMO function that the at least one O cloud node has been blocked; The method of claim 6 further comprising:

8. 1. An apparatus for blocking one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) nodes, comprising: at least one memory storing computer-executable instructions; receiving, by a service management and orchestration framework (SMO) function, a first request to shut down at least one O-cloud node, the first request being received from a user terminal or from an rApp of a non-real-time (Non-RT) RAN intelligent controller (RIC); sending, by the SMO function, a second request to an Infrastructure Management Service (IMS) and / or a Deployment Management Service (DMS) via an O2 interface to shut down the at least one O cloud node based on the received first request; Executing the computer-executable instructions to receive a first notification from the IMS / DMS that the at least one O cloud node has been blocked. at least one processor configured to Equipped with 10. The apparatus, wherein the SMO functionality is at least one of Federated Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).

9. the second request is an instruction to shut down a first O cloud node of the at least one O cloud node, the first notification indicates that the first O cloud node has been shut down, and the at least one processor: sending, by the SMO function, a third request to the IMS / DMS via an O2 interface to block a second O cloud node of the at least one O cloud node based on the received first request; Executing the computer-executable instructions to receive a second notification from the IMS / DMS that the second O cloud node has been blocked. The apparatus of claim 8 further configured to:

10. 10. The apparatus of claim 8, wherein the first request is triggered by an rApp of the non-RT RIC or by a manual request submitted via a Service Management and Orchestration Framework (SMO).

11. 9. The apparatus of claim 8, wherein the second request is sent to the IMS / DMS only by the SMO function based on the SMO function determining that the first request to block the at least one O cloud node is valid.

12. the at least one processor: Executing the computer-executable instructions for controlling, by the IMS / DMS, blocking the at least one O cloud node based on the second request to mark the O cloud node as unschedulable. The apparatus of claim 8 further configured to:

13. the at least one processor: Executing the computer-executable instructions for receiving the first notification that the O cloud node has been blocked by the SMO function receiving the first notification that the at least one O cloud node has been blocked from the IMS / DMS via the O2 interface. The apparatus of claim 8 further configured to:

14. the at least one processor: Executing the computer-executable instructions for receiving the first notification that the O cloud node has been blocked by the rApp of the non-RT RIC from the SMO function, the first notification that the at least one O cloud node has been blocked. The apparatus of claim 13 further configured to:

15. the at least one processor; receiving, by a service management and orchestration framework (SMO) function, a first request to shut down at least one O-cloud node, the first request being received from a user terminal or from an rApp of a non-real-time (Non-RT) RAN intelligent controller (RIC); sending, by the SMO function, a second request to an Infrastructure Management Service (IMS) and / or a Deployment Management Service (DMS) via an O2 interface to shut down the at least one O cloud node based on the received first request; receiving a first notification from the IMS / DMS that the at least one O cloud node has been blocked; Including, 1. A non-transitory computer-readable storage medium having stored thereon instructions executable by at least one processor to perform a method, wherein the SMO functionality is at least one of Federated Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).

16. the second request is an instruction to shut down a first O cloud node of the at least one O cloud node, the first notification indicates that the first O cloud node has been shut down, and the method further comprises: sending, by the SMO function, a third request to the IMS / DMS via an O2 interface to block a second O cloud node of the at least one O cloud node based on the received first request; receiving a second notification from the IMS / DMS that the second O cloud node has been blocked; 16. The non-transitory computer-readable storage medium of claim 15, further comprising:

17. 16. The non-transitory computer-readable storage medium of claim 15, wherein the first request is triggered by an rApp of the non-RT RIC or by a manual request submitted via a Service Management and Orchestration Framework (SMO).

18. 16. The non-transitory computer-readable storage medium of claim 15, wherein the second request is sent to the IMS / DMS only by the SMO function based on determining, by the SMO function, that the first request to block the at least one O cloud node is valid.

19. and controlling, by the IMS / DMS, to block the at least one O cloud node based on the second request to mark the O cloud node as unschedulable.

16. The non-transitory computer-readable storage medium of claim 15, further comprising:

20. receiving the first notification that the O cloud node has been blocked; receiving, by the SMO function, the first notification from the IMS / DMS via the O2 interface that the at least one O cloud node has been blocked; 16. The non-transitory computer-readable storage medium of claim 15, further comprising:

Images