O-cloud node cancellation blockade
By receiving and responding to requests to change the deployable state of O-cloud nodes, the problem of node blocking in O-RAN technology is solved, enabling rapid node recovery and efficient maintenance, and improving network performance and security.
Patent Information
- Application Number
- CN202280094976.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2022-08-25
- Filing Date
- 2022-11-29
- Publication Date
- 2024-11-29
AI Technical Summary
Existing O-RAN technology fails to provide an effective way to unblock O-cloud nodes, limiting supplier diversification and network security, and increasing the cost and cybersecurity risks of switching suppliers.
By receiving and responding to requests to change the deployable state of O-cloud nodes, and transmitting an indication that the deployable state of O-cloud nodes has been modified, the transition from a blocked state to an unblocked state is achieved, allowing nodes to resume deploying applications and workloads.
It improves the schedulability of O-cloud nodes, reduces unplanned state time, optimizes network performance and productivity, and provides fast and effective maintenance and security.
Smart Images

Figure CN119054335A_ABST
Abstract
Description
[0001] CROSS-REFERENCE TO RELATED APPLICATIONS
[0002] This application is based on and claims priority from Singapore Provisional Patent Application No. 10202250829N filed with the Singapore Patent Office on August 25, 2022, the disclosure of which is incorporated herein by reference in its entirety. Technical Field
[0003] Systems, methods, and apparatus consistent with example embodiments of the present disclosure relate to an open radio access network (O-RAN), and more particularly, to systems, methods, and apparatus for unblocking one or more O-RAN cloud (O-Cloud) nodes. Background Art
[0004] Prior to the development of O-RAN technology, radio access networks (RANs) used a "closed" system that relied on a proprietary interface between the radio and baseband unit, which limited the ability of service providers to diversify radio and baseband unit suppliers. In order to provide wireless services to customers, service providers need to select a specific supplier and make a large investment in the supplier's equipment. For service providers, changing from one supplier to another is a burdensome and often costly option. These inhibitors create barriers to entry for new suppliers, allowing existing suppliers to maintain high prices and eventually be absorbed by the service provider's customers. Additionally, service providers that rely heavily on a single supplier may face cybersecurity risks associated with potential security vulnerabilities in the supplier's software.
[0005] O-RAN technology "opens up" these previously proprietary interfaces and protocols, giving service providers more choices in suppliers, increasing flexibility in deployment options, and new capabilities such as automation, analytics, and network slicing. O-RAN technology removes barriers to entry, increases supplier competition, promotes innovation, enables agile multi-supplier deployment, reduces equipment costs for service providers (thereby reducing costs for service provider customers), and reduces network security risks.
[0006] Despite these advantages, the related art O-RAN technology still has problems. In particular, the current O-RAN technology fails to provide an effective way to unblock O-cloud nodes.
[0007] Improvements that address this deficiency are presented herein. These improvements may also be applicable to other technologies and telecommunication standards that use these technologies. Summary of the invention
[0008] A simplified summary of one or more embodiments of the present disclosure is presented below to provide a basic understanding of such embodiments. This summary is not an extensive overview of all contemplated embodiments, and is neither intended to identify key or important elements of all embodiments, nor to describe the scope of any or all embodiments. Its sole purpose is to present some concepts of one or more embodiments of the present disclosure in a simplified form as a prelude to a more detailed description presented later.
[0009] According to an exemplary embodiment, a method includes receiving a request to change the deployable state of an O-cloud node. The method includes changing the deployable state of the O-cloud node in response to receiving the request. The method also includes transmitting an indication that the deployable state of the O-cloud node has been modified in response to changing the deployable state.
[0010] According to an exemplary embodiment, a method includes transmitting a request to change the deployable state of an O-cloud node, which changes the deployable state of the O-cloud node from a blocked state in which the O-cloud node cannot deploy at least one of an application, a workload, or a network function to an unblocked state in which the O-cloud node can deploy at least one of the application, the workload, or the network function.
[0011] According to an exemplary embodiment, an apparatus in an open radio access network (O-RAN) includes: at least one memory configured to store computer program code; and at least one processor configured to access the at least one memory and operate as instructed by the computer program code. The computer program code includes a receiving code configured to cause at least one of the at least one processor to receive a request to change the deployable state of the O-cloud node. The computer program code includes a changing code configured to cause at least one of the at least one processor to change the deployable state of the O-cloud node in response to receiving the request. The computer program code also includes a transmission code configured to cause at least one of the at least one processor to transmit an indication that the deployable state of the O-cloud node has been modified in response to changing the deployable state.
[0012] Additional embodiments will be set forth in the description which follows and, in part, will be apparent from the description, and / or may be learned by practice of the presented embodiments of the disclosure. BRIEF DESCRIPTION OF THE DRAWINGS
[0013] The above and other aspects, features and aspects of embodiments of the present disclosure will be apparent from the following description in conjunction with the accompanying drawings, in which:
[0014] Figure 1 is a diagram of an example network device according to various embodiments of the present disclosure;
[0015] Figure 2 is a schematic diagram of an example O-RAN communication system according to various embodiments of the present disclosure;
[0016] Figure 3 illustrates an O-RAN architecture according to various embodiments of the present disclosure;
[0017] Figure 4A and Figure 4B The O-cloud identification process and the O-cloud node unblocking process according to various embodiments of the present disclosure are respectively illustrated; and
[0018] Figure 5 An example flow chart of an O-cloud node unblocking process according to various embodiments of the present disclosure is illustrated. DETAILED DESCRIPTION
[0019] The following detailed description of example embodiments refers to the accompanying drawings.The same reference numbers in different drawings may identify the same or similar elements.
[0020] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementation to disclosed precise forms. In view of the above disclosure, modifications and variations are possible, or modifications and variations can be obtained from the practice of implementation. Further, one or more features or components of an embodiment can be incorporated into another embodiment (or, one or more features of another embodiment) or combined with it. Additionally, in the flow charts and operational descriptions provided below, it is to be understood that one or more operations can be omitted, one or more operations can be added, one or more operations can be performed simultaneously (at least in part), and the order of one or more operations can be switched.
[0021] It will be apparent that the systems and / or methods described herein can 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 does not limit the implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it is to be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.
[0022] Even though particular combinations of features are recited in the claims and / or disclosed in the specification, these combinations are not intended to limit the disclosure of possible implementations. In fact, many of these features may be combined in ways not specifically recited in the claims and / or disclosed in the specification. Although each of the dependent claims listed below may directly depend on only one claim, the disclosure of possible implementations includes each dependent claim in combination with every other claim in the claim set.
[0023] Unless explicitly described in this way, the elements, actions or instructions used herein should not be interpreted as key or necessary. Moreover, as used herein, the articles "one" and "an" are intended to include one or more projects and can be used interchangeably with "one or more". In the case of only one project, the term "one" or similar language is used. Moreover, as used herein, the terms "having", "containing", "having", "including", "including", etc. are intended to be open terms. Further, unless otherwise explicitly stated, the phrase "based on" is intended to mean "based at least in part". In addition, expressions such as "at least one of [A] and [B]" or "at least one of [A] or [B]" should be understood to include only A, only B, or both A and B.
[0024] References throughout this specification to "one embodiment," "an embodiment," or similar language mean that a particular feature, structure, or characteristic described in connection with the indicated embodiment is included in at least one embodiment of the present solution. Thus, the phrases "in one embodiment," "in an embodiment," and similar language throughout this specification may, but do not necessarily, all refer to the same embodiment.
[0025] In addition, the described features, advantages and characteristics of the present disclosure may be combined in any suitable manner in one or more embodiments. Those skilled in the relevant art will recognize that, in view of the description herein, the present disclosure may be practiced without one or more specific features or advantages of a particular embodiment. In other examples, it may be recognized in certain embodiments that additional features and advantages may not be present in all embodiments of the present disclosure.
[0026] Embodiments of the present disclosure relate to systems, methods, and apparatus for unblocking one or more O-Cloud nodes. Figure 1 is a diagram of an example device 100 for implementing the systems, methods, and apparatus of the present disclosure. Device 100 may implement any application disclosed herein as well as any O-RAN RIC and any artificial intelligence / machine learning (AI / ML) framework. Device 100 may correspond to any type of known computer, server, or data processing device. For example, device 100 may include a processor, a personal computer (PC), a printed circuit board (PCB) including a computing device, a minicomputer, a mainframe computer, a microcomputer, a telephone computing device, a wired / wireless computing device (e.g., a smartphone, a personal digital assistant (PDA)), a laptop computer, a tablet computer, a smart device, or any other device with similar functions.
[0027] In some embodiments, Figure 1As shown, device 100 may include a collection of components, such as a processor 120 , a memory 130 , a storage component 140 , an input component 150 , an output component 160 , and a communication interface 170 .
[0028] The bus 110 may include one or more components that allow communication between the components of the device 100. For example, the bus 110 may be a communication bus, a crossbar, a network, etc. Although the bus 110 may be Figure 1 Although depicted as a single line in FIG. 1 , bus 110 may be implemented using multiple (two or more) connections between the collection of components of device 100. The present disclosure is not limited in this respect.
[0029] Device 100 may include one or more processors, such as processor 120. Processor 120 may be implemented in hardware, firmware, and / or a combination of hardware and software. For example, processor 120 may include 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), a general purpose single-chip or multi-chip processor or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof, which is designed to perform the functions described herein. A general purpose processor may be a microprocessor or any conventional processor, controller, microcontroller, or state machine. Processor 120 may also be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in combination with a DSP core, or any other such configuration. In some embodiments, specific processes and methods may be performed by circuit systems specific to a given function.
[0030] Processor 120 may control the overall operation of device 100 and / or a set of components of device 100 (eg, memory 130 , storage component 140 , input component 150 , output component 160 , and communication interface 170 ).
[0031] Device 100 may also include memory 130. In some embodiments, memory 130 may include random access memory (RAM), read-only memory (ROM), electrically erasable programmable ROM (EEPROM), flash memory, magnetic memory, optical memory, and / or another type of dynamic or static storage device. Memory 130 may store information and / or instructions for use (e.g., execution) by processor 120.
[0032] The storage component 140 of the device 100 may store information and / or computer-readable instructions and / or code related to the operation and use of the device 100. For example, the storage component 140 may include a hard disk (e.g., a magnetic disk, an optical disk, a magneto-optical disk, and / or a solid-state disk), a compact disk (CD), a digital versatile disk (DVD), a universal serial bus (USB) flash drive, a Personal Computer Memory Card International Association (PCMCIA) card, a floppy disk, a magnetic cassette, a magnetic tape, and / or another type of non-transitory computer-readable medium and a corresponding drive.
[0033] Device 100 may also include input component 150. Input component 150 may include one or more components that allow device 100 to receive information, such as via user input (e.g., a touch screen, keyboard, keypad, mouse, stylus, buttons, switches, microphone, camera, etc.). Alternatively or additionally, input component 150 may include a sensor for sensing information (e.g., a global positioning system (GPS) component, an accelerometer, a gyroscope, an actuator, etc.).
[0034] Output components 160 of device 100 may include one or more components (e.g., a display, a liquid crystal display (LCD), a light emitting diode (LED), an organic light emitting diode (OLED), a tactile feedback device, a speaker, etc.) that can provide output information from device 100.
[0035] The device 100 may also include a communication interface 170. The communication interface 170 may include a receiver component, a transmitter component and / or a transceiver component. The communication interface 170 may enable the device 100 to establish a connection and / or transfer communication with other devices (e.g., a server, another device). Communication may be achieved via a wired connection, a wireless connection, or a combination of a wired and wireless connection. The communication interface 170 may allow the device 100 to receive information from another device and / or provide information to another device. In some embodiments, the communication interface 170 may provide communication with another device via a network, such as a local area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a private network, a self-organizing network, an intranet, the Internet, a fiber-based network, 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 telephone network (e.g., a public switched telephone network (PSTN)), etc. and / or a combination of these or other types of networks. Alternatively or additionally, the communication interface 170 may provide communication with another device via a device-to-device (D2D) communication link, such as FlashLinQ, WiMedia, Bluetooth, ZigBee, Wi-Fi, LTE, 5G, etc. In other embodiments, the communication interface 170 may include an Ethernet interface, an optical interface, a coaxial interface, an infrared interface, a radio frequency (RF) interface, etc.
[0036] The device 100 may be included in the core network 240 and perform one or more processes described herein. The device 100 may perform operations based on the processor 120 executing computer-readable instructions and / or codes that may be stored by a non-transient computer-readable medium (such as, memory 130 and / or storage component 140). The computer-readable medium may refer to a non-transient memory device. The memory device may include memory space within a single physical storage device and / or memory space spread across multiple physical storage devices.
[0037] The computer-readable instructions and / or code may be read into the memory 130 and / or storage component 140 from another computer-readable medium or from another device via the communication interface 170. The computer-readable instructions and / or code stored in the memory 130 and / or storage component 140, if or when executed by the processor 120, may cause the device 100 to perform one or more processes described herein.
[0038] Alternatively or additionally, hardwired circuitry may be used in place of or in combination with software instructions to perform one or more processes described herein.Thus, the embodiments described herein are not limited to any specific combination of hardware circuitry and software.
[0039] Figure 1 The number and arrangement of components shown are provided as examples. Figure 1 There may be additional components, fewer components, different components, or components arranged differently than those shown. Figure 1 Two or more components shown may be implemented in a single component, or Figure 1 The single component shown may be implemented as multiple distributed components. Additionally or alternatively, Figure 1 The assembly of (one or more) components shown may perform the operations described by Figure 1 Another component shown may be a collection of components that perform one or more functions.
[0040] Figure 2 2 is a diagram illustrating an example O-RAN communication system 200 according to various embodiments of the present disclosure. The O-RAN communication system 200 may include one or more user equipment (UE) 210, one or more O-RAN radio units (O-RU) 220 (including one or more base stations 220a), one or more O-RAN distribution units (O-DU) 230, and one or more O-RAN centralized units (O-CU) 240.
[0041] Examples of UE 210 may include a cellular phone, a smart phone, a Session Initiation Protocol (SIP) phone, a laptop computer, a personal digital assistant (PDA), a satellite radio, a global positioning system (GPS), a multimedia device, a video device, a digital audio player (e.g., an MP3 player), a camera, a game console, a tablet computer, a smart device, a wearable device, a vehicle, an electric meter, a gas pump, large and small kitchen appliances, a healthcare device, an implant, a sensor / actuator, a display, or any other similarly functional device. Some of the one or more UEs 210 may be referred to as Internet of Things (IoT) devices (e.g., parking meters, gas pumps, toasters, vehicles, heart monitors, etc.). One or more UE 210 may also be referred to as a station, a mobile station, a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent, a mobile agent, a client, or some other suitable terminology.
[0042] One or more base stations 220A of the O-RU 220 may wirelessly communicate with one or more UEs 210. Each of the one or more base stations 220A may provide communication coverage to one or more UEs 210 located within a geographic coverage area of the base station 220A. Figure 2As shown, the base station 220A may transmit one or more beamforming signals in one or more transmission directions to one or more UEs 210. The one or more UEs 210 may receive the beamforming signals from the base station 220A in one or more reception directions. Alternatively or additionally, the one or more UEs 210 may transmit the beamforming signals to the base station 220 in one or more transmission directions. The base station 220A may receive the beamforming signals from the one or more UEs 210 in one or more reception directions.
[0043] One or more base stations 220A may include macro cells (e.g., high-power cellular base stations) and / or small cells (e.g., low-power cellular base stations). Small cells may include femto cells, pico cells, and micro cells. Whether macro cells or large cells, base stations 220A may include and / or be referred to as access points (APs), evolved (or, evolved universal terrestrial radio access network (E-UTRAN)) Node Bs (eNBs), next generation Node Bs (gNBs), or any other type of base station known to those of ordinary skill in the art.
[0044] In some embodiments, the O-RU 220 may be connected to the O-DU 230 via a FH link 224. The FH link may be a 25Gbps line where user plane (U-plane) and control plane (C-plane) packets are downloaded from the O-DU 230 to the O-RU 220. In some embodiments, the O-DU 230 may be connected to the O-CU 240 via a midhaul link 234. The O-CU 240 may include an O-CU control plane (O-CU-CP) packet generator 240A and an O-CU user plane (O-CU-UP) packet generator 240B. The C-plane and U-plane packets may originate from the O-CU-CP packet generator 240A and the O-CU-UP packet generator 240B, respectively. These components enable the radio access network (RAN) of the telecommunications system to connect one or more UEs 210 to other parts of the network.
[0045] The O-RAN communication system 200 may decompose RAN functions via the O-CU 240, the O-DU 230, and the O-RU 220. The O-CU 240 may be 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 O-DU 230 may be a logical node for hosting the radio link control (RLC), medium access control (MAC), and physical (PHY) sublayers of the RAN. The O-RU 220 is a physical node that converts radio signals from the antenna into digital signals, which may be transmitted to the O-DU 230 via a "fronthaul".
[0046] Figure 3 An example network architecture 300 that can be used to implement the techniques described herein is illustrated. The network architecture 300 may include, for example, an O-RU 320, an O-DU 330, an O-CU-CP 340A, an O-CU-UP 340B, and a service management and orchestration (SMO) 360. The RAN functions in the O-RAN architecture 300 may be controlled and optimized by one or more radio access network intelligent controllers (RICs). The RIC is a software-defined component that implements modular applications to facilitate the multi-supplier operability required in the O-RAN system 300 and to automate and optimize RAN operations. The RIC is divided into two types: non-real-time RIC (NRT-RIC) 362 and near real-time RIC (nRT-RIC) 350.
[0047] NRT-RIC 362 is the control point of the non-real-time control loop and operates at a time scale greater than 1 second within the service management and orchestration (SMO) framework. Its functionality is implemented through modular applications called rApps. The functionality includes: providing policies (i.e., a set of rules used to manage and control the changes and / or maintenance of the state of one or more managed objects) based on guidance and improvement across the A1 interface, which is the interface that enables communication between NRT-RIC 362 and nRT-RIC 350. The A1 policy can be a declarative policy expressed using formal statements that enables the NRT-RIC 362 within the SMO 360 to guide the nRT-RIC 350, thereby guiding the RAN to better achieve the RAN intent; perform data analysis; artificial intelligence / machine learning (AI / ML) training and reasoning for RAN optimization; and / or recommend configuration management actions through the O1 interface to manage operations and maintenance (OAM) 368, which is an interface that connects the SMO 360 to RAN management elements (e.g., nRT-RIC 350, O-CU-CP 340A, O-CU-UP 340B, O-DU 330, etc.).
[0048] The nRT-RIC 350 is located at the edge of the RAN and operates at a time scale between 10 milliseconds and 1 second. The nRT-RIC 350 is connected to the O-DU 330, O-CU-CP 340A, O-CU-UP 340B and the Open Evolved NodeB (O-eNB) (not shown) via the E2 interface. The nRT-RIC 350 controls the underlying RAN elements (E2 nodes / network functions (NFs)) on a near real-time control loop using the E2 interface. The nRT-RIC 350 monitors, suspends / stops, covers and controls E2 nodes (O-CU-CP, O-CU-UP, O-DU and O-eNB) via policies, where the O-DU is connected to the O-RU 320 via a fronthaul including a control user synchronization (CUS) plane and a management (M) plane. For example, the nRT sets policy parameters for the activation function of the E2 node. Further, nRT-RIC 350 hosts xApps to implement functions such as quality of service (QoS) optimization, mobility optimization, slice optimization, interference mitigation, load balancing, security, etc. These two types of RICs work together to optimize O-RAN. For example, NRT-RIC 362 provides policies, data, and AI / ML models implemented and used by nRT-RIC 350 for RAN optimization through the A1 interface, and nRT returns policy feedback (i.e., how the policies set by NRT-RIC 362 work).
[0049] The SMO 360 framework manages and orchestrates RAN elements 363. Specifically, the SMO 360 includes a federated O-Cloud Orchestration and Management (FOCOM) 364, a Network Function Orchestrator (NFO) 366 that manages virtual network functions (VNFs) based on virtual machines (VMs) (not shown) and container (i.e., instance) based VNFs (not shown), and an OAM 368 as part of the SMO 360 that manages and orchestrates the so-called O-Ran Cloud (O-Cloud) 370. The O-Cloud 370 is a collection of physical RAN nodes that host RICs, O-CUs, and O-DUs, supporting software components (e.g., operating systems and runtime environments), and the SMO 360 itself. In other words, the SMO 360 manages the O-Cloud 370 from within. The O2 interface is the interface between the SMO 360 and the O-Cloud 370 where it resides. Through the O2 interface, the SMO 360 provides an Infrastructure Management Service (IMS) 372 and a Deployment Management Service (DMS) 374.
[0050] NRT-RIC 362 may create a RAN optimization policy (i.e., an A1 policy for RAN optimization to achieve RAN intent). NRT-RIC 362 may then pass the policy to nRT-RIC 350 (i.e., A1 policy) via the A1 interface. Upon receiving the A1 policy, nRT-RIC 350 may perform control to implement the policy and execute in a control loop according to the policy.
[0051] As mentioned, Figure 3 An exemplary system architecture 300 is provided that can be used to implement the techniques described herein. In particular, for example, when a node of the O-cloud 370 requires some maintenance, an eviction command and / or a blocking command may be executed. Before maintenance is performed on the node, an eviction command may safely remove, evict, or transfer a pod or instance from the node. For example, eviction may delete all pods of a node (but there may be an exception that a "mirror pod" is not deleted). After an eviction command is executed on a particular node, the node may be referred to as "blocked". When a node is in an eviction or blocking state, the node may be active, but it cannot be used for scheduling, deployment, instantiation, etc. of a process or pod. When a node is blocked, new instances or pods may not be created for the blocked node, however, maintenance (e.g., hardware maintenance, such as changing a network interface card or adding physical memory hardware) may still be performed on the node. In some embodiments, when a node is blocked, there may be a "taint" associated with such a node.
[0052] In some embodiments, the blocking command can ensure that no new pods or instances are scheduled to the node of interest. That is, executing the blocking command may put the node in an unschedulable or unschedulable state. The blocking command can be used to ensure that no new pods or instances are scheduled to the node of interest. When the node is ready for maintenance, the node of interest may be in an unschedulable or unschedulable state. When the node is in an unschedulable state, other commands can be used to move the pod or instance out of the node of interest so that maintenance can be performed on the node. In some embodiments, executing the blocking command removes all pods arranged on the node of interest. Therefore, the scheduler can list the pods / instances removed from the new node and / or the alternative node. In some embodiments, multiple nodes (e.g., node clusters) can be expelled or blocked in sequence or simultaneously. In some embodiments, the node can be marked, labeled, or otherwise given some indicators that the node is in an expelled / expelled or blocked / blocked state.
[0053] After maintenance on the node is complete, the unblock command may allow the node to be scheduled again. In some embodiments, after maintenance is performed on the node, the node must be unblocked so that the node can resume workload deployment on the node. After the unblock command is executed on one or more nodes, pods or instances can be scheduled for such nodes, and pods or instances can be added to such nodes or deployed on such nodes. Figure 3 , SMO 360 can be used to unblock one or more O-cloud nodes. The process of unblocking one or more O-cloud nodes using SMO 360 can be triggered, activated, or caused to occur by a manual process or an automatic process. After the O-cloud node is unblocked, the network function (NF) deployment or application deployment can be restored on the node. For example, one or more and / or one or more VNF deployments (and / or physical network functions (PNFs)) can be restored on the unblocked node. In some embodiments, multiple nodes (e.g., a node cluster) can be unblocked sequentially or simultaneously. In some embodiments, a mark, flag, or other indicator can be added or removed to indicate that the node is in an unblocked or unblocked state.
[0054] Figure 4A and Figure 4B The operations involved in the exemplary O-cloud determination process 402 and the operations involved in the exemplary O-cloud node unblocking process 404 are illustrated respectively. Figure 4A and Figure 4B As shown, there may be one or more personnel 410 (eg, cloud maintainer 410), SMO 420, and O-cloud platform 430. SMO 420 may have NRT-RIC 422 and FOCOM 424, and O-cloud platform 430 may have IMS 432.
[0055] Prior to the O-cloud determination process 402 and / or the O-cloud node unblocking process 404, the system may perform one or more preliminary processes. For example, the system may perform a preliminary process to determine whether the SMO 420 and / or the O-cloud platform 430 are available. In some embodiments, if it is determined that the SMO 420 and the O-cloud platform 430 are available (e.g., have sufficient accessible computing resources), the system proceeds with the O-cloud determination process 402 and the O-cloud node unblocking process 404. Alternatively, the process may be omitted and it may be assumed that the SMO 420 and the O-cloud platform 430 are available. Additionally or alternatively, the system may perform a preliminary process to determine whether the O1 and O2 events have been subscribed to by the cloud maintainer 410, the NRT-RIC 422, or both. In some embodiments, if it is determined that there are O1 and / or O2 event subscriptions, the system proceeds with the O-cloud determination process 402 and the O-cloud node unblocking process 404.
[0056] Figure 4A The O-cloud node determination process 402 may include either or both of operation 442 or operation 444. In operation 442, the cloud maintainer 410 may determine to unblock one or more O-cloud nodes. In some embodiments, the cloud maintainer 410 determines to unblock one or more O-cloud nodes as a manual process performed by one person or a group of people. Further, the cloud maintainer 410 may receive notifications from the SMO 420, and as a result of subscribing to receive notifications, the cloud maintainer 410 may receive such notifications. The cloud maintainer 410 may make a determination based on the received notifications (e.g., O1 data, O2 telemetry data, etc.).
[0057] In operation 444, NRT-RIC 422 may make a determination to unblock an O-cloud node, for example, based on a rApp use case. In some embodiments, NRT-RIC 422 determines that unblocking an O-cloud node is an automated process that involves little human interaction. In some embodiments, SMO 420 may receive a service request that may include one or more identifiers (or, identification data) of the (multiple) O-cloud nodes to be unblocked. SMO 420 may use the received identification data to identify which O-cloud node in one or more O-cloud nodes is to be unblocked. Additionally or alternatively, the process may use other standards or preprogrammed conditions to determine which (multiple) O-cloud nodes are to be unblocked and when such (multiple) O-cloud nodes are to be unblocked. For example, the determination process may use one or more AI / ML algorithms that may be trained using training data; and the determination process may use the trained AI / ML algorithms to determine when and which (multiple) O-cloud nodes will be unblocked (e.g., based on input data, such as O1 data, O2 telemetry data, etc.). If and when the cloud maintainer 410 and / or the NRT-RIC 422 determines that one or more O-cloud nodes are to be unblocked, the O-cloud node unblocking process 404 may be performed.
[0058] In some embodiments, NRT-RIC 422 can request to unblock one or more O-cloud nodes when determining the increase of the computing load on the system, so it may be necessary to deploy additional applications to solve the increased computing load. NRT-RIC422 can determine the increased computing load (or, the increased CPU utilization or the increased CPU demand) by, for example, analyzing the current network business, network business model or via historical network business data. In some embodiments, NRT-RIC 422 periodically evaluates the computing load to quickly respond to the increased computing demand. By requesting one or more O-cloud nodes to unblock, the O-cloud nodes that are subsequently unblocked can be used to deploy additional applications to solve the increased computing load.
[0059] In some embodiments, even if the O-cloud node has completed maintenance, the O-cloud node may remain in an unblocked state until the system determines that such an O-cloud node is necessary to address the actual or expected increase in computing demand. By maintaining the O-cloud node in an unblocked state, the system can save energy and computing resources, thereby optimizing system performance to use an appropriate number of O-cloud nodes based on actual or expected network traffic. This dynamic allocation of O-cloud nodes allows the system to save energy when network traffic is low and gradually increase resource allocation when network traffic is high, thereby providing a system that can achieve high-quality network performance and optimal energy conservation.
[0060] Figure 4B The O-cloud node determination process 404 may begin with a request operation 446. In the request operation 446, there may be a request from the cloud maintainer 410, the NRT-RIC 422, or both. Specifically, in operation 448, the cloud maintainer 410 may facilitate a request to unblock one or more O-cloud nodes. The request of operation 448 may be transferred from a terminal (not shown) operated by the cloud maintainer 410 to the FOCOM 424. Additionally or alternatively, in operation 450, the NRT-RIC 422 may facilitate a request to unblock one or more O-cloud nodes. In some embodiments, one or more rApps may use the NRT-RIC 422 to transmit a request to unblock one or more O-cloud nodes. The request of operation 450 may be transferred from the RT-RIC 450 to the FOCOM 424.
[0061] In some embodiments, the NRT-RIC 422 and / or the cloud maintainer 410 may receive telemetry data when one or more O-cloud nodes are in a blocked state. The received telemetry data may be used by the NRT-RIC 422 and / or the cloud maintainer 410 to determine whether the O-cloud node has completed maintenance so that the O-cloud node can be used to unblock. Additionally or alternatively, the NRT-RIC 422 and / or the cloud maintainer 410 may receive troubleshooting data, which may be used to determine whether one or more O-cloud nodes have completed maintenance so that the O-cloud node can be used to unblock. In some embodiments, the NRT-RIC 422 and / or the cloud maintainer 410 may need to make a determination or receive an indication that the O-cloud node has completed maintenance and can be used to unblock before requesting to unblock such an O-cloud node.
[0062] Determining that one or more existing O-cloud nodes are to be unblocked (by the cloud maintainer 410 or rApp via the NRT-RIC 422) can trigger the FOCOM 424 to unblock a specified set of (multiple) O-cloud nodes. In response to the FOCOM 424 receiving one or more requests to unblock one or more O-cloud nodes, the system can perform operation 452, wherein the FOCOM 424 facilitates the process of unblocking one or more O-cloud nodes identified in the received (multiple) requests. The SMO 420 itself may not be able to perform the process of unblocking the O-cloud nodes, so the SMO 420 may need to interact with the IMS 432 to unblock the O-cloud nodes. The FOCOM 424 can specifically communicate with the IMS 432 of the O-cloud platform 430 using the O2 interface to unblock one or more O-cloud nodes. For example, the FOCOM 424 can use the O2 IMS service to unblock one or more O-cloud nodes. Operation 452 may be repeated for multiple requests from either or both of the cloud maintainer 410 or the NRT-RIC 422 .
[0063] In response to FOCOM 424 communicating with IMS 432, the system may perform operation 454, wherein IMS 432 processes one or more requests to unblock (multiple) O-cloud nodes. The process proceeds to loop 456. Loop 456 includes performing operation 458, wherein IMS 432 unblocks each O-cloud node included in the (multiple) requests simultaneously or sequentially. Loop 456 also includes operation 460, wherein IMS 432 marks each O-cloud node, which is unblocked via operation 458 that can be scheduled for one or more new workload deployments. In some embodiments, operation 458 switches a flag, which causes the O-cloud node to be indicated as unblocked. After each O-cloud node included in the (multiple) request is processed by loop 456 (i.e., unblocked by operation 458 and marked as schedulable for new workload deployment by operation 460), the process proceeds to either or both of operation 462 or operation 464. In operation 462, IMS 432 transmits one or more O-cloud status update notifications to FOCOM424, for example, via the O2 interface. In operation 464, IMS 432 transmits one or more O-cloud status update notifications to NRT-RIC422, for example, via the O2 interface. In some embodiments, the (multiple) notifications in operation 464 only occur if NRT-RIC 422 has subscribed to receive notifications from IMS 432. Either or both of operations 462 or 464 can be included in a notification operation 466, in which SMO 420 is informed of or receives a notification that the O-cloud node unblocking is complete. After operation 466, the unblocked O-cloud node is advantageously ready for one or more new workload deployments, i.e., the unblocked O-cloud node is available.
[0064] The O-cloud determination process 402 and the O-cloud node unblocking process 404 can be used to effectively perform maintenance on one or more O-cloud nodes that need maintenance. Specifically, the O-cloud determination process 402 and the O-cloud node unblocking process 404 can provide the ability to quickly and effectively unblock O-cloud nodes so that the O-cloud nodes can resume NF deployment. The systems, methods, and devices for providing such an ability to quickly and effectively unblock O-cloud nodes reduce the time that O-cloud nodes are in an unschedulable or unschedulable state, thereby ensuring that the O-cloud nodes operate with maximum efficiency, improving productivity, and providing optimal network performance. Therefore, the network service provider can quickly and effectively perform updates or maintenance on the O-cloud nodes, thereby providing added security and a higher quality network.
[0065] Figure 5A flow diagram of an embodiment of an O-cloud node unblocking process 500 is illustrated. The process may begin at operation 502, where a request to change the deployable state of an O-cloud node is received. Next, the process may proceed to operation 504, where the deployable state of the O-cloud node is changed in response to receiving the request. Finally, the process may proceed to operation 506, where in response to changing the deployable state, an indication that the deployable state of the O-cloud node has been modified is transmitted.
[0066] The foregoing disclosure provides illustration and description, but is not intended to be exhaustive or to limit implementations to the precise forms disclosed. Modifications and variations are possible in light of the above disclosure or may be acquired from practice of implementations.
[0067] It is to be understood that the specific order or hierarchy of the blocks in the process / flowchart disclosed herein is a diagram of an example method. Based on design preferences, it is to be understood that the specific order or hierarchy of the blocks in the process / flowchart can be rearranged. Further, some blocks can be combined or omitted. The attached method claims present the elements of each block in a sample order and are not meant to be limited to the specific order or hierarchy presented.
[0068] Some embodiments may involve a system, method and / or computer-readable medium at any possible level of technical detail integration. Further, one or more of the above components 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-transient storage medium (or multiple media) having computer-readable program instructions thereon for causing a processor to perform operations.
[0069] A computer-readable storage medium may be a tangible device that can retain and store 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 the following: a portable computer disk, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or flash memory), a static random access memory (SRAM), a portable compact disk read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanical encoding device (such as a protruding structure in a punch card or a groove, on which instructions are recorded) and any suitable combination of the foregoing. As used herein, a computer-readable storage medium should not be interpreted as a transient signal itself, such as a radio wave or other freely propagating electromagnetic wave, an electromagnetic wave propagated through a waveguide or other transmission medium (e.g., a light pulse passing through a fiber optic cable), or an electrical signal transmitted through a wire.
[0070] The computer-readable program instructions described herein can be downloaded from a computer-readable storage medium to a corresponding computing / processing device, or downloaded to an external computer or external storage device via a network (e.g., the Internet, a local area network, a wide area network, and / or a wireless network). The network may include copper transmission cables, transmission optical fibers, wireless transmissions, routers, firewalls, switches, gateway computers, and / or edge servers. The network adapter card or network interface in each computing / processing device receives the computer-readable program instructions from the network, and forwards the computer-readable program instructions to be stored in a computer-readable storage medium in the corresponding computing / processing device.
[0071] The computer readable program code / instruction for performing the operation can be an assembly instruction, an instruction set architecture (ISA) instruction, a machine instruction, a machine-related instruction, a microcode, a firmware instruction, a state setting data, the configuration data of the integrated circuit system, or a source code or object code written in any combination of one or more programming languages, including object-oriented programming languages (such as, Smalltalk, C++, etc.) and procedural programming languages (such as, "C" programming language or similar programming languages). The computer readable program instruction can be executed completely on the user's computer, partially on the user's computer, executed as an independent software package, partially on the user's computer and partially on a remote computer or completely on a remote computer or server. In the latter scenario, the remote computer can 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 can be connected to an external computer (for example, by using the Internet of an Internet service provider). In some embodiments, the electronic circuit system including, for example, a programmable logic circuit system, a field programmable gate array (FPGA) or a programmable logic array (PLA) can be executed by using the state information personalization electronic circuit system of the computer readable program instruction to perform computer readable program instructions, so as to perform various aspects or operations.
[0072] These computer-readable program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device create components for implementing the functions / actions specified in the boxes or multiple boxes of the flowchart and / or block diagram. These computer-readable program instructions can also be stored in a computer-readable storage medium (which can instruct a computer, a programmable data processing device, and / or other equipment to operate in a specific manner), so that the computer-readable storage medium having the instructions stored therein includes an article of manufacture, which includes instructions for implementing various aspects of the functions / actions specified in the boxes or multiple boxes of the flowchart and / or block diagram.
[0073] These computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other device to cause a series of operational steps to be performed on the computer, other programmable apparatus, or other device to produce a computer-implemented process, so that the instructions executed on the computer, other programmable apparatus, or other device implement the functions / actions specified in a box or multiple boxes in the flowchart and / or block diagram.
[0074] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality and operation of the possible implementation of the system, method and computer-readable medium according to various embodiments. In this regard, each box in the flowchart or block diagram can represent a module, segment or instruction portion, which includes one or more executable instructions for implementing the specified (multiple) logical functions. Compared with the boxes depicted in the accompanying drawings, the method, computer system and computer-readable medium may include additional boxes, fewer boxes, different boxes or boxes with different arrangements. In some alternative implementations, the functions mentioned in the box may not occur in the order mentioned in the accompanying drawings. For example, in fact, the two boxes shown in succession can be executed concurrently or substantially concurrently, or these boxes can sometimes be executed in reverse order, depending on the functionality involved. It will also be mentioned that each box illustrated in the block diagram and / or flowchart and the combination of boxes in the block diagram and / or flowchart can be implemented by a system based on special hardware, which performs a specified function or action or performs a combination of special hardware and computer instructions.
[0075] It will be apparent that the systems and / or methods described herein can 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 does not limit the implementation. Therefore, the operation and behavior of the systems and / or methods are described herein without reference to specific software code - it is to be understood that software and hardware can be designed to implement the systems and / or methods based on the description herein.
[0076] The above disclosure also encompasses the embodiments listed below:
[0077] (1) A method may include: receiving a request to change the deployable state of an O-cloud node; in response to receiving the request, changing the deployable state of the O-cloud node; and in response to changing the deployable state, transmitting an indication that the deployable state of the O-cloud node has been modified.
[0078] (2) A method according to feature (1), wherein changing the deployable state of the O-cloud node includes changing the deployable state from a blocked state to an unblocked state.
[0079] (3) A method according to feature (1) or (2), wherein the O-cloud node is unable to deploy at least one of the applications, workloads, or network functions in a blocked state, and the O-cloud node is able to deploy at least one of the applications, workloads, or network functions in an unblocked state.
[0080] (4) A method according to any one of features (1) to (3), wherein changing the deployable state of the O-cloud node includes changing information associated with a flag or mark indicating the deployable state of the O-cloud node.
[0081] (5) A method according to any one of features (1) to (4), wherein the receiving, changing and transmitting are performed by an infrastructure management service (IMS) of the O-cloud platform.
[0082] (6) A method according to any one of features (1) to (5), wherein receiving a request to change the deployable state of the O-cloud node includes receiving the request from at least one of a user terminal or a non-real-time radio access network intelligent controller (NRT-RIC).
[0083] (7) A method according to any of features (1) to (6), wherein the request is received in response to determining an increase in computational load.
[0084] (8) A method may include transmitting a request to change the deployable state of an O-cloud node, wherein the request changes the deployable state of the O-cloud node from a blocked state in which the O-cloud node cannot deploy at least one of an application, a workload, or a network function to an unblocked state in which the O-cloud node can deploy at least one of an application, a workload, or a network function.
[0085] (9) According to the method of feature (8), it also includes: receiving an indication that the deployable state is changed to an unblocked state.
[0086] (10) A method according to feature (8) or (9), wherein receiving the indication includes receiving information related to an updated flag or mark indicating that the deployable status of the O-cloud node is in an unblocked state.
[0087] (11) The method according to any one of features (8) to (10) further includes: completing deployment to receive a deployable state change indication; and receiving an indication that the deployable state is changed to an unblocked state based on completing a subscription to receive a deployable state change indication.
[0088] (12) A method according to any one of features (8) to (11), wherein the transmission request further comprises a transmission request from at least one of a user terminal or a non-real-time radio access network intelligent controller (NRT-RIC).
[0089] (13) A method according to any one of features (8) to (12), wherein transmitting the request further comprises transmitting the request to a Federated O-Cloud Orchestration and Management (FOCOM) component of a Service Management and Orchestration (SMO) framework.
[0090] (14) A method according to any one of features (8) to (13), wherein the FOCOM communicates with an infrastructure management service (IMS) of the O-cloud platform that performs the change from the blocked state to the unblocked state.
[0091] (15) An apparatus comprising: at least one memory configured to store computer program code; and at least one processor configured to access the at least one memory and operate as directed by the computer program code, the computer program code comprising: receiving code configured to cause at least one of the at least one processor to receive a request to change the deployable state of an open radio access network (O-RAN) cloud (O-cloud) node; changing code configured to cause at least one of the at least one processor to change the deployable state of the O-cloud node in response to receiving the request; and transmitting code configured to cause at least one of the at least one processor to transmit an indication that the deployable state of the O-cloud node has been modified in response to changing the deployable state.
[0092] (16) An apparatus according to feature (15), wherein the change code is further configured to cause at least one of the at least one processor to change the deployable state from a locked state to an unlocked state.
[0093] (17) An apparatus according to feature (15) or (16), wherein the O-cloud node is unable to deploy at least one of the applications, workloads, or network functions in a blocked state, and the O-cloud node is able to deploy at least one of the applications, workloads, or network functions in an unblocked state.
[0094] (18) An apparatus according to any one of features (15) to (17), wherein the receiving code is further configured to cause at least one of the at least one processor to receive a request through an infrastructure management service (IMS) component of the O-cloud platform, the changing code is further configured to cause at least one of the at least one processor to change the deployable state using the IMS, and the transmitting code is further configured to cause at least one of the at least one processor to transmit an indication from the IMS.
[0095] (19) An apparatus according to any one of features (15) to (18), wherein the change code is also configured to cause at least one of the at least one processors to change information associated with a flag or mark indicating a deployable status of the O-cloud node.
[0096] (20) An apparatus according to any one of features (15) to (19), wherein the request is received in response to determining an increase in computing load.
Claims
1. A method comprising: receiving a request to change a deployable state of an open radio access network (O-RAN) cloud (O-Cloud) node; In response to receiving the request, changing the deployable state of the O-cloud node; and In response to changing the deployable state, transmitting an indication that the deployable state of the O-cloud node has been modified.
2. The method according to claim 1, wherein changing the deployable state of the O-cloud node comprises: The deployable state is changed from a blocked state to an unblocked state.
3. The method according to claim 2, wherein: The O-Cloud Node cannot deploy at least one of the following in the blocked state: an application, a workload, or a network function, and The O-cloud node is capable of deploying at least one of the following in the unblocked state: the application, the workload, or the network function.
4. The method according to claim 1, wherein changing the deployable state of the O-cloud node comprises: Information associated with a flag or a mark indicating the deployable state of the O-cloud node is changed. 5 . The method of claim 1 , wherein the receiving, the changing, and the transmitting are performed by an Infrastructure Management Service (IMS) of an O-Cloud platform.
6. The method of claim 1 , wherein receiving the request to change the deployable state of the O-cloud node comprises: The request is received from at least one of a user terminal or a non-real-time radio access network intelligent controller (NRT-RIC).
7. The method of claim 1, wherein the request is received in response to a determination of an increase in computational load.
8. A method comprising: A request is transmitted to change the deployable state of an open radio access network (O-RAN) cloud (O-cloud) node, the request causing the deployable state of the O-cloud node to be changed from a blocked state, in which the O-cloud node cannot deploy at least one of the following: an application, a workload, or a network function, to an unblocked state, in which the O-cloud node is able to deploy at least one of the following: the application, the workload, or the network function.
9. The method according to claim 8, further comprising: An indication is received that the deployable state is changed to the unblocked state.
10. The method of claim 9, wherein receiving the indication comprises: Information related to an updated flag or indicia indicating that the deployable state of the O-cloud node is in the unblocked state is received.
11. The method according to claim 9, further comprising: Completes the subscription to receive deployable state change indications, and The indication that the deployable state is changed to the unblocked state is received based on completing the subscription to receive the deployable state change indication.
12. The method of claim 8, wherein the transmitting the request further comprises: The request is transmitted from at least one of a user terminal or a non-real-time radio access network intelligent controller (NRT-RIC).
13. The method of claim 8, wherein the transmitting the request further comprises: The request is transmitted to a Federated O-Cloud Orchestration and Management (FOCOM) component of a Service Management and Orchestration (SMO) framework.
14. The method of claim 8, wherein the FOCOM communicates with an Infrastructure Management Service (IMS) of an O-Cloud platform that performs the change of the blocked state to the unblocked state.
15. An apparatus comprising: at least one memory configured to store computer program code; as well as at least one processor configured to access the at least one memory and to operate as instructed by the computer program code, the computer program code comprising: receiving code configured to cause at least one of the at least one processor to receive a request to change a deployable state of an open radio access network (O-RAN) cloud (O-Cloud) node; changing code configured to cause at least one of the at least one processor to change the deployable state of the O-cloud node in response to receiving the request; and Transmitting code configured to cause at least one of the at least one processor to transmit an indication that the deployable state of the O-cloud node has been modified in response to changing the deployable state. 16 . The apparatus of claim 15 , wherein the change code is further configured to cause at least one of the at least one processor to change the deployable state from a blocked state to an unblocked state.
17. The device according to claim 16, wherein: The O-Cloud Node cannot deploy at least one of the following in the blocked state: an application, a workload, or a network function, and The O-cloud node is capable of deploying at least one of the following in the unblocked state: the application, the workload, or the network function.
18. The apparatus of claim 15, wherein: The receiving code is further configured to cause at least one of the at least one processor to receive the request through an infrastructure management service (IMS) component of the O-cloud platform, The change code is further configured to cause at least one of the at least one processor to change the deployable state using the IMS, and The transmitting code is further configured to cause at least one of the at least one processor to transmit the indication from the IMS.
19. The apparatus of claim 15, wherein the change code is further configured to cause at least one of the at least one processor to change information associated with a flag or a mark indicating the deployable state of the O-cloud node.
20. The apparatus of claim 15, wherein the request is received in response to a determination of an increase in computational load.
