Cloud server sharing method, device, equipment and storage medium

Abstract

The present application provides a cloud server sharing method, apparatus, device and storage medium, including: in response to cloud server demand, determining whether the second sub-user node belongs to the same sharing system; if determined, encrypting the first communication number with the second sub-user node public key to obtain a first encryption result and sending it to the blockchain network; receiving the second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtaining the second communication number based on the call; encrypting the first communication number and the second communication number to obtain a second encryption result; encrypting the second encryption result according to the second sub-user node public key to obtain a fourth encryption result, and sending the fourth encryption result to the blockchain; judging whether to share resources with the second sub-user node according to demand information; if determined, encrypting the cloud server address and login password with the second encryption result and sending them to the blockchain.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a cloud server sharing method, apparatus, device, and storage medium. Background Art

[0002] Cloud servers provide Internet-based infrastructure services to corporate and individual users. This user group is huge, and the demand for Internet host applications is increasing. Users use cloud server resources by renting cloud servers.

[0003] In the related art, a user can use the resources of a rented cloud server. For example, if a user signs a contract with a certain cloud server, the user can use the resources of the cloud server, but cannot use the resources of other cloud servers that have not signed a contract.

[0004] However, the existing cloud server usage method will cause waste of resources. Summary of the Invention

[0005] The present application provides a cloud server sharing method, apparatus, device and storage medium to solve the technical problem that the existing cloud server usage method causes waste of resources.

[0006] In a first aspect, the present application provides a cloud server sharing method, applied to a first sub-user node, the method comprising:

[0007] In response to a cloud server requirement published by a second sub-user node in the blockchain, determining, based on a user affiliation identifier, whether the second sub-user node belongs to the same shared system as the second sub-user node, wherein the cloud server requirement includes the user affiliation identifier, the second sub-user node blockchain identifier, and the requirement information;

[0008] If it is determined that the second sub-user node belongs to the same shared system, obtaining a first communication number, encrypting the first communication number using the public key of the second sub-user node according to a first preset algorithm to obtain a first encryption result, sending the first encryption result and the blockchain identifier of the first sub-user node to the blockchain network, so that the second sub-user node receives the first encryption result and the first sub-user node blockchain identifier, decrypting the first encryption result according to the first preset algorithm and the second sub-user node private key to obtain the first communication number, establishing a call with the first sub-user node according to the first communication number, and transmitting the second sub-user node blockchain identifier to the first sub-user node through the call signaling;

[0009] receiving a second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtaining a second communication number based on the call;

[0010] encrypting the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result;

[0011] Encrypting the second encrypted result using the public key of the second sub-user node to obtain a fourth encrypted result, and sending the fourth encrypted result to the blockchain so that the second sub-user node receives the fourth encrypted result, and decrypting the fourth encrypted result using the private key of the second sub-user node to obtain the second encrypted result;

[0012] determining, based on the demand information, whether to share resources with the second sub-user node;

[0013] If it is determined that resources are shared with the second sub-user node, encrypting the cloud server address and login password using the second encryption result according to a third preset algorithm to obtain a third encryption result;

[0014] The third encryption result and the second sub-user node blockchain identifier are sent to the blockchain, so that the second sub-user node receives the third encryption result, decrypts the third encryption result according to the second encryption result and the third preset algorithm to obtain the cloud server address and login password, and shares the cloud server resources of the first sub-user node according to the cloud server address and the login password.

[0015] The present application provides a method for realizing cloud server resource sharing between sub-users, wherein a first sub-user node and a second sub-user node belong to the same shared system, and the second sub-user node can initiate a cloud server demand to the first sub-user node through the blockchain, and the first sub-user node encrypts its own first communication number and sends it to the second sub-user node, and the second sub-user node uses the first communication number to establish a call with the first sub-user node, and the call signaling transmits the second sub-user node blockchain identifier and the second communication number corresponding to the two sub-user nodes, and the second encryption result after encrypting the first communication number and the second communication number can be used as an encryption key, if the cloud server resource corresponding to the first sub-user node is idle, the cloud server address and login password of the shared cloud service are encrypted by the encryption key and sent to the blockchain, and the second sub-user node can directly decrypt the encrypted cloud server address and login password sent to the first sub-user node, thereby realizing cloud server resource sharing, reducing the waste of cloud server resources, and improving the utilization rate of cloud service resources.

[0016] Optionally, determining whether the second sub-user node belongs to the same shared system based on the user affiliation identifier includes: comparing the user affiliation identifier in the cloud server requirement with the user affiliation identifier of the first sub-user node to determine whether the second sub-user node belongs to the same shared system.

[0017] Optionally, the same sharing system can pre-assign user affiliation identifiers to the first sub-user node and the second sub-user node. During the cloud server sharing process, the sub-user nodes can use the identifier to determine whether to share resources, quickly determine user affiliation, and further improve the cloud server sharing efficiency.

[0018] Optionally, the user affiliation identifier is a communication number; accordingly, determining whether the second sub-user node belongs to the same shared system based on the user affiliation identifier includes: determining whether the second sub-user node belongs to the same shared system based on the first communication number and the second communication number.

[0019] Among them, this application can use the communication number of the sub-user node as the user affiliation identification. If the communication numbers of the two sub-user nodes meet the preset rules, it is determined that they belong to the same shared system as the second sub-user node. There is no need to add other additional identifications. The judgment method is simple and fast, which further improves the sharing efficiency of the cloud server.

[0020] Optionally, the demand information includes usage time and resource usage capacity; accordingly, judging whether to share resources with the second sub-user node based on the demand information includes: determining whether the usage time is the idle time of the first sub-user node; if the usage time is the idle time of the first sub-user node, determining whether to share resources with the second sub-user node based on the resource usage capacity and the idle resources of the cloud server.

[0021] Here, the present application can share the cloud server with the second sub-user node during the idle time period based on the usage time and resource usage capacity of the cloud server by the second sub-user node, combined with the idle time and idle resources of the cloud server rented by itself, thereby realizing the sharing of cloud service resources during the idle time period, further improving resource utilization, and not affecting the business of the first sub-user node.

[0022] Optionally, the login password is a temporary login password with a preset validity period.

[0023] Among them, this application sets a validity period for the login password, which can ensure the security of cloud server resource sharing without affecting the normal use of the first sub-user node, further improving the user experience.

