Password cloud resource pool sharing method and device and storage medium

Abstract

The present disclosure provides a cryptographic cloud resource pool sharing method and device and storage medium, relates to the technical field of communication, and solves the technical problem that in the related art, due to the fact that the device information and cryptographic resource capacity of each cryptographic cloud manufacturer involve company secrets, it is difficult to realize the sharing of cryptographic cloud resource pools of different cryptographic cloud manufacturers. The method comprises the following steps: reading a first block and determining the cryptographic cloud service requirement of a second node; the first block is used to represent the cryptographic cloud service requirement of the second node in a consortium chain; the second node is a node other than the first node in the consortium chain; in response to the fact that the cryptographic cloud resource of the first node meets the cryptographic cloud service requirement of the second node, the target cryptographic cloud resource meeting the cryptographic cloud service requirement of the second node is allocated to the second node; the resource calling interface used for sharing the target cryptographic cloud resource is determined; and the identifier of the resource calling interface is written in the first block. The present disclosure is used for the cryptographic cloud resource pool sharing scene.

Description

TECHNICAL FIELD

[0001] The present disclosure relates to the technical field of communication, and particularly relates to a password cloud resource pool sharing method and device and storage medium. BACKGROUND

[0002] The password cloud service is a service of storing and managing passwords through the cloud, and the password cloud constructs a virtual password resource pool based on a password device, creates a password security service component through a password security image, and thus quickly deploys and constructs password security capabilities to guarantee business security. A user can store his / her own passwords in a cloud server and access and share the passwords at any time and anywhere through a mobile device or a computer.

[0003] With the increasing demand for password cloud services, the password resource pool of a password cloud vendor in a certain password cloud service area is difficult to meet the password cloud service demand of a customer, which requires multiple password cloud vendors to share the password cloud resource pool to meet the password cloud service demand of the customer. However, since the device information and password resource capabilities of each password cloud vendor involve company secrets, it is difficult to realize the sharing of the password cloud resource pool of different password cloud vendors. SUMMARY

[0004] The present disclosure provides a password cloud resource pool sharing method and device and storage medium, and solves the technical problem that the device information and password resource capabilities of each password cloud vendor involve company secrets, and it is difficult to realize the sharing of the password cloud resource pool of different password cloud vendors.

[0005] To achieve the above object, the present disclosure adopts the following technical solutions:

[0006] In a first aspect, a password cloud resource pool sharing method is provided, applied to a first node in a consortium chain, the nodes in the consortium chain being password cloud resource pool nodes, and the method comprising: reading a first block to determine a password cloud service demand of a second node; the first block being used to represent the password cloud service demand of the second node in the consortium chain; the second node being a node other than the first node in the consortium chain; in response to the password cloud resource of the first node meeting the password cloud service demand of the second node, allocating target password cloud resources meeting the password cloud service demand of the second node to the second node; determining a resource calling interface used to share the target password cloud resources; and writing an identifier of the resource calling interface in the first block.

[0007] With the first aspect above, in a possible implementation, after the identification of the resource calling interface is written in the first block, the method further includes: in response to a sharing request of the target cryptographic cloud resource, sharing the target cryptographic cloud resource to the second node based on the resource calling interface; updating the shared resource directory in the second block based on the category and the quantity of the shared target cryptographic cloud resource; the shared resource directory is used to record the sharable cryptographic cloud resource information of the nodes in the alliance chain; and the second block is used to record the information of the nodes in the alliance chain.

[0008] With the first aspect above, in a possible implementation, the method further includes: in response to a sharing end request of the target cryptographic cloud resource, stopping sharing the target cryptographic cloud resource to the second node; and updating the shared resource directory in the second block based on the category and the quantity of the target cryptographic cloud resource after the sharing ends.

[0009] With the first aspect above, in a possible implementation, before the shared resource directory in the second block is updated, the method further includes: writing the shared resource directory into the second block; and the shared resource directory at least includes one of the following: the identification of the first node, the resource category and the quantity information of the cryptographic cloud resource pool of the first node.

[0010] With the first aspect above, in a possible implementation, the cryptographic cloud service demand of the second node at least includes one of the following: the resource demand type of the second node, the resource demand quantity of the second node, the resource calling interface field, and the identification of the second node; and the method specifically includes: in a case where the cryptographic cloud resource of the first node meets the cryptographic cloud service demand of the second node, obtaining the resource demand type of the second node and the resource demand quantity of the second node; and allocating the target cryptographic cloud resource to the second node based on the resource demand type of the second node and the resource demand quantity of the second node.

[0011] With the first aspect above, in a possible implementation, the method further includes: receiving a cryptographic cloud service request from a user terminal; the cryptographic cloud service request includes the resource type and the resource quantity required by the cryptographic cloud service; and in a case where the cryptographic cloud resource of the first node cannot meet the cryptographic cloud service demand of the user terminal, writing the cryptographic cloud service demand of the first node into the first block.

[0012] In conjunction with the first aspect above, in one possible implementation, the target cryptographic cloud resource usage information includes at least one of the following: resource type, resource usage time, resource usage quantity, and second node identifier. The method further includes: obtaining the second node's usage information of the target cryptographic cloud resource; determining the second node for settling usage fees based on the second node identifier; and settling the resource type, resource usage time, and resource usage quantity based on the pre-set fee terms in the smart contract to determine the cryptographic cloud resource usage fee for the second node.

