Data IO and service on different pods of a RIC
To provide a low latency near RT RIC, some embodiments separate the RIC's functions into several different components that operate on different machines (e.g., execute on VMs or Pods) operating on the same host computer or different host computers. Some embodiments also provide high speed interfaces between these machines. Some or all of these interfaces operate in non-blocking, lockless manner in order to ensure that critical near RT RIC operations (e.g., datapath processes) are not delayed due to multiple requests causing one or more components to stall. In addition, each of these RIC components also has an internal architecture that is designed to operate in a non-blocking manner so that no one process of a component can block the operation of another process of the component. All of these low latency features allow the near RT RIC to serve as a high speed IO between the E2 nodes and the xApps.
1. A method of implementing a RAN (Radio Access Network) Intelligent Controller (RIC), the method comprising in a cloud datacenter:
deploying a first set of one or more machines to forward data messages between a set of base station components and a set of applications that interact with the RIC; and
deploying a second set of one or more machines to provide a set of management services to the set of applications, the second set of machines serving as an interface between the set of applications and a third set of machines that implement Service Management and Orchestration (SMO) operations including Discovery, Configuration, Resource management, Life-cycle management, and Fault tolerance, wherein the first set of machines and the second set of machines are distinct sets.
2. The method of claim 1 , wherein:
deploying the first set of machines comprises deploying the first set of machines to execute a set of datapath processing nodes that allow data messages to be exchanged between the set of base station components and the set of applications;
deploying the second set of machines comprises deploying the second set of machines to execute a set of service nodes that provide the set of services to the applications.
3. The method of claim 1 , wherein separating the first and second sets of machines allows for separate lifecycle management of each set of machines, which allows each set of machines to be updated and scaled differently.
4. The method of claim 1 , wherein separating the first and second sets of machines allows for separate HA (high availability) management of each set of machines.
5. The method of claim 1 , wherein separating the first and second sets of machines allows for separate auto-scaling of each set of machines.
6. The method of claim 1 , wherein at least one machine in the first set and one machine in the second set execute on the same host computer.
7. The method of claim 1 , wherein the first and second sets of machines execute on a plurality of host computers, with at least one first-set machine and at least one second-set machine executing on each of at least two host computers.
8. The method of claim 1 , wherein the second set machines execute on different set of host computers than the first set machines.
9. The method of claim 1 , wherein the first and second set of machines comprise first and second sets of Pods with no first-set machine executing on a host computer with a second-set machine.
10. The method of claim 1 , wherein the first and second set of machines comprise first and second sets of VMs.
11. The method of claim 1 , wherein the set of applications include a set of control plane applications or a set of RAN edge applications.
12. A RAN (Radio Access Network) Intelligent Controller (RIC), the RIC comprising: in a cloud datacenter:
a first set of one or more machines configured to forward data messages between a set of base station components and a set of applications that interact with the RIC; and
a second set of one or more machines configured to provide a set of management services to the set of applications, the second set of machines serving as an interface between the set of applications and a third set of machines that implement Service Management and Orchestration (SMO) operations including Discovery, Configuration, Resource management, Life-cycle management, and Fault tolerance, wherein the first set of machines and the second set of machines are distinct sets.
13. The RIC of claim 12 , wherein:
the first set of machines execute a set of datapath processing nodes that allow data messages to be exchanged between the set of base station components and the set of applications; and
the second set of machines execute a set of service nodes that provide the set of services to the set of applications.
14. The RIC of claim 12 , wherein separation of the first and second sets of machines allows for separate lifecycle management of each set of machines, which allows each set of machines to be updated and scaled differently.
15. The RIC of claim 12 , wherein separation of the first and second sets of machines allows for separate HA (high availability) management of each set of machines.
16. The RIC of claim 12 , wherein separation of the first and second sets of machines allows for separate auto-scaling of each set of machines.
17. The RIC of claim 12 further comprising at least one machine in the first set and one machine in the second set executing on the same host computer.
18. The RIC of claim 12 , wherein the first and second sets of machines execute on a plurality of host computers, with at least one first-set machine and at least one second-set machine executing on each of at least two host computers.
19. The RIC of claim 12 , wherein the second set machines execute on different set of host computers than the first set machines.
20. The RIC of claim 12 , wherein the first and second set of machines comprise first and second sets of Pods with no first-set machine executing on a host computer with a second-set machine.
21. The RIC of claim 12 , wherein the first and second set of machines comprise first and second sets of VMs.
22. The RIC of claim 12 , wherein the set of applications include a set of control plane applications or a set of RAN edge applications.