CN114298694A

CN114298694A - Block chain service platform management method and device, computer equipment and storage medium

Info

Publication number: CN114298694A
Application number: CN202111674272.6A
Authority: CN
Inventors: 闫核心; 张顺康
Original assignee: Shenzhen Mingzhu Technology Co ltd
Current assignee: Shenzhen Mingzhu Technology Co ltd
Priority date: 2021-12-31
Filing date: 2021-12-31
Publication date: 2022-04-08

Abstract

The application relates to a cross-block chain service platform management method, a cross-block chain service platform management device, computer equipment and a storage medium. The method comprises the following steps: the method comprises the steps of obtaining an operation instruction sent by at least one block chain account of a first platform, obtaining a service logic corresponding to the operation instruction, wherein the service logic belongs to the first platform, determining a alliance chain for managing communication between the first platform and a second platform when detecting that the service logic is related to the second platform, generating authority verification information corresponding to the service logic, sending the authority verification information to the second platform through the alliance chain, and obtaining a verification result of the second platform on the authority verification information through the alliance chain. By adopting the method, the business logic can be executed according to the auditing result, and because the alliance chain controls the communication process between the first platform and the second platform, various data of different platforms can be compatible, and the block chain service platforms are connected, thereby facilitating the information interaction.

Description

Block chain service platform management method and device, computer equipment and storage medium

Technical Field

The present application relates to the field of blockchain technologies, and in particular, to a method and an apparatus for managing a service platform across blockchains, a computer device, a storage medium, and a computer program product.

Background

With the development of a block chain technology, a BaaS platform (BaaS), namely "block chain as a Service", appears, which means that a block chain framework is combined with a cloud computing platform, and the advantages of high availability and convenience in expansion of a cloud Service infrastructure are utilized. The BaaS platform and other block chain service platforms provide efficient, high-performance and scalable block chain ecological environment and ecological matching service for developers to buy, so that a novel business scheme for helping enterprises to simplify operation flows is formed.

Most of current block chain service platforms are constructed based on a multi-organization mode, organization information is stored in a centralized mode, and scheduling and communication are carried out through a centralized platform. The information interaction in the block chain is very convenient to realize. However, when each organization belongs to different block chain service platforms, information interaction is extremely inconvenient, and information interaction of the block chain is difficult.

Disclosure of Invention

In view of the foregoing, it is desirable to provide a method, an apparatus, a computer device, a computer readable storage medium, and a computer program product for managing a cross-block chain service platform, which can implement efficient information interaction.

In a first aspect, the present application provides a method for managing a blockchain service platform, where the method includes:

acquiring an operation instruction sent by at least one block chain account of a first platform, and acquiring a service logic corresponding to the operation instruction;

determining a target block chain for managing communication and communication authority between the first platform and the second platform if the business logic is detected to be related to the second platform;

generating authority checking information corresponding to the business logic, and sending the authority checking information to the second platform through the target block chain, wherein the first platform and the second platform are both block chain service platforms;

and acquiring an auditing result of the second platform on the permission auditing information through the target block chain, and executing the service logic according to the auditing result.

In one embodiment, the determining a target block chain for managing communication between the first platform and the second platform if the service logic detecting the operation instruction is associated with the second platform includes:

determining a service requirement corresponding to the operation instruction based on the service logic;

and determining the target block chain if the service requirement is detected to correspond to the service function of the second platform.

In one embodiment, the detecting that the service requirement corresponds to a service function of the second platform, determining the target block chain includes:

determining the authority level corresponding to the service logic;

and if the permission level reaches a preset range, determining a target block chain corresponding to the service logic, wherein the target block chain is used for storing permission verification information and verification results between the first platform and the second platform and process information used for generating the verification results.

In one embodiment, the target block chain corresponds to a first preset data format and a second preset data format, and the generating of the permission check information corresponding to the service logic includes:

determining a platform authority auditing function in the service logic, wherein the platform authority auditing function is used for acquiring the auditing result, and the auditing result is used for judging whether the second platform has communication authority corresponding to the first platform;

converting the platform permission auditing function based on the first preset data format to obtain a converted platform permission auditing function;

acquiring a requirement to be audited corresponding to the second platform from the operation instruction;

converting the operating instruction corresponding to the requirement to be audited of the second platform based on the second preset data format to obtain the converted requirement to be audited;

and combining the converted requirements to be audited with the converted platform permission audit function to obtain the permission audit information.

In one embodiment, the second platform is multiple, and the generating of the audit result includes:

the plurality of second platforms respectively audit the authority audit information and generate audit signatures corresponding to the second platforms;

and calculating the number of the auditing signatures, and determining the auditing result based on the range of the number.

In one embodiment, the executing the business logic according to the audit result includes: the target block chain generates a corresponding block according to the service logic corresponding to the block chain account in the first platform;

and the target block chain generates a block of the audit result corresponding to the block chain account used for generating the audit result in the second platform.

In one embodiment, the target block chain is a federation chain, and the executing the service logic according to the audit result includes:

based on the service logic, connecting the first platform to a alliance chain where the second platform is located; alternatively, the first and second electrodes may be,

and generating a federation chain between the first platform and the second platform based on the business logic.

In a second aspect, an apparatus for managing a service platform across block chains, the apparatus comprising:

the instruction acquisition module is used for acquiring an operation instruction sent by at least one block chain account of a first platform and acquiring a service logic corresponding to the operation instruction;

a target block chain determining module, configured to determine a target block chain for managing communication and communication permission between the first platform and a second platform if the service logic is detected to be related to the second platform, where the first platform and the second platform are both block chain service platforms;

the auditing module is used for generating authority auditing information corresponding to the business logic and sending the authority auditing information to the second platform through the target block chain;

and the execution module is used for acquiring an audit result of the second platform on the permission audit information through the target block chain, and the first platform executes the service logic according to the audit result.

In a third aspect, the present application also provides a computer device. The computer device comprises a memory storing a computer program and a processor implementing the following steps when executing the computer program:

determining a target block chain for managing communication and communication authority between a first platform and a second platform when the business logic is detected to be related to the second platform, wherein the first platform and the second platform are both block chain service platforms;

generating authority checking information corresponding to the business logic, and sending the authority checking information to the second platform through the target block chain;

In a fourth aspect, the present application further provides a computer-readable storage medium. The computer-readable storage medium having stored thereon a computer program which, when executed by a processor, performs the steps of:

In a fifth aspect, the present application further provides a computer program product. The computer program product comprising a computer program which when executed by a processor performs the steps of:

The method, the device, the computer equipment, the storage medium and the computer program product for managing the cross-block-chain service platform acquire an operation instruction sent by at least one block chain account of a first platform, acquire a business logic corresponding to the operation instruction, wherein the business logic belongs to the first platform, even if the block chain account does not have knowledge in programming, the data processing related to the block chain can be realized, and when the business logic is detected to be related to a second platform, a target block chain for managing communication and communication authority between the first platform and the second platform is determined, authority checking information corresponding to the business logic is generated, the authority checking information is sent to the second platform through the target block chain, the checking result of the authority checking information by the second platform is acquired through the target block chain, the business logic is executed according to the checking result, because the target block chain controls the communication process between the first platform and the second platform, various data of different block chain service platforms can be compatible, and two information isolated islands are connected, so that information interaction is facilitated. Therefore, when the target block chain is a alliance chain, the alliance information among the platforms is managed through the alliance chain, the interaction of the information of different Baas platforms can be achieved only through the interface of the alliance chain, and alliance management among the different Baas platforms is achieved.

Drawings

FIG. 1 is a diagram of an application environment for a method for cross-blockchain service platform management in one embodiment;

FIG. 2 is a flowchart illustrating a method for managing a service platform across block chains according to an embodiment;

FIG. 3 is a flow diagram that illustrates the determination of a federation chain, in one embodiment;

FIG. 4 is a flow diagram illustrating the determination of a federation chain in another embodiment;

FIG. 5 is a flowchart illustrating the generation of permission audit information in one embodiment;

FIG. 6 is a schematic flow chart illustrating the generation of audit results in one embodiment;

FIG. 7 is a flow diagram illustrating the execution of business logic in one embodiment;

FIG. 8 is a flow diagram illustrating the execution of business logic in another embodiment;

FIG. 9 is a flow diagram illustrating joining a federation chain in one embodiment;

FIG. 10 is a schematic flow chart illustrating joining a federation chain in another embodiment;

FIG. 11 is a block diagram of an apparatus for cross blockchain service platform management in one embodiment;

FIG. 12 is a diagram illustrating an internal structure of a computer device according to an embodiment.

Detailed Description

In order to make the objects, technical solutions and advantages of the present application more apparent, the present application is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present application and are not intended to limit the present application.

The management method for the service platform across block chains provided by the embodiment of the application can be applied to the application environment shown in fig. 1. Wherein the terminal 102 communicates with the server 104 via a network. The data storage system may store data that the server 104 needs to process. The data storage system may be integrated on the server 104, or may be located on the cloud or other network server. The terminal 102 may be, but not limited to, various personal computers, notebook computers, smart phones, tablet computers, internet of things devices and portable wearable devices, and the internet of things devices may be smart speakers, smart televisions, smart air conditioners, smart car-mounted devices, and the like. The portable wearable device can be a smart watch, a smart bracelet, a head-mounted device, and the like. The server 104 may be implemented as a stand-alone server or as a server cluster comprised of multiple servers. The scheme provided by the embodiment of the application can be realized by the terminal 102; or cooperatively implemented by the terminal 102 and the server 104, wherein both the terminal 102 and the server 104 may be real blockchain nodes, and the terminal 102 and/or the server 104 may also be referred to as virtual blockchain nodes.

In one embodiment, as shown in fig. 2, a method for managing a blockchain service platform is provided, which is described by taking the method as an example applied to the server 104 in fig. 1, and includes the following steps:

step 202, acquiring an operation instruction sent by at least one block chain account of the first platform, and acquiring a service logic corresponding to the operation instruction.

The first platform refers to one or a group of blockchain service platforms for managing blockchains. The blockchain service platform may be configured to manage tasks of blockchain data within the platform, where the tasks may be operation information such as generation, import, and/or export of the blockchain data. The task may also be blockchain permission control information, where the blockchain permission control information includes permission control for access by blockchain nodes and/or permission control for operation of blockchain accounts. Specifically, the first platform may be a block chain as a Service platform (BaaS), or may be another block chain Service platform for deploying a block chain such as a public chain, a federation chain, or a private chain.