[0013] Secondly, a cryptographic cloud resource pool sharing device is provided, the device comprising: a processing unit; the processing unit being configured to read a first block and determine the cryptographic cloud service requirements of a second node; the first block being used to characterize the cryptographic cloud service requirements of the second node in a consortium blockchain; the second node being a node other than the first node in the consortium blockchain; the processing unit being configured to, in response to the first node's cryptographic cloud resources satisfying the second node's cryptographic cloud service requirements, allocate target cryptographic cloud resources that satisfy the second node's cryptographic cloud service requirements to the second node; the processing unit being configured to determine a resource call interface for sharing the target cryptographic cloud resources; and the processing unit being configured to write an identifier of the resource call interface into the first block.

[0014] In conjunction with the second aspect above, in one possible implementation, after writing the identifier of the resource call interface into the first block, the processing unit is further configured to: respond to the sharing request of the target cryptographic cloud resource, share the target cryptographic cloud resource with the second node based on the resource call interface; update the shared resource directory in the second block based on the type and quantity of the shared target cryptographic cloud resource; the shared resource directory is used to record the shareable cryptographic cloud resource information of the nodes in the consortium blockchain; the second block is used to record the information of the nodes in the consortium blockchain.

[0015] In conjunction with the second aspect above, in one possible implementation, the processing unit is further configured to: stop sharing the target cryptographic cloud resource with the second node in response to the request to end sharing the target cryptographic cloud resource; and update the shared resource directory in the second block based on the type and quantity of the target cryptographic cloud resource after the sharing ends.

[0016] In conjunction with the second aspect above, in one possible implementation, before updating the shared resource directory in the second block, the processing unit is further configured to: write the shared resource directory into the second block; the shared resource directory includes at least one of the following: the identifier of the first node, and information on the types and quantities of resources available from the first node's cryptographic cloud resource pool.

[0017] In conjunction with the second aspect above, in one possible implementation, the cryptographic cloud service requirements of the second node include at least one of the following: the resource requirement type of the second node, the resource requirement quantity of the second node, the resource call interface field, and the identifier of the second node; the device further includes: a communication unit; and a processing unit, specifically configured to: when it is determined that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirements of the second node, instruct the communication unit to obtain the resource requirement type and the resource requirement quantity of the second node; and allocate target cryptographic cloud resources to the second node based on the resource requirement type and the resource requirement quantity of the second node.

[0018] In conjunction with the second aspect above, in one possible implementation, the processing unit is further configured to: instruct the communication unit to receive a cryptographic cloud service request from the user terminal; the cryptographic cloud service request includes: the type and quantity of resources required for the cryptographic cloud service; and, if it is determined that the cryptographic cloud resources of the first node cannot meet the cryptographic cloud service requirements of the user terminal, write the cryptographic cloud service requirements of the first node into the first block.

[0019] In conjunction with the second aspect above, in one possible implementation, the target cryptographic cloud resource usage information includes at least one of the following: resource type, resource usage time, resource usage quantity, and second node identifier; the processing unit is further configured to instruct the communication unit to obtain the second node's target cryptographic cloud resource usage information; determine the second node for settling usage fees based on the second node identifier; and, based on the pre-set fee terms in the smart contract, settle the resource type, resource usage time, and resource usage quantity to determine the cryptographic cloud resource usage fee for the second node.

[0020] Thirdly, a cryptographic cloud resource pool sharing device is provided, comprising: a processor and a memory; wherein the memory is used to store computer execution instructions, and when the cryptographic cloud resource pool sharing device is running, the processor executes the computer execution instructions stored in the memory to cause the cryptographic cloud resource pool sharing device to perform the cryptographic cloud resource pool sharing method as described in the first aspect and any possible implementation thereof.

[0021] Fourthly, a computer-readable storage medium is provided, which stores instructions that, when executed by a processor of a cryptographic cloud resource pool sharing device, cause the cryptographic cloud resource pool sharing device to perform the cryptographic cloud resource pool sharing method as described in the first aspect above and any possible implementation thereof.

[0022] Fifthly, a chip is provided, the chip including a processor and a communication interface, the communication interface and the processor being coupled, the processor being used to run computer programs or instructions to implement the cryptographic cloud resource pool sharing method as described in the first aspect above and any possible implementation thereof.

[0023] In this disclosure, the name of the aforementioned cryptographic cloud resource pool sharing device does not limit the device or functional module itself. In actual implementation, these devices or functional modules may appear under other names. As long as the functions of each device or functional module are similar to those of this disclosure, they fall within the scope of this disclosure and its equivalents.

[0024] The technical solution provided in this disclosure brings at least the following beneficial effects: This disclosure provides a method for sharing a cryptographic cloud resource pool, the method comprising: reading a first block to determine the cryptographic cloud service requirements of a second node; the first block is used to characterize the cryptographic cloud service requirements of the second node in the consortium blockchain; the second node is a node other than the first node in the consortium blockchain; that is, reading the cryptographic cloud service requirements in the first block; in response to the cryptographic cloud resources of the first node satisfying the cryptographic cloud service requirements of the second node, allocating target cryptographic cloud resources that satisfy the cryptographic cloud service requirements of the second node to the second node; when it is determined that the first node can satisfy the cryptographic cloud requirements of the second node, allocating target cryptographic cloud resources that satisfy the cryptographic cloud service requirements of the second node to the second node; determining a resource call interface for sharing the target cryptographic cloud resources; writing the identifier of the resource call interface into the first block; determining the resource call interface for sharing the target cryptographic cloud resources based on the target cryptographic cloud resources, and writing the identifier of the resource call interface into the first block. In this way, the second node can read the identifier of the resource call interface in the first block and call the target cryptographic cloud resource through the resource call interface, thereby realizing the sharing of cryptographic cloud resources among nodes in the consortium blockchain. This solves the technical problem that the equipment information and cryptographic resource capabilities of various cryptographic cloud vendors involve company secrets and it is difficult to achieve the sharing of cryptographic cloud resource pools of different cryptographic cloud vendors. Attached Figure Description

