CN114679495A - Scheduling arrangement method and scheduling execution method for resource service operation request - Google Patents
Scheduling arrangement method and scheduling execution method for resource service operation request Download PDFInfo
- Publication number
- CN114679495A CN114679495A CN202210118358.9A CN202210118358A CN114679495A CN 114679495 A CN114679495 A CN 114679495A CN 202210118358 A CN202210118358 A CN 202210118358A CN 114679495 A CN114679495 A CN 114679495A
- Authority
- CN
- China
- Prior art keywords
- request
- resource service
- operation request
- service operation
- resource
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
- 238000000034 method Methods 0.000 title claims abstract description 90
- 238000009825 accumulation Methods 0.000 claims abstract description 58
- 230000007717 exclusion Effects 0.000 claims abstract description 37
- 238000012545 processing Methods 0.000 claims abstract description 23
- 238000004891 communication Methods 0.000 claims description 37
- 230000001360 synchronised effect Effects 0.000 claims description 12
- 230000000977 initiatory effect Effects 0.000 claims description 10
- 230000004044 response Effects 0.000 claims description 10
- 238000012546 transfer Methods 0.000 claims description 9
- 230000008569 process Effects 0.000 abstract description 13
- 238000010586 diagram Methods 0.000 description 9
- 238000011084 recovery Methods 0.000 description 6
- 238000005516 engineering process Methods 0.000 description 5
- 230000002159 abnormal effect Effects 0.000 description 3
- 230000004913 activation Effects 0.000 description 3
- 238000002955 isolation Methods 0.000 description 3
- 238000007781 pre-processing Methods 0.000 description 3
- 238000004590 computer program Methods 0.000 description 2
- 230000006870 function Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 2
- 238000013473 artificial intelligence Methods 0.000 description 1
- 230000005540 biological transmission Effects 0.000 description 1
- 230000015556 catabolic process Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000004883 computer application Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000008676 import Effects 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000006855 networking Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
- 230000001052 transient effect Effects 0.000 description 1
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/12—Protocols specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/34—Network arrangements or protocols for supporting network services or applications involving the movement of software or configuration parameters
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Health & Medical Sciences (AREA)
- Computing Systems (AREA)
- General Health & Medical Sciences (AREA)
- Medical Informatics (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
The application discloses a scheduling and arranging method and a scheduling and executing method of resource service operation requests, wherein the scheduling and arranging method comprises the following steps: determining whether mutually exclusive operation information exists in operation request data carried in the resource service operation request according to the acquired resource service operation request; if yes, determining whether a mutually exclusive resource service operation request with a mutually exclusive operation relation with the resource service operation request exists in a first stack table for storing the first resource service operation request; and if so, storing the resource service operation request into a second accumulation table for storing a second resource service operation request, thereby avoiding the problem that at least two request operation sequences with a mutual exclusion operation relationship are disordered in the process of executing and processing the resource service operation request, and ensuring the sequence of the mutual exclusion operation.
Description
Technical Field
The present application relates to the field of computer application technologies, and in particular, to a scheduling arrangement method and a scheduling execution method for a resource service operation request. The application also relates to a scheduling execution method and device of the Internet of things card service request, a computer storage medium and an electronic device.
Background
With the continuous discovery of computer technology and internet technology, the internet of things also grows under the background of times and the demand of technical development.
Service demand characteristics in the application scenario of the internet of things generally cause a large number of service requests to emerge when a service computing node arrives, for example: the service requests at the beginning or end of the month increase dramatically, which in turn leads to a timeout or breakdown of the service response of the service system.
Disclosure of Invention
The application provides a scheduling and arranging method of a resource service operation request, which aims to solve the problem of service response timeout or system crash caused by uneven request flow control in the prior art.
The application provides a method for arranging resource service operation requests, which comprises the following steps:
determining whether mutually exclusive operation information exists in operation request data carried in the resource service operation request according to the acquired resource service operation request;
if yes, determining whether a mutually exclusive resource service operation request with a mutually exclusive operation relation with the resource service operation request exists in a first stack table for storing the first resource service operation request;
and if so, storing the resource service operation request into a second accumulation table for storing a second resource service operation request.
In some embodiments, further comprising:
and when the determined operation request data carried in the resource service operation request does not have mutual exclusion operation information, storing the resource service operation request into the first stack table.
In some embodiments, further comprising:
when the mutually exclusive resource service operation request with the mutually exclusive operation relation with the resource service operation request does not exist in the first stack table, storing the resource service operation request into the first stack table.
In some embodiments, the determining, according to the obtained resource service operation request, whether there is mutual exclusion operation information in operation request data carried in the resource service operation request includes:
determining whether a service providing request needs to be initiated to a service source end providing the resource service or not according to the resource service operation request;
and if so, determining whether the operation request data carried in the resource service operation request has mutual exclusion operation information.
In some embodiments, further comprising:
and when the source end which needs to provide the resource service is determined whether to initiate the service providing request to the source end which provides the resource service is determined not according to the resource service operation request, processing the resource service operation request.
The present application further provides a scheduling and scheduling apparatus for a resource service operation request, including:
a first determining unit, configured to determine, according to an obtained resource service operation request, whether there is mutual exclusion operation information in operation request data carried in the resource service operation request;
a second determining unit, configured to determine, when a determination result of the first determining unit is yes, whether a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request exists in a first stack table used for storing the first resource service operation request;
and the storage unit is used for storing the resource service operation request into a second accumulation table used for storing a second resource service operation request when the determination result of the second determination unit is yes.
The present application further provides a method for scheduling and executing a resource service operation request, including:
acquiring a first resource service operation request in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first resource service operation request;
determining whether a requested operation performed on the first resource servicing operation request is successfully performed;
If yes, transferring a second resource service operation request in a second stack table to the first stack table for execution; the second stack table is used for storing the request operation data of the second resource service operation request which has a mutually exclusive operation relationship with the request operation data of the first resource service operation request in the first stack table.
In some embodiments, the determining whether the request operation performed on the first resource service operation request was successfully performed comprises:
determining whether the first resource service operation request has a configured interface to perform a request operation;
if so, initiating an execution request of the first resource service operation request according to the acquired interface authority of the interface; or, if not, initiating an execution request of the first resource service operation request;
in response to the execution request, determining whether a requested operation of the first resource servicing operation request was successfully executed.
In some embodiments, further comprising:
and updating the first resource service operation request of the first stack table when the determination is made whether the request operation performed on the first resource service operation request is successfully performed, and if not, updating the first resource service operation request of the first stack table.
In some embodiments, further comprising:
writing the execution state of the first resource servicing operation request into the first stack table.
In some embodiments, the writing of the execution state of the first resource servicing operation request to the first accumulation table includes at least one of:
when the request operation of the first resource service operation request is executed based on a synchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
when the request operation of executing the first resource service operation request is successfully executed based on a synchronous execution interface, modifying the executing state in the first accumulation table into an executing successful state;
when the execution of the request operation of executing the first resource service operation request is failed based on a synchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state;
when the request operation of the first resource service operation request is executed based on an asynchronous execution interface, modifying the state to be executed written in the first stack table aiming at the first resource service operation request into an executing state;
When the request operation of executing the first resource service operation request is successfully executed based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an asynchronous state;
when the request operation of executing the first resource service operation request fails to execute based on the asynchronous execution interface, the executing state written in the first stack table aiming at the first resource service operation request is modified into an executing failure state.
In some embodiments, said transferring a second resource service operation request in a second heap table into said first heap table for execution comprises:
selecting a target resource service operation request with the earliest storage time from the second accumulation list according to the storage time;
and transferring the target resource service operation request to the first stack table for execution.
The present application further provides a scheduling execution apparatus for a resource service operation request, including:
the acquisition unit is used for acquiring a first resource service operation request in the first stack table; wherein the first accumulation table is used for storing request operation data of the first resource service operation request;
A determining unit, configured to determine whether a request operation performed on the first resource service operation request is successfully performed;
a transfer unit, configured to transfer a second resource service operation request in a second stack table to the first stack table for execution when a determination result of the determination unit is yes; the second stack table is used for storing the request operation data of the second resource service operation request which has a mutually exclusive operation relationship with the request operation data of the first resource service operation request in the first stack table.
The application also provides a method for scheduling the Internet of things card service request, which comprises the following steps:
acquiring a first communication service request aiming at the Internet of things card in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first communication service request;
determining whether a request operation performed on the first communication service request is successfully performed;
if yes, transferring the second communication service request in the second stack table to the first stack table for execution; wherein the second stack table is configured to store request operation data of the second communication service request in a mutually exclusive operation relationship with the request operation data of the first communication service request in the first stack table.
The application also provides a computer storage medium for storing the data generated by the network platform and a program for processing the data generated by the network platform;
when the program is read and executed by the processor, the program executes the scheduling and arranging method of the resource service operation request; or, executing the scheduling execution method of the resource service operation request; or, the scheduling method of the service request of the internet of things card is executed.
The present application further provides an electronic device, comprising:
a processor;
the memory is used for storing a program for processing data generated by the network platform, and when the program is read and executed by the processor, the program executes the scheduling and arranging method of the resource service operation request; or, executing the scheduling execution method of the resource service operation request; or, the scheduling method of the service request of the internet of things card is executed.
Compared with the prior art, the method has the following advantages:
according to the scheduling and arranging method of the resource service operation request, whether the mutually exclusive resource service operation request needs to be determined to be stored in the first accumulation table is determined by determining whether the mutually exclusive operation information exists in the resource service operation request. When the resource service operation request has the mutual exclusion operation information, namely the mutual exclusion resource service operation request is stored in the first accumulation table, the resource service operation request is stored in the second accumulation table, so that the problem that at least two request operation sequences with mutual exclusion operation relations are disordered in the process of executing and processing the resource service operation request is avoided, and the sequence of the mutual exclusion operation is ensured.
In addition, by preprocessing the resource service operation request, the resource service operation request with the mutual exclusion operation is ensured to be isolated from the resource service operation request without the mutual exclusion operation in the scheduling and arranging process, and the scheduling and arranging speed of the resource service operation request with the mutual exclusion operation is improved.
According to the scheduling execution method of the resource service operation request, flow control and accumulation of the resource service operation request of the interface dimension can be achieved through the configured provider interface, and stability of processing of the access resource service operation request in the south direction is guaranteed. In the process of scheduling execution, after the processing of the first resource service operation request in the first accumulation table is completed, scheduling the second resource service operation request stored earliest in the second accumulation table to the first accumulation table for operation execution, so that the resource service operation request in the accumulation table can be pulled at regular time, and the processing speed of the resource service operation request is improved under the condition of realizing the isolation of the resource service operation request operation.
Drawings
FIG. 1 is a flowchart of an embodiment of a scheduling method for scheduling a resource service operation request provided in the present application;
FIG. 2 is a schematic structural diagram illustrating scheduling of an embodiment of a scheduling method for resource service operation requests provided in the present application;
FIG. 3 is a schematic structural diagram of an embodiment of a scheduling apparatus for scheduling a resource service operation request provided in the present application;
FIG. 4 is a flowchart of an embodiment of a method for scheduling execution of a resource service operation request provided in the present application;
FIG. 5 is a schematic structural diagram of an embodiment of a scheduling execution apparatus for a resource service operation request provided in the present application;
fig. 6 is a flowchart of an embodiment of a method for scheduling a service request of an internet of things card according to the present application;
fig. 7 is a schematic diagram of a scheduling architecture of an embodiment of a scheduling method for a service request of an internet of things card according to the present application;
fig. 8 is a schematic structural diagram of an embodiment of a scheduling execution device for a service request of an internet of things card according to the present application;
fig. 9 is a schematic structural diagram of an embodiment of an electronic device provided in the present application.
Detailed Description
In the following description, numerous specific details are set forth in order to provide a thorough understanding of the present application. This application is capable of implementation in many different ways than those herein set forth and of similar import by those skilled in the art without departing from the spirit of this application and is therefore not limited to the specific implementations disclosed below.
The terminology used in the description herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. The description used in this application and in the appended claims is for example: the terms "a," "an," "first," and "second," etc., are not intended to be limiting in number or order, but rather are used to distinguish one type of information from another.
As can be known from the above background art, the internet of things can cause a large number of service requests when a service computing node arrives, thereby causing problems such as service response timeout or system crash of a service system. The inventive concept of the present application also arises based on the above technical problems. The application scenarios involved may include: intelligent audio amplifier, intelligent house, agricultural equipment, intelligent media screen, sharing treasured that charges etc.. The function realization under each scene of the internet of things is generally to realize the communication function of data by installing an internet of things card on access equipment, and the internet of things card is connected with a wireless network through an interface by an SIM card, a sensor, a two-dimensional code and the like which are installed on various objects, so that the communication and conversation between people and the objects and between the objects can be realized. The internet of things can be understood as a network connecting objects. The internet of things card is also called a flow card and is used for transmitting data, sending instructions and the like, and is widely applied to the fields of artificial intelligence and internet of things, such as internet of vehicles, charging piles, vending machines, security and the like. In this embodiment, how to solve the problem of service response timeout or system crash caused by the uneven flow control request will be described with an internet of things platform as a management scheduling side. The communication resources of the internet of things card platform depend on accessed suppliers including direct connection operators and third-party service providers, and service capabilities of the suppliers may be greatly different. In the face of limited supplier capacity and the requirement of realizing scheduling and decision of resources for service requests which are flooded in large quantities, the stability of a supply chain system is guaranteed, and therefore efficient, high-quality and high-reliability communication service is provided. The following describes in detail a method for arranging resource service operation requests provided by the present application.
As shown in fig. 1 and fig. 2, fig. 1 is a flowchart of an embodiment of an arranging method of a resource service operation request provided by the present application, and fig. 2 is a schematic structural diagram of an arrangement of an embodiment of a scheduling arranging method of a resource service operation request provided by the present application, where the embodiment may include:
step S101: and determining whether mutually exclusive operation information exists in operation request data carried in the resource service operation request according to the acquired resource service operation request.
In this embodiment, the resource service operation request in step S101 may be a service request for an internet of things card, for example: an account opening service, an account selling service, a package renewal service, a release/bind service, a stop/recovery service, and the like. Mutual exclusion operation information may be understood as operations that are opposite or unrelated in operation to the requesting service, such as: and (5) stopping and resetting.
The purpose of step S101 is to determine whether there is mutual exclusion operation information in the resource service operation request.
In this embodiment, the step S101 of determining whether the operation request data carried in the resource service operation request has the mutual exclusion operation information may determine whether the mutual exclusion operation information exists by identifying field information in the operation request data, for example: identifying the field of the operation request data, and determining whether mutually exclusive operation information exists in the operation information described by the field.
In this embodiment, the specific implementation process of step S101 may include:
step S101-1: determining whether a service providing request needs to be initiated to a service source end providing the resource service or not according to the resource service operation request; in this embodiment, the service source may be understood as a provider service providing resource services, for example: when the resource service operation request is a communication service request, the provider side may be a service side providing a communication service.
Step S101-2: and if so, determining whether the operation request data carried in the resource service operation request has mutual exclusion operation information.
And if the determination result in the step S101-1 is negative, scheduling the resource service operation request to an execution processing side. In this embodiment, when the determination result is negative, the resource service operation request is dispatched to the internet of things card service platform for processing, and of course, the resource service operation request may also be dispatched to an execution processing side of the service source end for execution processing.
The step S101-1 may be understood as preprocessing the resource service operation request, and determining whether the resource service operation request needs to complete the related data service through the request service source end. If the request is yes, it indicates that the resource service operation request may have a mutual exclusion operation, and if the request is not yes, it indicates that the resource service operation request does not have a mutual exclusion operation, and the related request operation can be directly completed through the internet of things card service platform without being completed through the service source end.
The purpose of the step S101-2 is to determine whether there is mutual exclusion operation information in the resource service operation request, for example: identifying the operation field by identifying the operation request data in the resource service operation request, and determining whether the mutual exclusion operation information exists according to the identified operation field, such as: the identified operation field is shutdown, and the operation mutually exclusive with the shutdown is recovery, so that mutually exclusive operation information exists when the resource service operation request is determined to be the shutdown request. When the mutual exclusion operation information exists, step S102 is performed.
The step S102: if yes, determining whether a mutually exclusive resource service operation request with a mutually exclusive operation relation with the resource service operation request exists in a first stack table for storing the first resource service operation request.
The purpose of step S102 is to determine whether there is a mutex resource servicing operation request in the first stack table.
In this embodiment, the step S102 is to determine whether a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request is stored in the first stack table when the determination result in the step S101 is yes, where the first stack table is used for storing the first resource service operation request. In this embodiment, the determination result of step S102 may include at least two types, that is, the determination result is yes or the determination result is no, and of course, the determination result may also include that the determination result is abnormal, and when the determination result is abnormal, no subsequent operation may be performed, and information such as an abnormal prompt or an alarm is output. In this embodiment, the determination result is mainly described in two ways, yes and no. For example: if the resource service operation request is a service request of a package due shutdown, whether a service request of a machine recovery exists needs to be searched in the first stacking table, and if the service request of the machine recovery exists in the first stacking table, the service request of the machine recovery in the first stacking table and the service request of the package due shutdown can be determined to be a mutually exclusive resource service operation request of a mutually exclusive operation relationship, that is, the service request of the machine recovery is the mutually exclusive resource service operation request.
The step S102 is based on the subsequent scheduling operation executed in the step S101-2 when the mutual exclusion operation information exists in the resource service operation request. If the resource service operation request is a service request for which the package is due and stopped, whether a service request for recovering the machine exists needs to be searched in the first stacking table, and if a service request for changing the package exists in the first stacking table, it may be determined that the service request for changing the package in the first stacking table and the service request for which the package is due and stopped have no mutual exclusive operation relationship, that is, the mutually exclusive resource service operation request does not exist in the first stacking table.
In the step S101-2, when the resource service operation request does not have the mutual exclusion operation information, that is, the resource service operation request is identified, and when the field having the mutual exclusion operation relationship is not identified, it indicates that the resource service operation request does not have the mutual exclusion operation information, and at this time, the resource service operation request may be stored in the first accumulation table, so as to implement scheduling and arrangement of the resource service operation request.
Step S103: and if so, storing the resource service operation request into a second accumulation table for storing a second resource service operation request.
The purpose of step S103 is to schedule the resource service operation request when the determination result of step S102 is yes.
In this embodiment, when the determination result in the step S102 is yes, the resource service operation request is stored in a second stack table, that is, when the first stack table stores a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request, the resource service operation request is stored in the second stack table, so as to avoid that at least two resource service operation requests having a mutually exclusive operation relationship exist in the first stack table, and ensure the order of mutually exclusive operations when the resource service operation requests are executed. The resource service operation requests stored in the second accumulation table may be stored in a storage manner of sorting according to storage time or in a queue manner, so that first-in first-out may be implemented during subsequent scheduling.
In this embodiment, when the determination result in the step S102 is negative, that is, when the mutually exclusive resource service operation request relative to the resource service operation request does not exist in the first stack table, the resource service operation request is stored in the first stack table.
The foregoing is a description of an embodiment of a scheduling and arranging method for a resource service operation request provided by the present application, where the scheduling and arranging method determines whether it is necessary to determine whether a mutually exclusive resource service operation request is stored in a first accumulation table by determining whether there is mutually exclusive operation information in the resource service operation request, and when there is mutually exclusive operation information in the resource service operation request and the resource service operation request is stored in the first accumulation table, the resource service operation request is stored in a second accumulation table in a mutually exclusive manner, so as to avoid a problem that at least two mutually exclusive request operation sequences of mutually exclusive operation relationships are disordered in a process of executing and processing the resource service operation request, and ensure the sequence of operations.
In addition, by preprocessing the resource service operation request, the resource service operation request with the mutual exclusion operation is ensured to be isolated from the resource service operation request without the mutual exclusion operation in the scheduling and arranging process, and the scheduling and arranging speed of the resource service operation request with the mutual exclusion operation is improved.
The above is a specific description of an embodiment of a scheduling and scheduling method for a resource service operation request provided by the present application, and corresponds to the foregoing embodiment of the scheduling and scheduling method for a resource service operation request provided by the present application, and the present application further discloses an embodiment of a scheduling and scheduling apparatus for a resource service operation request, please refer to fig. 3. The device embodiments described below are merely illustrative.
As shown in fig. 3, fig. 3 is a schematic structural diagram of an embodiment of a scheduling and scheduling apparatus for a resource service operation request provided in the present application, where the scheduling and scheduling embodiment may include: a first determination unit 301, a second determination unit 302 and a storage unit 303.
The first determining unit 301 is configured to determine, according to the obtained resource service operation request, whether there is mutual exclusion operation information in operation request data carried in the resource service operation request.
The second determining unit 302 is configured to determine, when the determination result of the first determining unit is yes, whether a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request exists in a first stack table used for storing the first resource service operation request.
The storage unit 303 is configured to store the resource service operation request in a second accumulation table for storing a second resource service operation request when the determination result of the second determining unit 302 is yes.
The first determining unit 301 may include: a request initiation determining subunit, configured to determine, according to the resource service operation request, whether a service providing request needs to be initiated to a service source end that provides a resource service; the first determining unit 301 is specifically configured to determine whether there is mutually exclusive operation information in the operation request data carried in the resource service operation request, when the determination result of the request initiation determining subunit is yes. When the determination result of the request initiation determination subunit is negative, the first determination unit is specifically configured to schedule the resource service operation request to an execution processing side.
In this embodiment, the storing unit 303 may be further configured to store the resource service operation request into the first stack table when the determination result of the first determining unit 301 is negative.
In this embodiment, the storing unit 303 may be further configured to, when the determination result of the second determining unit 302 is negative, store the resource service operation request into the first stack table.
The above is a description of an embodiment of a scheduling and scheduling apparatus for a resource service operation request provided in the present application, and for specific contents of the embodiment of the scheduling and scheduling apparatus, reference may be made to the contents of the above embodiment of the scheduling and scheduling method, and details are not repeated here.
Based on the above, the present application further provides a method for scheduling and executing a resource service operation request, as shown in fig. 4, fig. 4 is a flowchart of an embodiment of the method for scheduling and executing a resource service operation request provided by the present application, where the embodiment of the method for scheduling and executing includes:
step S401: acquiring a first resource service operation request in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first resource service operation request.
In this embodiment, the step S401 is to obtain the first resource service operation request. The first resource servicing operation request is obtained from the first stack table. The first resource service operation request and the first accumulation table may refer to the description of step S101 above.
Step S402: determining whether a requested operation performed on the first resource servicing operation request was performed successfully.
The step S402 is to determine whether the request operation of the first resource service operation request is successfully executed, and specifically may include:
step S402-1: determining whether the first resource service operation request has a configured interface to perform a request operation; wherein the interface may be understood as a service provider interface capable of providing an operation service for said first resource service operation request. In this embodiment, the interface may also be understood as a resource providing a service. The interface may be configured in advance, and the specific interface (which may also be referred to as a resource) configuration may be a configuration code corresponding to an operation generated by information such as serviceVersion, serviceVersion _ operation (service version _ operation information), sublierid _ account (vendor ID _ account), sublierid _ account _ operation (vendor ID _ account _ operation information), and the like, where the configuration code is used to represent the interface; where account is the account of the supplier, avoiding possible duplication of account names, where a supplierId (supplier ID) is appended. The implementation of the configuration coding may be, for example: the requested service version is CUCC _ SELF _ V1, the business operation is IOT _ ASSETS _ ACTIVE, the account number of the card is 166WLW014184, the supplier is Qingdao Unicom (ID:1619674952767000), and the generated configuration code is as follows:
CUCC _ SELF _ V1; - (version V1, china unicom);
CUCC _ SELF _ V1_ IOT _ ASSETS _ ACTIVE; - - (internet of things card activation indicating china unicom version V1);
1619674952767000_166WLW 014184; - - (14184 account number representing the supplier);
1619674952767000_166WLW014184_ IOT _ ASSETS _ ACTIVE; - - (activation of the internet of things card representing the 14184 account of the supplier);
the specific implementation process of step S402-1 may be to search a database for a configuration code matching the first resource server request, and obtain the interface according to the searched configuration code. The database may store a table of configuration codes. For example:
assume that the list of eligible ids returned is: 4,1,3. And searching the configuration code by using the Id-4, if the configuration code exists, returning immediately, otherwise, searching by using the Id-1, if the configuration code does not exist, continuously searching by using the Id-3, and if the configuration code does not exist, indicating that the request is not limited and the access is possible.
And allowing a plurality of resource configurations to be returned in the resource search, wherein resource _ config is a resource configuration table, and resource _ lookup _ config is a resource configuration lookup table. Account resource configuration under the same provider is basically the same, and a placeholder is supported by the name _ pattern (resource name format) of the resource configuration table. For example: resource configuration obtained through 1619674952767000_166WLW014184_ IOT _ ASSETS _ ACTIVE (Id 1619674952767000 as provider, 166WLW014184 as account, internet of things card activation request):
| name _ pattern (resource name format) | Permit (license) |
| API_CUCC_SELF_V1_ACTIVE_{SupplierId}_{Account} | 40 |
Instantiating a resource according to resource configuration, and generating a resource name according to an API _ CUCC _ SELF _ V1_ ACTIVE _ { SupplierId } _ { Account } format, namely: API _ CUCC _ SELF _ V1_ ACTIVE _1619674952767000_166WLW 014184; thereby determining an interface of the first resource service operation request configuration for performing the request operation.
Step S402-2: when the determination result in the step S402-1 is yes, initiating an execution request of the first resource service operation request according to the acquired interface permission of the interface; when it is determined in the step S402-1 that the first resource service operation requests the presence of the configured interface (resource) for performing the request operation, the interface right of the interface, i.e. the license as in the example in the step S402-1, is acquired. The specific implementation process of step S402-2 may be an execution request initiated to a provider after the interface permission is acquired. Or, when the determination result of the step S402-1 is negative, the execution request of the first resource service operation request is initiated, that is, the execution request is initiated to the provider.
Step S402-3: in response to the execution request, determining whether a requested operation of the first resource servicing operation request was successfully executed.
Step S403: if so, transferring the second resource service operation request in the second stack table to the first stack table for execution; the second stack table is used for storing the request operation data of the second resource service operation request which has a mutually exclusive operation relation with the request operation data of the first resource service operation request in the first stack table.
The purpose of step S403 is to: when the determination result based on the step S402-3 is yes, the request information in the second pile table is transferred to the first pile table.
The specific implementation process of step S403 may include:
step S403-1: selecting a target resource service operation request with the earliest storing time in the second accumulation table according to the storing time;
step S403-2: and transferring the target resource service operation request to the first stack table for execution.
In order to avoid the problem of repeated scheduling of the resource service operation request, the embodiment further needs to record an execution state for the resource service operation request, and the method specifically includes:
writing the execution state of the first resource servicing operation request into the first stack table.
The execution state for the write in the first stack table may include at least one of:
When the request operation of the first resource service operation request is executed based on a synchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
when the request operation of executing the first resource service operation request is successfully executed based on a synchronous execution interface, modifying the executing state in the first accumulation table into an executing successful state;
when the execution of the request operation of executing the first resource service operation request is failed based on a synchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state;
when the request operation of the first resource service operation request is executed based on an asynchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
when the request operation of executing the first resource service operation request is successfully executed based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an asynchronous state;
When the request operation of executing the first resource service operation request fails to execute based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state.
In this embodiment, when the execution of the request operation of the first resource service operation request fails in response to the execution request in step S402-3, the first resource service operation request of the first stack table is updated. In this embodiment, in response to the execution request, the execution failure and/or the success of the request operation of the first resource service operation request may be recorded as the execution state. When the first resource service operation request in the first stack table fails to be executed, the process may return to step S401 to continue execution, that is, the next resource service operation request is scheduled to be executed.
According to the embodiment of the scheduling execution method of the resource service operation request, the flow control and accumulation of the resource service operation request of the interface dimension can be realized through the configured provider interface, and the stability of the processing of the access resource service operation request in the southbound direction is ensured. In the process of scheduling execution, after the processing of the first resource service operation request in the first stack table is completed, scheduling the second resource service operation request stored earliest in the second stack table to the first stack table for operation execution, so that the resource service operation request in the stack table can be pulled at regular time, and the processing speed of the resource service operation request is improved under the condition of realizing the isolation of the resource service operation request operation.
The foregoing is a detailed description of an embodiment of a method for scheduling and executing a resource service operation request provided by the present application, and corresponds to the foregoing embodiment of a method for scheduling and executing a resource service operation request, and the present application further discloses an embodiment of a device for scheduling and executing a resource service operation request, please refer to fig. 5, since the device embodiment is substantially similar to the method embodiment, the description is relatively simple, and related points can be found in part of the description of the method embodiment. The device embodiments described below are merely illustrative.
As shown in fig. 5, fig. 5 is a schematic structural diagram of an embodiment of a scheduling execution apparatus for a resource service operation request provided in the present application; the scheduling execution device embodiment comprises:
an obtaining unit 501, configured to obtain a first resource service operation request in a first stack table; wherein the first accumulation table is used for storing request operation data of the first resource service operation request. The step S401 may be referred to for a specific implementation process of the obtaining unit 501, and details are not repeated here.
A determining unit 502, configured to determine whether a requested operation performed on the first resource service operation request is successfully performed. In this embodiment, the determining unit 502 may include: a configuration determination subunit, a request initiation subunit, and an execution determination subunit.
The configuration determining subunit is configured to determine whether the first resource service operation request has a configured interface for performing the request operation; wherein the interface may be understood as a service provider interface capable of providing an operation service for said first resource service operation request. Specifically, the configuration code matching with the first resource server request is searched in the database, and the interface is obtained according to the searched configuration code, and the description of the step S402-1 may be referred to for related content.
The request initiating subunit is configured to, when the determination result of the configuration determining subunit is yes, initiate an execution request of the first resource service operation request according to the acquired interface permission of the interface; or, when the determination result of the configuration determination subunit is negative, the configuration determination subunit initiates an execution request of the first resource service operation request, that is, initiates an execution request to a provider.
The execution determining subunit is configured to determine, in response to the execution request, whether the request operation of the first resource service operation request is successfully executed.
A transferring unit 503, configured to transfer a second resource service operation request in a second stack table to the first stack table for execution according to a yes determination result of the determining unit; the second stack table is used for storing the request operation data of the second resource service operation request which has a mutually exclusive operation relation with the request operation data of the first resource service operation request in the first stack table.
In this embodiment, the transferring unit 503 may include: selecting a subunit and transferring the subunit.
And the selecting subunit is used for selecting the target resource service operation request with the earliest storing time in the second accumulation table according to the storing time.
The transfer subunit is configured to transfer the target resource service operation request to the first stack table for execution.
In order to avoid the problem of repeated scheduling of the resource service operation request, the embodiment further needs to record an execution state for the resource service operation request, and the method specifically includes: a status writing unit, configured to write an execution status of the first resource service operation request into the first stack table. The execution state specifically written by the state writing unit may include at least one of:
when the request operation of the first resource service operation request is executed based on a synchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
when the request operation of executing the first resource service operation request is successfully executed based on a synchronous execution interface, modifying the executing state in the first accumulation table into an executing successful state;
When the execution of the request operation of executing the first resource service operation request fails based on a synchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state;
when the request operation of the first resource service operation request is executed based on an asynchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
when the request operation of executing the first resource service operation request is successfully executed based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an asynchronous state;
when the request operation of executing the first resource service operation request fails to execute based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state.
The present embodiment may further include: and the updating unit is used for updating the first resource service operation request of the first stack table when the determination result of the execution determination subunit is negative, namely, when the execution fails.
The above is a description of an embodiment of a scheduling execution device for a resource service operation request provided in the present application, and for specific contents of the embodiment of the scheduling execution device, reference may be made to the contents of the above embodiment of the scheduling execution method, and a repeated description of corresponding contents is not repeated here.
Based on the above, the present application further provides a method for scheduling an internet of things card service request, as shown in fig. 6, where fig. 6 is a flowchart of an embodiment of the method for scheduling an internet of things card service request provided by the present application, and the embodiment of the method for scheduling may include:
step S601: acquiring a first communication service request aiming at the Internet of things card in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first communication service request.
Step S602: determining whether the request operation performed on the first communication service request is successfully performed.
Step S603: if yes, transferring the second communication service request in the second accumulation table to the first accumulation table for execution; wherein the second stack table is configured to store the request operation data of the second communication service request in a mutually exclusive operation relationship with the request operation data of the first communication service request in the first stack table.
In this embodiment, the internet of things card is an 2/3/4G card provided by mobile, telecommunication and internet operators, the appearance of the consumer-grade card is basically the same as that of a common SIM card, and a special number segment is adopted, so that the requirements of intelligent hardware and internet of things industries on equipment networking are met.
As shown in fig. 7, in this embodiment, the received communication service requests are scheduled and arranged according to a mutual exclusion operation relationship, that is, stacked in a first stack table or a second stack table, where the first stack table and the second stack table are stored in a database, and the distributed task scheduling platform may pull the to-be-processed communication service request from the database according to a set trigger time, that is, pull the first communication service request from the first stack table as the to-be-processed communication service request. And when the first communication service request is successfully executed, recording the execution state, and transferring the second communication service request stored earliest in the second accumulation table to the first accumulation table to serve as the communication service request to be processed to wait for the scheduling platform to schedule and execute. Scheduling execution may initiate an execution request to the vendor according to the determined interface.
For the specific contents of the above steps S601 to S603, reference may be made to the contents of the above steps S101 to S103 and steps S401 to S403, and the details are not repeated here.
In the embodiment of the scheduling method for the internet of things card service request provided by the application, the processing capacity of a provider is utilized to the maximum extent through the configuration interface, and when the request is overstocked, the operation request data is stored in the first accumulation table or the second accumulation table according to the mutual exclusion operation relationship, so that the isolation between the execution tasks of the service request is realized, and the same service request is prevented from being scheduled repeatedly.
Based on the above, the present application further provides a scheduling apparatus for a service request of an internet of things card, and as shown in fig. 8, an embodiment of the scheduling apparatus includes:
an obtaining unit 801, configured to obtain a first communication service request for an internet of things card in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first communication service request;
a determining unit 802, configured to determine whether a request operation performed on the first communication service request is successfully performed;
a transfer unit 803, configured to, when a determination result of the determination unit 802 is yes, transfer the second communication service request in the second stack table to the first stack table for execution; wherein the second stack table is configured to store request operation data of the second communication service request in a mutually exclusive operation relationship with the request operation data of the first communication service request in the first stack table.
Based on the above, the present application further provides a computer storage medium for storing data generated by a network platform and a program for processing the data generated by the network platform;
when the program is read and executed by a processor, the program executes the steps in the scheduling and arranging method embodiment of the resource service operation request; or, executing the steps in the scheduling execution method embodiment of the resource service operation request as described above; or, the steps of the scheduling method embodiment of the internet of things card service request as described above are executed.
Based on the above, the present application further provides an electronic device, as shown in fig. 9, where the embodiment of the electronic device includes:
a processor 901;
a memory 902 for storing a program for processing network platform generated data, which when read and executed by the processor, executes the scheduling and arranging method of resource service operation request as described above; or, executing the scheduling execution method of the resource service operation request; or, the scheduling method of the internet of things card service request is executed.
In a typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
1. Computer-readable media, including both permanent and non-permanent, removable and non-removable media, may implement the information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), Static Random Access Memory (SRAM), Dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), Read Only Memory (ROM), Electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), Digital Versatile Disks (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. As defined herein, computer readable media does not include non-transitory computer readable media (transient media), such as modulated data signals and carrier waves.
2. As will be appreciated by one skilled in the art, embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, and the like) having computer-usable program code embodied therein.
Although the present application has been described with reference to the preferred embodiments, it is not intended to limit the present application, and those skilled in the art can make variations and modifications without departing from the spirit and scope of the present application, therefore, the scope of the present application should be determined by the claims that follow.
Claims (16)
1. A method for arranging resource service operation requests is characterized by comprising the following steps:
determining whether mutual exclusion operation information exists in operation request data carried in the resource service operation request or not according to the acquired resource service operation request;
if yes, determining whether a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request exists in a first accumulation table for storing a first resource service operation request;
And if so, storing the resource service operation request into a second accumulation table for storing a second resource service operation request.
2. The method of claim 1, further comprising:
and when the determined operation request data carried in the resource service operation request does not have mutual exclusion operation information, storing the resource service operation request into the first stack table.
3. The method of claim 1, further comprising:
when the mutually exclusive resource service operation request with the mutually exclusive operation relation with the resource service operation request does not exist in the first stack table, storing the resource service operation request into the first stack table.
4. The method for scheduling and arranging resource service operation requests according to claim 1, wherein the determining whether mutually exclusive operation information exists in operation request data carried in the resource service operation request according to the acquired resource service operation request includes:
determining whether a service providing request needs to be initiated to a service source end providing the resource service or not according to the resource service operation request;
And if so, determining whether the operation request data carried in the resource service operation request has mutual exclusion operation information.
5. The method of claim 2, further comprising:
and when the source end which needs to provide the resource service is determined whether to initiate the service providing request to the source end which provides the resource service is determined not according to the resource service operation request, processing the resource service operation request.
6. An apparatus for scheduling and scheduling resource service operation requests, comprising:
a first determining unit, configured to determine, according to an obtained resource service operation request, whether there is mutual exclusion operation information in operation request data carried in the resource service operation request;
a second determining unit, configured to determine, when a determination result of the first determining unit is yes, whether a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request exists in a first stack table used for storing the first resource service operation request;
and the storage unit is used for storing the resource service operation request into a second accumulation table used for storing a second resource service operation request when the determination result of the second determination unit is positive.
7. A method for scheduling and executing a resource service operation request is characterized by comprising the following steps:
acquiring a first resource service operation request in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first resource service operation request;
determining whether a requested operation performed on the first resource servicing operation request is successfully performed;
if so, transferring the second resource service operation request in the second stack table to the first stack table for execution; the second stack table is used for storing the request operation data of the second resource service operation request which has a mutually exclusive operation relation with the request operation data of the first resource service operation request in the first stack table.
8. The method of claim 7, wherein the determining whether the request operation performed on the first resource service operation request was successfully performed comprises:
determining whether the first resource service operation request has a configured interface to perform a request operation;
if so, initiating an execution request of the first resource service operation request according to the acquired interface authority of the interface; or, if not, initiating an execution request of the first resource service operation request;
In response to the execution request, determining whether a request operation of the first resource service operation request is successfully executed.
9. The method of claim 7, further comprising:
and updating the first resource service operation request of the first stack table when the determination is made whether the request operation performed on the first resource service operation request is successfully performed, and if not, updating the first resource service operation request of the first stack table.
10. The method of claim 7, further comprising:
writing the execution state of the first resource servicing operation request into the first stack table.
11. The method of claim 10, wherein the writing the execution status of the first resource service operation request to the first accumulation table comprises at least one of:
when the request operation of the first resource service operation request is executed based on a synchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
When the request operation of executing the first resource service operation request is successfully executed based on a synchronous execution interface, modifying the executing state in the first accumulation table into an executing successful state;
when the execution of the request operation of executing the first resource service operation request is failed based on a synchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state;
when the request operation of the first resource service operation request is executed based on an asynchronous execution interface, modifying the to-be-executed state written in the first stack table aiming at the first resource service operation request into an executing state;
when the request operation of executing the first resource service operation request is successfully executed based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an asynchronous state;
when the request operation of executing the first resource service operation request fails to execute based on an asynchronous execution interface, modifying the executing state written in the first stack table aiming at the first resource service operation request into an executing failure state.
12. The method of claim 7, wherein the transferring the second resource service operation request in the second accumulation table to the first accumulation table for execution comprises:
selecting a target resource service operation request with the earliest storage time from the second accumulation list according to the storage time;
and transferring the target resource service operation request to the first stack table for execution.
13. A device for scheduling and executing a resource service operation request, comprising:
an obtaining unit, configured to obtain a first resource service operation request in a first stack table; wherein the first accumulation table is used for storing request operation data of the first resource service operation request;
a determining unit, configured to determine whether a request operation performed on the first resource service operation request is successfully performed;
a transfer unit, configured to transfer a second resource service operation request in a second stack table to the first stack table for execution when a determination result of the determination unit is yes; the second stack table is used for storing the request operation data of the second resource service operation request which has a mutually exclusive operation relation with the request operation data of the first resource service operation request in the first stack table.
14. A method for scheduling a service request of an Internet of things card is characterized by comprising the following steps:
acquiring a first communication service request aiming at the Internet of things card in a first accumulation table; wherein the first accumulation table is used for storing request operation data of the first communication service request;
determining whether a request operation performed on the first communication service request is successfully performed;
if yes, transferring the second communication service request in the second stack table to the first stack table for execution; wherein the second stack table is configured to store request operation data of the second communication service request in a mutually exclusive operation relationship with the request operation data of the first communication service request in the first stack table.
15. A computer storage medium for storing network platform generated data and a program for processing the network platform generated data;
the program, when read and executed by a processor, performs the scheduling method of resource service operation request according to any one of claims 1 to 5; or, executing the scheduling execution method of the resource service operation request according to any one of the claims 7-12; or, the scheduling method of the internet of things card service request according to claim 14 is performed.
16. An electronic device, comprising:
a processor;
a memory for storing a program for processing data generated by a network platform, wherein the program, when read and executed by the processor, performs the scheduling and scheduling method of resource service operation request according to any one of claims 1 to 5; or, executing the scheduling execution method of the resource service operation request according to any one of the claims 7-12; or, the scheduling method of the internet of things card service request according to claim 14 is performed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210118358.9A CN114679495B (en) | 2022-02-08 | 2022-02-08 | Scheduling method and scheduling execution method for resource service operation request |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210118358.9A CN114679495B (en) | 2022-02-08 | 2022-02-08 | Scheduling method and scheduling execution method for resource service operation request |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114679495A true CN114679495A (en) | 2022-06-28 |
| CN114679495B CN114679495B (en) | 2024-01-05 |
Family
ID=82072255
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210118358.9A Active CN114679495B (en) | 2022-02-08 | 2022-02-08 | Scheduling method and scheduling execution method for resource service operation request |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114679495B (en) |
Citations (19)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6145094A (en) * | 1998-05-12 | 2000-11-07 | Sun Microsystems, Inc. | Transaction locks for high availability |
| US20030014463A1 (en) * | 2001-07-04 | 2003-01-16 | Atsushi Togawa | Task management system |
| CN101065727A (en) * | 2004-09-30 | 2007-10-31 | 茨特里克斯系统公司 | Method and apparatus for virtualizing window information |
| US20110075596A1 (en) * | 2009-09-25 | 2011-03-31 | Nokia Corporation | Resource Overbooking |
| CN102369688A (en) * | 2011-04-07 | 2012-03-07 | 华为技术有限公司 | Method for adjusting resources dynamically and scheduling device |
| CN103095759A (en) * | 2011-11-02 | 2013-05-08 | 华为技术有限公司 | Resource environment recovering method and equipment |
| US20140366036A1 (en) * | 2013-06-09 | 2014-12-11 | Apple Inc. | Class-Based Mutex |
| CN104468764A (en) * | 2014-11-29 | 2015-03-25 | 华为技术有限公司 | Method, device and system for strategy scheduling |
| CN108432208A (en) * | 2016-12-15 | 2018-08-21 | 华为技术有限公司 | A kind of arranging service method, apparatus and server |
| CN108737485A (en) * | 2017-04-25 | 2018-11-02 | 中移物联网有限公司 | For the method and system of the operation of Internet of Things resource |
| CN109040152A (en) * | 2017-06-08 | 2018-12-18 | 阿里巴巴集团控股有限公司 | A kind of service request and providing method based on service orchestration, device and electronic equipment |
| CN109298936A (en) * | 2018-09-11 | 2019-02-01 | 华为技术有限公司 | A kind of resource regulating method and device |
| CN109445950A (en) * | 2018-09-30 | 2019-03-08 | 青岛海尔科技有限公司 | The mutual exclusion access method and system of OCF resource, server-side, medium, equipment |
| CN109960591A (en) * | 2019-03-29 | 2019-07-02 | 神州数码信息系统有限公司 | A method of the cloud application resource dynamic dispatching occupied towards tenant's resource |
| CN110503432A (en) * | 2019-08-20 | 2019-11-26 | 腾讯科技（深圳）有限公司 | Processing method, device and the computer readable storage medium of resource transfers request |
| CN111131336A (en) * | 2020-03-30 | 2020-05-08 | 腾讯科技（深圳）有限公司 | Resource access method, device, equipment and storage medium under multi-party authorization scene |
| CN112181602A (en) * | 2020-10-23 | 2021-01-05 | 济南浪潮数据技术有限公司 | Resource arranging method and device, electronic equipment and storage medium |
| US10893097B1 (en) * | 2019-07-31 | 2021-01-12 | Verizon Patent And Licensing Inc. | Methods and devices for discovering and employing distributed computing resources to balance performance priorities |
| CN113282395A (en) * | 2021-06-09 | 2021-08-20 | 中国农业银行股份有限公司 | Redis-based job request scheduling method, device, equipment and medium |
-
2022
- 2022-02-08 CN CN202210118358.9A patent/CN114679495B/en active Active
Patent Citations (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6145094A (en) * | 1998-05-12 | 2000-11-07 | Sun Microsystems, Inc. | Transaction locks for high availability |
| US20030014463A1 (en) * | 2001-07-04 | 2003-01-16 | Atsushi Togawa | Task management system |
| CN101065727A (en) * | 2004-09-30 | 2007-10-31 | 茨特里克斯系统公司 | Method and apparatus for virtualizing window information |
| CN101069156A (en) * | 2004-09-30 | 2007-11-07 | 茨特里克斯系统公司 | Method and apparatus for moving processes between isolation environments |
| US20110075596A1 (en) * | 2009-09-25 | 2011-03-31 | Nokia Corporation | Resource Overbooking |
| CN102369688A (en) * | 2011-04-07 | 2012-03-07 | 华为技术有限公司 | Method for adjusting resources dynamically and scheduling device |
| CN103095759A (en) * | 2011-11-02 | 2013-05-08 | 华为技术有限公司 | Resource environment recovering method and equipment |
| US20140366036A1 (en) * | 2013-06-09 | 2014-12-11 | Apple Inc. | Class-Based Mutex |
| CN104468764A (en) * | 2014-11-29 | 2015-03-25 | 华为技术有限公司 | Method, device and system for strategy scheduling |
| US20190306256A1 (en) * | 2016-12-15 | 2019-10-03 | Huawei Technologies Co., Ltd. | Service orchestration method and apparatus, and server |
| CN108432208A (en) * | 2016-12-15 | 2018-08-21 | 华为技术有限公司 | A kind of arranging service method, apparatus and server |
| CN108737485A (en) * | 2017-04-25 | 2018-11-02 | 中移物联网有限公司 | For the method and system of the operation of Internet of Things resource |
| CN109040152A (en) * | 2017-06-08 | 2018-12-18 | 阿里巴巴集团控股有限公司 | A kind of service request and providing method based on service orchestration, device and electronic equipment |
| CN109298936A (en) * | 2018-09-11 | 2019-02-01 | 华为技术有限公司 | A kind of resource regulating method and device |
| CN109445950A (en) * | 2018-09-30 | 2019-03-08 | 青岛海尔科技有限公司 | The mutual exclusion access method and system of OCF resource, server-side, medium, equipment |
| CN109960591A (en) * | 2019-03-29 | 2019-07-02 | 神州数码信息系统有限公司 | A method of the cloud application resource dynamic dispatching occupied towards tenant's resource |
| US10893097B1 (en) * | 2019-07-31 | 2021-01-12 | Verizon Patent And Licensing Inc. | Methods and devices for discovering and employing distributed computing resources to balance performance priorities |
| CN110503432A (en) * | 2019-08-20 | 2019-11-26 | 腾讯科技（深圳）有限公司 | Processing method, device and the computer readable storage medium of resource transfers request |
| CN111131336A (en) * | 2020-03-30 | 2020-05-08 | 腾讯科技（深圳）有限公司 | Resource access method, device, equipment and storage medium under multi-party authorization scene |
| CN112181602A (en) * | 2020-10-23 | 2021-01-05 | 济南浪潮数据技术有限公司 | Resource arranging method and device, electronic equipment and storage medium |
| CN113282395A (en) * | 2021-06-09 | 2021-08-20 | 中国农业银行股份有限公司 | Redis-based job request scheduling method, device, equipment and medium |
Non-Patent Citations (1)
| Title |
|---|
| 王达恩;许光辰;王启星;: "并行处理系统中的共享资源互斥操作――锁控制技术的一种应用模型", 重庆建筑大学学报, no. 06 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114679495B (en) | 2024-01-05 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US7756888B2 (en) | Method and apparatus for providing heterogeneous resources for client systems | |
| CN107729139B (en) | Method and device for concurrently acquiring resources | |
| CN111143093B (en) | Asynchronous message distributed processing method, device, equipment and storage medium | |
| US20170093988A1 (en) | Workflow service using state transfer | |
| CN110968586A (en) | Distributed transaction processing method and device | |
| US8682954B2 (en) | Replication in a network environment | |
| JP6975153B2 (en) | Data storage service processing method and equipment | |
| CN105160018A (en) | Method, device and system for image copy/paste | |
| CN114020444B (en) | Calling system and method for resource service application in enterprise digital middle station | |
| CN114036031A (en) | Scheduling system and method for resource service application in enterprise digital middleboxes | |
| CN114679503A (en) | Market data processing method, system and equipment | |
| US10133759B1 (en) | System for determining storage or output of data objects | |
| CN114679495A (en) | Scheduling arrangement method and scheduling execution method for resource service operation request | |
| CN110968406B (en) | Method, device, storage medium and processor for processing task | |
| CN112738181B (en) | Method, device and server for cluster external IP access | |
| CN112579308A (en) | Task processing method and system | |
| CN112769928B (en) | Information interaction method and device based on service scene | |
| CN111274176B (en) | Information processing method, electronic equipment, system and storage medium | |
| CN109343928B (en) | Virtual memory file redirection method and system for virtual machine in virtualization cluster | |
| CN112596882A (en) | Method, device and system for scheduling delayed tasks | |
| CN117742998B (en) | High-performance queuing method and system for charging acquisition data forwarding | |
| CN116431367B (en) | Method, system and computer readable storage medium for modifying ticket information | |
| CN110543351A (en) | Data processing method and computer device | |
| CN111404709B (en) | Method and device for operating policy rules under network function virtualization | |
| CN117938619A (en) | Abnormal node processing method, system, computing device and storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |