A blockchain-based software service management method, device and equipment

Abstract

Embodiments of the present specification disclose a blockchain-based software service management method, device and equipment. The scheme can include: deploying a software service management platform based on a blockchain node in a blockchain network in advance, each software service management platform can have management authority for software services provided at the blockchain network, so that a platform user at any software service management platform can send a management instruction for a target software service to the software service management platform to manage the target software service provided at the blockchain network based on the software service management platform and the corresponding blockchain node.

Description

Technical Field

[0001] This application relates to the field of software service management technology, and in particular to a software service management method, apparatus and equipment based on blockchain. Background Technology

[0002] SaaS, short for Software as a Service, is a new software service delivery model that has emerged with the development of internet technology and the maturity of application software. Service providers have full control over the management and maintenance of application software and publish corresponding software services on a SaaS platform. This allows service requesters to order the software services they need from the SaaS platform. Subsequently, service requesters can access the software services provided by the service provider through the SaaS platform or the internet without needing to maintain the application software themselves, making it convenient and fast. Currently, the listing, ordering, and evaluation of software services on SaaS platforms are usually controlled solely by the SaaS platform provider, which affects the transparency and credibility of software service management.

[0003] Therefore, improving the transparency and credibility of software service management has become an urgent technical problem to be solved. Summary of the Invention

[0004] The embodiments of this specification provide a blockchain-based software service management method, apparatus, and device that can improve the transparency and trustworthiness of software service management.

[0005] To solve the above-mentioned technical problems, the embodiments in this specification are implemented as follows: This specification provides an embodiment of a blockchain-based software service management method, comprising: The target platform obtains management instructions from platform users for the target software service; the target software service is a software service provided by a service provider to a service requester based on a blockchain network; the target platform is any software service management platform deployed on a blockchain node in the blockchain network, and the target platform has management authority over the software service provided on the blockchain network. In response to the management instruction, first blockchain transaction information for managing the target software service is generated; The first blockchain transaction information is sent to the blockchain network using the blockchain node used to deploy the target platform.

[0006] This specification provides an embodiment of a blockchain-based software service management device, comprising: The first acquisition module is used by the target platform to acquire management instructions from platform users for the target software service; the target software service is a software service provided by a service provider to a service requester based on a blockchain network; the target platform is any software service management platform deployed on a blockchain node in the blockchain network, and the target platform has management authority over the software service provided by the blockchain network. The first generation module is configured to generate first blockchain transaction information for managing the target software service in response to the management instruction. The first sending module is used to send the first blockchain transaction information to the blockchain network using the blockchain node used to deploy the target platform.

[0007] This specification provides an embodiment of a blockchain-based software service management device, comprising: At least one processor; and, 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, the instructions being executed by the at least one processor to enable the at least one processor to: The target platform obtains management instructions from platform users for the target software service; the target software service is a software service provided by the service provider to the service requester based on the blockchain network; the target platform is any software service management platform deployed on the blockchain node in the blockchain network, and the target platform has management authority over the software service provided on the blockchain network. In response to the management instruction, first blockchain transaction information for managing the target software service is generated; The first blockchain transaction information is sent to the blockchain network using the blockchain node used to deploy the target platform.

[0008] At least one embodiment provided in this specification can achieve the following beneficial effects: A software service management platform is pre-deployed on blockchain nodes within the blockchain network. This grants each software service management platform management authority over the software services provided on the blockchain network. Users on the target platform (e.g., any software service management platform) can then manage the target software services provided on the blockchain network by sending management commands to the target platform and corresponding blockchain nodes. Since each user on the target platform can manage the target software services independently, and the management information is stored on the blockchain network, this enhances the transparency and trustworthiness of software service management. Attached Figure Description

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

[0010] Figure 1 A schematic diagram illustrating an application scenario of a blockchain-based software service management method provided in the embodiments of this specification; Figure 2 A flowchart illustrating a blockchain-based software service management method provided in the embodiments of this specification; Figure 3 The embodiments provided in this specification correspond to Figure 2 A swimlane flowchart illustrating a blockchain-based software service management method. Figure 4 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a blockchain-based software service management device; Figure 5 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a blockchain-based software service management device. Detailed Implementation

[0011] To make the objectives, technical solutions, and advantages of one or more embodiments of this specification clearer, the technical solutions of one or more embodiments of this specification will be clearly and completely described below in conjunction with specific embodiments and corresponding drawings. Obviously, the described embodiments are only a part of the embodiments of this specification, and not all of them. Based on the embodiments in this specification, all other embodiments obtained by those skilled in the art without creative effort are within the protection scope of one or more embodiments of this specification.

[0012] The technical solutions provided in the various embodiments of this specification are described in detail below with reference to the accompanying drawings.

[0013] In existing technologies, as the number of participants in alliances increases, the demands for fairness, transparency, and autonomy among these participants also rise. In alliance scenarios, the inconsistent access standards of different SaaS platforms make it inconvenient for participants to access different platforms. Furthermore, the need to select a single participant to manage the SaaS platform not only affects the enthusiasm of other alliance members but also compromises the transparency and credibility of software service management by relying on a single party to manage the release, subscription, and evaluation of software services on the SaaS platform.

[0014] To address the shortcomings of existing technologies, this solution provides the following embodiments: Figure 1 This is a schematic diagram illustrating an application scenario of a blockchain-based software service management method provided in the embodiments of this specification.

[0015] like Figure 1 As shown, a blockchain network can have multiple blockchain nodes, such as node 101, node 102, node 103, node 104, and node 105. A blockchain can be understood as a data chain composed of multiple blocks stored sequentially. Each block's header contains its timestamp, the hash value of the previous block, and the hash value of the current block, enabling mutual verification between blocks and forming an immutable blockchain. Each block can be understood as a data block (a unit of data storage). As a decentralized database, a blockchain is a chain of data blocks linked together using cryptographic methods. Each data block contains information about a network transaction, used to verify the validity of the information (anti-counterfeiting) and generate the next block. The chain formed by connecting blocks end-to-end constitutes the blockchain. If data within a block needs to be modified, the content of all subsequent blocks must be modified, and the data backed up by all nodes in the blockchain network must also be modified. Therefore, blockchains are difficult to tamper with or delete, and once data is stored on the blockchain, it is a reliable method for maintaining content integrity.

[0016] Figure 1The document also illustrates devices 110 and 120 equipped with any software service management platform deployed on blockchain nodes within the blockchain network. Assuming the software service management platform on device 110 is a target platform, and the target platform has management authority over the software services provided on the blockchain network, a platform user can manipulate device 110 to allow the target platform to obtain management instructions from the platform user for the target software services provided on the blockchain network. In response to the management instructions, the target platform can also generate first blockchain transaction information for managing the target software services. Furthermore, by utilizing the blockchain node used to deploy the target platform, the first blockchain transaction information is sent to the blockchain network, thereby achieving management of the target software services.

[0017] Figure 1 The proposed solution enhances the transparency and trustworthiness of software service management by enabling users on various platforms to conveniently manage target software services provided by the blockchain network based on the target platform. Furthermore, since users on each platform only need to connect to a single software service management platform to achieve interoperability with other software service management platforms through the blockchain network, it also simplifies the operational convenience for various participants when accessing different software service management platforms.

[0018] Next, a blockchain-based software service management method provided in the embodiments of the specification will be described in detail with reference to the accompanying drawings: Figure 2 This is a flowchart illustrating a blockchain-based software service management method provided in an embodiment of this specification. From a programming perspective, the executor of this process can be a device equipped with the target platform, or an application program of the target platform. Figure 2 As shown, the process may include the following steps: Step 202: The target platform obtains management instructions from platform users for the target software service; the target software service is a software service provided by the service provider to the service requester based on the blockchain network; the target platform is any software service management platform deployed on the blockchain node in the blockchain network, and the target platform has management authority for the software service provided on the blockchain network.

[0019] In the embodiments described in this specification, service providers can publish software services in a blockchain network, and service demanders can order and evaluate the software services published in the blockchain network, thereby building a software service market (i.e., a SaaS market) based on the blockchain network.

[0020] Specifically, since blockchain nodes in a blockchain network typically have management authority over the software services provided on the blockchain network, one or more software service management platforms (e.g., SaaS platforms) with management authority over the software services provided on the blockchain network can be deployed on top of the blockchain nodes. These software service management platforms typically have a user interface (UI) to facilitate the management of software services on the blockchain network by service providers and service users through the user interface.

[0021] In practical applications, service providers and service requesters typically need to obtain prior access to the target platform to operate its user interface as platform users. This allows the target platform to obtain management instructions from the platform users regarding the target software service. These management instructions can be of various types and vary depending on the platform user's role. For example, when the platform user is a service provider, the management instructions may include service publishing instructions and service modification instructions. Conversely, when the platform user is a service requester, the management instructions may include service ordering instructions and service evaluation instructions.

[0022] In practical applications, since blockchain nodes often have their own independent local area networks (LANs), only data requiring collaboration is transmitted through the blockchain network. Therefore, each software service management platform deployed on a blockchain node can build its own local software service marketplace (i.e., a local SaaS marketplace). Simultaneously, because these software service management platforms can communicate with each other through the blockchain network, they can collaboratively build a distributed software service marketplace (i.e., a distributed SaaS marketplace).

[0023] Step 204: In response to the management instruction, generate first blockchain transaction information for managing the target software service.

[0024] In the embodiments described in this specification, the target platform typically needs to generate first blockchain transaction information that matches the management instructions, so as to manage the target software service based on the first blockchain transaction information. Specifically, the format of the blockchain transaction to be generated for each type of management instruction can be predetermined. After obtaining the management instruction in step 202, first blockchain transaction information that conforms to the preset format corresponding to the management instruction can be generated, so that each node in the blockchain network can identify the blockchain transaction, thereby realizing the management function for the target software service. In practical applications, the format and specific content of the blockchain transaction information generated for managing software services for different management instructions are usually not consistent. Subsequent embodiments will provide specific explanations, which will not be repeated here.

[0025] Step 206: Using the blockchain node used to deploy the target platform, send the first blockchain transaction information to the blockchain network.

[0026] In the embodiments described in this specification, the target platform can typically communicate with the blockchain node on which it is deployed, thereby enabling it to use the blockchain node to send the first blockchain transaction information to the blockchain network. This allows the platform user to manage the target software service after the blockchain network reaches a consensus on the first blockchain transaction information.

[0027] Figure 2 The proposed method improves the transparency and credibility of software service management because users on each target platform can manage the target software service themselves, and management information is stored on the blockchain network. Furthermore, each alliance member can build a local SaaS service marketplace on their respective blockchain nodes and can make their service capabilities visible and shared as needed, thus increasing member participation. Simultaneously, since management data related to the software service is exchanged through the blockchain network, alliance participants typically only need to connect to any one blockchain-based software service management platform to establish service connections with other blockchain-based software service management platforms, thereby reducing the access and interoperability costs for multiple software service management platforms.

[0028] based on Figure 2 In addition to the method described in the embodiments of this specification, some specific implementation schemes of the method are also provided, which will be described below.

[0029] In the embodiments of this specification, before deploying a software service management platform using a blockchain node, it is usually necessary to verify in advance whether the blockchain node is trustworthy. If it is trustworthy, the blockchain node can be allowed to manage the software services on the blockchain network, thereby ensuring the security and trustworthiness of the software service management process.

[0030] Based on this, step 202: before the target platform obtains the management instructions from the platform user for the target software service, may further include: Obtain the node identity information of the blockchain node.

[0031] Based on the node identity information, a second blockchain transaction information is generated; the second blockchain transaction information is used to request the blockchain node to grant management authority over the software services provided by the blockchain network; the blockchain network is used to grant the blockchain node management authority over the software services provided by the blockchain network after the node identity information is verified.

[0032] Using the blockchain node, the second blockchain transaction information is sent to the blockchain network.

[0033] In this embodiment, the node identity information of the blockchain node may include at least: unique node identification information and node public key information. The unique node identification information may include information such as node ID and node name that can uniquely identify the blockchain node. The node private key information corresponding to the node public key information is usually stored by each blockchain node itself. Subsequently, blockchain nodes can use their respective node private key information to digitally sign the blockchain transaction information they send. Other blockchain nodes can then use the node public key information pre-submitted by the blockchain node to verify the signature of the blockchain transaction, thereby ensuring the security and trustworthiness of the blockchain network operation. In practical applications, the node identity information of the blockchain node may also include node remarks, such as the identification information of the organization deploying the blockchain node.

[0034] In this embodiment of the specification, after the blockchain node sends the second blockchain transaction information to the blockchain network, the blockchain network needs to perform a node identity information verification operation based on the second blockchain transaction information. If the verification is successful, it can be indicated that the blockchain node is a trusted node, thereby granting the blockchain node management authority for the software services provided by the blockchain network, so that the blockchain node can be registered in the distributed SaaS service market built on the blockchain network.

[0035] In practical applications, blockchain networks can use smart contracts to verify node identity information based on the second blockchain transaction information. Specifically, since blockchain nodes deployed by trusted institutions are typically trusted nodes, the smart contract can be used to identify whether the blockchain node is deployed by a trusted institution based on the second blockchain transaction information. If so, a verification result indicating that the node's identity verification has passed is generated. This helps ensure the security and trustworthiness of software service management based on blockchain nodes.

[0036] This specification also provides embodiments for deploying a target platform and granting that platform management permissions for the software services provided by the blockchain network. These are explained for clarity.

[0037] Specifically, before step 202: the target platform obtains management instructions from platform users regarding the target software service, it may also include: Run the target platform based on the installation files of the target platform.

[0038] Based on the node identity information of the blockchain node, a binding relationship is established between the target platform and the blockchain node; the target platform is used to obtain management permissions for the software services provided by the blockchain network based on the binding relationship.

[0039] In the embodiments described in this specification, after the blockchain network verifies the identity information of a blockchain node and grants the blockchain node management authority for the software services provided by the blockchain network, it can deploy the target platform (i.e., the software service management platform) based on the blockchain node. Specifically, a trusted organization that deploys the blockchain node can obtain the installation file of the target platform and run the target platform using the installation file.

[0040] In the embodiments of this specification, there are multiple ways to obtain the installation files of the target platform.

[0041] Specifically, the installation file based on the target platform, before running the target platform, may further include: The installation file for the target platform is downloaded from the blockchain network using the blockchain node. Alternatively, Download the installation file for the target platform from the specified link address or the specified application.

[0042] In this embodiment, the installation file of the target platform can be pre-stored in a designated data storage space on the blockchain network. After the blockchain node's identity information is verified, the blockchain node can retrieve the installation file of the target platform from the chain. Alternatively, the installation file of the target platform can be published in the storage space corresponding to a designated application or a designated link address, allowing the blockchain node to retrieve the installation file of the target platform from off-chain.

[0043] In the embodiments described in this specification, the installation files of the target platform can be software development scaffolding. Trusted organizations can either directly provide the software service management platform obtained by running the installation files of the target platform to platform users, or utilize the secondary development and expansion capabilities of the installation files of the target platform to independently build a software service management platform that meets actual needs and provide it to platform users.

[0044] In practical applications, the target platform can be a web application. After deploying the target platform, the trusted organization can provide its access address to platform users, allowing them to open and use the target platform in their personal browsers. Alternatively, the target platform can be an app client, which platform users can install and run on their personal devices for convenient use. No specific limitations are imposed on this approach.

[0045] In the embodiments described in this specification, the installation files of the target platform typically provide basic blockchain contract interfaces, basic information configuration, default UI interaction, and secondary development and extension capabilities. The basic blockchain contract interfaces may include: identity authentication interfaces, service listing / delisting interfaces, service retrieval interfaces, service ordering interfaces, service authentication interfaces, and service evaluation interfaces. Basic information configuration may include: identity information configuration of bound blockchain nodes, service operation configuration, and chain information configuration. Secondary development and extension capabilities may include: support for self-implemented UI interaction, support for self-implemented local data caching, support for self-implemented smart contract interception logic, extensible configuration notification capabilities, and extensible implementation of early warning and monitoring capabilities.

[0046] In this embodiment, the basic information configuration capability can be used to establish a binding relationship between the target platform and the blockchain node based on the node identity information of the blockchain node. Specifically, the target platform's UI interface can provide controls for inputting the node identity information of the blockchain node to be bound. Trusted institutions can use these controls to input information such as the node's private key, node name, node ID, and node IP address at the target platform to establish a binding relationship between the two. In addition, the target platform's UI interface can also provide controls for inputting the chain information of the blockchain to which the blockchain node to be bound belongs, so as to clearly identify the blockchain network supporting the target platform's software service management.

[0047] In the embodiments described in this specification, since the target platform can obtain relatively private node identity information of blockchain nodes (e.g., node private key information), if the blockchain node is trustworthy, the target platform is usually also trustworthy, thereby enabling the target platform to obtain management rights over the software services provided by the blockchain network.

[0048] In practical applications, after establishing the binding relationship between the target platform and the blockchain node, it is also necessary to authenticate the target platform at the blockchain network to improve the security of software service management based on the target platform.

[0049] Based on this, before step 202: the target platform obtains management instructions from platform users for the target software service, it may also include: Based on the binding relationship, a third blockchain transaction is generated using the node identity information of the blockchain node; the third blockchain transaction is used to request the target platform to grant management permissions for the software services provided by the blockchain network; the blockchain network is used to respond to the third blockchain transaction by sending a software service management permission token to the target platform.

[0050] Using the blockchain node, the third blockchain transaction information is sent to the blockchain network.

[0051] In the embodiments of this specification, since the target platform can store the private key information of the blockchain node after establishing the binding relationship between the target platform and the blockchain node, when the target platform generates third blockchain transaction information for identity authentication, it can carry the unique identifier information of the blockchain node (e.g., node name, node ID, node IP address, etc.) in the third blockchain transaction information, and use the private key information of the blockchain node to digitally sign the third blockchain transaction information to ensure the credibility of the third blockchain transaction information, thereby improving the reliability and security of identity authentication for the target platform.

[0052] In the embodiments described in this specification, the blockchain network can use the public key information of the blockchain node stored on the chain to perform digital signature verification on the transaction information of the third blockchain. If the verification is successful, a software service management permission token (e.g., AccessToken) can be issued to the target platform so that the target platform can manage the software services provided by the blockchain network based on the software service management permission token.

[0053] In practical applications, to further ensure the reliability and security of identity authentication for target platforms, after issuing software service management permission tokens to the target platform, login status verification for data interface calls can be performed. This allows for pre-identification of whether the target platform has permission to use the specified data interface, whether there are any anomalies in the target platform's operating environment or user operations, and whether the user operations are within the default validity period. If the login status verification indicates no risk is identified, the identity verification for the target platform can be terminated, and an initialization data package can be sent to the target platform, thereby enabling the target platform's local SaaS marketplace to connect to a distributed SaaS marketplace built on a blockchain network.

[0054] In the embodiments of this specification, a method for the target platform to obtain the initialization data packet is also provided, and the relevant service information in the initialization data packet is shown.

[0055] Specifically, before step 202: the target platform obtains management instructions from platform users regarding the target software service, it may also include: Obtain relevant service information about the software services provided by the blockchain network.

[0056] Display relevant service information of the software service on the target platform.

[0057] In the embodiments described in this specification, the initialization data packet typically contains relevant service information about the software services currently available on the blockchain network, such as unique service identifiers, service descriptions, and service evaluations. After obtaining the relevant service information based on the initialization data packet, the target platform can usually display this information in its UI for users to view, thus facilitating users to publish, subscribe to, and evaluate software services according to their actual needs.

[0058] In the embodiments described in this specification, the target platform typically needs to perform a trust verification on the platform user in advance. If the verification result indicates that the platform user is trustworthy, the platform user is allowed to use the target platform to manage the software services on the blockchain network. Otherwise, the platform user will be prohibited from using the target platform to manage the software services on the blockchain network, thereby improving the security and trustworthiness of the management of the software services.

[0059] Based on this, before step 202: the target platform obtains management instructions from platform users for the target software service, it may also include: The target platform obtains a platform usage permission acquisition request from the platform user; the platform usage permission acquisition request carries the user's identity information.

[0060] In response to the request to obtain platform access rights, a trusted verification is performed on the user's identity information on the platform, and a verification result is obtained.

[0061] If the verification result indicates that the user's identity information for the platform user has been verified, then the platform user is granted access to the target platform.

[0062] In the embodiments described in this specification, platform users typically need to send their personal user identity information to the target platform so that the target platform can perform trusted verification of the platform user based on this user identity information. The platform user's user identity information may include: user public key information, user unique identification information (e.g., distributed identity (DID) information), user identity verification documents (e.g., business license information), and a digital signature generated using the user's private key information corresponding to the user's public key information.

[0063] In practical applications, the target platform can either automatically perform trusted verification of the user's identity information, or a trusted institution can be used to perform trusted verification of the user's identity information; there is no specific limitation on this. However, if the verification result indicates that the user's identity information has been verified successfully, it usually means that the user is a trusted user, and thus the user can be granted access to the target platform. For example, a login token for the target platform can be issued to the user, or a user account can be registered for the user, so that the user can control the target platform and manage the target software service based on the login token or user account.

[0064] In the embodiments of this specification, if the user identity information of the platform user is verified, it is usually necessary to store the user identity information of the platform user in the blockchain network in order to ensure the security and trustworthiness of the subsequent software service management operations of the platform user.

[0065] Based on this, before step 202: the target platform obtains management instructions from platform users for the target software service, it may also include: If the verification result indicates that the user's identity information for the platform user has been verified, then the platform user's public key information and the platform user's unique identifier information are associated and stored in the blockchain network.

[0066] Correspondingly, step 204: generating first blockchain transaction information for managing the target software service, which may specifically include: By using at least one of the node private key information corresponding to the node public key information and the user private key information corresponding to the user public key information, a digital signature is performed on the blockchain transaction information used to manage the target software service to obtain the first blockchain transaction information.

[0067] In this embodiment of the specification, after the user's identity information on the platform is verified, the target platform can generate blockchain transaction information carrying the user's public key information and unique identifier information, and digitally sign the blockchain transaction information using the private key information of the blockchain node bound to the target platform. After the blockchain network verifies the trustworthiness of the blockchain transaction information using the public key information of the blockchain node, it can associate and store the user's public key information, unique identifier information, target platform, and blockchain node, thereby using the blockchain node to provide trust endorsement for the target platform and its users.

[0068] In this embodiment, since the blockchain network can store the public key information of the blockchain nodes and the public key information of the platform users, at least one of the node private key information corresponding to the node public key information and the user private key information corresponding to the user public key information can be used to digitally sign the first blockchain transaction information used to manage the target software service. Subsequently, if other nodes in the blockchain network can successfully verify the signature of the first blockchain transaction information based on the public key information stored in the blockchain network, it can be shown that the first blockchain transaction information is generated by a trusted user and has not been tampered with. Therefore, the target software service in the blockchain network can be managed based on the first blockchain transaction information to ensure the trustworthiness and security of the software service management.

[0069] In the embodiments of this specification, the types of management instructions given by platform users for the target software service can be various, and these will be explained for the sake of understanding.

[0070] Type 1: The management instructions can be used to instruct the release of the target software service on the blockchain network.

[0071] Correspondingly, step 204: In response to the management instruction, generate first blockchain transaction information for managing the target software service, which may specifically include: In response to the management command, obtain the service description information of the target software service.

[0072] Based on the service description information, a first blockchain transaction is generated for publishing the target software service.

[0073] In the embodiments described in this specification, when a platform user needs to publish a target software service, that platform user is considered a service provider. Therefore, the platform user typically needs to input service description information for the target software service at the target platform, such as the software service name, input and output parameters, service call configuration information, service operation configuration information, and service billing policy information. In addition, the service description information for the target software service may also include the platform user's unique identifier information, the unique identifier information of the blockchain node bound to the target platform, etc., to identify the service provider offering the target software service, and the blockchain node that provides trust endorsement for the service provider.

[0074] In the embodiments described in this specification, the first blockchain transaction information may include service description information of the target software service, as well as digital signature information generated using the private key information of the platform user and / or the blockchain node. The blockchain network can invoke a service listing smart contract to issue a unique software service identifier, such as a globally unique software service ID, to the target software service after verifying the digital signature information in the first blockchain transaction information. The blockchain network can also publish the service description information of the target software service for platform users on various software service management platforms deployed on blockchain nodes to view and order the software service.

[0075] In the embodiments described in this specification, after a service requester orders a target software service on the blockchain network, the service provider typically needs to review the software service order for that target software service in order to decide whether to provide the software service to the service requester.

[0076] Based on this, after sending the first blockchain transaction information to the blockchain network, step 206 may further include: The target platform obtains software service orders for the target software service that have been paid for by the target user from the blockchain network.

[0077] Receive the review results from users of the platform regarding their software service orders.

[0078] If the audit result indicates that the audit is successful, the software service key is stored in the blockchain network so that the target user can obtain the software service key; the software service key is used to grant the target user the right to use the target software service.

[0079] If the review result indicates that the review is unsuccessful, information indicating that the platform user refuses to provide the target software service to the target user can be stored in the blockchain network so that the target user can be aware of the information.

[0080] In this embodiment, after a target user orders a target software service using a software service management platform deployed on a blockchain node and completes payment for the software service order, the service provider of the target software service (i.e., the platform user mentioned in step 202) can access the order information of the software service order from the target platform they are using. In practical applications, the order information of the software service order may include: the unique identifier of the service requester (i.e., the target user), the unique identifier of the blockchain node bound to the software service management platform used by the service requester, the order ID, the software service ID, the service start and end time, the billing policy, and other information.

[0081] In this embodiment, the service provider of the target software service can review the order information of the software service order to decide whether to provide the target software service to the target user according to the order. If so, a software service key can be generated and encrypted using the public key of the service requester (i.e., the target user) or the public key of the blockchain node bound to the software service management platform used by the service requester. The encrypted software service key can then be stored on the blockchain network so that the service requester (i.e., the target user) can obtain it from the blockchain network. Simultaneously, a service authorization notarization smart contract on the blockchain network can be used to notarize the authorization status of the software service order, thereby improving the traceability of the software service authorization process.

[0082] In this embodiment of the specification, the service provider (i.e., the platform user mentioned in step 202) may not store the software program of the target software service on the blockchain network, but instead run and maintain the software program of the target software service off-chain. Based on this, when the target user needs to obtain the target software service, they can use the software service key to generate a service acquisition request and send the service acquisition request to the service provider via off-chain methods or the blockchain network. The service provider can then send the feedback result generated in response to the service acquisition request to the target user via off-chain methods or the blockchain network; no specific limitations are imposed on this.

[0083] In the embodiments described in this specification, after the service provider publishes the target software service, there may be a need to modify some of the service description information.

[0084] Based on this, in Type 2, the management instructions can also be used to instruct the platform user to modify the target software service published on the blockchain network.

[0085] Correspondingly, step 204: In response to the management instruction, generate first blockchain transaction information for managing the target software service, which may specifically include: In response to the management command, obtain the modification information of the service description information for the target software service.

[0086] Based on the modified information, a first blockchain transaction is generated for modifying the target software service.

[0087] In the embodiments described in this specification, the blockchain network can invoke a service modification smart contract to modify the service description information of the published target software service based on the first blockchain transaction information used to modify the target software service, and broadcast the notification to each software service management platform to maintain the consistency between each local SaaS marketplace and on-chain data.

[0088] Based on this, after step 206: sending the first blockchain transaction information to the blockchain network, it may further include: Obtain the modified service description information of the target software service from the blockchain network.

[0089] The modified service description information of the target software service is displayed on the target platform so that platform users on the target platform can browse the relevant service information of the modified target software service.

[0090] In the embodiments described in this specification, the service requester typically needs to use the target platform to order the target software service.

[0091] Based on this, in Type 3, the management instructions can be used to instruct the ordering of the target software service published on the blockchain network.

[0092] Correspondingly, step 204: In response to the management instruction, generate first blockchain transaction information for managing the target software service, which may specifically include: In response to the management command, obtain the subscription information for the target software service.

[0093] Based on the order information, a first blockchain transaction is generated for ordering the target software service.

[0094] In the embodiments described in this specification, when a platform user needs to order a target software service, the platform user is considered a service requester. The ordering information for the target software service may include: the software service ID, pricing strategy, payment channel, and payment amount. The payment channel may include: offline banking channels, third-party payment channels, digital asset channels, etc. In practical applications, the first blockchain transaction information used to order the target software service may, in addition to the above ordering information, also include a timestamp and the private key signature of the blockchain node bound to the platform user and / or the target platform they are using.

[0095] In the embodiments described in this specification, the blockchain network can invoke a service purchase application smart contract to generate payment order information corresponding to the payment channel carried by the first blockchain transaction information after the signature verification of the first blockchain transaction information is passed, thereby facilitating payment by platform users.

[0096] Based on this, after step 206: sending the first blockchain transaction information to the blockchain network, it may further include: The payment order information corresponding to the first blockchain transaction information is obtained from the blockchain network; the payment order information is used to make payments for software service orders generated based on the order information.

[0097] The payment order information is displayed on the target platform.

[0098] In the embodiments described in this specification, the blockchain network has the ability to interact with the servers of various payment channels. Therefore, upon receiving first blockchain transaction information indicating that a platform user needs to order target software services using a designated payment channel, it can obtain payment order information corresponding to the first blockchain transaction information from the server of that designated payment channel. The target platform can then obtain this payment order information from the blockchain network and display it to the platform user (i.e., the service requester).

[0099] Subsequently, platform users can use the designated payment channel to make payments for the order information. After the payment is completed, the server of the designated payment channel can send a message to the blockchain network indicating that the payment order has been completed. The blockchain network can then invoke the service purchase confirmation contract to send the software service order to the service provider for review. Upon successful review, the service provider will send the software service key back to the platform user, allowing the user to use this key to obtain the purchased software service.

[0100] Based on this, after displaying the payment order information on the target platform, it may further include: Obtain the software service key corresponding to the software service order from the blockchain network; the software service key is used to grant the platform user the right to use the target software service; the software service key is stored in the blockchain network by the service provider of the target software service after confirming that the software service order payment has been completed and the software service order has been approved.

[0101] In the embodiments described in this specification, after ordering and enjoying the target software service, the service requester can usually evaluate the target software service for reference by other service requesters.

[0102] Based on this, in Type 4, the management instructions can be used to instruct the publication of evaluation information for the target software service on the blockchain network.

[0103] Correspondingly, step 204: In response to the management instruction, generate first blockchain transaction information for managing the target software service, which may specifically include: In response to the management command, obtain evaluation information for the target software service.

[0104] Based on the evaluation information, first blockchain transaction information is generated for evaluating the target software service.

[0105] In the embodiments of this specification, the first blockchain transaction information may typically carry evaluation information of the platform user regarding the target software service they have ordered. For example, this may include the unique identifier of the service requester (i.e., the platform user mentioned in step 202), the unique identifier of the blockchain node used by the service requester, the unique identifier of their software service order, the unique identifier of the target software service they ordered, and evaluation information. In addition, it may also include the unique identifier of the service provider of the target software service, and the unique identifier of the blockchain node used by the service provider. The first blockchain transaction information may also carry a timestamp and the private key signature information of the service requester and the blockchain node it uses.

[0106] A blockchain network can invoke a service evaluation notarization smart contract to store the first blockchain transaction information, thereby achieving reliable notarization of evaluation information for the target software service. Subsequently, the blockchain network can also send a message indicating that the notarization of the evaluation information for the target software service has been successful to the target platform, so that users on the platform are aware that their submitted evaluation information has been successfully submitted to the distributed SaaS marketplace built on the blockchain network.

[0107] Figure 3 The embodiments provided in this specification correspond to Figure 2 A swimlane flowchart illustrating a blockchain-based software service management method. (Example) Figure 3 As shown, this blockchain-based software service management process can involve various stakeholders, including service requesters, service providers, target platforms, and the blockchain network. The target platform can be any software service management platform deployed on a blockchain node within the blockchain network. The target platforms used by the service requester and service provider can be the same or different; there are no specific restrictions on this.

[0108] During the platform deployment phase, trusted institutions can pre-verify the identity information of blockchain nodes on the blockchain network. This allows them to use verified blockchain nodes to download the target platform's installation file from the blockchain network and run the target platform using that file. Trusted institutions can also establish a binding relationship between the target platform and the blockchain nodes based on their node identity information. Based on this binding relationship, they can then use the blockchain node's identity information to generate and send third-party blockchain transaction information to the blockchain network.

[0109] In response to third-party blockchain transaction information, the blockchain network can send a software service management permission token to the target platform. After receiving the token, the target platform can also obtain and display relevant service information about the software services provided by the blockchain network to complete the deployment of the target platform. Figure 3 (Not shown).

[0110] During the service management phase, both the service requester and the service provider can obtain prior access to the target platform. This allows the service provider to issue management instructions on the target platform to publish the target software service on the blockchain network. In response to these instructions, the target platform can obtain the service description information of the target software service and generate and send blockchain transaction information to the blockchain network for publishing the target software service. The blockchain network can then respond to this blockchain transaction information to publish the target software service.

[0111] Subsequently, the service requester can issue a management instruction to the target platform to order the target software service on the blockchain network. In response to this instruction, the target platform can obtain the order information for the target software service and generate and send blockchain transaction information for ordering the target software service to the blockchain network. Based on this order information, the blockchain network can generate and send payment order information corresponding to the software service order to the target platform. Correspondingly, the target platform can then display the payment order information corresponding to the software service order to the service requester, facilitating the service requester to complete the payment.

[0112] Once the blockchain network recognizes that a software service order has been paid for, it can send the order to the service provider. The service provider can then review the order. If approved, the provider can store the software service key on the blockchain network through the target platform. Correspondingly, the blockchain network can receive and send this software service key to the service requester, enabling the requester to use it to obtain the target software service from the service provider.

[0113] Service requesters can also issue management instructions to the target platform to evaluate the target software service they have subscribed to. In response to these instructions, the target platform can obtain evaluation information for the target software service and generate and send blockchain transaction information to the blockchain network for evaluating the service. The blockchain network can then respond to this transaction information by storing the evaluation information as evidence.

[0114] Based on the same idea, embodiments of this specification also provide apparatus corresponding to the above methods. Figure 4 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a blockchain-based software service management device. (For example...) Figure 4 As shown, the device may include: The first acquisition module 402 is used for the target platform to acquire management instructions from platform users for the target software service; the target software service is a software service provided by a service provider to a service requester based on a blockchain network; the target platform is any software service management platform deployed on a blockchain node in the blockchain network, and the target platform has management authority over the software service provided by the blockchain network.

[0115] The first generation module 404 is used to generate first blockchain transaction information for managing the target software service in response to the management instruction.

[0116] The first sending module 406 is used to send the first blockchain transaction information to the blockchain network using the blockchain node used to deploy the target platform.

[0117] based on Figure 4 The embodiments of this specification also provide some specific implementations of the device, which will be described below.

[0118] Optional, Figure 4 The device may further include: The second acquisition module is used to acquire the node identity information of the blockchain node; the node identity information includes at least: node unique identifier information and node public key information.

[0119] The second generation module is used to generate second blockchain transaction information based on the node identity information; the second blockchain transaction information is used to request the blockchain node to grant management permissions for the software services provided by the blockchain network; the blockchain network is used to grant the blockchain node management permissions for the software services provided by the blockchain network after the node identity information is verified.

[0120] The second sending module is used to send the second blockchain transaction information to the blockchain network using the blockchain node.

[0121] Optional, Figure 4 The device may further include: The installation file download module is used to download the installation file of the target platform from the blockchain network using the blockchain node.

[0122] The runtime module is used to run the target platform based on the installation files of the target platform.

[0123] The binding relationship establishment module is used to establish a binding relationship between the target platform and the blockchain node based on the node identity information of the blockchain node; the target platform is used to obtain management permissions for the software services provided by the blockchain network based on the binding relationship.

[0124] The third generation module is used to generate third blockchain transaction information based on the binding relationship and using the node identity information of the blockchain node; the third blockchain transaction information is used to request the target platform to grant management permissions for the software services provided by the blockchain network; the blockchain network is used to respond to the third blockchain transaction information by sending a software service management permission token to the target platform.

[0125] The third sending module is used to send the third blockchain transaction information to the blockchain network using the blockchain node.

[0126] The relevant service information acquisition module is used to acquire relevant service information of the software services provided by the blockchain network.

[0127] The related service information display module is used to display related service information of the software service on the target platform.

[0128] Optional, Figure 4 The device may further include: The third acquisition module is used for the target platform to acquire the platform user's platform access permission acquisition request; the platform access permission acquisition request carries the user's user identity information.

[0129] The trusted verification module is used to respond to the platform's permission acquisition request, perform trusted verification on the user's identity information, and obtain the verification result.

[0130] The permission granting module is used to grant the platform user permission to use the target platform if the verification result indicates that the user's identity information for the platform user has been verified.

[0131] The management storage module is used to associate and store the user's public key information and unique identifier information of the platform user to the blockchain network if the verification result indicates that the user's identity information of the platform user has been verified.

[0132] The first generation module 404 is specifically used to: digitally sign the blockchain transaction information used to manage the target software service by using at least one of the node private key information corresponding to the node public key information and the user private key information corresponding to the user public key information, thereby obtaining the first blockchain transaction information.

[0133] Optionally, if the management instruction is used to instruct the publication of the target software service on the blockchain network, then the first generation module 404 may specifically be used for: In response to the management command, obtain the service description information of the target software service.

[0134] Based on the service description information, a first blockchain transaction is generated for publishing the target software service.

[0135] Optional, Figure 4 The device may further include: The software service order acquisition module is used by the target platform to acquire software service orders for the target software service that have been paid for by the target user from the blockchain network.

[0136] The review result receiving module is used to receive the review results provided by the platform users regarding the software service order.

[0137] The software service key storage module is used to store the software service key to the blockchain network if the audit result indicates that the audit has passed; the software service key is used to grant the target user the right to use the target software service.

[0138] Optionally, if the management instruction is used to instruct the platform user to modify the target software service published on the blockchain network, then the first generation module 404 may specifically be used for: In response to the management command, obtain the modification information of the service description information for the target software service.

[0139] Based on the modified information, a first blockchain transaction is generated for modifying the target software service.

[0140] Optional, Figure 4 The device may further include: The service modification module is used to obtain the modified service description information of the target software service from the blockchain network.

[0141] The modified information display module is used to display the modified service description information of the target software service on the target platform.

[0142] Optionally, if the management instruction is used to instruct the ordering of the target software service published on the blockchain network, then the first generation module 404 may specifically be used for: In response to the management command, obtain the subscription information for the target software service.

[0143] Based on the order information, a first blockchain transaction is generated for ordering the target software service; Optional, Figure 4 The device may further include: The fourth acquisition module is used to acquire payment order information corresponding to the first blockchain transaction information from the blockchain network; the payment order information is used to make payments for software service orders generated based on the order information.

[0144] The payment order information display module is used to display the payment order information on the target platform.

[0145] The fifth acquisition module is used to acquire the software service key corresponding to the software service order from the blockchain network; the software service key is used to grant the platform user the right to use the target software service; the software service key is stored in the blockchain network by the service provider of the target software service after confirming that the software service order payment has been completed and the software service order has been approved.

[0146] Optionally, if the management instruction is used to instruct the publication of evaluation information for the target software service on the blockchain network, then the first generation module 404 may specifically be used for: In response to the management command, obtain evaluation information for the target software service.

[0147] Based on the evaluation information, first blockchain transaction information is generated for evaluating the target software service.

[0148] Based on the same idea, this specification also provides devices corresponding to the above methods in its embodiments.

[0149] Figure 5 The embodiments provided in this specification correspond to Figure 2 A schematic diagram of the structure of a blockchain-based software service management device. (For example...) Figure 5 As shown, device 500 may include: At least one processor 510; and, Memory 530 communicatively connected to the at least one processor; wherein, The memory 530 stores instructions 520 that can be executed by the at least one processor 510, the instructions being executed by the at least one processor 510 to enable the at least one processor 510 to: The target platform obtains management instructions from platform users for the target software service; the target software service is a software service provided by the service provider to the service requester based on the blockchain network; the target platform is any software service management platform deployed on a blockchain node in the blockchain network, and the target platform has management authority over the software service provided on the blockchain network. In response to the management instruction, first blockchain transaction information for managing the target software service is generated; The first blockchain transaction information is sent to the blockchain network using the blockchain node used to deploy the target platform.

[0150] The various embodiments in this specification are described in a progressive manner. Similar or identical parts between embodiments can be referred to mutually. Each embodiment focuses on its differences from other embodiments. In particular, for... Figure 5 As the device shown is basically similar to the method embodiment, the description is relatively simple, and relevant parts can be found in the description of the method embodiment.

[0151] In the 1990s, improvements to a technology could be clearly distinguished as either hardware improvements (e.g., improvements to the circuit structure of diodes, transistors, switches, etc.) or software improvements (improvements to methodology). However, with technological advancements, many methodological improvements today can be considered direct improvements to hardware circuit structures. Designers almost always obtain the corresponding hardware circuit structure by programming the improved methodology into the hardware circuit. Therefore, it cannot be said that a methodological improvement cannot be implemented using hardware physical modules. For example, a Programmable Logic Device (PLD) (such as a Field Programmable Gate Array (FPGA)) is such an integrated circuit whose logic function is determined by the user programming the device. Designers can program a digital system themselves to "integrate" it onto a PLD, without needing chip manufacturers to design and manufacture dedicated integrated circuit chips. Furthermore, nowadays, instead of manually manufacturing integrated circuit chips, this programming is mostly implemented using "logic compiler" software. Similar to the software compiler used in program development, the original code before compilation must also be written in a specific programming language, called a Hardware Description Language (HDL). There are many HDLs, such as ABEL (Advanced Boolean Expression Language), AHDL (Altera Hardware Description Language), Confluence, CUPL (Cornell University Programming Language), HDCal, JHDL (Java Hardware Description Language), Lava, Lola, MyHDL, PALASM, and RHDL (Ruby Hardware Description Language). Currently, the most commonly used are VHDL (Very-High-Speed ​​Integrated Circuit Hardware Description Language) and Verilog. Those skilled in the art should also understand that by simply performing some logic programming on the method flow using one of these hardware description languages ​​and programming it into an integrated circuit, the hardware circuit implementing the logical method flow can be easily obtained.

[0152] The controller can be implemented in any suitable manner. For example, it can take the form of a microprocessor or processor and a computer-readable medium storing computer-readable program code (e.g., software or firmware) executable by the (micro)processor, logic gates, switches, application-specific integrated circuits (ASICs), programmable logic controllers, and embedded microcontrollers. Examples of controllers include, but are not limited to, the following microcontrollers: ARC 625D, Atmel AT91SAM, Microchip PIC18F26K20, and Silicon Labs C8051F320. A memory controller can also be implemented as part of the control logic of the memory. Those skilled in the art will also recognize that, in addition to implementing the controller in purely computer-readable program code form, the same functionality can be achieved by logically programming the method steps to make the controller take the form of logic gates, switches, application-specific integrated circuits, programmable logic controllers, and embedded microcontrollers. Therefore, such a controller can be considered a hardware component, and the means included therein for implementing various functions can also be considered as structures within the hardware component. Alternatively, the means for implementing various functions can be considered as both software modules implementing the method and structures within the hardware component.

[0153] The systems, devices, modules, or units described in the above embodiments can be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer. Specifically, a computer can be, for example, a personal computer, a laptop computer, a cellular phone, a camera phone, a smartphone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or any combination of these devices.

[0154] For ease of description, the above devices are described separately by function as various units. Of course, in implementing this application, the functions of each unit can be implemented in one or more software and / or hardware.

[0155] Those skilled in the art will understand that embodiments of the present invention can be provided as methods, systems, or computer program products. Therefore, the present invention can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, the present invention can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0156] This invention is described with reference to flowchart illustrations and / or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each block of the flowchart illustrations and / or block diagrams, and combinations of blocks in the flowchart illustrations and / or block diagrams, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, special-purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, generate instructions for implementing the flowchart illustrations and / or block diagrams. Figure 1 One or more processes and / or boxes Figure 1 A device that provides the functions specified in one or more boxes.

[0157] These computer program instructions may also be stored in a computer-readable storage medium that can direct a computer or other programmable data processing device to function in a particular manner, such that the instructions stored in the computer-readable storage medium produce an article of manufacture including instruction means, which are implemented in a process Figure 1 One or more processes and / or boxes Figure 1 The function specified in one or more boxes.

[0158] These computer program instructions may also be loaded onto a computer or other programmable data processing equipment to cause a series of operational steps to be performed on the computer or other programmable equipment to produce a computer-implemented process, thereby providing instructions that execute on the computer or other programmable equipment for implementing the process. Figure 1 One or more processes and / or boxes Figure 1 The steps of the function specified in one or more boxes.

[0159] In a typical configuration, a computing device includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0160] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.

[0161] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information using any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital character versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include transient computer-readable media, such as modulated data signals and carrier waves.

[0162] It should also be noted that the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0163] Those skilled in the art will understand that embodiments of this application can be provided as methods, systems, or computer program products. Therefore, this application can take the form of a completely hardware embodiment, a completely software embodiment, or an embodiment combining software and hardware aspects. Furthermore, this application can take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, CD-ROM, optical storage, etc.) containing computer-usable program code.

[0164] This application can be described in the general context of computer-executable instructions, such as program modules, that are executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc., that perform a specific task or implement a specific abstract data type. This application can also be practiced in distributed computing environments where tasks are performed by remote processing devices connected via a communication network. In distributed computing environments, program modules can reside in local and remote computer storage media, including storage devices.

[0165] The above description is merely an embodiment of this application and is not intended to limit the scope of this application. Various modifications and variations can be made to this application by those skilled in the art. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should be included within the scope of the claims of this application.

Claims

1. A blockchain-based software service management method, comprising: The target platform obtains management instructions from platform users regarding the target software service; The target software service is a software service provided by the service provider to the service demander based on a blockchain network. The target platform is any software service management platform deployed on a blockchain node in the blockchain network. The target platform has management permissions for the software services provided on the blockchain network based on the binding relationship. Before the target platform obtains management instructions from the platform user for the target software service, the binding relationship between the target platform and the blockchain node is established based on the node identity information of the blockchain node. In response to the management instruction, first blockchain transaction information for managing the target software service is generated; The first blockchain transaction information is sent to the blockchain network using the blockchain node used to deploy the target platform.

2. The method as described in claim 1, further comprising, before the target platform obtains management instructions from platform users for the target software service: Obtain the node identity information of the blockchain node; Based on the node identity information, generate second blockchain transaction information; The second blockchain transaction information is used to request the blockchain node to grant management permissions for the software services provided by the blockchain network; The blockchain network is used to grant the blockchain node management authority over the software services provided by the blockchain network after the node's identity information has been verified. Using the blockchain node, the second blockchain transaction information is sent to the blockchain network.

3. The method as described in claim 2, wherein the node identity information includes at least: The node's unique identifier and public key information.

4. The method as described in claim 3, further comprising, before the target platform obtains management instructions from platform users regarding the target software service: Run the target platform based on the installation files of the target platform.

5. The method of claim 4, wherein before running the target platform based on the installation file of the target platform, it further includes: The installation file for the target platform is downloaded from the blockchain network using the blockchain node.

6. The method as described in claim 4, further comprising, before the target platform obtains management instructions from platform users regarding the target software service: Based on the aforementioned binding relationship, third-party blockchain transaction information is generated using the node identity information of the blockchain nodes. The third blockchain transaction information is used to request the target platform to grant management permissions for the software services provided on the blockchain network. The blockchain network is used to send a software service management permission token to the target platform in response to the third blockchain transaction information; Using the blockchain node, the third blockchain transaction information is sent to the blockchain network.

7. The method of claim 6, further comprising, before the target platform obtains management instructions from platform users for the target software service: Obtain relevant service information about the software services provided by the blockchain network; Display relevant service information of the software service on the target platform.

8. The method of claim 6, further comprising, before the target platform obtains management instructions from platform users for the target software service: The target platform obtains the platform user's request for platform access permission; The platform access permission request carries the user's identity information of the platform user; In response to the request to obtain platform access rights, a trusted verification is performed on the user's identity information on the platform, and a verification result is obtained. If the verification result indicates that the user's identity information for the platform user has been verified, then the platform user is granted access to the target platform.

9. The method of claim 8, further comprising, before the target platform obtains management instructions from platform users for the target software service, the following steps: If the verification result indicates that the user identity information of the platform user has been verified, then the user's public key information and the user's unique identifier information are associated and stored in the blockchain network. The generation of the first blockchain transaction information for managing the target software service specifically includes: By using at least one of the node private key information corresponding to the node public key information and the user private key information corresponding to the user public key information, a digital signature is performed on the blockchain transaction information used to manage the target software service to obtain the first blockchain transaction information.

