Blockchain network-based service management method and device, equipment, and medium

Abstract

This application discloses a service management method, apparatus, device, and medium based on a blockchain network, applicable to various scenarios such as intelligent transportation, assisted driving, cloud technology, and artificial intelligence. The method includes receiving a registration request from a requester for a specified service system on the blockchain network, wherein the registration request carries reuse information indicating the reuse of a registered address; then detecting the requester's registration status for other service systems on the blockchain network and obtaining a detection result; if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network, obtaining the requester's registered address on the blockchain network; then using the obtained registered address as the requester's registration address for the specified service system on the blockchain network and returning the registered address to the requester. The technical solution of this application improves the rationality of service management for requester registration and saves resource space on the blockchain network.

Description

Technical Field

[0001] This application relates to the field of computer technology, and more specifically, to a service management method, a service management device, an electronic device, and a computer-readable medium based on a blockchain network. Background Technology

[0002] Blockchain technology is widely used in finance, credit reporting, banking and other fields. In related technologies, when a requester needs to register for any service system on the blockchain network, it sends a registration request to the blockchain network. After registration is completed on the blockchain network, the registration address is returned to the requester, thus completing the requester's registration for the service system on the blockchain network.

[0003] As the number of service systems that requesters need to register on the blockchain network increases, and / or the number of requesters increases, the resource space of the blockchain network required for registration also increases.

[0004] It is evident that how to reasonably manage the registration of requesters in order to save the resources of the blockchain network is an urgent problem to be solved. Summary of the Invention

[0005] To address the aforementioned technical problems, embodiments of this application provide a service management method, apparatus, device, and medium based on a blockchain network, thereby improving the rationality of service management for requester registration to at least a certain extent and saving resource space in the blockchain network.

[0006] According to one aspect of the embodiments of this application, this application provides a service management method based on a blockchain network. The method includes: receiving a registration request sent by a requester for a specified service system on the blockchain network; wherein the registration request carries reuse information for indicating the reuse of a registered address; detecting the registration status of the requester for other service systems on the blockchain network based on the reuse information, and obtaining a detection result; if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network, obtaining the registered address of the requester on the blockchain network; using the obtained registered address as the registration address of the requester for the specified service system on the blockchain network, and returning the registered address to the requester.

[0007] According to one aspect of the embodiments of this application, this application provides a service management device based on a blockchain network. The device includes: a receiving module configured to receive a registration request sent by a requester for a specified service system on the blockchain network; wherein the registration request carries reuse information for indicating the reuse of a registered address; a detection module configured to detect the registration status of the requester for other service systems on the blockchain network based on the reuse information, and obtain a detection result; an acquisition module configured to acquire the registered address of the requester on the blockchain network if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network; and a return module configured to use the acquired registered address as the registration address of the requester for the specified service system on the blockchain network, and return the registered address to the requester.

[0008] According to one aspect of the embodiments of this application, an electronic device is provided, including one or more processors; and a storage device for storing one or more programs, which, when executed by the one or more processors, enable the electronic device to implement the service management method based on a blockchain network as described above.

[0009] According to one aspect of the embodiments of this application, the embodiments of this application provide a computer-readable medium having a computer program stored thereon, which, when executed by a processor, implements the service management method based on a blockchain network as described above.

[0010] According to one aspect of the embodiments of this application, the embodiments of this application provide a computer program product, including computer instructions, which, when executed by a processor, implement the service management method based on a blockchain network as described above.

[0011] In the technical solution provided by the embodiments of this application, the registration status of the requester for other service systems on the blockchain network is detected, and when the registration of the requester for other service systems on the blockchain network is successfully detected, the registered address of the requester on the blockchain network is obtained, and the registered address is used as the current registration address of the requester for the specified service system on the blockchain network, thereby realizing the reuse of the registration address.

[0012] On the one hand, by reusing registration addresses, the phenomenon of allocating a registration address for each service system registered on the blockchain network can be avoided; this reduces the waste of resource space caused by allocating registration addresses in the blockchain network, saves resource space in the blockchain network, and makes the blockchain network perform better.

[0013] On the one hand, reusing registration addresses can reduce the number of registration addresses of the same requester on the blockchain network for the service system, thereby facilitating the management of registration addresses and improving the rationality of service management for requester registration.

[0014] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and do not limit this application. Attached Figure Description

[0015] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with this application and, together with the description, serve to explain the principles of this application. It is obvious that the drawings described below are merely some embodiments of this application, and those skilled in the art can obtain other drawings based on these drawings without any inventive effort.

[0016] Figure 1 This is a schematic diagram of the blockchain network structure;

[0017] Figure 2 This is a diagram illustrating the connection relationships between blocks in a blockchain.

[0018] Figure 3 This is a schematic diagram illustrating an exemplary implementation environment in which the technical solutions of the embodiments of this application can be applied.

[0019] Figure 4 This is a flowchart illustrating a service management method based on a blockchain network, as shown in an exemplary embodiment of this application;

[0020] Figure 5 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0021] Figure 6 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0022] Figure 7 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0023] Figure 8 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0024] Figure 9 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0025] Figure 10This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0026] Figure 11 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0027] Figure 12 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0028] Figure 13 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0029] Figure 14 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0030] Figure 15 This is a schematic diagram of a data table related to a service management method based on a blockchain network, as illustrated in an exemplary embodiment of this application.

[0031] Figure 16 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0032] Figure 17 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0033] Figure 18 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0034] Figure 19 This is a flowchart illustrating a service management method based on a blockchain network, as shown in another exemplary embodiment of this application;

[0035] Figure 20 This is an interface diagram illustrating the integration result of a service management method based on a blockchain network, as shown in an exemplary embodiment of this application;

[0036] Figure 21 This is a block diagram illustrating a service management device based on a blockchain network, as shown in an exemplary embodiment of this application.

[0037] Figure 22 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments. Detailed Implementation

[0038] Exemplary embodiments will now be described in detail, examples of which are illustrated in the accompanying drawings. When the following description relates to the drawings, unless otherwise indicated, the same numbers in different drawings denote the same or similar elements. / / The embodiments described in the following exemplary embodiments do not represent all embodiments identical to those described in this application. Rather, they are merely examples of apparatuses and methods identical to some aspects of this application as detailed in the appended claims.

[0039] The block diagrams shown in the accompanying drawings are merely functional entities and do not necessarily correspond to physically independent entities. That is, these functional entities can be implemented in software, in one or more hardware modules or integrated circuits, or in different network and / or processor devices and / or microcontroller devices.

[0040] The flowcharts shown in the accompanying drawings are merely illustrative and do not necessarily include all content and operations / steps, nor do they necessarily have to be performed in the described order. For example, some operations / steps can be broken down, while others can be combined or partially combined; therefore, the actual execution order may change depending on the specific circumstances.

[0041] It should be noted that "multiple" as mentioned in this application refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, or B alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.

[0042] Before introducing the technical solutions of the embodiments of this application, the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0043] Blockchain is a novel application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanisms, and cryptographic algorithms. Essentially, a blockchain is a decentralized database, a chain of data blocks (i.e., blocks) linked together using cryptographic methods. Each data block contains information about a batch of network transactions, used to verify the validity of the information (anti-counterfeiting) and to generate the next block. A blockchain can include an underlying platform, a platform product and service layer, and an application service layer.

[0044] As mentioned above, a blockchain is essentially a decentralized database, and it is maintained collaboratively by nodes within a blockchain network. For example, please refer to [link to relevant documentation]. Figure 1 ,exist Figure 1The blockchain network shown may include multiple nodes 101, which can be various clients forming the blockchain network. Each node 101, in its normal operation, receives input information and maintains shared data within the blockchain network based on this information. To ensure information exchange within the blockchain network, information connections can exist between each node, allowing for information transmission. For example, when any node in the blockchain network receives input information, other nodes in the network obtain this input information according to a consensus algorithm and store it as shared data, ensuring data consistency across all nodes in the blockchain network.

[0045] Each node in a blockchain network has a corresponding node identifier, and each node can store the node identifiers of other nodes. This allows for the broadcast of generated blocks to other nodes in the blockchain network based on their node identifiers. Each node can maintain a list of node identifiers, storing the node name and its corresponding node identifier in this list. The node identifier can be an IP (Internet Protocol) address or any other information that can be used to identify the node.

[0046] Each node in a blockchain network stores the same blockchain. A blockchain consists of multiple blocks; please refer to [link to relevant documentation]. Figure 2 A blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores input information features, version number, timestamp, and difficulty value, while the block body stores the input information. The next block after the genesis block is the parent block of the genesis block. The next block also includes a block header and a block body. The block header stores the input information features of the current block, the block header features of the parent block, version number, timestamp, and difficulty value, and so on. This ensures that the block data stored in each block is related to the block data stored in the parent block, guaranteeing the security of the input information in the blocks.

[0047] In a blockchain network, each node can be a server or a terminal device. A server can be an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and intelligent platforms. Terminal devices can be smartphones, tablets, laptops, desktop computers, smart speakers, smartwatches, etc., but are not limited to these. Nodes can be directly or indirectly connected via wired or wireless communication, and this application does not impose any restrictions on this.

[0048] The aforementioned cloud computing refers to the delivery and usage model of IT infrastructure, specifically the acquisition of required resources through the network in an on-demand and easily scalable manner. In a broader sense, cloud computing refers to the delivery and usage model of services, namely, the acquisition of required services through the network in an on-demand and easily scalable manner. These services can be IT and software-related, internet-related, or other services. Cloud computing is a product of the convergence and development of traditional computer and network technologies such as grid computing, distributed computing, parallel computing, utility computing, network storage technologies, virtualization, and load balancing. Driven by the development of the internet, real-time data streams, the diversification of connected devices, and the demands of search services, social networks, mobile commerce, and open collaboration, cloud computing has rapidly developed. Unlike previous parallel and distributed computing, the emergence of cloud computing will, conceptually, drive a revolutionary change in the entire internet model and enterprise management model.

[0049] In related technologies, when a requester needs to register any service system on a blockchain network, it sends a registration request to the blockchain network. After registration is completed on the blockchain network, a registration address is returned to the requester, thus completing the registration of the service system on the blockchain network. However, as the number of service systems a requester needs to register on the blockchain network increases, and / or the number of requesters increases, the resource space required for registration on the blockchain network also increases. For example, a requester may be able to register 1, 100, 1000, or even more service systems on the blockchain network, and the number of requesters may be 1000, 10000, or even more. This poses a significant challenge to the resource space required for registration on the blockchain network.

[0050] Based on the aforementioned blockchain technology and the problems existing in related technologies, embodiments of this application provide a service management scheme based on a blockchain network. Please refer to... Figure 3 , Figure 3 This is a schematic diagram of an exemplary implementation environment of this application. The implementation environment includes terminal device 301, server 302, server 303, and blockchain network 304. Terminal device 301, server 302, server 303, and blockchain network 304 can communicate with each other via wired or wireless network; wherein:

[0051] Terminal device 301 corresponds to the requesting party, which is the party that requests to register with the service system and can be any object.

[0052] The terminal device 301 can be any electronic device with an input interface, including but not limited to smartphones, tablets, laptops, computers, smart voice interaction devices, smart home appliances, vehicle terminals, aircraft, etc. The input interface includes but is not limited to touch screens, keyboards, physical buttons, audio pickup devices, etc.

[0053] Server 302 corresponds to the service system side. The service system is a system that provides business services (such as transaction services) to objects. It can be a service system corresponding to a merchant entity (also known as a business entity) based on a social credit code. This service system has a computer hardware or software operating environment, such as a platform that provides transaction services through computer programs; the service system includes, but is not limited to, merchant service systems (such as merchant platforms).

[0054] Server 303 corresponds to the management system side. The management system is a system that provides technical services (such as data interface services) to service systems and / or objects. It can be a management system corresponding to a merchant entity (also known as a business entity) based on a social credit code. This management system has a computer hardware or software operating environment, such as a platform that provides technical services through computer programs; the management system includes, but is not limited to, technical service systems (such as technical platforms), Software-as-a-Service (SaaS) systems (such as SaaS platforms), etc.

[0055] Servers 302 and 303 can be servers that provide various services. They can be independent physical servers, server clusters or distributed systems composed of multiple physical servers, or cloud servers that provide basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communication, middleware services, domain name services, security services, CDN, and big data and intelligent platforms. This section does not impose any restrictions on these services.

[0056] Blockchain network 304 can be the blockchain network described above, which will not be repeated here.

[0057] In one embodiment of this application, the service management method based on the blockchain network can be executed by the terminal device 301, where the terminal device 301 corresponds to the requester.

[0058] For example, terminal device 301 sends a registration request for a specified service system on the blockchain network to server 303, wherein the registration request carries reuse information for indicating the reuse of a registered address; then it receives the registration address returned by server 303.

[0059] In one embodiment of this application, the service management method based on the blockchain network can be executed by server 303, in which case server 303 corresponds to the management system.

[0060] For example, server 303 receives a registration request for a specified service system on the blockchain network sent by terminal device 301, wherein the registration request carries reuse information for indicating the reuse of a registered address; then, based on the reuse information, it detects the registration status of the requester for other service systems on the blockchain network and obtains the detection result; if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network, it obtains the registered address of the requester on the blockchain network; then, it uses the obtained registered address as the registration address of the requester for the specified service system on the blockchain network and returns the registered address to the requester.

[0061] In this way, by implementing the technical solution of the embodiments of this application, the reuse of registration addresses is realized. By reusing registration addresses, not only can resource space in the blockchain network be saved and the performance of the blockchain network be improved, but the management of registration addresses can also be facilitated, the rationality of service management for requesters can be improved, and it can be applied to a wider range of scenarios.

[0062] It should be noted that in the specific implementation of this application, data related to the object is involved. When the embodiments of this application are applied to specific products or technologies, permission or consent from the object is required, and the collection, use and processing of related data must comply with the relevant laws, regulations and standards of the relevant countries and regions.

[0063] The following details the various implementation details of the technical solutions in the embodiments of this application:

[0064] Please see Figure 4 , Figure 4 This is a flowchart illustrating a method in one embodiment of this application. This service management method based on a blockchain network can be provided by... Figure 3 The server shown in the image (e.g., the management system) performs the execution. Figure 4 As shown, the service management method based on the blockchain network includes at least S401 to S404, which are described in detail below:

[0065] S401, Receive a registration request sent by the requester for a specified service system on the blockchain network; wherein the registration request carries reuse information for indicating the reuse of a registered address.

[0066] In this embodiment of the application, when a requester needs to register a specified service system on the blockchain network, a registration request can be sent; correspondingly, the management system can receive the registration request sent by the requester.

[0067] In this application embodiment, the designated service system refers to any service system; for example, if the requester is currently registering for service system A on the blockchain network, then service system A is called the designated service system, or if the requester is currently registering for service system B on the blockchain network, then service system B is called the designated service system.

[0068] In this embodiment, the management system receives a registration request from the requester for a specified service system on the blockchain network. It can detect whether the registration request carries reuse information to indicate the reuse of a registered address. Then, based on whether the registration request carries reuse information, it can determine whether to trigger the execution of the detection of the requester's registration status for other service systems on the blockchain network and obtain the detection result.

[0069] S402, based on the registration status of other service systems on the blockchain network by the requester of the reuse information detection, the detection result is obtained.

[0070] In this embodiment, the management system determines whether to trigger the detection of the requester's registration status of other service systems on the blockchain network based on the reuse information carried in the registration request, and obtains the detection result, which may include the following two situations; wherein:

[0071] In the first scenario, if the registration request contains reuse information, it indicates that the requester has explicitly indicated the need to reuse the registered address. Therefore, the registration status of the requester for other service systems on the blockchain network can be detected, and the detection results can be obtained.

[0072] Scenario 2: If the registration request does not carry reuse information, it indicates that the requester indicates that there is no need to reuse the registered address. Therefore, there is no need to detect the requester's registration status for other service systems on the blockchain network and obtain the detection result.

[0073] In this embodiment, the detection of the requester's registration status for other service systems on the blockchain network is triggered only when the registration request carries reuse information indicating the reuse of a registered address, thereby enabling the reuse of the registered address, which meets the requester's needs and provides greater flexibility.

[0074] In this application embodiment, other service systems are service systems that are different from the designated service system. There can be one or more other service systems; for example, the designated service system is service system A, and other service systems can be service system B or service system BC.

[0075] In one embodiment of this application, the designated service system and other service systems can be service systems corresponding to different merchants; for example, the designated service system is the service system corresponding to merchant A, and the other service systems can be the service systems corresponding to merchant B.

[0076] In one embodiment of this application, the designated service system is the designated development channel corresponding to the designated merchant system, and other service systems can be at least one of the development channels of other merchant systems and other development channels of the designated merchant system; for example, the designated service system is development channel 1 corresponding to the service system of merchant A, and other service systems can be the service system of merchant B and / or the development channel 2 of the service system of merchant A.

[0077] In one optional embodiment, the development channel is a method of showcasing and / or programming the service system; for example, a mini-program is one development channel, while an application is another; or an application designed using the HTML5 programming language is one development channel, while an application designed using the JAVA programming language is another. In practical applications, this can be flexibly adjusted according to the specific application scenario.

[0078] In this embodiment of the application, the registration status of the requester for other service systems on the blockchain network refers to whether the requester has registered for other service systems on the blockchain network, and if so, whether the registration was successful or failed.

[0079] That is, in this embodiment of the application, when the management system receives a registration request from the requester for a specified service system on the blockchain network, it will detect the registration status of the requester for other service systems on the blockchain network, thereby obtaining the detection results corresponding to the registration status of the requester for other service systems on the blockchain network.

[0080] S403, if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network, then obtain the registered address of the requester on the blockchain network.

[0081] In this embodiment, the management system detects the registration status of the requester for other service systems on the blockchain network based on the reuse information, obtains the detection results, and then determines whether to register the requester for the specified service system on the blockchain network based on the detection results.

[0082] In this embodiment of the application, determining whether to register the requester for the specified service system in the blockchain network based on the detection results can include the following two situations; wherein:

[0083] Scenario 1: If the detection result indicates that the requester has successfully registered for other service systems on the blockchain network, then there is no need to register the requester for the specified service system on the blockchain network. It is only necessary to obtain the requester's registered address on the blockchain network, thereby reusing the registered address, reducing the process of registering a new address and saving blockchain network resources.

[0084] Scenario 2: If the detection result indicates that the requester has not successfully registered for other service systems on the blockchain network (registration failed or not registered), then the registered address of the requester on the blockchain network cannot be obtained. Therefore, it is necessary to register the requester for the specified service system on the blockchain network to generate a new registration address.

[0085] S404: The obtained registered address is used as the requester's registration address on the blockchain network for the specified service system, and the registered address is returned to the requester.

[0086] Regarding the above situation one, in this embodiment of the application, the management system obtains the registered address of the requester on the blockchain network, and then uses the obtained registered address as the registration address of the requester for the specified service system on the blockchain network, and returns the registered address to the requester; in this way, the requester can determine that the requester has successfully registered for the specified service system on the blockchain network based on the received registered address.

[0087] Regarding scenario two above, in this embodiment of the application, the system generates a new registration address and then returns the newly generated registration address to the requester; in this way, the requester can determine that the requester has successfully registered for the specified service system on the blockchain network based on the newly generated registration address received.

[0088] In this embodiment, by reusing registration addresses, on the one hand, the waste of resource space caused by allocating registration addresses in the blockchain network is reduced, thus saving resource space in the blockchain network and making the blockchain network perform better; on the other hand, the number of registration addresses of the same requester for the service system on the blockchain network is reduced, which facilitates the management of registration addresses, improves the rationality of service management for requester registration, and can be applied to a wider range of scenarios.

[0089] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 5 As shown, the service management method based on the blockchain network may include S501 to S502, S401, and S403 to S404.

[0090] Detailed introductions of S501 to S502 are as follows:

[0091] S501, based on reuse information, detect whether the designated service system is the first service system that the requester has registered on the blockchain network.

[0092] In this embodiment, the management system receives a registration request from a requester for a specified service system on the blockchain network. The registration request carries reuse information to indicate the reuse of a registered address. Based on the reuse information, the management system can detect whether the specified service system is the first service system that the requester has registered on the blockchain network. Then, based on whether the specified service system is the first service system that the requester has registered on the blockchain network, it can determine whether to trigger the execution of the detection of the requester's registration of other service systems on the blockchain network and obtain the detection result.

[0093] In this embodiment of the application, the service system in which the requester registers for the first time on the blockchain network refers to the service system in which the registration requester registers for the first time on the blockchain network.

[0094] For example, suppose the requester has registered a total of 5 service systems on the blockchain network up to this point, with the registration times listed in order as service system A, service system B, service system C, service system D, and service system E. Then, service system A is the service system that the requester registered for the first time on the blockchain network, while service systems B, C, D, and E are all service systems that the requester has registered for the first time on the blockchain network.

[0095] S502, if the specified service system is not the first service system that the requester has registered on the blockchain network, then the requester's registration status for other service systems on the blockchain network is detected, and the detection result is obtained.

[0096] In this embodiment, the management system determines whether to trigger the detection of the requester's registration of other service systems on the blockchain network based on whether the specified service system is the first service system the requester has registered on the blockchain network. The detection result can include the following two situations; wherein:

[0097] Scenario 1: If the specified service system is not the first service system that the requester has registered on the blockchain network, it indicates that the requester has registered for other service systems on the blockchain network. Therefore, there is relevant registration information of the requester for other service systems on the blockchain network. In this case, the registration status of the requester for other service systems on the blockchain network can be detected to obtain the detection results.

[0098] Scenario 2: If the specified service system is the first service system that the requester has registered on the blockchain network, it indicates that the requester has not registered other service systems on the blockchain network. Therefore, there is no relevant registration information of the requester for other service systems on the blockchain network. In this case, there is no need to detect the registration status of the requester for other service systems on the blockchain network and obtain the detection result.

[0099] It should be noted that, Figure 5 For detailed information on S401, S403 to S404 shown, please refer to [link / reference]. Figure 4 S401, S403 to S404 shown will not be described again here.

[0100] In this embodiment, the detection of the requester's registration status for other service systems on the blockchain network is triggered only when the specified service system is detected as not being the first service system the requester has registered on the blockchain network. This avoids the situation where registration information cannot be obtained because the specified service system is the first service system the requester has registered on the blockchain network, making the triggering of the detection of the requester's registration status for other service systems on the blockchain network more reasonable.

[0101] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 6 As shown, the service management method based on the blockchain network may include S601 to S603, S401, and S403 to S404.

[0102] In this embodiment, the registration request also carries a first identifier of the requester, which is assigned to the requester by the management system after the requester successfully registers on the management system; for example, after requester 1 successfully registers on the management system, the management system assigns a first identifier uin to requester 1. In this way, the management system can manage the requester based on the first identifier assigned to the requester.

[0103] Detailed introductions of S601 to S603 are as follows:

[0104] S601, based on the first identifier, detect whether the designated service system is the first service system that the requester has registered on the blockchain network.

[0105] In this embodiment, the management system receives a registration request for a specified service system on the blockchain network from a requester. The registration request carries the requester's first identifier. Then, the management system can detect whether the specified service system is the first service system that the requester has registered on the blockchain network for the first time based on the requester's first identifier.

[0106] In one embodiment of this application, the process of detecting whether the designated service system is the first service system that the requester has registered on the blockchain network based on the first identifier in S601 may include the following steps:

[0107] Based on the preset mapping relationship between the second identifier and the first identifier, it is determined whether there is a second identifier that matches the first identifier; wherein, the second identifier is assigned to the requester by the designated service system after the requester successfully registers with the designated service system on the blockchain network;

[0108] If no second identifier matches the first identifier, then the designated service system is determined to be the service system that the requester first registered on the blockchain network;

[0109] If a second identifier exists that matches the first identifier, then it is determined that the specified service system is not the service system that the requester first registered on the blockchain network.

[0110] In one optional embodiment, the second identifier is assigned to the requester by the designated service system after the requester successfully registers with the designated service system on the blockchain network; for example, after requester 1 successfully registers with the management system, the designated service system assigns a second identifier (uid) to requester 1. In this way, the designated service system can manage the requester based on the second identifier assigned to the requester.

[0111] In one of the optional embodiments, a mapping relationship between the second identifier and the first identifier is preset; for example, please refer to Table 1, which shows an example of the mapping relationship between the second identifier and the first identifier.

[0112]

[0113] Table 1

[0114] S602, obtain the requester's registration information on the blockchain network for other service systems based on the first identifier.

[0115] In this embodiment of the application, registration information refers to information related to registration, including but not limited to registration time, registration success information, registration failure information, and registration address.

[0116] S603, based on the registration information, detects the registration status of the requester for other service systems on the blockchain network and obtains the detection result.

[0117] In this embodiment, the management system detects the registration status of the requester for other service systems on the blockchain network and obtains the detection result. Specifically, it can obtain the registration information of the requester for other service systems on the blockchain network based on the first identifier, and detect the registration status of the requester for other service systems on the blockchain network based on the registration information to obtain the detection result.

[0118] For example, suppose that, based on the first identifier, the registration information of requester 1 for service system A on the blockchain network is obtained as successful, with the registration address address 1, and the registration information of requester 1 for service system B on the blockchain network is obtained as unsuccessful; then we can obtain a detection result indicating that requester 1's registration for service system A on the blockchain network was successful, and a detection result indicating that requester 1's registration for service system B on the blockchain network failed.

[0119] It is understandable that if there are multiple other service systems, the detection results corresponding to each service system are obtained (as in the example above). As long as the detection result corresponding to at least one service system indicates that the requesting party has successfully registered the service system on the blockchain network, the registered address of the requesting party on the blockchain is obtained.

[0120] For example, continuing from the previous example, we obtain a detection result indicating that requester 1 has successfully registered for service system A on the blockchain network, and a detection result indicating that requester 1 has failed to register for service system B on the blockchain network. It can be seen that if there is a detection result for one of the two service systems (i.e., service system A) indicating that requester has successfully registered for service system A on the blockchain network, then we can obtain the registration address of the requester on the blockchain.

[0121] It should be noted that, Figure 6 For detailed information on S401, S403 to S404 shown, please refer to [link / reference]. Figure 4 S401, S403 to S404 shown will not be described again here.

[0122] In this embodiment of the application, the first identifier assigned to the requester by the management system can quickly and easily detect whether the specified service system is the first service system that the requester has registered on the blockchain network, and obtain the registration information of the requester for other service systems on the blockchain network, so as to obtain the registration status of the requester for other service systems on the blockchain network.

[0123] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 7 As shown, the service management method based on the blockchain network may include S701 to S702 and S401 to S403.

[0124] As described in the foregoing embodiments, the management system can obtain the registered address of the requester on the blockchain network; where there is only one registered address, the registered address can be returned to the requester; where there are multiple registered addresses, please refer to the detailed description of this embodiment.

[0125] Detailed introductions of S701 to S702 are as follows:

[0126] S701, Select the target registered address from multiple registered addresses.

[0127] In this embodiment of the application, when there are multiple registered addresses, the management system can select the target registered address from the multiple registered addresses.

[0128] In one embodiment of this application, the process of selecting a target registered address from multiple registered addresses in step S701 may include the following steps:

[0129] Randomly select one registered address from multiple registered addresses as the target registered address.

[0130] That is, in an optional embodiment, the management system selects the target registered address from multiple registered addresses.

[0131] In one embodiment of this application, the process of selecting a target registered address from multiple registered addresses in step S701 may include the following steps:

[0132] Send multiple registered addresses to the requester so that the requester can select the target registered address from among the multiple registered addresses;

[0133] The target registered address returned by the receiving party.

[0134] That is, in the optional embodiment, the management system sends multiple registered addresses to the requester, and then the requester selects one of the multiple registered addresses as the target registered address and receives the target registered address returned by the requester.

[0135] In one optional embodiment, the management system receives the target registered address returned by the requester, and then marks the target registered address as a commonly used registered address. When faced with the task of selecting a target registered address from multiple registered addresses again, the marked commonly used registered address can be selected as the target registered address.

[0136] Understandably, if the requester selects one of multiple registered addresses as the target registered address, the management system can avoid returning the registered address to the requester in subsequent processes, thus saving management system resources.

[0137] S702 uses the target's registered address as the requester's registered address on the blockchain network for the specified service system.

[0138] In this embodiment, the management system selects the target registered address from multiple registered addresses, and then uses the target registered address as the registration address of the requester on the blockchain network for the specified service system.

[0139] It should be noted that, Figure 7 For detailed information on S401 to S403 shown, please refer to [link / reference]. Figure 4 S401 to S403 shown will not be described again here.

[0140] In this embodiment of the application, when there are multiple registered addresses of the requester on the blockchain network, the management system or the requester can select one of the multiple registered addresses as the target registered address, and use the target registered address as the registration address of the requester for the specified service system on the blockchain network, thereby quickly and easily determining the registration address of the requester for the specified service system on the blockchain network.

[0141] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 8 As shown, the service management method based on the blockchain network may also include S801 to S803 after S404.

[0142] Detailed introductions of S801 to S803 are as follows:

[0143] S801, receives a virtual resource transfer request sent by a specified service system for the requester.

[0144] In this embodiment of the application, when the designated service system has a need to transfer virtual resources to the requester, it can issue a virtual resource transfer request; correspondingly, the management system can receive the virtual resource transfer request sent by the designated service system to the requester.

[0145] In this application embodiment, virtual resources refer to resources that can be copied, which can be stored on various storage devices such as servers, computers, mobile phones, and cloud storage; they include, but are not limited to, paintings, audio, video, equipment in games, pets, coupons, etc.

[0146] In this embodiment of the application, a virtual resource transfer request is used to instruct the transfer of virtual resources contained in the registration address of a specified service system on the blockchain network to the registration address (i.e., the registered address) where the requesting policy registers the specified service system on the blockchain network.

[0147] S802, transfer virtual resources to a registered address based on a virtual resource transfer request.

[0148] In this embodiment of the application, the management system receives a virtual resource transfer request sent by a designated service system to the requester, and then can transfer virtual resources to the registered address according to the virtual resource transfer request.

[0149] S803 returns the transfer result of the virtual resources to the specified service system.

[0150] In this embodiment, the management system transfers virtual resources to a registered address based on a virtual resource transfer request, and then returns the transfer result of the virtual resources to the designated service system. The transfer result of the virtual resources includes a successful transfer result or a failed transfer result. In this way, the designated service system can determine the transfer status of the virtual resources (i.e., whether the transfer was successful or failed) based on the transfer result of the virtual resources.

[0151] It should be noted that, Figure 8 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0152] In this embodiment, a virtual resource transfer request is sent by a designated service system to the requester, transferring virtual resources to the registered address (i.e., the registered address) of the designated service system on the blockchain network. This satisfies the needs of the designated service system and is applicable to scenarios involving virtual resource transfer between the designated service system and the requester.

[0153] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 9 As shown, the service management method based on the blockchain network may include S901 to S902, S801, S803, and S401 to S404.

[0154] Detailed introductions of S901 to S902 are as follows:

[0155] S901, Obtain the verification result for the requester based on the virtual resource transfer request; wherein, the verification result is the result of verifying the requester within a specified time period, and the specified time period is before the current time.

[0156] In this embodiment, the management system receives a virtual resource transfer request sent by a designated service system. Then, it can obtain the verification result for the requester based on the virtual resource transfer request. After that, it can determine whether to transfer the virtual resource to the registered address based on the obtained verification result for the requester.

[0157] In this embodiment of the application, the verification result for the requester refers to the result of verifying the requester within a specified time period; wherein:

[0158] Verification includes, but is not limited to, real-name verification, qualification verification, and permission verification. In practical applications, these can be flexibly adjusted according to specific application scenarios.

[0159] A specified time period refers to a period of time preceding the current moment, or simply a historical time period. The duration of the specified time period can be arbitrary. For example, if the current moment is 9:00:00 AM on September 1, 2022, the specified time period could be 9:00:00 AM on August 27, 2022 to 8:59:59 AM on September 1, 2022, or 00:00:00 AM on September 1, 2022 to 8:59:59 AM on September 1, 2022, etc. In practical applications, it can be flexibly adjusted according to the specific application scenario.

[0160] S902, if the verification result indicates that the verification of the requester has passed, then the virtual resource is transferred to the registered address.

[0161] In this embodiment of the application, the management system determines whether to transfer virtual resources to the registered address based on the verification result obtained for the requester, which may include the following two situations; wherein:

[0162] Scenario 1: If the verification result indicates that the requester has passed verification, the virtual resource is transferred to the registered address. Optionally, a virtual resource transfer success result is generated after the virtual resource transfer is successful.

[0163] Scenario 2: If the verification result indicates that the verification of the requester failed, no action is taken, i.e., the virtual resource is not transferred to the registered address. Optionally, a virtual resource transfer failure result can be generated based on the verification failure information.

[0164] It should be noted that, Figure 9 For detailed information on S801 and S803 shown, please refer to [link / reference]. Figure 8 S801 and S803 are shown. Figure 9 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0165] In this embodiment, virtual resources are transferred to the registered address only when the verification result obtained for the requester indicates that the verification of the requester has passed. This avoids the possibility of the requester being attacked and tampered with, ensuring the security and accuracy of virtual resource transfer. Furthermore, the verification result obtained is for the requester within a historical time period. Therefore, only this verification result needs to be obtained, eliminating the need for repeated verification processes, saving resources and increasing verification efficiency, thereby improving the efficiency of virtual resource transfer.

[0166] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 10As shown, the service management method based on the blockchain network may include S1001 to S1003, S902, S801, S803, and S401 to S404.

[0167] In this embodiment, the virtual resource transfer request carries a second identifier of the requester. As described in the previous embodiment, the second identifier is assigned to the requester by the designated service system after the requester has successfully registered with the designated service system on the blockchain network.

[0168] Detailed introductions of S1001 to S1003 are as follows:

[0169] S1001, Based on the preset mapping relationship between the second identifier and the first identifier, determine the first identifier that matches the second identifier; wherein, the first identifier is assigned to the requester by the management system after the requester successfully registers on the management system.

[0170] In this embodiment of the application, the management system can determine the first identifier that matches the second identifier based on the preset mapping relationship between the second identifier and the first identifier.

[0171] The mapping relationship between the first identifier and the preset second identifier and the first identifier in this embodiment can be found in the foregoing embodiments, and will not be repeated here.

[0172] S1002, obtain other identifiers associated with the first identifier, and use the service system corresponding to the other identifiers as the target service system; wherein, the other identifiers are assigned to the requester by the other service system.

[0173] In this embodiment of the application, the management system determines a first identifier that matches the second identifier, and then can obtain other identifiers associated with the first identifier, and use the service systems corresponding to the other identifiers as the target service systems.

[0174] In this application embodiment, "other identifiers" refers to a second identifier other than the second identifier of the requester carried in the virtual resource transfer request.

[0175] For example, if the second identifier of the requester carried in the virtual resource transfer request is uin=10, then according to Table 1 in the aforementioned embodiment, the first identifier is determined to be uid=1, and correspondingly, the other identifiers are obtained as uin=20.

[0176] In this embodiment of the application, the service system corresponding to other identifiers is referred to as the target service system.

[0177] For example, following the previous example, if other identifiers are uin=20, then according to Table 1 in the previous embodiment, service system B is determined to be the target service system.

[0178] S1003, Obtain the verification result initiated by the target service system for the requester's verification.

[0179] In this embodiment, the management system obtains other identifiers associated with the first identifier and uses the service systems corresponding to these other identifiers as the target service systems. Then, it can obtain the verification results initiated by the target service systems for the verification of the requester.

[0180] For example, continuing from the previous example, we can obtain the verification result initiated by service system B for the verification of requester 1.

[0181] It should be noted that, Figure 10 For a detailed description of S902 shown, please refer to [link / reference]. Figure 9 S902 as shown, Figure 10 For detailed information on S801 and S803 shown, please refer to [link / reference]. Figure 8 S801 and S803 are shown. Figure 10 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0182] In this embodiment of the application, the second identifier assigned to the requester by the designated service system can quickly and easily obtain the verification result of the requester within a historical time period, providing strong support for determining whether to transfer virtual resources to the registered address based on the verification result.

[0183] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 11 As shown, the service management method based on the blockchain network may include S1101 to S1102, S901, S801, S803, and S401 to S404.

[0184] As described in the foregoing embodiments, the management system can obtain the verification result for the requester based on the virtual resource transfer request; where there is only one verification result, it can determine whether to transfer the virtual resource to the registered address based on the verification result; where there are multiple verification results, please refer to the detailed description of this embodiment.

[0185] In this embodiment, the verification result is the verification result initiated by the target service system against the requester. The target service system is described in the foregoing embodiments and will not be repeated here.

[0186] Detailed introductions of S1101 to S1102 are as follows:

[0187] S1101 detects the security level of multiple target service systems respectively.

[0188] It is understood that the security levels of different target service systems may be the same or different; for example, some target service systems have a high security level, some have a moderate security level, and some have a low security level. Therefore, in this embodiment, the management system obtains the verification results of the requester verification initiated by multiple target service systems, and then can detect the security level of multiple target service systems respectively. Then, based on the detected security level of the target service system, it can determine whether to transfer virtual resources to the registered address.

[0189] S1102, if at least one target service system has a security level greater than a preset security level threshold, and the verification result initiated by at least one target service system for the requester indicates that the verification of the requester has passed, then the virtual resource is transferred to the registered address.

[0190] In this embodiment of the application, the management system determines whether to transfer virtual resources to a registered address based on the detected security level of the target service system, which may include the following two situations; wherein:

[0191] In scenario one, if at least one target service system has a security level greater than a preset security level threshold, and the verification result initiated by at least one target service system for the requester indicates that the verification of the requester has passed, then the virtual resources are transferred to the registered address.

[0192] In scenario two, if there is no target service system whose security level is greater than the preset security level threshold, and / or no target service system whose verification result for the requester indicates that the verification of the requester has passed, then no action will be taken, i.e., the virtual resources will not be transferred to the registered address.

[0193] It should be noted that, Figure 11 For a detailed description of S901 shown, please refer to [link / reference]. Figure 9 The S901 shown is... Figure 11 For detailed information on S801 and S803 shown, please refer to [link / reference]. Figure 8 S801 and S803 are shown. Figure 11 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0194] In this embodiment of the application, when there are multiple verification results for the requester within the historical time period, the determination of whether to transfer virtual resources to the registered address is quickly and easily realized by detecting whether there is a target service system whose security level meets the preset security level threshold and whether the verification result indicates that the verification result for the requester has passed.

[0195] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 12 As shown, the service management method based on the blockchain network may include S1201 to S1202, S901, S801, S803, and S401 to S404.

[0196] In this embodiment, the virtual resource transfer request carries the identification information of the virtual resource, such as tokenid.

[0197] Detailed introductions of S1201 to S1202 are as follows:

[0198] S1201: Obtain the virtual resource that matches the identification information of the virtual resource from the registered address of the designated service system on the blockchain network.

[0199] In this embodiment, the management system obtains the virtual resources that match the identification information of the virtual resources from the registration address of the designated service system on the blockchain network.

[0200] S1202, transfer the acquired virtual resources to the registered address.

[0201] In this embodiment, the management system obtains the virtual resources that match the identification information of the virtual resources from the registration address of the designated service system on the blockchain network. Then, the obtained virtual resources can be transferred to the registered address, thereby realizing the transfer of virtual resources.

[0202] It should be noted that, Figure 12 For a detailed description of S901 shown, please refer to [link / reference]. Figure 9 The S901 shown is... Figure 12 For detailed information on S801 and S803 shown, please refer to [link / reference]. Figure 8 S801 and S803 are shown. Figure 12 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0203] In this embodiment of the application, the identification information of virtual resources can be used to quickly and accurately locate the virtual resources to be transferred in the registered address of the specified service system on the blockchain network, and realize the transfer of virtual resources.

[0204] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 13 As shown, the service management method based on the blockchain network may also include S1301 to S1304 after S404.

[0205] Detailed introductions of S1301 to S1304 are as follows:

[0206] S1301, Receive the virtual resource query request sent by the requester.

[0207] In this embodiment of the application, when a requester has a need to query all the virtual resources it holds on the blockchain network, it can issue a virtual resource query request; correspondingly, the management system can receive the virtual resource query request sent by the requester.

[0208] In this embodiment of the application, the virtual resource query request is used to instruct the query requester to query the virtual resources contained in the registered addresses of various service systems on the blockchain network.

[0209] S1302, Obtain the registered addresses of the requester for each service system on the blockchain network based on the virtual resource query request.

[0210] In this embodiment of the application, the management system receives a virtual resource query request sent by the requester, and then obtains the registered addresses of the requester for each service system on the blockchain network based on the virtual resource query request.

[0211] In one embodiment of this application, the virtual resource query request carries a first identifier of the requester. As described in the previous embodiments, the first identifier is assigned to the requester by the management system after the requester successfully registers on the management system. S1302, obtaining the registration address corresponding to the requester's successful registration on the blockchain network for each service system based on the virtual resource query request, may include the following steps:

[0212] The first identifier is used to obtain the registered addresses of the requester on the blockchain network for each service system.

[0213] In one of the optional embodiments, a mapping relationship between a first identifier and a registered address is pre-defined; for example, please refer to Table 2, which shows an example of a mapping relationship between a first identifier and a registered address.

[0214]

[0215] Table 2

[0216] For example, if the first identifier of the requester carried in the virtual resource query request is uid=1, then according to Table 2, address1 and address2 can be obtained.

[0217] S1303 integrates the virtual resources contained in the registered addresses of various service systems on the blockchain network for the requester, and obtains the integration result of virtual resources.

[0218] In this embodiment, the management system obtains the registered addresses of the requester for each service system on the blockchain network based on the virtual resource query request. Then, it can integrate the virtual resources contained in the registered addresses of the requester for each service system on the blockchain network to obtain the integration result of virtual resources.

[0219] For example, continuing from the previous example, let the virtual resource contained in address1 be token1 and the virtual resource contained in address2 be token2. After integrating the virtual resource token1 contained in address1 and the virtual resource token2 contained in address2, the integrated result is token1 + token2.

[0220] S1304, returns the integration result of the virtual resources to the requester.

[0221] In this embodiment, the management system obtains the integration result of the virtual resources and then returns the integration result to the requester; thus, the requester can determine the status of the virtual resources it holds based on the integration result.

[0222] It should be noted that, Figure 13 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0223] In this embodiment, the virtual resource query request sent by the requester is used to provide feedback on the integration results of the virtual resources, thereby meeting the requester's needs. This is applicable to scenarios where the requester queries the virtual resources they hold.

[0224] In one embodiment of this application, another service management method based on a blockchain network is provided, which can be executed by a server 303 (such as a management system). Figure 14As shown, the service management method based on the blockchain network may also include S1401 to S1405 after S404.

[0225] Detailed introductions of S1401 to S1405 are as follows:

[0226] S1401, Receive the virtual resource migration request sent by the requester.

[0227] In this embodiment of the application, when the requesting party has a need to migrate virtual resources, it can issue a virtual resource migration request; correspondingly, the management system can receive the virtual resource migration request sent by the requesting party.

[0228] In this embodiment of the application, the virtual resource migration request is used to instruct the migration operation of virtual resources.

[0229] S1402, Obtain the registered addresses of the requester for each service system on the blockchain network based on the virtual resource migration request.

[0230] In this embodiment, the management system receives a virtual resource migration request from the requester, and then obtains the registered addresses of the requester for each service system on the blockchain network based on the virtual resource migration request.

[0231] In one embodiment of this application, the virtual resource migration request carries a first identifier of the requester. As described in the previous embodiments, the first identifier is assigned to the requester by the management system after the requester successfully registers on the management system. S1402, obtaining the requester's registered addresses for each service system on the blockchain network based on the virtual resource migration request, may include the following steps:

[0232] The first identifier is used to obtain the registered addresses of the requester on the blockchain network for each service system.

[0233] In one of the optional embodiments, the registered addresses of the requester for each service system on the blockchain network are obtained based on the first identifier. Please refer to the foregoing embodiments for details, which will not be repeated here.

[0234] S1403: Select the first registered address to be migrated and the second registered address to which to be migrated from the registered addresses of each service system on the blockchain network.

[0235] In this embodiment, the management system obtains the registered addresses of the requester for each service system on the blockchain network based on the virtual resource migration request. Then, it can select the first registered address to be migrated and the second registered address to be migrated to from the registered addresses of the requester for each service system on the blockchain network; wherein the first registered address and the second registered address are different registered addresses.

[0236] In one embodiment of this application, the process of selecting a first registration address to be migrated and a second registration address to which the requester needs to migrate from the registered addresses of each service system on the blockchain network in step S1403 may include the following steps:

[0237] From the registered addresses of each service system on the blockchain network, the requester randomly selects one registered address as the second registered address to be migrated to, and the other registered addresses are used as the first registered addresses to be migrated to.

[0238] That is, in an optional embodiment, the management system selects the first registered address to be migrated and the second registered address to which the requester needs to migrate from the registered addresses of each service system on the blockchain network.

[0239] In one embodiment of this application, the process of selecting a first registration address to be migrated and a second registration address to which the requester needs to migrate from the registered addresses of each service system on the blockchain network in step S1403 may include the following steps:

[0240] Send multiple registered addresses to the requester so that the requester can select a second registered address to which they wish to migrate;

[0241] The second registration address returned by the requester;

[0242] The other registered addresses on the blockchain network for each service system, excluding the second registered address, will be designated as the first registered address to be migrated.

[0243] That is, in an optional embodiment, the management system sends multiple registered addresses to the requester, and the requester selects one of the multiple registered addresses as the second registered address to be migrated to, and receives the second registered address returned by the requester. Correspondingly, the other registered addresses among the multiple registered addresses other than the second registered address are used as the first registered address to be migrated.

[0244] S1404, migrate the virtual resources contained in the first registration address to the second registration address.

[0245] In this embodiment, the management system selects a first registration address to be migrated and a second registration address to be migrated to from the registered addresses of each service system on the blockchain network. Then, the virtual resources contained in the first registration address can be migrated to the second registration address.

[0246] In one embodiment of this application, after migrating the virtual resources contained in the first registration address to the second registration address in step S1404, the following steps may also be included:

[0247] The first registered address is deregistered in the blockchain network, and the deregistration result of the first registered address is obtained;

[0248] Return the cancellation result of the first registered address to the requester.

[0249] That is, in the optional embodiment, the management system can cancel the first registered address in the blockchain network, obtain the cancellation result of the first registered address, and return the cancellation result of the first registered address to the requester, wherein the cancellation result of the first registered address includes a cancellation success result or a cancellation failure result; in this way, the requester can determine the cancellation status of the first registered address (i.e., cancellation success or cancellation failure) based on the cancellation result of the first registered address.

[0250] S1405 returns the migration result of the virtual resource to the requester.

[0251] In this embodiment, the management system migrates the virtual resources contained in the first registration address to the second registration address, and then returns the migration result of the virtual resources to the requester. The migration result of the virtual resources includes a successful migration result or a failed migration result. In this way, the requester can determine the migration status of the virtual resources (i.e., whether the migration was successful or failed) based on the migration result of the virtual resources.

[0252] It should be noted that, Figure 14 For detailed information on S401 to S404 shown, please refer to [link / reference]. Figure 4 S401 to S404 shown will not be described again here.

[0253] In this embodiment, the virtual resource migration request sent by the requester is fed back to the requester, thereby satisfying the requester's needs. This is applicable to scenarios where the requester transfers virtual resources contained in one or more registered addresses on the blockchain to other registered addresses on the blockchain.

[0254] The following is a detailed description of a specific scenario of an embodiment of this application:

[0255] In this embodiment, the management system is an open platform that provides technical services such as data interface API (Application Program Interface), the service system is a merchant platform that provides business services such as transaction services, the requester is the object, and the virtual resource is digital collections.

[0256] First, the relevant data tables involved in this application are introduced.

[0257] Please see Figure 15 This is a schematic diagram of the relevant data tables; where:

[0258] `app_info` is the merchant information table. The `appid` field represents the merchant's unique identifier on the open platform, and it serves as a foreign key, linking to the `user_uin` object's channel table. The `app_name` field represents the merchant's name, and the `state` field represents the merchant's status (frozen or active). Here, `string` indicates that the field is of string type, and `int` indicates that the field is of integer type.

[0259] The user_uin table is the object channel table. The uin field represents the object's unique identifier on the merchant platform; the appid field represents the merchant's unique identifier on the open platform; and the uid field represents the object's unique identifier on the open platform. As a foreign key, it is linked to the user_uid object information table. For example, the registration address (also known as the blockchain address, hereinafter referred to as the blockchain address) can be obtained from the user_uid object information table through the uid and displayed to the object.

[0260] The user_uid field is the object information table. The uid field represents the unique identifier of the object on the open platform. It can use an auto-incrementing primary key, starting from 1 and incrementing. The address field represents the blockchain address. The same object can register on the blockchain network for multiple merchant platforms, thus having multiple blockchain addresses.

[0261] `user_mobile` is a contact information index table. The `mobile` field represents contact information. The `mainuid` field is associated with `user_uid`, representing the blockchain address that the object registers for the first time on the blockchain network for a merchant platform. When registering for a merchant platform on the blockchain network, the object can choose to reuse the blockchain address, or it can generate a new blockchain address. When a new blockchain address is generated, a new record will be inserted into the `user_uid` object information table, and the `uid` will be written into the `otheruids` field. The `name` field represents the name, and the `auth_state` field indicates whether real-name authentication is required.

[0262] user_nf is the digital collectibles table. The uid field represents the unique identifier of the object on the open platform, the uin field represents the unique identifier of the object on the merchant platform, and the tokenid field is the identifier of the digital collectible (which can be transferred from the merchant to the object or the object to the merchant). Detailed information about the digital collectible can be queried on the open platform or blockchain network through the tokenid.

[0263] As is understandable, in the table above, string indicates that the field is of string type, int indicates that the field is of integer type, and boolean indicates that the field is of boolean type.

[0264] Secondly, based on the aforementioned data tables, this paper describes the process of merchant platforms registering on the blockchain network.

[0265] Please see Figure 16 The service management methods based on blockchain networks include at least S1601 to S1603, which are detailed below:

[0266] S1601, the object sends a registration request for the merchant platform on the blockchain network to the open platform through the merchant platform.

[0267] S1602, The open platform detects whether the registration request carries reuse information;

[0268] If reused information is detected in the registration request, the corresponding database is queried for the blockchain address of the object on the blockchain network for other merchant platforms, as well as the real-name information; the database only retrieves the blockchain address of the object on the blockchain network for other merchant platforms and returns the blockchain address.

[0269] If no reuse information is detected in the registration request, the object is registered on the blockchain network for the merchant platform, a newly generated blockchain address is obtained, and the newly generated blockchain address is returned.

[0270] S1603, the open platform returns the blockchain address to the object; the returned blockchain address can be the obtained blockchain address or a newly generated blockchain address.

[0271] For example, if object 1 registers with merchant platform A on the blockchain network, and the open platform is called, it first queries the user_mobile contact information index table to determine if object 1 has already registered. If it hasn't, then:

[0272] First, write the user_uid object information table, where uid can be controlled to increment using MySQL or Redis; assuming object 1 is the first object of the open platform, then uid = 1, and register merchant platform A on the blockchain network, generating a blockchain address 1Axxx, and inserting the blockchain address 1Axxx into the address in the user_uid object information table.

[0273] Next, the user_mobile contact information index table is written, with mobile = 158...838, auth_state = weak real name, mainuid = 1 to associate with the uid in the user_uid table, and other real name information is empty; in the user_uin object channel table, uin = 1@merchant A, and appid is merchant A. Then, the uin can be returned to object 1, and object 1 can be guided to complete real name verification to write other real name information.

[0274] It should be noted that, Figure 16 The illustrated embodiment can be implemented using a registration interface in an open platform, which is obtained by relevant developers through program coding.

[0275] Furthermore, based on the aforementioned data tables, the process of registering a merchant platform on the blockchain network is also described.

[0276] Please see Figure 17 The service management methods based on blockchain networks include at least S1701 to S1703, which are detailed below:

[0277] S1701, the object sends a registration request for the merchant platform on the blockchain network to the open platform through the merchant platform.

[0278] S1702, Open platform checks whether the registration request carries reuse information;

[0279] If reused information is detected in the registration request, the corresponding database is queried for the blockchain address and real-name information of the target on other merchant platforms on the blockchain network; where the database query finds the blockchain address and real-name information of the target on other merchant platforms on the blockchain network, the blockchain address and real-name information are returned.

[0280] If no reuse information is detected in the registration request, the object is registered on the blockchain network for the merchant platform, a newly generated blockchain address is obtained, and the newly generated blockchain address is returned.

[0281] S1703, the open platform returns the blockchain address to the object; the returned blockchain address can be the obtained blockchain address or a newly generated blockchain address.

[0282] It should be noted that, Figure 17 The illustrated embodiments and Figure 16 The difference between the illustrated embodiments lies in whether or not real-name information is retrieved from the database (wherein) Figure 16 No real-name information was found in the database. Figure 17 (The information is retrieved from the database using real-name information.) Figure 17For detailed information on S1701 to S1703 shown, please refer to [link / reference]. Figure 16 S1601 to S1603 shown will not be described again here.

[0283] It should be noted that, Figure 17 The illustrated embodiment can be implemented using the registration interface and the real-name interface in the open platform, which are obtained by relevant developers through program coding.

[0284] This application embodiment implements the reuse of registration addresses. By reusing registration addresses, not only can resource space in the blockchain network be saved and the performance of the blockchain network be improved, but the management of registration addresses can also be facilitated, thereby improving the rationality of service management for object registration.

[0285] Furthermore, the transfer process of digital collections will be described based on the aforementioned relevant data tables.

[0286] Please see Figure 18 The service management method based on blockchain networks includes at least S1801 to S1804, which are detailed below:

[0287] S1801, the object sends a digital collection transfer request to the open platform through the merchant platform, wherein the digital collection transfer request carries the identification information of the digital collection and the object's second identifier.

[0288] S1802, the open platform queries the corresponding database for the blockchain address of the object on the blockchain network for the merchant platform based on the object's second identifier; if the database query finds the blockchain address of the object on the blockchain network for the merchant platform, it returns the blockchain address.

[0289] S1803, the open platform transfers the digital collectible that matches the identification information of the digital collectible in the blockchain address to the blockchain address of the merchant platform on the blockchain network.

[0290] Optionally, the open platform obtains the verification result for the object based on the transfer request of the virtual resource; wherein, the verification result is the result of verifying the object within a specified time period, and the specified time period is before the current time; if the verification result indicates that the verification of the object is successful, the digital collectible that matches the identification information of the digital collectible in the blockchain address is transferred to the blockchain address of the merchant platform on the blockchain network.

[0291] S1804, the open platform returns the transfer results of the digital collection to the object.

[0292] Understandable Figure 18The illustrated embodiment is a digital collection transfer request initiated by an object. In other embodiments, it could also be a digital collection transfer request initiated by a merchant platform. In practical applications, it can be flexibly adjusted according to the specific application scenario.

[0293] It should be noted that, Figure 18 The illustrated embodiment can be implemented using a digital collection transfer interface in an open platform, which is obtained by relevant developers through program coding.

[0294] In this embodiment, the verification of the target object is achieved by obtaining the verification results of the target object within the historical time period. This process avoids repeated verification, saves the resources required for verification, improves verification efficiency, and enhances the efficiency of virtual resource transfer.

[0295] Finally, based on the aforementioned data tables, the process of querying digital collections is described.

[0296] Please see Figure 19 The service management methods based on blockchain networks include at least S1901 to S1903, which are detailed below:

[0297] S1901, the object sends a query request for digital collections to the open platform.

[0298] S1902, the open platform queries the corresponding database for the blockchain address of each merchant platform on the blockchain network based on the digital collection query request.

[0299] S1903, the open platform integrates the digital collectibles contained in the blockchain addresses of various merchant platforms on the blockchain network to obtain the integrated result of the digital collectibles.

[0300] S1904, The open platform returns the integrated results of the digital collection to the object.

[0301] It should be noted that, Figure 19 The illustrated embodiment can be implemented using the digital collection and query interface in the open platform, which is obtained by relevant developers through program coding.

[0302] Please see Figure 20 This is an example of an interface diagram showing the integrated result of a digital collection; in other examples, only all virtual resources may be displayed.

[0303] In this embodiment, an object can query all the virtual resources it holds at once, avoiding the cumbersome operation of querying each virtual resource held by an object on each merchant platform. This provides convenience for objects to query all the virtual resources they hold, saves query time, improves query efficiency, and results in a higher user experience satisfaction.

[0304] Figure 21 This is a block diagram illustrating a service management device based on a blockchain network, as shown in one embodiment of this application. Figure 21 As shown, the service management device based on the blockchain network includes:

[0305] The receiving module 2101 is configured to receive a registration request sent by the requester for a specified service system on the blockchain network;

[0306] The detection module 2102 is configured to detect the registration status of other service systems on the blockchain network by the requester based on the reuse information, and obtain the detection result;

[0307] The module 2103 is configured to obtain the registered address of the requester on the blockchain network if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network.

[0308] Return module 2104 is configured to use the obtained registered address as the requester's registration address on the blockchain network for the specified service system, and return the registered address to the requester.

[0309] In one embodiment of this application, the detection module 2102 is specifically configured as follows:

[0310] The system checks whether the registration request contains reuse information; the reuse information is used to indicate the reuse of a registered address.

[0311] If the registration request contains reuse information, the detection results will be obtained by checking the registration status of the requester for other service systems on the blockchain network.

[0312] In one embodiment of this application, the detection module 2102 is specifically configured as follows:

[0313] The reuse information is used to determine whether the designated service system is the first service system that the requester has registered on the blockchain network.

[0314] If the specified service system is not the first service system that the requester has registered on the blockchain network, then the requester's registration status for other service systems on the blockchain network will be checked to obtain the detection result.

[0315] In one embodiment of this application, the registration request also carries a first identifier of the requester, which is assigned to the requester by the management system after the requester successfully registers on the management system; the detection module 2102 is further configured as follows:

[0316] The first identifier is used to determine whether the designated service system is the first service system that the requester has registered on the blockchain network.

[0317] Obtain the requester's registration information on the blockchain network for other service systems based on the first identifier;

[0318] The detection results are obtained by detecting the registration information of the requester regarding the registration of other service systems on the blockchain network.

[0319] In one embodiment of this application, if it is determined that the requester has multiple registered addresses in the blockchain network, the acquisition module 2103 is specifically configured as follows:

[0320] Select the target registered address from multiple registered addresses;

[0321] The target's registered address is used as the requester's registered address on the blockchain network for the specified service system.

[0322] In one embodiment of this application, the acquisition module 2103 is specifically configured as follows:

[0323] Send multiple registered addresses to the requester so that the requester can select the target registered address from among the multiple registered addresses;

[0324] The target registered address returned by the receiving party.

[0325] In one embodiment of this application, the apparatus further includes a transfer module; wherein:

[0326] The receiving module 2101 is also configured to receive a virtual resource transfer request sent by a specified service system for the requester;

[0327] The transfer module is configured to transfer virtual resources to a registered address based on a virtual resource transfer request;

[0328] The return module 2104 is also configured to return the transfer result of the virtual resource to the specified service system.

[0329] In one embodiment of this application, the transfer module is specifically configured as follows:

[0330] Obtain the verification result for the requester based on the virtual resource transfer request; wherein, the verification result is the result of the verification of the requester within a specified time period, and the specified time period is before the current time.

[0331] If the verification result indicates that the verification of the requester has passed, the virtual resources are transferred to the registered address.

[0332] In one embodiment of this application, the virtual resource transfer request carries a second identifier of the requester. This second identifier is assigned to the requester by the designated service system after the requester successfully registers with the designated service system on the blockchain network. The transfer module is further configured as follows:

[0333] Based on the preset mapping relationship between the second identifier and the first identifier, a first identifier that matches the second identifier is determined; wherein, the first identifier is assigned to the requester by the management system after the requester successfully registers on the management system;

[0334] Obtain other identifiers associated with the first identifier, and use the service systems corresponding to these other identifiers as the target service systems; wherein, the other identifiers are assigned to the requester by the other service systems;

[0335] Obtain the verification result initiated by the target service system for the requester.

[0336] In one embodiment of this application, the verification result includes verification results initiated by multiple target service systems for the requester; the transfer module is further configured as follows:

[0337] The security levels of multiple target service systems are tested separately.

[0338] If at least one target service system has a security level greater than a preset security level threshold, and the verification result initiated by at least one target service system for the requester indicates that the verification of the requester has passed, then the virtual resources are transferred to the registered address.

[0339] In one embodiment of this application, the transfer module is further configured as follows:

[0340] Obtain the virtual resource whose identification information matches the virtual resource from the registered address of the designated service system on the blockchain network;

[0341] Transfer the acquired virtual resources to the registered address.

[0342] In one embodiment of this application, the apparatus further includes an integration module; wherein:

[0343] The receiving module 2101 is also configured to receive virtual resource query requests sent by the requester;

[0344] The acquisition module 2103 is also configured to obtain the registered addresses of the requester for each service system on the blockchain network based on the virtual resource query request;

[0345] The integration module is configured to integrate the virtual resources contained in the registered addresses of various service systems on the blockchain network for the requester, and obtain the integration result of the virtual resources.

[0346] Return module 2104 is also configured to return the integration result of the virtual resources to the requester.

[0347] In one embodiment of this application, the virtual resource query request carries a first identifier of the requester, which is assigned to the requester by the management system after the requester successfully registers on the management system; the acquisition module 2103 is specifically configured as follows:

[0348] The first identifier is used to obtain the registered addresses of the requester on the blockchain network for each service system.

[0349] In one embodiment of this application, the apparatus further includes a selection module and a migration module; wherein:

[0350] The receiving module 2101 is also configured to receive virtual resource migration requests sent by the requester;

[0351] The acquisition module 2103 is also configured to acquire the registered addresses of the requester for each service system on the blockchain network based on the virtual resource migration request;

[0352] The selection module is configured to select the first registration address to be migrated and the second registration address to be migrated to from the registered addresses of each service system on the blockchain network.

[0353] The migration module is configured to migrate virtual resources contained in the first registration address to the second registration address;

[0354] The return module 2104 is also configured to return the migration result of the virtual resource to the requester.

[0355] In one embodiment of this application, the virtual resource migration request carries a first identifier of the requester, which is assigned to the requester by the management system after the requester successfully registers on the management system; the acquisition module 2103 is specifically configured as follows:

[0356] The first identifier is used to obtain the registered addresses of the requester on the blockchain network for each service system.

[0357] In one embodiment of this application, the apparatus further includes a deregistration module; wherein:

[0358] The cancellation module is configured to cancel the first registered address in the blockchain network and obtain the cancellation result of the first registered address;

[0359] The return module 2104 is also configured to return the deregistration result of the first registered address to the requester.

[0360] In one embodiment of this application, the apparatus further includes a registration module; wherein:

[0361] The registration module is configured to register the requester for the specified service system on the blockchain network and generate a registration address if the detection result indicates that the requester has failed to register for other service systems on the blockchain network.

[0362] The return module 2104 is also configured to return the newly generated registration address to the requester.

[0363] In one embodiment of this application, the designated service system and other service systems are service systems corresponding to different merchants; or the designated service system is a designated development channel corresponding to a designated merchant system, and other service systems are at least one of the development channels of other merchant systems and other development channels of the designated merchant system.

[0364] It should be noted that the apparatus provided in the foregoing embodiments and the method provided in the foregoing embodiments belong to the same concept, and the specific way in which each module and unit performs operations has been described in detail in the method embodiments.

[0365] Embodiments of this application also provide an electronic device, including: one or more processors; and a storage device for storing one or more programs, which, when executed by one or more processors, enable the electronic device to implement the aforementioned service management method based on a blockchain network.

[0366] Figure 22 This is a schematic diagram of the structure of a computer system suitable for implementing the electronic devices of the present application embodiments.

[0367] It should be noted that, Figure 22 The computer system 2200 of the electronic device shown is merely an example and should not impose any limitation on the functionality and scope of use of the embodiments of this application.

[0368] like Figure 22As shown, the computer system 2200 includes a Central Processing Unit (CPU) 2201, which can perform various appropriate actions and processes, such as executing the methods described in the above embodiments, based on programs stored in Read-Only Memory (ROM) 2202 or programs loaded from storage portion 2208 into Random Access Memory (RAM) 2203. The RAM 2203 also stores various programs and data required for system operation. The CPU 2201, ROM 2202, and RAM 2203 are interconnected via a bus 2204. An Input / Output (I / O) interface 2205 is also connected to the bus 2204.

[0369] The following components are connected to I / O interface 2205: an input section 2206 including a keyboard, mouse, etc.; an output section 2207 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 2208 including a hard disk, etc.; and a communication section 2209 including a network interface card such as a LAN (Local Area Network) card, modem, etc. The communication section 2209 performs communication processing via a network such as the Internet. A drive 2210 is also connected to I / O interface 2205 as needed. Removable media 2211, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., are installed on drive 2210 as needed so that computer programs read from them can be installed into storage section 2208 as needed.

[0370] Specifically, according to embodiments of this application, the processes described above with reference to the flowcharts can be implemented as computer software programs. For example, embodiments of this application include a computer program product comprising a computer program carried on a computer-readable medium, the computer program including a computer program for performing the methods shown in the flowcharts. In such embodiments, the computer program can be downloaded and installed from a network via communication section 2209, and / or installed from removable medium 2211. When the computer program is executed by central processing unit (CPU) 2201, it performs various functions defined in the system of this application.

[0371] It should be noted that the computer-readable medium shown in the embodiments of this application can be a computer-readable signal medium or a computer-readable storage medium, or any combination of the two. For example, a computer-readable medium can be an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination thereof. More specific examples of a computer-readable medium may include, but are not limited to: an electrical connection having one or more wires, a portable computer disk, a hard disk, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), flash memory, optical fiber, portable compact disc read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination thereof. In this application, a computer-readable medium can be any tangible medium containing or storing a program that can be used by or in conjunction with an instruction execution system, apparatus, or device. In this application, a computer-readable signal medium can include a data signal propagated in baseband or as part of a carrier wave, carrying a computer-readable computer program. Such propagated data signals can take various forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination thereof. Computer-readable signal media can also be any computer-readable medium other than computer-readable storage media, which can send, propagate, or transmit a program for use by or in connection with an instruction execution system, apparatus, or device. The computer program contained on the computer-readable medium can be transmitted using any suitable medium, including but not limited to wireless, wired, etc., or any suitable combination thereof.

[0372] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this application. Each block in a flowchart or block diagram may represent a module, segment, or portion of code, which contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in a block diagram or flowchart, and combinations of blocks in a block diagram or flowchart, may be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0373] The units described in the embodiments of this application can be implemented in software or hardware, and the described units can also be located in a processor. The names of these units do not necessarily limit the specific unit itself.

[0374] Another aspect of this application provides a computer-readable medium storing a computer program that, when executed by a processor, implements the aforementioned service management method based on a blockchain network. This computer-readable medium may be included in the electronic device described in the above embodiments, or it may exist independently and not incorporated into the electronic device.

[0375] Another aspect of this application provides a computer program product or computer program including computer instructions stored in a computer-readable medium. A processor of a computer device reads the computer instructions from the computer-readable medium and executes the computer instructions, causing the computer device to perform the service management method based on a blockchain network provided in the various embodiments described above.

[0376] The above description is merely a preferred exemplary embodiment of this application and is not intended to limit the implementation of this application. Those skilled in the art can easily make corresponding modifications or alterations based on the main concept and spirit of this application. Therefore, the scope of protection of this application should be determined by the scope of protection claimed in the claims.

Claims

1. A service management method based on a blockchain network, characterized in that, The method includes: The system receives a registration request from a requester for a specified service system on the blockchain network; wherein the registration request carries reuse information for indicating the reuse of a registered address; Based on the reuse information, the registration status of the requester for other service systems on the blockchain network is detected, and the detection result is obtained; If the detection result indicates that the requester has successfully registered for other service systems on the blockchain network, then the registered address of the requester on the blockchain network is obtained; the registered address is a blockchain address used to store the virtual resources of the requester in the other service systems. The obtained registered address is used as the registration address of the requester on the blockchain network for storing the virtual resources of the requester in the specified service system, and the registered address is returned to the requester. If the detection result indicates that the requester has failed to register for the other service system on the blockchain network, a blockchain address is generated to serve as the registration address of the requester for the specified service system on the blockchain network.

2. The method as described in claim 1, characterized in that, The step of detecting the requester's registration status for other service systems on the blockchain network based on the reuse information, and obtaining the detection result, includes: Based on the reuse information, detect whether the designated service system is the first service system that the requester has registered on the blockchain network. If the designated service system is not the first service system that the requester has registered on the blockchain network, then the registration status of the requester for other service systems on the blockchain network is detected to obtain the detection result.

3. The method as described in claim 2, characterized in that, The registration request also carries the first identifier of the requester, which is assigned to the requester by the management system after the requester successfully registers on the management system; The step of detecting whether the designated service system is the first service system that the requester has registered on the blockchain network based on the reuse information includes: Based on the first identifier, detect whether the designated service system is the service system that the requester has first registered on the blockchain network; The detection of the requester's registration status with other service systems on the blockchain network, and the resulting detection results, include: Based on the first identifier, obtain the registration information of the requester for other service systems on the blockchain network; The detection results are obtained by detecting the registration status of the requester for other service systems on the blockchain network based on the registration information.

4. The method as described in claim 1, characterized in that, If it is found that the requester has multiple registered addresses in the blockchain network, then using the obtained registered addresses as the registration addresses of the requester on the blockchain network for storing the virtual resources of the requester in the designated service system includes: Select the target registered address from the plurality of registered addresses; The target's registered address is used as the registration address of the requester for the specified service system on the blockchain network.

5. The method as described in claim 4, characterized in that, The step of selecting a target registered address from the plurality of successfully registered addresses includes: Send the plurality of registered addresses to the requester, so that the requester selects the target registered address from the plurality of registered addresses; The target's registered address is returned by the requesting party.

6. The method according to any one of claims 1 to 5, characterized in that, After returning the registered address to the requester, the method further includes: Receive a virtual resource transfer request sent by the designated service system to the requester; Transfer the virtual resource to the registered address according to the virtual resource transfer request; Return the transfer result of the virtual resources to the specified service system.

7. The method as described in claim 6, characterized in that, The step of transferring virtual resources to the registered address according to the virtual resource transfer request includes: The verification result for the requester is obtained according to the virtual resource transfer request; wherein the verification result is the result of verifying the requester within a specified time period, and the specified time period is before the current time. If the verification result indicates that the verification of the requester is successful, then the virtual resources are transferred to the registered address.

8. The method as described in claim 7, characterized in that, The virtual resource transfer request carries a second identifier of the requester, which is assigned to the requester by the designated service system after the requester has successfully registered with the designated service system on the blockchain network. The step of obtaining the verification result for the requester based on the virtual resource transfer request includes: Based on the preset mapping relationship between the second identifier and the first identifier, a first identifier that matches the second identifier is determined; wherein, the first identifier is assigned to the requester by the management system after the requester successfully registers on the management system; Obtain other identifiers associated with the first identifier, and use the service system corresponding to the other identifiers as the target service system; wherein, the other identifiers are assigned to the requester by the other service system; Obtain the verification result initiated by the target service system for the requester.

9. The method as described in claim 7, characterized in that, The verification results include verification results initiated by multiple target service systems for the requester; if the verification results indicate that the verification of the requester is successful, then transferring virtual resources to the registered address includes: The security levels of the multiple target service systems are detected respectively; If at least one target service system has a security level greater than a preset security level threshold, and the verification result initiated by the at least one target service system for the requester indicates that the verification of the requester has passed, then the virtual resources are transferred to the registered address.

10. The method as described in claim 7, characterized in that, The virtual resource transfer request carries the identification information of the virtual resource; the transfer of the virtual resource to the registered address includes: The system obtains virtual resources that match the identification information of the virtual resources from the registration address of the designated service system on the blockchain network. The acquired virtual resources are transferred to the registered address.

11. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive the virtual resource query request sent by the requesting party; Based on the virtual resource query request, obtain the registered addresses of the requesting party for each service system on the blockchain network; The requester integrates the virtual resources contained in the registered addresses of various service systems on the blockchain network to obtain the integration result of virtual resources. The integration result of the virtual resources is returned to the requesting party.

12. The method as described in claim 11, characterized in that, The virtual resource query request carries a first identifier of the requester, which is assigned to the requester by the management system after the requester has successfully registered on the management system. The step of obtaining the registration address corresponding to the successful registration of the requester for each service system on the blockchain network based on the virtual resource query request includes: Based on the first identifier, obtain the registered addresses of the requester for each service system on the blockchain network.

13. The method according to any one of claims 1 to 5, characterized in that, The method further includes: Receive the virtual resource migration request sent by the requesting party; Based on the virtual resource migration request, obtain the registered addresses of the requesting party for each service system on the blockchain network; From the registered addresses of each service system on the blockchain network, the requesting party selects a first registration address to be migrated and a second registration address to which it needs to be migrated; The virtual resources contained in the first registration address are migrated to the second registration address; The migration result of the virtual resource is returned to the requester.

14. The method as described in claim 13, characterized in that, The virtual resource migration request carries a first identifier of the requester, which is assigned to the requester by the management system after the requester has successfully registered on the management system. The step of obtaining the registered addresses of the requesting party for each service system on the blockchain network according to the virtual resource migration request includes: Based on the first identifier, obtain the registered addresses of the requester for each service system on the blockchain network.

15. The method as described in claim 13, characterized in that, After migrating the virtual resources contained in the first registration address to the second registration address, the method further includes: The first registered address is deregistered in the blockchain network to obtain the deregistration result of the first registered address; Return the cancellation result of the first registered address to the requesting party.

16. The method according to any one of claims 1 to 5, characterized in that, After detecting the requester's registration status for other service systems on the blockchain network based on the reuse information and obtaining the detection result, the method further includes: If the detection result indicates that the requester has failed to register for other service systems on the blockchain network, then the requester will register for the specified service system on the blockchain network and generate a registration address. Return the newly generated registration address to the requester.

17. A service management device based on a blockchain network, characterized in that, The device includes: The receiving module is configured to receive a registration request sent by a requester for a specified service system on the blockchain network; wherein the registration request carries reuse information for indicating the reuse of a registered address; The detection module is configured to detect the registration status of the requester for other service systems on the blockchain network based on the reuse information, and obtain the detection result; The acquisition module is configured to acquire the registered address of the requester on the blockchain network if the detection result indicates that the requester has successfully registered for other service systems on the blockchain network; the registered address is a blockchain address used to store the virtual resources of the requester in the other service systems. The return module is configured to use the obtained registered address as the registration address of the requester on the blockchain network for storing the virtual resources of the requester in the specified service system, and return the registered address to the requester. The device is further configured to, if the detection result indicates that the requester has failed to register for the other service system on the blockchain network, generate a blockchain address, and use the generated blockchain address as the registration address of the requester for the specified service system on the blockchain network.

18. An electronic device, characterized in that, include: One or more processors; A storage device for storing one or more programs, which, when executed by the electronic device, cause the electronic device to implement the service management method based on a blockchain network as described in any one of claims 1 to 16.

19. A computer-readable medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the service management method based on a blockchain network as described in any one of claims 1 to 16.

20. A computer program product comprising computer instructions, characterized in that, When the computer instructions are executed by the processor, they implement the service management method based on a blockchain network as described in any one of claims 1 to 16.

Images