[0024] In a second aspect, the present application provides a cloud server sharing method, applied to a second sub-user node, the method comprising:

[0025] Publishing a cloud server demand in the blockchain, so that the first sub-user node responds to the cloud server demand and determines, based on the user's affiliation identifier, whether it belongs to the same shared system as the second sub-user node. If it is determined that the second sub-user node belongs to the same shared system, obtaining a first communication number, encrypting the first communication number using the second sub-user node's public key according to a first preset algorithm to obtain a first encryption result, and sending the first encryption result and the first sub-user node's blockchain identifier to the blockchain network, wherein the cloud server demand includes the user's affiliation identifier, the second sub-user node's blockchain identifier, and the demand information;

[0026] receiving the first encryption result and the first sub-user node blockchain identifier, and decrypting the first encryption result according to a first preset algorithm and a second sub-user node private key to obtain the first communication number;

[0027] Establishing a call with the first sub-user node according to the first communication number, and transmitting the second sub-user node blockchain identifier to the first sub-user node through call signaling, so that the first sub-user node receives the second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtaining a second communication number according to the call, encrypting the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result, encrypting the second encryption result according to the second sub-user node public key to obtain a fourth encryption result, and sending the fourth encryption result to the blockchain;

[0028] receiving the fourth encryption result, and decrypting the fourth encryption result according to the second sub-user node private key to obtain a second encryption result;

[0029] Receiving, through the blockchain, a third encryption result and a second sub-user node blockchain identifier, wherein the third encryption result and the second sub-user node blockchain identifier are for the first sub-user node to determine, based on the demand information, whether to share resources with the second sub-user node; if it is determined that resources are to be shared with the second sub-user node, encrypting the cloud server address and login password using the second encryption result according to a third preset algorithm, and sending the obtained third encryption result to the blockchain;

[0030] The third encryption result is decrypted according to the second encryption result and the third preset algorithm to obtain a cloud server address and a login password, and the cloud server resources of the first sub-user node are shared according to the cloud server address and the login password.

[0031] The second sub-user node provided in this application can share the cloud server resources of the first sub-user node, and prove its identity to the first sub-user node through dual authentication of calls and blockchain, thereby avoiding waste of resources on the basis of security and improving the utilization rate of cloud server resources.

[0032] In a third aspect, the present application provides a cloud server sharing device, applied to a first sub-user node, the device comprising:

[0033] an affiliation determination module, configured to respond to a cloud server requirement published by a second sub-user node in the blockchain and determine, based on a user affiliation identifier, whether the second sub-user node belongs to the same shared system, wherein the cloud server requirement includes the user affiliation identifier, the second sub-user node blockchain identifier, and the requirement information;

[0034] a first processing module, configured to, if it is determined that the second sub-user node and the second sub-user node belong to the same shared system, obtain a first communication number, encrypt the first communication number using the second sub-user node public key according to a first preset algorithm to obtain a first encryption result, send the first encryption result and the first sub-user node blockchain identifier to the blockchain network, so that the second sub-user node receives the first encryption result and the first sub-user node blockchain identifier, decrypt the first encryption result using the first preset algorithm and the second sub-user node private key to obtain the first communication number, establish a call with the first sub-user node using the first communication number, and transmit the second sub-user node blockchain identifier to the first sub-user node through call signaling;

[0035] a second processing module, configured to receive a second sub-user node blockchain identifier transmitted by the second sub-user node via call signaling, and obtain a second communication number based on the call;

[0036] a third processing module, configured to encrypt the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result;

[0037] a fourth processing module, configured to encrypt the second encrypted result according to the public key of the second sub-user node to obtain a fourth encrypted result, and send the fourth encrypted result to the blockchain so that the second sub-user node receives the fourth encrypted result, and decrypt the fourth encrypted result according to the private key of the second sub-user node to obtain a second encrypted result;

[0038] a determination module, configured to determine whether to share resources with the second sub-user node based on the demand information;

[0039] a fifth processing module, configured to, if it is determined that resources are shared with the second sub-user node, encrypt the cloud server address and the login password using the second encryption result according to a third preset algorithm to obtain a third encryption result;

[0040] The sixth processing module is used to send the third encryption result and the second sub-user node blockchain identifier to the blockchain, so that the second sub-user node receives the third encryption result, decrypts the third encryption result according to the second encryption result and the third preset algorithm to obtain the cloud server address and login password, and shares the cloud server resources of the first sub-user node according to the cloud server address and the login password.

[0041] Optionally, the attribution determination module is specifically configured to:

[0042] The user affiliation identifier in the cloud server requirement is compared with the user affiliation identifier of the first sub-user node to determine whether the second sub-user node belongs to the same shared system.

[0043] Optionally, the user attribution identifier is a communication number;

[0044] Accordingly, the attribution determination module is specifically configured to:

[0045] According to the first communication number and the second communication number, it is determined whether the second sub-user node belongs to the same shared system.

[0046] Optionally, the demand information includes usage time and resource usage capacity;

[0047] Accordingly, the judgment module is specifically configured to:

[0048] determining whether the usage time is the idle time of the first sub-user node;

[0049] If the usage time is the idle time of the first sub-user node, whether to share resources with the second sub-user node is determined according to the resource usage capacity and the idle resources of the cloud server.

[0050] Optionally, the login password is a temporary login password with a preset validity period.

[0051] In a fourth aspect, the present application provides a cloud server sharing device, applied to a second sub-user node, the device comprising:

[0052] A request publishing module, configured to publish a cloud server demand in the blockchain, so that the first sub-user node responds to the cloud server demand and determines, based on the user affiliation identifier, whether it belongs to the same shared system as the second sub-user node. If it is determined that the second sub-user node belongs to the same shared system, the first communication number is obtained, and the first encryption result is obtained by encrypting the first communication number using the second sub-user node public key according to a first preset algorithm. The first encryption result and the first sub-user node blockchain identifier are sent to the blockchain network, wherein the cloud server demand includes the user affiliation identifier, the second sub-user node blockchain identifier, and the demand information.

[0053] a seventh processing module, configured to receive the first encryption result and the first sub-user node blockchain identifier, and decrypt the first encryption result according to a first preset algorithm and a second sub-user node private key to obtain the first communication number;