One or more blockchain accounts exist in the first platform, after the blockchain accounts send out operation instructions through blockchain link points in the first platform, authority requirements are determined through service logic in the operation instructions, judgment is carried out based on the authority requirements and authority levels corresponding to the blockchain accounts, if the authority levels are higher than or equal to the authority requirements, the service logic can be directly executed, and if the authority levels are lower than the authority requirements, authority acquisition can be carried out. In the process of acquiring the authority, if the authority requirement only relates to the blockchain in the first platform, the related function across the blockchains can be directly enabled to acquire the corresponding authority. It will be appreciated that the blockchains within the first platform form a blockchain network under which individual blockchains may communicate by means of the first platform.

For the blockchain account number of the first platform, it may correspond to various organizations, which establish corresponding blockchains by means of the first platform, and these blockchains may be federation chains. It will be appreciated that these federation chains are generated based on business logic in the first platform, and even an organization that has no blockchain development capability at all, may rely on the first platform to create its own blockchain.

Step 204, detecting that the service logic is related to the second platform, determining a target block chain for managing communication and communication authority between the first platform and the second platform, wherein both the first platform and the second platform are block chain service platforms.

The relevance of the service logic to the second platform can be determined by a variety of means. After execution of the service logic, if certain request instructions or operation instructions are sent to the second platform, it may be determined that the service logic is associated with the second platform; if the execution result of the business logic relates to certain rights of the second platform, the business logic can be determined to be related to the second platform; if the execution result of the service logic establishes an information channel between the first platform and the second platform, it can be determined that the service logic is related to the second platform.

Having determined that the business logic is associated with the second platform, a target blockchain for managing communications between the first platform and the second platform may solve a number of aspects. On one hand, the first platform and the second platform may belong to different block chain networks, and data structures or algorithms such as data formats, language versions, functional relationships and the like in the first platform and the second platform are likely to have great differences, so that the compatibility problem of heterogeneous data can be solved by using the target block chain for management. On the other hand, since the first platform and the second platform may belong to different organizations and permissions between the organizations are irrelevant, the target blockchain may provide zero-knowledge proof to facilitate information interaction between the two organizations, and if the target blockchain is used as a federation chain, privacy and other factors of the two organizations may be considered.

The first platform and the second platform are in a relative relationship, and the relative relationship has a plurality of angles. If the first platform is a party actively initiating communication, the second platform is a party passively accepting communication; if the first platform initiates a party for some approval, the second platform is the party for approval. It is understood that the correspondence between the first platform and the second platform may be transformed according to instructions issued by the blockchain account numbers in the platforms, and may be one-to-one or one-to-many. The block chain service platform may be a BaaS platform, a SaaS platform, or the like.

For the communication authority between the first platform and the second platform, which has a corresponding relationship with the alliance members, if the communication authority exists, the block chain accounts of the same alliance are respectively positioned on the two platforms, and the block chain accounts can carry out service logics such as communication, quitting and the like across the platforms; if the block chain account has no communication authority, the block chain account belongs to a candidate coalition member or an applicant of the coalition member, and mainly executes business logic of joining a coalition, creating a coalition and the like.

In a specific embodiment, the organization 1 in the first platform calls the BaaS API to parse the request data body and send the request data body to the federation control module, and executes the service logic corresponding to joining the federation chain and exiting the federation chain, where any service logic notifies the organization member of the BaaS federation in the first platform to perform signature approval through the BaaS API, and notifies the organization member of another BaaS platform in the federation to perform signature approval through an approval interface provided by the monitoring management chain through the federation chain, so that step 206 needs to be executed.

And step 206, generating authority checking information corresponding to the business logic, and sending the authority checking information to the second platform through the target block chain.

The permission audit information can be obtained after the business logic is operated, or can be generated by calculation based on some data corresponding to the business logic. For example, when the service logic is used to obtain the signature information, some data to be checked is obtained from the operation instruction, and after the data to be checked is combined with the service logic, the authority check information is obtained.

The target block chain sends the authority verification information to the second platform, on one hand, the safety of the information is ensured through properties of decentralization, non-tampering and the like of the block chain, and on the other hand, the convenient interaction of various data is realized, so that the problems of data compatibility and the like are avoided. For example: when the business logic relates to an operation instruction of a certain data object, and the data object only exists in the first platform, if the data object is converted through the target block chain, the data object is converted into a general data type corresponding to the target block chain, and the general data type is sent to the second platform, the compatibility problem can not occur. For another example, a certain service logic is a dedicated service logic under the first platform, and needs to rely on the environmental data or some hardware of the first platform to guarantee its operation result, and the target block chain may convert the dedicated service logic, convert the dedicated service logic into a general data function corresponding to the target block chain, and after sending the general data function to the second platform, it may ensure the normal operation of the second platform.

In a specific embodiment, after the approval of the organization signatures is completed, the alliance chain configuration management module of the first platform generates configuration information corresponding to the established alliances, and performs uplink storage on the alliance information through the management chain interaction module of the first platform, so step 208 is performed.

And 208, acquiring an auditing result of the second platform on the authority auditing information through the target block chain, and executing service logic according to the auditing result.

