O-cloud site failure workload recovery

Abstract

Example embodiments of the present disclosure relate to O-Cloud site failure workload recovery. The method may include detecting, by a Network Function Orchestrator (NFO), a failure of a Network Function (NF); and based on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) to recreate the first NF.

Description

O-CLOUD SITE FAILURE WORKLOAD RECOVERYTECHNICAL FIELD

[0001] The present disclosure relates to O-Cloud site failure workload recovery.BACKGROUND

[0002] The information disclosed in this background section is only for the enhancement of understanding of the general background of the disclosure and should not be taken as an acknowledgement or any form of suggestion that this information forms the prior art already known to a person skilled in the art.

[0003] A radio access network (RAN) is an important component in a telecommunications system, as it connects end-user devices (or user equipment) to other parts of the network. The RAN includes a combination of various network elements (NEs) that connect end-users to a core network. Traditionally, hardware and / or software of a particular RAN is vendor specific.

[0004] Open RAN (O-RAN) technology has emerged to enable multiple vendors to provide hardware and / or software to a telecommunications system. Since different vendors are involved, the type of hardware and / or software provided may also be different. That is, different types of NEs may be provided by different vendors, and depending on the specific service, the NE could be virtualized in software form (e.g., virtual machine (VM)-based), or could be in physical hardware form (e.g., non-VM based).

[0005] To this end, O-RAN disaggregates the RAN functions into a centralized unit (CU), a distributed unit (DU), and a radio unit (RU). The CU may be a logical node for hosting Radio Resource Control (RRC), Service Data Adaptation Protocol (SDAP), and / or Packet DataConvergence Protocol (PDCP) sublayers of the RAN. The DU may be a logical node hosting Radio Link Control (RLC), Media Access Control (MAC), and Physical (PHY) sublayers of the RAN. The RU may be a physical node that converts radio signals from antennas to digital signals that can be transmitted over the Front Haul to a DU. Because these entities have open protocols and interfaces between them, they can be developed by different vendors.

[0006] FIG. 1 illustrates an 0-RAN architecture in the related art. RAN functions in the 0-RAN architecture may be controlled and optimized by a RAN Intelligent Controller (RIC). The RIC may be a software-defined component that implements modular applications to facilitate the multivendor operability required in the 0-RAN system, as well as to automate and optimize RAN operations. As shown in FIG. 1, the RIC may be divided into two types: a non-real-time RIC (Non-RT RIC) 120 and a near-real-time RIC (Near-RT RIC) 130.

[0007] The Non-RT RIC 120 may be the control point of a non-real-time control loop and may operate on a timescale greater than 1 second within a Service Management and Orchestration (SMO) framework 110. Its functionalities may be implemented through modular applications called rApps, and may include: providing policy based guidance and enrichment across the Al interface, which is the interface that enables communication between the Non-RT RIC and the Near-RT RIC; performing data analytics; Artificial Intelligence / Machine Learning (AI / ML) training and inference for RAN optimization; and / or recommending configuration management actions over the 01 interface, which may be the interface that connects the SMO to RAN managed elements (e.g., Near-RT RIC 130, 0-RAN Centralized Unit (O-CU) 140,150, 0-RAN Distributed Unit (O-DU) 170, etc.).

[0008] The Near-RT RIC 130 may operate on a timescale between 10 milliseconds and 1 second and may be coupled with the O-DU 170, the O-CU (disaggregated into the O-CU controlplane (O-CU-CP) 140 and the O-CU user plane (O-CU-UP) 150), and an open evolved NodeB (O-eNB) 160 via the E2 interface. The Near-RT RIC 130 may use the E2 interface to control the underlying RAN elements (E2 nodes / network functions (NFs)) over a near-real-time control loop. The Near-RT RIC 130 may monitor, suspend / stop, override, and control the E2 nodes (O-CU 140,150, O-DU 170, and O-eNB 160) via policies. For example, the Near-RT RIC 130 may set policy parameters on activated functions of the E2 nodes. Further, the Near-RT RIC 130 may host xApps to implement functions such as quality of service (QoS) optimization, mobility optimization, slicing optimization, interference mitigation, load balancing, security, etc.

[0009] Here, the O-CU-CP 140 and the O-CU-UP 150 may be coupled to each other via the El interface, and may be coupled to the O-DU 170 via the Fl-c interface and Fl-u interface, respectively. Further, the O-RU 180 maybe coupled to the O-DU 170 via the Open Fronthaul (OF) Control (C), User (U), Synchronization (S), and Management (M) Planes, and may be coupled to the SMO 110 via the OF M-Plane.

[0010] The two types of RICs work together to optimize the O-RAN. For example, the Non-RT RIC 120 may provide the policies, data, and AVML models enforced and used by the Near-RT RIC 130 for RAN optimization, and the Near-RT RIC 130 may return policy feedback (i.e., how the policy set by the Non-RT RIC 120 works).

[0011] As mentioned above, the Non-RT RIC 120 may be located within the SMO framework 110, which manages and orchestrates RAN elements. Specifically, the SMO 110 may manage and orchestrate what is referred to as the O-Ran Cloud (O-Cloud) 190. The O-Cloud 190 may be a collection of physical RAN nodes that host the RICs, O-CUs, and O-DUs, the supporting software components (e.g., the operating systems and runtime environments), and the SMO 110 itself. In other words, the SMO 110 may manage the O-Cloud 190 from within. The 02 interfacemay be the interface between the SMO 110 and the O-Cloud 190 it resides in. Through the 02 interface, the SMO 110 may provide infrastructure management services (IMS) and deployment management services (DMS).

