Cross-chain invitation method and device for alliance members, medium and electronic equipment

Abstract

The embodiment of the invention provides a cross-chain invitation method and device for alliance members, a computer readable medium and electronic equipment. The method comprises the following steps: acquiring an alliance invitation request of an alliance creator corresponding to a first block chain network; constructing a cross-chain network invitation member transaction according to the alliance invitation request, storing the cross-chain network invitation member transaction to a global routing chain, and obtaining a cross-chain network invitation member transaction event from the global routing chain by a target control console to which a target object corresponding to the second block chain network belongs, after a processing result of the cross-chain network invitation member transaction event by the target object is received, the processing result transaction is stored to the global routing chain; and obtaining the triggered processing result transaction event from the global routing chain, and when determining that the target object agrees to join the target alliance according to the processing result transaction event, storing alliance member joining information to the first block chain network. According to the embodiment of the invention, invitation of alliance members across different block chain networks is realized.

Description

Technical Field

[0001] This application relates to the field of blockchain technology. Specifically, it relates to a method, apparatus, computer-readable medium, and electronic device for cross-chain invitation of consortium members. Background Art

[0002] Forming a consortium is an important way to conduct network collaboration.

[0003] Currently, a centralized method is mainly used to invite consortium members. In this way, different institutions use the same platform, and the internal operation and decision-making processes lack transparency, posing a risk of damage to user rights and interests, and the applicable scope of inviting consortium members is relatively small. Summary of the Invention

[0004] Embodiments of this application provide a method, apparatus, computer-readable medium, and electronic device for cross-chain invitation of consortium members, which can, at least to a certain extent, invite users docked to the control consoles of different blockchains to join the same consortium, thereby expanding the applicable scope of inviting consortium members.

[0005] Other features and advantages of this application will become apparent through the following detailed description, or will be partially learned through the practice of this application.

[0006] According to one aspect of the embodiments of this application, a method for cross-chain invitation of consortium members is provided. The method includes: obtaining a consortium invitation request from a consortium creator, where the consortium invitation request is used to invite a target object corresponding to a second blockchain network to join a target consortium created by the consortium creator, and the consortium creator corresponds to a first blockchain network; constructing a cross-chain network invitation member transaction according to the consortium invitation request, and storing the cross-chain network invitation member transaction in a global routing chain, so that a target console to which the target object belongs obtains a subscribed cross-chain network invitation member transaction event from the global routing chain, and after receiving a processing result of the cross-chain network invitation member transaction event by the target object, storing a processing result transaction constructed according to the processing result in the global routing chain, where the cross-chain network invitation member transaction event is triggered by the cross-chain network invitation member transaction, and the global routing chain is a blockchain in a blockchain network located outside the first blockchain network and the second blockchain network; obtaining a processing result transaction event triggered by the processing result transaction from the global routing chain, and when it is determined according to the processing result transaction event that the target object agrees to join the target consortium, storing consortium member joining information in a first blockchain of the first blockchain network, where the consortium member joining information is used to indicate that the target object is added to the target consortium.

[0007] According to one aspect of the embodiments of the present application, there is provided a cross-chain invitation device for consortium members. The device includes: an acquisition unit, configured to acquire a consortium invitation request from a consortium creator, where the consortium invitation request is used to invite a target object corresponding to a second blockchain network to join a target consortium created by the consortium creator, and the consortium creator corresponds to a first blockchain network; a construction and storage unit, configured to construct a cross-chain network invitation member transaction according to the consortium invitation request and store the cross-chain network invitation member transaction in a global routing chain, so that a target control console to which the target object belongs obtains a subscribed cross-chain network invitation member transaction event from the global routing chain, and after receiving a processing result of the target object for the cross-chain network invitation member transaction event, stores a processing result transaction constructed according to the processing result in the global routing chain, where the cross-chain network invitation member transaction event is triggered by the cross-chain network invitation member transaction, and the global routing chain is a blockchain in a blockchain network located outside the first blockchain network and the second blockchain network; an acquisition and storage unit, configured to acquire a processing result transaction event triggered by the processing result transaction from the global routing chain, and in the case of determining that the target object agrees to join the target consortium according to the processing result transaction event, store consortium member joining information in a first blockchain of the first blockchain network, where the consortium member joining information is used to indicate that the target object is added to the target consortium.

[0008] In some embodiments of the present application, based on the foregoing solution, the target control console receives the processing result of the target object for the cross-chain network invitation member transaction event after sending the cross-chain network invitation member transaction event to the target object; the target control console sends the cross-chain network invitation member transaction event to the target object in the case of determining according to the cross-chain network invitation member transaction event that processing by a user belonging to the target control console is required.

[0009] In some embodiments of the present application, based on the foregoing solution, the target control console sends the cross-chain network invitation member transaction event to the target object in the case of determining according to the cross-chain network invitation member transaction event that the invited target object corresponds to the second blockchain network and determining according to the cross-chain network invitation member transaction event that processing by a user belonging to the target control console is required.

[0010] In some embodiments of the present application, based on the foregoing solution, the global routing chain includes the digital certificate of the target object, the digital certificate includes the public key of the target object, the processing result transaction and the processing result transaction event include signature information generated by the target object based on the private key of the target object for the processing result, and the device further includes a signature verification unit; after obtaining the processing result transaction event triggered by the processing result transaction from the global routing chain, the signature verification unit is configured to: verify the signature information in the processing result transaction event based on the digital certificate of the target object obtained from the global routing chain; in the case of successful verification, determine whether the target object agrees to join the target alliance according to the processing result transaction event.

[0011] In some embodiments of the present application, based on the foregoing solution, the alliance invitation request includes the identifier of the target object, the global routing chain further includes the identifiers of each object, and the device further includes a determination unit; before constructing a cross-chain network invitation member transaction according to the alliance invitation request, the determination unit is configured to: determine whether the global routing chain includes the identifier of the target object in the alliance invitation request; wherein, constructing a cross-chain network invitation member transaction according to the alliance invitation request is performed when it is determined that the global routing chain includes the identifier of the target object in the alliance invitation request.

[0012] In some embodiments of the present application, based on the foregoing solution, before determining whether the global routing chain includes the identifier of the target object in the alliance invitation request, the determination unit is configured to: determine whether the target object already belongs to the target alliance; wherein, determining whether the global routing chain includes the identifier of the target object in the alliance invitation request is performed when it is determined that the target object does not belong to the target alliance.

[0013] In some embodiments of the present application, based on the foregoing solution, the device further includes a judgment unit; before determining whether the target object already belongs to the target alliance, the judgment unit is configured to: judge whether the target object has been invited by the alliance creator, wherein, determining whether the target object already belongs to the target alliance is performed when the target object has been invited by the alliance creator.

[0014] In some embodiments of the present application, based on the foregoing solution, the acquisition and storage unit is configured to: send the alliance member joining information to the first blockchain network, so that when the blockchain node of the first blockchain network determines that the alliance member joining information is from the console corresponding to the creator of the target alliance, store the alliance member joining information in the first blockchain of the first blockchain network.

[0015] In some embodiments of the present application, based on the foregoing solution, the global routing chain is located in a global routing chain network, and the global routing chain network includes multiple nodes; the method is executed by a current control console, and the current control console is one of at least one control console corresponding to the first blockchain network, and the target control console is one of at least one control console corresponding to the second blockchain network. The control console corresponding to the first blockchain network and the control console corresponding to the second blockchain network can interact with at least one node in the global routing chain network.

[0016] According to one aspect of the embodiments of the present application, there is provided a computer-readable medium having a computer program stored thereon, and when the computer program is executed by a processor, it implements the cross-chain invitation method for consortium members as described in the above embodiments.

[0017] According to one aspect of the embodiments of the present application, there is provided an electronic device, including: one or more processors; a storage device for storing one or more programs, and when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the cross-chain invitation method for consortium members as described in the above embodiments.

[0018] According to one aspect of the embodiments of the present application, there is provided a computer program product, the computer program product includes computer instructions, the computer instructions are stored in a computer-readable storage medium, a processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the computer device executes the cross-chain invitation method for consortium members as described in the above embodiments.

[0019] In the technical solutions provided by some embodiments of the present application, after obtaining an alliance invitation request from the alliance creator corresponding to the first blockchain network, a cross-chain network invitation member transaction is constructed according to the alliance invitation request, and then the cross-chain network invitation member transaction is stored in the global routing chain of a blockchain network outside the first blockchain network and the second blockchain network. This enables the target control console to which the target object belongs to obtain a cross-chain network invitation member transaction event triggered by the cross-chain network invitation member transaction from the global routing chain. The target object can also feedback a corresponding processing result to the target control console, and the target control console will store the processing result transaction constructed according to the processing result in the global routing chain. After that, the target control console can obtain the subscribed processing result transaction event triggered by the processing result transaction from the global routing chain. Thus, when it is determined according to the processing result transaction event that the target object agrees to join the target alliance, the alliance member joining information indicating that the target object is added to the target alliance is stored in the first blockchain of the first blockchain network. On the one hand, since the blockchain networks corresponding to the alliance creator and the target object can be different blockchain networks, users on different blockchain-connected control consoles can be invited to join the same alliance, realizing the invitation of alliance members across different blockchain networks and greatly expanding the applicable scope of inviting alliance members. On the other hand, since the cross-chain network invitation member transaction, the processing result transaction, and the alliance member joining information are all stored in the global routing chain, all links of inviting alliance members can be traced through the blockchain, reducing the risk of centralized malicious behavior, enhancing transparency, improving the reliability and traceability of inviting alliance members, and ensuring user rights and interests.

[0020] It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and cannot limit the present application. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] The accompanying drawings herein are incorporated into the specification and form a part of the specification, showing embodiments consistent with the present application, and are used together with the specification to explain the principles of the present application. Obviously, the accompanying drawings in the following description are only some embodiments of the present application. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts. In the drawings:

[0022] Figure 1 A schematic diagram showing the invitation of group members using a centralized platform in the related art is shown;

[0023] Figure 2 A schematic diagram showing the invitation of alliance members based on blockchain in the related art is shown;

[0024] Figure 3A schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied is shown;

[0025] Figure 4 A flowchart of a cross-chain invitation method for consortium members according to an embodiment of the present application is shown;

[0026] Figure 5 A schematic diagram of a schematic principle according to an embodiment of the present application is shown;

[0027] Figure 6A A schematic diagram of the first part of a timing diagram according to an embodiment of the present application is shown;

[0028] Figure 6B A schematic diagram of the second part of a timing diagram according to an embodiment of the present application is shown;

[0029] Figure 7 A flowchart showing the steps before step 450 and the details of step 450 in an embodiment according to the present application; Figure 4 is shown;

[0030] Figure 8 A flowchart showing the steps before step 440 and the details of step 440 in an embodiment according to the present application; Figure 7 is shown;

[0031] Figure 9 A flowchart showing the steps before step 430 and the details of step 430 in an embodiment according to the present application; Figure 8 is shown;

[0032] Figure 10 A flowchart showing the details of step 460 in an embodiment according to the present application; Figure 4 is shown;

[0033] Figure 11 A block diagram of a cross-chain invitation device for consortium members according to an embodiment of the present application is shown;

[0034] Figure 12 A schematic diagram of the structure of a computer system of an electronic device suitable for implementing the embodiments of the present application is shown. Detailed implementation manners

[0035] Example embodiments will now be described more fully with reference to the accompanying drawings. However, the example embodiments can be implemented in various forms and should not be construed as limited to the examples set forth herein; rather, these embodiments are provided so that this application will be more complete and comprehensive, and will fully convey the concept of the example embodiments to those skilled in the art.

[0036] In addition, the described features, structures, or characteristics may be combined in any suitable manner in one or more embodiments. In the following description, numerous specific details are provided to give a thorough understanding of the embodiments of the present application. However, those skilled in the art will realize that the technical solutions of the present application may be practiced without one or more of the specific details, or other methods, components, devices, steps, etc. may be employed. In other cases, well-known methods, devices, implementations, or operations are not shown or described in detail to avoid obscuring aspects of the present application.

[0037] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of an overall module or unit that includes the function of that module or unit.

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

[0039] The flowcharts shown in the drawings are only illustrative and do not necessarily include all the contents and operations / steps, nor are they necessarily executed in the described order. For example, some operations / steps can be decomposed, while some operations / steps can be combined or partially combined, so the actual execution order may change according to the actual situation.

[0040] In the related art, the following two main schemes are mainly adopted for inviting group members or alliance members:

[0041] Scheme 1: Invite group members in a centralized manner. Suppose a member alice belonging to institution A creates a group, and the group name of this group can be Trusted Group 001. alice is the group creator of this group. Assume that alice wants to invite a member bob belonging to institution B to join this group. If bob successfully joins the group, bob is a participant in this group.

[0042] Figure 1 Shows a schematic diagram of using a centralized platform to invite group members in the related art. Please refer to Figure 1As shown in the figure, Alice invites Bob to join the group she created. The specific process can include the following steps: ① Alice initiates a member invitation request through the control console to invite Bob from Organization B to join the group. The data carried by this member invitation request will be stored in the database by the control console. ② Bob from Organization B can read the same database through this control console, and thus view the information "Alice from Organization A invites me to join the trusted group 001". ③ Bob can make a decision on whether to join this group. If he decides to join the group, that is, he agrees to this member invitation request, and the consent information will also be written into the database. At the end of this process, whether it is a user on Organization A or Organization B, they can learn from the database that the user Bob from Organization B has joined the trusted computing group 001 created by the user Alice from Organization A.

[0043] Solution 2: Adopt the blockchain method to achieve decentralized invitation of cross-institutional, organizational, and group members, but this solution is based on the same chain.

[0044] Figure 2 The figure shows a schematic diagram of inviting consortium members based on blockchain in the related art. As Figure 2 shown in the figure, the process of Solution 2 is described as follows: (1) The invitation of consortium members is no longer based on a centralized platform, and it is not necessary for all institutional users to use a unified platform. (2) Alice, the consortium creator from Organization A, can invite Bob, a user from Organization B, through her own control console. (3) Alice's invitation request will be submitted to the blockchain through the control console of her organization and trigger the [Consortium Member Invitation] blockchain contract event. (4) The control consoles of each organization can subscribe to this event, and only the control console where the invited party Bob is located has the right to process this event. Other control consoles will ignore the events processed by non-current console users. (5) After the control console of Organization B subscribes to this invitation event, it will notify Bob to process it. Bob can agree or refuse. The invited processing result of Bob will also be submitted to the blockchain and trigger the [Invited Processing Result] event. (6) The control console where the invitation event initiator is located will subscribe to and process this invited processing result event. Non-invitation event initiators have no right to process and will ignore this event. If the processing result of the invited person is to agree to join the consortium, the consortium creator Alice will add the invited party Bob to the consortium.

[0045] However, the above-mentioned related technologies obviously have the following defects:

[0046] Solution 1: All member invitations need to go through a centralized control console, which has the risk of centralized abuse. The personal information of users from different organizations, institutions, and groups is exposed on this centralized control console, and it is necessary to fully trust the centralized control console.

[0047] Solution 2: Although it is based on blockchain and adopts a decentralized approach, it is only applicable when all the consoles used by organizations, institutions, and groups are based on the same chain. If other consoles are connected to other chains, members cannot invite each other, forming information silos.

[0048] Therefore, the present application first provides a method for cross-chain invitation of consortium members. The method for cross-chain invitation of consortium members provided by the embodiments of the present application can overcome the above-mentioned defects. It can not only realize the invitation of consortium members across different blockchain networks, break information silos, greatly expand the applicable scope of inviting consortium members, but also reduce the risk of centralized malicious behavior, enhance transparency, and improve the reliability and traceability of inviting consortium members.

[0049] Figure 3 The schematic diagram of an exemplary system architecture to which the technical solution of the embodiments of the present application can be applied is shown. As Figure 3 shown, the system architecture 300 may include multiple business chain networks and a global routing chain network 340. The multiple business chain networks specifically include a first business chain network 310, a second business chain network 320, and a third business chain network 330. The first business chain network 310 includes a first user terminal 311, a first console server 312, and a first blockchain network 313. The second business chain network 320 includes a second user terminal 321, a second console server 322, and a second blockchain network 323. The third business chain network 330 includes a third user terminal 331, a third console server 332, and a third blockchain network 333. Each blockchain network includes multiple blockchain nodes. Between the user terminal and the console server in each business chain network, and between the console server and the blockchain network, they are all connected through communication links. Communication connections are also established between any two blockchain nodes in each blockchain network. This enables the console server in each business chain network to communicate with any blockchain node in the blockchain network of this business chain network. The global routing chain network 340 is also a blockchain network, which includes multiple blockchain nodes. The console server in the business chain network can communicate with one or more blockchain nodes in the global routing chain network 340. The same blockchain is stored on each blockchain node of a blockchain network, and the same blockchain is also stored on each blockchain node of the global routing chain network 340. This blockchain is the global routing chain. The first console server 312 deploys a first console, and a first client capable of accessing the first console is deployed on the first user terminal 311. The second console server 322 deploys a second console, and a second client capable of accessing the second console is deployed on the second user terminal 321. The first console server 312 may be the execution subject of the solution of the embodiments of the present application. When a method for cross-chain invitation of consortium members provided by the embodiments of the present application is applied to Figure 3In the system architecture shown, a process can be as follows: First, the first user of the first user terminal 311 sends a coalition invitation request to the first control console server 312 through the first client, requesting to add the second user corresponding to the second blockchain network 323 to the target coalition created by the first user corresponding to the first blockchain network 313; then, the first control console on the first control console server 312 constructs a cross-chain network invitation member transaction according to the coalition invitation request and stores the cross-chain network invitation member transaction in the global routing chain of the global routing chain network 340; then, the cross-chain network invitation member transaction triggers a cross-chain network invitation member transaction event in the global routing chain. Since the control consoles in all business chain networks, including the second control console in the second control console server 322, have subscribed to the cross-chain network invitation member transaction event, the second control console in the second control console server 322 will receive the subscribed cross-chain network invitation member transaction event; then, the second control console sends the cross-chain network invitation member transaction event to the second user terminal 321 where the corresponding second user is located, and the second user uses the second client to process it; then, the second control console receives the processing result of the second user for the cross-chain network invitation member transaction event, constructs a corresponding processing result transaction, and stores it in the global routing chain of the global routing chain network 340; next, the processing result transaction triggers a processing result transaction event in the global routing chain. Since the control consoles in all business chain networks, including the first control console on the first control console server 312, have subscribed to the processing result transaction event, the first control console on the first control console server 312 will receive the subscribed processing result transaction event; finally, if the first control console determines that the second user agrees to join the target coalition according to the processing result transaction event, it will send the corresponding coalition member addition information to a blockchain node of the first blockchain network 313, so as to store the coalition member addition information in the first blockchain of the first blockchain network 313.

[0050] In some embodiments of the present application, a user is bound to a control console, and each user can only access the control console to which they are bound.

[0051] In some embodiments of the present application, each user can create one or more coalitions.

[0052] In some embodiments of the present application, a coalition can only allow users of different control consoles to join.

[0053] In some embodiments of the present application, different users who join a coalition have different roles, and the different users who join the coalition are used to cooperate to complete a task.

[0054] In some embodiments of the present application, the first control console also obtains the subscribed information on the joining of consortium members from the first blockchain, constructs a corresponding transaction based on the information on the joining of consortium members, and stores the transaction in the global routing chain. Other control consoles, including the second control console, will obtain the smart contract event triggered by the transaction and send the information carried by the smart contract event to the blockchain of the affiliated business chain network, and will also obtain the subscribed information from the blockchain.

[0055] In some embodiments of the present application, the control console in each business chain network can communicate with any blockchain node in the global routing chain network 340.

[0056] In some embodiments of the present application, each blockchain node in the global routing chain network 340 can only communicate with the control console in one business chain network, and the control consoles that at least two blockchain nodes in the global routing chain network 340 can communicate with belong to different business chain networks.

[0057] It should be understood that Figure 3 the number of business chain networks, the number of control console servers in each business chain network, the number of user terminals connected to each control console server, the number of blockchain nodes in the blockchain network, and the number of blockchain nodes in the global routing chain network are only illustrative. According to the implementation requirements, there can be any number of business chain networks and control console servers, the number of user terminals connected to each control console server can also be any number, and the number of blockchain nodes in the blockchain network and the global routing chain network can also be arbitrary, that is, the number of business chain networks can be less than 3 or more than 3, the control console servers can be more than 2, the number of user terminals connected to each control console server can be multiple, and the number of blockchain nodes in the blockchain network and / or the global routing chain network can be more than 5 or less than 5.

[0058] It should be noted that Figure 3 only one embodiment of the present application is shown. Although in the Figure 3 solution of the embodiment, the blockchain nodes in the blockchain network are servers, the control console runs on the server, and the user terminal is a desktop computer, in other embodiments of the present application, the blockchain nodes, the operating devices of the control console, and the user terminal can also be various types of terminal devices such as laptop computers, desktop computers, tablet computers, vehicle-mounted terminals, portable wearable devices, workstations, etc.; although in the Figure 3In the solution of the embodiment, the device types of the blockchain nodes in the blockchain network are the same. However, in other embodiments of the present application, the blockchain nodes in the blockchain network can adopt different types of devices; although the above embodiment provides a process in which a first user request corresponding to a first blockchain network adds a second user corresponding to a second blockchain network to a target alliance created by the first user, in other embodiments of the present application, Figure 3 the system architecture shown can also be applied to implement a process in which any user request corresponding to any blockchain network adds a user corresponding to any other blockchain network to an alliance; although in Figure 3 the solution of the embodiment, the transaction event is actively pushed by the blockchain network to the control console, but in other embodiments of the present application, the control console can also monitor the blockchain network and actively pull the transaction event from the blockchain network; although in Figure 3 the solution of the embodiment, the number of blockchain nodes included in different blockchain networks is the same, but in other embodiments of the present application, the number of blockchain nodes included in different blockchain networks can be different. The embodiments of the present application do not make any limitations in this regard, and the protection scope of the present application should not be limited thereby.

[0059] It is easy to understand that the cross-chain invitation method for alliance members provided by the embodiments of the present application is generally executed by a server. Correspondingly, the cross-chain invitation device for alliance members is generally set in the server. However, in other embodiments of the present application, the terminal device can also have a similar function to the server, so as to execute the cross-chain invitation solution for alliance members provided by the embodiments of the present application.

[0060] Therefore, the embodiments of the present application can be applied to a terminal or a server. The server can be an independent physical server, or a server cluster or a distributed system composed of multiple physical servers. It can also be a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN, and big data and artificial intelligence platforms. The terminal can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a smart speaker, a smart watch, etc., but is not limited thereto. The terminal and the server can be directly or indirectly connected through wired or wireless communication methods, and the present application does not make any restrictions in this regard.

[0061] The solution of the embodiment of this application can be applied to the field of blockchain. Blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithms. Blockchain, in essence, is a decentralized database, a series of data blocks generated by using cryptographic methods. Each data block contains information about a batch of network transactions, which is used to verify the validity of the information (anti-counterfeiting) and generate the next block. Blockchain can include the blockchain underlying platform, the platform product service layer, and the application service layer.

[0062] The blockchain underlying platform can include processing modules such as user management, basic services, smart contracts, and operation monitoring. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private keys (account management), key management, and the maintenance of the correspondence between the real identity of the user and the blockchain address (permission management). And under authorized circumstances, it supervises and audits the transaction situations of certain real identities, and provides the rule configuration for risk control (risk control and auditing); the basic service module is deployed on all blockchain node devices, used to verify the validity of business requests, and record them on the storage after consensus on valid requests. For a new business request, the basic service first performs interface adaptation parsing and authentication processing (interface adaptation), then encrypts the business information through the consensus algorithm (consensus management), transmits it to the shared ledger completely and consistently after encryption (network communication), and performs record storage; the smart contract module is responsible for the registration and issuance of contracts, contract triggering, and contract execution. Developers can define contract logic through a certain programming language, publish it to the blockchain (contract registration), trigger the execution according to the logic of the contract terms by calling keys or other events, complete the contract logic, and at the same time provide the functions of contract upgrade and cancellation; the operation monitoring module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation during the product release process, and the visual output of the real-time state during product operation, such as: alarming, monitoring the network situation, monitoring the health status of node devices, etc.

[0063] The platform product service layer provides the basic capabilities and implementation frameworks of typical applications. Developers can build on these basic capabilities and overlay the characteristics of the business to complete the blockchain implementation of the business logic. The application service layer provides application services based on the blockchain solution for business participants to use.

[0064] The following elaborates in detail on the implementation details of the technical solution of the embodiment of this application:

[0065] Figure 4The flowchart of the cross-chain invitation method for alliance members according to an embodiment of the present application is shown. The cross-chain invitation method for alliance members can be executed by various devices capable of computing and processing, such as user terminals or cloud servers. User terminals include, but are not limited to, mobile phones, computers, intelligent voice interaction devices, smart home appliances, vehicle-mounted terminals, aircraft, smart watches, etc. The cross-chain invitation method for alliance members can be executed by the current control console deployed on these terminals or devices. Please refer to Figure 4 As shown, the cross-chain invitation method for alliance members at least includes the following steps:

[0066] In step 410, obtain an alliance invitation request from the alliance creator. The alliance invitation request is used to invite a target object corresponding to the second blockchain network to join the target alliance created by the alliance creator, and the alliance creator corresponds to the first blockchain network.

[0067] The alliance creator can be a user belonging to the current control console. The alliance creator can send an alliance invitation request to the current control console through its client. The alliance invitation request can include the identification information of the alliance creator and the identification information of the invited target object. Of course, the alliance invitation request can also include the identification information of the target alliance that the target object is invited to join.

[0068] In an embodiment of the present application, the alliance invitation request further includes the identification information and name of the target object.

[0069] The name of the target object is the nickname of the target object, which can also be used for information verification.

[0070] An alliance is a collection of objects, equivalent to a group. The objects in the alliance can be users or accounts. An alliance is composed of trusted collaborative participants. When an object is invited to join the alliance, the object becomes a participant in the alliance. Different participants in the same alliance can participate in trusted collaboration. Participants have roles, and different participants in the same alliance can have different roles. For example, the roles of four participants in an alliance can be a computing task creator, a data source provider, a computing model provider, and a computing result user respectively. These participants with different roles can complete trusted computing tasks through collaboration. Among them, the data source provider is used to provide the data required for trusted computing, the computing model provider is used to provide the trusted computing logic, the computing task creator is used to create a trusted computing task, and can configure the task name, task description, alliance, data source provider, computing model provider, computing result user, etc. in the trusted computing task. The alliance creator can also be a participant in the alliance.

[0071] Figure 5 The schematic diagram according to an embodiment of the present application is shown. Please refer to Figure 5As shown, it shows three business chain networks. Each business chain network includes a blockchain network and several BCC (Blockchain Confidential Computing) control consoles. Each BCC control console belongs to an organization, institution, or group. Each BCC control console has several users belonging to that BCC control console. Therefore, for each BCC control console, the users belonging to that BCC control console are also the users of the organization, institution, or group to which the BCC control console belongs, that is, the users of the business chain network where the BCC control console is located, and also the users corresponding to the blockchain network in the business chain network where the BCC control console is located. Each BCC control console can only be accessed by the users exclusive to that BCC control console. Organizations, institutions, or groups can be various entities such as hospitals, schools, etc. The same person can be a user of different institutions or BCC control consoles.

[0072] Figure 5 The blockchain network in [description] includes multiple blockchain nodes. Any two blockchain nodes in the blockchain network can communicate with each other. Each BCC control console can communicate with one or more blockchain nodes in the blockchain network. For example, it can communicate with the blockchain node closest to it in the blockchain network. Each blockchain node can also belong to an institution. A blockchain is stored on the blockchain node. The global routing chain network includes multiple blockchain nodes. A global routing chain, which is a blockchain, is stored on each blockchain node. Each blockchain node corresponds to a business chain network, and each blockchain node can communicate with the BCC control console in the corresponding business chain network. For example, Figure 5 the global routing chain network in [description] includes two blockchain nodes corresponding to business chain network 1. Each BCC control console includes multiple modules. The cross-chain gateway module in the BCC control console can be used to interact with the corresponding blockchain node in the global routing chain network.

[0073] Users of the same or different business chain networks can join the same trusted computing alliance. Each user, as a participant in the alliance, can perform trusted computing. As Figure 5 shown, different users in the same trusted computing alliance can set up a group of trusted computing resources to perform trusted computing.

[0074] Suppose user alice in business chain network 1 creates a coalition named "Trusted Coalition 001". Then, user alice becomes the creator of this coalition. If coalition creator alice wants to invite user bob in business chain network 2 to join this coalition, user bob will become a participant in this coalition after joining. Each user of each institution can act as both the creator and the participant of a coalition. Each user can create one or more coalitions, and each institution or each control console can have creators of multiple coalitions.

[0075] Although in the above embodiments, each blockchain node in the global routing chain network can only communicate with the BCC control console in the business chain network corresponding to this blockchain node, in other embodiments of the present application, a blockchain node in the global routing chain network can also communicate with any BCC control console in any business chain network.

[0076] Therefore, the business chain network to which the first blockchain network belongs includes one or more control consoles corresponding to the first blockchain network. The current control console is one of at least one control console corresponding to the first blockchain network, and each control console corresponding to the first blockchain network can access the first blockchain.

[0077] Next, in combination with Figure 6A and Figure 6B to further introduce the solution of the embodiments of the present application. Figure 6A The schematic diagram shows the first part of a timing diagram according to an embodiment of the present application. Please refer to Figure 6A As shown, it involves user alice of organization A and BCC control console A, user bob of organization B and BCC control console B, and the global routing chain provided by the routing chain network. Among them, BCC control console A and BCC control console B belong to different business chain networks and correspond to different blockchain networks. User alice can be the coalition creator, and she can invite user bob to join the coalition created by user alice, making user bob become a participant in this coalition. It is easy to understand that Figure 6A and Figure 6B the business chain networks in should actually be blockchain networks. For the convenience of description here, they are collectively referred to as business chain networks.

[0078] First, in the stage of participant identity release, the following steps are executed:

[0079] Step 01, user bob sends an account creation request to BCC control console B to create a Bob account on BCC control console B.

[0080] This step can be performed through the management page of BCC control console B of organization B.

[0081] Step 02, Bob's identity completion information is uploaded to the local business chain, and sensitive information is encrypted and stored in the local database.

[0082] Whenever a new account is created, the corresponding identity completion information needs to be uploaded to the local business chain. Sensitive information includes the user's private key. Identity completion information includes basic identity information and other information. Basic identity information specifically includes: chain network number, user identifier, user nickname, and user chain identity certificate. Among them, the chain network number is the number of the blockchain network corresponding to the user; the user identifier is the identifier corresponding to the user, such as a UUID (Universally Unique Identifier); the user nickname can be a string provided by the user in a personalized manner; the user chain identity certificate is the user's digital certificate, which can include the user's public key. The local business chain is the business chain network 2 corresponding to the BCC control console B, that is, the blockchain network corresponding to the BCC control console B.

[0083] Step 03, the BCC control console B receives the TxID (Transaction ID) returned by the business chain network 2.

[0084] Step 04, the BCC control console B publishes the basic identity information of user bob to the global routing chain in the routing chain network.

[0085] Step 05, the BCC control console B receives the TxID (Transaction ID) returned by the business chain network 2.

[0086] Step 06, the BCC control console B returns the received TxID to user bob.

[0087] Then, as the invited party, Organization A performs the following steps in the invitation request initiation stage:

[0088] Step 07, user alice sends an invitation request to the BCC control console A to invite user bob to join the alliance she created.

[0089] User alice can send an invitation request by filling in the identifier (such as 100001) and nickname (such as bob) of user bob.

[0090] Step 08, the BCC control console A verifies the identity and permissions of the requester who sent the invitation request.

[0091] Specifically, the invitation request can carry the identity identifier of the requester. Based on this identity identifier, it can be determined whether the requester, user alice, has the permission to create an alliance and whether it is disabled, so as to perform the identity and permission verification.

[0092] In the introductionFigure 4 Before step 450 in the embodiment, the steps before step 450 will be introduced in detail.

[0093] In one embodiment of the present application, the alliance invitation request includes the identifier of the target object. The global routing chain also includes the identifiers of each object. The global routing chain is located in the global routing chain network, and the global routing chain network includes multiple nodes. The control console corresponding to the first blockchain network can interact with at least one node in the global routing chain network.

[0094] The global routing chain is also a blockchain, and the global routing chain network is a blockchain network independent of the first blockchain network and the second blockchain network.

[0095] Figure 7 Shows a Figure 4 Flowchart of the steps before step 450 and the details of step 450 in the embodiment according to one embodiment of the present application.

[0096] Please refer to Figure 7 As shown, in step 440, it is determined whether the global routing chain includes the identifier of the target object in the alliance invitation request.

[0097] In the case where it is determined that the global routing chain includes the identifier of the target object in the alliance invitation request, step 450 is executed.

[0098] As mentioned above, the global routing chain includes the identifiers of all objects. Therefore, it is possible to determine whether the identifier of the target object is included by querying the global routing chain.

[0099] In one embodiment of the present application, the alliance invitation request further includes the nickname of the target object. Determining whether the global routing chain includes the identifier of the target object in the alliance invitation request includes: determining whether the global routing chain includes the identifier of the target object in the alliance invitation request; in the case where the identifier of the target object in the alliance invitation request is included, determining whether the nickname corresponding to the identifier of the target object in the global routing chain is consistent with the nickname of the target object in the alliance invitation request; if so, step 450 is executed.

[0100] Although the user identifier can be a globally unique code such as UUID that can uniquely identify a user in different business chain networks, in some scenarios, the user identifier may be unique only in the corresponding business chain network, and the same user identifier may exist in different business chain networks. In the embodiments of the present application, through double verification based on the identifier and nickname of the target object, the reliability of the invitation is ensured.

[0101] Figure 8 Shows a Figure 7 Flowchart of the steps before step 440 and the details of step 440 in the embodiment according to one embodiment of the present application. Please refer toFigure 8 As shown, before determining whether the global routing chain includes the identifier of the target object in the alliance invitation request, the cross-chain invitation method for the alliance member further includes the following steps:

[0102] In step 430, determine whether the target object already belongs to the target alliance.

[0103] It is possible to determine whether the target object already belongs to the target alliance by querying the first blockchain network.

[0104] If the target object already belongs to the target alliance, then there will be corresponding transaction information on the blockchain; therefore, by querying the blockchain, the judgment result of whether the target object already belongs to the target alliance can be obtained. In specific applications, it is possible to query by sending query information carrying the identifier information of the target object and the identifier information of the target alliance to the nodes in the blockchain network.

[0105] If it is determined that the target object already belongs to the target alliance, the entire process can be ended.

[0106] Step 440 may specifically include the following steps:

[0107] In step 440', in the case where it is determined that the target object does not belong to the target alliance, determine whether the global routing chain includes the identifier of the target object in the alliance invitation request.

[0108] That is to say, determining whether the global routing chain includes the identifier of the target object in the alliance invitation request is carried out in the case where it is determined that the target object does not belong to the target alliance.

[0109] In the embodiment of the present application, by pre-determining whether the target object already belongs to the target alliance before executing step 430, it is possible to avoid information chaos on the blockchain and reduce useless calculations, thereby saving resources.

[0110] Figure 9 Shows a Figure 8 flowchart of the steps before step 430 and the details of step 430 in an embodiment according to the present application. Please refer to Figure 9 As shown, before determining whether the target object already belongs to the target alliance, the cross-chain invitation method for the alliance member further includes the following steps:

[0111] In step 420, determine whether the target object has been invited by the alliance creator.

[0112] Specifically, the current control console can maintain a correspondence table between coalition creators and objects. The correspondence table between coalition creators and objects can be mapped based on the information on the blockchain, and it stores the identification information of the objects invited by each coalition creator. It is possible to determine whether the target object has been invited by the coalition creator by querying the correspondence table between coalition creators and objects. Of course, it is also possible to determine whether the target object has been invited by the coalition creator by querying the first blockchain in the first blockchain network. For example, it is possible to determine whether the target object has been invited by the coalition creator by querying whether there is a corresponding transaction in the first blockchain.

[0113] In an embodiment of the present application, determining whether a target object has been invited by a coalition creator includes: determining whether the status of the target object is in an invitation state, where the invitation state means that the target object has been invited by the coalition creator and has not yet joined the target coalition created by the coalition creator.

[0114] The embodiments of the present application can make a more refined determination of the status of the target object.

[0115] Step 430 may specifically include the following steps:

[0116] In step 430', in the case where the target object has been invited by the coalition creator, determine whether the target object already belongs to the target coalition.

[0117] In the embodiments of the present application, only when the target object has been invited by the coalition creator, the steps of determining whether the target object already belongs to the target coalition and its subsequent steps are executed. Once the target object has been invited by the coalition creator, it can end, thereby avoiding invalid invitations and saving computing resources.

[0118] Please continue to refer to Figure 6A , after step 08, the following steps are further included:

[0119] Step 09, BCC control console A checks whether the user has been invited by querying the business chain network 1.

[0120] Step 10, BCC control console A obtains the corresponding query result from the business chain network 1.

[0121] Step 11, if the member has been invited, that is, if the user has been invited by alice to be a coalition member, the process ends.

[0122] Step 12, BCC control console A checks whether the user already belongs to the coalition by querying the business chain network 1.

[0123] Step 13, BCC control console A obtains the corresponding query result from the business chain network 1.

[0124] Step 14, if the member has belonged to the alliance, end the process.

[0125] Step 15, the BCC control console A checks whether the invited user Bob exists on the global routing chain.

[0126] Query whether there is a bob with the user identifier 100001 on the global routing chain.

[0127] Step 16, if it exists, the BCC control console A will obtain the chain network number where the invited user Bob is located.

[0128] The chain network number can be, for example, blockchain-lkaee2dmf6.

[0129] Please continue to refer to Figure 4 , in step 450, construct a cross-chain network invitation member transaction according to the alliance invitation request, and store the cross-chain network invitation member transaction in the global routing chain, so that the target control console to which the target object belongs can obtain the subscribed cross-chain network invitation member transaction event from the global routing chain, and after receiving the processing result of the cross-chain network invitation member transaction event by the target object, store the processing result transaction constructed according to the processing result in the global routing chain, where the cross-chain network invitation member transaction event is triggered by the cross-chain network invitation member transaction, and the global routing chain is a blockchain in a blockchain network outside the first blockchain network and the second blockchain network.

[0130] Specifically, after the cross-chain network invitation member transaction is stored in the global routing chain, an intelligent contract event of the cross-chain network invitation member transaction event will be triggered in the global routing chain network, and each control console has subscribed to the cross-chain network invitation member transaction event in advance. Therefore, the control consoles owned by each organization can receive the cross-chain network invitation member transaction event.

[0131] Please continue to refer to Figure 7 , in step 450', in the case where it is determined that the global routing chain includes the identifier of the target object in the alliance invitation request, construct a cross-chain network invitation member transaction according to the alliance invitation request.

[0132] In an embodiment of the present application, the target control console is one of at least one control console corresponding to the second blockchain network, and the control console corresponding to the second blockchain network can interact with at least one node in the global routing chain network.

[0133] In one embodiment of the present application, the target control console receives the processing result of the cross-chain network invitation member transaction event from the target object after sending the cross-chain network invitation member transaction event to the target object; the target control console sends the cross-chain network invitation member transaction event to the target object when it is determined according to the cross-chain network invitation member transaction event that the processing needs to be performed by a user belonging to the target control console.

[0134] The cross-chain network invitation member transaction event may include the identifier of the target object. The target control console stores the identifiers of each user belonging to the target control console. The target control console can determine whether the cross-chain network invitation member transaction event needs to be processed by a user belonging to the target control console by comparing the identifier of the target object in the cross-chain network invitation member transaction event with the identifiers of each user belonging to the target control console that have been stored.

[0135] In one embodiment of the present application, the target control console sends the cross-chain network invitation member transaction event to the target object when it is determined according to the cross-chain network invitation member transaction event that the target object to be invited corresponds to the second blockchain network and it is determined according to the cross-chain network invitation member transaction event that the processing needs to be performed by a user belonging to the target control console.

[0136] The cross-chain network invitation member transaction may include the chain network number corresponding to the target object. The chain network number corresponding to the second blockchain network may be stored in the target control console. The target control console can determine whether the target object to be invited corresponds to the second blockchain network by comparing the chain network number it stores with the chain network number in the cross-chain network invitation member transaction.

[0137] In an embodiment of the present application, the cross-chain network invitation member transaction event is sent to the target object only when the conditions that the target object to be invited corresponds to the second blockchain network and it is determined according to the cross-chain network invitation member transaction event that the processing needs to be performed by a user belonging to the target control console are met. When these conditions are not met, the process can be ended, avoiding useless calculations and saving computational overhead.

[0138] Please continue to refer to Figure 6A , after step 16, the following steps are further included:

[0139] Step 17, BCC control console A constructs a cross-chain network alliance member invitation event transaction.

[0140] The cross-chain network alliance member invitation event transaction is the aforementioned cross-chain network invitation member transaction.

[0141] The transaction parameters of this transaction will specify that the user ID corresponding to the invitation chain network number blockchain-lkaee2dmf6 is Bob with the user ID of 100001.

[0142] Step 18, the transaction of the consortium member invitation event is uploaded to the blockchain.

[0143] Store the cross-chain network consortium member invitation event transaction in the global routing chain.

[0144] Step 19, trigger the cross-chain network consortium member invitation event in the routing chain network.

[0145] The cross-chain network consortium member invitation event is the aforementioned cross-chain network invitation member transaction event.

[0146] Step 20, BCC control console A receives the TxID (Transaction ID) returned by the routing chain network.

[0147] Step 21, BCC control console A returns the received TxID to user alice.

[0148] Please continue to refer to Figure 6A As shown, organization B, as the invitee, performs the following steps during the on-chain event monitoring phase:

[0149] Step 22, BCC control console B subscribes to the on-chain cross-chain network consortium member invitation event from the global routing chain.

[0150] Step 23, if the invitation event does not belong to the processing of users in the current chain network, ignore it.

[0151] If the invitation event does not belong to the processing of users in the blockchain network corresponding to BCC control console B, ignore this invitation event.

[0152] Step 24, if BCC control console B determines that the invited user does not belong to the current console user, ignore it.

[0153] Step 25, if the invitation event is an event that needs to be processed by the current console user, store this invitation event in the local database.

[0154] Please continue to refer to Figure 6A As shown, organization B, as the invitee, performs the following steps during the invitation event processing phase:

[0155] Step 26, notify the invitee to process the event.

[0156] BCC control console B notifies the invited user bob to process the invitation event.

[0157] Step 27, process the event.

[0158] User bob processes the invitation event by submitting the processing result to BCC control console B.

[0159] Step 28, BCC control console B obtains the processing result, which can be agreeing to join the alliance or refusing to join the alliance.

[0160] Step 29, BCC control console B obtains the corresponding TxID.

[0161] Step 30, BCC control console B puts the invited request processing result, that is, the processing result of the invitation event, on the global routing chain.

[0162] Step 31, BCC control console B receives the TxID (Transaction ID) returned by the routing chain network.

[0163] Step 32, BCC control console B returns the TxID to user bob.

[0164] In step 460, obtain the processing result transaction event triggered by the processing result transaction from the global routing chain, and when it is determined according to the processing result transaction event that the target object agrees to join the target alliance, store the alliance member joining information in the first blockchain of the first blockchain network, where the alliance member joining information is used to indicate that the target object is added to the target alliance.

[0165] The processing result transaction will also trigger a corresponding smart contract event in the global routing chain network, that is, the processing result transaction event.

[0166] Each control console including the current control console has subscribed to the processing result transaction event, so each control console can receive the processing result transaction event, but only the current control console has the right to process the processing result transaction event. The alliance member joining information will also be stored in the first blockchain in the form of a transaction.

[0167] In an embodiment of the present application, the global routing chain includes the digital certificate of the target object, the digital certificate includes the public key of the target object, and the processing result transaction and the processing result transaction event include the signature information generated by the target object based on the private key of the target object for the processing result.

[0168] Figure 10 Shows according to an embodiment of the present application Figure 4 The flowchart of the details of step 460 in the embodiment. Please refer to Figure 10 As shown, step 460 specifically includes the following steps:

[0169] In step 461, obtain the processing result transaction event triggered by the processing result transaction from the global routing chain.

[0170] In step 462, the signature information in the processing result transaction event is verified based on the digital certificate of the target object obtained from the global routing chain.

[0171] The verification can be performed in the following manner: decrypt the signature information using the public key in the digital certificate, compare the processing result in the processing result transaction event with the decryption result of the signature information. If the two are consistent, it indicates that the verification passes; otherwise, it indicates that the verification fails.

[0172] In step 463, in the case where the verification passes, it is determined whether the target object agrees to join the target alliance according to the processing result transaction event.

[0173] In the embodiment of the present application, by verifying the signature information using the digital certificate, it is ensured that the processing result is provided by the target object, enhancing the security of the system.

[0174] In an embodiment of the present application, storing the alliance member joining information in the first blockchain of the first blockchain network includes: sending the alliance member joining information to the first blockchain network so that the blockchain nodes of the first blockchain network store the alliance member joining information in the first blockchain of the first blockchain network when determining that the alliance member joining information is from the control console corresponding to the creator of the target alliance.

[0175] In the embodiment of the present application, the blockchain nodes of the first blockchain network further verify the alliance member joining information, further improving the security and reliability of the system.

[0176] Figure 6B Shows a schematic diagram of the second part of the timing diagram according to an embodiment of the present application. Next, the subsequent solutions of the embodiments of the present application will be introduced in detail. Please refer to Figure 6B As shown in detail in the subsequent solutions of the embodiments of the present application. Please refer to Figure 6B As shown, after step 32, organization A, as the inviter, performs the following steps in the on-chain event monitoring phase:

[0177] Step 33, BCC control console A subscribes to the on-chain cross-chain network alliance member invited processing result event from the global routing chain.

[0178] That is, obtain the processing result transaction event from the global routing chain.

[0179] Step 34, BCC control console A verifies the invited user authorization signature information.

[0180] BCC control console A verifies the signature information based on the digital certificate.

[0181] Step 35, the signature verification fails.

[0182] If the signature verification fails, the process ends.

[0183] Step 36, if the invited user refuses to join the alliance or the on-chain time of the processing result times out, ignore the event.

[0184] Step 37, if the invited user agrees to join the alliance, continue with the subsequent steps.

[0185] Then, Organization A, as the inviter, executes the following steps in the stage of depositing evidence on the chain:

[0186] Step 38, BCC Console A adds the invited members to the alliance.

[0187] BCC Console A requests to store the information of adding alliance members in the form of a transaction in the business chain network 1 corresponding to BCC Console A.

[0188] Step 39, the business chain network 1 determines whether the transaction is initiated by the alliance creator.

[0189] Step 40, if so, the business chain network 1 returns the TxId to BCC Console A.

[0190] Next, Organization A, as the inviter, executes the following steps in the stage of monitoring on-chain events:

[0191] Step 41, BCC Console A obtains the subscribed on-chain alliance member addition information from the business chain network 1.

[0192] Step 42, BCC Console A stores the on-chain alliance member addition information in the local database.

[0193] Then, BCC Console A executes the following steps:

[0194] Step 43, BCC Console A initiates a transaction that the invited user Bob has been successfully added to the alliance to the routing chain network.

[0195] Step 44, BCC Console A receives the TxId returned by the routing chain network.

[0196] Then, Organization B, as the invitee, executes the following steps in the stage of monitoring on-chain events:

[0197] Step 45, BCC Console B subscribes to the information that Bob has been successfully added to the alliance from the global routing chain.

[0198] Step 46, BCC Console B adds the information of successfully joining the cross-network alliance to the local business chain, that is, the business chain network 2.

[0199] Step 47, BCC Console B receives the TxId returned by the business chain network 2.

[0200] Step 48, BCC control console B subscribes from the local service chain, i.e., service chain network 2, to the result information that Bob has successfully joined the cross-network alliance.

[0201] Step 49, BCC control console B stores the obtained result information that Bob has successfully joined the cross-network alliance into the local database.

[0202] In summary, according to the cross-chain invitation method for alliance members provided in the embodiments of the present application, the following beneficial effects can be achieved: Based on a multi-party jointly built routing chain, it is possible to invite and connect users on the control consoles of homogeneous or heterogeneous different blockchains to join the same trusted computing alliance. The user identification data (user unique number, user nickname, user chain identity certificate) on different blockchains will be published to the routing chain, and the cross-chain invitation between multiple different participants in the trusted computing alliance is realized through the coordination of this routing chain.

[0203] The following introduces the device embodiments of the present application, which can be used to execute the cross-chain invitation method for alliance members in the above embodiments of the present application. For the details not disclosed in the device embodiments of the present application, please refer to the embodiments of the cross-chain invitation method for alliance members in the above of the present application.

[0204] Figure 11 The block diagram of the cross-chain invitation device for alliance members according to an embodiment of the present application is shown.

[0205] Refer to Figure 11As shown, the cross-chain invitation device 1100 for alliance members according to an embodiment of the present application includes: an acquisition unit 1110, a construction and storage unit 1120, and an acquisition and storage unit 1130. Among them, the acquisition unit 1110 is used to acquire an alliance invitation request from an alliance creator, and the alliance invitation request is used to invite a target object corresponding to a second blockchain network to join a target alliance created by the alliance creator, and the alliance creator corresponds to a first blockchain network; the construction and storage unit 1120 is used to construct a cross-chain network invitation member transaction according to the alliance invitation request and store the cross-chain network invitation member transaction in the global routing chain, so that a target control console to which the target object belongs can obtain a subscribed cross-chain network invitation member transaction event from the global routing chain, and after receiving a processing result of the target object for the cross-chain network invitation member transaction event, store a processing result transaction constructed according to the processing result in the global routing chain, where the cross-chain network invitation member transaction event is triggered by the cross-chain network invitation member transaction, and the global routing chain is a blockchain in a blockchain network outside the first blockchain network and the second blockchain network; the acquisition and storage unit 1130 is used to obtain a processing result transaction event triggered by the processing result transaction from the global routing chain, and when it is determined according to the processing result transaction event that the target object agrees to join the target alliance, store alliance member joining information in a first blockchain of the first blockchain network, and the alliance member joining information is used to indicate that the target object is added to the target alliance.

[0206] In some embodiments of the present application, based on the foregoing solution, the target control console receives the processing result of the target object for the cross-chain network invitation member transaction event after sending the cross-chain network invitation member transaction event to the target object; the target control console sends the cross-chain network invitation member transaction event to the target object when it is determined according to the cross-chain network invitation member transaction event that processing by a user belonging to the target control console is required.

[0207] In some embodiments of the present application, based on the foregoing solution, the target control console sends the cross-chain network invitation member transaction event to the target object when it is determined according to the cross-chain network invitation member transaction event that the invited target object corresponds to the second blockchain network and that processing by a user belonging to the target control console is required.

[0208] In some embodiments of the present application, based on the foregoing solution, the global routing chain includes the digital certificate of the target object, the digital certificate includes the public key of the target object, the processing result transaction and the processing result transaction event include signature information generated by the target object based on the private key of the target object for the processing result, and the device further includes a signature verification unit; after obtaining the processing result transaction event triggered by the processing result transaction from the global routing chain, the signature verification unit is configured to: verify the signature information in the processing result transaction event based on the digital certificate of the target object obtained from the global routing chain; in the case of successful verification, determine whether the target object agrees to join the target alliance according to the processing result transaction event.

[0209] In some embodiments of the present application, based on the foregoing solution, the alliance invitation request includes the identifier of the target object, the global routing chain further includes the identifiers of each object, and the device further includes a determination unit; before constructing a cross-chain network invitation member transaction according to the alliance invitation request, the determination unit is configured to: determine whether the global routing chain includes the identifier of the target object in the alliance invitation request; wherein, constructing a cross-chain network invitation member transaction according to the alliance invitation request is performed when it is determined that the global routing chain includes the identifier of the target object in the alliance invitation request.

[0210] In some embodiments of the present application, based on the foregoing solution, before determining whether the global routing chain includes the identifier of the target object in the alliance invitation request, the determination unit is configured to: determine whether the target object already belongs to the target alliance; wherein, determining whether the global routing chain includes the identifier of the target object in the alliance invitation request is performed when it is determined that the target object does not belong to the target alliance.

[0211] In some embodiments of the present application, based on the foregoing solution, the device further includes a judgment unit; before determining whether the target object already belongs to the target alliance, the judgment unit is configured to: judge whether the target object has been invited by the alliance creator, wherein, determining whether the target object already belongs to the target alliance is performed when the target object has been invited by the alliance creator.

[0212] In some embodiments of the present application, based on the foregoing solution, the acquisition and storage unit 1130 is configured to: send the alliance member joining information to the first blockchain network, so that the blockchain nodes of the first blockchain network store the alliance member joining information in the first blockchain of the first blockchain network when it is determined that the alliance member joining information is from the console corresponding to the creator of the target alliance.

[0213] In some embodiments of the present application, based on the foregoing solution, the global routing chain is located in a global routing chain network, and the global routing chain network includes multiple nodes; the method is executed by a current control console, and the current control console is one of at least one control console corresponding to the first blockchain network, and the target control console is one of at least one control console corresponding to the second blockchain network. The control consoles corresponding to the first blockchain network and the control consoles corresponding to the second blockchain network can interact with at least one node in the global routing chain network.

[0214] Figure 12 FIG. shows a schematic structural diagram of a computer system of an electronic device suitable for implementing embodiments of the present application.

[0215] It should be noted that Figure 12 The computer system 1200 of the shown electronic device is only an example and should not impose any limitations on the functions and usage scopes of the embodiments of the present application.

[0216] As Figure 12 shown, the computer system 1200 includes a central processing unit (CPU) 1201, which can perform various appropriate actions and processes according to a program stored in a read-only memory (ROM) 1202 or a program loaded from a storage section 1208 into a random access memory (RAM) 1203, such as executing the method described in the above embodiments. In the RAM 1203, various programs and data required for system operation are also stored. The CPU 1201, the ROM 1202, and the RAM 1203 are connected to each other through a bus 1204. An input / output (I / O) interface 1205 is also connected to the bus 1204.

[0217] The following components are connected to the I / O interface 1205: an input section 1206 including a keyboard, a mouse, etc.; an output section 1207 including a cathode ray tube (CRT), a liquid crystal display (LCD), etc. and a speaker, etc.; a storage section 1208 including a hard disk, etc.; and a communication section 1209 including a network interface card such as a LAN (Local Area Network) card, a modem, etc. The communication section 1209 performs communication processing via a network such as the Internet. A drive 1210 is also connected to the I / O interface 1205 as needed. A removable medium 1211 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc. is installed on the drive 1210 as needed so that a computer program read from the same can be installed into the storage section 1208 as needed.

[0218] Specifically, according to an embodiment of the present application, the processes described above with reference to the flowchart can be implemented as a computer software program. For example, an embodiment of the present application includes a computer program product that includes a computer program carried on a computer-readable medium, and the computer program includes program codes for performing the methods shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 1209, and / or installed from the removable medium 1211. When the computer program is executed by a central processing unit (CPU) 1201, various functions defined in the system of the present application are executed.

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

[0220] The flowcharts and block diagrams in the accompanying drawings illustrate the possible architectures, functions, and operations of systems, methods, and computer program products according to various embodiments of the present application. Among them, each block in the flowchart or block diagram can represent a module, a program segment, or a part of code, and the above module, program segment, or part of code contains one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions marked in the blocks may occur in a different order from that marked in the accompanying drawings. For example, two consecutive blocks shown can actually be executed substantially in parallel, and they can sometimes be executed in the reverse order, depending on the functions involved. It should also be noted that each block in the block diagram or flowchart, as well as the combination of blocks in the block diagram or flowchart, can be implemented by a dedicated hardware-based system for performing the specified functions or operations, or can be implemented by a combination of dedicated hardware and computer instructions.

[0221] The units involved in the embodiments of the present application can be implemented in software or in hardware, and the described units can also be provided in a processor. Among them, the names of these units do not constitute a limitation to the unit itself in certain cases.

[0222] As one aspect, the present application also provides a computer-readable medium, which can be included in the electronic device described in the above embodiments; or it can exist alone without being assembled into the electronic device. The above computer-readable medium carries one or more programs, and when the one or more programs are executed by an electronic device, the electronic device implements the methods described in the above embodiments.

[0223] It should be noted that although several modules or units of the device for action execution are mentioned in the above detailed description, such a division is not mandatory. In fact, according to the embodiments of the present application, the features and functions of the two or more modules or units described above can be embodied in one module or unit. Conversely, the features and functions of one module or unit described above can be further divided and embodied by multiple modules or units.

[0224] Through the description of the above embodiments, those skilled in the art can easily understand that the example embodiments described here can be implemented by software or by a combination of software and necessary hardware. Therefore, the technical solutions according to the embodiments of the present application can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (such as a CD-ROM, a USB flash drive, a mobile hard disk, etc.) or on a network, including several instructions to enable a computing device (such as a personal computer, a server, a touch terminal, or a network device, etc.) to execute the methods according to the embodiments of the present application.

[0225] It can be understood that in the specific embodiments of the present application, data related to the invitation process of alliance members is involved. When the above embodiments of the present application are applied to specific products or technologies, user permission or consent is required, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards of relevant countries and regions.

[0226] After considering the specification and practicing the disclosed embodiments here, those skilled in the art will readily conceive of other embodiments of the present application. The present application is intended to cover any variations, uses, or adaptations of the present application, which follow the general principles of the present application and include common general knowledge or conventional technical means in the technical field not disclosed in the present application.

[0227] It should be understood that the present application is not limited to the exact structures described above and shown in the drawings, and various modifications and changes can be made without departing from its scope. The scope of the present application is only limited by the appended claims.

Claims

1. A cross-chain invitation method for alliance members, characterized in that, The method includes: Obtaining a coalition invitation request from a coalition creator, where the coalition invitation request is used to invite a target object corresponding to a second blockchain network to join a target coalition created by the coalition creator, and the coalition creator corresponds to a first blockchain network; Constructing a cross-chain network invitation member transaction according to the coalition invitation request, and storing the cross-chain network invitation member transaction in a global routing chain, so that a target control console to which the target object belongs obtains a subscribed cross-chain network invitation member transaction event from the global routing chain, and after receiving a processing result of the target object for the cross-chain network invitation member transaction event, stores a processing result transaction constructed according to the processing result in the global routing chain, where the cross-chain network invitation member transaction event is triggered by the cross-chain network invitation member transaction, and the global routing chain is a blockchain in a blockchain network outside the first blockchain network and the second blockchain network; Obtaining a processing result transaction event triggered by the processing result transaction from the global routing chain, and when it is determined according to the processing result transaction event that the target object agrees to join the target coalition, storing coalition member joining information in a first blockchain of the first blockchain network, where the coalition member joining information is used to indicate that the target object is added to the target coalition.

2. The cross-chain invitation method for alliance members according to claim 1, wherein, The target control console receives the processing result of the target object for the cross-chain network invitation member transaction event after sending the cross-chain network invitation member transaction event to the target object; the target control console sends the cross-chain network invitation member transaction event to the target object when it is determined according to the cross-chain network invitation member transaction event that processing by a user belonging to the target control console is required.

3. The cross-chain invitation method for alliance members according to claim 2, wherein The target control console sends the cross-chain network invitation member transaction event to the target object when it is determined according to the cross-chain network invitation member transaction event that the invited target object corresponds to the second blockchain network and that processing by a user belonging to the target control console is required.

4. The cross-chain invitation method for alliance members according to claim 1, wherein The global routing chain includes a digital certificate of the target object, the digital certificate includes a public key of the target object, and the processing result transaction and the processing result transaction event include signature information generated by the target object based on a private key of the target object for the processing result; After obtaining the processing result transaction event triggered by the processing result transaction from the global routing chain, the method further includes: Verifying the signature information in the processing result transaction event based on the digital certificate of the target object obtained from the global routing chain; When the verification is passed, determining whether the target object agrees to join the target coalition according to the processing result transaction event.

5. The cross-chain invitation method for alliance members according to claim 1, characterized in that The coalition invitation request includes an identifier of the target object, and the global routing chain further includes identifiers of each object; before constructing a cross-chain network invitation member transaction according to the coalition invitation request, the method further includes: Determine whether the global routing chain includes the identifier of the target object in the alliance invitation request; wherein, constructing a cross-chain network invitation member transaction according to the alliance invitation request is performed when it is determined that the global routing chain includes the identifier of the target object in the alliance invitation request.

6. The cross-chain invitation method for alliance members according to claim 5, wherein Before determining whether the global routing chain includes the identifier of the target object in the alliance invitation request, the method further includes: Determine whether the target object already belongs to the target alliance; wherein, determining whether the global routing chain includes the identifier of the target object in the alliance invitation request is performed when it is determined that the target object does not belong to the target alliance.

7. The cross-chain invitation method for alliance members according to claim 6, wherein Before determining whether the target object already belongs to the target alliance, the method further includes: Judge whether the target object has been invited by the alliance creator, wherein, determining whether the target object already belongs to the target alliance is performed when the target object has been invited by the alliance creator.

8. The cross-chain invitation method for alliance members according to claim 1, characterized in that, The storing the alliance member joining information into the first blockchain of the first blockchain network includes: Sending the alliance member joining information to the first blockchain network so that the blockchain nodes of the first blockchain network store the alliance member joining information into the first blockchain of the first blockchain network when it is determined that the alliance member joining information is from the console corresponding to the creator of the target alliance.

9. The cross-chain invitation method for alliance members according to any one of claims 1-8, characterized in that The global routing chain is located in a global routing chain network, and the global routing chain network includes multiple nodes; the method is executed by the current console, the current console is one of at least one console corresponding to the first blockchain network, the target console is one of at least one console corresponding to the second blockchain network, and the console corresponding to the first blockchain network and the console corresponding to the second blockchain network can interact with at least one node in the global routing chain network.

10. A cross-chain invitation device for alliance members, characterized in that, The device includes: An obtaining unit, configured to obtain an alliance invitation request from an alliance creator, where the alliance invitation request is used to invite a target object corresponding to a second blockchain network to join a target alliance created by the alliance creator, and the alliance creator corresponds to a first blockchain network; A constructing and storing unit, configured to construct a cross-chain network invitation member transaction according to the alliance invitation request, and store the cross-chain network invitation member transaction into the global routing chain, so that the target console to which the target object belongs obtains a subscribed cross-chain network invitation member transaction event from the global routing chain, and after receiving the processing result of the target object for the cross-chain network invitation member transaction event, stores a processing result transaction constructed according to the processing result into the global routing chain, wherein, the cross-chain network invitation member transaction event is triggered by the cross-chain network invitation member transaction, and the global routing chain is a blockchain in a blockchain network outside the first blockchain network and the second blockchain network; An acquisition and storage unit is configured to acquire a processing result transaction event triggered by the processing result transaction from the global routing chain, and store membership addition information of the alliance in the first blockchain of the first blockchain network when it is determined, according to the processing result transaction event, that the target object agrees to join the target alliance, where the membership addition information of the alliance is used to indicate that the target object is added to the target alliance.

11. 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 cross-chain invitation method for alliance members as described in any one of claims 1 to 9.

12. An electronic device, characterized in that, Comprising: One or more processors; A storage device for storing one or more programs, which, when executed by the one or more processors, cause the one or more processors to implement the cross-chain invitation method for alliance members as described in any one of claims 1 to 9.

13. A computer program product, characterized in that, The computer program product includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to execute the cross-chain invitation method for alliance members as described in any one of claims 1 to 9.

Images