Requesting and transmitting data for related accounts
US-2021320920-A1 · Oct 14, 2021 · US
US12244592B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-12244592-B2 |
| Application number | US-202117358130-A |
| Country | US |
| Kind code | B2 |
| Filing date | Jun 25, 2021 |
| Priority date | Dec 9, 2019 |
| Publication date | Mar 4, 2025 |
| Grant date | Mar 4, 2025 |
A practical reading order for non-experts. Skip the full description unless you need deep technical detail.
What the patent document calls the invention.
A short plain-language summary of the technical disclosure.
Who owns or filed the patent and who is credited as inventor.
Filing, priority, publication, and grant dates set the timeline.
The legal scope of protection — read this for what is actually claimed.
Technology tags used to group this patent with similar filings.
Prior art links and similar publications in this corpus.
Official abstract text for this publication.
Systems and methods for efficiently and securely requesting and receiving, from a remote service, data for multiple accounts associated with the same device or application. In one example, a client device is configured to request application data for all accounts associated with the device or application installation 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. 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.
Opening claim text (preview).
The invention claimed is: 1. A method, comprising: identifying, by one or more processors, from data maintained by a registry service, a plurality of second identifiers corresponding to a plurality of accounts that are associated with a first identifier; performing, by the one or more processors, one or more hash functions on each of the plurality of second identifiers to obtain a hash value for a set of accounts; reducing, by the one or more processors, each of the hash values to a predefined length to obtain a truncated hash value for each account of the set; generating a data structure comprising an entry for each account that associates the truncated hash value for that account with application data associated with the account, and which does not include any of the plurality of second identifiers; and transmitting, to an application backend service, a separate remote procedure call for each of the plurality of second identifiers. 2. The method of claim 1 , further comprising transmitting the data structure to a client computing device. 3. The method of claim 1 , wherein each account is one of a profile, an avatar, a linked service, or a linked device. 4. The method of claim 1 , wherein the first identifier is associated with an application on a client computing device. 5. The method of claim 4 , wherein the first identifier corresponds to a request for application data of the application. 6. The method of claim 1 , further comprising obtaining, by the one or more processors, application data for each account of the set. 7. The method of claim 6 , wherein the application data for each account of the set is obtained from an application backend service. 8. The method of claim 1 , wherein generating the data structure further comprises: ordering at least two entries of the data structure based on a sorting of information relating to the accounts represented in the at least two entries of the data structure; ordering at least two entries of the data structure based on the second identifier corresponding to the account represented in each of the at least two entries of the data structure; or ordering at least two entries of the data structure based on the hash value corresponding to the account represented in each of the at least two entries of the data structure. 9. The method of claim 1 , wherein the one or more hash functions are not the same. 10. The method of claim 1 , wherein the application data comprises a number of messages associated with each account of the set. 11. A method, comprising: identifying, by one or more processors of a client device, a plurality of second identifiers corresponding to a plurality of accounts that are associated with a first identifier; performing, by the one or more processors, one or more hash functions on each of the plurality of second identifiers to obtain a hash value for each of the plurality of accounts; reducing, by the one or more processors, each of the hash values to a predefined length to obtain a truncated hash value for each of the plurality of accounts; and identifying, by the one or more processors, which application data within a data structure corresponds to each of the plurality of accounts using at least the truncated hash values for each of the plurality of accounts, wherein the data structure comprises an entry for each of the plurality of accounts that associates the truncated hash value for a corresponding account with application data for the corresponding account, and which does not include any of the plurality of second identifiers; and transmitting, from the client device to a registry service, a single remote procedure call that includes the first identifier. 12. The method of claim 11 , further comprising receiving the data structure from the registry service. 13. The method of claim 11 , wherein identifying which application data within the data structure corresponds to each of the plurality of accounts further comprises using the order of at least two of the entries of the data structure. 14. The method of claim 11 , wherein the application data within the data structure comprises a number of messages associated with each of the plurality of accounts. 15. The method of claim 14 , wherein: the number of messages associated with each of the plurality of accounts represents a number of unread messages associated with each of the plurality of accounts; or the number of messages associated with each of the plurality of accounts represents a number of total messages associated with each of the plurality of accounts. 16. The method of claim 11 , further comprising: generating, by the one or more processors, an indication on the client device of a number of messages associated with each of the plurality of accounts. 17. The method of claim 11 , wherein the plurality of accounts is associated with a single application installation on the client device. 18. The method of claim 17 , wherein the single application installation is an installation of one of an email application, a social media application, or a banking application.
Protocols for remote procedure calls [RPC] · CPC title
User profiles · CPC title
Hash functions, e.g. MD5, SHA, HMAC or f9 MAC · CPC title
wherein the data content is protected, e.g. by encrypting or encapsulating the payload · CPC title
for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273) · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.