Blockchain-based scheduling decision method and system for cloud network scenarios

Abstract

This invention relates to the field of blockchain technology, providing a blockchain-based scheduling decision-making method and system for cloud network scenarios. The method is applied to a cloud network platform and includes: determining a scheduling strategy based on tasks published by cloud network terminals; obtaining a decision result based on the tasks, cloud network resource status, and the scheduling strategy; and executing the scheduling based on the decision result. The scheduling strategy is obtained after a first smart contract on the blockchain has passed a vote. This invention verifies and publishes an immutable scheduling strategy through blockchain, enabling tasks published by cloud network terminals to be scheduled securely and reliably, thus providing a foundation for open management and efficient integration of heterogeneous resources across multiple cloud networks.

Description

Technical Field

[0001] This invention relates to the field of blockchain technology, and in particular to a blockchain-based scheduling decision-making method and system for cloud network scenarios. Background Technology

[0002] In the wave of transformation from the real economy to the digital economy, various industries are rapidly integrating and permeating each other, forming a complex network of businesses. Digitalization brings more stringent requirements to business channels, competitive landscape, user experience, and many other aspects. The cloud and network that support these businesses must have more convenient and efficient service capabilities. Therefore, computing power must be deployed to the edge and endpoint, forming a vertically interconnected cloud-edge-end architecture. Furthermore, relying solely on a single cloud service makes it difficult to provide high-quality online resources to cloud users worldwide while maintaining reasonable profitability. For cloud service consumers, on the one hand, they hope to break free from the constraints of cloud platform lock-in; on the other hand, they urgently expect to access cloud resources globally on demand, efficiently, and at low cost. These demands are driving cloud services towards vertically interconnected cloud-edge-end architecture and effective collaboration among heterogeneous clouds, forming a distributed cloud architecture with a mesh-like layout—the cloud network. Distributed cloud platforms aim to lower market entry barriers for cloud network resource providers and application providers, unify the management of various heterogeneous resources, and provide efficient services to numerous entities.

[0003] In traditional cloud service scenarios, scheduling decisions are controlled by a single cloud network resource provider. The output and execution of these decisions are black boxes, lacking transparency and failing to meet the trust requirements of multi-party participation. However, in distributed cloud scenarios with multi-party participation, the trustworthiness of scheduling decisions is a critical issue. The central system responsible for overall planning in a distributed cloud platform must be able to prove its innocence, especially by ensuring the transparency, fairness, and verifiability of scheduling decisions. This is essential to attract numerous cloud network providers to the platform and to encourage cloud network resource users to purchase resources and deploy applications from it. Summary of the Invention

[0004] This invention provides a blockchain-based scheduling decision-making method and system for cloud network scenarios, which addresses the shortcomings of insufficient transparency in scheduling decision output in existing technologies, and achieves transparent, fair, and verifiable scheduling decisions.

[0005] This invention provides a blockchain-based scheduling decision-making method for cloud network scenarios, applied to a cloud network platform, including:

[0006] Determine the scheduling strategy based on the tasks issued by the cloud network terminal;

[0007] The decision result is obtained based on the task, cloud network resource status, and scheduling strategy;

[0008] Based on the decision result, execute the scheduling;

[0009] The scheduling strategy is obtained after the first smart contract on the blockchain passes a vote.

[0010] According to the present invention, a blockchain-based scheduling decision method for cloud network scenarios includes the step of obtaining a decision result based on the task, cloud network resource status, and scheduling strategy, comprising:

[0011] If the scheduling strategy is determined to be a synchronous verification scheduling strategy, then the cloud network resource status and the task are used as inputs, and the second smart contract is run through the blockchain node to execute the scheduling strategy and obtain the decision result.

[0012] According to the present invention, a blockchain-based scheduling decision method for cloud network scenarios includes the step of obtaining a decision result based on the task, cloud network resource status, and scheduling strategy, comprising:

[0013] If the scheduling strategy is determined to be an asynchronous verification scheduling strategy, then:

[0014] In the Trusted Execution Environment (TEE), based on the cloud network resource status and the task, the off-chain execution of the scheduling strategy obtains the decision result and records the decision basis.

[0015] The decision-making basis and the decision-making result are verified by running a third smart contract through the blockchain node.

[0016] According to the present invention, a blockchain-based scheduling decision-making method for cloud network scenarios includes the step of verifying the decision basis and the decision result by running a third smart contract through the blockchain node, comprising:

[0017] The third smart contract is run through the blockchain node, and the verification result is obtained based on the zero-knowledge proof information, with random parameters and the decision basis as inputs. The verification conclusion is obtained based on the verification result and the decision result.

[0018] The zero-knowledge proof information is information provided by the cloud network platform to verify the decision basis and the decision result.