The audit result is obtained through the target block chain, on one hand, the audit results of a plurality of nodes can be summarized by utilizing a consensus mechanism of the block chain, elements such as non-falsification, safety and the like can be guaranteed, and on the other hand, the compatibility problem of data can be guaranteed. It can be understood that some authorization information audits involve a plurality of second platforms, and a large number of block chain accounts exist in each second platform, so that it is necessary to transmit the effect of the audit result through the target block chain.

The auditing result can be whether the authority auditing information passes the auditing, and various modes are available for judging whether the auditing information passes the auditing. After the predetermined number of nodes achieve consensus, it can be determined that the audit is passed; after the account corresponding to a certain primary node determines that the audit is passed, it may also be determined that the audit is passed.

The business logic can be executed after the audit is passed, and can also be executed after the audit is not passed. For example: and if a certain service logic representation is added into the alliance chain of a certain second platform, when the consensus mechanism in the alliance chain is checked, and after the checking is passed, the service logic is executed. If a business logic representation returns some prompt message if the audit is not passed, the business logic is executed after the audit is not passed.

Executing business logic according to the auditing result, wherein the business logic can be three-aspect events, namely an event of the first platform, an event of the second platform and an event of the target block chain;

in the first platform, when the approval of a plurality of organization signatures is completed, the alliance configuration management module generates configuration information corresponding to the established alliances, the alliance information is subjected to uplink storage through the management chain interaction module, and the infrastructure module is called to update corresponding nodes according to the generated alliance configuration information.

In the second platform, the service logic request data body is analyzed and sent to the alliance control module, the alliance logic adding is executed, the configuration information corresponding to the alliance is updated, the updated alliance information is uplink stored, and the corresponding node is updated according to the generated alliance configuration information.

In the target block chain, the operation records of the alliance are recorded, and the life cycle of the alliance is completely saved.

In the management method of the cross-block chain service platform, an operation instruction sent by at least one block chain account number of a first platform is obtained, a business logic corresponding to the operation instruction is obtained, the business logic belongs to the first platform, even if the block chain account number does not have knowledge in programming, data processing related to the block chain can be realized, if the business logic is detected to be related to a second platform, a target block chain for managing communication between the first platform and the second platform is determined, authority auditing information corresponding to the business logic is generated, the authority auditing information is sent to the second platform through the target block chain, the auditing result of the second platform on the authority auditing information is obtained through the target block chain, the business logic is executed according to the auditing result, because the target block chain controls the communication process between the first platform and the second platform, various data of different platforms can be compatible, the block chain service platforms are connected, so that information interaction is facilitated. In addition, when the target block chain is a alliance chain, the alliance information among the platform is managed through the alliance chain, and only an interface of the alliance chain is needed, so that the interaction of the information of different BaaS platforms can be achieved, and alliance management among the different BaaS platforms is achieved.

In one embodiment, as shown in fig. 3, when the service logic of the operation instruction is detected to be related to the second platform, determining a target block chain for managing communication between the first platform and the second platform includes:

step 302, determining a service requirement corresponding to the operation instruction based on the service logic.

For the process of determining the service requirement, the process may be determined according to a mapping relationship between the operation instruction and the service logic in the first platform, or may be performed by performing a certain conversion on the operation instruction which is easy to be understood by the user through a conversion function integrated in the first platform to obtain a preset service logic in the first platform, where the preset service logic may correspond to the preset service requirement in the first platform to obtain the service requirement corresponding to the operation instruction. For example, when an operation instruction of a user is "create target block chain", after the operation instruction is input to the first platform, the first platform performs a certain operation on the operation instruction according to the service logic to obtain a service requirement corresponding to the operation instruction.

Step 304, determining the target block chain if the service requirement is detected to correspond to the service function of the second platform.

The correspondence between the service requirement and the service function is a generic correspondence, and the correspondence may be embodied in a square, may be embodied in a service function in which the service requirement points to any block chain account in the second platform, may be embodied in a requirement in which the service requirement is a requirement for granting an authority by the second platform, and may also be embodied in data transferability. For example, when an organization belonging to the first platform and the second platform respectively issues a communication request, it may be determined that the service requirement corresponds to the service function; for another example, if data interaction is required between the first platform and the second platform, it may be determined that the service requirement corresponds to a service function of the second platform.

After determining the correspondence of the business requirements to the business functions, a target blockchain may be determined. Optionally, the first platform and/or the second platform may generate the target block chain, and the first platform and/or the second platform may also be connected to the target block chain, which is a kind of target block chain in most cases for the target block chain itself, so as to guarantee privacy of each account number in the first platform and the second platform.

In this embodiment, the service requirement is determined through the service logic in the first platform, and because the service requirement does not relate to the bottom logic of each platform, the data heterogeneous problem or the data environment between different platforms does not need to be considered, the service function corresponding to the service requirement is determined across platforms, and then the target block chain is determined based on the service function, so that data interaction between multiple platforms is realized.

In one embodiment, as shown in fig. 4, detecting that the service requirement corresponds to a service function of the second platform, determining the target block chain includes:

step 402, determining the authority level corresponding to the service logic.

And if the authority level corresponding to the service logic is out of the preset range, the service logic does not relate to information interaction of multiple platforms, and a target block chain does not need to be determined. For example, if the service logic is used to log in to the first platform, the target block chain does not need to be determined; if the service logic is used for establishing the block chain in the first platform, the target block chain does not need to be determined; if the business logic corresponds to a data refresh command in the first platform, the target block chain does not need to be determined.