[0025] To more clearly illustrate the technical solutions in the embodiments of this disclosure or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below.

[0026] Figure 1 This is a schematic diagram of the structure of a cryptographic cloud resource pool sharing system provided in an embodiment of the present disclosure;

[0027] Figure 2 This is a schematic diagram of the hardware structure of a cryptographic cloud resource pool sharing device provided in an embodiment of the present disclosure;

[0028] Figure 3 A flowchart illustrating a cryptographic cloud resource pool sharing method provided in this embodiment of the disclosure;

[0029] Figure 4 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0030] Figure 5 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0031] Figure 6 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0032] Figure 7 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0033] Figure 8 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0034] Figure 9 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0035] Figure 10 A flowchart illustrating yet another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure;

[0036] Figure 11 This is a schematic diagram of the structure of a cryptographic cloud resource pool sharing device provided in an embodiment of this disclosure. Detailed Implementation

[0037] The following describes in detail, with reference to the accompanying drawings, a method, apparatus, and storage medium for sharing a cryptographic cloud resource pool provided in this disclosure.

[0038] In this article, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, A and / or B can represent three situations: A exists alone, A and B exist simultaneously, and B exists alone.

[0039] The terms “first” and “second” in this disclosure and its accompanying drawings are used to distinguish different objects or to distinguish different treatments of the same object, rather than to describe a particular order of objects.

[0040] Furthermore, the terms "comprising" and "having," and any variations thereof, used in the description of this disclosure are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include other steps or units not listed, or may optionally include other steps or units inherent to such processes, methods, products, or apparatus. It should be noted that in the embodiments of this disclosure, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this disclosure should not be construed as preferred or advantageous over other embodiments or designs. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0041] In the description of this disclosure, unless otherwise stated, "multiple" means two or more.

[0042] Cryptographic cloud service is a service that stores and manages passwords in the cloud. It builds a virtualized cryptographic resource pool based on cryptographic devices and creates cryptographic security service components through cryptographic security images, thereby quickly deploying and building cryptographic security capabilities to ensure business security. Users can store their passwords on cloud servers and access and share them anytime, anywhere via mobile devices or computers. With the increasing demand for cryptographic cloud services, the cryptographic resource pools of a single cryptographic cloud provider in a particular service region may be insufficient to meet customer needs. This necessitates multiple cryptographic cloud providers sharing a cryptographic cloud resource pool to satisfy customer demands. However, due to the confidentiality of equipment information and cryptographic resource capabilities among different cryptographic cloud providers, sharing cryptographic cloud resource pools from different providers is difficult.

[0043] To address the aforementioned technical problems, this disclosure provides a method, apparatus, and storage medium for sharing cryptographic cloud resource pools. This addresses the technical issue that the sharing of cryptographic cloud resource pools from different cryptographic cloud vendors is difficult due to the involvement of company secrets in the equipment information and cryptographic resource capabilities of various cryptographic cloud vendors. Applied to a first node in a consortium blockchain, where the nodes in the consortium blockchain are cryptographic cloud resource pool nodes, the method includes: reading a first block to determine the cryptographic cloud service requirements of a second node; the first block represents the cryptographic cloud service requirements of the second node in the consortium blockchain; the second node is a node other than the first node in the consortium blockchain; that is, reading the cryptographic cloud service requirements in the first block; in response to the first node's cryptographic cloud resources satisfying the second node's cryptographic cloud service requirements, allocating target cryptographic cloud resources that satisfy the second node's cryptographic cloud service requirements to the second node; and, if it is determined that the first node can satisfy the second node's cryptographic cloud requirements, allocating cryptographic cloud resources that satisfy the second node's cryptographic cloud service requirements to the second node. The service requires target cryptographic cloud resources; the resource call interface for sharing the target cryptographic cloud resources is determined; the identifier of the resource call interface is written into the first block; based on the target cryptographic cloud resources, the resource call interface for sharing the target cryptographic cloud resources is determined, and the identifier of the resource call interface is written into the first block, so that the second node can read the identifier of the resource call interface and call the target cryptographic cloud resources through the resource call interface; in this way, the sharing of cryptographic cloud resources among nodes in the consortium blockchain is realized, thereby solving the technical problem that the equipment information and cryptographic resource capabilities of various cryptographic cloud vendors involve company secrets, making it difficult to achieve the sharing of cryptographic cloud resource pools of different cryptographic cloud vendors.

[0044] In one possible implementation, the aforementioned cryptographic cloud resource pool sharing method can be applied to the cryptographic cloud resource pool sharing system 100. The following, in conjunction with... Figure 1 This application provides a detailed description of a cryptographic cloud resource pool sharing system 100 according to embodiments. For example... Figure 1 As shown, Figure 1 A cryptographic cloud resource pool sharing system 100 is provided for embodiments of this disclosure. The system includes: a cryptographic cloud resource pool sharing device 101 applied to a first node and a cryptographic cloud resource pool sharing device 102 applied to a second node.

[0045] The cryptographic cloud resource pool sharing device 101 applied to the first node is used to read the first block and determine the cryptographic cloud service requirements of the second node. The first block is used to represent the cryptographic cloud service requirements of the second node in the consortium blockchain. The second node is a node other than the first node in the consortium blockchain. In response to the cryptographic cloud resources of the first node meeting the cryptographic cloud service requirements of the second node, the device allocates target cryptographic cloud resources that meet the cryptographic cloud service requirements of the second node. It determines the resource call interface for sharing the target cryptographic cloud resources and writes the identifier of the resource call interface into the first block.