[0019] According to the present invention, a blockchain-based scheduling decision-making method for cloud network scenarios includes the step of verifying the decision basis and the decision result by running a third smart contract through the blockchain node, comprising:

[0020] The third smart contract is run through the blockchain node, and the verification result is obtained based on the decision basis and the scheduling strategy, using the decision basis as input. The verification conclusion is then obtained based on the verification result and the decision result.

[0021] According to the blockchain-based scheduling decision-making method for cloud network scenarios provided by the present invention, the step of determining the scheduling strategy based on the tasks published by the cloud network terminal includes:

[0022] Based on the specified information included in the task published by the cloud network terminal, the policy that matches the specified information in the policy set is used as the scheduling policy; or,

[0023] Based on the tasks published by the cloud network terminal, select a strategy from the strategy set as the scheduling strategy;

[0024] The strategy is added to the strategy set after the first smart contract on the blockchain passes the vote.

[0025] This invention provides a blockchain-based scheduling decision-making system for cloud network scenarios, comprising:

[0026] The strategy module is used to determine the scheduling strategy based on the tasks published by the cloud network terminal;

[0027] The decision-making module is used to obtain a decision result based on the task, the cloud network resource status, and the scheduling strategy;

[0028] The scheduling module is used to perform scheduling based on the decision results;

[0029] The scheduling strategy is obtained after the first smart contract on the blockchain passes a vote.

[0030] The present invention also provides an electronic device, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the program to implement the steps of the blockchain-based scheduling decision method for cloud network scenarios as described above.

[0031] The present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon, which, when executed by a processor, implements the steps of the blockchain-based scheduling decision method for cloud network scenarios as described above.

[0032] The present invention also provides a computer program product, including a computer program that, when executed by a processor, implements the steps of the blockchain-based scheduling decision method for cloud network scenarios as described above.

[0033] The present invention provides a blockchain-based scheduling decision-making method and system for cloud network scenarios. By verifying and making the scheduling strategy public and tamper-proof through blockchain, the tasks issued by cloud network terminals can be scheduled securely and reliably, thus providing a foundation for open management and efficient integration of heterogeneous resources of multiple cloud networks. Attached Figure Description

[0034] To more clearly illustrate the technical solutions in this invention or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this invention. For those skilled in the art, other drawings can be obtained from these drawings without creative effort.

[0035] Figure 1 This is a flowchart illustrating the blockchain-based scheduling decision-making method for cloud network scenarios provided by the present invention.

[0036] Figure 2 This is a schematic diagram of the architecture of the verifiable scheduling decision system model provided in the embodiments of the present invention;

[0037] Figure 3 This is a schematic diagram of the decentralized management of the scheduling strategy provided in an embodiment of the present invention;

[0038] Figure 4 This is a schematic diagram of the synchronous verification model provided in an embodiment of the present invention;

[0039] Figure 5 This is a schematic diagram of the asynchronous verification model provided in an embodiment of the present invention;

[0040] Figure 6 This is a schematic diagram illustrating the decentralized management implementation method of the scheduling strategy provided in this embodiment of the invention;

[0041] Figure 7 This is a schematic diagram illustrating the implementation of the synchronous verification mode provided in this embodiment of the invention;

[0042] Figure 8 This is a schematic diagram illustrating an implementation method for the asynchronous verification mode provided in this invention.

[0043] Figure 9 This is a schematic diagram of the structure of the electronic device provided by the present invention;

[0044] Figure 10 This is a schematic diagram of the structure of the blockchain-based scheduling and decision-making system for cloud network scenarios provided by the present invention.

[0045] Figure label:

[0046] 1: Strategy module; 2: Decision module; 3: Scheduling module;

[0047] 910: Processor; 920: Communication interface; 930: Memory;

[0048] 940: Communication bus. Detailed Implementation

[0049] To make the objectives, technical solutions, and advantages of this invention clearer, the technical solutions of this invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of this invention. All other embodiments obtained by those skilled in the art based on the embodiments of this invention without creative effort are within the scope of protection of this invention.

[0050] The following is combined Figure 1 , Figures 6 to 8 This invention describes a blockchain-based scheduling decision-making method for cloud network scenarios.

[0051] like Figure 1 As shown, this embodiment of the invention provides a blockchain-based scheduling decision-making method for cloud network scenarios, applied to the cloud network platform, including:

[0052] Step 101: Determine the scheduling strategy based on the tasks published by the cloud network terminal;

[0053] Step 103: Based on the task, cloud network resource status, and scheduling strategy, obtain the decision result;

[0054] Step 105: Based on the decision result, execute the scheduling;

[0055] The scheduling strategy is obtained after the first smart contract on the blockchain passes a vote.