And step 404, if the permission level reaches a preset range, determining a target block chain corresponding to the service logic, wherein the target block chain is used for storing permission verification information and verification results between the first platform and the second platform and process information used for generating the verification results.

The process information for generating the audit result may be a signature process issued by some account numbers in the second platform, and the process of generating the audit result is based on a consensus mechanism.

In an optional embodiment, the service logic corresponding to the step 402 and the step 404 is a logic corresponding to federation information interaction, and is used for verifying the authority of the organization, if no authority exists, the authority application transaction is initiated, and after the authority owner agrees, the designated information can be obtained; and defines the standard format and method of alliance information interaction.

In the embodiment, the permission level corresponding to the service logic is detected, so that the target block chain can be prevented from generating too many blocks, and the overall calculation amount is reduced; the authority verification information, the verification result and the process information for generating the verification result between the first platform and the second platform are stored through the target block chain, so that information evidence can be stored, and the reliability and the safety of data are guaranteed.

In one embodiment, as shown in fig. 5, the target block chain corresponds to a first predetermined data format and a second predetermined data format, and the first predetermined data format and the second predetermined data format are both data formats specified by the target block chain and are used for converting data output by the first platform into the data formats. The first preset data format is used for determining a data type or a function type corresponding to a platform permission auditing function, and the second preset data format is used for determining a data type or a function type corresponding to a requirement to be audited; for specific format requirements, the first preset data format and the second preset data format may have the same data type or different data types. It can be understood that the first preset data format and the second preset data format are embodied in a federation information interaction standard format and method in a block chain, and are also embodied in a standard format and method for interaction between a BaaS platform and a management chain defined by a management chain interaction module.

Generating the authority verification information corresponding to the service logic comprises the following steps:

step 502, determining a platform permission auditing function in the service logic, wherein the platform permission auditing function is used for acquiring an auditing result, and the auditing result is used for judging whether the first platform has the communication permission with the second platform or not, or the auditing result is used for judging whether the second platform has the communication permission with the first platform or not.

If the platform permission auditing condition or the platform permission auditing event is responded, the platform permission auditing function is executed. The platform permission auditing function is a function for transmitting a platform permission auditing result, belongs to the business logic of the first platform, and is called only when the second platform runs, so that the platform permission auditing result can be timely and accurately obtained, and whether the first platform has the communication permission corresponding to the second platform or not is judged. It can be understood that when the first platform has the communication right with the second platform, the blockchain account number in the first platform can communicate with the blockchain account number in the second platform; when the second platform has the communication right with the first platform, the block chain account in the second platform can communicate with the block chain account in the first platform.

Step 504, based on the first preset data format, the platform permission auditing function is converted, and the converted platform permission auditing function is obtained.

The platform permission auditing function has the same service function no matter whether format conversion is carried out or not, and only the converted platform permission auditing function can be used for carrying out cross-platform information transmission so as to be convenient for receiving and sending information by block chain accounts among different platforms.

Step 506, obtaining the requirement to be audited corresponding to the second platform from the operation instruction.

And step 508, converting the operation instruction corresponding to the to-be-audited requirement of the second platform based on the second preset data format to obtain the converted to-be-audited requirement.

Whether format conversion is carried out on the requirements to be audited or not, the corresponding business functions are the same, and only the requirements to be audited after conversion are in a second preset data format determined by the target block chain, so that the requirements to be audited after conversion are convenient for cross-platform information transmission, and information receiving and sending are convenient for block chain accounts among different platforms.

And 510, combining the converted to-be-audited requirement with the converted platform permission audit function to obtain permission audit information.

In this embodiment, the auditing result is obtained through the platform authority auditing function, so that the data can be reused for multiple times, the function required by the requirement to be audited is determined, and the preset data format is determined by the target block chain, so that cross-platform data transceiving is realized, information interaction is performed on block chain accounts among multiple platforms, and the function is responsible for storing uplink of the standard format information of the alliance, and completely storing the operation record of the alliance and the life cycle of the alliance.

In an embodiment, if there is one second platform, after determining the block chain account number of the second platform corresponding to the permission review information, signing the permission review information through each block chain account number of the second platform, so as to achieve authorization of the permission review information. And if the audit is not passed, returning a prompt message.

In one embodiment, as shown in fig. 6, the second platform is multiple, and the generating of the audit result includes:

step 602, the plurality of second platforms respectively audit the authority audit information, and generate audit signatures corresponding to the second platforms.

The process of checking the permission checking information is a process of checking the permission checking information by each second platform, and may be a process of checking some block chain accounts related to the business logic in each block chain service platform. If the business logic is related to a certain block chain account number in the second platform, the signature generated by the block chain account number is an audit signature of the second platform; if the business logic is related to a certain block chain in the second platform, after the block chain account corresponding to the block chain is audited and agreed, the generated audit signature set is the audit signature of the second platform.

Step 604, calculating the number of the audit signatures, and determining the audit result based on the range of the number of the audit signatures.

The number of the audit signatures may be the number of the audit signatures of the second platform, or the number of the audit signatures generated by each block chain account corresponding to the service logic in each second platform. It is to be understood that the number of audit signatures of the second platform and the number of audit signatures generated by each blockchain account may be different, and the audit result may be generated under different conditions.