[0046] The cryptographic cloud resource pool sharing device 102 applied to the second node is used to read the resource call interface identifier in the first block, generate a resource call interface based on the resource call interface identifier, and call the target cryptographic cloud resource.

[0047] In one possible implementation, the hardware structure of the cryptographic cloud resource pool sharing device includes: Figure 2 The components included in the cryptographic cloud resource pool sharing device 200 shown below are described in detail below. Figure 2 The hardware structure of the cryptographic cloud resource pool sharing device is illustrated using the cryptographic cloud resource pool sharing device 200 as an example. Figure 2 As shown, the cryptographic cloud resource pool sharing device 200 includes at least one processor 201, a communication line 202, and at least one communication interface 204, and may also include a memory 203. The processor 201, memory 203, and communication interface 204 can be connected via the communication line 202.

[0048] The processor 201 may be a central processing unit (CPU), an application-specific integrated circuit (ASIC), or one or more integrated circuits configured to implement embodiments of the present disclosure, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0049] Communication line 202 may include a path for transmitting information between the aforementioned components.

[0050] The communication interface 204 is used to communicate with other devices or communication networks. It can use any transceiver-like device, such as Ethernet, radio access network (RAN), wireless local area network (WLAN), etc.

[0051] The memory 203 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of including or storing desired program code having the form of instructions or data structures and accessible by a computer, but not limited thereto.

[0052] In one possible design, the memory 203 can exist independently of the processor 201, meaning the memory 203 can be an external memory of the processor 201. In this case, the memory 203 can be connected to the processor 201 via the communication line 202 to store execution instructions or application code, and its execution is controlled by the processor 201 to implement the cryptographic cloud resource pool sharing method provided in the following embodiments of this disclosure. In another possible design, the memory 203 can also be integrated with the processor 201, meaning the memory 203 can be an internal memory of the processor 201. For example, the memory 203 can be a cache, which can be used to temporarily store some data and instruction information.

[0053] As one possible implementation, processor 201 may include one or more CPUs, for example Figure 2 CPU0 and CPU1 in the example. As another possible implementation, the cryptographic cloud resource pool sharing device 200 may include multiple processors, such as... Figure 2 The processors 201 and 207 are included. As another possible implementation, the cryptographic cloud resource pool sharing device 200 may also include an output device 205 and an input device 206.

[0054] The following provides a detailed description of a cryptographic cloud resource pool sharing method provided in the embodiments of this disclosure.

[0055] like Figure 3 As shown, Figure 3 This disclosure provides a method for sharing a cryptographic cloud resource pool, which can be applied to, for example... Figure 2 The method in the cryptographic cloud resource pool sharing device shown includes the following steps S301-S304, which will be described in detail below.

[0056] S301. The cryptographic cloud resource pool sharing device reads the first block to determine the cryptographic cloud service requirements of the second node.

[0057] The first block represents the cryptographic cloud service needs of the second node in the consortium blockchain; the second node is a node other than the first node in the consortium blockchain.

[0058] In one possible implementation, the cryptographic cloud resource pool sharing device obtains the cryptographic cloud service requests from other nodes in the consortium blockchain from the first block.

[0059] It is understandable that the cryptographic cloud requirement is a cryptographic cloud service requirement written into the first block when other nodes cannot meet the user's cryptographic cloud business needs in their local cryptographic cloud resource pool.

[0060] S302, the cryptographic cloud resource pool sharing device responds to the fact that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirements of the second node, and allocates target cryptographic cloud resources that meet the cryptographic cloud service requirements of the second node.

[0061] In one possible implementation, the cryptographic cloud resource pool sharing device allocates the target cryptographic cloud resources required by the second node to the second node when it determines that the cryptographic cloud resources that the first node can share meet the cryptographic cloud service requirements of the second node.

[0062] For example, the cryptographic cloud resource pool sharing device obtains the types and quantities of cryptographic cloud resources required by the second node's cryptographic cloud service needs, determines that the cryptographic cloud resources that the first node can share can meet the cryptographic cloud service needs of the second node, and allocates the target cryptographic cloud resources required by the second node's cryptographic cloud service to the second node.

[0063] S303, The cryptographic cloud resource pool sharing device determines the resource call interface used for sharing the target cryptographic cloud resources.

[0064] In one possible implementation, the cryptographic cloud resource pool sharing device determines the type of the target cryptographic cloud resource and the location of the target cryptographic cloud, and then determines the resource call interface for sharing the target cryptographic cloud resource.

[0065] S304. The password cloud resource pool sharing device writes the identifier of the resource call interface in the first block.

[0066] In one possible implementation, the cryptographic cloud resource pool sharing device writes the identifier field of the resource call interface of the shared target cryptographic cloud resource into the first block.

[0067] Understandably, the second node can read the identifier of the resource call interface from the first block, generate a resource call interface based on the identifier, and call the target cryptographic cloud resource through the resource call interface.

[0068] The technical solution provided by the above embodiments can bring at least the following beneficial effects: reading the first block to determine the cryptographic cloud service requirements of the second node; the first block is used to characterize the cryptographic cloud service requirements of the second node in the consortium blockchain; the second node is a node other than the first node in the consortium blockchain; that is, reading the cryptographic cloud service requirements in the first block; in response to the first node's cryptographic cloud resources satisfying the second node's cryptographic cloud service requirements, allocating target cryptographic cloud resources that satisfy the second node's cryptographic cloud service requirements to the second node; when it is determined that the first node can satisfy the second node's cryptographic cloud requirements, allocating target cryptographic cloud resources that satisfy the second node's cryptographic cloud service requirements to the second node; determining a resource call interface for sharing the target cryptographic cloud resources; writing the identifier of the resource call interface in the first block; determining the resource call interface for sharing the target cryptographic cloud resources based on the target cryptographic cloud resources, and writing the identifier of the resource call interface in the first block. In this way, the second node can read the identifier of the resource call interface in the first block and call the target cryptographic cloud resource through the resource call interface, thereby realizing the sharing of cryptographic cloud resources among nodes in the consortium blockchain. This solves the technical problem that the equipment information and cryptographic resource capabilities of various cryptographic cloud vendors involve company secrets and it is difficult to achieve the sharing of cryptographic cloud resource pools of different cryptographic cloud vendors.