[0056] In a preferred embodiment, the nodes of the blockchain network include servers belonging to resource providers, servers belonging to resource consumers, and servers belonging to the cloud network platform; the cloud network terminals include cloud network terminals held by resource providers and / or cloud network terminals held by resource consumers; the step of determining the scheduling strategy can be based on a pre-configured set of strategies, that is, the scheduling strategy is at least one of multiple strategies included in the set of strategies.

[0057] In other words, the step of determining the scheduling strategy based on the tasks published by the cloud network terminal includes:

[0058] Based on the specified information included in the task published by the cloud network terminal, the policy that matches the specified information in the policy set is used as the scheduling policy; or,

[0059] Based on the tasks published by the cloud network terminal, select a strategy from the strategy set as the scheduling strategy;

[0060] The strategy is added to the strategy set after the first smart contract on the blockchain passes the vote.

[0061] In this implementation, each strategy in the strategy set is obtained after being voted on and approved by the first smart contract running on the blockchain. Therefore, the scheduling strategy selected or specified from the strategy set must also be a strategy obtained after being voted on and approved by the first smart contract running on the blockchain.

[0062] The initiator of the strategy vote can be either the cloud network platform or any cloud network terminal. Furthermore, the determination of the scheduling strategy is not limited to the initiator; that is, the final determined scheduling strategy may not be the strategy initiated by the cloud network terminal that issued the task as the initiator of the strategy vote. The first smart contract refers to a smart contract that uses voting by audit nodes (such as members of an audit committee) on the blockchain network to pass or reject a strategy. Policies that pass the vote are added to the strategy set (also known as the strategy pool), while strategies that are rejected are not added to the strategy set.

[0063] It is worth noting that the members of the review committee can be determined through voting or rotation; and in the first smart contract, the conditions for a vote to pass can be set as any one or any combination of the following conditions:

[0064] 1. The voting result shows that the number of nodes that passed meets the set requirements;

[0065] 2. The voting result is that the proportion of nodes that pass meets the set requirements.

[0066] 3. The number of nodes that voted against the proposal meets the set requirements;

[0067] 4. The proportion of nodes that voted against the proposal met the set requirements.

[0068] The beneficial effects of this embodiment are as follows:

[0069] By using blockchain to verify publicly tamper-proof scheduling strategies, tasks published by cloud network terminals can be scheduled securely and reliably, thus providing a foundation for open management and efficient integration of heterogeneous resources across multiple cloud networks.

[0070] Based on the above embodiments, this embodiment provides specific steps for obtaining decision results according to the scheduling strategy. The decision results in this embodiment can be obtained based on two schemes: off-chain and on-chain, as detailed below.

[0071] The on-chain solution is a synchronous verification decision-making scheme suitable for tasks with high reliability requirements and low scheduling efficiency requirements. Its core idea is to design the scheduling algorithm as a smart contract that executes directly on the blockchain. The specific steps of the on-chain solution are as follows:

[0072] The step of obtaining the decision result based on the task, cloud network resource status, and scheduling strategy includes:

[0073] If the scheduling strategy is determined to be a synchronous verification scheduling strategy, then the cloud network resource status and the task are used as inputs, and the second smart contract is run through the blockchain node to execute the scheduling strategy and obtain the decision result.

[0074] In this embodiment's on-chain solution, the execution of the second smart contract can be understood as a scheduling algorithm running on the blockchain, which can securely, reliably, and trustworthyly arrive at decision results while ensuring openness and immutability.

[0075] Off-chain solutions are asynchronous verification decision-making schemes suitable for tasks with low reliability requirements but high scheduling efficiency requirements. The core idea is that the scheduling algorithm executes in a TEE environment, and the execution of the algorithm is verified using information on the blockchain. The specific steps of the off-chain solution are as follows:

[0076] The step of obtaining the decision result based on the task, cloud network resource status, and scheduling strategy includes:

[0077] If the scheduling strategy is determined to be an asynchronous verification scheduling strategy, then:

[0078] In the Trusted Execution Environment (TEE), based on the cloud network resource status and the task, the off-chain execution of the scheduling strategy obtains the decision result and records the decision basis.

[0079] The decision-making basis and the decision-making result are verified by running a third smart contract through the blockchain node.

[0080] Furthermore, the step of verifying the decision basis and the decision result by running a third smart contract through the blockchain node includes:

[0081] The third smart contract is run through the blockchain node, and the verification result is obtained based on the zero-knowledge proof information, with random parameters and the decision basis as inputs. The verification conclusion is obtained based on the verification result and the decision result.

[0082] The zero-knowledge proof information is information provided by the cloud network platform to verify the decision basis and the decision result.

[0083] Alternatively, the step of running a third smart contract through the blockchain node to verify the decision basis and the decision result includes:

[0084] The third smart contract is run through the blockchain node, and the verification result is obtained based on the decision basis and the scheduling strategy, using the decision basis as input. The verification conclusion is then obtained based on the verification result and the decision result.