[0012] Typically, an O-Cloud site (e.g., the physical site) may implement worker nodes which can be deployed together in a cluster (e.g., a grouping of nodes). Clusters may also be deployed across multiple O-Cloud sites. Network functions (NF’s) which may implement RAN functions may be deployed in the cluster on the O-Cloud site.SUMMARY

[0013] In the related art, an O-Cloud site failure (e.g., a node failure) may occur which can disrupt service or cause downtime for an NF. While there may be systems which can act as a backup or mechanisms for implementing recovery, there is no method in the related art to easily recover the workload which was previously deployed on a worker node of the cluster on an O-Cloud site. Accordingly, there is a need for a method for recovering the workload on an O-Cloud site in the event of site failure.

[0014] Example embodiments of the present disclosure may provide a method including detecting, by a Network Function Orchestrator (NFO), a failure of a Network Function (NF); and based on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) to recreate the first NF.

[0015] Based on the above example embodiments, an automated recovery process by instructing DMS to recreate the NF deployment may be achieved, enabling efficient and automated recovery, thereby minimizing service disruption without manual intervention.

[0016] According to example embodiments, a network function orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O-RAN) may be provided, the NFO configured to: detect a failure of a Network Function (NF) hosted in an 0-RAN Cloud (O-Cloud) of the O-RAN; and based on detecting the failure, send an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.

[0017] According to example embodiments, a non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method may be provided, the method including: detecting, by a Network Function Orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (0-RAN), a failure of a Network Function (NF) hosted in an O-RAN Cloud (O-Cloud) of the 0-RAN; and based on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.

[0018] 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 realized by practice of the presented embodiments of the disclosure.BRIEF DESCRIPTION OF THE DRAWINGS

[0019] Features, aspects, and advantages of embodiments of the disclosure will be described below with reference to the accompanying drawings, in which like reference numerals denote like elements, and wherein:

[0020] FIG. 1 illustrates an example O-RAN architecture according to the related art, in which one or more example embodiments may be applied;

[0021] FIG. 2 illustrates an example sequence diagram for O-Cloud application workload failover;

[0022] FIG. 3 illustrates an example sequence diagram for creating and failing over to a new cluster in a backup site;

[0023] FIG. 4 illustrates an example sequence diagram for failing over to a backup cluster in a backup site;

[0024] FIG. 5 illustrates an example sequence diagram for cross-site high availability control plane, single-site deployment plane;

[0025] FIG. 6 illustrates an example sequence diagram for cross-site high availability control and deployment planes;

[0026] FIG. 7 illustrates a block diagram of an example method for redeploying a failed workload by a network function orchestrator;

[0027] FIG. 8 illustrates a block diagram of an example device for implementing one or more example embodiments; and

[0028] FIG. 9 illustrates a block diagram of an example environment for implementing one or more example embodiments.DETAILED DESCRIPTION

[0029] The following detailed description of example embodiments refers to the accompanying drawings. 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. Further, 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, the flowchart and description of operations provided below relate to one of the various embodiments. It should be noted that it is possible to make otherembodiments that do not exactly match the flowchart and its description. It is understood that in other embodiments one or more operations may be omitted, one or more operations may be added, one or more operations may be performed simultaneously (at least in part).

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

[0031] Even though particular combinations of features are disclosed in the claims and / or in the specification, these combinations are not intended to limit the disclosure of 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 dependent claim listed below may directly depend on only one claim, the disclosure of implementations includes each dependent claim in combination with every other claim in the claim set.

[0032] No element, act, or instruction used herein should be construed as critical or essential 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.” Also, as used herein, the terms “has,” “have,” “having,” “include,” “including,” or the like are intended to be open-ended terms. Further, the phrase “based on” is intended to mean “based, at least in part, on” unless explicitly stated otherwise. Furthermore, expressions such as “at least one of [A] and[B]”, “[A] and / or [B]”, or “at least one of [A] or [B]”, are to be understood as including only A, only B, or both A and B.

[0033] It shall be noted that, descriptions of example embodiments of the present disclosure may include terms and names defined in one or more standard organizations, such as the 3rd Generation Partnership Project (3GPP) standard organization, the European Telecommunications Standards Institute (ETSI) standard organization, the Open Radio Access Network (0-RAN) Alliance standard organization, and the like.

[0034] According to example embodiments, to address Whole NF Deployment Failure in O-Cloud, this solution ensures rapid redeployment of the affected NF within the same cluster, assuming the cluster remains operational. Once the SMO detects the failure, NFO triggers an automated recovery process by instructing DMS to recreate the NF deployment. This enables efficient, automated recovery, minimizing service disruption without manual intervention.

[0035] According to example embodiments, site failure can be mitigated using high-availability solutions. Clusters can be deployed at a single site or across multiple sites, and different failure recovery strategies exist depending on the cluster configuration. In the event of a site failure, recovery involves either redeploying workloads to an existing cluster, creating a new cluster before redeployment, or dynamically reallocating resources within a multi-site cluster. The appropriate method depends on the distribution of control planes and deployment planes across sites.

[0036] Four examples of recovery solutions for handling site failures in an O-Cloud environment, based on different cluster architectures and redundancy strategies may be described herein.