[0069] One possible implementation is, such as Figure 4 As shown, after the above-mentioned S304 and the password cloud resource pool sharing device write the identifier of the resource call interface in the first block, it is also necessary to update the shared resource directory in the second block. This process can be implemented through the following S401-S402, which will be explained in detail below.

[0070] S401, the cryptographic cloud resource pool sharing device responds to the sharing request of the target cryptographic cloud resource and shares the target cryptographic cloud resource with the second node based on the resource call interface.

[0071] In one possible implementation, the second node reads the identifier of the resource call interface from the first block and generates a resource call interface based on the identifier. The cryptographic cloud resource pool sharing device responds to the sharing request of the target cryptographic cloud resource and shares the target cryptographic cloud resource with the second node based on the resource call interface.

[0072] In one possible implementation, the resource access interface is an Application Programming Interface (API).

[0073] S402, The cryptographic cloud resource pool sharing device updates the shared resource catalog in the second block based on the type and quantity of the shared target cryptographic cloud resources.

[0074] The shared resource directory records information about shareable cryptographic cloud resources of nodes in the consortium blockchain. The second block records information about the nodes in the consortium blockchain.

[0075] In one possible implementation, the shared resource directory records the shareable cryptographic cloud resource information of all nodes in the consortium blockchain. When the first node shares the target cryptographic cloud resource with the second node, the shared resource directory in the second block needs to be updated according to the shared target cryptographic cloud resource.

[0076] The technical solution provided by the above embodiments can bring at least the following beneficial effects: In response to the sharing request of the target cryptographic cloud resource, the cryptographic cloud resource pool sharing device shares the target cryptographic cloud resource with the second node based on the resource call interface. Based on the type and quantity of the shared target cryptographic cloud resource, it updates the shared resource directory in the second block used to record the shareable cryptographic cloud resource information of the nodes in the consortium chain, so as to avoid other nodes in the consortium chain repeatedly sending cryptographic cloud service requests to the first node.

[0077] One possible implementation is, such as Figure 5 As shown, when the first node stops sharing the target cryptographic cloud resources with the second node, the shared resource directory in the second block needs to be updated. This process can be specifically determined through the following S501-S502, which will be explained in detail below.

[0078] S501, In response to the request to end the sharing of the target cryptographic cloud resource, the cryptographic cloud resource sharing device stops sharing the target cryptographic cloud resource with the second node.

[0079] In one possible implementation, when the local cryptographic cloud resource pool of the second node can meet the user's cryptographic cloud service needs, a sharing termination request is sent to the first target node. In response to the sharing termination request of the target cryptographic cloud resource, the cryptographic cloud resource pool sharing device stops sharing the target cryptographic cloud resource with the second node.

[0080] S502, the cryptographic cloud resource pool sharing device updates the shared resource catalog in the second block based on the type and quantity of the target cryptographic cloud resources after the sharing ends.

[0081] In one possible implementation, after the sharing ends, the cryptographic cloud resource pool sharing device reclaims the unused cryptographic cloud resources of the second node and updates the shared resource catalog in the second block based on the types and quantities of the unused cryptographic cloud resources.

[0082] The technical solution provided by the above embodiments can bring at least the following beneficial effects: In response to the sharing end request of the target cryptographic cloud resource, the cryptographic cloud resource sharing device stops sharing the target cryptographic cloud resource with the second node, and updates the shared resource catalog in the second block based on the types and quantities of unused cryptographic cloud resources.

[0083] In one possible implementation, combining Figure 4 ,like Figure 6 As shown, the shared resource directory needs to be built before updating the shared resource directory in the second block. This process can be implemented through the following S601, which will be explained in detail below.

[0084] S601, the password cloud resource pool sharing device writes the shared resource directory into the second block.

[0085] The shared resource directory shall include at least one of the following: the identifier of the first node, the types and quantities of resources available from the first node's cryptographic cloud resource pool.

[0086] In one possible implementation, the cryptographic cloud resource pool sharing device writes the shared resource directory of all nodes in the consortium blockchain into the second block.

[0087] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the cryptographic cloud resource pool sharing device writes the shared resource directory into the second block, so that the nodes in the consortium chain can determine the nodes with the cryptographic cloud resources required by the node based on the shared resource directory, and send the cryptographic cloud service request to the node.

[0088] In one possible implementation, the cryptographic cloud service requirements of the second node include at least one of the following: the resource requirement type of the second node, the quantity of resources required by the second node, the resource call interface field, and the identifier of the second node. Combined with... Figure 3 ,like Figure 7 As shown, the above-mentioned S302, the process of the cryptographic cloud resource pool sharing device allocating target cryptographic cloud resources that meet the cryptographic cloud service requirements of the second node in response to the cryptographic cloud resources of the first node meeting the cryptographic cloud service requirements of the second node, can be specifically implemented through the following S701-S702, which will be described in detail below.

[0089] S701, when the cryptographic cloud resource pool sharing device determines that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirements of the second node, it obtains the resource requirement type and the resource requirement quantity of the second node.

[0090] In one possible implementation, the cryptographic cloud resource pool sharing device reads the shared resource directory of the first node in the second block, and determines, based on the shared resource directory of the first node, whether the cryptographic cloud of the first node meets the cryptographic cloud service requirements of the second node.