[0085] In other words, there are multiple ways to perform asynchronous verification. In this embodiment, the cloud network platform provides two verification methods: one is zero-knowledge proof, which uses zero-knowledge proof to prove whether the scheduling algorithm runs safely and correctly and whether the scheduling decision is fair and reliable without leaking privacy; the other is reproducible verification, which is that the verification node reproduces the decision-making process based on the input and output data.

[0086] Based on the idea of ​​zero-knowledge proof: Zero-knowledge proof transforms the scheduling algorithm process into an arithmetic circuit, converting the left and right inputs and output gates of its addition and multiplication gates into curves through polynomial encoding. After polynomial encoding, changing any value will cause a significant disturbance to the entire curve; therefore, proof can be achieved by randomly verifying a single point on the curve. Furthermore, to ensure the privacy of the computation process, the polynomial operations can be synchronously mapped onto an elliptic curve group, hiding the real data. Verifiers can randomly select numbers as input parameters, serving as a random number seed, and invoke the verification contract. Verification nodes invoke the decision criteria and input parameters, verifying points on the elliptic curve group through zero-knowledge proof. When multiple verification nodes verify correctly, it indicates that the scheduling algorithm executes securely and correctly, and the scheduling decision is fair and reliable.

[0087] The basic idea of ​​reproducible verification is as follows: when an entity disagrees with the scheduling decision, the verification node calls the decision basis to re-execute the scheduling strategy and compares the result with the result uploaded by the scheduling system. If the two results are consistent, it means that the scheduling system has indeed run the scheduling strategy correctly. When multiple verification nodes run and produce the same result as the scheduling system, it means that the scheduling system has correctly executed the scheduling algorithm and the scheduling decision is reliable.

[0088] The scheduling strategy corresponding to the on-chain solution should be a synchronous verification scheduling strategy, and the scheduling strategy corresponding to the off-chain solution should be an asynchronous verification scheduling strategy. That is, the scheduling strategy in the strategy pool includes information on whether the verification strategy is synchronous or asynchronous.

[0089] In some preferred implementations, the scheduling strategy does not include information on whether the verification strategy is synchronous or asynchronous, but the scheduling strategy is deployed on-chain or off-chain according to its intended verification strategy.

[0090] In on-chain solutions, since the decision-making process takes place on the blockchain, the decision-making process itself has been verified by the blockchain network nodes, so its credibility is better, but its scheduling efficiency is relatively low.

[0091] In contrast, in the off-chain solution, the decision result is obtained in the off-chain Trusted Execution Environment (TEE) and then verified on the blockchain. That is, the verification process is carried out synchronously with the scheduling process based on the decision result. The verification conclusion of the decision result is obtained during or after the scheduling execution. Therefore, its credibility is relatively weak, but the scheduling efficiency is higher.

[0092] It is worth noting that although the description uses the term "off-chain solution," this does not constitute a limitation on the off-chain solution. That is, the decision-making results in the off-chain solution are obtained off-chain, but the decision-making results and the basis for the decision still need to be verified on the blockchain.

[0093] Meanwhile, the blockchain networks in this embodiment and the previous embodiment can be the same or different.

[0094] In a scheme that uses the same blockchain network, the first smart contract, the second smart contract, and the third smart contract can be understood as either sub-contracts of the same smart contract or as independent smart contracts.

[0095] Furthermore, in schemes that use the same blockchain network, the number of smart contracts is not limited to the first smart contract, the second smart contract, and the third smart contract; that is, there may be other sub-contracts or independent smart contracts in the blockchain network.

[0096] In this embodiment, the status of cloud network resources can be obtained based on lightweight nodes deployed on the device (such as cloud network terminals), processed by a multi-party data processing center, and then uploaded to the blockchain platform and / or cloud network platform. This ensures reliable data collection from the source and avoids inconsistencies between on-chain and off-chain scheduling.

[0097] Based on any of the above embodiments, the following are examples of scheduling strategies, synchronous verification, and asynchronous verification from the perspective of cloud network platform users:

[0098] 1. Decentralized Management Implementation Example of Scheduling Strategy

[0099] The lifecycle of a scheduling policy can be divided into four phases: creation, execution, update, and deregistration. Figure 6 For example, in the scenario shown:

[0100] 1.1 Creation Process

[0101] 1) Users design and create scheduling strategies and send them to the platform;

[0102] 2) The platform uses formal verification models and testing frameworks to perform security checks on scheduling strategies;

[0103] 3) If the test passes, the platform will place the scheduling policy in the policy pool, set the status to pending review, and send the scheduling policy identifier and status to the blockchain;