[0054] a call processing module, configured to establish a call with the first sub-user node according to the first communication number, and transmit the second sub-user node blockchain identifier to the first sub-user node via call signaling, so that the first sub-user node receives the second sub-user node blockchain identifier transmitted by the second sub-user node via call signaling, obtain a second communication number according to the call, encrypt the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result, encrypt the second encryption result according to the second sub-user node public key to obtain a fourth encryption result, and send the fourth encryption result to the blockchain;

[0055] an eighth processing module, configured to receive the fourth encryption result, and decrypt the fourth encryption result according to the second sub-user node private key to obtain a second encryption result;

[0056] a receiving module, configured to receive, via a blockchain, a third encryption result and a second sub-user node blockchain identifier, wherein the third encryption result and the second sub-user node blockchain identifier are for the first sub-user node to determine, based on the demand information, whether to share resources with the second sub-user node; if it is determined that resources are to be shared with the second sub-user node, encrypting the cloud server address and login password using the second encryption result according to a third preset algorithm, and sending the obtained third encryption result to the blockchain;

[0057] The ninth processing module is used to decrypt the third encryption result according to the second encryption result and the third preset algorithm to obtain the cloud server address and login password, and share the cloud server resources of the first sub-user node according to the cloud server address and the login password.

[0058] In a fifth aspect, the present application provides a cloud server sharing device, comprising: at least one processor and a memory;

[0059] The memory stores computer-executable instructions;

[0060] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the cloud server sharing method described in the first aspect and various possible designs of the first aspect.

[0061] In a sixth aspect, the present application provides a cloud server sharing device, comprising: at least one processor and a memory;

[0062] The memory stores computer-executable instructions;

[0063] The at least one processor executes the computer-executable instructions stored in the memory, so that the at least one processor executes the cloud server sharing method described in the second aspect and various possible designs of the second aspect.

[0064] In the seventh aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When the processor executes the computer-executable instructions, the cloud server sharing method described in the first aspect and various possible designs of the first aspect is implemented.

[0065] In an eighth aspect, the present application provides a computer-readable storage medium, which stores computer-executable instructions. When a processor executes the computer-executable instructions, the cloud server sharing method described in the second aspect and various possible designs of the second aspect is implemented.

[0066] In a ninth aspect, the present application provides a computer program product, comprising a computer program, which, when executed by a processor, implements the cloud server sharing method as described in the first aspect and various possible designs of the first aspect.

[0067] In a tenth aspect, the present application provides a computer program product, including a computer program, which, when executed by a processor, implements the cloud server sharing method described in the second aspect and various possible designs of the second aspect.

[0068] The present application provides a cloud server sharing method, apparatus, device and storage medium, wherein the second sub-user node of the method can initiate a cloud server demand to the first sub-user node through the blockchain, the first sub-user node encrypts its own first communication number and sends it to the second sub-user node, the second sub-user node uses the first communication number to establish a call with the first sub-user node, and the call signaling transmits the second sub-user node blockchain identifier and the second communication number corresponding to the two sub-user nodes, the second encryption result after encrypting the first communication number and the second communication number can be used as an encryption key, if the cloud server resources corresponding to the first sub-user node are idle, the cloud server address and login password of the shared cloud service are encrypted by the encryption key and sent to the blockchain, the second sub-user node can directly decrypt the encrypted cloud server address and login password sent to the first sub-user node, thereby realizing cloud server resource sharing, reducing the waste of cloud server resources, and improving cloud service resource utilization. BRIEF DESCRIPTION OF THE DRAWINGS

[0069] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0070] Figure 1 A schematic diagram of a cloud server sharing system architecture provided in an embodiment of the present application;

[0071] Figure 2 A flowchart of a cloud server sharing method provided in an embodiment of the present application;

[0072] Figure 3 A flowchart of another cloud server sharing method provided in an embodiment of the present application;

[0073] Figure 4 A schematic diagram of the structure of a cloud server sharing device provided in an embodiment of the present application;

[0074] Figure 5 A schematic diagram of the structure of a cloud server sharing device provided in an embodiment of the present application.

[0075] The above drawings illustrate specific embodiments of the present disclosure, which will be described in more detail below. These drawings and textual descriptions are not intended to limit the scope of the present disclosure in any way, but rather to illustrate the concepts of the present disclosure to those skilled in the art by reference to specific embodiments. DETAILED DESCRIPTION

[0076] Exemplary embodiments will be described in detail herein, with examples illustrated in the accompanying drawings. In the following description, when referring to the drawings, identical numerals in different figures represent identical or similar elements, unless otherwise indicated. The embodiments described in the following exemplary embodiments are not intended to represent all possible embodiments consistent with the present disclosure. Rather, they are merely examples of apparatus and methods consistent with certain aspects of the present disclosure, as detailed in the appended claims.

[0077] The terms "first," "second," "third," and "fourth," etc. (if any) in the specification and claims of this application and in the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a particular order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate so that the embodiments of the application described herein can be implemented in orders other than those illustrated or described herein. In addition, the terms "including" and "having," and any variations thereof, are intended to cover non-exclusive inclusions. For example, a process, method, system, product, or apparatus comprising a series of steps or elements is not necessarily limited to those steps or elements explicitly listed, but may include other steps or elements not explicitly listed or inherent to such process, method, product, or apparatus.

[0078] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant laws, regulations and standards, and corresponding operation entrances must be provided for users to choose to authorize or refuse.

[0079] As an important resource provider, cloud servers offer significant convenience to both corporate and individual users. Users can utilize the resources of previously leased cloud servers. For example, if a user has signed a contract with a specific cloud server, they can use that server's resources, but cannot access resources from other unsigned cloud servers. However, for subsidiaries within the same group company, different branches, subsidiaries, or even different departments may simultaneously lease the same cloud server, resulting in low utilization and wasted resources. This can consume significant network resources without high utilization, leading to resource waste.

[0080] In order to solve the above technical problems, the embodiments of the present application provide a cloud server sharing method, device, equipment and storage medium. This method can realize the sharing of cloud server resources between two sub-user nodes belonging to the same sharing system, and realize identity authentication and login information transmission through call signaling and blockchain. It realizes the sharing of cloud server resources on the basis of ensuring security and improves resource utilization.

[0081] Optionally, Figure 1 This is a schematic diagram of a cloud server sharing system architecture provided by an embodiment of the present application. Figure 1 As shown, the above architecture includes: a first sub-user node 101, a second sub-user node 102, and a cloud server node 103.

