Wrapped Continuation Tokens for Multi-Geolocation Data Paging
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional systems face challenges in efficiently storing and retrieving big data across multiple geolocations due to increased volume, variety, and velocity of data, leading to inefficiencies in performance, seamlessness, and scalability.
Innovation Solution
The method involves wrapping continuation tokens with location information to support paging across multiple servers, allowing for efficient data retrieval and aggregation across different geolocations by identifying the geographic location of subsequent data sets and directing requests accordingly.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If data is stored and retrieved across multiple geolocations in conventional systems, then data availability increases, but system complexity and retrieval inefficiency increase
Solution Approach 1:
The patent introduces continuation tokens as intermediary elements that carry location information between data servers and client devices. These tokens mediate the complex multi-location data retrieval process by encapsulating server location data, allowing seamless pagination across geolocations without exposing system complexity to the client.
Solution Approach 2:
The patent segments large data sets into paginated portions, with each page associated with a specific server location. By dividing data into manageable chunks and tracking their locations through continuation tokens, the system makes multi-geolocation retrieval more manageable and less complex.
2Quantity of substance
If data volume increases across multiple geolocations, then data capacity increases, but retrieval performance and efficiency deteriorate
Solution Approach 1:
The system performs preliminary actions by pre-calculating and embedding location information in continuation tokens during data pagination. This advance preparation allows client devices to directly access the correct server locations without performing complex queries, significantly improving retrieval efficiency as data capacity scales.
Solution Approach 2:
The patent changes the parameter structure of data retrieval by introducing location-aware continuation tokens that encode server identification information. This parameter transformation enables efficient routing to specific geolocations based on data size and distribution, maintaining retrieval performance despite increased data capacity.
3Adaptability or versatility
If pagination is implemented across multiple servers, then data scalability increases, but system seamlessness and complexity increase
Solution Approach 1:
Continuation tokens serve as mediators that hide the complexity of multi-server pagination from client devices. By encapsulating server location information and pagination state within these tokens, the system maintains operational seamlessness while achieving scalable data distribution across multiple servers and geolocations.
4Adaptability or versatility
If data is distributed across different geolocations, then system scalability increases, but data retrieval complexity and time increase
Solution Approach 1:
The system performs preliminary actions by pre-computing and storing location information in continuation tokens during the data pagination process. This advance preparation eliminates the need for time-consuming location queries during data retrieval, maintaining fast access times even as the system scales to multiple geolocations.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Aspects of the disclosure relate to wrapping continuation tokens to support paging for multiple servers across different geolocations. An enterprise server may receive a first request for a plurality of records, and the first request for the plurality of records may request a quantity of records exceeding a page size limit. In response to receiving the first request, the enterprise server may retrieve a first set of records comprising a first number of records equal to the page size limit. The enterprise server may generate a first wrapped continuation token comprising location information identifying a geographic location of a first server where a next set of records is to be retrieved. Finally, the enterprise server may send, to the client device, the first set of records and the first wrapped continuation token, which may cause the client device to process the first set of records.