O-CLOUD NODE UNCORDON

1 . A method, comprising:

receiving a request to change a deployable state of an open radio access network (O-RAN) cloud (O-Cloud) node;

changing the deployable state of the O-Cloud node in response to receiving the request; and

transmitting an indication that the deployable state of the O-Cloud node has been modified in response to changing the deployable state.

2 . The method of claim 1 , wherein changing the deployable state of the O-Cloud node comprises changing the deployable state from a cordoned state to an uncordoned state.

3 . The method of claim 2 , wherein:

the O-Cloud node is incapable of deploying at least one of an application, a workload, or a network function in the cordoned state, and

the O-Cloud node is capable of deploying at least one of the application, the workload, or the network function in the uncordoned state.

4 . The method of claim 1 , wherein changing the deployable state of the O-Cloud node comprises changing information related to a flag or marker that indicates the deployable state of the O-Cloud node.

5 . The method of claim 1 , wherein the receiving, the changing, and the transmitting are performed by infrastructure management services (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 receiving the request 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:

transmitting a request to change a 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 change from a cordoned state in which the O-Cloud node is incapable of deploying at least one of an application, a workload, or a network function to an uncordoned state in which the O-Cloud node is capable of deploying at least one of the application, the workload, or the network function.

9 . The method of claim 8 , further comprising receiving an indication that the deployable state changed to the uncordoned state.

10 . The method of claim 9 , wherein receiving the indication comprises receiving information related to an updated flag or marker that indicates the deployable state of the O-Cloud node is in the uncordoned state.

11 . The method of claim 9 , further comprising:

completing a subscription to receive deployable state change indications, and

receiving the indication that the deployable state changed to the uncordoned state based on completing the subscription to receive the deployable state change indications.

12 . The method of claim 8 , wherein the transmitting the request further comprises transmitting the request 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 transmitting the request 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 services (IMS) of an O-Cloud platform that performs the change from the cordoned state to the uncordoned state.

15 . An apparatus, comprising:

at least one memory configured to store computer program code; and

at least one processor configured to access said at least one memory and operate as instructed by said computer program code, said computer program code including:

receiving code configured to cause at least one of said 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 said 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 said 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 changing code is further configured to cause at least one of said at least one processor to change the deployable state from a cordoned state to an uncordoned state.

17 . The apparatus of claim 16 wherein:

the O-Cloud node is incapable of deploying at least one of an application, a workload, or a network function in the cordoned state, and

the O-Cloud node is capable of deploying at least one of the application, the

workload, or the network function in the uncordoned state.

18 . The apparatus of claim 15 , wherein:

the receiving code is further configured to cause at least one of said at least one processor to receive the request by an infrastructure management services (IMS) component of an O-Cloud platform,

the changing code is further configured to cause at least one of said 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 said at least one processor to transmit the indication from the IMS.

19 . The apparatus of claim 15 , wherein the changing code is further configured to cause at least one of said at least one processor to change information related to a flag or marker that indicates 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.