Related Account Data via Single RPC and Truncated Hashes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing methods for requesting and transmitting data for multiple accounts from a single device or application are inefficient, leading to increased latency and security risks due to separate remote procedure calls and exposure of account IDs.
Innovation Solution
A method where a client device makes a single remote procedure call to a registry service using a device or application installation ID, which then retrieves data for multiple accounts and returns it using truncated hash values to obscure actual account IDs, reducing security risks and latency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate remote procedure calls are made for each account, then account data can be retrieved individually, but latency increases and security risks increase due to exposure of account IDs
Solution Approach 1:
The patent combines multiple separate remote procedure calls into a single call by introducing a registry service that aggregates account data. Instead of making individual RPC calls for each account, the system makes one call to retrieve data for multiple accounts simultaneously, thereby reducing latency while maintaining security through obfuscation of account identifiers
Solution Approach 2:
The registry service acts as an intermediary between the client device and the remote service. It receives the single RPC call, identifies associated accounts, retrieves their data, obfuscates account IDs using truncated hash values, and returns the aggregated data. This intermediary approach enables batch processing while protecting account identifier exposure
2Ease of operation
If account IDs are included in remote procedure calls, then specific account data can be requested, but security risks increase due to potential data interception and account ID exposure
Solution Approach 1:
The patent creates a copy of the account identification mechanism using truncated hash values instead of actual account IDs. These hash values serve as placeholders that allow the system to retrieve and identify account data without exposing the actual account identifiers in the network traffic, thus maintaining operational capability while eliminating security risks from interception
Solution Approach 2:
The system changes the parameter used for account identification from actual account IDs to truncated hash values. This parameter transformation maintains the functionality of identifying and retrieving account-specific data while removing the harmful exposure of sensitive account identifiers in the communication protocol
3Reliability
If multiple separate transmissions are made for each account ID, then security can be maintained, but efficiency decreases and latency increases
Solution Approach 1:
The patent merges multiple separate transmissions into a single transmission by using the registry service to aggregate account data. The system makes one RPC call and retrieves data for multiple accounts simultaneously, then returns all data in a single response, thereby improving efficiency while maintaining security through obfuscation of account identifiers throughout the transmission process
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Systems and methods for efficiently and securely requesting and receiving, from a remote service (140, 160), data for multiple accounts associated with the same device or application. In one example, a client device (100) is configured to request application data for all accounts (112) associated with the device or application installation (110) using a single remote procedure call, rather than requiring separate calls for each account, and to do so by providing a single identifier rather than including identifiers specific to each associated account (202). The remote service is further configured to return the requested information in a manner that obfuscates the account identifiers and thus limits their potential use if the communication is intercepted, such that the application data can be efficiently transmitted together even where security or other concerns would otherwise dictate that separate transmissions should be made for each account (302-308).