Update coordination in a multi-tenant cloud computing environment
US-10768920-B2 · Sep 8, 2020 · US
US11354295B2 · US · B2
| Field | Value |
|---|---|
| Publication number | US-11354295-B2 |
| Application number | US-201715553952-A |
| Country | US |
| Kind code | B2 |
| Filing date | Aug 18, 2017 |
| Priority date | Aug 18, 2017 |
| Publication date | Jun 7, 2022 |
| Grant date | Jun 7, 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 and systems for processing incoming data in real-time are described herein. The incoming data is processed in real-time to generate data records that may be improved over time, for example, by automatically correcting inaccurate data in the records. In some embodiments, when data is received, a real-time process is initially performed on the received data under a first time constraint to produce first data for a data record. Subsequently, one or more non-real-time processes are then performed on the received data under a second time constraint to produce second data for the data record. The second data may be used to update the data record, for example, to correct any inaccuracy caused by the real-time process of the received data. Preferably, the second time constraint is longer than the first time constraint.
Opening claim text (preview).
What is claimed is: 1. A system, comprising: a non-transitory memory; and one or more hardware processors coupled to the non-transitory memory and configured to read instructions from the non-transitory memory to cause the system to perform operations comprising: receiving a transaction request for processing one or more transactional actions related to a user account based on a set of transaction data; processing, by a first processing module, the transaction request based on the set of transaction data under a first time constraint that indicates a first instance of time to abort the processing of the transaction request by the first processing module, wherein the processing the transaction request under the first time constraint comprises generating a first value for a temporary data record associated with the user account based on the set of transaction data; updating the temporary data record associated with the user account based on the first value; processing, by a second processing module different from the first processing module, the transaction request based on the set of transaction data under a second time constraint that indicates a second instance of time to abort the processing of the transaction request by the second processing module, wherein the second instance of time is later than the first instance of time, and wherein the processing the transaction request under the second time constraint comprises generating a second value for the temporary data record associated with the user account based on the set of transaction data; determining, by the second processing module, that a correction to the temporary data record is required based on a difference between the first value and the second value; determining, by the second processing module, that the first processing module is permitted to edit the temporary data record based on the first instance of time indicated by the first time constraint; in response to determining that the first processing module is permitted to edit the temporary data record, suspending, by the second processing module, the correction to the temporary data record based on the second value; subsequent to the suspending, determining, by the second processing module, that the first processing module is no longer permitted to edit the temporary data record based on the first instance of time indicated by the first time constraint; and in response to determining that the first processing module is no longer permitted to edit the temporary data record, resuming, by the second processing module, the correction to the temporary data record, wherein the resuming the correction comprises changing a value in the temporary record using the second value. 2. The system of claim 1 , wherein the updating the temporary data record comprises changing a data value in the temporary data record using the first value. 3. The system of claim 1 , wherein the transaction request is associated with a timestamp representing a time at which the transaction request is received, and wherein the operations further comprise: determining the first instance of time based on the timestamp and the first time constraint, wherein the updating the temporary data record is in response to a determination that the first instance of time has not passed. 4. The system of claim 1 , wherein the operations further comprise accessing the first value stored in the updated temporary data record, wherein the determining that the correction to the temporary data record is required is further based on comparing the second value against the first value accessed from the updated temporary data record. 5. The system of claim 1 , wherein the operations further comprise: determining, from a plurality of temporary data records associated with the user account, the temporary data record for updating based on a timestamp indicated in the transaction request. 6. The system of claim 1 , wherein the operations further comprise: disregarding, by the first processing module, at least a portion of the transaction request that has not been processed when the processing of the transaction request by the first processing module is aborted. 7. The system of claim 1 , wherein the determining that the first processing module is no longer permitted to edit the temporary data record comprises: determining that the first instance of time has passed. 8. The system of claim 1 , wherein the operations further comprise subsequent to resuming the correction to the temporary data record, updating a permanent data record associated with the user account based on a data value in the temporary data record. 9. The system of claim 1 , wherein the operations further comprise: processing by a third processing module, the transaction request under a third time constraint, wherein the third time constraint indicates a third instance of time that is later than the second instance of time, and wherein the processing the transaction request under the third time constraint comprises generating a third value for the temporary data record; and in response to determining that the second processing module is no longer permitted to edit the temporary data record based on the second time constraint, correcting, by the third processing module, the temporary data record based on the third value. 10. The system of claim 9 , wherein the first processing module is configured to process the transaction request in an online environment, and wherein the third processing module is configured to process the transaction request in an offline environment. 11. The system of claim 1 , wherein the one or more transaction actions comprise at least one of a login transaction or a purchase transaction. 12. A method, comprising: receiving, by one or more hardware processors associated with a data processing system, event data associated with one or more events related to a user account; processing, by a first processing module of the data processing system, the event data under a first time constraint that indicates a first expiration time to abort the processing of the event data by the first processing module, wherein the processing the event data under the first time constraint comprises generating a first value for a temporary data record associated with the user account based on the event data; updating, by the first processing module, the temporary data record associated with the user account based on the first value; processing, by a second processing module of the data processing system different from the first processing module, the event data under a second time constraint that indicates a second expiration time to abort the processing of the event data by the second processing module, wherein the second expiration time is later than the first expiration time, and wherein the processing the event data under the second time constraint comprises generating a second value for the temporary data record associated with the user account based on the event data; determining, by the second processing module, that a correction to the temporary data record is required based on a difference between the first value and the second value; in response to determining that the temporary data record is editable by the first processing module based on the first time constraint, suspending, by the second processing module, the correction to the temporary data record based on the second value; and subsequent to the suspending and in response to determining that the temporary data record is no longer editable by the first processing based on the first time constraint, resuming, by the second processing module, the correction to the temporary
Updates performed during online database operations; commit processing · CPC title
Information retrieval; Database structures therefor; File system structures therefor · CPC title
using timestamps · CPC title
Ensuring data consistency and integrity · CPC title
Temporal data queries · CPC title
Related publications grouped by family.
Answers are generated from the same data shown on this page.