Warnermedia Direct, LLC

Franklyn Hu

Erik Fortune

Hazel Diana Mary

Adam Gilman

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.

Client device configuration based on client context

The described technology is generally directed towards caching session state data on a client device, so that services called by the client device and other services can use the session state data without having to recollect such information from a server or servers that maintain the ground truth values for the session state data. The session state data can be divided into payload datasets based on domains or the like, so that only a relevant part of the session state data need be attached to a given communication, and/or updated when a session variable changes in some way. A payload dataset can be encoded or encrypted so that a service can verify the integrity of the payload dataset before using it, such as for service-to-service communication.

Growing community of inventors

Seattle, WA, United States of America

Franklyn Hu