In an optional embodiment, steps 602 and 604 occur in the second platform, and the second platform correspondingly monitors each transaction message of the management chain, sends the message to be notified to the event module, and then the event module notifies the service to be authorized to the user page through the API, so that the user can process the service in time and advance the service flow. After obtaining the operation instruction sent by the second platform user, the alliance configuration management module applies the management method of the Baas platform alliance configuration information to manage the configuration file generated in the Baas service, and meanwhile, the infrastructure interaction module defines the standard format and method interacting with the underlying infrastructure.

In this embodiment, the plurality of second platforms respectively perform auditing on the permission audit information, and after the audit signatures are generated, the audit result is determined based on the range of the number of the audit signatures, so as to better adapt to the specific characteristics of the block chain itself and realize the characteristics of decentralization and tamper resistance.

In one embodiment, as shown in fig. 7, executing the business logic according to the audit result includes:

step 702, corresponding to the block chain account number in the first platform, the target block chain generates a corresponding block according to the service logic.

Step 704, the target block chain generates a block of the audit result corresponding to the block chain account for generating the audit result in the second platform.

Step 702, 704 is a process of authority control, which designs a alliance authority control function of an alliance chain, and interacts with an event center module of a Baas platform service through a management chain interaction module after being responsible for authorizing an applicant service; the across-platform block chain account alliance information can be stored on a target block chain through the process of alliance information storage, so that the related operation of alliance can be conveniently carried out; the federation information may correspond to communication rights, among other things, to determine the scope of the federation chain. The block for generating the audit result may be a process of performing uplink storage on the modified federation information, or a process of performing uplink storage on an approval or authorization related event.

In this embodiment, the first platform enables the target block chain to generate a block corresponding to the service logic, and the target block chain generates a block corresponding to the audit result. Therefore, on one hand, the reliability of auditing can be ensured, the interactive information between the first platform and the second platform is more public, and on the other hand, the whole data is controlled, so that the problem caused by data compatibility between the platforms is avoided. In addition, alliance information can be provided through a target block chain, so that each block chain service platform can select whether to join the alliance.

The federation chain where the second platform is located may be a federation chain where the second platform is used as an identifier of the federation chain to determine the federation chain where the second platform is located, or may be a federation chain where the second platform is located with an account of the second platform as an identifier. It will be appreciated that the connection process and the generation process of the federation chain may be simultaneous, as the blockchain account number in the first platform may correspond to the blockchain account number in multiple second platforms. Thus, the specific common logic of service execution (including creating federation, joining federation) is defined.

In this embodiment, the first platform is connected to the alliance chain where the second platform is located or the alliance chain between the first platform and the second platform is created, so that the block chain account in the first platform can conveniently communicate with the block chain account in the second platform, and cross-platform information interaction is achieved on the premise of protecting privacy.

In one embodiment, as shown in fig. 8, the target blockchain is taken as a management chain of an organizational union, and the first platform and the second platform are collectively referred to as a blockchain service platform, and business functions therein are discussed.

Three types of functions of the management chain are as follows:

1. the alliance information interaction function: the system is responsible for reading the information on the management chain and verifying the authority of the organization, if the authority can not be applied for transaction, the designated information can be obtained after the authority owner agrees. And defines the functions of standard format and method for interacting with the alliance information.

2. The alliance information storage function: and the system is responsible for storing the information of the standard format of the alliance on the uplink and completely storing the operation record and the life cycle of the alliance.

3. Alliance authority control function: and the system is responsible for authorizing the service of the application party and interacting with the event center module of the Baas platform service through the management chain interaction module.

In a block chain service platform represented by a BaaS platform, five types of functional modules of a service are as follows:

a management chain interaction module: the system comprises an access identity with a management chain, a standard format and a method for interaction between a BaaS platform and the management chain, monitoring transaction information of each item of the management chain, and sending information needing to be notified to an event module.

An event module: the system is responsible for notifying the service needing authorization to a user page through an API (application programming interface), so that the user can process the service in time and the service flow is promoted.

A alliance control module: the specific logic of service execution (including creating federation, joining federation) is defined.

The alliance configuration management module: a method for managing configuration information of a Baas platform alliance is provided and is responsible for managing configuration files generated in Baas services.

And an infrastructure interaction module for defining a standard format and a method for interacting with the underlying infrastructure.

In an optional embodiment, the blockchain accounts in the blockchain service platforms interact through an internal interface of the platform, and the blockchain service platforms interact through an interface of a management chain for managing cross-platform communication, for example: the method comprises the steps that an organization corresponding to a block chain account in the BaaS platform and an interactive interface of the BaaS platform service are established; the management chain API is an external interface for interaction between the non-native BaaS platform organization and the native BaaS platform management chain, and is authorized to be accessible.

In an alternative embodiment, as shown in fig. 9, in order to more clearly reflect the process of data interaction, taking a federation joined in a federation chain as an example, a flow description is performed on a first blockchain service platform as a main body, which includes the following steps:

1. and the organization in the first platform calls a first platform interface such as a BaasaAPI and the like to analyze the request data body and send the request data body to the alliance control module through the corresponding block chain account number, and the alliance logic is added.

2. And the joining alliance service informs alliance organization members in the first platform such as the Baas to carry out signature approval through the first platform interface such as the BaaS API, and informs organization members in the second platform such as the Baas to carry out signature approval through an approval interface provided by a monitoring management chain.