[0082] The first sub-user node 101 and the second sub-user node 102 belong to the same shared system. For example, the first sub-user node 101 and the second sub-user node 102 correspond to different departments of the same company, or branches or subsidiaries under the same head office, or different terminal devices of the same user.

[0083] The first sub-user node 101 and the second sub-user node 102 may be set on a server or a terminal device, or may be the server or the terminal device itself.

[0084] The cloud server node 103 is a cloud server that is contracted with the first sub-user node or leased by the first sub-user node 101 .

[0085] Among them, the first sub-user node 101, the second sub-user node 102, and the cloud server node 103 are all registered in the blockchain and can be connected through the blockchain.

[0086] Optionally, the first sub-user node 101, the second sub-user node 102, and the cloud server node 103 are all nodes in the blockchain, and register their own identity information in the form of a broadcast message signed by a private key in the blockchain. The broadcast message includes: blockchain identifier, public key, identity identifier, etc.

[0087] It is understandable that the number and specific structure of the above nodes can be determined according to actual conditions. Figure 1 This is for illustration only, and the embodiments of the present application do not impose any specific limitation on the number of the above nodes.

[0088] It is understood that the structure illustrated in the embodiments of this application does not constitute a specific limitation on the cloud server sharing system architecture. In other feasible implementations of this application, the above architecture may include more or fewer components than shown, or combine or split certain components, or arrange components differently. The specific configuration can be determined based on the actual application scenario and is not limited here. Figure 1 The components shown can be implemented in hardware, software, or a combination of software and hardware.

[0089] In addition, the network architecture and business scenarios described in the embodiments of the present application are intended to more clearly illustrate the technical solutions of the embodiments of the present application, and do not constitute a limitation on the technical solutions provided in the embodiments of the present application. Ordinary technicians in this field can know that with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of the present application are also applicable to similar technical problems.

[0090] The technical solution of the present application is described below using several embodiments as examples, and the same or similar concepts or processes may not be repeated in some embodiments.

[0091] Figure 2 A flow chart of a cloud server sharing method provided in an embodiment of the present application, which can be applied to Figure 1 The first sub-user node 101 in the embodiment may be a server or a terminal device, and the specific execution subject may be determined according to the actual application scenario. Figure 2 As shown, the method includes the following steps:

[0092] S201: In response to a cloud server demand published by a second sub-user node in the blockchain, determine, based on a user affiliation identifier, whether the second sub-user node belongs to the same shared system.

[0093] Among them, the cloud server requirements include user affiliation identification, second sub-user node blockchain identification and demand information.

[0094] Optionally, the demand information includes at least one of storage capacity, rate or usage time.

[0095] Optionally, the cloud server requirement is published by the second sub-user node in the blockchain in the form of a broadcast message signed by a private key.

[0096] Optionally, after receiving the broadcast message in the blockchain, the first sub-user node verifies the private key signature of the broadcast message. If the verification is successful, an authentication operation of the user's attribution identity is performed.

[0097] Optionally, based on the user affiliation identifier, determining whether the second sub-user node belongs to the same shared system includes: comparing the user affiliation identifier in the cloud server requirement with the user affiliation identifier of the first sub-user node to determine whether the second sub-user node belongs to the same shared system.

[0098] Optionally, the same sharing system can pre-assign user affiliation identifiers to the first sub-user node and the second sub-user node. During the cloud server sharing process, the sub-user nodes can use the identifier to determine whether to share resources, quickly determine user affiliation, and further improve the cloud server sharing efficiency.

[0099] Optionally, the user affiliation identifier is a communication number; accordingly, determining whether the user belongs to the same shared system as the second sub-user node based on the user affiliation identifier includes: determining whether the user belongs to the same shared system as the second sub-user node based on the first communication number and the second communication number.

[0100] Optionally, whether the user node and the second sub-user node belong to the same shared system can be determined based on a preset rule. The preset rule can be determined based on the circumstances and is not specifically limited in this embodiment of the present application. For example, if the first N digits or the last N digits of the communication number are the same, then the user node and the second sub-user node are determined to belong to the same shared system. N is a positive integer and can be determined based on the circumstances.

[0101] Among them, the embodiment of the present application can use the communication number of the sub-user node as the user affiliation identification. If the communication numbers of two sub-user nodes meet the preset rules, it is determined that they belong to the same shared system as the second sub-user node. There is no need to add other additional identifications. The judgment method is simple and fast, which further improves the sharing efficiency of the cloud server.

[0102] S202: If it is determined that the second sub-user node belongs to the same shared system, a first communication number is obtained, and the first communication number is encrypted using the public key of the second sub-user node according to a first preset algorithm to obtain a first encryption result, and the first encryption result and the blockchain identifier of the first sub-user node are sent to the blockchain network so that the second sub-user node receives the first encryption result and the blockchain identifier of the first sub-user node, and the first encryption result is decrypted according to the first preset algorithm and the private key of the second sub-user node to obtain the first communication number, a call is established with the first sub-user node according to the first communication number, and the second sub-user node blockchain identifier is transmitted to the first sub-user node through call signaling.

[0103] Optionally, the first encryption result and the first sub-user node blockchain identifier are sent to the blockchain network in the form of a broadcast message signed by a private key.

[0104] S203: Receive the second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtain the second communication number based on the call.

[0105] S204: Encrypt the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result.

[0106] S205: Encrypt the second encryption result according to the public key of the second sub-user node to obtain a fourth encryption result, and send the fourth encryption result to the blockchain so that the second sub-user node receives the fourth encryption result, and decrypt the fourth encryption result according to the private key of the second sub-user node to obtain a second encryption result.

[0107] Optionally, the fourth encryption result is sent to the blockchain in the form of a broadcast message signed by a private key.

[0108] S206: Determine whether to share resources with the second sub-user node according to the demand information.

[0109] Optionally, the demand information includes usage time and resource usage capacity; accordingly, based on the demand information, it is determined whether to share resources with the second sub-user node, including: determining whether the usage time is the idle time of the first sub-user node; if the usage time is the idle time of the first sub-user node, determining whether to share resources with the second sub-user node based on the resource usage capacity and the idle resources of the cloud server.