10. The method of any one of claims 1-9, wherein the management instruction is used to instruct the publication of the target software service at the blockchain network; The step of generating first blockchain transaction information for managing the target software service in response to the management instruction specifically includes: In response to the management command, obtain the service description information of the target software service; Based on the service description information, a first blockchain transaction is generated for publishing the target software service.

11. The method of claim 10, wherein after sending the first blockchain transaction information to the blockchain network, it further comprises: The target platform obtains software service orders for the target software service that have been paid for by the target user from the blockchain network; Receive the review results from the platform users regarding the software service orders; If the audit result indicates that the audit has passed, the software service key is stored in the blockchain network; The software service key is used to grant the target user access to the target software service.

12. The method of any one of claims 1-9, wherein the management instruction is used to instruct the platform user to modify the target software service published on the blockchain network; The step of generating first blockchain transaction information for managing the target software service in response to the management instruction specifically includes: In response to the management command, obtain modification information for the service description information of the target software service; Based on the modified information, a first blockchain transaction is generated for modifying the target software service.

13. The method of claim 12, further comprising, after sending the first blockchain transaction information to the blockchain network: Obtain the modified service description information of the target software service from the blockchain network; The modified service description information of the target software service is displayed on the target platform.

14. The method of any one of claims 1-9, wherein the management instruction is used to instruct the ordering of the target software service published on the blockchain network; The step of generating first blockchain transaction information for managing the target software service in response to the management instruction specifically includes: In response to the management command, obtain the subscription information for the target software service; Based on the order information, a first blockchain transaction is generated for ordering the target software service.

15. The method of claim 14, wherein after sending the first blockchain transaction information to the blockchain network, it further comprises: Obtain payment order information corresponding to the first blockchain transaction information from the blockchain network; The payment order information is used to make payments for software service orders generated based on the order information; The payment order information is displayed on the target platform.

16. The method of claim 15, wherein after displaying the payment order information on the target platform, it further comprises: Obtain the software service key corresponding to the software service order from the blockchain network; The software service key is used to grant platform users access to the target software service. The software service key is stored in the blockchain network by the service provider of the target software service after confirming that the software service order payment has been completed and the software service order has been approved.

17. The method of any one of claims 1-9, wherein the management instruction is used to instruct the publication of evaluation information for the target software service at the blockchain network; The step of generating first blockchain transaction information for managing the target software service in response to the management instruction specifically includes: In response to the management command, obtain evaluation information for the target software service; Based on the evaluation information, first blockchain transaction information is generated for evaluating the target software service.

18. A blockchain-based software service management device, comprising: The first acquisition module is used by the target platform to acquire management instructions from platform users for the target software service. The target software service is a software service provided by the service provider to the service demander based on a blockchain network. The target platform is any software service management platform deployed on a blockchain node in the blockchain network. The target platform has management permissions for the software services provided on the blockchain network based on the binding relationship. Before the target platform obtains management instructions from the platform user for the target software service, the binding relationship between the target platform and the blockchain node is established based on the node identity information of the blockchain node. The first generation module is configured to generate first blockchain transaction information for managing the target software service in response to the management instruction; The first sending module is used to send the first blockchain transaction information to the blockchain network using the blockchain node used to deploy the target platform.

19. The apparatus of claim 18, further comprising: The second acquisition module is used to acquire the node identity information of the blockchain node; The node identity information includes at least: unique node identifier information and node public key information; The second generation module is used to generate second blockchain transaction information based on the node identity information; the second blockchain transaction information is used to request the blockchain node to grant management authority over the software services provided by the blockchain network; the blockchain network is used to grant the blockchain node management authority over the software services provided by the blockchain network after the node identity information is verified. The second sending module is used to send the second blockchain transaction information to the blockchain network using the blockchain node.

20. The apparatus of claim 19, further comprising: The installation file download module is used to download the installation file of the target platform from the blockchain network using the blockchain node; The runtime module is used to run the target platform based on the installation files of the target platform; The binding relationship establishment module is used to establish a binding relationship between the target platform and the blockchain node based on the node identity information of the blockchain node; The target platform is used to obtain management permissions for software services provided by the blockchain network based on the binding relationship. The third generation module is used to generate third blockchain transaction information based on the binding relationship and using the node identity information of the blockchain node; the third blockchain transaction information is used to request the target platform to grant management permissions for the software services provided by the blockchain network. The blockchain network is used to send a software service management permission token to the target platform in response to the third blockchain transaction information; The third sending module is used to send the third blockchain transaction information to the blockchain network using the blockchain node.

21. The apparatus of claim 20, further comprising: The third acquisition module is used for the target platform to acquire the platform user's platform access permission acquisition request; The platform access permission request carries the user's identity information of the platform user; The trusted verification module is used to respond to the platform's permission acquisition request, perform trusted verification on the user identity information of the platform user, and obtain the verification result; The permission granting module is used to grant the platform user permission to use the target platform if the verification result indicates that the user's identity information for the platform user has been verified.

22. The apparatus of any one of claims 18-21, wherein if the management instruction is used to instruct the publication of the target software service at the blockchain network, the first generation module is specifically configured to: In response to the management command, obtain the service description information of the target software service; Based on the service description information, generate first blockchain transaction information for publishing the target software service; or... If the management instruction is used to instruct the modification of the target software service published by the platform user on the blockchain network, then the first generation module is specifically used for: In response to the management command, obtain modification information for the service description information of the target software service; Based on the modified information, a first blockchain transaction is generated for modifying the target software service.

23. The apparatus of any one of claims 18-21, wherein if the management instruction is used to instruct the ordering of the target software service published on the blockchain network, the first generation module is specifically configured to: In response to the management command, obtain the subscription information for the target software service; Based on the order information, a first blockchain transaction is generated for ordering the target software service; The device further includes: The fourth acquisition module is used to acquire payment order information corresponding to the first blockchain transaction information from the blockchain network; the payment order information is used to make payments for software service orders generated based on the order information; A payment order information display module is used to display the payment order information on the target platform. The fifth acquisition module is used to acquire the software service key corresponding to the software service order from the blockchain network; the software service key is used to grant the platform user the right to use the target software service; the software service key is stored in the blockchain network by the service provider of the target software service after confirming that the software service order payment has been completed and the software service order has been approved.

24. The apparatus of any one of claims 18-21, wherein if the management instruction is used to instruct the publication of evaluation information for the target software service at the blockchain network, the first generation module is specifically configured to: In response to the management command, obtain evaluation information for the target software service; Based on the evaluation information, first blockchain transaction information is generated for evaluating the target software service.

25. A blockchain-based software service management device, comprising: 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, the instructions being executed by the at least one processor to enable the at least one processor to: The target platform obtains management instructions from platform users for the target software service; the target software service is a software service provided by a service provider to a service requester based on a blockchain network; the target platform is any software service management platform deployed on a blockchain node in the blockchain network, and the target platform has management permissions for the software service provided on the blockchain network based on a binding relationship. Before the target platform obtains management instructions from platform users for the target software service, the binding relationship between the target platform and the blockchain node is established based on the node identity information of the blockchain node. In response to the management instruction, first blockchain transaction information for managing the target software service is generated; The first blockchain transaction information is sent to the blockchain network using the blockchain node used to deploy the target platform.

Images