System and method for low latency edge computing

Abstract

Aspects of the subject disclosure may include, for example, a method in which a processing system receives data at an edge node of a network that also includes regional nodes and central nodes. The processing system also determines a latency criterion associated with an application for processing the data; the application corresponds to an application programming interface. The method also includes processing the data in accordance with the application, monitoring a latency associated with the processing, and determining whether the latency meets the latency criterion. The processing system dynamically assigns data processing resources so that the latency meets the latency criterion; the resources include computation, network and storage resources of the edge node, a central node, and a regional node in communication with the edge node and the central node. Other embodiments are disclosed.

What is claimed is: 
     
         1 . A method comprising:
 monitoring, by a processing system including a processor, a latency associated with executing of an application by an end user device, the application being associated with a first microservice located at an edge node and a second microservice located at a non-edge node that is one of a regional node or a central node;   determining, by the processing system, whether a latency criterion is satisfied by comparing the latency to the latency criterion; and   responsive to the latency criterion not being satisfied, triggering, by the processing system, a procedure for reducing the latency comprising moving at least one of the first or second microservices to a different node.   
     
     
         2 . The method of  claim 1 , wherein the latency is end-to-end latency, and wherein the moving of the at least one of the first or second microservices to the different node comprises moving the second microservice to one of the edge node or a second edge node. 
     
     
         3 . The method of  claim 1 , wherein the moving of the at least one of the first or second microservices to the different node comprises moving the second microservice from the central node to the regional node. 
     
     
         4 . The method of  claim 1 , further comprising:
 retrieving, by the processing system, the latency criterion from an application programming interface (API) used by the application; and   retrieving, by the processing system, information regarding the API from a database accessible to the edge node, the regional node, and the central node, wherein the API comprises a plurality of base APIs, and wherein the database comprises a list of data objects to be accessed via the plurality of base APIs.   
     
     
         5 . The method of  claim 4 , further comprising triggering, by the processing system, responsive to the latency criterion not being satisfied, a second procedure for reducing the latency comprising placement of the base APIs at one or more of the edge node, the regional node, and the central node. 
     
     
         6 . The method of  claim 1 , further comprising retrieving, by the processing system, a plurality of key performance indicators (KPIs), and wherein the monitoring the latency comprises determining the latency from at least one of the plurality of KPIs. 
     
     
         7 . The method of  claim 1 , further comprising triggering, by the processing system, responsive to the latency criterion not being satisfied, a second procedure for reducing the latency comprising providing a mapping between processing sub-tasks and the edge node, the regional node, and the central node. 
     
     
         8 . A device comprising:
 a processing system including a processor; and   a memory that stores executable instructions that, when executed by the processing system, facilitate performance of operations comprising:   monitoring a latency associated with executing of an application by a communication device, the application being associated with a first microservice located at an edge node and a second microservice located at a non-edge node that is one of a regional node or a central node;   determining whether a latency criterion is satisfied by comparing the latency to the latency criterion; and   responsive to the latency criterion not being satisfied causing at least one of the first or second microservices to be moved to a different node.   
     
     
         9 . The device of  claim 8 , wherein the latency is end-to-end latency, and wherein the moving of the at least one of the first or second microservices to the different node comprises moving the second microservice to one of the edge node or a second edge node. 
     
     
         10 . The device of  claim 8 , wherein the moving of the at least one of the first or second microservices to the different node comprises moving the second microservice from the central node to the regional node. 
     
     
         11 . The device of  claim 8 , wherein the operations further comprise:
 retrieving the latency criterion from an application programming interface (API) used by the application; and   retrieving information regarding the API from a database accessible to the edge node, the regional node, and the central node, wherein the API comprises a plurality of base APIs, and wherein the database comprises a list of data objects to be accessed via the plurality of base APIs.   
     
     
         12 . The device of  claim 11 , wherein the operations further comprise triggering, responsive to the latency criterion not being satisfied, a procedure for reducing the latency comprising placement of the base APIs at one or more of the edge node, the regional node, and the central node. 
     
     
         13 . The device of  claim 8 , wherein the operations further comprise retrieving a plurality of key performance indicators (KPIs), and wherein the monitoring the latency comprises determining the latency from at least one of the plurality of KPIs. 
     
     
         14 . The device of  claim 8 , wherein the operations further comprise triggering, responsive to the latency criterion not being satisfied, a procedure for reducing the latency comprising providing a mapping between processing sub-tasks and the edge node, the regional node, and the central node. 
     
     
         15 . A non-transitory, machine-readable medium comprising executable instructions that, when executed by a processing system including a processor, facilitate performance of operations comprising:
 monitoring a latency associated with executing of an application by a communication device, the application being associated with a first microservice located at an edge node and a second microservice located at a non-edge node that is one of a regional node or a central node;   determining whether a latency criterion is satisfied by comparing the latency to the latency criterion; and   responsive to the latency criterion not being satisfied causing at least one of the first or second microservices to be moved to a different node.   
     
     
         16 . The non-transitory, machine-readable medium of  claim 15 , wherein the latency is end-to-end latency, and wherein the moving of the at least one of the first or second microservices to the different node comprises moving the second microservice to one of the edge node or a second edge node. 
     
     
         17 . The non-transitory, machine-readable medium of  claim 15 , wherein the moving of the at least one of the first or second microservices to the different node comprises moving the second microservice from the central node to the regional node. 
     
     
         18 . The non-transitory, machine-readable medium of  claim 15 , wherein the operations further comprise:
 retrieving the latency criterion from an application programming interface (API) used by the application; and   retrieving information regarding the API from a database accessible to the edge node, the regional node, and the central node, wherein the API comprises a plurality of base APIs, and wherein the database comprises a list of data objects to be accessed via the plurality of base APIs.   
     
     
         19 . The non-transitory, machine-readable medium of  claim 18 , wherein the operations further comprise triggering, responsive to the latency criterion not being satisfied, a procedure for reducing the latency comprising placement of the base APIs at one or more of the edge node, the regional node, and the central node. 
     
     
         20 . The non-transitory, machine-readable medium of  claim 15 , wherein the operations further comprise triggering, responsive to the latency criterion not being satisfied, a procedure for reducing the latency comprising providing a mapping between processing sub-tasks and the edge node, the regional node, and the central node.