[0037] Solution 1 A: Creating and failing over to a new cluster in a backup site

[0038] Cluster 1 and all NF deployments exist only in Site 1, and Site 2 does not have a backup cluster pre-provisioned. If Site 1 fails, Cluster 1 is completely lost. The recovery process involves: creating a new cluster (Cluster 2) at Site 2, redeploying NF workloads onto the newly created Cluster 2.

[0039] Solution IB: Failing over to backup cluster in a backup Site

[0040] Cluster 1 is initially created at Site 1, and NF deployments run on Cluster 1. Site 2 already has a backup cluster (Cluster 2) available but is not actively hosting workloads. If Site 1 fails, Cluster 1 and its workloads are lost. The recovery process involves: Redeploying NF workloads onto the existing Cluster 2 at Site 2.

[0041] Solution 1C: Cross-site high availability control plane, single-site deployment plane.

[0042] Cluster 1 spans both Site 1 and Site 2, but only the control plane is distributed across both sites, while the deployment plane exists only in Site 1. If Site 1 fails, Cluster 1 remains operational but loses all deployment plane resources, meaning it can no longer host any workloads. The recovery process involves: Provisioning new deployment plane resources (worker nodes) at Site 2 within the existing Cluster 1, Redeploying NF workloads onto the newly allocated deployment plane at Site 2.

[0043] Solution ID: Cross-site high availability control and deployment planes

[0044] Both Site 1 and Site 2 have control planes and deployment planes, creating a high-availability (HA) cluster that actively runs workloads across both sites. If Site 1 fails, the cluster remains operational, and the only required action is to redeploy affected workloads on available deployment planes at Site 2. This solution follows the same recovery process as node failure, which is described in a separate section.

[0045] Based on the above, an automated recovery process by instructing DMS to recreate the NF deployment may be achieved, enabling efficient and automated recovery, thereby minimizing service disruption without manual intervention.

[0046] It is contemplated that features, advantages, and significances of example embodiments described hereinabove are merely a portion of the present disclosure, and are not intended to be exhaustive or to limit the scope of the present disclosure. Further descriptions of the features, components, configuration, operations, and implementations of the example embodiments of the present disclosure are provided in the following.

[0047] FIG. 2 illustrates an example sequence diagram for O-Cloud application workload failover.

[0048] Service Management Orchestration framework (SMO) 200 may be provided, including FOCOM 201 and NFO 202. O-Cloud 210 may also be provided, including IMS 211, DMS 212, the old NF deployment 213, and new NF deployment 214. DMS 212, old NF deployment 213, and new NF deployment 214 may be deployed in the cluster. As a pre-condition, the cluster is provisioned, and a NF deployment may be running thereon. A NF deployment on old NF deployment 213 may go down (e.g., failure), and SMO 200 may detect the NF deployment failure.

[0049] At

[0001] , the NFO 202 may instruct DMS 212 to recreate the NF deployment.

[0050] At

[0002] , the DMS 212 may send the instruction to recreate NF deployment to new NF deployment 214. Accordingly, the workload is recovered.

[0051] FIG. 3 illustrates an example sequence diagram for creating and failing over to a new cluster in a backup site. In this example use-case, Cluster 1 and all NF deployments exist onlyin Site 1, and Site 2 does not have a backup cluster pre-provisioned. If Site 1 fails, Cluster 1 is completely lost.

[0052] SMO 200 may be provided, including FOCOM 201 and NFO 202. O-Cloud 210 may also be provided, including IMS 211, O-Cloud Site 1 220 implementing cluster 1, and O-Cloud Site 2230 implementing cluster 2. O-Cloud Site 1 220 may include DMS 221 and worker nodes 222, and O-Cloud Site 2 230 may include DMS 231 and worker nodes 232. As a precondition, cluster 1 is already created, and NF deployments may be created and running on cluster 1.

[0053] At

[0001] , an alarm may be configured by FOCOM 201 with IMS 211.

[0054] At

[0002] , IMS 211 may detect that site 1 fails.

[0055] At

[0003] , the alarm configured at IMS 211 is triggered and detected by FOCOM 201.

[0056] At

[0004] , FOCOM 201 may instruct IMS 211 to create cluster 2 at O-Cloud Site 2 230.

[0057] At

[0005] , IMS 211 may provision the DMS 231 at Site 2.

[0058] At

[0006] , IMS 211 may provision worker nodes 232 at Site 2.

[0059] At

[0007] , NFO 202 may instruct DMS 231 to recreate NF deployment(s) on cluster 2.

[0060] At

[0008] , DMS 231 may recreate NF deployment(s) on worker nodes 232. Accordingly, the workload may be recovered.

[0061] FIG. 4 illustrates an example sequence diagram for failing over to a backup cluster in a backup site. In this example use-case, Cluster 1 is initially created at Site 1, and NF deployments run on Cluster 1. Site 2 already has a backup cluster (Cluster 2) available but is notactively hosting workloads. If Site 1 fails, Cluster 1 and its workloads are lost. Cluster 1 spans both Site 1 and Site 2, but only the control plane is distributed across both sites, while the deployment plane exists only in Site 1. If Site 1 fails, Cluster 1 remains operational but loses all deployment plane resources, meaning it can no longer host any workloads.

