The internet of things
US-2019349426-A1 · Nov 14, 2019 · US
US11275851B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11275851-B2 |
| Application number | US-201916720320-A |
| Country | US |
| Kind code | B2 |
| Filing date | Dec 19, 2019 |
| Priority date | Dec 19, 2019 |
| Publication date | Mar 15, 2022 |
| Grant date | Mar 15, 2022 |
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.
Methods, systems, and apparatus, including computer programs encoded on computer storage media, for decentralized data management are provided. One of the methods includes: instructing, by an operator, a client to obtain data from a data source, wherein the operator is not allowed to directly obtain data from the data source; receiving, by the operator, encrypted data from the client, wherein the encrypted data is generated by the client based on the obtained data from the data source and an encryption key of an authorized data consumer; and storing, by the operator, the encrypted data into a data store for the authorized data consumer to access and decrypt, wherein the operator is not allowed to read the saved encrypted data from the data store.
Opening claim text (preview).
What is claimed is: 1. A computer-implemented method for decentralized data management, comprising: constructing, by an operator, a data collection task comprising one or more of: location information, a time period, and a user account identifier, wherein the operator comprises a software program; sending, by the operator, the data collection task to a client to obtain data from a data source corresponding to the data collection task, wherein the operator is not allowed to directly obtain data from the data source; receiving, by the operator, encrypted data from the client, wherein the encrypted data is generated by the client based on the obtained data from the data source using an encryption key of an authorized data consumer; and storing, by the operator, the encrypted data into a data store for the authorized data consumer to access and decrypt, wherein the operator is not allowed to read the saved encrypted data from the data store. 2. The method of claim 1 , wherein the storing the encrypted data into the data store comprises: transforming the encrypted data into structured data; and storing the structured data into the data store. 3. The method of claim 1 , further comprising: removing the encrypted data from a storage medium of the operator. 4. The method of claim 1 , wherein the sending the data collection task to the client to obtain the data from the data source comprises: transmitting the user account identifier to the client for the client to obtain the data from the data source according to the user account identifier. 5. The method of claim 1 , wherein the user account identifier is mapped to a user account information comprising one or more of the following: token, cookie, user id (uid), or phone number. 6. The method of claim 1 , wherein the data collection task instructs the client to perform: starting data collection according to the location information, the time period, and the user account identifier; stopping the data collection; or restarting the data collection. 7. The method of claim 1 , wherein: the encrypted data comprises ride-hailing user payment information, ride-hailing trip information, ride-hailing user location information; and the storing, by the operator, the encrypted data into a data store comprises: storing the ride-hailing user payment information into a first data store; storing the ride-hailing trip information into a second data store; and storing the ride-hailing user location information into a third data store. 8. The method of claim 1 , wherein the storing the encrypted data into the data store comprises: storing the encrypted data into the data store by using a Data Access Object (DAO) associated with the data store. 9. The method of claim 1 , wherein the encrypted data is tagged with a time to live (TTL), and the encrypted data is automatically removed from the data store upon expiration of the TTL. 10. A system of an operator for decentralized data management, comprising one or more processors and one or more non-transitory computer-readable memories coupled to the one or more processors and configured with instructions executable by the one or more processors to cause the system to perform operations comprising: constructing, by the operator, a data collection task comprising one or more of: location information, a time period, and a user account identifier; sending, by the operator, the data collection task to a client to obtain data from a data source corresponding to the data collection task, wherein the operator is not allowed to directly obtain data from the data source; receiving, by the operator, encrypted data from the client, wherein the encrypted data is generated by the client based on the obtained data from the data source and an encryption key of an authorized data consumer; and storing, by the operator, the encrypted data into a data store for the authorized data consumer to access and decrypt, wherein the operator is not allowed to read the saved encrypted data from the data store. 11. The system of claim 10 , wherein storing the encrypted data into the data store comprises: transforming the encrypted data into structured data; and storing the structured data into the data store. 12. The system of claim 10 , wherein the operations further comprise: removing the encrypted data from a storage medium of the operator. 13. The system of claim 10 , wherein the data collection task instructs the client to perform: starting data collection according to the location information, the time period, and the user account identifier; stopping the data collection; or restarting the data collection. 14. A non-transitory computer-readable storage medium of an operator for decentralized data management configured with instructions executable by one or more processors to cause the one or more processors to perform operations comprising: constructing, by the operator, a data collection task comprising one or more of: location information, a time period, and a user account identifier; sending, by the operator, the data collection task to a client to obtain data from a data source corresponding to the data collection task, wherein the operator is not allowed to directly obtain data from the data source; receiving, by the operator, encrypted data from the client, wherein the encrypted data is generated by the client based on the obtained data from the data source and an encryption key of an authorized data consumer; and storing, by the operator, the encrypted data into a data store for the authorized data consumer to access and decrypt, wherein the operator is not allowed to read the saved encrypted data from the data store. 15. The storage medium of claim 14 , wherein the storing the encrypted data into the data store comprises: transforming the encrypted data into structured data; and storing the structured data into the data store. 16. The storage medium of claim 14 , wherein the operations further comprise: removing the encrypted data from the operator's storage medium. 17. The storage medium of claim 14 , wherein the data collection task instructs the client to perform: starting data collection according to the location information, the time period, and the user account identifier; stopping the data collection; or restarting the data collection.
Tools and structures for managing or administering access control systems · CPC title
to a system of files or objects, e.g. local or distributed file system or database · CPC title
Providing cryptographic facilities or services · CPC title
where protection concerns the structure of data, e.g. records, types, queries · CPC title
by registering files or documents with a third party · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.