US 10,310,913 B2Granted

Method, device and system for processing parallel services

AssigneeTencent Technology (Shenzhen) Company Limited

InventorsWeijie Ni, Qiming Xie, Jin Zhang, Zhimin Yin, Wenrong Li

Life of this patent

Estimating the term…

Loading patent…

Abstract

The present invention provides a method a device and a system for processing parallel services, which includes: determining, by a synchronization locking server, whether a service request for locking is locked after receiving a locking request sent by a service server, and locking the service request when the service request is unlocked and returning a locking success response to the service server, or returning a locking failure response to the service server when the service request is locked, so as to ensure accuracy of a processing result of the parallel services that are processed across the cities, IDCs or servers.

Claims12

Dependent claims

A computer-implemented method for processing parallel services, the method comprising:

receiving, by a synchronization locking server, a locking request for locking a service request sent by a service server, wherein the locking request carries a service identity, and the service identity is a service-type identity or a user identity that do not change over time;
extracting, by the synchronization locking server, the service identity from the received locking request, and determining whether a service request corresponding to the service identity is locked or not, further comprising:
performing an operation on the service identity according to a preset hash algorithm, and determining whether the service identity has been indexed or not according to the operation result, and
determining, using a locking data list table, that (i) the service request is locked when the service identity has been indexed and a start time of locking the service request has not been cleared, (ii) the service request is unlocked when the service identity has not been indexed, and (iii) the service request is to be unlocked when the start time of locking the service request has been cleared;
in accordance with a determination that the service request is locked, returning a locking failure response to the service server;
in accordance with a determination that the service request is unlocked, indexing the service identity, locking the service request corresponding to the service identity by recording a result of the preset hash algorithm as the service identity and the corresponding start time of locking for the service request in the locking data list table, and returning a locking success response to the service server, wherein the service server performs a service processing based on the service request;
in accordance with a determination that the service request is to be unlocked, clearing the indexed service identity and the corresponding start time of locking the service request and locking the service request corresponding to the service identity by recording a result of the preset hash algorithm as the service identity and the corresponding start time of locking for the service request in the locking data list table, and returning a locking success response to the service server;
receiving, by the synchronization locking server, an unlocking request sent by the service server, after the service server finishes the service processing
extracting, by the synchronization locking server, the service identity from the received unlocking request;
and
unlocking, by the synchronization locking server, the service request corresponding to the service identity.

8 more elements

A synchronization locking server, comprising a memory and a processor communicating with the memory, wherein the memory stores instructions, that when executed by the processor configure the processor to perform the following operations:

receiving, by a synchronization locking server, a locking request for locking a service request sent by a service server, wherein the locking request carries a service identity, and the service identity is a service-type identity or a user identity that do not change over time;
extracting, by the synchronization locking server, the service identity from the received locking request, and determining whether a service request corresponding to the service identity is locked or not, further comprising:
performing an operation on the service identity according to a preset hash algorithm, and determining whether the service identity has been indexed or not according to the operation result, and
determining, using a locking data list table, that (i) the service request is locked when the service identity has been indexed and a start time of locking the service request has not been cleared, (ii) the service request is unlocked when the service identity has not been indexed, and (iii) the service request is to be unlocked when the start time of locking the service request has been cleared;
in accordance with a determination that the service request is locked, returning a locking failure response to the service server;
in accordance with a determination that the service request is unlocked, indexing the service identity, locking the service request corresponding to the service identity by recording a result of the preset hash algorithm as the service identity and the corresponding start time of locking for the service request in the locking data list table, and returning a locking success response to the service server, wherein the service server performs a service processing based on the service request;
in accordance with a determination that the service request is to be unlocked, clearing the indexed service identity and the corresponding start time of locking the service request and locking the service request corresponding to the service identity by recording a result of the preset hash algorithm as the service identity and the corresponding start time of locking for the service request in the locking data list table, and returning a locking success response to the service server;
receiving, by the synchronization locking server, an unlocking request sent by the service server, after the service server finishes the service processing;
extracting, by the synchronization locking server, the service identity from the received unlocking request;
and
unlocking, by the synchronization locking server, the service request corresponding to the service identity.

8 more elements

A non-transitory computer-readable storage medium storing instructions that, when executed by a processor of a synchronization locking server, configure the processor to perform the following operations:

receiving, by a synchronization locking server, a locking request for locking a service request sent by a service server, wherein the locking request carries a service identity, and the service identity is a service-type identity or a user identity that do not change over time;
extracting, by the synchronization locking server, the service identity from the received locking request, and determining whether a service request corresponding to the service identity is locked or not, further comprising:
performing an operation on the service identity according to a preset hash algorithm, and determining whether the service identity has been indexed or not according to the operation result, and
determining, using a locking data list table, that (i) the service request is locked when the service identity has been indexed and a start time of locking the service request has not been cleared, (ii) the service request is unlocked when the service identity has not been indexed, and (iii) the service request is to be unlocked when the start time of locking the service request has been cleared;
in accordance with a determination that the service request is locked, returning a locking failure response to the service server;
in accordance with a determination that the service request is unlocked, indexing the service identity, locking the service request corresponding to the service identity by recording a result of the preset hash algorithm as the service identity and the corresponding start time of locking for the service request in the locking data list table, and returning a locking success response to the service server, wherein the service server performs a service processing based on the service request;
in accordance with a determination that the service request is to be unlocked, clearing the indexed service identity and the corresponding start time of locking the service request and locking the service request corresponding to the service identity by recording a result of the preset hash algorithm as the service identity and the corresponding start time of locking for the service request in the locking data list table, and returning a locking success response to the service server;
receiving, by the synchronization locking server, an unlocking request sent by the service server, after the service server finishes the service processing;
extracting, by the synchronization locking server, the service identity from the received unlocking request;
and
unlocking, by the synchronization locking server, the service request corresponding to the service identity.

8 more elements

Dependencies are inferred from the claim text.

Facts

Application: 14/621,474Filed 13 Feb 2015 · continuation
Priority: CN 2012 1 030349524 Aug 2012
Published: US 2015/0160986 A111 Jun 2015
Granted: 4 Jun 2019
Term ends: Not estimatedThe source records don’t support an estimate.

Classification2 codes

G06F 9/52
Multiprogramming arrangements: program synchronisation; Mutual exclusion, e.g. by means of semaphores
G06F
Computing and data processing

Family

PCT/CN2013/081864Parent of this continuation · filed 20 Aug 2013
US 2015/0160986 A1Pre-grant publication · published 11 Jun 2015
US 10,310,913 B2This patent

From the US filing history. Foreign family members aren’t listed.

Timeline

Citations

Open elsewhere

Building an agent or pulling many patents? Use the API or MCP server instead of scraping pages. Get an API key