[0110] Here, the embodiment of the present application can share the cloud server with the second sub-user node during the idle time period based on the second sub-user node's usage time and resource usage capacity of the cloud server, combined with the idle time and idle resources of the cloud server it rents, thereby realizing cloud service resource sharing during the idle time period, further improving resource utilization, and not affecting the business of the first sub-user node.

[0111] S207: If it is determined to share resources with the second sub-user node, the cloud server address and the login password are encrypted using the second encryption result according to a third preset algorithm to obtain a third encryption result.

[0112] Among them, the first preset algorithm, the second preset algorithm and the third preset algorithm can be the same or different, and can be determined according to actual conditions. The embodiment of the present application does not impose any specific restrictions on this.

[0113] Optionally, the login password is a temporary login password with a preset validity period.

[0114] It is understandable that the preset validity period can be determined based on actual conditions, and the embodiments of the present application do not impose any specific restrictions on this.

[0115] Optionally, the preset validity period may be data entered by the user.

[0116] Optionally, the preset validity period may be determined according to the operating status of the first sub-user node.

[0117] Among them, the embodiment of the present application sets a validity period for the login password, which can ensure the security of cloud server resource sharing without affecting the normal use of the first sub-user node, further improving the user experience.

[0118] S208: Send the third encryption result and the blockchain identifier of the second sub-user node to the blockchain, so that the second sub-user node receives the third encryption result, decrypts the third encryption result according to the second encryption result and the third preset algorithm, obtains the cloud server address and login password, and shares the cloud server resources of the first sub-user node according to the cloud server address and login password.

[0119] Optionally, the third encryption result and the second sub-user node blockchain identifier are sent to the blockchain in the form of a broadcast message signed by a private key.

[0120] An embodiment of the present application provides a method for realizing cloud server resource sharing between sub-users, wherein a first sub-user node and a second sub-user node belong to the same shared system, and the second sub-user node can initiate a cloud server demand to the first sub-user node through the blockchain, and the first sub-user node encrypts its own first communication number and sends it to the second sub-user node, and the second sub-user node uses the first communication number to establish a call with the first sub-user node, and the call signaling transmits the second sub-user node blockchain identifier and the second communication number corresponding to the two sub-user nodes, and the second encryption result after encrypting the first communication number and the second communication number can be used as an encryption key. If the cloud server resource corresponding to the first sub-user node is idle, the cloud server address and login password of the shared cloud service are encrypted by the encryption key and sent to the blockchain, and the second sub-user node can directly decrypt the encrypted cloud server address and login password sent to the first sub-user node, thereby realizing cloud server resource sharing, reducing the waste of cloud server resources, and improving the utilization rate of cloud service resources.

[0121] Optionally, Figure 3 This is a flow chart of another cloud server sharing method provided in an embodiment of the present application. The embodiment of the present application can be applied to Figure 1 The second sub-user node 102 in the embodiment may be a server or a terminal device, and the specific execution subject may be determined according to the actual application scenario. Figure 3 As shown, the method includes the following steps:

[0122] S301: Publish cloud server requirements in the blockchain so that the first sub-user node responds to the cloud server requirements, and determines whether it belongs to the same shared system as the second sub-user node based on the user affiliation identifier. If it is determined that it belongs to the same shared system as the second sub-user node, obtain a first communication number, encrypt the first communication number using the second sub-user node public key according to a first preset algorithm to obtain a first encryption result, and send the first encryption result and the first sub-user node blockchain identifier to the blockchain network.

[0123] Among them, the cloud server requirements include user affiliation identification, second sub-user node blockchain identification and demand information.

[0124] S302: Receive a first encryption result and a first sub-user node blockchain identifier, and decrypt the first encryption result according to a first preset algorithm and a second sub-user node private key to obtain a first communication number.

[0125] S303: Establish a call with the first sub-user node according to the first communication number, and transmit the second sub-user node blockchain identifier to the first sub-user node through the call signaling, so that the first sub-user node receives the second sub-user node blockchain identifier transmitted by the second sub-user node through the call signaling, and obtains the second communication number according to the call, encrypts the first communication number and the second communication number according to the second preset algorithm to obtain a second encryption result, encrypts the second encryption result according to the public key of the second sub-user node to obtain a fourth encryption result, and sends the fourth encryption result to the blockchain.

[0126] Optionally, after obtaining the first communication number, a call may be automatically initiated to the first communication number through the second communication number.

[0127] S304: Receive the fourth encryption result, and decrypt the fourth encryption result according to the second sub-user node private key to obtain a second encryption result.

[0128] S305: Receive the third encryption result and the second sub-user node blockchain identifier through the blockchain.

[0129] Among them, the third encryption result and the second sub-user node blockchain identifier are that the first sub-user node determines whether to share resources with the second sub-user node based on the demand information. If it is determined to share resources with the second sub-user node, the cloud server address and login password are encrypted according to the second encryption result according to the third preset algorithm, and the third encryption result is obtained and sent to the blockchain.

[0130] S306: Decrypt the third encryption result according to the second encryption result and the third preset algorithm to obtain the cloud server address and login password, and share the cloud server resources of the first sub-user node according to the cloud server address and login password.

[0131] The second sub-user node provided in the embodiment of the present application can share the cloud server resources of the first sub-user node, and prove its identity to the first sub-user node through dual authentication of calls and blockchain, thereby avoiding waste of resources on the basis of security and improving the utilization rate of cloud server resources.

[0132] In one possible implementation, a cloud server sharing method is introduced based on a specific application scenario. The specific implementation is as follows:

[0133] A certain group company M has two subsidiaries, A and B. Subsidiary A leases cloud server resource D from cloud server provider C.

[0134] Subsidiary A, Subsidiary B, and Cloud Server Provider C are all nodes in the blockchain. They register their identity information in the form of a broadcast message signed by a private key in the blockchain. The broadcast message includes: blockchain identifier, public key, identity identifier, etc.

[0135] Since the employees under the name of subsidiary A and the employees under the name of subsidiary B belong to the same group company, the two companies have group user mobile phone numbers of the same operator. For example, subsidiary A corresponds to the first communication number and subsidiary B corresponds to the second communication number. These two mobile phone numbers belong to the same operator, so the terminal equipment of subsidiary A and the terminal equipment of subsidiary B can use the method of calling the communication number to conduct voice communication.

[0136] Subsidiary B publishes its cloud server requirements in the form of a private key-signed broadcast message in the blockchain network, including the required storage capacity, speed, usage time, etc. of the server, the blockchain identifier of Subsidiary B, and the identifier of Group Company M.

