Technologies for transparent function as a service arbitration for edge systems

Abstract

Technologies for function as a service (FaaS) arbitration include an edge gateway, multiple endpoint devices, and multiple service providers. The edge gateway receives a registration request from a service provider that is indicative of an FaaS function identifier and a transform function. The edge gateway verifies an attestation received from the service provider and registers the service provider. The edge gateway receives a function execution request from an endpoint device that is indicative of the FaaS function identifier. The edge gateway selects the service provider based on the FaaS function identifier, programs an accelerator with the transform function, executes the transform function with the accelerator to transform the function execution request to a provider request, and submits the provider request to the service provider. The service provider may be selected based on an expected service level included in the function execution request. Other embodiments are described and claimed.

1 - 20 . (canceled) 
     
     
         21 . An apparatus comprising:
 memory; and   at least one processor to execute instructions to at least:
 access a registration request from a service provider; 
 register the service provider in association with at least one of a function identifier or a function type of a function provided by the service provider; 
 store a reputation score of the service provider in association with a registration of the service provider, the reputation score based on at least one of: (a) verification of an attestation from the service provider of a protection property, (b) reliability associated with the service provider, (c) availability associated with the service provider, or (d) a response time associated with the service provider; and 
 share the registration of the service provider with an edge node. 
   
     
     
         22 . The apparatus of  claim 21 , wherein the at least one processor is to register the service provider in response to the reputation score of the service provider satisfying an expected reputation score. 
     
     
         23 . The apparatus of  claim 21 , wherein the at least one processor is to register the service provider as providing the function as a function as a service (FaaS), the registration request including at least one of an identifier to identify the service provider or a FaaS type parameter to identify the function. 
     
     
         24 . The apparatus of  claim 21 , wherein the registration request is indicative of at least one of a cost or a service level agreement. 
     
     
         25 . The apparatus of  claim 21 , wherein the at least one processor is to select the service provider to execute the function for an endpoint device based on the reputation score of the service provider satisfying a requested reputation score in a function execution request from the endpoint device. 
     
     
         26 . The apparatus of  claim 21 , wherein the at least one processor is to select the service provider to execute the function for an endpoint device based on a service level agreement (SLA) accepted by the service provider satisfying an expected SLA in a function execution request from the endpoint device. 
     
     
         27 . The apparatus of  claim 21 , wherein the at least one processor is to update the reputation score based on at least one of: (a) an execution result of the function or (b) whether a service level agreement (SLA) accepted by the service provider satisfies an expected SLA requested by an endpoint device. 
     
     
         28 . The apparatus of  claim 21 , wherein the at least one processor is in a first edge gateway, and the edge node is in a second edge gateway. 
     
     
         29 . An apparatus comprising:
 a registration manager to:
 access a registration request from a service provider; and 
 register the service provider in association with at least one of a function identifier or a function type of a function provided by the service provider; and 
   a function execution manager to store a reputation score of the service provider in association with a registration of the service provider, the reputation score based on at least one of: (a) verification of an attestation from the service provider of a protection property, (b) reliability associated with the service provider, (c) availability associated with the service provider, or (d) a response time associated with the service provider.   
     
     
         30 . The apparatus of  claim 29 , wherein the registration manager is to share the registration of the service provider with an edge node. 
     
     
         31 . The apparatus of  claim 30 , wherein the registration manager is in a first edge gateway, and the edge node is in a second edge gateway. 
     
     
         32 . The apparatus of  claim 29 , wherein the registration manager is to register the service provider in response to the reputation score of the service provider satisfying an expected reputation score. 
     
     
         33 . The apparatus of  claim 29 , wherein the registration manager is to register the service provider as providing the function as a function as a service (FaaS), the registration request including at least one of an identifier to identify the service provider or a FaaS type parameter to identify the function. 
     
     
         34 . The apparatus of  claim 29 , wherein the registration request is indicative of at least one of a cost or a service level agreement. 
     
     
         35 . The apparatus of  claim 29 , further including a service provider manager to select the service provider to execute the function for an endpoint device based on the reputation score of the service provider satisfying a requested reputation score in a function execution request from the endpoint device. 
     
     
         36 . The apparatus of  claim 29 , further including a service provider manager to select the service provider to execute the function for an endpoint device based on a service level agreement (SLA) accepted by the service provider satisfying an expected SLA in a function execution request from the endpoint device. 
     
     
         37 . The apparatus of  claim 29 , wherein the function execution manager is to update the reputation score based on at least one of: (a) an execution result of the function or (b) whether a service level agreement (SLA) accepted by the service provider satisfies an expected SLA requested by an endpoint device. 
     
     
         38 . An apparatus comprising:
 means for registering, the registering means to:
 access a registration request from a service provider; and 
 register the service provider in association with at least one of a function identifier or a function type of a function provided by the service provider; and 
   means for managing function execution, the managing means to store a reputation score of the service provider in association with a registration of the service provider, the reputation score based on at least one of: (a) verification of an attestation from the service provider of a protection property, (b) reliability associated with the service provider, (c) availability associated with the service provider, or (d) a response time associated with the service provider.   
     
     
         39 . The apparatus of  claim 38 , wherein the registering means is to store the registration of the service provider with an edge node. 
     
     
         40 . The apparatus of  claim 39 , wherein the registering means is in an edge gateway separate from the edge node. 
     
     
         41 . The apparatus of  claim 38 , wherein the registering means is to register the service provider in response to the reputation score of the service provider satisfying an expected reputation score. 
     
     
         42 . The apparatus of  claim 38 , wherein the registering means is to register the service provider as providing the function as a function as a service (FaaS), the registration request including at least one of an identifier to identify the service provider or a FaaS type parameter to identify the function. 
     
     
         43 . The apparatus of  claim 38 , wherein the registration request is indicative of at least one of a cost or a service level agreement. 
     
     
         44 . The apparatus of  claim 38 , further including means for selecting the service provider to execute the function for an endpoint device based on the reputation score of the service provider satisfying a requested reputation score in a function execution request from the endpoint device. 
     
     
         45 . The apparatus of  claim 38 , further including means for selecting the service provider to execute the function for an endpoint device based on a service level agreement (SLA) accepted by the service provider satisfying an expected SLA in a function execution request from the endpoint device. 
     
     
         46 . The apparatus of  claim 38 , wherein the managing means is to update the reputation score based on at least one of: (a) an execution result of the function or (b) whether a service level agreement (SLA) accepted by the service provider satisfies an expected SLA requested by an endpoint device. 
     
     
         47 . At least one storage device comprising computer-readable instructions that, when executed, cause at least one processor in a first edge gateway to at least:
 access a registration request from a service provider;   register the service provider in association with at least one of a function identifier or a function type of a function provided by the service provider;   store a reputation score of the service provider in association with a registration of the service provider, the reputation score based on at least one of: (a) verification of an attestation from the service provider of a protection property, (b) reliability associated with the service provider, (c) availability associated with the service provider, or (d) a response time associated with the service provider; and   share the registration of the service provider with a second edge gateway.   
     
     
         48 . The at least one storage device of  claim 47 , wherein the instructions are to cause the at least one processor to register the service provider in response to the reputation score of the service provider satisfying an expected reputation score. 
     
     
         49 . The at least one storage device of  claim 47 , wherein the instructions are to cause the at least one processor to register the service provider as providing the function as a function as a service (FaaS), the registration request includes at least one of an identifier to identify the service provider or a FaaS type parameter to identify the function. 
     
     
         50 . The at least one storage device of  claim 47 , wherein the registration request is indicative of at least one of a cost or a service level agreement. 
     
     
         51 . The at least one storage device of  claim 47 , wherein the instructions are to cause the at least one processor to select the service provider to execute the function for an endpoint device based on the reputation score of the service provider satisfying a requested reputation score in a function execution request from the endpoint device. 
     
     
         52 . The at least one storage device of  claim 47 , wherein the instructions are to cause the at least one processor to select the service provider to execute the function for an endpoint device based on a service level agreement (SLA) accepted by the service provider satisfying an expected SLA in a function execution request from the endpoint device. 
     
     
         53 . The at least one storage device of  claim 47 , wherein the instructions are to cause the at least one processor to update the reputation score based on at least one of: (a) an execution result of the function or (b) whether a service level agreement (SLA) accepted by the service provider satisfies an expected SLA requested by an endpoint device.