[0091] In one possible implementation, the cryptographic cloud resource pool sharing device, after determining that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirements of the second node, obtains the resource requirement type and the resource requirement quantity of the second node from the cryptographic cloud service requirements.

[0092] S702, the cryptographic cloud resource pool sharing device allocates target cryptographic cloud resources to the second node based on the resource demand type and resource demand quantity of the second node.

[0093] In one possible implementation, after obtaining the resource requirement type and resource requirement quantity of the second node, the cryptographic cloud resource pool sharing device determines the target cryptographic cloud resource with the same resource requirement type as the second node from the local cryptographic cloud resource pool, and allocates the target cryptographic cloud resource to the second node according to the resource requirement quantity.

[0094] The technical solution provided by the above embodiments can bring at least the following beneficial effects: When the cryptographic cloud resource pool sharing device determines that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirements of the second node, it obtains the resource requirement type and the resource requirement quantity of the second node, and allocates target cryptographic cloud resources to the second node based on the resource requirement type and the resource requirement quantity of the second node, so that the second node can meet the user's cryptographic cloud business requirements through the target cryptographic cloud resources.

[0095] One possible implementation is, such as Figure 8 As shown, when the first node cannot meet the password cloud service request of the user terminal, the password cloud service request of the first node needs to be written into the first block. This process can be implemented through the following S801-S802, which will be explained in detail below.

[0096] S801, The password cloud resource pool sharing device receives a password cloud service request from a user terminal.

[0097] In one possible implementation, the cryptographic cloud service request includes: the type and quantity of resources required by the cryptographic cloud service.

[0098] S802. When the cryptographic cloud resource pool sharing device determines that the cryptographic cloud resources of the first node cannot meet the cryptographic cloud service needs of the user terminal, it writes the cryptographic cloud service needs of the first node into the first block.

[0099] In one possible implementation, the cryptographic cloud resource pool sharing device receives a cryptographic cloud service request from a user terminal. If it determines that the resource type of the local cryptographic cloud resource pool cannot meet the cryptographic cloud service needs of the user terminal, it writes the cryptographic cloud service request of the first node into the first block, so that other nodes in the consortium blockchain can share cryptographic cloud resources with the first node based on the cryptographic cloud service request of the first node.

[0100] In one possible implementation, the cryptographic cloud resource pool sharing device receives a cryptographic cloud service request from a user terminal. If it is determined that the amount of resources in the local cryptographic cloud resource pool cannot meet the cryptographic cloud service needs of the user terminal, the device writes the cryptographic cloud service request of the first node into the first block, so that other nodes in the consortium blockchain can share cryptographic cloud resources with the first node based on the first node's cryptographic cloud service request.

[0101] The technical solution provided by the above embodiments can bring at least the following beneficial effects: When the cryptographic cloud resource pool sharing device receives a cryptographic cloud service request from a user terminal, and determines that the types and / or quantities of resources in the local cryptographic cloud resource pool cannot meet the cryptographic cloud service needs of the user terminal, it writes the cryptographic cloud service requirements of the first node into the first block, so that other nodes in the consortium blockchain can share cryptographic cloud resources with the first node based on the cryptographic cloud service requirements of the first node.

[0102] In one possible implementation, the target cryptographic cloud resource usage information includes at least one of the following: resource type, resource usage time, resource usage quantity, and second node identifier; such as... Figure 9 As shown, after the second node uses the target cryptographic cloud resource, it is necessary to settle the usage fee for the target cryptographic cloud resource. This process can be implemented through the following S901-S903, which will be explained in detail below.

[0103] S901, The cryptographic cloud resource pool sharing device obtains the second node's usage information of the target cryptographic cloud resources.

[0104] In one possible implementation, the cryptographic cloud resource pool sharing device obtains the type of resources used by the second node, the time of resource use, and the quantity of resources used.

[0105] S902, the password cloud resource pool sharing device determines the second node for settling usage fees based on the second node identifier.

[0106] In one possible implementation, the cryptographic cloud resource pool sharing device determines the second node for settling usage fees based on the second node identifier in the cryptographic cloud resource usage information.

[0107] S903, the cryptographic cloud resource pool sharing device, based on the pre-set fee terms in the smart contract, settles the resource type, resource usage time, and resource quantity used to determine the cryptographic cloud resource usage fee for the second node.

[0108] In one possible implementation, the smart contract pre-sets relevant billing rules regarding the type of cryptographic cloud resources, the time of resource usage, and the quantity of resources used. The cryptographic cloud resource pool sharing device settles the usage fees for the second node based on the pre-set fee terms in the smart contract, including the type of resource used, the time of resource usage, and the quantity of resources used.

[0109] The technical solution provided by the above embodiments can bring at least the following beneficial effects: the cryptographic cloud resource pool sharing device settles the resource type, resource time, and resource quantity based on the preset fee terms in the smart contract, and determines the cryptographic cloud resource usage fee of the second node; so that the nodes in the consortium chain can settle the usage fee of the cryptographic cloud shared resources after using them.

[0110] One possible implementation is, such as Figure 10 As shown, Figure 10 This is a flowchart illustrating another method for sharing a cryptographic cloud resource pool provided in this embodiment of the present disclosure; the process specifically includes the following S1001-S1008, which will be described in detail below.

[0111] S1001, the password cloud resource pool sharing device received a new business request.

[0112] S1002. The password cloud resource pool sharing device determines whether the local password cloud resource pool meets the new business requirements. If yes, execute S1003; otherwise, execute S1004.

[0113] S1003, the password cloud resource pool sharing device connects with new services using local resources.