[0137] After receiving the broadcast message in the blockchain network, subsidiary A verifies the private key signature of the broadcast message. If the verification is successful, based on the identification of group company M in the broadcast message, it is discovered that subsidiary B belongs to the same group company as itself. Subsidiary A then encrypts its own first communication number using subsidiary B's public key according to a pre-agreed algorithm to obtain encryption result 1. Then, subsidiary A sends the encryption result 1 and subsidiary A's identification together with a broadcast message signed by subsidiary A's private key to the blockchain network.

[0138] After receiving the broadcast message, subsidiary B verifies the private key signature of the broadcast message. If the verification is successful, it uses the private key of subsidiary B to decrypt the encrypted result 1 in the broadcast message according to the pre-agreed algorithm to obtain the decrypted result. The terminal device of subsidiary B automatically initiates a call through the first communication number obtained from the decryption result. During the call establishment process, the blockchain identifier of subsidiary B is transmitted to subsidiary A through the signaling channel of the call.

[0139] Through the above steps, Subsidiary A received Subsidiary B's blockchain identifier transmitted via the signaling channel, as well as Subsidiary B's second communication number displayed when calling the voice channel. During the subsequent identity verification process, the first and second communication numbers are encrypted according to a pre-agreed algorithm, resulting in Subsidiary A obtaining Encryption Result 2. Subsidiary A then uses Subsidiary B's blockchain identifier received via the signaling channel to query the blockchain ledger and obtain the blockchain public key corresponding to Subsidiary B's blockchain identifier. Subsidiary A then re-encrypts Encryption Result 2 using Subsidiary B's blockchain public key to obtain Encryption Result 4. Subsidiary A then sends Encryption Result 4 to the blockchain network using a broadcast message signed with its private key.

[0140] After receiving the broadcast message, subsidiary B verifies the private key signature of the broadcast message. If the verification is successful, subsidiary B uses its own private key to decrypt the encrypted result 4 to obtain the encrypted result 2.

[0141] Based on the cloud server usage time and capacity information provided by Subsidiary B, Subsidiary A determines that this time period is its own idle time period and can lend its cloud service resources to Subsidiary B. Subsidiary A then uses Encryption Result 2 to encrypt the leased cloud server address and login password according to a pre-agreed algorithm to obtain Encryption Result 3. Subsidiary A then sends a broadcast message signed with its private key, along with Encryption Result 3 and Subsidiary B's blockchain identifier, to the blockchain network.

[0142] After receiving the broadcast message, subsidiary B verifies the private key signature of the broadcast message. If the verification is successful, subsidiary B decrypts the encryption result 3 using the secret key encryption result 2 to obtain the cloud server address and login password, and can then use the cloud server to rent resources.

[0143] Figure 4 A schematic diagram of the structure of a cloud server sharing device provided in an embodiment of the present application is applied to a user node, such as Figure 4 As shown, the apparatus of the embodiment of the present application includes: an attribution determination module 401, a first processing module 402, a second processing module 403, a third processing module 404, a fourth processing module 405, a judgment module 406, a fifth processing module 407 and a sixth processing module 408. The cloud server sharing device here can be a server or a terminal device, or a chip or integrated circuit that realizes the functions of a server or a terminal device. It should be noted here that the division of the attribution determination module 401, the first processing module 402, the second processing module 403, the third processing module 404, the fourth processing module 405, the judgment module 406, the fifth processing module 407 and the sixth processing module 408 is only a division of logical functions. Physically, the two can be integrated or independent.

[0144] The attribution determination module is configured to respond to a cloud server requirement published by the second sub-user node in the blockchain and determine, based on the user attribution identifier, whether the second sub-user node belongs to the same shared system as the second sub-user node, wherein the cloud server requirement includes the user attribution identifier, the second sub-user node blockchain identifier, and the requirement information;

[0145] a first processing module, configured to, if it is determined that the node and the second sub-user node belong to the same shared system, obtain a first communication number, encrypt the first communication number using the public key of the second sub-user node according to a first preset algorithm to obtain a first encryption result, send the first encryption result and the blockchain identifier of the first sub-user node to the blockchain network, so that the second sub-user node receives the first encryption result and the blockchain identifier of the first sub-user node, decrypt the first encryption result using the first preset algorithm and the private key of the second sub-user node to obtain the first communication number, establish a call with the first sub-user node according to the first communication number, and transmit the blockchain identifier of the second sub-user node to the first sub-user node through call signaling;

[0146] A second processing module is configured to receive a second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtain a second communication number based on the call;

[0147] a third processing module, configured to encrypt the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result;

[0148] a fourth processing module, configured to encrypt the second encryption result according to the public key of the second sub-user node to obtain a fourth encryption result, send the fourth encryption result to the blockchain, so that the second sub-user node receives the fourth encryption result, and decrypt the fourth encryption result according to the private key of the second sub-user node to obtain a second encryption result;

[0149] a judgment module, configured to judge whether to share resources with the second sub-user node according to the demand information;

[0150] a fifth processing module, configured to, if it is determined that resources are shared with the second sub-user node, encrypt the cloud server address and the login password using the second encryption result according to a third preset algorithm to obtain a third encryption result;

[0151] The sixth processing module is used to send the third encryption result and the blockchain identifier of the second sub-user node to the blockchain, so that the second sub-user node receives the third encryption result, decrypts the third encryption result according to the second encryption result and the third preset algorithm, obtains the cloud server address and login password, and shares the cloud server resources of the first sub-user node according to the cloud server address and login password.

[0152] Optionally, the attribution determination module is specifically configured to:

[0153] The user affiliation identifier in the cloud server requirement is compared with the user affiliation identifier of the first sub-user node to determine whether the second sub-user node belongs to the same shared system.

[0154] Optionally, the user attribution identifier is a communication number;

[0155] Accordingly, the attribution determination module is specifically configured to:

[0156] According to the first communication number and the second communication number, it is determined whether the second sub-user node belongs to the same shared system.

[0157] Optionally, the demand information includes usage time and resource usage capacity;

[0158] Accordingly, the judgment module is specifically used to:

[0159] Determining whether the usage time is the idle time of the first sub-user node;

[0160] If the usage time is the idle time of the first sub-user node, whether to share resources with the second sub-user node is determined based on the resource usage capacity and the idle resources of the cloud server.

[0161] Optionally, the login password is a temporary login password with a preset validity period.

[0162] The embodiment of the present application also provides another cloud server sharing device, which is applied to the second sub-user node. The device of the embodiment of the present application includes: a request issuing module, a seventh processing module, a call processing module, an eighth processing module, a receiving module and a ninth processing module. The cloud server sharing device here can be a server or a terminal device, or a chip or integrated circuit that implements the functions of a server or a terminal device. It should be noted here that the division of the request issuing module, the seventh processing module, the call processing module, the eighth processing module, the receiving module and the ninth processing module is only a division of logical functions. Physically, the two can be integrated or independent.

[0163] Among them, the request publishing module is used to publish the cloud server demand in the blockchain, so that the first sub-user node responds to the cloud server demand, determines whether it belongs to the same shared system as the second sub-user node based on the user's belonging identifier, and if it is determined that it belongs to the same shared system as the second sub-user node, obtains a first communication number, encrypts the first communication number using the second sub-user node's public key according to a first preset algorithm to obtain a first encryption result, and sends the first encryption result and the first sub-user node's blockchain identifier to the blockchain network, wherein the cloud server demand includes the user's belonging identifier, the second sub-user node's blockchain identifier, and the demand information;

[0164] A seventh processing module is configured to receive the first encryption result and the first sub-user node blockchain identifier, and decrypt the first encryption result according to the first preset algorithm and the second sub-user node private key to obtain a first communication number;

[0165] a call processing module, configured to establish a call with a first sub-user node according to a first communication number, and transmit a second sub-user node blockchain identifier to the first sub-user node via call signaling, so that the first sub-user node receives the second sub-user node blockchain identifier transmitted by the second sub-user node via call signaling, obtain a second communication number according to the call, encrypt the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result, encrypt the second encryption result according to a public key of the second sub-user node to obtain a fourth encryption result, and send the fourth encryption result to the blockchain;

[0166] an eighth processing module, configured to receive the fourth encryption result, and decrypt the fourth encryption result according to the second sub-user node private key to obtain a second encryption result;

[0167] a receiving module, configured to receive, via a blockchain, a third encryption result and a second sub-user node blockchain identifier, wherein the third encryption result and the second sub-user node blockchain identifier are: a first sub-user node, based on demand information, determines whether to share resources with the second sub-user node; if it is determined that resources are to be shared with the second sub-user node, encrypting the cloud server address and login password using the second encryption result according to a third preset algorithm, and sending the obtained third encryption result to the blockchain;

[0168] The ninth processing module is used to decrypt the third encryption result according to the second encryption result and the third preset algorithm to obtain the cloud server address and login password, and share the cloud server resources of the first sub-user node according to the cloud server address and login password.

[0169] refer to Figure 5 , which shows a schematic diagram of the structure of a cloud server sharing device 500 suitable for implementing embodiments of the present disclosure. The cloud server sharing device 500 can be a terminal device or a server. The terminal device may include, but is not limited to, mobile terminals such as mobile phones, laptops, digital broadcast receivers, personal digital assistants (PDAs), tablet computers (Portable Android Devices, PADs), portable multimedia players (PMPs), in-vehicle terminals (e.g., in-vehicle navigation terminals), and fixed terminals such as digital TVs and desktop computers. Figure 5 The cloud server sharing device shown is only an example and should not bring any limitation to the functions and scope of use of the embodiments of the present disclosure.

[0170] like Figure 5 As shown, cloud server sharing device 500 may include a processing device (e.g., a central processing unit, a graphics processing unit, etc.) 501, which can perform various appropriate actions and processes based on programs stored in read-only memory (ROM) 502 or programs loaded from storage device 508 into random access memory (RAM) 503. RAM 503 also stores various programs and data required for the operation of cloud server sharing device 500. Processing device 501, ROM 502, and RAM 503 are interconnected via bus 504. An input / output (I / O) interface 505 is also connected to bus 504.

[0171] Typically, the following devices may be connected to the I / O interface 505: input devices 506 including, for example, a touch screen, a touchpad, a keyboard, a mouse, a camera, a microphone, an accelerometer, a gyroscope, etc.; output devices 507 including, for example, a liquid crystal display (LCD), a speaker, a vibrator, etc.; storage devices 508 including, for example, a magnetic tape, a hard disk, etc.; and communication devices 509. The communication devices 509 may allow the cloud server sharing device 500 to communicate with other devices wirelessly or by wire to exchange data. Figure 5 The cloud server sharing device 500 is shown as having various devices, but it should be understood that it is not required to implement or possess all the devices shown. More or fewer devices may be implemented or possessed instead.

[0172] In particular, according to an embodiment of the present disclosure, the process described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable medium, and the computer program includes program code for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network via the communication device 509, or installed from the storage device 508, or installed from the ROM 502. When the computer program is executed by the processing device 501, the above-mentioned functions defined in the method of the embodiment of the present disclosure are performed.

[0173] It should be noted that the computer-readable medium described above in the present disclosure may be a computer-readable signal medium or a computer-readable storage medium, or any combination thereof. Computer-readable storage media may include, for example, but not limited to, electrical, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or components, or any combination thereof. More specific examples of computer-readable storage media may include, but are not limited to, an electrical connection having one or more conductors, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination thereof. In the present disclosure, a computer-readable storage medium may be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In the present disclosure, a computer-readable signal medium may include a data signal propagated in baseband or as part of a carrier wave, carrying computer-readable program code. Such a propagated data signal may take a variety of forms, including, but not limited to, electromagnetic signals, optical signals, or any suitable combination thereof. A computer-readable signal medium may also be any computer-readable medium other than a computer-readable storage medium that can transmit, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device. Program code embodied on a computer-readable medium may be transmitted using any suitable medium, including but not limited to wire, optical cable, RF (radio frequency), or any suitable combination thereof.

[0174] The computer-readable medium may be included in the cloud server sharing device; or it may exist independently without being assembled into the cloud server sharing device.

[0175] The computer-readable medium carries one or more programs. When the one or more programs are executed by the cloud server sharing device, the cloud server sharing device executes the method shown in the above embodiment.