[0062] Service Management Orchestration framework (SMO) 200 may be provided, including FOCOM 201 and NFO 202. O-Cloud 210 may also be provided, including IMS 211, DMS 212, the old NF deployment 213, and new NF deployment 214. DMS 212, old NF deployment 213, and new NF deployment 214 may be deployed in the cluster. As a pre-condition, the cluster is provisioned, and a NF deployment may be running thereon. A NF deployment on old NF deployment 213 may go down (e.g., failure), and SMO 200 may detect the NF deployment failure.

[0063] At

[0001] , an alarm may be configured by FOCOM 201 with IMS 211.

[0064] At

[0002] , IMS 211 may detect that site 1 fails.

[0065] At

[0003] , the alarm configured at IMS 211 is triggered and detected by FOCOM 201.

[0066] At

[0004] , IMS 211 may send an inventory change notice to FOCOM 201.

[0067] At

[0005] , NFO 202 may instruct DMS 231 to recreate NF deployment(s) on cluster 2.

[0068] At

[0006] , DMS 231 may recreate NF deployment(s) on worker nodes 232. Accordingly, the workload may be recovered.

[0069] FIG. 5 illustrates an example sequence diagram for cross-site high availability control plane, single-site deployment plane. In this example use-case, Cluster 1 spans both Site 1 and Site 2, but only the control plane is distributed across both sites, while the deployment planeexists only in Site 1. If Site 1 fails, Cluster 1 remains operational but loses all deployment plane resources, meaning it can no longer host any workloads.

[0070] SMO 200 may be provided, including FOCOM 201 and NFO 202. O-Cloud 210 may also be provided, including IMS 211, and a cluster having DMS 212, O-Cloud Site 1 220, and O-Cloud Site 2 230, wherein the O-Cloud Sites 1 220 and O-Cloud Site 2 230 are on the same cluster. O-Cloud Site 1 220 may implement Control Plane Node 1 223 and Worker Nodes 222, and O-Cloud Site 2230 may implement Control Plane Node 2233 and New Worker Nodes 234. As a precondition, cluster may be running across Site 1 and Site 2, NF deployment(s) are created and running on the cluster, and Site 2 has available capacity of additional nodes.

[0071] At

[0001] , an alarm may be configured by FOCOM 201 with IMS 211.

[0072] At

[0002] , IMS 211 may detect that site 1 fails. At this point, the cluster may be running across sites with worker nodes in site 1 only. Site 1 goes down.

[0073] At

[0003] , the alarm configured at IMS 211 is triggered and detected by FOCOM 201.

[0074] At

[0004] , IMS 211 may deploy additional worker nodes to cluster in O-Cloud Site 2230 as new worker nodes 234. The cluster now includes worker nodes in Site 2.

[0075] At

[0005] , DMS 212 may redeploy NF deployments onto Cluster at O-Cloud Site 2 230 as an instruction to control plane node 2233.

[0076] At

[0006] , Control Plane Node 2 233 may redeploy NF deployments onto new worker nodes 234. Accordingly, the workload may be recovered.

[0077] FIG. 6 illustrates an example sequence diagram for cross-site high availability control and deployment planes. In this example use-case, both Site 1 and Site 2 have control planes and deployment planes, creating a high-availability (HA) cluster that actively runs workloadsacross both sites. If Site 1 fails, the cluster remains operational, and the only required action is to redeploy affected workloads on available deployment planes at Site 2. This solution follows the same recovery process as node failure.

[0078] SMO 200 may be provided, including FOCOM 201 and NFO 202. O-Cloud 210 may also be provided, including IMS 211, and a cluster having DMS 212, O-Cloud Site 1 220, and O-Cloud Site 2 230, wherein the O-Cloud Sites 1 220 and O-Cloud Site 2 230 are on the same cluster. O-Cloud Site 1 220 may implement Control Plane Node 1 223 and Worker Nodes 222, and O-Cloud Site 2230 may implement Control Plane Node 2233 and New Worker Nodes 234. As a precondition, cluster may be running across Site 1 and Site 2, NF deployment(s) are created and running on the cluster, and Site 2 has available capacity of additional nodes.

[0079] At

[0001] , an alarm may be configured by FOCOM 201 with IMS 211.

[0080] At

[0002] , IMS 211 may detect that site 1 fails. At this point, the cluster may be running across both sites.

[0081] At

[0003] , the alarm configured at IMS 211 is triggered and detected by FOCOM 201.

[0082] At

[0004] , DMS 212 may redeploy failed workloads onto Cluster at O-Cloud Site 2 230 as an instruction to control plane node 2233.

[0083] At

[0005] , Control Plane Node 2 233 may redeploy failed workloads onto new worker nodes 234. Accordingly, the workload may be recovered. It should be appreciated that compared to FIG. 5, this case does not need to redeploy an NF deployment, and can simply redeploy the failed workload since the backup nodes are already deployed.

[0084] FIG. 7 illustrates a block diagram of an example method for redeploying a failed workload by a network function orchestrator.

[0085] At operation S701, the NFO may detect a failure of the NF. According to example embodiments, detecting the failure of the NF may comprise triggering an alarm configured by Infrastructure Management Service (IMS).

[0086] At operation S702, based on detecting the failure in operation S701, the NFO may send an instruction to a deployment management service (DMS) to recreate the first NF.

[0087] According to one example use-case, the NF may be deployed, for example, on a first cluster of a first O-Cloud Site. The IMS may be configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the second cluster.

[0088] In another example use-case, the IMS may be configured to send an inventory change notice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.

[0089] Accordingly to another example use-case, the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additional worker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises redeploying the NF by a control-plane node of the second O-Cloud Site.

[0090] According to an example use-case, the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in both the first O-Cloud site and second O-Cloud Site, wherein the instruction to the DMS to recreate the first NF comprises redeploying failed workloads a control -plane node of the second O-Cloud Site.

[0091] Based on the above example embodiments, an automated recovery process by instructing DMS to recreate the NF deployment may be achieved, enabling efficient and automated recovery, thereby minimizing service disruption without manual intervention.

[0092] FIG. 8 illustrates a block diagram of an example device 800 for implementing one or more example embodiments. As shown in FIG. 8, the device 800 includes processor 810, a memory 820, a storage component 830, an input component 840, an output component 850, a communication interface 860, and a bus 870.

[0093] The processor 810, as used herein, means any type of computational circuit that may comprise hardware elements and software elements. The processor 810 may be embodied as a multi-core processor, a single core processor, or a combination of one or more multi-core processors and / or one or more single core processors, a distributed processing system, or the like. The processor 810 may be a Central Processing Unit (CPU), a graphics processing unit (GPU), an accelerated processing unit (APU), an application-specific integrated circuit (ASIC), or another type of processing component.

[0094] Memory 820 includes a non-transitory computer readable medium. Memory 820 includes a random-access memory (RAM), a read only memory (ROM), and / or another type of dynamic or static storage device (e.g., a flash memory, a magnetic memory, and / or an optical memory) that stores information and / or instructions for use by processor 810. The memory 820 comprises machine-readable instructions which are executable by the processor 810. These machine-readable instructions when executed by the processor 810 cause the processor 810 to perform one or more method steps of an embodiment described above.

[0095] Storage component 830 stores information and / or software related to the operation and use of the device 800. For example, storage component 830 may include a hard disk (e.g., amagnetic disk, an optical disk, a magneto-optic disk, and / or a solid-state disk), a compact disc (CD), a digital versatile disc (DVD), a floppy disk, a cartridge, a magnetic tape, and / or another type of non-transitory computer-readable medium, along with a corresponding drive.

[0096] Input component 840 is configured to receive information, such as user input. For example, the input component 840 may include, but not be limited to, a touch screen display, a keyboard, a keypad, a mouse, a button, a switch, and / or a microphone. Additionally, or alternatively, the input component 840 may include a sensor for sensing information (e.g., a global positioning system (GPS), an accelerometer, a gyroscope, and / or an actuator).

[0097] Output component 850 is configured to provide output information from the device 800. For example, the output component 850 may be, but not limited to, a display, a speaker, an instruction device to an external device, and / or one or more light-emitting diodes (LEDs).

[0098] Communication interface 860 is an interface that provides a communication connection to other devices, such as external devices and internal devices. The connection by the communication interface 860 can be a wired connection, a wireless connection, or a combination of wired and wireless connections, and can be a direct connection or an indirect connection via a communication network that exists between the device 800 and other devices. In other words, the standard of the communication interface 860 is not limited.

[0099] The bus 870 acts as an interconnect between the processor 810, the memory 820, the storage component 830, the input component 840, the output component 850, and the communication interface 860 of the device 800. The bus 870 may include a wired interconnection or a wireless interconnection.

[0100] The number and arrangement of components shown in FIG. 8 are provided as an example. In practice, device 800 may include additional components, fewer components, differentcomponents, or differently arranged components than those shown in FIG. 8. Additionally, or alternatively, a set of components (e.g., one or more components) of device 800 may perform one or more functions described as being performed by another set of components of device 800. Further, one or more method steps described in any of the embodiments may be performed utilizing a plurality of devices 800 in communication with one another.

[0101] Example embodiments of the present disclosure may be implemented in any suitable type of environment. In the following, an example environment (in which the example embodiments may be implemented) is described.

[0102] FIG. 9 illustrates a block diagram of an example environment 900 for implementing in which systems and / or method, described herein, may be implemented. The implementation environment 900 includes a UE (User equipment) 910, a service environment 920, and a network 930. The service environment 920 include one or more sub-environments 921. To illustrate this, FIG. 9 shows, for convenience, examples of a 1st sub-environment 921-1, a 2nd sub-environment 921-2, and an N-th sub-environment 921-N (where N is any natural number).

[0103] The UE 910 is connected to the network 930, and the network 930 is connected to the service environment 920. The connections may be wired, wireless, or a combination of both wired and wireless. The UE 910 and the service environment 920 are connected via the network 930.

[0104] The UE 910 is a device that communicates with the service environment 920. The UE 910 receives information from the service environment 920 and / or sends information to the service environment 920. Also, the UE 910 may generate and / or store information to be transmitted, as necessary. Also, the UE 910 may store and / or process information that is received, as necessary.

[0105] The example figure 9 refers to the “UE”. However, it should be understood by those skilled in the art that general terms such as “user device,” “terminal,” “terminal device,” “communication device,” and “communication terminal” can be used interchangeably with the term “UE.”

[0106] For example, the UE 910 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 smart phone, a radiotelephone, etc.), a wearable device (e.g., a pair of smart glasses or a smart watch), or a similar device.