3. When the organization signatures in the first platforms are approved, the alliance configuration management module generates configuration information corresponding to the established alliances, and the alliance information is subjected to uplink storage through the management chain interaction module.

4. And calling the infrastructure module to update the corresponding node according to the generated alliance configuration information.

In an alternative embodiment, as shown in fig. 10, in order to reflect the process of data interaction more clearly, taking a federation joined in a federation chain as an example, a flow description is performed on the second blockchain service platform as a main body, which includes the following steps:

1. and the Baas platform as the first platform accesses the alliance information interaction contract to acquire alliance information on the chain.

2. The Baas platform as the first platform executes a transaction, the transaction content is used for authorizing an application party, and a callback function is provided when the signature is completed.

3. And the management chain interaction module monitors that the transaction needs permission of a plurality of persons, calls the event module to inform the alliance organization members to carry out signature approval, and informs the organization members of the Baas platform serving as a second platform in the alliance to carry out signature approval through an approval interface provided by the monitoring management chain.

4. And the management chain sends the request body to a management chain interaction module of the second platform, the management chain interaction module of the second platform analyzes the request data body and transmits the request data body to a alliance control module of the second platform, relevant logic for adding the alliance is executed, and the alliance where the block chain account of the first platform is added to the block chain account of the second platform is determined.

5. And the second platform updates the configuration information corresponding to the alliance and stores the updated alliance information through the uplink of the management chain.

6. And the second platform updates the corresponding node according to the generated alliance configuration information.

Therefore, the ability of establishing alliances among different block chain service platforms can be met; and the information interaction between different block chain service platforms can be met, so that the block chain accounts of different block chain service platforms can exchange information with each other to establish a union. And the ability of tracing the history is provided, and the operation record and the life cycle of the alliance are completely saved. Specifically, the alliance information is stored through the management chain, the management chain provides an external interface, and interaction of information between different Baas platforms is achieved. When a first BaaS platform organization wants to interact with second BaaS information, an authorization identity is obtained through a management chain with a alliance chain function, alliance information is obtained through a management chain alliance information interaction module, and then the alliance authority control module interacts with second BaaS platform services. And directly interacting with the BaaS platform service through the Baas API in each organization in the BaaS platform. A standard exists for the alliance establishment among organizations of different platforms, which is beneficial to the development of alliance chains.

It should be understood that, although the steps in the flowcharts related to the embodiments as described above are sequentially displayed as indicated by arrows, the steps are not necessarily performed sequentially as indicated by the arrows. The steps are not performed in the exact order shown and described, and may be performed in other orders, unless explicitly stated otherwise. Moreover, at least a part of the steps in the flowcharts related to the embodiments described above may include multiple steps or multiple stages, which are not necessarily performed at the same time, but may be performed at different times, and the execution order of the steps or stages is not necessarily sequential, but may be rotated or alternated with other steps or at least a part of the steps or stages in other steps.

Based on the same inventive concept, the embodiment of the present application further provides a device for managing a service platform across block chains, which is used for implementing the method for managing a service platform across block chains. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme described in the above method, so that specific limitations in one or more embodiments of the device for managing a service platform across block chains provided below can be referred to the above limitations on the method for managing the service platform across block chains, and are not described herein again.

In one embodiment, as shown in fig. 11, there is provided a cross-blockchain service platform management apparatus, including: an instruction obtaining module 1102, a target block chain determining module 1104, an auditing module 1106, and an executing module 1108, wherein:

the instruction obtaining module 1102 is configured to obtain an operation instruction sent by at least one block chain account of a first platform, and obtain a service logic corresponding to the operation instruction;

a target block chain determining module 1104, configured to determine a target block chain for managing communication and communication permission between the first platform and a second platform when the service logic is detected to be related to the second platform, where the first platform and the second platform are both block chain service platforms;

an audit module 1106, configured to generate permission audit information corresponding to the service logic, and send the permission audit information to the second platform through the target block chain;

an executing module 1108, configured to obtain, by the target block chain, an audit result of the second platform on the permission audit information, where the first platform executes the service logic according to the audit result.

In one embodiment, the target block chain determining module 1104 includes:

the requirement determining unit is used for determining the service requirement corresponding to the operation instruction based on the service logic;

a target block chain determining unit, configured to determine the target block chain if it is detected that the service requirement corresponds to a service function of the second platform.

In one embodiment, the target block chain determining unit includes:

the permission level determining subunit is used for determining the permission level corresponding to the service logic;

and the target block chain determining subunit is used for determining a target block chain corresponding to the service logic if the permission level reaches a preset range, and the target block chain is used for storing permission verification information and verification results between the first platform and the second platform and process information used for generating the verification results.

In one embodiment, the audit module 1106 includes:

an audit function determining unit, configured to determine, by a first platform, a platform permission audit function in the service logic, where the platform permission audit function is configured to obtain an audit result, and the audit result is used to determine whether the first platform has a communication permission with the second platform, or the audit result is used to determine whether the second platform has a communication permission with the first platform;

a function format conversion unit, configured to convert the platform permission audit function based on the first preset data format to obtain a converted platform permission audit function;

the requirement determining unit is used for acquiring a requirement to be audited corresponding to the second platform from the operation instruction;

