CN114679495B - Scheduling method and scheduling execution method for resource service operation request - Google Patents

Scheduling method and scheduling execution method for resource service operation request Download PDF

Info

Publication number
CN114679495B
CN114679495B CN202210118358.9A CN202210118358A CN114679495B CN 114679495 B CN114679495 B CN 114679495B CN 202210118358 A CN202210118358 A CN 202210118358A CN 114679495 B CN114679495 B CN 114679495B
Authority
CN
China
Prior art keywords
request
resource service
service operation
operation request
execution
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.)
Active
Application number
CN202210118358.9A
Other languages
Chinese (zh)
Other versions
CN114679495A (en
Inventor
揭鸿
张志东
王�华
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alibaba Cloud Computing Ltd
Original Assignee
Alibaba Cloud Computing Ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Alibaba Cloud Computing Ltd filed Critical Alibaba Cloud Computing Ltd
Priority to CN202210118358.9A priority Critical patent/CN114679495B/en
Publication of CN114679495A publication Critical patent/CN114679495A/en
Application granted granted Critical
Publication of CN114679495B publication Critical patent/CN114679495B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

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 method and a scheduling execution method for resource service operation requests, wherein the scheduling method comprises the following steps: determining whether operation request data carried in the resource service operation request has mutual exclusion operation information according to the acquired resource service operation request; if yes, determining whether a mutual exclusion resource service operation request with mutual exclusion operation relation with the resource service operation request exists in a first accumulation table for storing the first resource service operation request; if yes, the resource service operation request is stored in a second accumulation table for storing a second resource service operation request, so that the problem that at least two request operation sequences with mutual exclusion operation relation 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.

Description

Scheduling method and scheduling execution method for resource service operation request
Technical Field
The application relates to the technical field of computer application, in particular to a scheduling method and a scheduling execution method for resource service operation requests. The application also relates to a scheduling execution method and device for the service request of the internet of things card, a computer storage medium and electronic equipment.
Background
With the continuous discovery of computer technology and internet technology, the internet of things has also grown under the background of the age and the technical development requirements.
Service demand characteristics in an application scenario of the internet of things generally emerge a large number of service requests when a service computing node arrives, for example: service requests at the beginning of the month or at the end of the month may increase dramatically, resulting in a service response timeout or crash of the service system.
Disclosure of Invention
The application provides a scheduling method of resource service operation requests, which aims to solve the problems of service response overtime or system breakdown caused by uneven request flow control in the prior art.
The application provides a scheduling method of resource service operation requests, which comprises the following steps:
determining whether operation request data carried in the resource service operation request has mutual exclusion operation information according to the acquired resource service operation request;
if yes, determining whether a mutual exclusion resource service operation request with mutual exclusion operation relation with the resource service operation request exists in a first accumulation table for storing the first resource service operation request;
if yes, the resource service operation request is stored in a second accumulation table for storing a second resource service operation request.
In some embodiments, further comprising:
and when the operation request data carried in the determined resource service operation request does not have mutual exclusion operation information, storing the resource service operation request into the first accumulation table.
In some embodiments, further comprising:
and 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 accumulation table, storing the resource service operation request into the first accumulation table.
In some embodiments, the determining, according to the acquired resource service operation request, whether the operation request data carried in the resource service operation request has mutual exclusion operation information includes:
determining whether a service providing request needs to be initiated to a service source end providing resource service according to the resource service operation request;
if yes, determining whether mutual exclusion operation information exists in operation request data carried in the resource service operation request.
In some embodiments, further comprising:
and when the service providing request is determined to be no to be initiated to the source end providing the resource service according to the resource service operating request, processing the resource service operating request.
The application also provides a scheduling device for resource service operation request, comprising:
the first determining unit is used for determining whether operation request data carried in the resource service operation request have mutual exclusion operation information according to the acquired resource service operation request;
the second determining unit is used for 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 accumulation table for storing the first resource service operation request according to the fact that the determination result of the first determining unit is yes;
and the storage unit is used for storing the resource service operation request into a second accumulation table for storing a second resource service operation request according to the fact that the determination result of the second determination unit is yes.
The application also provides a scheduling execution method of the resource service operation request, which comprises the following steps:
acquiring a first resource service operation request in a first accumulation table; the first accumulation table is used for storing request operation data of the first resource service operation request;
determining whether a request operation performed on the first resource service operation request is successfully performed;
If yes, transferring a second resource service operation request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second resource service operation request with mutual exclusion operation relation with request operation data of the first resource service operation request in the first stacking table.
In some embodiments, the determining whether the request operation performed on the first resource service operation request was performed successfully comprises:
determining whether the first resource service operation request has a configured interface to perform a request operation;
if yes, 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;
and responding to the execution request, and determining whether the request operation of the first resource service operation request is successfully executed.
In some embodiments, further comprising:
and updating the first resource service operation request of the first accumulation table when the request operation executed on the first resource service operation request is determined to be executed successfully or not and is not executed successfully.
In some embodiments, further comprising:
writing the execution state of the first resource service operation request into the first accumulation table.
In some embodiments, the writing the execution state of the first resource service operation request into the first heap table includes at least one of:
when the request operation of the first resource service operation request is executed based on the synchronous execution interface, modifying the to-be-executed state written in the first accumulation 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 the synchronous execution interface, modifying the executing state in the first accumulation table into an executing success state;
when the request operation of executing the first resource service operation request fails to be executed based on the synchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed 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 a to-be-executed state written in the first accumulation 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 accumulation table aiming at the first resource service operation request into an asynchronous executing state;
when the request operation of executing the first resource service operation request fails to be executed based on the asynchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed into an executing failure state.
In some embodiments, the transferring the second resource service operation request in the second heap table to the first heap table is performed, including:
selecting a target resource service operation request with earliest deposit time from the second accumulation table according to the deposit time;
and transferring the target resource service operation request to the first accumulation table for execution.
The application also provides a scheduling execution device of the resource service operation request, which comprises:
an acquiring unit, configured to acquire a first resource service operation request in a first heap table; 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, when the determination result of the determination unit is yes, a second resource service operation request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second resource service operation request with mutual exclusion operation relation with request operation data of the first resource service operation request in the first stacking table.
The application also provides a scheduling method of 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; 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 a second communication service request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second communication service request, which has a mutual exclusion operation relationship with the request operation data of the first communication service request in the first stacking table.
The application also provides 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 the processor, performs a scheduling method of resource service operation requests as described above; or, executing the scheduling execution method of the resource service operation request; or executing the scheduling method of the internet of things card service request.
The application also provides an electronic device comprising:
a processor;
a memory for storing a program for processing data generated by a network platform, which when read and executed by the processor, performs a scheduling method of resource service operation requests as described above; or, executing the scheduling execution method of the resource service operation request; or executing the scheduling method of the internet of things card service request.
Compared with the prior art, the application has the following advantages:
according to the scheduling method for the resource service operation request, whether the mutually exclusive resource service operation request is stored or not is determined by determining whether the mutually exclusive operation information exists in the resource service operation request. When the mutual exclusion operation information exists in the resource service operation request, 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 relation are disordered in the process of executing the resource service operation request is avoided, and the sequency of the mutual exclusion operation is ensured.
In addition, by preprocessing the resource service operation request, isolation of the resource service operation request with the mutex operation and the resource service operation request without the mutex operation is ensured in the scheduling process, and scheduling speed of the resource service operation request with the mutex operation is improved.
According to the scheduling execution method for the resource service operation requests, the flow control and accumulation of the resource service operation requests in the interface dimension can be realized through the configured provider interface, and the stability of processing the southbound access resource service operation requests is ensured. In the process of scheduling execution, after the processing of a first resource service operation request in a first stacking table is completed, the operation execution is carried out from a second resource service operation request stored earliest in the second stacking table to the first stacking table, so that the resource service operation request in the stacking table can be pulled regularly, and the processing speed of the resource service operation request is improved under the condition of isolating the resource service operation request operation.
Drawings
FIG. 1 is a flow chart of an embodiment of a scheduling method for resource service operation requests provided herein;
FIG. 2 is a schematic diagram of a scheduling method for scheduling resource service operation requests according to an embodiment of the present application;
FIG. 3 is a schematic structural diagram of an embodiment of a scheduling apparatus for resource service operation request provided in the present application;
FIG. 4 is a flowchart of an embodiment of a method for scheduling and executing a resource service operation request provided in the present application;
FIG. 5 is a schematic structural diagram of an embodiment of a scheduling execution device for resource service operation request provided in the present application;
fig. 6 is a flowchart of an embodiment of a scheduling method for an internet of things card service request provided in the present application;
fig. 7 is a schematic diagram of a scheduling architecture of an embodiment of a scheduling method for service requests of an internet of things card provided in the present application;
fig. 8 is a schematic structural diagram of an embodiment of a scheduling execution device for an internet of things card service request provided in 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, however, susceptible of embodiment in many other ways than those herein described and similar generalizations can be made by those skilled in the art without departing from the spirit of the application and the application is therefore not limited to the specific embodiments disclosed below.
The terminology used in the present application is for the purpose of describing particular embodiments only and is not intended to be limiting of the present application. The manner of description used in this application and in the appended claims is for example: "a", "a" and "a" etc. are not limited in number or order, but are used to distinguish the same type of information from each other.
In view of the above background art, the internet of things may present a large number of service requests when the service computing node arrives, so as to cause problems such as service response timeout or system crash of the service system. The inventive concept of the present application is also based on the above technical problems. The application scenario involved may include: intelligent sound box, intelligent house, agricultural equipment, intelligent media screen, shared treasured that charges etc.. The function realization under each scene of the internet of things is to realize the communication function of data by installing an internet of things card on the access equipment, and the internet of things card is connected with a wireless network through interfaces by SIM cards, sensors, two-dimension codes and the like which are installed on various objects, so that the communication and conversation between people and objects and between objects can be realized. The internet of things is understood to mean a network that connects 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 the internet of things, such as the internet of vehicles, charging piles, vending machines, security protection and the like. In this embodiment, a description will be given of how to solve the problem of service response timeout or system crash caused by the uneven request flow control by using the internet of things card 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 capacities among the suppliers may be quite different. In the face of limited provider capacity and large-batch incoming service requests, scheduling and decision-making of resources need to be realized, and stability of a supply chain system is ensured, so that efficient, high-quality and high-reliability communication service is provided. The following describes in detail a scheduling method of resource service operation requests provided in the present application.
As shown in fig. 1 and fig. 2, fig. 1 is a flowchart of an embodiment of a scheduling method for resource service operation requests provided in the present application, and fig. 2 is a schematic structural diagram of scheduling in an embodiment of a scheduling method for resource service operation requests provided in the present application, where the embodiment may include:
step S101: and determining whether operation request data carried in the resource service operation request has mutual exclusion operation information 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, a sales service, a package renewal service, a unbinding/binding service, a stop/reset service, etc. Mutual exclusion operation information may be understood as an operation that is the opposite or irrelevant in operation of the requesting service, such as: and stopping and resetting.
The purpose of step S101 is to determine whether mutual exclusion operation information exists in the resource service operation request.
In this embodiment, in the step S101, it is determined whether the operation request data carried in the resource service operation request has mutual exclusion operation information, and whether the operation request data has mutual exclusion operation information may be determined by identifying field information in the operation request data, for example: and identifying a field of the operation request data, and determining whether the operation information described by the field has mutually exclusive operation information.
In this embodiment, the specific implementation procedure of step S101 may include:
step S101-1: determining whether a service providing request needs to be initiated to a service source end providing resource service according to the resource service operation request; in this embodiment, the service source may be understood as a provider service end that provides a resource service, 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: if yes, determining whether mutual exclusion operation information exists in operation request data carried in the resource service operation request.
If the result of the determination in step S101-1 is negative, the resource service operation request is scheduled to the execution processing side. In this embodiment, when the determination result is no, the resource service operation request is scheduled to the service platform of the internet of things card for processing, and of course, the resource service operation request may also be scheduled to the execution processing side of the service source end for executing 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. And when the request is yes, the fact that the mutual exclusion operation possibly exists in the resource service operation request is indicated, when the request is no, the fact that the mutual exclusion operation does not exist in the resource service operation request is indicated, and related request operation can be directly completed through the Internet of things card service platform without being completed through a service source terminal.
The purpose of the step S101-2 is to determine whether mutual exclusion operation information exists in the resource service operation request, for example: identifying an operation field by identifying operation request data in the resource service operation request, and determining whether mutual exclusion operation information exists according to the identified operation field, for example: the identified operation field is shutdown, and the operation mutually exclusive with shutdown is multiplex, so that the mutual exclusion 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 so, 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 accumulation table for storing the first resource service operation request.
The purpose of step S102 is to determine whether there is a request for mutex resource service operation in the first heap table.
In this embodiment, the step S102 is based on the determination result in the step S101 being yes, determining 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 heap table, where the first heap table is used for storing the first resource service operation request. In this embodiment, the determination result in the 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 no subsequent operation may be performed during the abnormality, and information such as an abnormality prompt or an alarm may be output. In this embodiment, the determination result is mainly described in both yes and no modes. For example: if the service request of the multiplex exists in the first accumulation table, the service request of the multiplex in the first accumulation table and the service request of the package expiration stop can be determined, and the service request of the mutex resource serving in a mutex operation relation is the mutex resource serving request, namely the service request of the multiplex is the mutex resource serving request.
The step S102 is based on the subsequent scheduling operation performed in the step S101-2 when the mutual exclusion operation information exists in the resource service operation request. If the service request of the package change exists in the first stacking table, it can be determined that the service request of the package change in the first stacking table and the service request of the package expiration stop have no mutual exclusive operation relationship, i.e. the mutual exclusive resource service operation request does not exist in the first stacking table.
In the step S101-2, when the mutual exclusion operation information does not exist in the resource service operation request, that is, when the field having the mutual exclusion operation relationship is not identified, it is indicated that the mutual exclusion operation information does not exist in the resource service operation request, and at this time, the resource service operation request may be stored in the first stacking table, so as to implement scheduling arrangement of the resource service operation request.
Step S103: if yes, the resource service operation request is stored in 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 based on the yes determination of step S102.
In this embodiment, when the determination result of step S102 is yes, the resource service operation request is stored in the second stacking table, that is, when the first stacking table stores therein 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 stacking table, so as to avoid at least two resource service operation requests having a mutually exclusive operation relationship in the first stacking table, and ensure the sequency of the mutually exclusive operation when the resource service operation request is executed. The storage mode of the resource service operation requests stored in the second stacking table may be sorting according to storage time or storing according to a queue mode, so that first-in first-out can be realized when the subsequent scheduling is executed.
In this embodiment, when the determination result of the step S102 is no, that is, when the mutually exclusive resource service operation request with respect to the resource service operation request does not exist in the first heap table, the resource service operation request is stored in the first heap table.
The above is a description of an embodiment of a scheduling method for resource service operation requests, where the scheduling method embodiment determines whether to determine whether to store a mutex resource service operation request in a first stacking table by determining whether to have mutex operation information in the resource service operation request, and stores the resource service operation request in a second stacking table when the mutex operation information is stored in the resource service operation request and the mutex resource service operation request is stored in the first stacking table, so as to avoid a problem that at least two request operation orders with mutex operation relationships are disordered in the process of executing the resource service operation request, and ensure the sequency of the mutex operation.
In addition, by preprocessing the resource service operation request, isolation of the resource service operation request with the mutex operation and the resource service operation request without the mutex operation is ensured in the scheduling process, and scheduling speed of the resource service operation request with the mutex operation is improved.
The foregoing is a specific description of an embodiment of a scheduling method for resource service operation requests, corresponding to the foregoing embodiment of a scheduling method for resource service operation requests, and the application further discloses an embodiment of a scheduling apparatus for resource service operation requests, please refer to fig. 3, and since the apparatus embodiment is substantially similar to the method embodiment, the description is relatively simple, and the relevant matters refer to part of the description of the method embodiment. 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 apparatus for resource service operation request provided in the present application, where the scheduling embodiment may include: a first determining unit 301, a second determining unit 302 and a storing unit 303.
The first determining unit 301 is configured to determine, according to the obtained resource service operation request, whether operation request data carried in the resource service operation request has mutual exclusion operation information.
The second determining unit 302 is configured to determine, according to yes result of the determination by the first determining unit, whether a mutually exclusive resource service operation request having a mutually exclusive operation relationship with the resource service operation request exists in a first stacking table for storing a first resource service operation request.
The storage unit 303 is configured to store the resource service operation request in a second heap table that is used to store a second resource service operation request, when the determination result of the second determination 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, when the determination result of the request initiation determining subunit is yes, whether operation request data carried in the resource service operation request has mutual exclusion operation information. And when the determination result of the request initiation determination subunit is no, the first determination unit is specifically configured to schedule the resource service operation request to an execution processing side.
In this embodiment, the storage unit 303 may be further configured to store the resource service operation request in the first heap table when the determination result of the first determination unit 301 is no.
In this embodiment, the storage unit 303 may be further configured to store the resource service operation request in the first heap table when the determination result of the second determination unit 302 is no.
The foregoing is a description of an embodiment of a scheduling apparatus for resource service operation request provided in the present application, and specific content of the embodiment of the scheduling apparatus may refer to content of the embodiment of the scheduling method, which is not repeated herein.
Based on the foregoing, 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 a method for scheduling and executing a resource service operation request, 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; the first accumulation table is used for storing request operation data of the first resource service operation request.
In this embodiment, the purpose of step S401 is to obtain a first resource service operation request. The first resource service operation request is obtained from the first heap table. The first resource service operation request and the first heap table may refer to the description of step S101 described above.
Step S402: determining whether a request operation performed on the first resource service operation request was successfully performed.
The purpose of step S402 is to determine whether the request operation of the first resource service operation request is successfully executed, which may specifically include:
step S402-1: determining whether the first resource service operation request has a configured interface to perform a request operation; an 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 specific interface (may also be referred to as resource) configuration may be that a configuration code corresponding to an operation is generated through information such as serviceVersion, serviceversion_operation (service version_operation information), supplierId_account (vendor ID_account number), supplierId_account_operation (vendor ID_account_operation information), and the like, where the configuration code is used to characterize the interface; where accounts are the accounts of the suppliers, avoiding that the account name may be duplicated, here with a supplerid (vendor ID) appended. The implementation of the configuration code may be, for example: the requested service version is CUCC_SELF_V1, the business operation is IOT_ASSETS_ACTIVE, the card account is 166WLW014184, the vendor is Qingdao Unicom (ID: 1619674952767000), then the configuration code generated is as follows:
CUCC_SELF_V1; - - (means chinese communication version V1);
CUCC_SELF_V1_IOT_ASSETS_ACTIVE; - - (internet of things card activation representing chinese communication version V1);
1619674952767000_166wlw014184; - - (14184 account number representing vendor);
1619674952767000_166wlw014184_iot_assets_active; - - (internet of things card activation of 14184 account number representing vendor);
the specific implementation process of step S402-1 may be searching for a configuration code matching the first resource service request in a database, and obtaining the interface according to the found configuration code. The database may store a configuration encoding table. For example:
assume that returning a eligible Id list is: 4,1,3. The configuration code is first looked up using id=4, if present, return immediately, otherwise look up with id=1, if not present, continue looking up with id=3, if not present, indicate that the request is unrestricted, and access is possible.
In the resource lookup, a plurality of resource configurations are allowed to be returned, wherein resource_config is a resource configuration table, and resource_lookup_config is a resource configuration lookup table. The account number resource configuration under the same provider is basically the same, and the name_pattern of the resource configuration table supports placeholders. For example: resource configuration obtained by 1619674952767000_166wlw014184_iot_assets_active (vendor Id1619674952767000, account number 166WLW014184, internet of things card activation request):
name_pattern (resource name format) Permission (license)
API_CUCC_SELF_V1_ACTIVE_{SupplierId}_{Account} 40
Instantiating a resource according to the resource configuration, and generating a resource name according to an API_CUCC_SELF_V1_ACTIVE_ { supplerid } _ { Account } format, namely: api_cucc_self_v1_active_1619674952767000_166wlw014184; thereby determining an interface of the first resource service operation request configuration to perform a request operation.
Step S402-2: when the determination result of the step S402-1 is yes, initiating an execution request of the first resource service operation request according to the acquired interface authority of the interface; when it is determined that the first resource service operation request has an interface (resource) configured to perform the request operation according to the step S402-1, the interface authority of the interface, that is, the license as in the example in the step S402-1 is acquired. The specific implementation process of step S402-2 may be that, after the interface authority is obtained, an execution request is initiated to the vendor. Or, when the result of the determination in step S402-1 is no, an execution request of the first resource service operation request is initiated, that is, an execution request is initiated to a provider.
Step S402-3: and responding to the execution request, and determining whether the request operation of the first resource service operation request is successfully executed.
Step S403: if yes, transferring a second resource service operation request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second resource service operation request with mutual exclusion operation relation with request operation data of the first resource service operation request in the first stacking table.
The purpose of the step S403 is to: and (3) transferring the request information in the second stacking table to the first stacking table when the determination result of the step S402-3 is yes.
The specific implementation process of step S403 may include:
step S403-1: selecting a target resource service operation request with earliest deposit time from the second accumulation table according to the deposit time;
step S403-2: and transferring the target resource service operation request to the first accumulation table for execution.
In order to avoid the problem of repeated scheduling of the resource service operation request, the embodiment further needs to record the execution state for the resource service operation request, which specifically may include:
writing the execution state of the first resource service operation request into the first accumulation table.
The execution state for writing in the first heap table may include at least one of:
When the request operation of the first resource service operation request is executed based on the synchronous execution interface, modifying the to-be-executed state written in the first accumulation 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 the synchronous execution interface, modifying the executing state in the first accumulation table into an executing success state;
when the request operation of executing the first resource service operation request fails to be executed based on the synchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed 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 a to-be-executed state written in the first accumulation 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 accumulation table aiming at the first resource service operation request into an asynchronous executing state;
When the request operation of executing the first resource service operation request fails to be executed based on the asynchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed 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 heap table is updated. In this embodiment, in response to the execution request, the execution failure and/or success of the request operation of the first resource service operation request may be recorded. When the execution of the first resource service operation request in the first heap table fails, the execution may return to step S401 to continue, that is, perform scheduling execution processing on the next resource service operation request.
According to the scheduling execution method embodiment of the resource service operation request, the flow control and accumulation of the resource service operation request in the interface dimension can be realized through the configured provider interface, and the stability of processing the south access resource service operation request is ensured. In the process of scheduling execution, after the processing of a first resource service operation request in a first stacking table is completed, the operation execution is carried out from a second resource service operation request stored earliest in the second stacking table to the first stacking table, so that the resource service operation request in the stacking table can be pulled regularly, and the processing speed of the resource service operation request is improved under the condition of isolating the resource service operation request operation.
The foregoing is a specific description of an embodiment of a method for scheduling and executing a resource service operation request, which corresponds to the foregoing embodiment of the method for scheduling and executing a resource service operation request, and the application further discloses an embodiment of a device for scheduling and executing a resource service operation request, please refer to fig. 5, and since the device embodiment is substantially similar to the method embodiment, the description is relatively simple, and the relevant points refer to 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 device for 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 heap table; the first accumulation table is used for storing request operation data of the first resource service operation request. The specific implementation process of the obtaining unit 501 may refer to the step S401, and a detailed description is not repeated here.
A determining unit 502, configured to determine whether a request operation performed on the first resource service operation request is successfully performed. In this embodiment, the determining unit 502 may include: the system comprises 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 a request operation; an 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 service request is searched in the database, the interface is obtained according to the searched configuration code, and the related content can refer to the description of the step S402-1.
The request initiating subunit is configured to initiate an execution request of the first resource service operation request according to the acquired interface authority of the interface when the determination result of the configuration determining subunit is yes; or, when the determination result of the configuration determination subunit is no, initiating an execution request of the first resource service operation request, that is, initiating an execution request to a provider.
The execution determining subunit is configured to determine, in response to the execution request, whether a request operation of the first resource service operation request is successfully executed.
A transferring unit 503, configured to transfer, when the determination result of the determining unit is yes, the second resource service operation request in the second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second resource service operation request with mutual exclusion operation relation with request operation data of the first resource service operation request in the first stacking 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 stacking table according to the storing time.
The transferring subunit is configured to transfer the target resource service operation request to the first heap table for execution.
In order to avoid the problem of repeated scheduling of the resource service operation request, the embodiment further needs to record the execution state for the resource service operation request, which specifically may include: and the state writing unit is used for writing the execution state of the first resource service operation request into the first accumulation table. The execution state of the specific writing by the state writing unit may include at least one of the following:
when the request operation of the first resource service operation request is executed based on the synchronous execution interface, modifying the to-be-executed state written in the first accumulation 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 the synchronous execution interface, modifying the executing state in the first accumulation table into an executing success state;
When the request operation of executing the first resource service operation request fails to be executed based on the synchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed 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 a to-be-executed state written in the first accumulation 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 accumulation table aiming at the first resource service operation request into an asynchronous executing state;
when the request operation of executing the first resource service operation request fails to be executed based on the asynchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed 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 accumulation table when the determination result of the execution determination subunit is NO, namely, the execution fails.
The foregoing is a description of an embodiment of a scheduling execution device for a resource service operation request provided in the present application, and specific content of the embodiment of the scheduling execution device may refer to content of the embodiment of the scheduling execution method, and corresponding content is not described repeatedly herein.
Based on the foregoing, the present application further provides a scheduling method of an internet of things card service request, as shown in fig. 6, fig. 6 is a flowchart of an embodiment of a scheduling method of an internet of things card service request provided in the present application, where the embodiment of the scheduling method may include:
step S601: acquiring a first communication service request aiming at the internet of things card in a first accumulation table; the first accumulation table is used for storing request operation data of the first communication service request.
Step S602: a determination is made as to whether a request operation performed on the first communication service request was performed successfully.
Step S603: if yes, transferring a second communication service request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second communication service request, which has a mutual exclusion operation relationship with the request operation data of the first communication service request in the first stacking table.
In this embodiment, the internet of things card is a 2/3/4G card provided by a mobile, telecom and Unicom operator, the appearance of the consumer-level card is basically the same as that of a common SIM card, and a special number segment is adopted to meet the requirements of intelligent hardware and internet of things industry on equipment networking.
In this embodiment, as shown in fig. 7, the received communication service requests are scheduled according to a mutual exclusion operation relationship, that is, stacked in a first stacking table or a second stacking table, where the first stacking table and the second stacking 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 stacking table as the to-be-processed communication service request. And when the first communication service request is successfully executed, recording an execution state, and transferring the second communication service request stored earliest in the second accumulation table into the first accumulation table as the communication service request to be processed, and waiting for the dispatching platform to dispatch and execute. Scheduling execution may initiate an execution request to the provider according to the determined interface.
For the specific content of the above steps S601 to S603, reference may be made to the content of the above steps S101 to S103 and the content of the above steps S401 to S403, and the detailed description will not be repeated here.
According to the scheduling method embodiment of the Internet of things card service request, the processing capacity of the provider is utilized to the maximum extent through the configuration interface, and when backlog occurs in the request, operation request data are stored in the first stacking table or the second stacking table according to the mutually exclusive operation relation, so that isolation between execution tasks is realized for the service request, and the same service request is prevented from being repeatedly scheduled.
Based on the foregoing, the application further provides a scheduling device for a service request of an internet of things card, as shown in fig. 8, where an embodiment of the scheduling device includes:
an obtaining unit 801, configured to obtain a first communication service request for an internet of things card in a first stacking table; 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 transferring unit 803 for transferring the second communication service request in the second heap table to the first heap table for execution when the determination result of the determining unit 802 is yes; the second stacking table is used for storing request operation data of the second communication service request, which has a mutual exclusion operation relationship with the request operation data of the first communication service request in the first stacking table.
Based on the foregoing, the present application further provides a computer storage medium for storing network platform generated data and a program for processing the network platform generated data;
the program, when read by a processor for execution, performs the steps in the scheduling method embodiment of the resource service operation request as described above; or, executing the steps in the scheduling execution method embodiment of the resource service operation request described above; or, executing the steps of the scheduling method embodiment of the internet of things card service request.
Based on the foregoing, the application further provides an electronic device, as shown in fig. 9, where an 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, performs the scheduling method of resource service operation request as described above; or, a scheduling execution method of executing the resource service operation request as described above; or executing the scheduling method of the internet of things card service request.
In one typical configuration, a computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include volatile memory in a computer-readable medium, random Access Memory (RAM) and/or nonvolatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.
1. Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement 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 storage media for a computer 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 Discs (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. Computer readable media, as defined herein, does not include non-transitory computer readable media (transmission media), such as modulated data signals and carrier waves.
2. It will be appreciated by those skilled in the art that 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.
While the preferred embodiment has been described, it is not intended to limit the invention thereto, and any person skilled in the art may make variations and modifications without departing from the spirit and scope of the present invention, so that the scope of the present invention shall be defined by the claims of the present application.

Claims (16)

1. A method for orchestrating resource service operation requests, comprising:
determining whether operation request data carried in the resource service operation request has mutual exclusion operation information according to the acquired resource service operation request;
if yes, determining whether a mutual exclusion resource service operation request with mutual exclusion operation relation with the resource service operation request exists in a first accumulation table for storing the first resource service operation request;
If yes, the resource service operation request is stored in a second accumulation table for storing a second resource service operation request.
2. The scheduling method of resource service operation requests according to claim 1, further comprising:
and when the operation request data carried in the determined resource service operation request does not have mutual exclusion operation information, storing the resource service operation request into the first accumulation table.
3. The scheduling method of resource service operation requests according to claim 1, further comprising:
and 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 accumulation table, storing the resource service operation request into the first accumulation table.
4. The scheduling method of resource service operation requests according to claim 1, wherein the determining whether the operation request data carried in the resource service operation request has mutual exclusion operation information 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 resource service according to the resource service operation request;
If yes, determining whether mutual exclusion operation information exists in operation request data carried in the resource service operation request.
5. The scheduling method of resource service operation requests according to claim 2, further comprising:
and when the service providing request is determined to be no to be initiated to the source end providing the resource service according to the resource service operating request, processing the resource service operating request.
6. A scheduling apparatus for resource service operation requests, comprising:
the first determining unit is used for determining whether operation request data carried in the resource service operation request have mutual exclusion operation information according to the acquired resource service operation request;
the second determining unit is used for 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 accumulation table for storing the first resource service operation request according to the fact that the determination result of the first determining unit is yes;
and the storage unit is used for storing the resource service operation request into a second accumulation table for storing a second resource service operation request according to the fact that the determination result of the second determination unit is yes.
7. A scheduling execution method for a resource service operation request, comprising:
acquiring a first resource service operation request in a first accumulation table; the first accumulation table is used for storing request operation data of the first resource service operation request;
determining whether a request operation performed on the first resource service operation request is successfully performed;
if yes, transferring a second resource service operation request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second resource service operation request with mutual exclusion operation relation with request operation data of the first resource service operation request in the first stacking table.
8. The method of claim 7, wherein 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 yes, 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;
And responding to the execution request, and determining whether the request operation of the first resource service operation request is successfully executed.
9. The scheduling execution method of resource service operation request according to claim 7, further comprising:
and updating the first resource service operation request of the first accumulation table when the request operation executed on the first resource service operation request is determined to be executed successfully or not and is not executed successfully.
10. The scheduling execution method of resource service operation request according to claim 7, further comprising:
writing the execution state of the first resource service operation request into the first accumulation table.
11. The method of claim 10, wherein writing the execution state of the first resource service operation request into the first heap table includes at least one of:
when the request operation of the first resource service operation request is executed based on the synchronous execution interface, modifying the to-be-executed state written in the first accumulation 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 the synchronous execution interface, modifying the executing state in the first accumulation table into an executing success state;
when the request operation of executing the first resource service operation request fails to be executed based on the synchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed 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 a to-be-executed state written in the first accumulation 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 accumulation table aiming at the first resource service operation request into an asynchronous executing state;
when the request operation of executing the first resource service operation request fails to be executed based on the asynchronous execution interface, the executing state written in the first accumulation table aiming at the first resource service operation request is changed into an executing failure state.
12. The method for scheduling execution of resource service operation requests according to claim 7, wherein transferring the second resource service operation request in the second heap table to the first heap table is performed, comprising:
selecting a target resource service operation request with earliest deposit time from the second accumulation table according to the deposit time;
and transferring the target resource service operation request to the first accumulation table for execution.
13. A scheduling execution apparatus for a resource service operation request, comprising:
an acquiring unit, configured to acquire a first resource service operation request in a first heap table; 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, when the determination result of the determination unit is yes, a second resource service operation request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second resource service operation request with mutual exclusion operation relation with request operation data of the first resource service operation request in the first stacking table.
14. The scheduling method of the service request of the internet of things card is characterized by comprising the following steps of:
acquiring a first communication service request aiming at the internet of things card in a first accumulation table; 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 a second communication service request in a second stacking table to the first stacking table for execution; the second stacking table is used for storing request operation data of the second communication service request, which has a mutual exclusion operation relationship with the request operation data of the first communication service request in the first stacking 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 a scheduling method of resource service operation requests according to any of the preceding claims 1-5; or, executing the scheduling execution method of the resource service operation request according to any one of the preceding claims 7-12; or, executing the scheduling method of the internet of things card service request according to the above claim 14.
16. An electronic device, comprising:
a processor;
a memory for storing a program for processing network platform generated data, which program, when read and executed by the processor, performs the scheduling method of resource service operation requests according to any one of the preceding claims 1-5; or, executing the scheduling execution method of the resource service operation request according to any one of the preceding claims 7-12; or, executing the scheduling method of the internet of things card service request according to the above claim 14.
CN202210118358.9A 2022-02-08 2022-02-08 Scheduling method and scheduling execution method for resource service operation request Active CN114679495B (en)

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 CN114679495A (en) 2022-06-28
CN114679495B true 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 (16)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6145094A (en) * 1998-05-12 2000-11-07 Sun Microsystems, Inc. Transaction locks for high availability
CN101065727A (en) * 2004-09-30 2007-10-31 茨特里克斯系统公司 Method and apparatus for virtualizing window information
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
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

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US7302686B2 (en) * 2001-07-04 2007-11-27 Sony Corporation Task management system
US20110075596A1 (en) * 2009-09-25 2011-03-31 Nokia Corporation Resource Overbooking
US9176792B2 (en) * 2013-06-09 2015-11-03 Apple Inc. Class-based mutex

Patent Citations (17)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6145094A (en) * 1998-05-12 2000-11-07 Sun Microsystems, Inc. Transaction locks for high availability
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
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
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
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)

* Cited by examiner, † Cited by third party
Title
并行处理系统中的共享资源互斥操作――锁控制技术的一种应用模型;王达恩;许光辰;王启星;;重庆建筑大学学报(第06期);全文 *

Also Published As

Publication number Publication date
CN114679495A (en) 2022-06-28

Similar Documents

Publication Publication Date Title
US11146502B2 (en) Method and apparatus for allocating resource
CN107729139B (en) Method and device for concurrently acquiring resources
CA3000422C (en) Workflow service using state transfer
CN107241281B (en) Data processing method and device
US20090012963A1 (en) Method and apparatus for providing heterogeneous resources for client systems
CN111143093B (en) Asynchronous message distributed processing method, device, equipment and storage medium
CN111399764B (en) Data storage method, data reading device, data storage equipment and data storage medium
CN110457142B (en) Service processing method, system, machine room, architecture and electronic equipment
CN109639598A (en) Request processing method, server, storage medium and device based on micro services
CN110764930B (en) Request or response processing method and device based on message mode
CN105243001A (en) Abnormal alarm method and apparatus for business object
CN114265713B (en) RDMA event management method, RDMA event management device, RDMA event management computer equipment and storage medium
CN111294377B (en) Dependency network request sending method, terminal device and storage medium
CN107147610B (en) Resource processing method and device
CN114036031A (en) Scheduling system and method for resource service application in enterprise digital middleboxes
CN114679495B (en) Scheduling method and scheduling execution method for resource service operation request
US10133759B1 (en) System for determining storage or output of data objects
CN110968406B (en) Method, device, storage medium and processor for processing task
CN112738181B (en) Method, device and server for cluster external IP access
CN115220887A (en) Processing method of scheduling information, task processing system, processor and electronic equipment
US8904369B2 (en) Method and system for automated process distribution
CN116095074A (en) Resource allocation method, device, related equipment and storage medium
CN111061888B (en) Image acquisition method and system
CN111404709B (en) Method and device for operating policy rules under network function virtualization
CN113900776A (en) Task scheduling method and service system

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