[0107] The service environment 920 is an environment that communicates with the UE 910 to provide one or more services. The service environment 920 receives information from the UE 910 and / or sends information to the UE 910. Also, the service environment 920 may generate and / or store information to be transmitted, as necessary. Also, the service environment 920 may store and / or process information that is received, as necessary. For example, the service environment 920 may provide computing resources as one of the services. It should be noted that the service is not limited to being provided to the UE; it may also be provided to devices other than the UE. For example, based on communication from the UE, the service may perform processes such as anomaly detection or traffic analysis and notify the results to a predetermined destination.

[0108] The example figure 9 refers to the “service environment”. The term "service environment" is used to refer to the broader context within which services operate. For example, cloud environments, platforms, computing systems, network systems, and cloud systems generally represent the environments in which services are conducted, and these are included within the "service environment." However, the "service environment" is not limited to these examples.Additionally, the specific types of environments within the "service environment" are not restricted. For instance, cloud environments and cloud systems can be categorized as private cloud, public cloud, hybrid cloud, or multi-cloud, all of which are included within the "service environment."

[0109] The one or more services provided by the service environment 920 is not specifically limited and can be adjusted according to the embodiments. For example, the services may include a service that provides information to the UE 910, a service that stores information from the UE 910, or a service that performs processing based on information from the UE 910 and returns the results of the processing.

[0110] In an embodiment, the Service Environments 920 may also provide computing resources as the service. The computing resources can be hardware resources and / or software resources. For example, applications, processors, memory, and storage can be included in the provided computing resources. Each computing resource can communicate with other computing resources via wired connections, wireless connections, or a combination of wired and wireless connections.[OHl] The provided computing resources can be actual resources (also referred to as physical resources) and / or virtual resources. Furthermore, means of virtualization for virtual resources can be selected as appropriate. That is, in this disclosure, the use of adjectives such as "Virtual" or "Virtualized" to describe names does not imply that they are virtualized by a specific means of virtualization. For example, “virtual machine” refers to software that operates like an actual computer, realized through means of virtualization, and it is not intended to exclude those realized by specific means of virtualization such as Hypervisors or Containers. Conversely, when means of virtualization such as Hypervisors or containers are mentioned in this disclosure, it is merely cited as a general method of implementation. It should also be interpreted that embodimentsimplemented with other virtualization means are also disclosed. Also, the services may also be provided using resources virtualized by different means.

[0112] The service environment 920 includes one or more devices, such as servers and network devices, which provide services or perform processes. The placement of these devices within the service environment 920 can be determined as appropriate. Additionally, if the service environment 920 includes one or more sub-environments 921, the placement of devices can be determined based on predetermined policies for each sub-environment 921. For example, devices related to the first service may be placed in the 1st sub-environment 921-1, and devices related to the second service may be placed in the 2nd sub -environment 921-2. In another example, devices expected to have a higher load than a predetermined threshold may be placed in the 1st subenvironment 921-1, while devices expected to have a lower load than the predetermined threshold may be placed in the 2nd sub-environment 921-2. In this way, specific devices can be placed in specific sub -environments 921. Conversely, each sub-environment 921 can be specialized for a particular purpose.

[0113] In an embodiment, all processes executed in a single service may run within a single service environment, or in multiple service environments. Multiple processes executed in a single service could be provided by different service environments.

[0114] The network 930 is a network that exchanges information between the UE 910 and the service environment 920. The network 930 includes one or more wired and / or wireless networks.

[0115] For example, the network 930 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), alocal area network (LAN), a wide area network (WAN), a metropolitan area network (MAN), a telephone network (e.g., the Public Switched Telephone Network (PSTN)), a private network, an ad hoc network, an intranet, the Internet, a fiber optic-based network, or the like, a non-terrestrial network (NTN), and / or a combination of these or other types of networks.

[0116] The network 930 can be a part of a network. For example, in a 5G network that includes a RAN, a transport network, and a core network, the network 930 can be at least one of the RAN, the transport network, or the core network. For example, the service environment 920 could be in the core network, in which case the network 930 could correspond to a network that is a combination of a RAN and a transport network and is part of the 5G network.

[0117] The number and arrangement of devices and networks shown in FIG. 9 are provided as an example. It should be understood that any changes that may be implemented by those skilled in the art, such as the addition or rearrangement of well-known devices or networks at the time of implementation, are included in this disclosure.Various Aspects of Embodiments

[0118] It is contemplated that the example embodiments described hereinabove with reference to FIG. 2 to FIG. 9 are merely examples of possible embodiments of the present disclosure, and are not intended to limit or restrict the scope of the present disclosure.

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

[0120] Some embodiments may relate to a device (e.g., node, etc.), a system, a method, and / or a computer-readable medium at any possible technical detail level of integration. Further,one or more of the above components described above may be implemented as instructions stored on a computer-readable medium and executable by at least one processor (and / or may include at least one processor). The computer-readable medium may include a computer-readable non-transitory storage medium (or media) having computer-readable program instructions thereon for causing a processor to carry out operations.

[0121] The computer-readable storage medium can be a tangible device that can retain and store instructions for use by an instruction execution device. The computer-readable storage medium may be, for example, but is not limited to, an electronic storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. A non-exhaustive list of more specific examples of the computer-readable storage medium includes the following: a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), electrically erasable programmable read-only memory (EEPROM), a static random access memory (SRAM), a portable compact disc read-only memory (CD-ROM), a digital versatile disk (DVD), a memory stick, a floppy disk, a mechanically encoded device such as punch-cards or raised structures in a groove having instructions recorded thereon, and any suitable combination of the foregoing. A computer-readable storage medium, as used herein, is not to be construed as being transitory signals per se, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through a waveguide or other transmission media (e.g., light pulses passing through a fiber-optic cable), or electrical signals transmitted through a wire.