[0176] Computer program code for performing the operations of the present disclosure may be written in one or more programming languages, or a combination thereof, including object-oriented programming languages ​​such as Java, Smalltalk, C++, and conventional procedural programming languages ​​such as "C" or similar programming languages. The program code may be executed entirely on the user's computer, partially on the user's computer, as a stand-alone software package, partially on the user's computer and partially on a remote computer, or entirely on a remote computer or server. In cases involving a remote computer, the remote computer may be connected to the user's computer via any type of network, including a local area network (LAN) or a wide area network (WAN), or may be connected to an external computer (e.g., via the Internet using an Internet service provider).

[0177] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interface, device or unit, which can be electrical, mechanical or other forms.

[0178] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0179] Other embodiments of the present disclosure will readily occur to those skilled in the art after considering the specification and practicing the applications disclosed herein. This application is intended to cover any variations, uses, or adaptations of the present disclosure that follow the general principles of the present disclosure and include common knowledge or customary techniques in the art not disclosed herein. The description and examples are to be considered as exemplary only, with the true scope and spirit of the present disclosure being indicated by the following claims.

[0180] It should be understood that the present disclosure is not limited to the exact structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present disclosure is limited only by the appended claims.

Claims

1. A cloud server sharing method, characterized in that: Applied to a first sub-user node, the method includes: In response to a cloud server requirement published by a second sub-user node in the blockchain, determining, based on a user affiliation identifier, whether the second sub-user node belongs to the same shared system as the second sub-user node, wherein the cloud server requirement includes the user affiliation identifier, the second sub-user node blockchain identifier, and the requirement information; If it is determined that the second sub-user node belongs to the same shared system, obtaining a first communication number, encrypting the first communication number using the public key of the second sub-user node according to a first preset algorithm to obtain a first encryption result, sending the first encryption result and the blockchain identifier of the first sub-user node to the blockchain network, so that the second sub-user node receives the first encryption result and the first sub-user node blockchain identifier, decrypting the first encryption result according to the first preset algorithm and the second sub-user node private key to obtain the first communication number, establishing a call with the first sub-user node according to the first communication number, and transmitting the second sub-user node blockchain identifier to the first sub-user node through the call signaling; receiving a second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtaining a second communication number based on the call; encrypting the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result; Encrypting the second encrypted result using the public key of the second sub-user node to obtain a fourth encrypted result, and sending the fourth encrypted result to the blockchain so that the second sub-user node receives the fourth encrypted result, and decrypting the fourth encrypted result using the private key of the second sub-user node to obtain the second encrypted result; determining, based on the demand information, whether to share resources with the second sub-user node; If it is determined that resources are shared with the second sub-user node, encrypting the cloud server address and login password using the second encryption result according to a third preset algorithm to obtain a third encryption result; The third encryption result and the second sub-user node blockchain identifier are sent to the blockchain, so that the second sub-user node receives the third encryption result, decrypts the third encryption result according to the second encryption result and the third preset algorithm to obtain the cloud server address and login password, and shares the cloud server resources of the first sub-user node according to the cloud server address and the login password.

2. The method according to claim 1, characterized in that The determining, based on the user belonging identifier, whether the second sub-user node belongs to the same shared system includes: The user affiliation identifier in the cloud server requirement is compared with the user affiliation identifier of the first sub-user node to determine whether the second sub-user node belongs to the same shared system.

3. The method according to claim 1, characterized in that The user attribution identifier is a communication number; Correspondingly, determining whether the second sub-user node belongs to the same shared system according to the user belonging identifier includes: According to the first communication number and the second communication number, it is determined whether the second sub-user node belongs to the same shared system.

4. The method according to any one of claims 1 to 3, characterized in that The demand information includes usage time and resource usage capacity; Accordingly, the determining, based on the demand information, whether to share resources with the second sub-user node includes: determining whether the usage time is the idle time of the first sub-user node; If the usage time is the idle time of the first sub-user node, whether to share resources with the second sub-user node is determined according to the resource usage capacity and the idle resources of the cloud server.

5. The method according to any one of claims 1 to 3, characterized in that The login password is a temporary login password with a preset validity period.

6. A cloud server sharing method, characterized in that: Applied to the second sub-user node, the method includes: Publishing a cloud server demand in the blockchain, so that the first sub-user node responds to the cloud server demand and determines, based on the user's affiliation identifier, whether it belongs to the same shared system as the second sub-user node. If it is determined that the second sub-user node belongs to the same shared system, obtaining a first communication number, encrypting the first communication number using the second sub-user node's public key according to a first preset algorithm to obtain a first encryption result, and sending the first encryption result and the first sub-user node's blockchain identifier to the blockchain network, wherein the cloud server demand includes the user's affiliation identifier, the second sub-user node's blockchain identifier, and the demand information; receiving the first encryption result and the first sub-user node blockchain identifier, and decrypting the first encryption result according to a first preset algorithm and a second sub-user node private key to obtain the first communication number; Establishing a call with the first sub-user node according to the first communication number, and transmitting the second sub-user node blockchain identifier to the first sub-user node through call signaling, so that the first sub-user node receives the second sub-user node blockchain identifier transmitted by the second sub-user node through call signaling, and obtaining a second communication number according to the call, encrypting the first communication number and the second communication number according to a second preset algorithm to obtain a second encryption result, encrypting the second encryption result according to the second sub-user node public key to obtain a fourth encryption result, and sending the fourth encryption result to the blockchain; receiving the fourth encryption result, and decrypting the fourth encryption result according to the second sub-user node private key to obtain a second encryption result; Receiving, through the blockchain, a third encryption result and a second sub-user node blockchain identifier, wherein the third encryption result and the second sub-user node blockchain identifier are for the first sub-user node to determine, based on the demand information, whether to share resources with the second sub-user node; if it is determined that resources are to be shared with the second sub-user node, encrypting the cloud server address and login password using the second encryption result according to a third preset algorithm, and sending the obtained third encryption result to the blockchain; The third encryption result is decrypted according to the second encryption result and the third preset algorithm to obtain a cloud server address and a login password, and the cloud server resources of the first sub-user node are shared according to the cloud server address and the login password.

7. A cloud server sharing device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the cloud server sharing method according to any one of claims 1 to 5.

8. A cloud server sharing device, characterized in that: include: at least one processor; as well as a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the cloud server sharing method according to claim 6.

9. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the cloud server sharing method according to any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the cloud server sharing method according to claim 6.

Images