System and method for draining of O-Cloud node
Provided are a method, system, and an Service Management and Orchestration Framework (SMO) and O-Cloud to drain one or more O-Cloud Nodes based on recommendations from an rApp or manually by an O-Cloud Maintainer via the SMO. In particular, the method may include: receiving, by a SMO function, a first request or recommendation to drain at least one O-Cloud Node, the first request or recommendation being received from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC) or from an O-Cloud Maintainer; transmitting, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to drain the at least one O-Cloud Node based on the received first request or recommendation; and receiving, from the IMS/DMS, a first notification as to whether the at least one O-Cloud Node has been drained.
1. A method for draining one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) Nodes, the method comprising:
receiving, by a Service Management and Orchestration Framework (SMO) function, a first request or recommendation to drain at least one O-Cloud Node, the first request or recommendation being received from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC) or from an O-Cloud Maintainer, wherein draining the at least one O-Cloud Node comprises at least one of: migrating network functions or components of the network functions to another O-Cloud Node, relocating the network functions or the components of the network functions to another O-Cloud Node, or terminating all the network functions or all the components of the network functions of the O-Cloud Node;
transmitting, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to drain the at least one O-Cloud Node based on the received first request or recommendation; and
receiving, from the IMS/DMS, a first notification as to whether the at least one O-Cloud Node has been drained,
wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).
2. The method as claimed in claim 1 , wherein the second request is an instruction to drain a first O-Cloud Node of the at least one O-Cloud Node, wherein the first notification indicates that the first O-Cloud Node has been drained, and wherein the method further comprises:
transmitting, by the SMO function to the IMS/DMS via the O2 interface, a third request to drain a second O-Cloud Node of the at least one O-Cloud Node based on the received first request or recommendation.
3. The method as claimed in claim 1 , wherein the first request or recommendation is based on metric and/or observability data received by the rApp or the O-Cloud Maintainer via O1- and/or O2-related services.
4. The method as claimed in claim 1 , wherein the second request is transmitted by the SMO function to the IMS/DMS based on determining, by the SMO function, to accept the first request or recommendation to drain the at least one O-Cloud Node.
5. The method as claimed in claim 1 , wherein the first notification indicates that the at least one O-Cloud Node was not drained or an exception occurred.
6. The method as claimed in claim 1 , wherein the first notification indicates that the at least one O-Cloud Node was drained, and wherein the receiving the first notification comprises:
receiving, from the IMS/DMS by the SMO function via the O2 interface, the first notification that the at least one O-Cloud Node has been drained.
7. The method as claimed in claim 6 , further comprising:
notifying, by the SMO function, the rApp of the Non-RT RIC or the O-Cloud Maintainer that the at least one O-Cloud Node has been drained.
8. The method as claimed in claim 1 , wherein the draining the at least one O-Cloud Node further comprises at least one of: marking the at least one O-Cloud Node as unschedulable and setting the at least one O-Cloud Node to a maintenance mode.
9. The method as claimed in claim 1 , wherein the first request or recommendation includes an identifier of the at least one O-Cloud Node to be drained.
10. An apparatus for draining one or more Open Radio Access Network (O-RAN) Cloud (O-Cloud) Nodes, the apparatus comprising:
at least one memory storing computer-executable instructions; and
at least one processor configured to execute the computer-executable instructions to:
receive, by a Service Management and Orchestration Framework (SMO) function, a first request or recommendation to drain at least one O-Cloud Node, the first request or recommendation being received from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC) or from an O-Cloud Maintainer, wherein draining the at least one O-Cloud Node comprises at least one of: migrating network functions or components of the network functions to another O-Cloud Node, relocating the network functions or the components of the network functions to another O-Cloud Node, or terminating all the network functions or all the components of the network functions of the O-Cloud Node;
transmit, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to drain the at least one O-Cloud Node based on the received first request or recommendation; and
receive, from the IMS/DMS, a first notification as to whether the at least one O-Cloud Node has been drained,
wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).
11. The apparatus as claimed in claim 10 , wherein the second request is an instruction to drain a first O-Cloud Node of the at least one O-Cloud Node, wherein the first notification indicates that the first O-Cloud Node has been drained, and wherein the at least one processor is further configured to execute the computer-executable instructions to:
transmit, by the SMO function to the IMS/DMS via the O2 interface, a third request to drain a second O-Cloud Node of the at least one O-Cloud Node based on the received first request or recommendation.
12. The apparatus as claimed in claim 10 , wherein the first request or recommendation is based on metric and/or observability data received by the rApp or the O-Cloud Maintainer via O1- and/or O2-related services.
13. The apparatus as claimed in claim 10 , wherein the second request is transmitted by the SMO function to the IMS/DMS based on determining, by the SMO function, to accept the first request or recommendation to drain the at least one O-Cloud Node.
14. The apparatus as claimed in claim 10 , wherein the first notification indicates that the at least one O-Cloud Node was not drained or an exception occurred.
15. The apparatus as claimed in claim 10 , wherein the first notification indicates that the at least one O-Cloud Node was drained, and wherein the at least one processor is further configured to execute the computer-executable instructions to receive the first notification by:
receiving, from the IMS/DMS by the SMO function via the O2 interface, the first notification that the at least one O-Cloud Node has been drained.
16. The apparatus as claimed in claim 15 , wherein the at least one processor is further configured to execute the computer-executable instructions to:
notifying, by the SMO function, the rApp of the Non-RT RIC or the O-Cloud Maintainer that the at least one O-Cloud Node has been drained.
17. A non-transitory computer-readable recording medium having recorded thereon instructions executable by at least one processor to cause the processor to perform a method comprising:
receiving, by a Service Management and Orchestration Framework (SMO) function, a first request or recommendation to drain at least one O-Cloud Node, the first request or recommendation being received from an rApp of a Non-Real-Time (Non-RT) RAN Intelligent Controller (RIC) or from an O-Cloud Maintainer, wherein draining the at least one O-Cloud Node comprises at least one of: migrating network functions or components of the network functions to another O-Cloud Node, relocating the network functions or the components of the network functions to another O-Cloud Node, or terminating all the network functions or all the components of the network functions of the O-Cloud Node;
transmitting, by the SMO function to an Infrastructure Management Services (IMS) and/or Deployment Management Services (DMS) via an O2 interface, a second request to drain the at least one O-Cloud Node based on the received first request or recommendation; and
receiving, from the IMS/DMS, a first notification as to whether the at least one O-Cloud Node has been drained,
wherein the SMO function is at least one of a Federated O-Cloud Orchestration and Management (FOCOM) and Network Function Orchestration (NFO).
18. The non-transitory computer-readable recording medium as claimed in claim 17 , wherein the second request is an instruction to drain a first O-Cloud Node of the at least one O-Cloud Node, wherein the first notification indicates that the first O-Cloud Node has been drained, and wherein the method further comprises:
transmitting, by the SMO function to the IMS/DMS via the O2 interface, a third request to drain a second O-Cloud Node of the at least one O-Cloud Node based on the received first request or recommendation.
19. The non-transitory computer-readable recording medium as claimed in claim 17 , wherein the first request or recommendation is based on metric and/or observability data received by the rApp or the O-Cloud Maintainer via O1- and/or O2-related services.
20. The non-transitory computer-readable recording medium as claimed in claim 17 , wherein the second request is transmitted by the SMO function to the IMS/DMS based on determining, by the SMO function, to accept the first request or recommendation to drain the at least one O-Cloud Node.