the requirement conversion unit is used for converting the operation instruction corresponding to the requirement to be audited of the second platform based on the second preset data format to obtain the converted requirement to be audited;

and the permission auditing information generating unit is used for combining the converted to-be-audited requirement with the converted platform permission auditing function to obtain the permission auditing information.

In one embodiment, the second platform is multiple, and the apparatus further comprises:

the signature generation module is used for respectively auditing the authority auditing information through a plurality of second platforms and generating auditing signatures corresponding to the second platforms;

and the auditing result calculating module is used for calculating the number of the auditing signatures and determining the auditing result based on the range of the number.

In one embodiment, the executing module 1108 includes:

a first execution unit, configured to generate, according to the service logic, a corresponding block by the target block chain corresponding to the block chain account in the first platform;

and the second execution unit is used for generating a block of the audit result by the target block chain corresponding to the block chain account used for generating the audit result in the second platform.

In one embodiment, the target block chain is a federation chain, and the executing module 1108 includes:

a joining federation unit, configured to connect the first platform to a federation chain where the second platform is located based on the service logic; alternatively, the first and second electrodes may be,

and creating a federation unit, which is used for generating a federation chain between the first platform and the second platform based on the service logic.

The modules in the above service platform management device across block chains may be implemented wholly or partially by software, hardware and a combination thereof. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.

In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 12. The computer device includes a processor, a memory, and a network interface connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a cross blockchain service platform management method.

Those skilled in the art will appreciate that the architecture shown in fig. 12 is merely a block diagram of some of the structures associated with the disclosed aspects and is not intended to limit the computing devices to which the disclosed aspects apply, as particular computing devices may include more or less components than those shown, or may combine certain components, or have a different arrangement of components.

In one embodiment, a computer device is further provided, which includes a memory and a processor, the memory stores a computer program, and the processor implements the steps of the above method embodiments when executing the computer program.

In an embodiment, a computer-readable storage medium is provided, on which a computer program is stored which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

In an embodiment, a computer program product is provided, comprising a computer program which, when being executed by a processor, carries out the steps of the above-mentioned method embodiments.

It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, database, or other medium used in the embodiments provided herein may include at least one of non-volatile and volatile memory. The nonvolatile Memory may include Read-Only Memory (ROM), magnetic tape, floppy disk, flash Memory, optical Memory, high-density embedded nonvolatile Memory, resistive Random Access Memory (ReRAM), Magnetic Random Access Memory (MRAM), Ferroelectric Random Access Memory (FRAM), Phase Change Memory (PCM), graphene Memory, and the like. Volatile Memory can include Random Access Memory (RAM), external cache Memory, and the like. By way of illustration and not limitation, RAM can take many forms, such as Static Random Access Memory (SRAM) or Dynamic Random Access Memory (DRAM), among others. The databases referred to in various embodiments provided herein may include at least one of relational and non-relational databases. The non-relational database may include, but is not limited to, a block chain based distributed database, and the like. The processors referred to in the embodiments provided herein may be general purpose processors, central processing units, graphics processors, digital signal processors, programmable logic devices, quantum computing based data processing logic devices, etc., without limitation.

The technical features of the above embodiments can be arbitrarily combined, and for the sake of brevity, all possible combinations of the technical features in the above embodiments are not described, but should be considered as the scope of the present specification as long as there is no contradiction between the combinations of the technical features.

The above-mentioned embodiments only express several embodiments of the present application, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present application. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the concept of the present application, which falls within the scope of protection of the present application. Therefore, the protection scope of the present application shall be subject to the appended claims.

Claims

1. A method for managing a blockchain service platform, the method comprising:

2. The method of claim 1, wherein the determining a target block chain for managing communication between the first platform and the second platform if the service logic detecting the operation instruction is associated with the second platform comprises:

3. The method of claim 2, wherein the detecting that the traffic demand corresponds to a traffic function of the second platform, determining the target blockchain comprises:

determining the authority level corresponding to the service logic;

4. The method according to claim 1, wherein the target block chain corresponds to a first preset data format and a second preset data format, and the generating of the permission check information corresponding to the service logic includes:

determining a platform permission auditing function in the service logic, wherein the platform permission auditing function is used for acquiring the auditing result, and the auditing result is used for judging whether the first platform has the communication permission with the second platform or not, or the auditing result is used for judging whether the second platform has the communication permission with the first platform or not;

5. The method of claim 1, wherein the second platform is multiple, and wherein the generating of the audit result comprises:

and calculating the number of the auditing signatures, and determining the auditing result based on the range of the number of the auditing signatures.

6. The method of claim 1, wherein said executing the business logic according to the audit result comprises:

the target block chain generates a corresponding block according to the service logic corresponding to the block chain account in the first platform;

7. The method according to any one of claims 1 to 6, wherein the target block chain is a federation chain, and the executing the service logic according to the audit result comprises:

connecting the first platform to the alliance chain where the second platform is located based on the business logic; alternatively, the first and second electrodes may be,

and generating the alliance chain between the first platform and the second platform based on the service logic.

8. An apparatus for managing a service platform across block chains, the apparatus comprising:

9. A computer device comprising a memory and a processor, the memory storing a computer program, characterized in that the processor, when executing the computer program, implements the steps of the method of any of claims 1 to 7.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the steps of the method of any one of claims 1 to 7.