[0122] Computer-readable program instructions described herein can be downloaded to respective computing / processing devices from a computer-readable storage medium or to anexternal computer or external storage device via a network, for example, the Internet, a local area network, a wide area network and / or a wireless network. The network may comprise copper transmission cables, optical transmission fibers, wireless transmission, routers, firewalls, switches, gateway computers, and / or edge servers. A network adapter card or network interface in each computing / processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for storage in a computer-readable storage medium within the respective computing / processing device.

[0123] Computer-readable program code / instructions for carrying out operations may be assembler instructions, instruction-set-architecture (ISA) instructions, machine instructions, machine-dependent instructions, microcode, firmware instructions, state-setting data, configuration data for integrated circuitry, or either source code or object code written in any combination of one or more programming languages, including an object-oriented programming language such as Smalltalk, C++, or the like, and procedural programming languages, such as the "C" programming language or similar programming languages.

[0124] The computer-readable program instructions may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user's computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user's computer through any type of network, including a local area network (LAN) or a wide area network (WAN), or the connection may be made to an external computer (for example, through the Internet using an Internet Service Provider). In some embodiments, electronic circuitry including, for example, programmable logic circuitry, field-programmable gate arrays (FPGA), or programmable logic arrays (PLA) may execute the computer-readable program instructions by utilizing state information of the computer-readable program instructions to personalize the electronic circuitry, in order to perform aspects or operations.

[0125] These computer-readable program instructions may be provided to a processor of a general -purpose computer, special-purpose computer, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions / acts specified in the flowchart and / or block diagram block or blocks. These computer-readable program instructions may also be stored in a computer-readable storage medium that can direct a computer, a programmable data processing apparatus, and / or other devices to function in a particular manner, such that the computer-readable storage medium having instructions stored therein comprises an article of manufacture including instructions which implement aspects of the function / act specified in the flowchart and / or block diagram block or blocks.

[0126] The computer-readable program instructions may also be loaded onto a computer, other programmable data processing apparatus, or other devices to cause a series of operational steps to be performed on the computer, other programmable apparatus or other devices to produce a computer-implemented process, such that the instructions which execute on the computer, other programmable apparatus, or other device implement the functions / acts specified in the flowchart and / or block diagram block or blocks.

[0127] The flowchart 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 flowchart or block diagrams may represent a module, segment, or portion of instructions, which comprises one or more executable instructions for implementing the specified logical function(s). The method,computer system, and computer-readable medium may include additional blocks, fewer blocks, different blocks, or differently arranged blocks than those depicted in the Figures. 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, in fact, be executed concurrently or substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and / or flowchart illustration, and combinations of blocks in the block diagrams and / or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts or carry out combinations of special purpose hardware and computer instructions.

[0128] It will be apparent that systems and / or methods, described herein, may be implemented in different forms of hardware, firmware, or a combination of hardware and software. The actual specialized control hardware or software code used to implement these systems and / or methods is not limited to the implementations. Thus, the operation and behavior of the systems and / or methods were described herein without reference to specific software code — it is understood that software and hardware may be designed to implement the systems and / or methods based on the description herein.

[0129] In view of the above, various further respective aspects and features of embodiments of the present disclosure may be defined by the following items:Item [1]: A method including: detecting, by a Network Function Orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O- RAN), a failure of a Network Function (NF) hosted in an 0-RAN Cloud (O-Cloud) of the 0-RAN;and based on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.Item [2]: The method according to Item [1]: wherein detecting the failure of the NF includes triggering an alarm configured by an Infrastructure Management Service (IMS).Item [3]: The method according to any one of Items [l]-[2]: wherein the NF is deployed on a first cluster of a first O-Cloud Site.Item [4]: The method according to Item [3]: wherein an Infrastructure Management Service (IMS) is configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF includes recreating NF deployments on worker nodes of the second cluster.Item [5] : The method according to Item [3] : wherein an Infrastructure Management Service (IMS) is configured to send an inventory change notice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF includes recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.Item [6]: The method according to any one of Items [l]-[2], wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additionalworker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF includes redeploying the NF by a control-plane node of the second O-Cloud Site.Item [7]: The method according to any one of Items [l]-[2], wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in both the first O-Cloud site and second O-Cloud Site, wherein the instruction to the DMS to recreate the first NF includes redeploying failed workloads a control-plane node of the second O-Cloud Site.Item [8]: A network function orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O-RAN), the NFO configured to: detect a failure of a Network Function (NF) hosted in an O-RAN Cloud (O-Cloud) of the O-RAN; and based on detecting the failure, send an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.Item [9]: The NFO according to Item [8]: wherein detecting the failure of the NF includes triggering an alarm configured by an Infrastructure Management Service (IMS).Item

[0010] : The NFO according to any one of Items [8]-[9] : wherein the NF is deployed on a first cluster of a first O-Cloud Site.Item

[0011] : The NFO according to Item

[0010] : wherein an Infrastructure Management Service (IMS) is configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF includes recreating NF deployments on worker nodes of the second cluster.Item

[0012] : The NFO according to Item

[0010] : wherein an Infrastructure Management Service (IMS) is configured to send an inventory change notice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF includes recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.Item