[0104] 4) When the review committee detects a new scheduling policy in the policy pool, it reviews the scheduling policy. Once the policy is approved, it updates the status to "approved" in both the policy pool and the blockchain.

[0105] 5) Once the platform detects that the scheduling policy status has changed to "approved," it determines whether to execute it on the blockchain or in a TEE environment based on the complexity of the scheduling policy. If it executes on the blockchain, a smart contract is created and deployed to the blockchain; if it executes in a TEE environment, the scheduling algorithm is deployed in the TEE environment. After deployment, the scheduling policy status is updated to "runnable."

[0106] 1.2 Operation Process

[0107] 1) Users send their resource requirements and specified scheduling policy identifiers to the platform;

[0108] 2) The platform determines the deployment environment of the scheduling strategy based on the scheduling strategy identifier. If it is executed on the blockchain, the smart contract is called; if it is run in the TEE environment, the state data is transmitted to the TEE environment as input parameters.

[0109] 3) After the scheduling algorithm is executed in the blockchain, the scheduling decision is recorded on the chain. After the platform listens for the event, it initiates physical scheduling. After the scheduling algorithm is executed in the TEE environment, the platform initiates physical scheduling based on the result and sends the status data, scheduling decision, and scheduling strategy identifier to the blockchain.

[0110] 1.3 Update Process

[0111] 1) The strategy generator initiates a request to update the scheduling strategy to the platform;

[0112] 2) The platform updates the scheduling policy status to "pending review" in the policy pool and blockchain;

[0113] 3) The review committee detects the event, reviews the new scheduling strategy, and updates the scheduling strategy status to "approved" after the review is passed;

[0114] 4) After the platform detects the event, it redeploys the scheduling policy and updates it to a runnable state.

[0115] 1.4 Cancellation Process

[0116] 1) The policy initiator submits a policy cancellation request to the platform;

[0117] 2) The review committee reviews the application to cancel the scheduling strategy;

[0118] 3) If the review is approved, the platform will update the scheduling strategy status in the strategy pool and on the blockchain to "cancelled".

[0119] 2. Example of Synchronous Verification Mode

[0120] like Figure 7 As shown:

[0121] 1) When a user or cloud service provider has objections to the scheduling policy, they can initiate a verification request to the platform;

[0122] 2) After the platform verifies permissions, it obtains the scheduling basis and scheduling decisions in the blockchain and analyzes them with the actual physical scheduling results;

[0123] 3) The platform will return the analysis results to the user.

[0124] 3. Implementation Examples of Asynchronous Verification Mode

[0125] like Figure 8 As shown:

[0126] 1) When users or cloud service providers have objections to the scheduling policy, they can initiate a verification request to the platform. The verification request must include the verification mode. If the zero-knowledge proof verification method is selected, a random number must also be entered.

[0127] 2) After the platform verifies the permissions, it calls the asynchronous verification contract according to the verification mode;

[0128] 3) If the verification mode is zero-knowledge proof verification, the asynchronous verification contract will specify the points to be verified in the elliptic curve group according to the random number. Multiple verification nodes will call the decision basis and input parameters to perform verification through zero-knowledge proof and return the results to the platform. If the verification mode is reproducible verification, multiple verification nodes will call the decision basis and input parameters to re-execute the verification algorithm and return the results to the platform.

[0129] 4) The platform processes the results and returns the results to the user.

[0130] The following describes the blockchain-based scheduling decision-making device for cloud network scenarios provided by the present invention. The blockchain-based scheduling decision-making device for cloud network scenarios described below can be referred to in correspondence with the blockchain-based scheduling decision-making method for cloud network scenarios described above.

[0131] like Figure 10 As shown, this embodiment of the invention provides a blockchain-based scheduling decision system for cloud network scenarios, including:

[0132] Strategy module 1 is used to determine the scheduling strategy based on the tasks published by the cloud network terminal;

[0133] Decision module 2 is used to obtain a decision result based on the task, cloud network resource status, and scheduling strategy;

[0134] Scheduling module 3 is used to perform scheduling based on the decision results;

[0135] The scheduling strategy is obtained after the first smart contract on the blockchain passes a vote.

[0136] Furthermore, the decision module 2 includes:

[0137] The synchronization submodule is used to determine that the scheduling strategy is a synchronous verification scheduling strategy. Then, with the cloud network resource status and the task as input, the second smart contract is run through the blockchain node to execute the scheduling strategy and obtain the decision result.

[0138] The asynchronous submodule, used to determine that the scheduling strategy is an asynchronous verification scheduling strategy, then:

[0139] In the Trusted Execution Environment (TEE), based on the cloud network resource status and the task, the off-chain execution of the scheduling strategy obtains the decision result and records the decision basis.

[0140] The decision-making basis and the decision-making result are verified by running a third smart contract through the blockchain node.

[0141] Furthermore, the asynchronous submodule includes:

[0142] The zero-knowledge proof unit is used to run a third smart contract through the blockchain node, using random parameters and the decision basis as inputs, to obtain a verification result based on the zero-knowledge proof information, and to obtain a verification conclusion based on the verification result and the decision result.

[0143] The zero-knowledge proof information is information provided by the cloud network platform to verify the decision basis and the decision result.

[0144] The replication verification unit is used to run a third smart contract through the blockchain node, take the decision basis as input, obtain the verification result based on the scheduling strategy, and obtain the verification conclusion based on the verification result and the decision result.

[0145] Specifically, the strategy module 1 includes:

[0146] A designated submodule is used to select policies from the policy set that match the specified information in the task published by the cloud network terminal as scheduling policies; or,

[0147] The selected submodule is used to select a policy from the policy set as the scheduling policy based on the task published by the cloud network terminal.

[0148] The strategy is added to the strategy set after the first smart contract on the blockchain passes the vote.

[0149] The beneficial effects of this embodiment are as follows:

[0150] By using blockchain to verify publicly tamper-proof scheduling strategies, tasks published by cloud network terminals can be scheduled securely and reliably, thus providing a foundation for open management and efficient integration of heterogeneous resources across multiple cloud networks.

[0151] Based on any of the above embodiments, the following will provide a complete embodiment of a blockchain-based verifiable scheduling decision system for cloud network scenarios, from the perspective of inventive concept.

[0152] The purpose of this embodiment is to overcome the shortcomings of the prior art and design a blockchain-based verifiable scheduling decision system for cloud network scenarios, so as to ensure decentralized management of scheduling strategies and transparent and verifiable scheduling decisions in a distributed cloud platform.

[0153] The innovations of this embodiment are as follows: First, decentralized management of scheduling strategies. The distributed cloud platform aims to integrate heterogeneous resources from multiple cloud networks, adopting a relatively open management model. Scheduling strategies are flexible, customizable, and evolvable. Furthermore, the security and reliability of scheduling strategies must be guaranteed. Therefore, blockchain technology and formal verification are used to achieve a scalable, decentralized strategy pool management model, with a review committee managing the registration, review, operation, and deregistration of scheduling strategies. Second, in scenarios with high trust requirements and low scheduling efficiency requirements, blockchain technology is used to achieve synchronous verification of scheduling decisions; that is, the input, algorithm, and output of scheduling are all on the blockchain. Third, in scenarios with low trust requirements and high scheduling efficiency requirements, blockchain and TEE technology are used to achieve asynchronous verification of scheduling decisions; that is, the input and output of scheduling are on the blockchain, and the scheduling algorithm is executed in the TEE environment.

[0154] The technical solution of this embodiment is described in detail below.

[0155] like Figure 2 As shown, a full lifecycle analysis of the scheduling strategy of a distributed cloud platform is conducted, and a decentralized scheduling strategy management system is designed. From strategy registration and review to execution and deregistration, all processes are managed in a decentralized manner, with the strategy state maintained in the blockchain and strategy pool. From the perspective of the specific deployment and operation of the scheduling system, a verifiable scheduling decision-making framework is designed, enabling authorized users to verify the fairness and reliability of scheduling decisions.

[0156] Based on user preferences, scheduling decision characteristics, and the features of the blockchain system, this embodiment constructs a synchronous verification operation model and an asynchronous verification operation model. The platform breaks down the tasks to be processed and then divides them into the two operation models according to predetermined rules for scheduling decisions, ensuring that the operation process of the scheduling system is traceable and the operation results are verifiable.

[0157] First, we will introduce the decentralized management of the scheduling strategy in this embodiment.

[0158] like Figure 3As shown, in a distributed cloud platform, the scheduling decision-making module and scheduling strategy algorithm of the central system are flexible, open, customizable, and evolvable. Under this assumption, the strategy pool will be frequently and dynamically updated. To ensure that the updates and maintenance of the strategy pool are not controlled by a single party, a decentralized strategy pool management model is designed using blockchain technology. The registration, review, operation, and deregistration of scheduling strategies must be reviewed by a review committee, and each process in the lifecycle will be published on the blockchain.

[0159] Any entity on the platform can design and create scheduling strategies. After designing a new scheduling strategy, its security is tested using the platform's formal verification model and testing framework. Once the test is passed, the algorithm is transmitted to the platform and blockchain via a distributed digital identity account, and one or more attribute tags are selected for the strategy. At this point, the strategy's status is "pending review." The platform establishes a review committee, whose members can be elected by vote or rotated. The review committee reviews new strategies or requested updates. Upon successful review, the strategy's status is updated in the blockchain, and its status in the strategy pool is marked as "approved." The platform deploys approved scheduling strategies to the blockchain or TEE environment. After successful deployment, the strategy's status is updated to "runnable." Any entity can specify a scheduling strategy for its published tasks. If the user does not specify a strategy, the platform will automatically select and implement a strategy. As the platform evolves, when a strategy becomes inapplicable, an reviewer with deprecation authority marks the strategy, removes it from the strategy pool, and updates the blockchain status, thus achieving full lifecycle management of the strategy.