[0114] S1004. The cryptographic cloud resource pool sharing device writes the required cryptographic cloud resource information to the first block and updates the cryptographic cloud service requirements in the first block.

[0115] S1005, The cryptographic cloud resource pool sharing device identifies nodes that can meet the needs of cryptographic cloud services.

[0116] S1006. The password cloud resource pool sharing device starts the smart contract to record the usage of password cloud resource pool resources.

[0117] S1007, the cryptographic cloud resource pool sharing device connects with the first node and updates the cryptographic cloud service requirements in the first block.

[0118] S1008, The password cloud resource pool sharing device updates the password cloud resource pool information of the local node.

[0119] As can be seen, the above mainly describes the technical solutions provided by the embodiments of this disclosure from a methodological perspective. To achieve the above functions, it includes corresponding hardware structures and / or software modules for executing each function. Those skilled in the art should readily recognize that, in conjunction with the modules and algorithm steps of the various examples described in the embodiments disclosed herein, the embodiments of this disclosure can be implemented in hardware or a combination of hardware and computer software. Whether a function is executed in hardware or by computer software driving hardware depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this disclosure.

[0120] This disclosure embodiment can divide the cryptographic cloud resource pool sharing device into functional modules according to the above method example. For example, each function can be divided into its own functional module, or two or more functions can be integrated into one processing module. The integrated module can be implemented in hardware or as a software functional module. Optionally, the module division in this disclosure embodiment is illustrative and only represents one logical functional division; other division methods may be used in actual implementation.

[0121] One possible implementation is, such as Figure 11 , Figure 11 This is a schematic diagram of the structure of a cryptographic cloud resource pool sharing device 1100 provided in this disclosure.

[0122] A cryptographic cloud resource pool sharing device 1100 includes: a processing unit 1102; the processing unit 1102 is used to read a first block and determine the cryptographic cloud service requirements of a second node; the first block is used to characterize the cryptographic cloud service requirements of the second node in the consortium blockchain; the second node is a node other than the first node in the consortium blockchain; the processing unit 1102 is used to allocate target cryptographic cloud resources that meet the cryptographic cloud service requirements of the second node in response to the first node's cryptographic cloud resources meeting the second node's cryptographic cloud service requirements; the processing unit 1102 is used to determine the resource call interface for sharing the target cryptographic cloud resources; the processing unit 1102 is used to write the identifier of the resource call interface into the first block.

[0123] In one possible implementation, after writing the identifier of the resource call interface in the first block, the processing unit 1102 is further configured to: in response to a sharing request for the target cryptographic cloud resource, share the target cryptographic cloud resource with the second node based on the resource call interface; update the shared resource directory in the second block based on the type and quantity of the shared target cryptographic cloud resource; the shared resource directory is used to record the shareable cryptographic cloud resource information of the nodes in the consortium blockchain; the second block is used to record the information of the nodes in the consortium blockchain.

[0124] In one possible implementation, the processing unit 1102 is further configured to: stop sharing the target cryptographic cloud resource with the second node in response to the request to end the sharing of the target cryptographic cloud resource; and update the shared resource directory in the second block based on the type and quantity of the target cryptographic cloud resource after the sharing ends.

[0125] In one possible implementation, before updating the shared resource directory in the second block, the processing unit 1102 is further configured to: write the shared resource directory into the second block; the shared resource directory includes at least one of the following: the identifier of the first node, the types and quantities of resources that the first node's cryptographic cloud resource pool can provide.

[0126] In one possible implementation, the cryptographic cloud service requirements of the second node include at least one of the following: the resource requirement type of the second node, the resource requirement quantity of the second node, the resource call interface field, and the identifier of the second node; the device further includes: a communication unit 1101; and a processing unit 1102, specifically configured to: when it is determined that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirements of the second node, instruct the communication unit 1101 to obtain the resource requirement type and the resource requirement quantity of the second node; and allocate target cryptographic cloud resources to the second node based on the resource requirement type and the resource requirement quantity of the second node.

[0127] In one possible implementation, the processing unit 1102 is further configured to: instruct the communication unit 1101 to receive a cryptographic cloud service request from the user terminal; the cryptographic cloud service request includes: the type and quantity of resources required for the cryptographic cloud service; and, if it is determined that the cryptographic cloud resources of the first node cannot meet the cryptographic cloud service requirements of the user terminal, write the cryptographic cloud service requirements of the first node into the first block.

[0128] In one possible implementation, the target cryptographic cloud resource usage information includes at least one of the following: resource type, resource usage time, resource usage quantity, and second node identifier; the processing unit 1102 is further configured to instruct the communication unit 1101 to obtain the second node's target cryptographic cloud resource usage information; determine the second node for settling usage fees based on the second node identifier; and settle the resource type, resource usage time, and resource usage quantity based on the pre-set fee terms in the smart contract to determine the cryptographic cloud resource usage fee for the second node.

[0129] This disclosure also provides a cryptographic cloud resource pool sharing device, which includes a processor and a memory. The memory stores computer execution instructions. When the cryptographic cloud resource pool sharing device is running, the processor executes the computer execution instructions stored in the memory, so that the cryptographic cloud resource pool sharing device performs the cryptographic cloud resource pool sharing method described in this disclosure.

[0130] Embodiments of this disclosure provide a computer program product containing instructions that, when executed on a computer, cause the computer to perform the cryptographic cloud resource pool sharing method described in the above method embodiments.

[0131] Embodiments of this disclosure provide a chip including a processor and a communication interface, the communication interface and the processor being coupled together. The processor is used to run computer programs or instructions to implement the cryptographic cloud resource pool sharing method as described in the above method embodiments.

