IP Library Granted Patent US 11,086,657
Granted Patent B2
US 11,086,657 · App. 16/266,144 · Granted Aug 10, 2021

Method and system for scheduling transactions in a data system

Inventors: Guangxin Yang (Beijing, CN); Dongyue Wang (Beijing, CN); Xinyu Wang (Beijing, CN); Wei Liang (Beijing, CN); Sihan Ge (Beijing, CN)
Assignee: Verizon Media Inc.
G06F9/466G06F9/485G06F9/4887G06F16/2379
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,086,657
App. No.
16/266,144
Granted
Aug 10, 2021
Kind
B2
Abstract

The present teaching relates to scheduling transactions at a node in a data system. In one example, a request is obtained for performing a first transaction at the node. A mixing condition associated with the first transaction is determined. The first transaction is initiated. The first transaction is suspended when the mixing condition is met. A second transaction is carried out at the node. The first transaction and the second transaction are directed to a same portion of data at the node.

Claims (49)

1. A method, implemented on a machine having at least one processor, storage, and a communication platform connected to a network for scheduling transactions at a node, the method comprising:

initiating a first transaction directed to a portion of data at the node, the first transaction being associated with a preemption criterion;

suspending the first transaction in response to the preemption criterion being satisfied;

identifying, in response to the suspending, a second transaction that is directed to the portion of data at the node in accordance with a priority model;

carrying out the second transaction at the node; and

setting a status flag for at least one record included in the portion of data based on the second transaction, the status flag indicating a manner by which the at least one record is modified by the second transaction so that upon being resumed, the first transaction is to face a same state of the portion of data as when being suspended.

2. The method of claim 1 , wherein the priority model is selected based on information related to a first transaction.

3. The method of claim 2 , wherein the priority model identifies the second transaction based on a user associated with the first transaction.

4. The method of claim 1 , wherein the preemption criterion is one of:

the first transaction running for a pre-determined period of time since the first transaction was initiated or last suspended; and

a first portion of the first transaction having been executed since the first transaction was initiated or last suspended, wherein the first portion is at least one of: a fragment of the first transaction, a step in a fragment, a pre-determined number of blocks in a step, and a pre-determined number of records in a step.

5. The method of claim 1 , further comprising:

continuing the first transaction after the second transaction is completed or when the second transaction is executed for a period of time.

6. The method of claim 1 , further comprising:

recording an execution context for the first transaction before carrying out the second transaction; and

retrieving the execution context and the status flag after carrying out the second transaction.

7. A machine-readable, non-transitory and tangible medium having information recorded thereon for scheduling transactions at a node in a data system, wherein the information, when read by the machine, causes the machine to perform the following:

initiating a first transaction directed to a portion of data at the node, the first transaction being associated with a preemption criterion;

suspending the first transaction in response to the preemption criterion being satisfied;

identifying, in response to the suspending, a second transaction that is directed to the portion of data at the node in accordance with a priority model;

carrying out the second transaction at the node; and

setting a status flag for at least one record included in the portion of data based on the second transaction, the status flag indicating a manner by which the at least one record is modified by the second transaction so that upon being resumed, the first transaction is to face a same state of the portion of data as when being suspended.

8. The medium of claim 7 , wherein the priority model is selected based on information related to a first transaction.

9. The medium of claim 8 , wherein the priority model identifies the second transaction based on a user associated with the first transaction.

10. The medium of claim 7 , wherein the preemption criterion is one of:

the first transaction running for a pre-determined period of time since the first transaction was initiated or last suspended; and

a first portion of the first transaction having been executed since the first transaction was initiated or last suspended, wherein the first portion is at least one of: a fragment of the first transaction, a step in a fragment, a pre-determined number of blocks in a step, and a pre-determined number of records in a step.

11. The medium of claim 7 , the method further comprising:

continuing the first transaction after the second transaction is completed or when the second transaction is executed for a period of time.

12. The medium of claim 7 , the method further comprising:

recording an execution context for the first transaction before carrying out the second transaction; and

retrieving the execution context and the status flag after carrying out the second transaction.

13. A system, having at least one processor, storage, and a communication platform connected to a network for scheduling transactions at a node in a data system, the system comprising:

a transaction execution module configured for:

initiating a first transaction directed to a portion of data at the node, the first transaction being associated with a preemption criterion;

suspending the first transaction in response to the preemption criterion being satisfied;

identifying, in response to the suspending, a second transaction that is directed to the portion of data at the node in accordance with a priority model;

carrying out the second transaction at the node; and

setting a status flag for at least one record included in the portion of data based on the second transaction, the status flag indicating a manner by which the at least one record is modified by the second transaction so that upon being resumed, the first transaction is to face a same state of the portion of data as when being suspended.

14. The system of claim 13 , wherein the priority model is selected based on information related to a first transaction.

15. The system of claim 14 , wherein the priority model identifies the second transaction based on a user associated with the first transaction.

16. The system of claim 13 , wherein the preemption criterion is one of:

the first transaction running for a pre-determined period of time since the first transaction was initiated or last suspended; and

a first portion of the first transaction having been executed since the first transaction was initiated or last suspended, wherein the first portion is at least one of: a fragment of the first transaction, a step in a fragment, a pre-determined number of blocks in a step, and a pre-determined number of records in a step.

17. The system of claim 13 , wherein the transaction execution module is further configured for:

continuing the first transaction after the second transaction is completed or when the second transaction is executed for a period of time.

18. The system of claim 13 , wherein the transaction execution module is further configured for:

recording an execution context for the first transaction before carrying out the second transaction; and

retrieving the execution context and the status flag after carrying out the second transaction.

Assignments (6)
PATENT SECURITY AGREEMENT (FIRST LIEN) Recorded Sep 29, 2022
From: YAHOO ASSETS LLC
To: ROYAL BANK OF CANADA, AS COLLATERAL AGENT
Reel/Frame 061571/0773 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 16, 2021
From: YAHOO AD TECH LLC (FORMERLY VERIZON MEDIA INC.)
To: YAHOO ASSETS LLC
Reel/Frame 058982/0282 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 26, 2020
From: OATH INC.
To: VERIZON MEDIA INC.
Reel/Frame 054258/0635 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2019
From: YANG, GUANGXIN; WANG, DONGYUE; WANG, XINYU; LIANG, WEI; GE, SIHAN
To: YAHOO! INC.
Reel/Frame 048225/0354 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2019
From: YAHOO! INC.
To: YAHOO HOLDINGS, INC.
Reel/Frame 048231/0001 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 4, 2019
From: YAHOO HOLDINGS, INC.
To: OATH INC.
Reel/Frame 048231/0368 →