[0160] The synchronous verification mode of this embodiment will be introduced next.

[0161] like Figure 4 As shown, the synchronous verification operation model is that the scheduling algorithm runs in the blockchain platform, and the running results are generated directly on the chain. The synchronous verification method is suitable for tasks with high trust requirements and low scheduling efficiency requirements. The core idea is to design the scheduling algorithm as a smart contract to be executed directly on the blockchain.

[0162] In synchronous verification mode, scheduling is based on real-time status data of all resources managed by the distributed cloud platform. A lightweight node is planned to be implanted on the device side, allowing status data to be directly processed by multiple data processing centers before being uploaded to the blockchain platform. This ensures reliable data collection from the source and avoids inconsistencies between on-chain and off-chain scheduling criteria. A multi-standard scheduling smart contract is designed, with the platform calling the smart contract to output scheduling decisions based on the characteristics of subtasks. Scheduling decisions are generated directly on-chain, and the platform triggers physical scheduling upon detecting the decision's occurrence.

[0163] In synchronous verification mode, the scheduling system runs directly on the blockchain, which records the entire decision-making process, ensuring that the decision-making process is traceable and verifiable.

[0164] Finally, the asynchronous verification mode of this embodiment will be introduced.

[0165] like Figure 5 The asynchronous verification model, in this context, means that the scheduling algorithm runs off-chain, and then the blockchain verifies whether the algorithm has been executed correctly. Asynchronous verification is suitable for tasks with low reliability requirements and high scheduling efficiency requirements. The core idea is that the scheduling algorithm is executed in a TEE environment, and the execution of the algorithm is verified by information on the blockchain.

[0166] In asynchronous verification mode, scheduling is based on real-time status data of all resources. Lightweight nodes are embedded on the device, and the status data is directly processed by multiple data processing centers before being uploaded to the blockchain platform, ensuring reliable data collection from the source. The scheduling system obtains the global status from the data center, selects a suitable scheduling strategy, and makes a decision. To ensure that the algorithm's execution is not affected by external interference, the decision-making process is executed in a TEE environment. The decision basis and decision results are uploaded to the blockchain platform for storage, and the decision results trigger physical scheduling.

[0167] The beneficial effects of this embodiment are as follows:

[0168] A blockchain-based verifiable scheduling decision-making system for cloud network scenarios is designed. The system establishes a review committee to achieve decentralized management of the entire lifecycle of scheduling strategies using blockchain technology. Users can create their own scheduling strategies or adopt those from a strategy pool, enabling flexible, open, customizable, and evolving scheduling strategies. Furthermore, synchronous and asynchronous verification models can be established according to different application scenarios. The asynchronous verification model offers two verification methods: zero-knowledge proof verification and reproducible verification, based on data privacy requirements, ensuring the secure and correct execution of the scheduling algorithm and the fairness and reliability of scheduling decisions.

[0169] Figure 9 An example is a schematic diagram of the physical structure of an electronic device, such as... Figure 9 As shown, the electronic device may include a processor 910, a communications interface 920, a memory 930, and a communication bus 940. The processor 910, communications interface 920, and memory 930 communicate with each other via the communication bus 940. The processor 910 can call logical instructions in the memory 930 to execute a blockchain-based scheduling decision-making method for cloud network scenarios. This method includes: determining a scheduling strategy based on tasks published by cloud network terminals; obtaining a decision result based on the task, cloud network resource status, and the scheduling strategy; and executing the scheduling based on the decision result. The scheduling strategy is obtained after the first smart contract on the blockchain has passed a vote.

[0170] Furthermore, the logical instructions in the aforementioned memory 930 can be implemented as software functional units and, when sold or used as independent products, can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present invention, essentially, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of the present invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0171] On the other hand, the present invention also provides a computer program product, which includes a computer program that can be stored on a non-transitory computer-readable storage medium. When the computer program is executed by a processor, the computer can execute the blockchain-based scheduling decision method for cloud network scenarios provided by the above methods. The method includes: determining a scheduling strategy based on a task published by a cloud network terminal; obtaining a decision result based on the task, the cloud network resource status, and the scheduling strategy; and executing scheduling based on the decision result. The scheduling strategy is obtained after the blockchain runs a first smart contract and passes a vote.

