Systems and methods to determine mobile edge deployment of microservices

1. A method comprising:

determining, by a device, latency budgets for particular ones of a plurality of microservices for an application associated with a user equipment (UE) device, wherein the plurality of microservices are deployed in a cloud computing center;

determining, by the device, that a measured latency for a particular microservice, of the plurality of microservices, has exceeded a latency budget for the particular microservice by at least a latency budget threshold while the particular microservice is deployed in the cloud computing center, wherein the measured latency is based on a measured network latency for the particular microservice and a measured computation time for the particular microservice;

determining, by the device, that deploying the particular microservice on a Multi-Access Edge Computing (MEC) network associated with a base station servicing the UE device, reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice, wherein determining that deploying the particular microservice on the MEC network reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice includes:

determining a latency difference between a latency associated with the cloud computing center and a latency associated with the MEC network; and

determining that the latency difference is greater than an amount by which the latency budget for the particular microservice has been exceeded;

deploying, by the device, the particular microservice on the MEC network, based on determining that deploying the particular microservice on the MEC network reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice; and

sending, by the device, a recommendation to the UE device to use the particular microservice deployed at the MEC network.

2. The method of claim 1 , further comprising:

determining a computation requirement associated with the particular microservice; and

determining that the MEC network satisfies the computation requirement associated with the particular microservice before deploying the particular microservice in the MEC network.

3. The method of claim 1 , wherein determining that the measured latency for the particular microservice has exceeded the latency budget for the particular microservice by at least the latency budget threshold includes:

determining the measured latency for the particular microservice as a sum of the measured network latency for the particular microservice and the measured computation time for the particular microservice.

4. The method of claim 1 , further comprising:

determining a data workflow between particular ones of the plurality of microservices;

identifying one or more dependency microservices for the particular microservice, wherein the particular microservice depends on output from the one or more dependency microservices to perform a function; and

deploying the one or more dependency microservices in the MEC network, in response to identifying the one or more dependency microservices.

5. The method of claim 1 , further comprising:

determining that another microservice, of the plurality of microservices, is associated with a security requirement; and

deploying the other microservice in the MEC network, based on determining that the other microservice is associated with a security requirement.

6. The method of claim 1 , wherein the MEC network corresponds to a private MEC network.

7. The method of claim 1 , further comprising:

receiving an indication from the UE device to use the deployed particular microservice for the application in the MEC network; and

routing protocol data units (PDU) associated with the particular microservice for the application to the MEC network, in response to receiving the indication from the UE device to use the deployed particular microservice for the application in the MEC network.

8. The method of claim 7 , further comprising:

monitoring a latency associated with the deployed particular microservice in the MEC network; and

determining whether the monitored latency is lower than a latency associated with a deployment of the particular microservice in the cloud computing center.

9. The method of claim 1 , further comprising:

receiving a request from the UE device for a list of available microservices deployed in the MEC network; and

providing the requested list of available microservices deployed in the MEC network to the UE device.

10. The method of claim 1 , further comprising:

determining that an available processing or network capacity associated with the MEC network is less than an available capacity threshold; and

transferring the particular microservice to another MEC network, based on determining that the available processing or network capacity associated with the MEC network is less than the available capacity threshold.

11. The method of claim 1 , wherein the particular microservice is deployed in a container, and wherein the container is associated with another container that includes a function to collect metrics information associated with the particular microservice.

12. A device comprising:

a processor configured to execute instructions to:

determine latency budgets for particular ones of a plurality of microservices for an application associated with a user equipment (UE) device, wherein the plurality of microservices are deployed in a cloud computing center;

determine that a measured latency for a particular microservice, of the plurality of microservices, has exceeded a latency budget for the particular microservice by at least a latency budget threshold while the particular microservice is deployed in the cloud computing center, wherein the measured latency is based on a measured network latency for the particular microservice and a measured computation time for the particular microservice;

