Patent classifications
H04L67/5682
Data Sharing In Geographically Partitioned Networks
Techniques are disclosed for the sharing and transferring of user data in online network systems operating in multiple jurisdictions. The different jurisdictions may be, for example, different geo-partitions in an online network system. Various techniques are disclosed for providing cross-partition operational functionalities (e.g., cross-geo transactions) between geo-partitioned server systems through the sharing and transferring of data between the geo-partitions. The geo-partitions may have established permissions for data that can be shared between the geo-partitions. A server system in one geo-partition may generate an auxiliary account from a subset of data shared across the geo-partitions that complies with the data permissions. Complying with the established data permissions may inhibit overlapping between the different laws or regulations of the geo-partitions.
A SERVICE CACHING METHOD FOR A CROSS-BORDER SERVICE NETWORK
The present invention discloses a service caching method for a cross-border service network, wherein the method includes: a cache space of a service switch node is divided into a resident area, a change area, a pre-reclaimed area and a maintenance index area; among them, a cache hit frequency is: a resident area>a change area>a pre-reclaimed area, and the maintenance index area is used for separate storage services call path. when a service call is generated, a cache content in the cache space is replaced according to a cache value of a missed cache or a hit cache; a service router and service switch nodes in the corresponding area jointly form a hierarchical cache mode. When the cache space of any node in the service switch node is insufficient, the service switch nodes in the same area perform collaborative cache and store them in other cache space of the service switch node through indexing. The method provided by the present invention can improve the cache utilization efficiency in the cross-border service network, thereby accelerating service invocation.
A SERVICE CACHING METHOD FOR A CROSS-BORDER SERVICE NETWORK
The present invention discloses a service caching method for a cross-border service network, wherein the method includes: a cache space of a service switch node is divided into a resident area, a change area, a pre-reclaimed area and a maintenance index area; among them, a cache hit frequency is: a resident area>a change area>a pre-reclaimed area, and the maintenance index area is used for separate storage services call path. when a service call is generated, a cache content in the cache space is replaced according to a cache value of a missed cache or a hit cache; a service router and service switch nodes in the corresponding area jointly form a hierarchical cache mode. When the cache space of any node in the service switch node is insufficient, the service switch nodes in the same area perform collaborative cache and store them in other cache space of the service switch node through indexing. The method provided by the present invention can improve the cache utilization efficiency in the cross-border service network, thereby accelerating service invocation.
BATCH DELETION METHOD AND APPARATUS FOR CACHE CONTENTS, DEVICE AND READABLE STORAGE MEDIUM
A batch deletion method, apparatus, and device for cached content and a non-transitory computer-readable storage medium are disclosed. The method may include: adding keywords to content identifiers which correspond to cached resources (S101); saving the content identifiers separately (S102); finding, through a keyword-based query, content identifiers meeting at least one condition (S103); locating storage paths of cached resources by using the content identifiers meeting the at least one condition (S104); and deleting the located cached resources one by one (S105).
SYSTEM FOR TRIGGERING CROSS CHANNEL DATA CACHING ON NETWORK NODES
Embodiments of the present invention provide a system for triggering cross channel data caching on network nodes. Historical event data and live event data of a user may be monitored to determine an expected event that includes one or more expected channels. An expected period of time for the expected event may also be determined. Relevant user data may then be identified from one or more systems of record and cached or otherwise compressed. One or more nodes of a network associated with each of the one or more expected channels are then identified. The cached data is then transmitted to virtual data structures associated with each of the one or more nodes. The cached data is then generally maintained in these virtual data structures on the network for the expected period of time.
Templating data service responses
The described technology is directed towards locating and using a template for processing data item data from a general form into a client-specific form for returning in response to a client request. A client request includes a data item identifier and client-specific information. The data item's identifier is processed into a data type and/or identifier, e.g., a string. The client-specific information is used to determine a device class, device type and/or client platform software version. The template is found in a hierarchy of templates based upon the client-specific information and the data type or data ID string, e.g., the client-specific information may be used to determine a subset of template folders that is evaluated to find a file with a filename matching the string. The folders may be ordered from most-specific to least-specific, so as to locate the most specific template file that applies.
Templating data service responses
The described technology is directed towards locating and using a template for processing data item data from a general form into a client-specific form for returning in response to a client request. A client request includes a data item identifier and client-specific information. The data item's identifier is processed into a data type and/or identifier, e.g., a string. The client-specific information is used to determine a device class, device type and/or client platform software version. The template is found in a hierarchy of templates based upon the client-specific information and the data type or data ID string, e.g., the client-specific information may be used to determine a subset of template folders that is evaluated to find a file with a filename matching the string. The folders may be ordered from most-specific to least-specific, so as to locate the most specific template file that applies.
TECHNOLOGIES FOR CROSS-DEVICE SHARED WEB RESOURCE CACHE
Technologies for cross-device shared web resource caching include a client device and a shared cache device. The client device scans for a shared cache device in local proximity to the client device and, in response to the scan, registers with the shared cache device. After registering, the client device requests a cached web resource from the shared cache device. The shared cache device determines whether a cached web resource that matches the request is installed in a shared cache. The shared cache device may determine whether an origin of the request matches the mi gin of the cached web resource. If installed, the shared cache device sends a found response and the cached web resource to the client device. If not installed, the shared cache device sends a not-found response and the client device may request the web resource from a remote web server. Other embodiments are described and claimed.
MACHINE-DRIVEN CROWD-DISAMBIGUATION OF DATA RESOURCES
Embodiments seek to protect privacy of potentially sensitive client resources in web transactions using crowd-disambiguation. Crowd-disambiguation machines can aggregate information about resources from multiple clients as resource fingerprints, and can use the fingerprints to provide crowd-sourced services in a privacy-protected manner. For example, embodiments can communicate a resource fingerprint as a fully ambiguated resource instance (FARI) and a partially disambiguated resource instance (PDRI). When one (or few) clients communicates the resource fingerprint, the identity of the resource remains obfuscated from the crowd-disambiguation machine. As more clients communicate fingerprints for the same resource (e.g., identified by the matching FARIs), respective, differently generated PDRIs of those fingerprints enable the crowd-disambiguation machine to resolve further portions of the resource, ultimately permitting the resource to be revealed and considered non-private (e.g., for use in hint generation or other crowd-sourced services).
MACHINE-DRIVEN CROWD-DISAMBIGUATION OF DATA RESOURCES
Embodiments seek to protect privacy of potentially sensitive client resources in web transactions using crowd-disambiguation. Crowd-disambiguation machines can aggregate information about resources from multiple clients as resource fingerprints, and can use the fingerprints to provide crowd-sourced services in a privacy-protected manner. For example, embodiments can communicate a resource fingerprint as a fully ambiguated resource instance (FARI) and a partially disambiguated resource instance (PDRI). When one (or few) clients communicates the resource fingerprint, the identity of the resource remains obfuscated from the crowd-disambiguation machine. As more clients communicate fingerprints for the same resource (e.g., identified by the matching FARIs), respective, differently generated PDRIs of those fingerprints enable the crowd-disambiguation machine to resolve further portions of the resource, ultimately permitting the resource to be revealed and considered non-private (e.g., for use in hint generation or other crowd-sourced services).