Dynamic internal service/function discovery in telecom cloud architecture

1 . A method of internal discovery in a telecommunications core network, the method comprising:

at a telecommunications core network machine having a microservices architecture, registering a credential for a container and task in a database as a microservice pod comes up;

retrieving container information updated in the database once information for the microservice pod is updated;

sending a message, by at least one of a task, container, or pod for the microservice, to a controller to register the microservice; and

handling multiple externally-facing interfaces, each managed by a specific microservice, allowing for flexible reactions to demands;

wherein microservices tracked by the database are within a centralized unit control plane (CU-CP) logical boundary of a telecommunications network.

2 . The method of claim 1 , wherein the machine is a virtual machine.

3 . The method of claim 1 , wherein the telecommunications core network uses one of Kubernetes or Docker Swarm for at least two of provisioning, deployment, scaling, networking, and load balancing.

4 . The method of claim 1 , wherein the at least one of a task, container, or pod starts periodic heartbeat messaging with the controller to maintain synchronization and detect failures.

5 . The method of claim 1 , further comprising periodically updating container information throughout collocated containers, ensuring that collocated pods are aware of a current network state.

6 . The method of claim 1 , further comprising sending a message, by the at least one of a task, container or pod, to at least one of another task, another container, or another pod to register the microservice.

7 . The method of claim 6 , further comprising sending periodic heartbeat messages, by the at least one of a task, container or pod, to the controller to maintain synchronization and detect failures.

8 . The method of claim 7 , further comprising determining, by the controller, that at least one of the periodic heartbeat messages is not received from the at least one of a task, container or pod.

9 . The method of claim 8 , further comprising:

advertising, by the controller, that the at least one of a task, container or pod is dead to at least one of another task, another container, or another pod; and

updating the database, by the controller, that the at least one of a task, container or pod is dead.

10 . A method of internal discovery in a telecommunications core network, the method comprising:

resolving, at a telecommunications core network machine, a microservice using a fully qualified domain name (FQDN);

updating a state of a first pod for the microservice and information of the first pod in a database;

retrieving the information of the first pod and services of the first pod from the database by a newly arrived pod;

sending a message, by the newly arrived pod, to at least one of a task, container, or another pod to register the newly arrived pod; and

handling multiple externally-facing interfaces, each managed by a specific microservice, allowing for flexible reactions to demands;

wherein microservices tracked by the database are within a centralized unit control plane (CU-CP) logical boundary of a telecommunications network.

11 . The method of claim 10 , further comprising periodically updating container information throughout collocated containers, ensuring that collocated pods are aware of a current network state.

12 . The method of claim 10 , further comprising, within a single microservice, hosting a database service registry and a service distribution controller.

13 . The method of claim 10 , wherein newly created containers or pods start periodic heartbeat messaging with a controller of the telecommunications core network to maintain synchronization and detect failures.

14 . The method of claim 10 , wherein the telecommunications core network uses one of Kubernetes or Docker Swarm for at least two of provisioning, deployment, scaling, networking, and load balancing.

15 . The method of claim 10 , further comprising starting periodic heartbeat messaging with a controller of the telecommunications core network by the newly arrived pod.

16 . A non-transitory computer-readable medium comprising instructions for internal discovery in a telecommunications core network which, when executed, cause a system to perform steps comprising:

at a telecommunications core network machine having a microservices architecture, registering a credential for a container and task in a database as a microservice pod comes up;

retrieving container information updated in the database once information for the microservice pod is updated; and

sending a message, by at least one of a task, container, or pod for the microservice, to a controller to register the microservice; and

handling multiple externally-facing interfaces, each managed by a specific microservice, allowing for flexible reactions to demands;

wherein microservices tracked by the database are within a centralized unit control plane (CU-CP) logical boundary of a telecommunications network.