[0132] The computer-readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of computer-readable storage media (a non-exhaustive list) include: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), registers, hard disks, optical fibers, compact disc read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing, or any other form of computer-readable storage medium in the art. An exemplary storage medium is coupled to a processor, enabling the processor to read information from and write information to the storage medium. Of course, the storage medium may also be a component of the processor. The processor and the storage medium may reside in an application-specific integrated circuit (ASIC). In this embodiment of the disclosure, the computer-readable storage medium can be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, apparatus, or device.

[0133] Since the apparatus, devices, computer-readable storage media, and computer program products in the embodiments of this disclosure can be applied to the above methods, the technical effects they can achieve can also be referred to the above method embodiments. The embodiments of this disclosure will not be repeated here.

[0134] The above descriptions are merely specific embodiments of this disclosure, but the scope of protection of this disclosure is not limited thereto. Any variations or substitutions within the technical scope disclosed in this disclosure should be included within the scope of protection of this disclosure. Therefore, the scope of protection of this disclosure should be determined by the scope of the claims.

Claims

1. A password cloud resource pool sharing method, characterized in that, A first node applied to a consortium chain, wherein the nodes in the consortium chain are cryptographic cloud resource pool nodes, and the method comprises the following steps: reading a first block to determine a cryptographic cloud service requirement of a second node, wherein the first block is used to represent the cryptographic cloud service requirement of the second node in the consortium chain, and the second node is a node other than the first node in the consortium chain; in response to the cryptographic cloud resources of the first node meeting the cryptographic cloud service requirement of the second node, allocating target cryptographic cloud resources meeting the cryptographic cloud service requirement of the second node to the second node; determining a resource calling interface for sharing the target cryptographic cloud resources; writing an identifier of the resource calling interface in the first block.

2. The method of claim 1, wherein, After the identifier of the resource calling interface is written in the first block, the method further comprises the following steps: in response to a sharing request of the target cryptographic cloud resources, sharing the target cryptographic cloud resources to the second node based on the resource calling interface; updating a shared resource directory in a second block based on the category and quantity of the shared target cryptographic cloud resources, wherein the shared resource directory is used to record the sharable cryptographic cloud resource information of the nodes in the consortium chain, and the second block is used to record the information of the nodes in the consortium chain.

3. The method of claim 2, wherein, The method further comprises the following steps: in response to an end request of the sharing of the target cryptographic cloud resources, stopping sharing the target cryptographic cloud resources to the second node; updating the shared resource directory in the second block based on the category and quantity of the target cryptographic cloud resources after the end of the sharing.

4. The method of claim 3, wherein, Before updating the shared resource directory in the second block, the method further comprises the following steps: writing the shared resource directory into the second block, wherein the shared resource directory at least comprises one of the following: an identifier of the first node, resource category and quantity information that can be provided by the cryptographic cloud resource pool of the first node.

5. The method of claim 4, wherein, The cryptographic cloud service requirement of the second node at least comprises one of the following: resource requirement type of the second node, resource requirement quantity of the second node, resource calling interface field, and identifier of the second node; and the response to the cryptographic cloud resources of the first node meeting the cryptographic cloud service requirement of the second node, and the allocation of the target cryptographic cloud resources meeting the cryptographic cloud service requirement of the second node to the second node, comprises the following steps: in the case that the cryptographic cloud resources of the first node meet the cryptographic cloud service requirement of the second node, acquiring the resource requirement type of the second node and the resource requirement quantity of the second node; allocating the target cryptographic cloud resources to the second node based on the resource requirement type of the second node and the resource requirement quantity of the second node.

6. The method of claim 5, wherein, The method further comprises the following steps: receiving a cryptographic cloud service request from a user terminal, wherein the cryptographic cloud service request comprises resource type and resource quantity required by the cryptographic cloud service; in the case that the cryptographic cloud resources of the first node cannot meet the cryptographic cloud service requirement of the user terminal, writing the cryptographic cloud service requirement of the first node into the first block.

7. The method according to any one of claims 1 to 6, characterized in that, The target cryptographic cloud resource usage information at least includes one of the following: usage resource type, usage resource time, usage resource quantity, the second node identifier, and the method further includes: Obtaining the target cryptographic cloud resource usage information of the second node; Determining the second node for settling the usage fee based on the second node identifier; Based on the fee clause preset in the smart contract, the usage resource type, the usage resource time, and the usage resource quantity are settled, and the cryptographic cloud resource usage fee of the second node is determined.

8. A cryptographic cloud resource pool sharing apparatus characterized by comprising: Comprising: A processing unit; The processing unit is used to read a first block and determine the cryptographic cloud service demand of a second node; The first block is used to represent the cryptographic cloud service demand of the second node in the alliance chain; The second node is a node other than the first node in the alliance chain; The processing unit is used to allocate target cryptographic cloud resources that meet the cryptographic cloud service demand of the second node to the second node in response to the cryptographic cloud resources of the first node meeting the cryptographic cloud service demand of the second node; The processing unit is used to determine a resource calling interface for sharing the target cryptographic cloud resources; The processing unit is used to write the identifier of the resource calling interface in the first block.

9. A cryptographic cloud resource pool sharing apparatus, characterized by, Comprising: A processor and a memory; wherein the memory is used to store computer execution instructions, when the cryptographic cloud resource pool sharing device runs, the processor executes the computer execution instructions stored in the memory, so that the cryptographic cloud resource pool sharing device executes the cryptographic cloud resource pool sharing method in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer readable storage medium stores instructions, when the instructions in the computer readable storage medium are executed by the processor of the cryptographic cloud resource pool sharing, so that the cryptographic cloud resource pool sharing device executes the cryptographic cloud resource pool sharing method in any one of claims 1-7.

Images