determine that deploying the particular microservice on a Multi-Access Edge Computing (MEC) network associated with a base station servicing the UE device, reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice, wherein, when determining that deploying the particular microservice on the MEC network reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice, the processor is further configured to:

determine a latency difference between a latency associated with the cloud computing center and a latency associated with the MEC network; and

determine that the latency difference is greater than an amount by which the latency budget for the particular microservice has been exceeded;

deploy the particular microservice on the MEC network, based on determining that deploying the particular microservice on the MEC network reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice; and

send a recommendation to the UE device to use the particular microservice deployed at the MEC network.

13. The device of claim 12 , wherein the processor is further configured to:

determine a computation requirement associated with the particular microservice; and

determine that the MEC network satisfies the computation requirement associated with the particular microservice before deploying the particular microservice in the MEC network.

14. The device of claim 12 , wherein, when determining that the measured latency for the particular microservice has exceeded a latency budget for the particular microservice by at least the latency budget threshold, the processor is further configured to:

determine the measured latency for the particular microservice as a sum of the measured network latency for the particular microservice and the measured computation time for the particular microservice.

15. The device of claim 12 , wherein the processor is further configured to:

determine a data workflow between particular ones of the plurality of microservices;

identify one or more dependency microservices for the particular microservice, wherein the particular microservice depends on output from the one or more dependency microservices to perform a function; and

deploy the one or more dependency microservices in the MEC network, in response to identifying the one or more dependency microservices.

16. The device of claim 12 , wherein the processor is further configured to:

determine that another microservice, of the plurality of microservices, is associated with a security requirement; and

deploy the other microservice in the MEC network, based on determining that the other microservice is associated with a security requirement.

17. The device of claim 12 , wherein the processor is further configured to:

receive an indication from the UE device to use the deployed particular microservice for the application in the MEC network; and

route protocol data units (PDU) associated with the particular microservice for the application to the MEC network, in response to receiving the indication from the UE device to use the deployed particular microservice for the application in the MEC network.

18. The device of claim 12 , wherein the processor is further configured to:

receive a request from the UE device for a list of available microservices deployed in the MEC network; and

provide the requested list of available microservices deployed in the MEC network to the UE device.

19. A non-transitory computer-readable memory device storing instructions executable by a processor, the non-transitory computer-readable memory device comprising:

one or more instructions to determine latency budgets for particular ones of a plurality of microservices for an application associated with a user equipment (UE) device, wherein the plurality of microservices are deployed in a cloud computing center;

one or more instructions to determine that a measured latency for a particular microservice, of the plurality of microservices, has exceeded a latency budget for the particular microservice by at least a latency budget threshold while the particular microservice is deployed in the cloud computing center, wherein the measured latency is based on a measured network latency for the particular microservice and a measured computation time for the particular microservice;

one or more instructions to determine that deploying the particular microservice on a Multi-Access Edge Computing (MEC) network associated with a base station servicing the UE device, reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice, wherein the one or more instructions to determine that deploying the particular microservice on the MEC network reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice includes:

one or more instructions to determine a latency difference between a latency associated with the cloud computing center and a latency associated with the MEC network; and

one or more instructions to determine that the latency difference is greater than an amount by which the latency budget for the particular microservice has been exceeded;

one or more instructions to deploy the particular microservice on the MEC network, based on determining that deploying the particular microservice on the MEC network reduces the measured latency for the particular microservice to be within the latency budget for the particular microservice; and

one or more instructions to send a recommendation to the UE device to use the particular microservice deployed at the MEC network.

20. The non-transitory computer-readable memory device of claim 19 , further comprising:

one or more instructions to determine a data workflow between particular ones of the plurality of microservices;

one or more instructions to identify one or more dependency microservices for the particular microservice, wherein the particular microservice depends on output from the one or more dependency microservices to perform a function; and

one or more instructions to deploy the one or more dependency microservices in the MEC network, in response to identifying the one or more dependency microservices.