WO2022095022A1 - 计算资源的调度方法、装置、计算机设备及存储介质 - Google Patents

计算资源的调度方法、装置、计算机设备及存储介质 Download PDF

Info

Publication number
WO2022095022A1
WO2022095022A1 PCT/CN2020/127496 CN2020127496W WO2022095022A1 WO 2022095022 A1 WO2022095022 A1 WO 2022095022A1 CN 2020127496 W CN2020127496 W CN 2020127496W WO 2022095022 A1 WO2022095022 A1 WO 2022095022A1
Authority
WO
WIPO (PCT)
Prior art keywords
service provider
cloud service
blueprint
resource
blockchain
Prior art date
Application number
PCT/CN2020/127496
Other languages
English (en)
French (fr)
Inventor
张晨
庄丽婉
潘凤薇
金韬
黄韬
Original Assignee
网络通信与安全紫金山实验室
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 网络通信与安全紫金山实验室 filed Critical 网络通信与安全紫金山实验室
Publication of WO2022095022A1 publication Critical patent/WO2022095022A1/zh

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F9/00—Arrangements for program control, e.g. control units
    • G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
    • G06F9/46—Multiprogramming arrangements
    • G06F9/50—Allocation of resources, e.g. of the central processing unit [CPU]
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/64—Protecting data integrity, e.g. using checksums, certificates or signatures

