Client device configuration based on client context
The described technology is generally directed towards configuring a client device with client configuration data based on client context data. The configuration data can include endpoints of various services to which the client can connect that are appropriate for the client device based on the client context data, along with dimension information (route key values) for connecting to each such service. For example, a roaming client device can be given an endpoint and dimension information to connect to a content service in the roaming region, with a different endpoint and dimension information for communicating user information to a home region to which the user is affiliated. This facilitates single hop/reduced latency for content requests, and compliance with home regulations via a single hop to the home service.
1. A system, comprising:
a processor; and
a memory that stores executable instructions that, when executed by the processor of the system, facilitate performance of operations, the operations comprising:
receiving, from a client device, a client request for client configuration data, the client request associated with client context data,
in response to the request, determining, based on the client context data, a structured template, wherein the structured template is configured for use with the client device having a specified geographic origination location,
based on the client configuration data corresponding to the structured template, directing the sending of a request from the client device to an endpoint device, wherein an endpoint comprising the endpoint device is specified by the structured template as being within the specified geographic origination location.
2. The system of claim 1 , wherein a type of the request is one of a user data-related request or a content data-related request, and wherein the use of the endpoint is based on the type of the request.
3. The system of claim 2 , wherein the operations further comprise:
based on the client configuration data, sending a second request from the client device to a second endpoint, wherein the second endpoint is a geographically nearest endpoint to the client device, wherein a second type of the second request is the other one of a user data-related request or a content data-related request, and wherein the use of the second endpoint is based on the type of the second request.
4. The system of claim 1 , wherein the use of the specified geographic origination location complies with a data transfer compliance requirement associated with the client device or with the specified geographic origination location.
5. The system of claim 1 , wherein the use of the specified geographic origination location complies with a data transfer compliance requirement associated with an entity associated with the client device or with data being transferred in association with the request.
6. The system of claim 1 , further comprising:
template matching logic employed by the processor to determine the structured template from a set of available structured templates, including the structured template, based on the client context data.
7. The system of claim 1 , wherein the determining the structured template comprises locating the structured template at a cache at the client device.
8. The system of claim 1 , wherein the operations further comprise:
updating the structured template based on data received at the system specifying a compliance requirement related to data transfer.
9. The system of claim 1 , wherein the operations further comprise:
based on the client configuration data, sending, to the client device, notification of a software version update to a software employed at the client device.
10. A non-transitory machine-readable medium, comprising executable instructions that, when executed by a processor, facilitate performance of operations, the operations comprising:
sending, from a client device, a client request for client configuration data, the client request associated with client context data;
in response to the request, automatically receiving a structured template identifier defining a structured template cached at the client device, wherein the structured template is configured for use with the client device having a specified geographic location; and
based on the structured template, directing the sending of a request from the client device to an endpoint device, wherein an endpoint comprising the endpoint device is specified by the structured template as being within the specified geographic origination location.
11. The non-transitory machine-readable medium of claim 10 , wherein the structured template is configured for use with the client device based on at least one of: a request type of a user data-related request, a request type of a content data-related request, the specified geographic origination location of the client device, a current geographic location of the client device, a type of the client device, a software of the client device, or a requirement associated with an administrator of the client device.
12. The non-transitory machine-readable medium of claim 10 , wherein the operations further comprise:
receiving and implementing an update to the structured template based on the client context data sent from the client device.
13. The non-transitory machine-readable medium of claim 10 , wherein the operations further comprise:
receiving a command to delete a second structured template based on the client context data sent from the client device.
14. A method, comprising:
receiving, from a client device, a client request for receiving first data or sending second data;
based on the client request, and based on one or more parameters generated from client context data associated with the client request, identifying a structured template,
wherein the structured template is configured for use with at least one of the client request being a user data-related request type or the client request being a content data-related request type, and
wherein the structure template is configured for use with the client device having a specified geographic origination location; and
using the structured template to direct execution of the client request at the client device to an endpoint at the specified geographic location, wherein the endpoint is specified by the structured template as being within the specified geographic origination location.
15. The method of claim 14 , further comprising:
receiving, from the client device, the client context data; and
based on the client context data, generating the one or more parameters.
16. The method of claim 14 , further comprising:
based on the one or more parameters generated from the client context data, generating the structured template to be identified at the identifying; and
in response to the generating the structured template, and based on the one or more parameters generated from the client context data, assigning the structured template for use in instances of the user data-related request type or the content data-related request type.
17. The method of claim 16 , further comprising:
in response to the generating the structured template, caching the structured template at the client device.
18. The method of claim 14 , further comprising:
based on the one or more parameters generated from the client context data, updating a default structured template with the one or more configurations defining communication use by the client device, wherein the structured template identified is the updated default structured template.
19. The method of claim 14 , further comprising:
directing deletion of a structured template, other than the structured template, based on the client context data.
20. The method of claim 14 , further comprising:
using the structured template to direct execution of the client request at the client device to the endpoint further being associated with a request type of the client request being the user data-related request type or the content data-related request type.