[0172] In another aspect, the present invention also provides a non-transitory computer-readable storage medium storing a computer program thereon. When executed by a processor, the computer program implements a blockchain-based scheduling decision method for cloud network scenarios provided by the above methods. The method includes: determining a scheduling strategy based on a task published by a cloud network terminal; obtaining a decision result based on the task, the cloud network resource status, and the scheduling strategy; and executing scheduling based on the decision result. The scheduling strategy is obtained after the blockchain runs a first smart contract and passes a vote.

[0173] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Those skilled in the art can understand and implement this without any creative effort.

[0174] Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented by means of software plus necessary general-purpose hardware platforms, and of course, it can also be implemented by hardware. Based on this understanding, the above technical solutions, in essence or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in the various embodiments or some parts of the embodiments.

[0175] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of the present invention.

Claims

1. A blockchain-based scheduling decision method for cloud network scenarios, characterized in that, Applied to cloud network platforms, including: Determine the scheduling strategy based on the tasks issued by the cloud network terminal; The decision result is obtained based on the task, cloud network resource status, and scheduling strategy; Based on the decision result, execute the scheduling; The scheduling strategy is obtained after the first smart contract running on the blockchain votes to approve it. The first smart contract refers to a smart contract that uses voting by audit nodes on a blockchain network to pass or reject a strategy. The scheduling strategy is divided into on-chain scheme and off-chain scheme based on the requirements of reliability and scheduling efficiency. The on-chain solution is a synchronous verification decision-making scheme; the off-chain solution is an asynchronous verification decision-making scheme.

2. The cloud network scene-oriented blockchain-based scheduling decision method according to claim 1, characterized in that, The step of obtaining the decision result based on the task, cloud network resource status, and scheduling strategy includes: If the scheduling strategy is determined to be a synchronous verification scheduling strategy, then the scheduling strategy is executed by running a second smart contract through a blockchain node, using the cloud network resource status and the task as inputs, to obtain the decision result. 3.The cloud network scene oriented blockchain based scheduling decision method according to claim 1, characterized in that, The step of obtaining the decision result based on the task, cloud network resource status, and scheduling strategy includes: If the scheduling strategy is determined to be an asynchronous verification scheduling strategy, then: In the Trusted Execution Environment (TEE), based on the cloud network resource status and the task, the off-chain execution of the scheduling strategy obtains the decision result and records the decision basis. A third-party smart contract is run through a blockchain node to verify the decision basis and the decision result.

4. The cloud network scene-oriented blockchain-based scheduling decision method according to claim 3, characterized in that, The step of running a third smart contract through the blockchain node to verify the decision basis and the decision result includes: The third smart contract is run through the blockchain node, and the verification result is obtained based on the zero-knowledge proof information, with random parameters and the decision basis as inputs. The verification conclusion is obtained based on the verification result and the decision result. The zero-knowledge proof information is information provided by the cloud network platform to verify the decision basis and the decision result.

5. The cloud network scene-oriented blockchain-based scheduling decision method according to claim 3, characterized in that, The step of running a third smart contract through the blockchain node to verify the decision basis and the decision result includes: The third smart contract is run through the blockchain node, and the verification result is obtained based on the decision basis and the scheduling strategy, using the decision basis as input. The verification conclusion is then obtained based on the verification result and the decision result.

6. The cloud network scene oriented blockchain-based scheduling decision method according to any one of claims 1 to 5, characterized in that, The step of determining the scheduling strategy based on the tasks published by the cloud network terminal includes: Based on the specified information included in the task published by the cloud network terminal, the policy that matches the specified information in the policy set is used as the scheduling policy; or, Based on the tasks published by the cloud network terminal, select a strategy from the strategy set as the scheduling strategy; The strategy is added to the strategy set after the first smart contract on the blockchain passes the vote.

7. A blockchain-based scheduling and decision-making system for cloud network scenarios, characterized in that, include: The strategy module is used to determine the scheduling strategy based on the tasks published by the cloud network terminal; The decision-making module is used to obtain a decision result based on the task, the cloud network resource status, and the scheduling strategy; The scheduling module is used to perform scheduling based on the decision results; The scheduling strategy is obtained after the first smart contract running on the blockchain votes to approve it. The first smart contract refers to a smart contract that uses voting by audit nodes on a blockchain network to pass or reject a strategy. The scheduling strategy is divided into on-chain scheme and off-chain scheme based on the requirements of reliability and scheduling efficiency. The on-chain solution is a synchronous verification decision-making scheme; the off-chain solution is an asynchronous verification decision-making scheme.

8. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the program, it implements the steps of the blockchain-based scheduling decision method for cloud network scenarios as described in any one of claims 1 to 6.

9. A non-transitory computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the blockchain-based scheduling decision method for cloud network scenarios as described in any one of claims 1 to 6.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by the processor, it implements the steps of the blockchain-based scheduling decision method for cloud network scenarios as described in any one of claims 1 to 6.

Images