[0013] : The NFO according to any one of Items [8]-[9], wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additional worker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF includes redeploying the NF by a control-plane node of the second O-Cloud Site.Item

[0014] : The NFO according to any one of Items [8]-[9], wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in both the first O-Cloud site and second O-Cloud Site, wherein the instruction to the DMS to recreate the first NF includes redeploying failed workloads a control-plane node of the second O-Cloud Site.Item

[0015] : A non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method including: detecting, by a Network Function Orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O-RAN), a failure of a Network Function (NF) hosted in an 0-RAN Cloud (O-Cloud) of the 0-RAN; and based on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.Item

[0016] : The non-transitory computer-readable recording medium according to Item

[0015] , wherein detecting the failure of the NF comprises triggering an alarm configured by an Infrastructure Management Service (IMS).Item

[0017] : The non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0016] , wherein the NF is deployed on a first cluster of a first O-Cloud Site.Item

[0018] : The non-transitory computer-readable recording medium according to Item

[0017] , wherein an Infrastructure Management Service (IMS) is configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the second cluster.Item

[0019] : The non-transitory computer-readable recording medium according to Item

[0017] , wherein an Infrastructure Management Service (IMS) is configured to send an inventory changenotice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.Item

[0020] : The non-transitory computer-readable recording medium according to any one of Items

[0015] -

[0016] , wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additional worker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises redeploying the NF by a control-plane node of the second O-Cloud Site.It will be apparent that within the scope of the appended clauses, the present disclosures may be practiced otherwise than as specifically described herein.

Claims

What is claimed is:

1. A method comprising:detecting, by a Network Function Orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O-RAN), a failure of a Network Function (NF) hosted in an O-RAN Cloud (O-Cloud) of the O-RAN; andbased on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.

2. The method as claimed in claim 1, wherein detecting the failure of the NF comprises triggering an alarm configured by an Infrastructure Management Service (IMS).

3. The method as claimed in claim 1, wherein the NF is deployed on a first cluster of a first O-Cloud Site.

4. The method as claimed in claim 3, wherein an Infrastructure Management Service (IMS) is configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the second cluster.

5. The method as claimed in claim 3, wherein an Infrastructure Management Service (IMS) is configured to send an inventory change notice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS torecreate the first NF comprises recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.

6. The method as claimed in claim 1, wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additional worker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises redeploying the NF by a control-plane node of the second O-Cloud Site.

7. The method as claimed in claim 1, wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in both the first O-Cloud site and second O-Cloud Site, wherein the instruction to the DMS to recreate the first NF comprises redeploying failed workloads a control-plane node of the second O-Cloud Site.

8. A network function orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O-RAN), the NFO configured to:detect a failure of a Network Function (NF) hosted in an O-RAN Cloud (O-Cloud) of the O-RAN; andbased on detecting the failure, send an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.

9. The NFO as claimed in claim 8, wherein detecting the failure of the NF comprises triggering an alarm configured by an Infrastructure Management Service (IMS).

10. The NFO as claimed in claim 8, wherein the NF is deployed on a first cluster of a first O-Cloud Site.

11. The NFO as claimed in claim 10, wherein an Infrastructure Management Service (IMS) is configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the second cluster.

12. The NFO as claimed in claim 10, wherein an Infrastructure Management Service (IMS) is configured to send an inventory change notice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.

13. The NFO as claimed in claim 8, wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additional worker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises redeploying the NF by a control-plane node of the second O-Cloud Site.

14. The NFO as claimed in claim 8, wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in both the firstO-Cloud site and second O-Cloud Site, wherein the instruction to the DMS to recreate the first NF comprises redeploying failed workloads a control-plane node of the second O-Cloud Site.

15. A non-transitory computer-readable recording medium having recorded thereon instructions executable to perform a method comprising:detecting, by a Network Function Orchestrator (NFO) of a Service Management and Orchestration framework (SMO) of an Open Radio Access Network (O-RAN), a failure of a Network Function (NF) hosted in an O-RAN Cloud (O-Cloud) of the O-RAN; andbased on detecting the failure, sending, by the NFO, an instruction to a Deployment Management Service (DMS) of the O-Cloud to recreate the first NF.

16. The non-transitory computer-readable recording medium as claimed in claim 15, wherein detecting the failure of the NF comprises triggering an alarm configured by an Infrastructure Management Service (IMS).

17. The non-transitory computer-readable recording medium as claimed in claim 15, wherein the NF is deployed on a first cluster of a first O-Cloud Site.

18. The non-transitory computer-readable recording medium as claimed in claim 17, wherein an Infrastructure Management Service (IMS) is configured to create a second cluster at a second O-Cloud Site and provision worker nodes at the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the second cluster.

19. The non-transitory computer-readable recording medium as claimed in claim 17, wherein an Infrastructure Management Service (IMS) is configured to send an inventory change notice to a Federated O-Cloud Orchestration and Management (FOCOM) upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises recreating NF deployments on worker nodes of the first cluster of a second O-Cloud Site.

20. The non-transitory computer-readable recording medium as claimed in claim 15, wherein the NF is initially deployed on a cluster running across a first O-Cloud Site and a second O-Cloud Site with worker nodes active in the first O-Cloud site only, wherein the IMS is configured to deploy additional worker nodes to the second O-Cloud Site upon detecting the failure, and wherein the instruction to the DMS to recreate the first NF comprises redeploying the NF by a controlplane node of the second O-Cloud Site.

Images