Definitions

  • the present application relates to the field of cloud computing, and in particular, to a method, apparatus, computer equipment and storage medium for scheduling computing resources.
  • cloud-edge collaboration technology With the continuous development of cloud computing and the rapid growth of edge applications, cloud-edge collaboration technology has become a new research and development hotspot. Among them, the cloud-edge collaboration platform not only realizes the full utilization of idle computing resources, but also saves the resource use cost of the resource demander. Users can dynamically and conveniently deploy applications or computing tasks on the resource devices of cloud service providers through cloud-edge collaboration technology, so that compared with traditional cloud services, it can achieve second-level scheduling, dynamically and flexibly shrink and expand available resources. computing resources.
  • Various exemplary embodiments of the present application provide a computing resource scheduling method, apparatus, computer device, and storage medium.
  • a method for scheduling computing resources includes a configuration database, a metering information database, and a blockchain access controller.
  • the method includes: accessing the controller through the blockchain. Upload the successfully executed historical scheduling instructions stored in the configuration database to the blockchain platform; send the verified first historical metering information stored in the metering information database to the blockchain access control and verifying and comparing the first historical metering information on the blockchain access controller with the second historical metering information stored on the blockchain platform.
  • the successfully executed historical scheduling instructions are periodically sent to the blockchain platform through the blockchain access controller.
  • the first historical metering information is quantitatively sent to the blockchain access controller through the blockchain access controller.
  • the cloud-edge collaboration platform further includes a metering monitoring module, and the method further includes: monitoring metering operations through the monitoring and metering module to acquire metering information, and periodically sending the acquired metering information to in the metering information database to form the first historical metering information.
  • the method further includes: determining the matching deployment resource blueprint of the user terminal and the available resource blueprint of the cloud service provider terminal; according to the matching deployment resource blueprint and the available resource blueprint, generating a scheduling instruction, and executing the scheduling instruction to perform resource scheduling; and storing the scheduling instruction in the configuration database.
  • the step of determining a deployment resource blueprint and a provisionable resource blueprint that match each other includes: according to the deployment resource blueprint sent by the user terminal, determining a provisionable resource blueprint that matches the deployment resource blueprint. resource blueprint, and store the deployment resource blueprint sent by the user terminal in the configuration database; or determine that it matches the available resource blueprint according to the available resource blueprint sent by the cloud service provider terminal and store the available resource blueprint sent by the cloud service provider terminal in the configuration database.
  • the cloud-side collaboration platform further includes a default record database
  • the method further includes: during the resource scheduling, the cloud service provider terminal, the user terminal or the cloud service provider platform
  • the breach of contract information corresponding to the breach of contract is stored in the breach record database; the step of determining the matched deployment resource blueprint of the user terminal and the available resource blueprint of the cloud service provider terminal , including: when the default information of the cloud service provider terminal is greater than a first threshold, lowering the matching priority of the cloud service provider terminal; and/or when the default information of the user terminal is greater than a second threshold , lower the matching priority of the user terminal.
  • the method further includes: receiving the available resource blueprint sent by the cloud service provider terminal, and verifying the legitimacy of the available resource blueprint.
  • the step of receiving the available resource blueprint sent by the cloud service provider terminal, and verifying the legitimacy of the available resource blueprint includes: receiving a blueprint sent by the cloud service provider terminal.
  • a cloud service provider signing request, the cloud service provider signing request includes the available resource blueprint; verify the legality of the available resource blueprint, and return the validity verification result to the cloud service provider terminal; If the blueprint of the available resources is legal, then the access controller of the blockchain will monitor whether the blueprint of the available resources is uploaded to the blockchain platform by the cloud service provider terminal, and at the same time, the cloud service will be received from the cloud service provider.
  • the available resource blueprint sent by the business terminal is used to execute the resource scheduling; if it is monitored that the available resource blueprint is linked to the blockchain platform, the cloud service provider signing request is terminated.
  • the method further includes: receiving the deployment resource blueprint sent by the user terminal, and verifying the legitimacy of the deployment resource blueprint.
  • the step of receiving the deployment resource blueprint sent by the user terminal and verifying the legitimacy of the deployment resource blueprint includes: receiving a user subscription request sent by the user terminal, the The user signing request includes the deployment resource blueprint; verify the legality of the deployment resource blueprint, and return the legality verification result to the user terminal; if the deployment resource blueprint is legal, pass the blockchain
  • the access controller monitors whether the deployment resource blueprint is uploaded to the blockchain platform by the user terminal and simultaneously receives the deployment resource blueprint sent by the user terminal to execute the resource scheduling; if monitored After the deployment resource blueprint is uploaded to the blockchain platform, the user signing request is terminated.
  • the method further includes: receiving metering information corresponding to the resource scheduling sent by the cloud service provider terminal, and verifying whether the metering information is legal.
  • the step of receiving the metering information corresponding to the resource scheduling sent by the cloud service provider terminal, and verifying whether the metering information is legal includes: receiving the measurement information sent by the cloud service provider terminal.
  • the resource view includes the metering information; verify the legality of the metering information, and return the verification result of the legality to the cloud service provider terminal, if the metering information is legal, pass
  • the blockchain access controller monitors whether the metering information is uploaded to the blockchain platform.
  • the method further includes: when acquiring a user settlement request, generating user billing information according to the metering information; sending the user billing information to the user terminal; If the user transfer transaction corresponding to the user billing information is sent, the user settlement information corresponding to the user transfer transaction is broadcast to the blockchain platform through the blockchain access controller, and the user settlement request is ended. .
  • the method further includes: when acquiring a cloud service provider settlement request, generating cloud service provider billing information according to the metering information; sending the cloud service provider billing information to the cloud service provider terminal; If the confirmation information corresponding to the cloud service provider's billing information sent by the cloud service provider terminal is received, execute the cloud service provider transfer transaction corresponding to the cloud service provider's billing information; access the controller through the blockchain Monitor whether the cloud service provider settlement information corresponding to the cloud service provider's transfer transaction is linked to the blockchain platform, and if it is monitored that the cloud service provider settlement information is linked to the blockchain platform, the process ends.
  • Cloud service provider settlement request when acquiring a cloud service provider settlement request, generating cloud service provider billing information according to the metering information; sending the cloud service provider billing information to the cloud service provider terminal; If the confirmation information corresponding to the cloud service provider's billing information sent by the cloud service provider terminal is received, execute the cloud service provider transfer transaction corresponding to the cloud service provider's billing information; access the controller through the blockchain Monitor whether the cloud service provider settlement information corresponding to the
  • a computing resource scheduling device which is set in a cloud-edge collaboration platform, and the device includes: a configuration database for storing legal historical deployment resource blueprints, legal historically available resource blueprints and Successfully executed historical scheduling instructions; a metering information database for storing verified historical metering information; and a blockchain access controller for executing the interaction between the cloud-edge collaboration platform and the blockchain platform.
  • a computer device including a memory and a processor, wherein the memory stores a computer program, and the processor implements the steps of the methods of the foregoing embodiments when the processor executes the computer program.
  • Yet another aspect of the present application provides a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, implements the steps of the methods of the foregoing embodiments.
  • the above-mentioned scheduling method, device, computer equipment and storage medium for computing resources realize the interaction between the cloud-side collaboration platform and the blockchain platform by setting the blockchain access controller in the cloud-side collaboration platform.
  • the resource supply and demand parties of the user terminal, the cloud service provider terminal and the cloud-side collaboration platform are provided with transparency and reliability of tariff settlement, realizing the reuse of idle computing resources and saving the resource use cost of the resource demander.
  • FIG. 1 is an application environment diagram of a computing resource scheduling method in one embodiment.
  • FIG. 2 is a schematic flowchart of a method for scheduling computing resources in one embodiment.
  • FIG. 3 is a schematic flowchart of a method for scheduling computing resources in one embodiment.
  • FIG. 4 is a schematic flowchart of a method for scheduling computing resources in one embodiment.
  • FIG. 5 is a schematic diagram of the interaction of the cloud service provider terminal in the uplink of the contracting process in one embodiment.
  • FIG. 6 is a schematic diagram of the interaction of the user terminal in the uplink of the subscription process in one embodiment.
  • Fig. 7 is an interactive schematic diagram of uploading the construction scheduling instruction transaction on the cloud-edge collaboration platform in one embodiment.
  • FIG. 8 is an interactive schematic diagram of uploading a resource view of a cloud service provider terminal in an embodiment.
  • FIG. 9 is an interactive schematic diagram of uploading a settlement bill of a user terminal to the chain in one embodiment.
  • FIG. 10 is a schematic diagram of the on-chain interaction of the settlement bill of the cloud service provider in one embodiment.
  • FIG. 11 is a schematic diagram of deployment of a scheduling system for computing resources in one embodiment.
  • FIG. 12 is a schematic diagram of a blockchain node on the cloud-edge collaboration platform side in one embodiment.
  • FIG. 13 is a structural block diagram of a cloud-edge collaboration platform in one embodiment.
  • Figure 14 is a diagram of the internal structure of a computer device in one embodiment.
  • the cloud-edge collaboration technology can achieve second-level scheduling, dynamically and flexibly shrink and expand available computing resources, compared with traditional cloud services, traditional computing resources scheduling and tariff settlement are usually handled by the cloud.
  • the edge collaboration platform is responsible, so the fairness and transparency of scheduling cannot be guaranteed to users and cloud service providers. Therefore, when choosing cloud services or conducting tariff settlement, there is a problem of mutual distrust among users, cloud-side collaboration platforms, and cloud service providers, which restricts the development of cloud-side collaboration technologies to a certain extent.
  • the computing resource scheduling method provided by the present application can be applied to the application environment shown in FIG. 1 .
  • the user terminal 300 has a requirement to deploy computing resources
  • the cloud service provider terminal 400 can provide computing resources.
  • the cloud-side collaboration platform 100 communicates with the user terminal 300 and the cloud service provider terminal 400 respectively, and can search for and schedule the matching available resources of the cloud service provider terminal 400 according to the resource deployment requirements of the user terminal 300 to meet the requirements of the user terminal 300 demand. It can be understood that the cloud-side collaboration platform 100 can also search for a matching deployment resource requirement of the user terminal 300 according to the available resources of the cloud service provider terminal 400 , and schedule the available resources to the user terminal 300 .
  • a blockchain platform 200 is also provided, that is, a blockchain module of a blockchain node having a distributed storage node structure.
  • the blockchain platform 200 is used to record the scheduling information in the resource scheduling process and the metering information of the resource scheduling, and to provide relevant data verification when the user terminal 300 or the cloud service provider terminal 400 and the cloud-edge collaborative platform perform resource scheduling and settlement .
  • the structures of the cloud-edge collaboration platform 100 , the blockchain platform 200 , the user terminal 300 , and the cloud service provider 400 in this embodiment will be described below with reference to FIG. 1 .
  • the cloud-edge collaboration platform 100 includes a platform device 110 , a blockchain access controller 120 and a platform server 130 .
  • the platform device 110 includes a scheduler 112 , a configuration database 114 , a monitoring module 116 and a metering information database 118 .
  • the scheduler 112 is configured to perform scheduling transactions on idle resources according to the scheduling instructions, and write the available resource blueprints, the deployment resource blueprints, and the scheduling instructions in the resource scheduling into the configuration database 114 .
  • the deployment resource blueprint refers to parameters of computing resources required by the user terminal 300 in resource scheduling
  • the available resource blueprint refers to parameters of computing resources that can be provided by the cloud service provider terminal 400 in resource scheduling.
  • the configuration database 114 is used to store legal historical deployment resource blueprints, legal historically available resource blueprints and historical scheduling instructions that have been successfully executed, and send the successfully executed scheduling instructions to the blockchain access controller 120.
  • the configuration database 114 is a service discovery component, which may be, for example, one of etcd, Zookeeper, Consul, and the like.
  • the historical scheduling instructions that have been successfully executed refer to the deployment resource blueprints, available resource blueprints, and scheduling instructions that have been used in the past resource scheduling.
  • the user terminal 300 can monitor the blockchain platform 200, and after monitoring the historical scheduling instructions on the blockchain platform 200, verify whether the local historical scheduling instructions of the user terminal 300 are consistent with the historical scheduling instructions on the chain.
  • the cloud service provider terminal 400 can also monitor the blockchain platform 200, and after monitoring the historical scheduling instructions to be linked to the blockchain platform 200, verify the local historical scheduling instructions of the cloud service provider terminal 400 and the on-chain historical scheduling instructions. Whether the historical scheduling instructions are consistent.
  • the successfully executed historical scheduling instructions may also be periodically sent by the configuration database 114 to the blockchain access controller 120 and then uploaded to the blockchain platform 200 by the blockchain access controller 120 .
  • the monitoring module 116 is used for monitoring the metering operation to acquire metering information, and sending the acquired metering information to the metering information database 118 .
  • the monitoring module 116 may be a monitoring system, such as Prometheus.
  • the metering operation refers to the metering operation performed by the cloud service provider terminal 400 on the scheduling of computing resources during the resource scheduling process, including but not limited to: the measurement of the provisioning time of the computing resources, the measurement of the traffic when the computing resources are provided, and the measurement of the computing resources. A measure of the total provided capacity of a computing resource.
  • the metering information refers to the metering information generated by the metering operation, including but not limited to: the provisioning time of computing resources, the traffic when computing resources are provided, and the total provisioning capacity of computing resources.
  • the acquired metering information may also be periodically sent to the metering information database 118 by the monitoring module 116 .
  • the metering information database 118 is used for storing metering information, and quantitatively sending the stored metering information to the blockchain access controller 120 . Since the stored metering information may vary in size within a unit time, sending the metering information to the blockchain access controller 120 in a quantitative manner can improve the efficiency of each transmission.
  • the metering information database 118 may be a time series database, for example, a time series database (Times Series Database, TSDB) of Facebook Cloud may be used.
  • TSDB Times Series Database
  • the blockchain access controller 120 is used to realize the interaction between the platform device 110 and the blockchain platform 200, including uploading the data of the platform device 110 to the blockchain platform 200 or monitoring and obtaining the data on the blockchain platform 200. data.
  • the platform server 130 is used for business process display, registration, authentication, signing, and the like.
  • the platform server 130 may generally adopt a C/S architecture.
  • the blockchain platform 200 includes a blockchain node module 210 , a smart contract module 220 and a CA certification platform 230 .
  • the blockchain node module 210 has a distributed data structure including nodes in a blockchain network. These nodes are jointly maintained by the cloud-edge collaboration platform, user terminals, and cloud service provider terminals.
  • the smart contract module 220 has an identity verification and authorization module, a signing module, an accounting module, and a settlement module.
  • the identity verification and authorization authentication module is used to verify the user's read and write permissions.
  • the signing module is used to execute the signing process.
  • the accounting module is used to record scheduling information and metering settlement information in the resource scheduling process.
  • the settlement module is used to settle the bill between the user terminal 300 or the cloud service provider terminal 400 and the cloud-edge collaboration platform 100 .
  • the blockchain platform 100 may further include a punishment module, which is used to record the breach of contract information of the user terminal 300, the cloud service provider terminal 400 and the cloud-edge collaboration platform 100.
  • the breach of contract corresponding to the breach of contract information includes, but is not limited to, the user terminal 300 fails to perform tariff settlement on time and according to the amount; the cloud service provider terminal 400 fails to provide the agreed computing resources or the link is disconnected during the provision of computing resources; and the cloud-side collaboration platform 100 indicates that the computing resources of the cloud service provider terminal 400 scheduled by the scheduling user terminal 300 cannot meet the requirements of the user terminal 300 and the like.
  • the user terminal 300 refers to a computing resource demander.
  • the user terminal 300 may include a user client for interacting with the blockchain platform 200 and the cloud-edge collaboration platform 100 respectively.
  • the cloud service provider terminal 400 refers to a computing resource provider.
  • the cloud service provider terminal 400 may include a resource device cloud service provider client, which is used to interact with the blockchain platform 200 and the cloud-edge collaboration platform 100 respectively.
  • Resource devices are used to provide computing resources.
  • FIG. 2 a method for scheduling computing resources is provided, including the following steps:
  • step S100 the successfully executed historical scheduling instructions stored in the configuration database are uploaded to the blockchain platform through the blockchain access controller.
  • the historical scheduling instructions that have been successfully executed refer to the scheduling instructions that have been used in resource scheduling in the past.
  • the successfully executed historical scheduling instructions stored in the configuration database 114 are sent by the configuration database 114 to the blockchain access controller 120 .
  • the blockchain platform 200 performs identity permission verification and transaction verification. If the identity permission check and the transaction check pass, the data is uploaded to the blockchain node module 210 .
  • the configuration database 114 may periodically transmit these data to the blockchain access controller 120, and the blockchain access controller 120 uploads the data to the blockchain platform 200 in parallel during the resource scheduling process.
  • Chain data so as to realize the asynchronous parallel execution of resource scheduling and data uploading, and improve the efficiency of data uploading and resource scheduling.
  • Step S120 sending the verified first historical metering information stored in the metering information database to the blockchain access controller through the blockchain access controller for storage on the blockchain platform.
  • the second historical measurement information is verified. Verify and compare the first historical measurement information on the blockchain access controller with the second historical measurement information stored on the blockchain platform.
  • the metering information refers to the metering information generated by the metering operation and used for tariff calculation, including but not limited to: computing resource provision time, traffic when computing resources are provided, and total provided capacity of computing resources.
  • the metering information stored in the metering information database 118 is sent to the blockchain access controller 120 by the metering information database 118 .
  • the metering information database 118 can quantitatively send these data to the blockchain access controller 120, which improves the communication efficiency between the metering information database 118 and the blockchain access controller 120.
  • the interaction between the cloud-side collaboration platform and the blockchain platform is realized by setting the blockchain access controller in the cloud-side collaboration platform.
  • the distributed storage of all data in the process of resource scheduling that cannot be tampered with provides transparency and credibility of tariff settlement for both the supply and demand sides of the blockchain platform and the cloud-edge collaboration platform, and realizes the reuse of idle computing resources. Save the resource usage cost of the resource demander.
  • the cloud-edge collaboration platform 100 may further include a monitoring module 116 .
  • the monitoring module 116 monitors the settlement process of resource scheduling, and sends the corresponding metering information to the metering information database 118 for storage.
  • the method for scheduling computing resources shown in FIG. 3 includes the following steps.
  • Step S200 determining the matching deployment resource blueprint of the user terminal and the available resource blueprint of the cloud service terminal.
  • the matching deployment resource blueprint of the user terminal 300 and the available resource blueprint of the cloud service terminal 400 refer to the corresponding deployment resource blueprint and available resource blueprint in one scheduling instruction. Both the deployment resource blueprint and the available resource blueprint are resource blueprints that have been signed and verified on the cloud-side collaboration platform.
  • the deployment resource blueprint of the user terminal 300 and the available resource blueprint of the cloud service terminal 400 match each other, it is necessary to consider whether the available resource blueprint can satisfy the deployment resource blueprint, and whether the available resource blueprint matches the deployment resource Whether the blueprint will cause waste of resources.
  • step S200 may include determining the available resource blueprint matching the deployment resource blueprint according to the deployment resource blueprint sent by the user terminal 300, and storing the deployment resource blueprint sent by the user terminal 300 in the configuration database 114; Or according to the available resource blueprint sent by the cloud service provider terminal 400 , a deployment resource blueprint matching the available resource blueprint is determined, and the available resource blueprint sent by the cloud service provider terminal 400 is stored in the configuration database 114 .
  • Step S220 generating a scheduling instruction according to the matching deployment resource blueprint and the available resource blueprint, and executing the scheduling instruction to perform resource scheduling.
  • Step S240 the scheduling instruction is stored in the configuration database.
  • a scheduling instruction is generated according to the matching deployment resource blueprint and the available resource blueprint, and the scheduling instruction schedules the computing resources of the cloud service provider client 400 to the user terminal 300 according to the available resource blueprint to implement resource scheduling.
  • scheduling instructions may be stored to configuration database 114 after resource scheduling is completed or failed. Therefore, it can be understood that the scheduling instructions stored in the configuration database 114 include scheduling instructions that fail to be scheduled and scheduling instructions that are successfully scheduled.
  • the method for scheduling computing resources shown in FIG. 4 includes the following steps.
  • Step S300 when the cloud service provider terminal, the user terminal or the cloud service provider platform breaches the contract during the resource scheduling, store the breach of contract information corresponding to the breach of contract in the breach record database.
  • the breach of contract may include that the user terminal 300 fails to perform tariff settlement on time and according to the amount; the cloud service provider terminal 400 fails to provide the agreed computing resources or the link is disconnected during the provision of computing resources; and the cloud-edge collaboration platform 100 is The computing resources of the cloud service provider terminal 400 scheduled by the scheduling user terminal 300 cannot meet the requirements of the user terminal 300 and the like.
  • the breach of contract will be recorded in the breach record database of the cloud-edge collaboration platform.
  • the default record database can also regularly or quantitatively upload the default information to the blockchain platform 200 through the blockchain access controller 120, and then pass the identity permission verification and transaction verification of the blockchain platform 200. After that, it is uploaded to the blockchain platform 200.
  • Step S320 when the default information of the cloud service provider terminal is greater than the first threshold, lower the matching priority of the cloud service provider terminal.
  • the default information corresponding to the breach of contract may be a quantified value of the breach of contract, for example, the number of disconnections during the cloud service provider terminal 400 provides the cloud service, the difference between the actual provided computing resources and the contracted available resources, the user terminal 300 should pay.
  • punishment measures are implemented on the corresponding executive body.
  • step S320 when the first threshold is 3 times, and the default information of the cloud service provider terminal 400 is that the link is disconnected 4 times during the provision of cloud services, that is, the default information of the cloud service provider terminal 400 is greater than the first threshold, then The matching priority of the cloud service provider terminal 400 is lowered, that is, other cloud service provider terminals 400 with higher priorities are preferentially matched in the next matching.
  • Step S340 when the default information of the user terminal is greater than a second threshold, lower the matching priority of the user terminal.
  • step S340 for example, when the default information of the user terminal 300 is that the number of days in arrears for the payment of the tariff payable is 10 days, and the second threshold is 5 days, the matching priority of the user terminal 300 is lowered.
  • the above-mentioned default information may also be quantifying various default behaviors into credit values, and adjusting the matching priority according to the credit values, which is not particularly limited in this application.
  • the default information of the cloud-side collaboration platform 100 may also be recorded.
  • the default information of the cloud-edge collaboration platform 100 is greater than a certain threshold, the corresponding user terminal 300 or the cloud service provider platform 400 will be compensated.
  • steps in the flowcharts of FIGS. 2-4 are shown in sequence according to the arrows, these steps are not necessarily executed in the sequence shown by the arrows. Unless explicitly stated herein, the execution of these steps is not strictly limited to the order, and these steps may be performed in other orders. Moreover, at least a part of the steps in FIGS. 2-4 may include multiple sub-steps or multiple stages. These sub-steps or stages are not necessarily executed at the same time, but may be executed at different times. These sub-steps or stages are not necessarily completed at the same time. The order of execution of the steps is not necessarily sequential, but may be performed alternately or alternately with other steps or at least a part of sub-steps or stages of other steps.
  • FIG. 5 is a schematic diagram of the interaction of the cloud service provider's terminal in the uplink of the signing process in one embodiment.
  • the signing process of the available resource blueprint of the cloud service provider terminal 400 refers to verifying the available resource blueprint provided by the cloud service provider terminal 400 in the cloud-side collaboration platform 100 .
  • the cloud service provider terminal 400 can broadcast the available resource blueprint to the blockchain platform 200 .
  • the available resource blueprint is uploaded to the blockchain platform 200 .
  • the cloud service provider terminal 400 sends the available resource blueprint including the available resource parameters and the signature of the cloud service provider terminal to the cloud-edge collaboration platform 100, and the cloud-side collaboration platform 100 performs syntax verification and logical verification on the available resource blueprint , where the syntax verification refers to verifying the grammatical correctness of the data, and the logical verification refers to whether the available resource parameters are reasonable. If the syntax verification and logical verification are passed, the cloud-edge collaboration platform 100 signs the available resource parameters, and returns the legal verification result to the cloud service provider terminal 400. If the syntax verification and logic verification are not passed, the cloud-edge collaboration platform 100 returns the illegal verification result to the cloud service provider terminal 400 .
  • the cloud service provider terminal 400 receives the verification result. If the returned verification result is legal, construct a transaction according to the available resource blueprint, and broadcast the available resource blueprint to the blockchain platform 200, after passing the identity permission verification and transaction verification of the blockchain platform 200 On-chain to blockchain platform 200. If the returned verification result is invalid, the cloud service provider terminal 400 modifies the error and repeats the signing process.
  • the cloud-side collaboration platform 100 After signing the contract for the available resource blueprint of the cloud service provider terminal 400, if the cloud-side collaboration platform 100 receives the contracted available resource blueprint sent by the cloud service provider terminal 400, it will perform resource scheduling for the contracted available resource blueprint , and at the same time monitor the data on the blockchain platform 120 through the blockchain access controller 120 to verify whether the blueprint of the available resources that has been contracted and the blueprint of the available resources that have been previously linked on the blockchain platform 200 is verified. If they are consistent, if they are inconsistent, the available resource blueprint on the blockchain platform 200 shall prevail. Due to the blockchain platform 200, the data transmission between the cloud service provider terminal 400 and the cloud-edge collaboration platform 100 is more reliable, which increases the transparency and reliability of tariff settlement for resource scheduling.
  • the method for scheduling computing resources may further include: step S400, receiving the blueprint of the available resources sent by the cloud service provider terminal, and verifying the legality of the blueprint of the available resources.
  • step S400 may include the following steps.
  • Step S420 Receive a cloud service provider subscription request sent by the cloud service provider terminal, where the cloud service provider subscription request includes the available resource blueprint.
  • Step S440 verifies the legality of the available resource blueprint, and returns the legality verification result to the cloud service provider terminal.
  • Step S460 if the available resource blueprint is legal, monitor through the blockchain access controller whether the available resource blueprint is uploaded to the blockchain platform by the cloud service provider terminal and received at the same time
  • the available resource blueprint sent by the cloud service provider terminal is used to perform the resource scheduling.
  • Step S480 if it is monitored that the available resource blueprint is linked to the blockchain platform, the cloud service provider signing request is ended.
  • FIG. 6 is a schematic diagram of the interaction of the user terminal in the uplink of the subscription process in one embodiment.
  • the subscription process for the deployment resource blueprint of the user terminal 300 in FIG. 6 is similar to the subscription process for the resource blueprint that can be provided by the cloud service provider terminal 400 in FIG. 5 .
  • FIG. 5 is the interaction between the cloud-edge collaboration platform 100 , the cloud service provider terminal 400 and the blockchain platform 200
  • FIG. 6 is the interaction between the cloud-edge collaboration platform 100 , the user terminal 300 and the blockchain platform 200 . interaction, so it is not repeated here.
  • the method for scheduling computing resources may further include: step S500, receiving the deployment resource blueprint sent by the user terminal, and verifying the validity of the deployment resource blueprint.
  • step S500 may include the following steps.
  • Step S520 Receive a user subscription request sent by the user terminal, where the user subscription request includes the deployment resource blueprint.
  • Step S540 verifying the legality of the deployment resource blueprint, and returning the verification result of the legality to the user terminal.
  • Step S560 if the deployment resource blueprint is legal, monitor whether the deployment resource blueprint is uploaded by the user terminal to the blockchain platform through the blockchain access controller and simultaneously receive the data from the user.
  • the deployment resource blueprint sent by the end terminal is used to perform the resource scheduling.
  • Step S580 if it is monitored that the deployment resource blueprint is linked to the blockchain platform, the user signing request is ended.
  • FIG. 7 is an interactive schematic diagram of uploading a construction scheduling instruction transaction on the cloud-edge collaboration platform in one embodiment.
  • the process of constructing the scheduling instruction transaction of the cloud-side collaboration platform 100 refers to constructing the scheduling instruction in the cloud-side collaboration platform into a transaction, and the transaction includes the scheduling instruction and the platform signature.
  • the cloud-side collaboration platform 100 may construct scheduling instruction transactions periodically. After the scheduling instruction transaction is constructed, the cloud-edge collaboration platform 100 broadcasts the scheduling instruction transaction to the blockchain platform 200 . After the blockchain platform 200 passes the identity permission verification and transaction verification, the scheduling instruction transaction is uploaded to the blockchain platform 200 .
  • the user terminal 300 and the cloud service provider terminal 400 monitor the blockchain platform 200 to monitor and verify whether the scheduling instruction transaction is uploaded to the blockchain platform 200 .
  • FIG. 8 is an interactive schematic diagram of uploading a resource view of a cloud service provider terminal in an embodiment.
  • the cloud service provider terminal 400 sends the resource view including the signature of the cloud service provider terminal to the user terminal 300 and the cloud-edge collaboration platform 100 respectively.
  • the resource view indicates a data view of the usage of the metering information of the resource equipment of the cloud service provider terminal.
  • the user terminal 400 and the cloud-edge collaboration platform 100 respectively verify whether the metering information of the resource view is correct, sign if correct, and return the verification result to the cloud service provider terminal 400 .
  • the cloud service provider terminal 400 After receiving the verification result of the signature of the user terminal 300 and the verification result of the signature of the cloud-edge collaboration platform 100, the cloud service provider terminal 400 broadcasts the resource view including the metering information, the signature of the cloud-edge collaboration platform, and the signature of the cloud service provider terminal. to Blockchain Platform 200.
  • the blockchain platform 200 performs identity permission verification and transaction verification on the resource view.
  • the identity permission verification and transaction verification pass the resource view is uploaded to the blockchain platform 200.
  • the user terminal 300 and the cloud service provider terminal 400 monitor whether the resource view is linked to the blockchain platform 200, and verify whether the linked resource view is correct.
  • the method for scheduling computing resources may further include the following steps: Step S600 , receiving metering information corresponding to the resource scheduling sent by the cloud service provider terminal, and verifying whether the metering information is legal.
  • step S600 may include the following steps.
  • Step S620 Receive a resource view sent by the cloud service provider terminal, where the resource view includes the metering information.
  • Step S640 verifying the legality of the metering information, and returning the verification result of the legality to the cloud service provider terminal, if the metering information is legal, monitoring the Whether the metering information is uploaded to the blockchain platform.
  • FIG. 9 is an interactive schematic diagram of uploading a settlement bill of a user terminal to the chain in one embodiment.
  • the cloud-edge collaboration platform 100 initiates a settlement request, and generates billing information, and the billing information includes the signature of the cloud-edge collaboration platform. If the user terminal 300 agrees with the bill, it will transfer money with the cloud-edge collaboration platform 100 . After the transfer is successful, the cloud-edge collaboration platform 100 broadcasts the transfer information (including bills and transfer vouchers) to the blockchain platform 200 . At the same time, the user terminal 300 and the cloud-edge collaboration platform 100 monitor whether the transfer information is uploaded to the blockchain platform 200 .
  • the method for scheduling computing resources may further include the following steps.
  • Step S700 when acquiring a user settlement request, generate user billing information according to the metering information.
  • Step S720 sending the user billing information to the user terminal.
  • Step S740 if a user transfer transaction corresponding to the user billing information sent by the user terminal is received, broadcast the user settlement information corresponding to the user transfer transaction to the district through the blockchain access controller. block chain platform, and end the user settlement request.
  • FIG. 10 is a schematic diagram of the on-chain interaction of the settlement bill of the cloud service provider terminal in one embodiment.
  • the uploading process of the settlement bill of the cloud service provider terminal 400 in FIG. 10 is similar to the uploading process of the settlement bill of the user terminal 300 in FIG. 9 .
  • FIG. 9 is the interaction between the cloud-side collaboration platform 100 , the user terminal 300 and the blockchain platform 200
  • FIG. 10 is the interaction between the cloud-side collaboration platform 100 , the cloud service provider terminal 400 and the blockchain platform 200 . interaction, so it is not repeated here.
  • the cloud-edge collaboration platform may further include the following steps.
  • Step S800 when acquiring the cloud service provider settlement request, generate cloud service provider billing information according to the metering information.
  • Step S820 sending the cloud service provider billing information to the cloud service provider terminal.
  • Step S840 if receiving confirmation information corresponding to the cloud service provider billing information sent by the cloud service provider terminal, execute a cloud service provider transfer transaction corresponding to the cloud service provider billing information;
  • Step S860 monitor whether the cloud service provider settlement information corresponding to the cloud service provider transfer transaction is uploaded to the blockchain platform through the blockchain access controller, and if the cloud service provider settlement information is monitored to be uploaded to the chain To the blockchain platform, the cloud service provider settlement request is ended.
  • step S860 the cloud service provider settlement information in step S860 is sent to the blockchain platform 200 by the cloud service provider terminal 400 .
  • FIG. 11 is a schematic diagram of deployment of a scheduling system for computing resources in one embodiment.
  • the blockchain platform uses hyperledger fabric, which includes three types of organizations: cloud-edge collaboration platforms, cloud service providers, and users. Each organization needs to deploy peer nodes, and all organizations belong to the same channel.
  • the Orderer node is provided by the cloud-edge collaboration platform and cloud service provider, and is optional for users.
  • Each module of the smart contract is implemented by chaincode.
  • FIG. 12 is a schematic diagram of a blockchain node on the cloud-edge collaboration platform side in one embodiment.
  • a cloud-edge collaboration platform at least 3 Orderer nodes are required when the platform is initialized (the raft consensus algorithm requires that the number of Orderer nodes required for each channel is odd), and 2 Peer nodes (the number of Peer nodes needs to be an even number), to Make sure that the blockchain system can function properly.
  • the cloud-edge collaboration platform 100 can appropriately reduce the holdings of Orderer nodes and Peer nodes, and at the same time install and instantiate the initial chaincode.
  • an apparatus for scheduling computing resources including:
  • a configuration database for storing successfully executed historical scheduling instructions
  • a metering information database for storing verified historical metering information
  • the blockchain access controller is used to execute the interaction between the cloud-edge collaboration platform and the blockchain platform.
  • the configuration database 114 and the metering information database 118 are respectively connected in communication with the blockchain access controller 120, so as to store the successfully executed historical scheduling instructions stored in the configuration database 114 and the verification information stored in the metering information database
  • the past historical metering information is sent to the blockchain access controller in a timed or quantitative manner.
  • the blockchain access controller 120 is used to perform the interaction between the cloud-edge collaboration platform and the blockchain platform.
  • Each module in the above-mentioned apparatus for scheduling computing resources may be implemented in whole or in part by software, hardware, and combinations thereof.
  • the above modules can be embedded in or independent of the processor in the computer device in the form of hardware, or stored in the memory in the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
  • a computer device is provided, and the computer device may be a server, and its internal structure diagram may be as shown in FIG. 14 .
  • the computer device includes a processor, memory, a network interface, and a database connected by a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities.
  • the memory of the computer device includes a non-volatile storage medium, an internal memory.
  • the nonvolatile storage medium stores an operating system, a computer program, and a database.
  • the internal memory provides an environment for the execution of the operating system and computer programs in the non-volatile storage medium.
  • the various databases of the computer equipment are used to store data used for computing resource scheduling.
  • the network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for mobilizing computing resources is implemented.
  • FIG. 14 is only a block diagram of a partial structure related to the solution of the present application, and does not constitute a limitation on the computer equipment to which the solution of the present application is applied. Include more or fewer components than shown in the figures, or combine certain components, or have a different arrangement of components.
  • a computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, the following steps are implemented:
  • the verified historical metering information stored in the metering information database is sent to the blockchain access controller 120 through the blockchain access controller.
  • Nonvolatile memory may include read only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM), or flash memory.
  • Volatile memory may include random access memory (RAM) or external cache memory.
  • RAM is available in various forms such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous chain Road (Synchlink) DRAM (SLDRAM), memory bus (Rambus) direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM), etc.
  • SRAM static RAM
  • DRAM dynamic RAM
  • SDRAM synchronous DRAM
  • DDRSDRAM double data rate SDRAM
  • ESDRAM enhanced SDRAM
  • SLDRAM synchronous chain Road (Synchlink) DRAM
  • SLDRAM synchronous chain Road (Synchlink) DRAM
  • Rambus direct RAM
  • DRAM direct memory bus dynamic RAM
  • RDRAM memory bus dynamic RAM

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • General Physics & Mathematics (AREA)
  • General Engineering & Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Health & Medical Sciences (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Computer Hardware Design (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

一种计算资源的调度方法、装置、计算机设备和存储介质。所述方法包括：通过所述区块链访问控制器（120）将存储在所述配置数据库（114）中的成功执行的历史调度指令上链至区块链平台（200）；将存储在所述计量信息数据库（118）中的验证过的第一历史计量信息发送至所述区块链访问控制器（120），用于与所述区块链平台（200）上存储的第二历史计量信息进行验证，并将所述区块链访问控制器（120）上的所述第一历史计量信息与所述区块链平台（200）上存储的第二历史计量信息进行验证比对。

Description

计算资源的调度方法、装置、计算机设备及存储介质
相关申请
本申请要求于2020年11月04日提交中国专利局、申请号为202011213390.2、发明名称为“计算资源的调度方法、装置、计算机设备及存储介质”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本申请涉及云计算领域，特别是涉及一种计算资源的调度方法、装置、计算机设备和存储介质。
背景技术
随着云计算不断发展以及边缘应用的快速增长，云边协同技术已成为新的研发热点。其中，云边协同平台在实现对空闲计算资源的充分利用的同时，也节约了资源需求方的资源使用成本。用户可以通过云边协同技术将应用或计算任务动态、便捷地部署在云服务商的资源设备上，从而相比于传统的云服务，可实现秒级调度，动态、灵活地收缩和扩容可用的计算资源。
发明内容
本申请各示例性的实施例提供一种计算资源的调度方法、装置、计算机设备和存储介质。
本申请的一方面，提供一种计算资源的调度方法，所述云边协同平台包括配置数据库，计量信息数据库和区块链访问控制器，所述方法包括：通过所述区块链访问控制器将存储在所述配置数据库中的成功执行的历史调度指令上链至区块链平台；将存储在所述计量信息数据库中的验证过的第一历史计量信息发送至所述区块链访问控制器；将所述区块链访问控制器上的所述第一历史计量信息与所述区块链平台上存储的第二历史计量信息进行验证比对。
在一实施例中，所述成功执行的历史调度指令通过所述区块链访问控制器定时地发送至区块链平台。
在一实施例中，所述第一历史计量信息通过所述区块链访问控制器定量地发送至所述区块链访问控制器。
在一实施例中，所述云边协同平台还包括计量监控模块，所述方法还包括：通过所述监控计量模块监控计量操作以获取计量信息，并定时地将所述获取的计量信息发送至所述计量信息数据库中以形成所述第一历史计量信息。
在一实施例中，所述方法还包括：确定彼此匹配的用户终端的部署资源蓝图和云服务商终端的可提供资源蓝图；根据彼此匹配的所述部署资源蓝图和所述可提供资源蓝图，生成调度指令，并执行所述调度指令以执行资源调度；将所述调度指令存储至所述配置数据库。
在一实施例中，所述确定彼此匹配的部署资源蓝图和可提供资源蓝图的步 骤，包括：根据所述用户终端发送的所述部署资源蓝图，确定与所述部署资源蓝图相匹配的可提供资源蓝图，并将所述用户终端发送的所述部署资源蓝图存储至所述配置数据库；或根据所述云服务商终端发送的所述可提供资源蓝图，确定与所述可提供资源蓝图相匹配的所述部署资源蓝图，并将所述云服务商终端发送的所述可提供资源蓝图存储至所述配置数据库。
在一实施例中，所述云边协同平台还包括违约记录数据库，所述方法还包括：当在所述资源调度中，所述云服务商终端、所述用户终端或所述云服务商平台发生违约行为时，将对应所述违约行为的违约信息存储至所述违约记录数据库；所述确定彼此匹配的所述用户终端的部署资源蓝图和所述云服务商终端的可提供资源蓝图的步骤，包括：当所述云服务商终端的所述违约信息大于第一阈值时，降低所述云服务商终端的匹配优先级；和/或当所述用户终端的所述违约信息大于第二阈值时，降低所述用户终端的匹配优先级。
在一实施例中，所述方法还包括：接收所述云服务商终端发送的所述可提供资源蓝图，并验证所述可提供资源蓝图的合法性。
在一实施例中，所述接收所述云服务商终端发送的所述可提供资源蓝图，并验证所述可提供资源蓝图的合法性的步骤，包括：接收由所述云服务商终端发送的云服务商签约请求，所述云服务商签约请求包括所述可提供资源蓝图；验证所述可提供资源蓝图的合法性，向所述云服务商终端返回所述合法性的验证结果；若所述可提供资源蓝图为合法，则通过所述区块链访问控制器监控所述可提供资源蓝图是否由所述云服务商终端上链至所述区块链平台并同时接收由所述云服务商终端发送的所述可提供资源蓝图以执行所述资源调度；若监控到所述可提供资源蓝图上链至所述区块链平台，则结束所述云服务商签约请求。
在一实施例中，所述方法还包括：接收所述用户终端发送的所述部署资源蓝图，并验证所述部署资源蓝图的合法性。
在一实施例中，所述接收所述用户终端发送的所述部署资源蓝图，并验证所述部署资源蓝图的合法性的步骤，包括：接收由所述用户终端发送的用户签约请求，所述用户签约请求包括所述部署资源蓝图；验证所述部署资源蓝图的合法性，向所述用户终端返回所述合法性的验证结果；若所述部署资源蓝图为合法，则通过所述区块链访问控制器监控所述部署资源蓝图是否由所述用户终端上链至所述区块链平台并同时接收由所述用户端终端发送的所述部署资源蓝图以执行所述资源调度；若监控到所述部署资源蓝图上链至所述区块链平台，则结束所述用户签约请求。
在一实施例中，所述方法还包括：接收所述云服务商终端发送的对应所述资源调度的计量信息，并验证所述计量信息是否合法。
在一实施例中，所述接收所述云服务商终端发送的对应所述资源调度的所述计量信息，并验证所述计量信息是否合法的步骤，包括：接收由所述云服务商终端发送的资源视图，所述资源视图包括所述计量信息；验证所述计量信息的合法性，并向所述云服务商终端返回所述合法性的验证结果，若所述计量信息为合法，则通过所述区块链访问控制器监控所述计量信息是否上链至所述区块链平台。
在一实施例中，所述方法还包括：当获取用户结算请求时，根据所述计量信息生成用户账单信息；将所述用户账单信息发送至所述用户终端；若接收到由所述用户终端发送的对应所述用户账单信息的用户转账交易，则通过所述区块链访问控制器将对应所述用户转账交易的用户结算信息广播至所述区块链平台，并结束所述用户结算请求。
在一实施例中，所述方法还包括：当获取云服务商结算请求时，根据所述计量信息生成云服务商账单信息；将所述云服务商账单信息发送至所述云服务商终端；若接收到由所述云服务商终端发送的对应所述云服务商账单信息的确认信息，则执行对应所述云服务商账单信息的云服务商转账交易；通过所述区块链访问控制器监控对应所述云服务商转账交易的云服务商结算信息是否上链至所述区块链平台，若监控到所述云服务商结算信息上链至所述区块链平台，则结束所述云服务商结算请求。
本申请的另一方面，提供一种计算资源的调度装置，设置于云边协同平台中，所述装置包括：配置数据库，用于存储合法的历史部署资源蓝图、合法的历史可提供资源蓝图与成功执行的历史调度指令；计量信息数据库，用于存储验证过的历史计量信息；以及区块链访问控制器，用于执行所述云边协同平台和区块链平台之间的交互。
本申请的再一方面，提供一种计算机设备，包括存储器和处理器，所述存储器存储有计算机程序，所述处理器执行所述计算机程序时实现上述各实施例的方法的步骤。
本申请的又一方面，提供一种计算机可读存储介质，其上存储有计算机程序，所述计算机程序被处理器执行时实现上述各实施例的方法的步骤。
上述计算资源的调度方法、装置、计算机设备和存储介质，通过在云边协同平台中设置区块链访问控制器，实现云边协同平台与区块链平台的交互。通过将存储在云边协同平台的配置数据库中成功执行的历史调度指令上链至区块链平台，并通过区块链访问控制器监控存储在在计量信息数据库中的验证过的第一历史计量信息与区块链平台上存储的由云服务商终端上链的区块链平台的第二历史计量信息是否一致，从而实现不可篡改的资源调度过程中所有数据的分布式存储。这样为用户终端、云服务商终端与云边协同平台的资源供需三方提供了资费结算的透明性与可信性，实现了重复利用空闲计算资源的同时，节约资源需求方的资源使用成本。
附图说明
图1为一个实施例中计算资源调度方法的应用环境图。
图2为一个实施例中计算资源的调度方法的流程示意图。
图3为一个实施例中计算资源的调度方法的流程示意图。
图4为一个实施例中计算资源的调度方法的流程示意图。
图5为一个实施例中云服务商终端的签约过程的上链的交互示意图。
图6为一个实施例中用户终端的签约过程的上链的交互示意图。
图7为一个实施例中云边协同平台的构建调度指令交易的上链的交互示意 图。
图8为一个实施例中云服务商终端的资源视图的上链的交互示意图。
图9为一个实施例中用户终端的结算账单的上链的交互示意图。
图10为一个实施例中云服务商的结算账单的上链交互示意图。
图11为一个实施例中计算资源的调度系统的部署示意图。
图12为一个实施例中云边协同平台侧的区块链节点的示意图。
图13为一个实施例中云边协同平台的结构框图。
图14为一个实施例中计算机设备的内部结构图。
具体实施方式
为了使本申请的目的、技术方案及优点更加清楚明白，以下结合附图及实施例，对本申请进行进一步详细说明。应当理解，此处描述的具体实施例仅仅用以解释本申请，并不用于限定本申请。
如前所述，虽然云边协同技术相比于传统的云服务，可实现秒级调度，动态、灵活地收缩和扩容可用的计算资源，但是传统的计算资源的调度与资费结算由于通常由云边协同平台负责，所以无法向用户与云服务商保证调度的公平性与透明性。因此，在选择云服务或进行资费结算时，存在用户、云边协同平台、云服务商三者互不信任的问题，这在一定程度上制约了云边协同技术的发展。
本申请提供的计算资源的调度方法，可以应用于如图1所示的应用环境中。其中，用户终端300具有部署计算资源的需求，云服务商终端400可以提供计算资源。云边协同平台100分别与用户终端300和云服务商终端400通信，并且可以根据用户终端300的部署资源的需求查找并调度相匹配的云服务商终端400的可提供资源，以满足用户终端300的需求。可以理解地，云边协同平台100也可以根据云服务商终端400的可提供资源查找相匹配的用户终端300的部署资源的需求，并将可提供资源调度给所述用户终端300。
在图1的应用环境中，还设置有区块链平台200，即具有分布式存储节点结构的区块链节点的区块链模块。该区块链平台200用于记录资源调度过程中的调度信息以及资源调度的计量信息，以及用于在用户终端300或云服务商终端400与云边协同平台进行资源调度结算时提供相关数据验证。
下面将进一步结合图1，说明本实施例中云边协同平台100、区块链平台200、用户终端300和云服务商400的结构。
云边协同平台100包括平台设备110、区块链访问控制器120及平台服务端130。平台设备110包括调度器112、配置数据库114、监控模块116及计量信息数据库118。
调度器112用于根据调度指令对空闲资源进行调度交易，并将资源调度中的可提供资源蓝图、部署资源蓝图以及调度指令写入配置数据库114中。其中，部署资源蓝图指资源调度中用户终端300所需求的计算资源的参数，可提供资源蓝图是指资源调度中云服务商终端400可提供的计算资源的参数。
配置数据库114用于存储合法的历史部署资源蓝图、合法的历史可提供资 源蓝图和成功执行过的历史调度指令，并将成功执行过的调度指令发送至区块链访问控制器120。配置数据库114为服务发现组件，例如可以为etcd，Zookeeper和Consul等中的一者。其中成功执行过的历史调度指令是指在过去的资源调度中使用过的部署资源蓝图、可提供资源蓝图和调度指令。用户终端300可以对区块链平台200进行监控，当监控到历史调度指令上链至区块链平台200后，验证用户终端300本地的历史调度指令与链上的历史调度指令是否一致。同样地，云服务商终端400也可以对区块链平台200进行监控，当监控到历史调度指令上链至区块链平台200后，验证云服务商终端400本地的历史调度指令与链上的历史调度指令是否一致。
可选地，成功执行过的历史调度指令还可以定时地由配置数据库114发送至区块链访问控制器120并进而由区块链访问控制器120上链至区块链平台200。
监控模块116用于监控计量操作以获取计量信息，并将所述获取的计量信息发送至计量信息数据库118。监控模块116可以为监控系统，例如Prometheus。其中，计量操作是指在资源调度过程中，云服务商终端400对计算资源的调度的计量操作，包括但不限于：对计算资源提供时长的计量、对计算资源提供时的流量的计量和对计算资源的提供总容量的计量。计量信息是指计量操作所产生的计量信息，包括但不限于：计算资源提供时长、计算资源提供时的流量和计算资源的提供总容量。
可选地，所获取的计量信息还可以由监控模块116定时地发送至计量信息数据库118。
计量信息数据库118用于存储计量信息，并定量地将存储的计量信息发送至区块链访问控制器120。由于存储的计量信息在单位时间内可能大小不一，因此采用定量的方式将计量信息发送至区块链访问控制器120可以提高每次发送的效率。计量信息数据库118可以是一种时间序列数据库，例如可以采用阿里云的时间序列数据库(Times Series Database，TSDB)。
区块链访问控制器120用于实现平台设备110与区块链平台200的交互，包括将平台设备110的数据上链至区块链平台200或监控和获取区块链平台200上的链上数据。
平台服务端130用于业务流程的展示、注册、认证、签约等。平台服务端130一般可以采用C/S架构。
区块链平台200包括区块链节点模块210、智能合约模块220以及CA认证平台230。区块链节点模块210具有分布式数据结构，包括区块链网络中的节点。这些节点由云边协同平台、用户终端、云服务商终端共同维护。
智能合约模块220具有身份校验及授权鉴权模块、签约模块、记账模块、结算模块。身份校验及授权鉴权模块用于验证用户的读写权限。签约模块用于执行签约流程。记账模块用于在资源调度过程中记录调度信息以及计量结算信息。结算模块用于对用户终端300或云服务商终端400和云边协同平台100之间的账单进行结算。
可选地，区块链平台100还可以包括惩处模块，该惩处模块用于记录用户 终端300、云服务商终端400和云边协同平台100的违约信息。违约信息对应的违约行为包括但不限于，用户终端300未按时按额进行资费结算；云服务商终端400未提供约定的计算资源或在提供计算资源期间出现断链等情况；以及云边协同平台100为调度用户终端300调度的云服务商终端400的计算资源不能满足用户终端300的需求等。
用户终端300指的是计算资源需求方。用户终端300可以包括用户客户端，该用户客户端用于分别与区块链平台200和云边协同平台100进行交互。
云服务商终端400指的是计算资源提供方。云服务商终端400可以包括资源设备云服务商客户端，该云服务商客户端用于分别与区块链平台200和云边协同平台100进行交互。资源设备用于提供计算资源。
请结合图1参照图2，如图2所示，提供了一种计算资源的调度方法，包括以下步骤：
步骤S100，通过所述区块链访问控制器将存储在所述配置数据库中的成功执行的历史调度指令上链至区块链平台。
其中，成功执行过的历史调度指令是指在过去的资源调度使用过的调度指令。
具体地，存储在配置数据库114中的成功执行的历史调度指令由配置数据库114发送至区块链访问控制器120。区块链平台200进行身份许可校验与交易校验。若身份许可校验和交易校验通过，则将数据上链至区块链节点模块210。
可选地，配置数据库114可以定时地将这些数据传送至区块链访问控制器120，区块链访问控制器120再将数据上链至区块链平台200上从而在资源调度过程中并行地上链数据，从而实现资源调度和数据上链的异步并行执行，提高数据的上链效率和资源调度的执行效率。
步骤S120，通过所述区块链访问控制器将存储在所述计量信息数据库中的验证过的第一历史计量信息发送至所述区块链访问控制器用于与所述区块链平台上存储的第二历史计量信息进行验证。并将所述区块链访问控制器上的所述第一历史计量信息与所述区块链平台上存储的第二历史计量信息进行验证比对。
计量信息是指计量操作所产生的用于进行资费计算的计量信息，包括但不限于：计算资源提供时长、计算资源提供时的流量和计算资源的提供总容量。
具体地，存储在计量信息数据库118中的计量信息由计量信息数据库118发送至区块链访问控制器120。
可选地，计量信息数据库118可以定量地将这些数据发送至区块链访问控制器120，提高了计量信息数据库118与区块链访问控制器120之间的通信效率。
上述计算资源的调度方法中，通过在云边协同平台中设置区块链访问控制器，实现云边协同平台与区块链平台的交互。通过将存储在云边协同平台的配置数据库中合法的成功执行的历史调度指令以及存储在在计量信息数据库中的验证过的历史计量信息传送至区块链访问控制器用于一致性验证，从而实现不可篡改的资源调度过程中所有数据的分布式存储，为区块链平台与云边协同平台的资源供需双方提供了资费结算的透明性与可信性，实现了重复利用空闲计 算资源的同时，节约资源需求方的资源使用成本。
在另一个实施例中，云边协同平台100还可以包括监控模块116。监控模块116监控资源调度的结算过程，并将对应的计量信息发送至计量信息数据库118用于存储。
请参照图3，图3示出的计算资源的调度方法包括以下步骤。
步骤S200，确定彼此匹配的用户终端的部署资源蓝图和云服务终端的可提供资源蓝图。
其中，彼此匹配的用户终端300的部署资源蓝图和云服务终端400的可提供资源蓝图是指，在一个调度指令中相对应的部署资源蓝图和可提供资源蓝图。部署资源蓝图和可提供资源蓝图均为在云边协同平台进行过签约验证的资源蓝图。
具体地，在确定彼此匹配的用户终端300的部署资源蓝图和云服务终端400的可提供资源蓝图时，需要考虑到可提供资源蓝图是否能满足部署资源蓝图，以及可提供资源蓝图匹配给部署资源蓝图是否会造成资源的浪费。
可以理解的是，步骤S200可以包括根据用户终端300发送的部署资源蓝图，来确定与该部署资源蓝图相匹配的可提供资源蓝图，并将用户终端300发送的部署资源蓝图存储至配置数据库114；或根据云服务商终端400发送的可提供资源蓝图，确定与可提供资源蓝图相匹配的部署资源蓝图，并将云服务商终端400发送的可提供资源蓝图存储至配置数据库114。
步骤S220，根据彼此匹配的部署资源蓝图和可提供资源蓝图，生成调度指令，并执行该调度指令以执行资源调度。
步骤S240，将调度指令存储至配置数据库。
具体地，根据相匹配的部署资源蓝图和可提供资源蓝图生成调度指令，该调度指令将云服务商客户端400的计算资源按照可提供资源蓝图调度给用户终端300，以实现资源调度。
在一个实施例中，调度指令可以在资源调度完成或者失败后存储至配置数据库114。因此，可以理解的是，存储在配置数据库114中的调度指令包括调度失败的调度指令和调度成功的调度指令。
请参照图4，图4示出的计算资源的调度方法包括以下步骤。
步骤S300，当在资源调度中，云服务商终端、用户终端或云服务商平台发生违约行为时，将对应违约行为的违约信息存储至所述违约记录数据库。
如前所述，违约行为可以包括用户终端300未按时按额进行资费结算；云服务商终端400未提供约定的计算资源或在提供计算资源期间出现断链等情况；以及云边协同平台100为调度用户终端300调度的云服务商终端400的计算资源不能满足用户终端300的需求等。本领域的技术人员应当知晓对云服务中各方的各种违约行为，本发明对此不作特别限定。
具体地，在云服务商终端400、用户终端300或云服务商平台100一方在资源调度中发生违约行为时，该违约行为将被记录在云边协同平台的违约记录数据库中。可以理解的是，该违约记录数据库也可以定时地或定量地将违约信息通过区块链访问控制器120上传至区块链平台200，并在通过区块链平台200的 身份许可验证和交易验证后，上链至区块链平台200。
步骤S320，当云服务商终端的违约信息大于第一阈值时，降低云服务商终端的匹配优先级。
对应于违约行为的违约信息可以是违约行为的量化值，例如，云服务商终端400提供云服务期间的断链次数、实际提供的计算资源和签约的可提供资源的差值，用户终端300应付资费的支付拖欠天数，云服务商平台100错误匹配部署资源蓝图和可提供资源蓝图的次数等。当这些量化值大于一阈值时，则对相应执行主体实施惩罚措施。例如，在步骤S320中，当第一阈值为3次，云服务商终端400的违约信息为在提供云服务期间断链了4次，即云服务商终端400的违约信息大于第一阈值，则将该云服务商终端400的匹配优先级降低，即在下次匹配时优先匹配其他具有更高优先级的云服务商终端400。
步骤S340，当所述用户终端的所述违约信息大于第二阈值时，降低所述用户终端的匹配优先级。
与步骤S330相似地，在步骤S340中，例如当用户终端300的违约信息为应付资费的支付拖欠天数累计为10天，而第二阈值是5天，则降低用户终端300的匹配优先级。
可以理解的是，上述的违约信息也可以是将各种违约行为量化为信用值，并根据信用值来调节匹配优先级，本申请对此不作特别的限定。
可选地，也可以对云边协同平台100的违约信息进行记录。在发现云边协同平台100的违约信息大于特定阈值时，将对对应的用户终端300或云服务商平台400进行补偿。
应该理解的是，虽然图2-4的流程图中的各个步骤按照箭头的指示依次显示，但是这些步骤并不是必然按照箭头指示的顺序依次执行。除非本文中有明确的说明，这些步骤的执行并没有严格的顺序限制，这些步骤可以以其它的顺序执行。而且，图2-4中的至少一部分步骤可以包括多个子步骤或者多个阶段，这些子步骤或者阶段并不必然是在同一时刻执行完成，而是可以在不同的时刻执行，这些子步骤或者阶段的执行顺序也不必然是依次进行，而是可以与其它步骤或者其它步骤的子步骤或者阶段的至少一部分轮流或者交替地执行。
请参照图5，图5为一个实施例中云服务商终端的签约过程的上链的交互示意图。
云服务商终端400的可提供资源蓝图的签约过程，是指将云服务商终端400提供的可提供资源蓝图在云边协同平台100中进行验证。在本实施例中，若通过云边协同平台的验证，云服务商终端400就可以将该可提供资源蓝图广播至区块链平台200。在通过区块链平台200的身份许可校验和交易校验后，该可提供资源蓝图上链至区块链平台200。
具体地，云服务商终端400发送包括可提供资源参数以及云服务商终端的签名的可提供资源蓝图至云边协同平台100，云边协同平台100对该可提供资源蓝图进行语法验证以及逻辑验证，其中，语法验证指验证数据的语法正确性，逻辑验证指可提供资源参数是否合理。若通过语法验证和逻辑验证，则云边协同平台100对该可提供资源参数进行签名，并将合法的验证结果返回给云服务 商终端400。若未通过语法验证和逻辑验证，则云边协同平台100将不合法的验证结果返回给云服务商终端400。
接着，云服务商终端400接收验证结果。若返回的验证结果为合法，根据该可提供资源蓝图构建为交易，并将该可提供资源蓝图广播至区块链平台200，在通过区块链平台200的身份许可校验和交易校验后上链至区块链平台200。若返回的验证结果为不合法，则云服务商终端400修改错误并重复签约过程。
在云服务商终端400的可提供资源蓝图签约后，云边协同平台100若接收到云服务商终端400发送该签约过的可提供资源蓝图，则针对该签约过的可提供资源蓝图进行资源调度，并同时通过区块链访问控制器120监控区块链平台120上的数据，验证收到的签约过的可提供资源蓝图是否与区块链平台200上之前上链的该可提供资源蓝图是否一致，若不一致，则以区块链平台200上的可提供资源蓝图为准。由于区块链平台200，使得云服务商终端400和云边协同平台100之间的数据传输更加可靠，增加了资源调度的资费结算的透明性与可信性。
在该签约过程中，所述计算资源的调度方法还可以包括：步骤S400，接收所述云服务商终端发送的所述可提供资源蓝图，并验证所述可提供资源蓝图的合法性。
具体地，步骤S400可以包括以下步骤。
步骤S420，接收由所述云服务商终端发送的云服务商签约请求，所述云服务商签约请求包括所述可提供资源蓝图。
步骤S440验证所述可提供资源蓝图的合法性，向所述云服务商终端返回所述合法性的验证结果。
步骤S460，若所述可提供资源蓝图为合法，则通过所述区块链访问控制器监控所述可提供资源蓝图是否由所述云服务商终端上链至所述区块链平台并同时接收由所述云服务商终端发送的所述可提供资源蓝图以执行所述资源调度。
步骤S480，若监控到所述可提供资源蓝图上链至所述区块链平台，则结束所述云服务商签约请求。
图6为一个实施例中用户终端的签约过程的上链的交互示意图。图6的用户终端300的部署资源蓝图的签约过程与图5的云服务商终端400的可提供资源蓝图的签约过程相似。不同之处在于图5是云边协同平台100、云服务商终端400和区块链平台200之间的交互，而图6是云边协同平台100、用户终端300和区块链平台200之间的交互，因此在这里不再赘述。
在该签约过程中，所述计算资源的调度方法还可以包括：步骤S500，接收所述用户终端发送的所述部署资源蓝图，并验证所述部署资源蓝图的合法性。
具体地，步骤S500可以包括以下步骤。
步骤S520，接收由所述用户终端发送的用户签约请求，所述用户签约请求包括所述部署资源蓝图。
步骤S540，验证所述部署资源蓝图的合法性，向所述用户终端返回所述合法性的验证结果。
步骤S560，若所述部署资源蓝图为合法，则通过所述区块链访问控制器监 控所述部署资源蓝图是否由所述用户终端上链至所述区块链平台并同时接收由所述用户端终端发送的所述部署资源蓝图以执行所述资源调度。
步骤S580，若监控到所述部署资源蓝图上链至所述区块链平台，则结束所述用户签约请求。
图7为一个实施例中云边协同平台的构建调度指令交易的上链的交互示意图。云边协同平台100的构建调度指令交易的过程指将云边协同平台中的调度指令构建为交易，该交易中包含调度指令及平台签名。可选地，云边协同平台100可以定时地构建调度指令交易。当调度指令交易构建完成后，云边协同平台100将该调度指令交易广播至区块链平台200。区块链平台200通过身份许可校验和交易校验后，将调度指令交易上链至区块链平台200。同时，用户终端300和云服务商终端400监控区块链平台200，监控并验证该调度指令交易是否上链至区块链平台200。
图8为一个实施例中云服务商终端的资源视图的上链的交互示意图。在该资源视图的上链过程中，云服务商终端400分别向用户终端300和云边协同平台100发送包含云服务商终端的签名的资源视图。所述资源视图指示出了云服务商终端的资源设备的计量信息的使用情况的数据视图。用户终端400和云边协同平台100在收到资源视图后，分别验证资源视图的计量信息是否正确，如正确则进行签名，并返回验证结果给所述云服务商终端400。云服务商终端400收到用户终端300的签名的验证结果和云边协同平台100的签名的验证结果后，将包含计量信息、云边协同平台的签名、云服务商终端签名的该资源视图广播至区块链平台200。区块链平台200对该资源视图进行身份许可校验和交易校验。当身份许可校验和交易校验通过时，将资源视图上链至区块链平台200。同时，用户终端300和云服务商终端400监控该资源视图是否上链至区块链平台200，并验证上链的资源视图是否正确。
在该资源视图的上链过程中，计算资源的调度方法还可以包括步骤：步骤S600，接收所述云服务商终端发送的对应所述资源调度的计量信息，并验证所述计量信息是否合法。
具体地，步骤S600可以包括以下步骤。
步骤S620，接收由所述云服务商终端发送的资源视图，所述资源视图包括所述计量信息。
步骤S640，验证所述计量信息的合法性，并向所述云服务商终端返回所述合法性的验证结果，若所述计量信息为合法，则通过所述区块链访问控制器监控所述计量信息是否上链至所述区块链平台。
图9为一个实施例中用户终端的结算账单的上链的交互示意图。在该实施例中，云边协同平台100发起结算请求，并生产账单信息，账单信息中包含云边协同平台的签名。用户终端300若同意该账单，则与云边协同平台100进行转账。转账成功后，云边协同平台100将转账的信息(包含账单、转账凭证)广播至区块链平台200。同时，用户终端300和云边协同平台100监控该转账的信息是否上链至区块链平台200。
在该结算账单的上链过程中，该计算资源的调度方法还可以包括以下步骤。
步骤S700，当获取用户结算请求时，根据所述计量信息生成用户账单信息。
步骤S720，将所述用户账单信息发送至所述用户终端。
步骤S740，若接收到由所述用户终端发送的对应所述用户账单信息的用户转账交易，则通过所述区块链访问控制器将对应所述用户转账交易的用户结算信息广播至所述区块链平台，并结束所述用户结算请求。
图10为一个实施例中云服务商终端的结算账单的上链交互示意图。图10的云服务商终端400的结算账单的上链过程与图9的用户终端300的结算账单的上链过程相似。不同之处在于图9是云边协同平台100、用户终端300和区块链平台200之间的交互，而图10是云边协同平台100、云服务商终端400和区块链平台200之间的交互，因此在这里不再赘述。
在该结算账单的上链过程中，云边协同平台还可以包括以下步骤。
步骤S800，当获取云服务商结算请求时，根据所述计量信息生成云服务商账单信息。
步骤S820，将所述云服务商账单信息发送至所述云服务商终端。
步骤S840，若接收到由所述云服务商终端发送的对应所述云服务商账单信息的确认信息，则执行对应所述云服务商账单信息的云服务商转账交易；
步骤S860，通过所述区块链访问控制器监控对应所述云服务商转账交易的云服务商结算信息是否上链至所述区块链平台，若监控到所述云服务商结算信息上链至所述区块链平台，则结束所述云服务商结算请求。
需要注意的是，步骤S860中的云服务商结算信息是由云服务商终端400发送至区块链平台200的。
图11为一个实施例中计算资源的调度系统的部署示意图。区块链平台选用hyperledger fabric，包含三类组织：云边协同平台、云服务商以及用户，每个组织都需部署Peer节点，所有组织属于同一通道(Channel)内。其中Orderer节点由云边协同平台、云服务商提供，对用户为可选项。智能合约各个模块由链码实现。
图12为一个实施例中云边协同平台侧的区块链节点的示意图。作为云边协同平台，在平台初始化时需要至少3个Orderer的节点(raft共识算法要求每个通道需要的Orderer节点数为单数)，以及2个Peer节点(Peer节点的数量需要为偶数)，以确保区块链系统可以正常运行。运行之后，云边协同平台100可以适当减少Orderer节点和Peer节点的持有量，同时将初始的链码安装并实例化。
在一个实施例中，如图13所示，提供了一种计算资源的调度装置，包括：
配置数据库，用于存储成功执行的历史调度指令；
计量信息数据库，用于存储验证过的历史计量信息；以及
区块链访问控制器，用于执行所述云边协同平台和区块链平台之间的交互。
其中，配置数据库114和计量信息数据库118分别与区块链访问控制器120通信连接，以将存储在所述配置数据库114中的成功执行的历史调度指令和储在所述计量信息数据库中的验证过的历史计量信息以定时或定量的方式发送至区块链访问控制器。区块链访问控制器120用于执行所述云边协同平台和区块链平台之间的交互。
关于计算资源的调度装置的具体限定可以参见上文中对于计算资源的调度方法的限定，在此不再赘述。上述计算资源的调度装置中的各个模块可全部或部分通过软件、硬件及其组合来实现。上述各模块可以硬件形式内嵌于或独立于计算机设备中的处理器中，也可以以软件形式存储于计算机设备中的存储器中，以便于处理器调用执行以上各个模块对应的操作。
在一个实施例中，提供了一种计算机设备，该计算机设备可以是服务器，其内部结构图可以如图14所示。该计算机设备包括通过系统总线连接的处理器、存储器、网络接口和数据库。其中，该计算机设备的处理器用于提供计算和控制能力。该计算机设备的存储器包括非易失性存储介质、内存储器。该非易失性存储介质存储有操作系统、计算机程序和数据库。该内存储器为非易失性存储介质中的操作系统和计算机程序的运行提供环境。该计算机设备的各数据库用于存储用于计算资源调度的数据。该计算机设备的网络接口用于与外部的终端通过网络连接通信。该计算机程序被处理器执行时以实现一种计算资源的调动方法。
本领域技术人员可以理解，图14中示出的结构，仅仅是与本申请方案相关的部分结构的框图，并不构成对本申请方案所应用于其上的计算机设备的限定，具体的计算机设备可以包括比图中所示更多或更少的部件，或者组合某些部件，或者具有不同的部件布置。
在一个实施例中，提供了一种计算机可读存储介质，其上存储有计算机程序，计算机程序被处理器执行时实现以下步骤：
通过所述区块链访问控制器将存储在所述配置数据库中的成功执行的历史调度指令上链至区块链平台；
通过所述区块链访问控制器将存储在所述计量信息数据库中的验证过的历史计量信息发送至区块链访问控制器120。
关于计算机可读存储介质的具体限定可以参见上文中对于计算资源的调度方法的限定，在此不再赘述。
本领域普通技术人员可以理解实现上述实施例方法中的全部或部分流程，是可以通过计算机程序来指令相关的硬件来完成，所述的计算机程序可存储于一非易失性计算机可读取存储介质中，该计算机程序在执行时，可包括如上述各方法的实施例的流程。其中，本申请所提供的各实施例中所使用的对存储器、存储、数据库或其它介质的任何引用，均可包括非易失性和/或易失性存储器。非易失性存储器可包括只读存储器(ROM)、可编程ROM(PROM)、电可编程ROM(EPROM)、电可擦除可编程ROM(EEPROM)或闪存。易失性存储器可包括随机存取存储器(RAM)或者外部高速缓冲存储器。作为说明而非局限，RAM以多种形式可得，诸如静态RAM(SRAM)、动态RAM(DRAM)、同步DRAM(SDRAM)、双数据率SDRAM(DDRSDRAM)、增强型SDRAM(ESDRAM)、同步链路(Synchlink)DRAM(SLDRAM)、存储器总线(Rambus)直接RAM(RDRAM)、直接存储器总线动态RAM(DRDRAM)、以及存储器总线动态RAM(RDRAM)等。
以上实施例的各技术特征可以进行任意的组合，为使描述简洁，未对上述 实施例中的各个技术特征所有可能的组合都进行描述，然而，只要这些技术特征的组合不存在矛盾，都应当认为是本说明书记载的范围。
以上所述实施例仅表达了本申请的几种实施方式，其描述较为具体和详细，但并不能因此而理解为对发明专利范围的限制。应当指出的是，对于本领域的普通技术人员来说，在不脱离本申请构思的前提下，还可以做出若干变形和改进，这些都属于本申请的保护范围。因此，本申请专利的保护范围应以所附权利要求为准。

Claims (18)

  1. 一种计算资源的调度方法，由云边协同平台执行，其中，所述云边协同平台包括配置数据库，计量信息数据库和区块链访问控制器，所述方法包括：
    通过所述区块链访问控制器将存储在所述配置数据库中的成功执行的历史调度指令上链至区块链平台；
    将存储在所述计量信息数据库中的验证过的第一历史计量信息发送至所述区块链访问控制器，并将所述区块链访问控制器上的所述第一历史计量信息与所述区块链平台上存储的第二历史计量信息进行验证比对。
  2. 根据权利要求1所述的方法，其中，所述成功执行的历史调度指令通过所述区块链访问控制器定时地发送至所述区块链平台。
  3. 根据权利要求1所述的方法，其中，所述第一历史计量信息通过所述区块链访问控制器定量地发送至所述区块链访问控制器。
  4. 根据权利要求1所述的方法，其中，所述云边协同平台还包括计量监控模块，所述方法还包括：
    通过所述监控计量模块监控计量操作以获取计量信息，并定时地将所述计量信息发送至所述计量信息数据库中以形成所述第一历史计量信息。
  5. 根据权利要求1所述的方法，其中，所述方法还包括：
    确定彼此匹配的用户终端的部署资源蓝图和云服务商终端的可提供资源蓝图；
    根据彼此匹配的所述部署资源蓝图和所述可提供资源蓝图，生成调度指令，并执行所述调度指令以执行资源调度；
    将所述调度指令存储至所述配置数据库以形成所述成功执行的历史调度指令。
  6. 根据权利要求5所述的方法，其中，所述确定彼此匹配的部署资源蓝图和可提供资源蓝图的步骤，包括：
    根据所述用户终端发送的所述部署资源蓝图，确定与所述部署资源蓝图相匹配的所述可提供资源蓝图，并将所述用户终端发送的所述部署资源蓝图存储至所述配置数据库以形成合法的历史部署资源蓝图；或
    根据所述云服务商终端发送的所述可提供资源蓝图，确定与所述可提供资源蓝图相匹配的所述部署资源蓝图，并将所述云服务商终端发送的所述可提供资源蓝图存储至所述配置数据库以形成合法的历史可提供资源蓝图。
  7. 根据权利要求5所述的方法，其中，所述云边协同平台还包括违约记录数据库，所述方法还包括：
    当在所述资源调度中，所述云服务商终端或所述用户终端发生违约行为时，将对应所述违约行为的违约信息存储至所述违约记录数据库；
    所述确定彼此匹配的所述用户终端的部署资源蓝图和所述云服务商终端的可提供资源蓝图的步骤，包括：
    当所述云服务商终端的所述违约信息大于第一阈值时，降低所述云服务商 终端的匹配优先级；和/或
    当所述用户终端的所述违约信息大于第二阈值时，降低所述用户终端的匹配优先级。
  8. 根据权利要求5所述的方法，其中，所述方法还包括：
    接收所述云服务商终端发送的所述可提供资源蓝图，并验证所述可提供资源蓝图的合法性。
  9. 根据权利要求8所述的方法，其中，所述接收所述云服务商终端发送的所述可提供资源蓝图，并验证所述可提供资源蓝图的合法性的步骤，包括：
    接收由所述云服务商终端发送的云服务商签约请求，所述云服务商签约请求包括所述可提供资源蓝图；
    验证所述可提供资源蓝图的合法性，向所述云服务商终端返回所述合法性的验证结果；
    若所述可提供资源蓝图为合法，则通过所述区块链访问控制器监控所述可提供资源蓝图是否由所述云服务商终端上链至所述区块链平台并同时接收由所述云服务商终端发送的所述可提供资源蓝图以执行所述资源调度；
    若监控到所述可提供资源蓝图上链至所述区块链平台，则结束所述云服务商签约请求。
  10. 根据权利要求5所述的方法，其中，所述方法还包括：
    接收所述用户终端发送的所述部署资源蓝图，并验证所述部署资源蓝图的合法性。
  11. 根据权利要求10所述的方法，其中，所述接收所述用户终端发送的所述部署资源蓝图，并验证所述部署资源蓝图的合法性的步骤，包括：
    接收由所述用户终端发送的用户签约请求，所述用户签约请求包括所述部署资源蓝图；
    验证所述部署资源蓝图的合法性，向所述用户终端返回所述合法性的验证结果；
    若所述部署资源蓝图为合法，则通过所述区块链访问控制器监控所述部署资源蓝图是否由所述用户终端上链至所述区块链平台并同时接收由所述用户端终端发送的所述部署资源蓝图以执行所述资源调度；
    若监控到所述部署资源蓝图上链至所述区块链平台，则结束所述用户签约请求。
  12. 根据权利要求5所述的方法，其中，所述方法还包括：
    接收所述云服务商终端发送的对应所述资源调度的计量信息，并验证所述计量信息是否合法。
  13. 根据权利要求12所述的方法，其中，所述接收所述云服务商终端发送的对应所述资源调度的所述计量信息，并验证所述计量信息是否合法的步骤，包括：
    接收由所述云服务商终端发送的资源视图，所述资源视图包括所述计量信息；
    验证所述计量信息的合法性，并向所述云服务商终端返回所述合法性的验证结果；
    若所述计量信息为合法，则通过所述区块链访问控制器监控所述计量信息是否上链至所述区块链平台。
  14. 根据权利要求12或13所述的方法，其中，所述方法还包括：
    当获取用户结算请求时，根据所述计量信息生成用户账单信息；
    将所述用户账单信息发送至所述用户终端；
    若接收到由所述用户终端发送的对应所述用户账单信息的用户转账交易，则通过所述区块链访问控制器将对应所述用户转账交易的用户结算信息广播至所述区块链平台，并结束所述用户结算请求。
  15. 根据权利要求12或13所述的方法，其中，所述方法还包括：
    当获取云服务商结算请求时，根据所述计量信息生成云服务商账单信息；
    将所述云服务商账单信息发送至所述云服务商终端；
    若接收到由所述云服务商终端发送的对应所述云服务商账单信息的确认信息，则执行对应所述云服务商账单信息的云服务商转账交易；
    通过所述区块链访问控制器监控对应所述云服务商转账交易的云服务商结算信息是否上链至所述区块链平台，若监控到所述云服务商结算信息上链至所述区块链平台，则结束所述云服务商结算请求。
  16. 一种计算资源的调度装置，设置于云边协同平台中，其中，所述装置包括：
    配置数据库，用于存储合法的历史部署资源蓝图、合法的历史可提供资源蓝图与成功执行的历史调度指令；
    计量信息数据库，用于存储验证过的第一历史计量信息；以及
    区块链访问控制器，用于执行所述云边协同平台和区块链平台之间的交互。
  17. 一种计算机设备，包括存储器和处理器，所述存储器存储有计算机程序，其特征在于，所述处理器执行所述计算机程序时实现权利要求1至15中任一项所述方法的步骤。
  18. 一种计算机可读存储介质，其上存储有计算机程序，其中，所述计算机程序被处理器执行时实现权利要求1至15中任一项所述的方法的步骤。
PCT/CN2020/127496 2020-11-04 2020-11-09 计算资源的调度方法、装置、计算机设备及存储介质 WO2022095022A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202011213390.2A CN112035268B (zh) 2020-11-04 2020-11-04 计算资源的调度方法、装置、计算机设备及存储介质
CN202011213390.2 2020-11-04

Publications (1)

Publication Number Publication Date
WO2022095022A1 true WO2022095022A1 (zh) 2022-05-12

Family

ID=73573206

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/127496 WO2022095022A1 (zh) 2020-11-04 2020-11-09 计算资源的调度方法、装置、计算机设备及存储介质

Country Status (2)

Country Link
CN (1) CN112035268B (zh)
WO (1) WO2022095022A1 (zh)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115733622A (zh) * 2022-11-14 2023-03-03 天津理工大学 基于区块链的云边协同安全数据共享与计算方法
CN116489224A (zh) * 2023-06-19 2023-07-25 中国联合网络通信集团有限公司 多云容器调度方法、装置、设备及存储介质

Families Citing this family (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115086331B (zh) * 2022-07-20 2024-06-07 阿里巴巴（中国）有限公司 云设备调度方法、装置及系统、电子设备及存储介质
CN116781697A (zh) * 2023-07-08 2023-09-19 武昌理工学院 基于大数据处理技术的5g信号处理系统及其方法

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107391252A (zh) * 2016-05-16 2017-11-24 阿里巴巴集团控股有限公司 一种资源处理方法及装置
CN110844394A (zh) * 2019-12-06 2020-02-28 腾讯科技（深圳）有限公司 一种基于区块链的垃圾分类激励方法及装置
US20200201683A1 (en) * 2018-12-24 2020-06-25 LiquidApps Ltd Systems and method for managing memory resources used by smart contracts of a blockchain
CN111507881A (zh) * 2020-04-20 2020-08-07 支付宝实验室(新加坡)有限公司 一种资源需求信息处理方法、装置及设备
CN111783150A (zh) * 2020-06-30 2020-10-16 北京海益同展信息科技有限公司 一种基于区块链的资源分配方法及装置

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107222303A (zh) * 2017-05-11 2017-09-29 暨南大学 基于区块链和云平台的数字版权追溯系统建设方法
CN107491947B (zh) * 2017-08-24 2020-06-02 维沃移动通信有限公司 一种资源转移方法、相关设备及系统
CN108446992A (zh) * 2018-05-11 2018-08-24 济南浪潮高新科技投资发展有限公司 一种基于区块链的网联汽车精准事故处理方法

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN107391252A (zh) * 2016-05-16 2017-11-24 阿里巴巴集团控股有限公司 一种资源处理方法及装置
US20200201683A1 (en) * 2018-12-24 2020-06-25 LiquidApps Ltd Systems and method for managing memory resources used by smart contracts of a blockchain
CN110844394A (zh) * 2019-12-06 2020-02-28 腾讯科技（深圳）有限公司 一种基于区块链的垃圾分类激励方法及装置
CN111507881A (zh) * 2020-04-20 2020-08-07 支付宝实验室(新加坡)有限公司 一种资源需求信息处理方法、装置及设备
CN111783150A (zh) * 2020-06-30 2020-10-16 北京海益同展信息科技有限公司 一种基于区块链的资源分配方法及装置

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN115733622A (zh) * 2022-11-14 2023-03-03 天津理工大学 基于区块链的云边协同安全数据共享与计算方法
CN116489224A (zh) * 2023-06-19 2023-07-25 中国联合网络通信集团有限公司 多云容器调度方法、装置、设备及存储介质
CN116489224B (zh) * 2023-06-19 2023-08-22 中国联合网络通信集团有限公司 多云容器调度方法、装置、设备及存储介质

Also Published As

Publication number Publication date
CN112035268A (zh) 2020-12-04
CN112035268B (zh) 2021-06-08

Similar Documents

Publication Publication Date Title
WO2022095022A1 (zh) 计算资源的调度方法、装置、计算机设备及存储介质
CN110598446B (zh) 基于区块链的测试方法、装置、存储介质和计算机设备
CN108961030B (zh) 关于电子票据的数据处理方法、装置、系统、介质和设备
CN111970129B (zh) 一种基于区块链的数据处理方法、设备以及可读存储介质
CN109242467B (zh) 基于区块链的组网方法、装置、计算机设备和存储介质
CN109040029B (zh) 在区块链中执行事务的方法和装置
CN109300038B (zh) 一种资源流的交易系统
CN109146483B (zh) 基于区块链网络的信用记录方法和系统
CN111080455A (zh) 基于区块链的跨境交易方法、装置及硬件设备
CN111368340A (zh) 基于区块链的通证安全校验方法、装置及硬件设备
CN113556339B (zh) 支持异构可信执行环境tee算力节点交互的隐私计算方法
CN110516417B (zh) 一种智能合约的权限验证方法及装置
CN110992178A (zh) 区块链节点的验证方法、装置、计算机设备及存储介质
CN111881483A (zh) 基于区块链的资源账户绑定方法、装置、设备和介质
CN112232822A (zh) 区块链网络的交易处理方法、节点、设备及存储介质
CN111191212B (zh) 基于区块链的数字凭证处理方法、装置、设备和存储介质
CN110851877B (zh) 一种数据处理方法、装置及区块链节点设备、存储介质
CN111292174A (zh) 一种纳税信息处理方法、装置及计算机可读存储介质
CN112235239B (zh) 基于区块链的sd-wan业务系统及其实现方法
CN110276693B (zh) 保险理赔方法及系统
CN113114629B (zh) 基于区块链的合同管理方法、装置、设备及存储介质
JP2008167406A (ja) ディジタルリソースを販売する方法および装置
CN111901359A (zh) 资源账户授权方法、装置、系统、计算机设备和介质
CN111383110A (zh) 跨区块链的通证转移方法、装置及硬件设备
US20220253841A1 (en) Method for providing neutral host network service by using blockchain, and system and device therefor

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20960480

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20960480

Country of ref document: EP

Kind code of ref document: A1