CN112734373A

CN112734373A - Information processing method, information processing apparatus, electronic device, and medium

Info

Publication number: CN112734373A
Application number: CN202011642892.7A
Authority: CN
Inventors: 刘捷; 周燕
Original assignee: Industrial and Commercial Bank of China Ltd ICBC
Current assignee: Industrial and Commercial Bank of China Ltd ICBC
Priority date: 2020-12-31
Filing date: 2020-12-31
Publication date: 2021-04-30

Abstract

The utility model provides an information processing method, which comprises the steps of receiving initial information of m asset maintenance requests by using a blockchain node of a blockchain network, wherein the initial information comprises initial maintenance operation and initial maintenance information executed on a business architecture description model, m is a positive integer greater than or equal to 2, determining whether n asset maintenance requests of asset maintenance conflict exist, n is a positive integer greater than or equal to 2 and is less than or equal to m, and if the n asset maintenance requests exist, processing the initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, wherein the target information is used for indicating target maintenance operation and target maintenance information executed on the business architecture description model; and based on the target maintenance information, performing target maintenance operation on the business architecture description model to obtain maintenance result information and storing the maintenance result information in the block link point. An information processing apparatus, an electronic device, and a medium are also provided. The method and the device provided by the disclosure can be applied to the financial field or other fields.

Description

Information processing method, information processing apparatus, electronic device, and medium

Technical Field

The present disclosure relates to the field of blockchain technologies, and in particular, to an information processing method and apparatus based on a blockchain network, an electronic device, and a medium.

Background

The accuracy of the business architecture description model is of great significance for understanding the production and operation conditions of enterprises. With the continuous expansion of large-scale enterprise services, the continuous promotion of each service of the enterprise shows that newly-added services are continuously developed and online while stock services are continuously updated in an iterative manner, so that a service architecture description model also needs to be iterated and promoted synchronously with the iterative updating and the online development of the services. Therefore, it is very important to effectively manage the business architecture description model, and the change condition of the enterprise business architecture and the change condition of the corresponding business can be grasped in time.

At present, the related art also provides some management methods for the business architecture description model. For example, with centralized database management, users browse and use via a B/S (Browser/Server) approach. However, in the course of implementing the disclosed concept, the inventors found that there are at least the following problems in the related art: because agile development and rapid iteration projects are gradually becoming important modes of development and online of a business system, the business architecture description model is updated more frequently and intensively, and if a centralized database is adopted to manage and update the more frequently and intensively business architecture description model, the technical problems of asset update conflict and missing rollback asset completion mechanism inevitably occur, and if the technical problems cannot be effectively solved, the normal operation of each business of an enterprise is seriously influenced.

Disclosure of Invention

In view of the above, in order to at least partially overcome the technical problem that asset update conflicts and missing fallback asset completion mechanisms inevitably occur in the related art that employs a centralized database to manage the business architecture description model that is updated more frequently and intensively. The disclosure provides an information processing method, an information processing device, electronic equipment and a medium based on a block chain network.

In order to achieve the above object, an aspect of the present disclosure provides an information processing method based on a blockchain network, which may include: and receiving initial information of m asset maintenance requests by using the blockchain nodes of the blockchain network, wherein the initial information comprises initial maintenance operation and initial maintenance information executed on the service architecture description model, and m is a positive integer greater than or equal to 2. And determining whether n asset maintenance requests with asset maintenance conflicts exist in the m asset maintenance requests, wherein n is a positive integer greater than or equal to 2 and is less than or equal to m. And if so, processing initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, wherein the target information comprises target maintenance operation and target maintenance information used for indicating the execution of the business architecture description model. And based on the target maintenance information, executing the target maintenance operation on the business architecture description model to obtain maintenance result information, and storing the maintenance result information in the block chain node.

According to an embodiment of the present disclosure, the asset maintenance request may include: and the asset change execution request is used for indicating to execute change operation on the business architecture description model. And/or an asset change rollback request, wherein the asset change rollback request is used for indicating that a change rollback operation is executed on the business architecture description model.

According to an embodiment of the present disclosure, the determining whether there are n asset maintenance requests with an asset maintenance conflict in the m asset maintenance requests may include: and responding to the received m asset maintenance requests, and sending the approval information corresponding to the m asset maintenance requests to an approval node so that the approval node can return an approval result based on the approval information. And receiving the approval result returned by the approval node. And if the approval result shows that the m asset maintenance requests are approved, determining whether n asset maintenance requests with asset maintenance conflict exist in the m asset maintenance requests.

According to an embodiment of the present disclosure, the determining whether there are n asset maintenance requests with an asset maintenance conflict in the m asset maintenance requests may include: and if the m asset maintenance requests comprise m asset change execution requests, determining whether n asset maintenance requests in conflict with asset change exist based on initial information corresponding to the m asset change execution requests. Or if the m asset maintenance requests comprise m asset change rollback requests, determining whether n asset maintenance requests with asset rollback conflict exist based on rollback results corresponding to the m asset change rollback requests. Or if the m asset maintenance requests include p asset change execution requests and q asset change rollback requests, determining whether n asset maintenance requests in asset completion conflict exist based on initial information corresponding to the p asset change execution requests and rollback results corresponding to the q asset change rollback requests, wherein p and q are positive integers, and p + q is m.

According to an embodiment of the present disclosure, the processing the initial information of the n asset maintenance requests to determine the target information corresponding to the m asset maintenance requests may include: and determining whether the asset maintenance conflict is a field information conflict or a semantic information conflict or not according to the initial information of the n asset maintenance requests. If not, merging the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, wherein the merged information comprises merged maintenance operation and merged maintenance information executed on the business architecture description model. And determining the merged information corresponding to the n asset maintenance requests and the initial information of m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

According to an embodiment of the present disclosure, the merging the initial information of the n asset maintenance requests may include: and responding to the n asset maintenance requests, and calling an intelligent contract of the block chain node, wherein the intelligent contract is configured with a merging mechanism. And merging the initial information of the n asset maintenance requests based on the merging mechanism.

According to an embodiment of the present disclosure, the method may further include: if yes, returning the initial information of the n asset maintenance requests. And determining the initial information of the m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

According to an embodiment of the present disclosure, in a case that the asset maintenance request includes an asset change execution request, the performing the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information may include: and executing asset change operation on the business architecture description model based on the merging information corresponding to the n asset maintenance requests to obtain a first change result. And executing asset change operation on the business architecture description model based on the initial information of the m-n asset maintenance requests to obtain a second change result.

According to an embodiment of the present disclosure, in a case that the asset maintenance request includes an asset change rollback request, the performing the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information may include: and executing asset completion operation on the business architecture description model based on the merging information corresponding to the n asset maintenance requests to obtain a first completion result. And executing asset completion operation on the business architecture description model based on the initial information of the m-n asset maintenance requests to obtain a second completion result.

According to any of the above embodiments of the present disclosure, the method may further include: and storing the target information corresponding to the m asset maintenance requests in the blockchain node.

According to an embodiment of the present disclosure, the method may further include: and if the examination and approval result shows that the examination and approval of the m asset maintenance requests are not passed, storing the initial information of the m asset maintenance requests and the examination and approval result in the block chain node.

In order to achieve the above object, another aspect of the present disclosure provides an information processing apparatus based on a blockchain network, which may include: an initial maintenance information receiving module, configured to receive initial information of m asset maintenance requests by using a blockchain node of the blockchain network, where the initial information includes an initial maintenance operation and initial maintenance information performed on a service architecture description model, and m is a positive integer greater than or equal to 2. And the asset maintenance conflict determining module is used for determining whether n asset maintenance requests with asset maintenance conflicts exist in the m asset maintenance requests, wherein n is a positive integer greater than or equal to 2, and n is less than or equal to m. And if the target maintenance information determining module exists, processing initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, wherein the target information comprises target maintenance operation and target maintenance information used for indicating the execution of the business architecture description model. And a maintenance result information processing module, configured to perform the target maintenance operation on the service architecture description model based on the target maintenance information to obtain maintenance result information, and store the maintenance result information in the blockchain node.

According to an embodiment of the present disclosure, the asset maintenance conflict determination module may include: and the examination and approval information sending submodule is used for responding to the received m asset maintenance requests and sending examination and approval information corresponding to the m asset maintenance requests to an examination and approval node so that the examination and approval node can return an examination and approval result based on the examination and approval information. And the approval result receiving submodule is used for receiving the approval result returned by the approval node. And the asset maintenance conflict determination submodule is used for determining whether n asset maintenance requests with asset maintenance conflicts exist in the m asset maintenance requests or not if the approval result shows that the m asset maintenance requests are approved.

According to an embodiment of the present disclosure, the asset maintenance conflict determination submodule may include: and the asset maintenance conflict determining unit is used for determining whether n asset maintenance requests with asset change conflicts exist based on the initial information corresponding to the m asset change execution requests if the m asset maintenance requests comprise the m asset change execution requests. Or a second determining unit of asset maintenance conflict, configured to determine, if the m asset maintenance requests include m asset change rollback requests, whether n asset maintenance requests with asset rollback conflict exist based on a rollback result corresponding to the m asset change rollback requests. Or a third asset maintenance conflict determining unit, configured to determine, if the m asset maintenance requests include p asset change execution requests and q asset change rollback requests, whether there are n asset maintenance requests with an asset completion conflict based on initial information corresponding to the p asset change execution requests and rollback results corresponding to the q asset change rollback requests, where p and q are positive integers, and p + q is m.

According to an embodiment of the present disclosure, the target maintenance information determining module may include: and the asset maintenance conflict determining submodule is used for determining whether the asset maintenance conflict is a field information conflict or a semantic information conflict according to the initial information of the n asset maintenance requests. And if not, merging the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, wherein the merged information comprises merged maintenance operation and merged maintenance information executed on the service architecture description model. And a target maintenance information first determining submodule, configured to determine the merging information corresponding to the n asset maintenance requests and the initial information of m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

According to an embodiment of the present disclosure, the initial information merging sub-module may include: and the intelligent contract calling unit is used for calling the intelligent contracts of the block chain nodes in response to the n asset maintenance requests, wherein the intelligent contracts are configured with a merging mechanism. And the initial information merging unit is used for merging the initial information of the n asset maintenance requests based on the merging mechanism.

According to an embodiment of the present disclosure, the target maintenance information determining module may further include: and the initial information returning submodule is used for returning the initial information of the n asset maintenance requests if the initial information is the same as the initial information of the n asset maintenance requests. And a second target maintenance information determining submodule, configured to determine initial information of the m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

According to an embodiment of the present disclosure, in a case where the asset maintenance request includes an asset change execution request, the maintenance result information processing module may include: and a first change result obtaining module, configured to perform, based on the merging information corresponding to the n asset maintenance requests, an asset change operation on the business architecture description model to obtain a first change result. And a second change result obtaining module, configured to perform, based on the initial information of the m-n asset maintenance requests, an asset change operation on the business architecture description model to obtain a second change result.

According to an embodiment of the present disclosure, in a case where the asset maintenance request includes an asset change rollback request, the maintenance result information processing module may include: and a first completion result obtaining module, configured to perform, based on the merging information corresponding to the n asset maintenance requests, an asset completion operation on the service architecture description model to obtain a first completion result. And the second completion result obtaining module is used for executing asset completion operation on the business architecture description model based on the initial information of the m-n asset maintenance requests to obtain a second completion result.

According to an embodiment of the present disclosure, the apparatus may further include: and the target information storage module is used for storing the target information corresponding to the m asset maintenance requests in the block chain node.

According to an embodiment of the present disclosure, the asset maintenance conflict determination module may be further configured to: and if the examination and approval result shows that the examination and approval of the m asset maintenance requests are not passed, storing the initial information of the m asset maintenance requests and the examination and approval result in the block chain node.

To achieve the above object, another aspect of the present disclosure provides an electronic device including: one or more processors, a memory for storing one or more programs, wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the information processing method based on the blockchain network as described above.

To achieve the above object, another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions for implementing the information processing method based on a blockchain network as described above when the instructions are executed.

To achieve the above object, another aspect of the present disclosure provides a computer program including computer executable instructions for implementing the information processing method based on a blockchain network as described above when the instructions are executed.

Different from the prior art, the information processing method based on the blockchain network provided by the disclosure relates to an asset dynamic storage and processing method based on the business architecture description model asset conflict of the blockchain network, and the method combines the business architecture description model and the blockchain technology, fully utilizes the characteristics of non-tampering and traceability of the blockchain technology, stores the asset dynamic iteration update information of the business architecture description model asset conflict on the blockchain, can realize the traceability of business architecture description model iteration, ensures the timeliness of model results, reduces the conflict of asset maintenance, and ensures the normal operation of each business of an enterprise.

Drawings

For a more complete understanding of the present disclosure and the advantages thereof, reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which:

fig. 1 schematically shows a system architecture of an information processing method and apparatus based on a blockchain network suitable for an embodiment of the present disclosure;

FIG. 2 schematically illustrates a schematic diagram of a business architecture description model of an embodiment of the disclosure;

fig. 3 schematically shows a flow chart of an information processing method based on a blockchain network according to an embodiment of the present disclosure;

FIG. 4 schematically illustrates a flow chart of an information processing method for performing asset changes on a business architecture description model based on a blockchain network according to an embodiment of the present disclosure;

FIG. 5 schematically illustrates a flow chart of an information processing method for performing asset fallback on a business architecture description model based on a blockchain network according to an embodiment of the present disclosure;

fig. 6 schematically shows a block diagram of an information processing apparatus based on a blockchain network according to an embodiment of the present disclosure;

fig. 7 schematically illustrates a schematic diagram of a computer-readable storage medium product adapted to implement the above-described blockchain network-based information processing method according to an embodiment of the present disclosure; and

fig. 8 schematically shows a block diagram of an electronic device adapted to implement the above-described blockchain network-based information processing method according to an embodiment of the present disclosure.

In the drawings, the same or corresponding reference numerals indicate the same or corresponding parts.

It should be noted that the figures are not drawn to scale and that elements of similar structure or function are generally represented by like reference numerals throughout the figures for illustrative purposes.

Detailed Description

Hereinafter, embodiments of the present disclosure will be described with reference to the accompanying drawings. It should be understood that the description is illustrative only and is not intended to limit the scope of the present disclosure. In the following detailed description, for purposes of explanation, numerous specific details are set forth in order to provide a thorough understanding of the embodiments of the disclosure. It may be evident, however, that one or more embodiments may be practiced without these specific details. Moreover, in the following description, descriptions of well-known structures and techniques are omitted so as to not unnecessarily obscure the concepts of the present disclosure.

The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. The terms "comprises," "comprising," and the like, as used herein, specify the presence of stated features, steps, operations, and/or components, but do not preclude the presence or addition of one or more other features, steps, operations, or components. All terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art unless otherwise defined. It is noted that the terms used herein should be interpreted as having a meaning that is consistent with the context of this specification and should not be interpreted in an idealized or overly formal sense.

Where a convention analogous to "at least one of A, B and C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B and C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.). Where a convention analogous to "A, B or at least one of C, etc." is used, in general such a construction is intended in the sense one having skill in the art would understand the convention (e.g., "a system having at least one of A, B or C" would include but not be limited to systems that have a alone, B alone, C alone, a and B together, a and C together, B and C together, and/or A, B, C together, etc.).

Some block diagrams and/or flow diagrams are shown in the figures. It will be understood that some blocks of the block diagrams and/or flowchart illustrations, or combinations thereof, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, or other programmable information processing apparatus, such that the instructions, which execute via the processor, create means for implementing the functions/acts specified in the block diagrams and/or flowchart block or blocks. The techniques of this disclosure may be implemented in hardware and/or software (including firmware, microcode, etc.). In addition, the techniques of this disclosure may take the form of a computer program product on a computer-readable storage medium having instructions stored thereon for use by or in connection with an instruction execution system.

With the continuous expansion of large-scale enterprise services, the services of the enterprise are also continuously promoted, which means that newly-added services are continuously developed and brought on line while stock services are continuously updated in an iterative manner, so that a service architecture description model also needs to be synchronously iterated and promoted along with the iterative updating and development of the services. Therefore, it is very important to effectively manage the business architecture description model, and the change condition of the enterprise business architecture and the change condition of the corresponding business can be grasped in time. Because agile development and rapid iteration projects are gradually becoming important modes of development and online of a business system, the business architecture description model is updated more frequently and intensively, and if a centralized database is adopted to manage and update the more frequently and intensively business architecture description model, the technical problems of asset update conflict and missing rollback asset completion mechanism inevitably occur, and if the technical problems cannot be effectively solved, the normal operation of each business of an enterprise is seriously influenced.

In view of this, embodiments of the present disclosure provide an information processing method and apparatus based on a blockchain network, an electronic device, and a computer-readable storage medium. The information processing method comprises an asset maintenance conflict determining stage and an asset maintenance information processing stage. In the stage of determining the asset maintenance conflict, firstly, receiving initial information of m asset maintenance requests by using a blockchain node of a blockchain network, wherein the initial information comprises initial maintenance operation and initial maintenance information executed on a service architecture description model, m is a positive integer greater than or equal to 2, and then determining whether n asset maintenance requests of asset maintenance conflict exist in the m asset maintenance requests, wherein n is a positive integer greater than or equal to 2, and n is less than or equal to m. If the information exists, entering a processing stage of the asset maintenance information, firstly, processing initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, wherein the target information comprises target maintenance operation and target maintenance information used for indicating execution of the business architecture description model, finally, executing the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information, and storing the maintenance result information in the block link point.

It should be noted that the information processing method and apparatus based on the blockchain network provided by the present disclosure may be used in the financial field, and may also be used in any field other than the financial field. Therefore, the application field of the information processing method and apparatus based on the blockchain network provided by the present disclosure is not limited.

The information processing method and device provided by the disclosure relate to a business architecture description model and a blockchain technology, wherein a blockchain is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism and an encryption algorithm. The Blockchain (Blockchain) is an important concept of the bitcoin, which is essentially a decentralized database, and is used as the underlying technology of the bitcoin, and is a series of data blocks which are generated by using a cryptographic method to be related, wherein each data block contains information of a batch of bitcoin network transactions, and the information is used for verifying the validity (anti-counterfeiting) of the information and generating the next block. The blocks are one storage unit, and all communication information of each block node within a certain time is recorded. The blocks are linked through random hashing (also called hashing algorithm), the next block contains the hash value of the previous block, one block is connected with one block successively along with the expansion of information exchange, and the formed result is called a block chain.

Fig. 1 schematically shows a system architecture 100 of an information processing method and apparatus based on a blockchain network suitable for an embodiment of the present disclosure. It should be noted that fig. 1 is only an example of a system architecture to which the embodiments of the present disclosure may be applied to help those skilled in the art understand the technical content of the present disclosure, and does not mean that the embodiments of the present disclosure may not be applied to other devices, systems, environments or scenarios.

As shown in fig. 1, a system architecture 100 of the information processing method and apparatus based on a blockchain network includes a blockchain network 101, an operation node 1031, an operation node 1032, an approval node 1041, and an approval node 1042.

In the present disclosure, the blockchain network 101 incorporates new blocks into a set of blockchain nodes of a blockchain in a consensus manner. Block chain network 101 may include block link point 1011, block link point 1012, block link point 1013, block link point 1014, block link point 1015, and network 102. Network 102 is used to provide a medium for communication links between a plurality of block-linked nodes. Network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, to name a few.

In this disclosure, a modeler of a service architecture description model may interact with one or more blockchain nodes in the blockchain network 101 through one or more operation nodes in the operation nodes 1031 and the operation nodes 1032, send a model maintenance request of the service architecture description model to a blockchain node, send approval information corresponding to the model maintenance request to an approval node at the blockchain node, after the approval node approves the approval information and returns an approval result, receive the approval result sent by the approval person through one or more approval nodes in the approval node 1041 and the approval node 1042, and store request result information corresponding to the model maintenance request on the blockchain according to the approval result.

It should be understood that the number of blockchain nodes, operational nodes, and approval nodes deployed in fig. 1 is merely illustrative. There may be any number of blockchain nodes, operational nodes, and approval nodes, as desired for an implementation.

FIG. 2 schematically illustrates a schematic diagram of a business architecture description model of an embodiment of the disclosure. As shown in FIG. 2, the business architecture description model 200 may include textual descriptions and associations of the business architecture flow model 201, the product model 202, and the entity model 203 currently used by the enterprise.

The process model 201: the method is characterized in that services in different service fields are divided based on planning, execution and supervision value flows of the services, each value flow is divided into different activities, tasks are decomposed from the activities, the tasks are decomposed into flow descriptions after the steps according to service rules and conditions, and the five levels (service fields, value flows, activities, tasks and steps) are shared.

For example, in a flow model for banking, the business domains generally include, but are not limited to: personal deposits, personal accounts, credit cards, personal loans, and the like. Value streams generally include, but are not limited to: business planning, business preparation, servicing customers, etc. Activities generally include, but are not limited to: making management system, issuing credit card, drawing credit card fund, returning credit card arrears, etc. Tasks generally include, but are not limited to: identifying individual customers, monitoring real-time fraud risk, accepting credit card fund withdrawal applications, settling foreign currencies, and the like. The steps generally include, but are not limited to: calculating the risk bearing capacity grade of the client, auditing the newly-built personal client information, initiating a sensitive examination and approval application, checking an account and the like.

Product model 202 is a set of standard structures that define the products of an enterprise, including product lines, product groups, base products, vendable products, and associations between products.

For example, in the product model of banking, generally include, but are not limited to: debit cards, credit cards, quasi-credit cards, international debit cards, and the like.

The entity model 203 records the service content of each service object, and each service object includes a core entity, a life cycle (state of the core entity), a subordinate entity (describing attribute information of the core entity), an association relationship between service objects, and a constraint condition.

It should be noted that, in addition to the aforementioned process model 201, product model 202, and entity model 203, the business architecture may also include a one-to-one association relationship or a one-to-many association relationship between the components in each level.

It should be noted that fig. 2 is only an example of a model included in a business architecture description model to which the embodiment of the present disclosure may be applied to help a person skilled in the art understand the technical content of the present disclosure, but it does not mean that the business architecture description model of the embodiment of the present disclosure may not include other models, and as a business is updated and expanded, the model included in the business architecture description model is continuously iterated and updated.

In this context, it is to be understood that the terms to which the invention relates include blockchains, blockchain networks, ledgers, intelligent contracts and consensus. Wherein the blockchain is a storage structure for encrypted, chained transactions formed by blocks. The header of each block can comprise the hash values of all transactions in the block and also comprises the hash values of all transactions in the previous block, so that the falsification and forgery prevention of the transactions in the block are realized on the basis of the hash values; newly generated transactions, after being filled into the tiles and passing through the consensus of nodes in the blockchain network, are appended to the end of the blockchain to form a chain growth. A blockchain network refers to a collection of nodes that collectively incorporate a new block into a blockchain. The ledger is a general term for a blockchain (also referred to as ledger data) and a state database synchronized with the blockchain. Wherein, the blockchain records the transaction in the form of a file in a file system; the state database records the transactions in the blockchain in the form of different types of key-value pairs and is used for supporting quick query of the transactions in the blockchain. The intelligent contract, also called chain code or application code, is a program deployed in a node of a block chain network, the program is triggered to execute according to a condition, and the node executes the intelligent contract called in the received transaction to update or inquire the key value of the state database to data. Consensus refers to the process for agreeing on transactions in a block between the nodes involved, the agreed-upon block to be appended to the end of the block chain, with mechanisms to achieve consensus including proof of workload, proof of rights, proof of share authorization, proof of elapsed time, etc.

Fig. 3 schematically shows a flowchart of an information processing method based on a blockchain network according to an embodiment of the present disclosure. As shown in fig. 3, the method may include operations S310 to S340.

In operation S310, initial information of m asset maintenance requests is received using blockchain nodes of a blockchain network. In the present disclosure, the initial information includes an initial maintenance operation and initial maintenance information performed on the business architecture description model, and m is a positive integer greater than or equal to 2.

In accordance with embodiments of the present disclosure, a block link point may be any one or more block link nodes as shown in fig. 2. The operational node may be any one or more of the operational nodes shown in fig. 2. The approval node may be any one or more of the approval nodes shown in fig. 2.

According to the embodiment of the disclosure, the initial information of the m asset maintenance requests may be sent to the blockchain node by a modeling person through the operation node, where each asset maintenance request is used to indicate a maintenance operation for iteratively updating the service architecture description model, and may include, but is not limited to, addition, edition, deletion, rollback, and completion of the process model, the entity model, the model description in the product model, and the association relationship between the model components, which are described in fig. 2, and these maintenance operations will reflect the latest service architecture change, service project requirement, and the service change corresponding thereto. The maintenance information may include, but is not limited to, asset components describing the process model, entity model, model description in the product model and associations between the model components as described in fig. 2, and fields corresponding to the asset components, depending on the business architecture description model.

Taking banking as an example, in conjunction with the business architecture description model shown in fig. 2, assume that the next updated version of the application software will provide support for the credit card system to apply for the virtual digital credit card service for the smartphone according to the actual business requirements. Accordingly, the flow model, the product model and the entity model need to be modified in the service architecture description model. Specifically, the flow model is modified, so that the modified flow model includes a flow for applying for a virtual digital credit card. And modifying the product model to enable the modified product model to be added with information such as the product and product conditions of the virtual digital credit card. And modifying the entity model to enable the modified entity model to be added with the medium information of the digital virtual credit card and the like.

In operation S320, it is determined whether there are n asset maintenance requests of the m asset maintenance requests for which asset maintenance conflicts. In the present disclosure, n is a positive integer greater than or equal to 2, and n ≦ m. In the related art, if n asset maintenance requests with conflicting asset maintenance exist in m asset maintenance requests, the n asset maintenance requests are directly returned to the modeler. In contrast, in the present disclosure, the following operation S330 will be performed.

In accordance with embodiments of the present disclosure, asset maintenance conflicts may include, but are not limited to, formal conflicts and substance conflicts. A formal conflict includes, but is not limited to, a potential conflict between two or more asset updates, but does not actually change the same asset component or field, or semantically conflicts with the same asset component, and a substantial conflict may include, but is not limited to, a conflict between two or more asset updates, and changes to the same asset component or field.

In the related art, if there are n asset maintenance requests with an asset maintenance conflict, the n asset maintenance requests with an asset maintenance conflict are directly returned to the sender. However, according to the embodiment of the present disclosure, the initial information with conflict is processed to obtain the target information.

In operation S330, if there are n asset maintenance requests, processing initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, where the target information includes target maintenance operation and target maintenance information for indicating execution of the business architecture description model.

The target maintenance operation is obtained by processing the initial maintenance operation, and the target maintenance information is obtained by processing the initial maintenance information. The types of the asset conflicts are different, and different processing modes are adopted for the initial information of the n asset maintenance requests.

In operation S340, based on the target maintenance information, a target maintenance operation is performed on the business architecture description model to obtain maintenance result information, and the maintenance result information is stored at the block link point.

According to the embodiment of the disclosure, if n asset maintenance requests of asset maintenance conflict do not exist in m asset maintenance requests, the initial maintenance operation can be performed on the service architecture description model based on the initial maintenance information included in the m asset maintenance requests directly in response to the received m asset maintenance requests to obtain maintenance result information, and the maintenance result information is stored in the block link point.

By the embodiment of the disclosure, the characteristics of non-tampering and traceability of the block chain technology are fully utilized, the initial information is processed to obtain the target information under the condition that the asset request has conflict, the asset maintenance is carried out on the business architecture description model based on the target information, and the asset dynamic iterative update information of the asset conflict is stored on the block chain, so that the iterative traceability of the business architecture description model can be realized, the timeliness of model results is ensured, the conflict of asset maintenance is reduced, and the normal operation of each business of an enterprise is ensured.

Having described the general principles of the present disclosure, various non-limiting embodiments of the present disclosure are described in detail below.

As an alternative embodiment, the asset maintenance request comprises: and the asset change execution request is used for indicating that the change operation is executed on the business architecture description model. And/or an asset change rollback request, wherein the asset change rollback request is used for indicating that a change rollback operation is executed on the business architecture description model.

According to an embodiment of the present disclosure, the asset maintenance request may include only an asset change execution request, only an asset change rollback request, and both an asset change execution request and an asset change rollback request. According to the iterative update condition of the actual service, the corresponding asset maintenance request can be determined.

In the present disclosure, the alteration operation may include, but is not limited to, operations of adding, editing, deleting, rolling back, supplementing, etc. to the model description in the process model, the entity model, the product model, and the association relationship between the components of the model. Correspondingly, the change rollback operation may include, but is not limited to, rollback operations of addition, editing, deletion, rollback, completion and the like of model descriptions in the process model, the entity model and the product model and the association relationship between the model components, that is, performing a undo operation on a previously performed update operation.

Through the embodiment of the disclosure, the information processing method based on the block chain network supports asset maintenance requests of various change contents, so that iterative update management aiming at the business architecture description model is more comprehensive, and the real-time performance and the reliability of the business architecture description model are improved.

As an alternative embodiment, the determining whether there are n asset maintenance requests of the m asset maintenance requests for which there is an asset maintenance conflict includes: and responding to the received m asset maintenance requests, and sending the approval information corresponding to the m asset maintenance requests to the approval node, so that the approval node can return an approval result based on the approval information. And receiving an approval result returned by the approval node. And if the approval result shows that the m asset maintenance requests are approved, determining whether n asset maintenance requests with asset maintenance conflict exist in the m asset maintenance requests. The approval result can only confirm the correctness of the asset maintenance request in business, and does not consider whether the asset maintenance request has conflict of asset maintenance.

As an alternative embodiment, if the approval result indicates that the m asset maintenance requests are not approved, the initial information and the approval result of the m asset maintenance requests are stored in the block link point, and the information of other assets is not changed.

According to the embodiment of the disclosure, the asset maintenance conflict is detected only when the asset maintenance request is approved, so as to determine whether the asset maintenance conflict exists, and the asset maintenance request which does not meet the requirement can be fed back quickly through approval, so that the resource of information processing is saved.

It is understood that the asset maintenance request for the business architecture model includes information of maintenance operations to be performed and objects to be maintained, which may be one or more asset components in the business architecture description model or one or more fields of the asset components.

As an alternative embodiment, the determining whether there are n asset maintenance requests of the m asset maintenance requests for which there is an asset maintenance conflict may include: and if the m asset maintenance requests comprise m asset change execution requests, determining whether n asset maintenance requests in asset change conflict exist based on the initial information corresponding to the m asset change execution requests.

Example 1: 2 asset maintenance requests are received, asset change 1 and asset change 2 respectively. Wherein the asset change 1 is a "partner" field for indicating a modification of a "credit card issuance" activity, the initial information corresponding to the asset change 1 is a "partner" field for the modification of the "credit card issuance" activity, the initial maintenance operation is a modification, and the initial maintenance information is a "partner" field for the "credit card issuance" activity. The asset change 2 indicates a "destination" field of the modification "credit card issuance" activity, the initial information corresponding to the asset change 2 is the "destination" field of the modification "credit card issuance" activity, the initial maintenance operation is also the modification, and the initial maintenance information is the "destination" field of the "credit card issuance" activity. Since both are directed to the same asset component or field, the asset maintenance conflict between asset change 1 and asset change 2 may be determined to be a formal conflict.

Example 2: 2 asset maintenance requests are received, asset change 3 and asset change 4 respectively. The asset change 3 is used for indicating that the added ' people ' bank ' is associated with the ' affiliate ' of the ' credit card issuing ' activity, the initial information corresponding to the asset change 3 is the association of the added ' people ' bank ' with the ' affiliate ' of the ' credit card issuing ' activity, the initial maintenance operation is the addition, and the initial maintenance information is the association of the ' people ' bank ' with the ' affiliate ' of the ' credit card issuing ' activity. The asset change 4 is used for indicating that the added VISA organization is associated with the affiliate of the credit card issuing activity, the initial information corresponding to the asset change 4 is that the added VISA organization is associated with the affiliate of the credit card issuing activity, the initial maintenance operation is also increased, and the initial maintenance information is that the VISA organization is associated with the affiliate of the credit card issuing activity. Since both are directed to semantically conflicting changes to the same asset component, the asset maintenance conflict between asset change 3 and asset change 4 may be determined to be a formal conflict.

Example 3: 2 asset maintenance requests are received, asset change 5 and asset change 6 respectively. Wherein the asset change 5 is used to indicate that the "partner" field of the "credit card issuance" activity is modified, the "airline" is modified to be the "transportation enterprise", the initial information corresponding to the asset change 5 is the "partner" field of the "credit card issuance" activity is modified, the "airline" is modified to be the "transportation enterprise", the initial maintenance operation is modified, and the "partner" field of the "credit card issuance" activity, which is the initial maintenance information, is changed from the "airline" to the "transportation enterprise". The asset change 6 is used to indicate that the "partner" field of the "credit card issuance" activity is modified, the "airline" is modified to the "airline (passenger transport)", the initial information corresponding to the asset change 6 is the "partner" field of the "credit card issuance" activity is modified, the "airline" is modified to the "airline (passenger transport)", the initial maintenance operation is also modified, and the "partner" field of the "credit card issuance" activity is changed from the "airline" to the "airline (passenger transport)", the initial maintenance information is. Since both are modifications to the "partner" field of the same "credit card issuance" activity and semantic conflicts occur in the contents of the modifications, it can be determined that the asset maintenance conflict between asset change 5 and asset change 5 is a substantial conflict.

It should be noted that, the above embodiments are only to better illustrate how to determine whether there are conflicts among multiple asset maintenance requests according to asset components and fields, and the type of the conflict is not the only conflict scenario or type, and there may be any form of initial information according to the specific situation of the business architecture description model and the asset maintenance request, and the disclosure is not limited thereto.

As an alternative embodiment, the determining whether there are n asset maintenance requests of the m asset maintenance requests for which there is an asset maintenance conflict may include: and if the m asset maintenance requests comprise m asset change rollback requests, determining whether n asset maintenance requests with asset rollback conflict exist based on rollback results corresponding to the m asset change rollback requests.

As an alternative embodiment, the determining whether there are n asset maintenance requests of the m asset maintenance requests for which there is an asset maintenance conflict may include: if the m asset maintenance requests comprise p asset change execution requests and q asset change rollback requests, determining whether n asset maintenance requests with asset completion conflict exist based on initial information corresponding to the p asset change execution requests and rollback results corresponding to the q asset change rollback requests, wherein p and q are positive integers, and p + q is m.

According to an embodiment of the present disclosure, the underlying principles of the asset auto-completion process are similar to the conflict resolution process described previously. The completion process also needs to detect whether asset completion conflicts exist through intelligent contracts, and two situations exist at the moment. In the implementation, if the rollback approval is passed, the business architecture description model and the model content (asset components, fields and other information) which are proposed to rollback and the expected rollback result are recorded when the application is proposed. The above is referred to as rollback reference snapshot data, and adds the rollback business architecture description model information to the blockchain. Triggering an automatic asset completion process.

Case 1: assets to be replenished are not associated with the rollback reference snapshot data, either are changed to different asset components or fields, or are semantically conflicting changes to the same asset component. At this time, the completion action and the backspacing asset are considered not to conflict, the contents of the asset completion without actual conflict can be merged through the merging rule set in the intelligent contract, and the completed contents are written into the block. For example, asset change 3, asset change 4, and asset change 5 as previously described. The operation of the asset change is in the order that after the asset change 3, the asset change 4 and the asset change 5 occur in sequence. A rollback asset change 3 is now required. After the block data is rolled back, the block data has been rolled back to the state before the asset change 3 occurred. Judging according to the actual change content that there is no field conflict or semantic conflict between the three changes, namely the conflict type is form conflict, then automatically and sequentially initiating the two block data change operations of asset change 4 and asset change 5, namely the configuration asset can be completed.

Case 2: the assets needing to be completed and the rollback reference snapshot data need to be changed in a mutually conflicting way on the same asset component or field, or the same asset component is changed in an opposite way (which is equivalent to changing the rollback content back to the original state before rollback), and here, two or more asset updates are considered to be in conflict and cannot be automatically processed. At this time, the applicant needs to be prompted, automatic completion cannot be achieved, and if data needs to be completed, an asset change operation needs to be initiated additionally to achieve completion. For example, asset change 4, asset change 5, and asset change 8 as previously described, where asset change 8 is used to indicate the partner that deleted the "Credit card issuance" activity, "airline (passenger transport)". The operation of the asset change is in the order that after asset change 4, asset change 5 and asset change 8 occur in sequence. A rollback asset change 4 is now required. After the block data is rolled back, the block data has been rolled back to the state before the asset change 4 occurred. And judging according to the actual change content that the three changes are all operations carried out on the ' credit card issuing activity ' partner ', and if field conflict or semantic conflict exists, namely the conflict type is substantial conflict, the system informs the applicant and cannot automatically replenish the assets. It should be noted that, the method for determining the asset rollback conflict and the asset completion conflict may refer to the method for determining the asset change conflict, which is not described herein again.

As an alternative embodiment, processing the initial information of the n asset maintenance requests to determine the target information corresponding to the m asset maintenance requests includes: and determining whether the asset maintenance conflict is a field information conflict or a semantic information conflict aiming at the initial information of the n asset maintenance requests. If not, merging the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, wherein the merged information comprises merged maintenance operation and merged maintenance information executed on the business architecture description model, and determining the merged information corresponding to the n asset maintenance requests and the initial information of the m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

According to an embodiment of the present disclosure, if 3 asset maintenance requests include 1 asset change 7 in addition to the asset change 1 and the asset change 2 in the foregoing example 1, and the asset change 7 does not conflict with both the asset change 1 and the asset change 2, merged information corresponding to the 2 asset maintenance requests, which is a "partner" field and a "destination" field of a modification "credit card issuance" activity, that is, a "partner" field and a "destination" field of a merging maintenance operation as modifications, and merged maintenance information which is a "partner" field and a "destination" field of a "credit card issuance" activity, may be generated for the merging of the asset change 1 and the asset change 2. The merged maintenance information and the asset change 7 are determined as target information corresponding to 3 asset maintenance requests.

It should be noted that the generated merged information corresponding to the n asset maintenance requests may be one piece of information or multiple pieces of information, which is not limited in this disclosure.

By the embodiment of the disclosure, the initial information of n asset maintenance requests can be processed under the condition that whether the asset maintenance conflict is a field information conflict or a semantic information conflict, one or more pieces of combined information corresponding to the n asset maintenance requests are generated, the technical problem that the n asset maintenance requests are directly returned to a sender in the related technology is solved, the change times of the model can be reduced, frequent change is avoided, and the information storage burden of the block chain can be reduced by combining the asset maintenance requests.

As an alternative embodiment, merging the initial information of n asset maintenance requests includes: and responding to the n asset maintenance requests, and calling the intelligent contract of the blockchain node, wherein the intelligent contract is configured with a merging mechanism. And merging the initial information of the n asset maintenance requests based on a merging mechanism.

According to the embodiment of the disclosure, for the information of the asset maintenance request which can be merged, different fields or parameter data modified in the change can be merged through a merging mechanism set in an intelligent contract, multiple operations on the asset are merged into one operation, and the updated content is written into the block by one-time updating. The change times can be reduced, and the model iterative updating speed is improved.

As an alternative embodiment, the method further comprises: and if the asset maintenance conflict is determined to be a field information conflict or a semantic information conflict, returning the initial information of the n asset maintenance requests. And determining the initial information of the m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

According to the embodiment of the disclosure, in the case that the change field information conflict or the semantic information conflict is determined, the change field information is considered to need to be returned to the applicant, so that the applicant can modify the change, submit the change request again, or wait for the block chain to be automatically synchronized and then reapply based on the latest asset.

Through the embodiment of the disclosure, the total change information of the business architecture description model is uploaded to the block chain, the change path of the business architecture description model can be disclosed, the block chain technology ensures that the information cannot be falsified, and the automatic processing of conflict between changes is realized, so that the real-time performance and the reliability of the business architecture description model data are improved.

As an alternative embodiment, in the case that the asset maintenance request includes an asset change execution request, performing a target maintenance operation on the business architecture description model based on the target maintenance information to obtain the maintenance result information includes: based on the merged information corresponding to the n asset maintenance requests, performing an asset change operation on the business architecture description model to obtain a first change result, and based on the initial information of the m-n asset maintenance requests, performing an asset change operation on the business architecture description model to obtain a second change result.

According to the embodiment of the present disclosure, if 3 asset maintenance requests include 1 asset change 7 in addition to the asset change 1 and the asset change 2 in the foregoing example 1, the asset change of the asset change 1 and the asset change 2 can be completed by performing one asset change operation on the business architecture description model. Then, the asset change 7 is executed, and the asset change corresponding to the asset change request 7 is completed.

Fig. 4 schematically illustrates a flow diagram for performing asset changes to a business architecture description model based on a blockchain network according to an embodiment of the present disclosure.

As shown in fig. 4, an information processing method 400 of performing asset changes on a business architecture description model involves interactions between modelers 410, approvers 430, and a blockchain network 420, which may include operations S411 and S412, and operations S421 to S427. In specific implementation, the modeler 410 performs operation S411 to submit a model change request to the blockchain network 420, and after receiving the model change request, the blockchain network 420 may first perform operation S421 to add the model change request information to the blockchain. Operation S422 is then performed to send the change approval information to the approver 430. Next, operation S423 is performed, and the change approval result is received. Then, operation S424 is executed to associate and map the model change request with the approval information. If the approval result indicates that the approval is passed, i.e. the change is approved, operation S425 is performed, and the modified service architecture description model information is added to the block chain. Operation S426, collision recognition and processing is then performed. If the identified conflict indicates that the change request is mergeable and does not result in a field conflict or semantic conflict, then merge the change request that does not result in a field conflict or semantic conflict. If the identified conflict indicates that the change request is not combinable and cannot be automatically processed, operation S412 is executed to return to the manual processing of the modeler. If the approval result indicates that the approval is not passed, that is, the change is not approved, operation S427 is executed, and the service architecture description model information and the approval result before the modification are added to the block chain.

By the embodiment of the disclosure, the problem of asset update conflict of multiple service frameworks in model maintenance is solved, and the change result information is uploaded to the block chain, so that automatic management of asset maintenance related information can be realized.

As an alternative embodiment, in the case that the asset maintenance request includes an asset change rollback request, performing the target maintenance operation on the business architecture description model to obtain the maintenance result information based on the target maintenance information includes: and performing asset completion operation on the business architecture description model based on the merging information corresponding to the n asset maintenance requests to obtain a first completion result. And based on the initial information of the m-n asset maintenance requests, performing asset completion operation on the business architecture description model to obtain a second completion result.

Through the embodiment of the disclosure, the total change information of the business architecture description model is uploaded to the block chain, the change path of the business architecture description model can be disclosed, the block chain technology ensures that the information cannot be falsified, and automatic back-filling of the change backspacing asset according to the change history path is realized, so that the real-time performance and the reliability of the business architecture description model data are improved.

Fig. 5 schematically illustrates a flow diagram for performing asset fallback on a business architecture description model based on a blockchain network according to an embodiment of the present disclosure.

As shown in fig. 5, the information processing method 500 for performing asset rollback on a business architecture description model involves interaction between modelers 410, approvers 430, and blockchain network 420, and may include operations S511 through S514, and operations S521 through S528. In specific implementation, the modeler 410 performs operation S511 to submit a model change rollback request to the blockchain network 420, and after receiving the model change rollback request, the blockchain network 420 may first perform operation S521 to perform a query in an intelligent contract. Operation S512 is then performed to return asset change records to the modeler 410 that confirm that rollback is required. The modeler 410 performs operation S522 to send the asset change record requiring rollback to the approver 430, so that the approver 430 can return the approval result based on the received asset change record requiring rollback. Next, operation S523 is performed to receive a result of the change rollback approval. Operation S524 is executed to associate and map the model change rollback request with the approval information. If the approval result indicates that the approval is passed, that is, the change rollback is agreed, operation S525 is performed, and the rollback business architecture description model information is added to the block chain. Operation S526 is then performed, conflict identification and asset completion. If the identified conflict indicates that the change request is mergeable, no field conflict or semantic conflict is caused. The asset change is automatically performed. And an operation S513 is executed, and if the automatic completion cannot be performed, the manual processing is returned to the modeler to prompt the modeler that the automatic completion cannot be performed. If the approval result indicates that the approval is not passed, that is, the change rollback is not approved, operation S527 is executed, and the rollback request information and the approval result are added to the block chain. Finally, operation S528 is performed to notify the approval staff of the returned service architecture description model information, and operation S514 is performed to notify the modeling staff of the returned service architecture description model information.

By the embodiment of the disclosure, not only can the change of the business architecture description model be supported, but also the rollback after the change of the business architecture description model can be supported, the automatic retroplement of the assets after the rollback is realized, and the real-time performance and the reliability of the business architecture description model data can be improved.

As an alternative embodiment, the method further comprises: target information corresponding to the m asset maintenance requests is stored at the block link points. Optionally, the asset maintenance request and the approval information may be subjected to associated mapping, so that all the change information of the service architecture description model can be uploaded to the block chain, and the asset maintenance information can be traced.

It should be noted that, for other operations of the business architecture description model, such as query, trace back change history, block storage processing, etc., since conflict processing involving asset change is not involved, the disclosure is not set forth.

Fig. 6 schematically shows a block diagram of an information processing apparatus based on a blockchain network according to an embodiment of the present disclosure. As shown in fig. 6, the information processing apparatus 600 may include an initial maintenance information receiving module 610, an asset maintenance conflict determination module 620, a target maintenance information determination module 630, and a maintenance result information processing module 640.

An initial maintenance information receiving module 610, configured to receive initial information of the m asset maintenance requests by using a blockchain node of the blockchain network. The initial information comprises initial maintenance operation and initial maintenance information which are executed on the business architecture description model, and m is a positive integer which is greater than or equal to 2. Optionally, the initial maintenance information receiving module 610 may be configured to perform operation S310 described in fig. 3, for example, and is not described herein again.

And the asset maintenance conflict determining module 620 is configured to determine whether n asset maintenance requests of the asset maintenance conflict exist in the m asset maintenance requests, where n is a positive integer greater than or equal to 2, and n is less than or equal to m. Optionally, the asset maintenance conflict determination module 620 may be configured to perform operation S320 described in fig. 3, for example, and will not be described herein again.

And a target maintenance information determining module 630, configured to process initial information of the n asset maintenance requests, if the initial information exists, to determine target information corresponding to the m asset maintenance requests, where the target information includes target maintenance operation and target maintenance information for indicating to perform on the business architecture description model. Optionally, the target maintenance information determining module 630 may be configured to perform operation S330 described in fig. 3, for example, and is not described herein again.

And the maintenance result information processing module 640 is configured to perform a target maintenance operation on the service architecture description model based on the target maintenance information to obtain maintenance result information, and store the maintenance result information in the block link point. Optionally, the maintenance result information processing module 640 may be configured to perform operation S340 described in fig. 3, for example, and is not described herein again.

As an alternative embodiment, the asset maintenance conflict determination module comprises: and the examination and approval information sending submodule is used for responding to the received m asset maintenance requests and sending the examination and approval information corresponding to the m asset maintenance requests to the examination and approval node so that the examination and approval node can return an examination and approval result based on the examination and approval information. And the approval result receiving submodule is used for receiving the approval result returned by the approval node. And the asset maintenance conflict determination submodule is used for determining whether n asset maintenance requests with asset maintenance conflicts exist in the m asset maintenance requests or not if the approval result shows that the m asset maintenance requests are approved.

As an alternative embodiment, the asset maintenance conflict determination submodule includes: and the asset maintenance conflict first determining unit is used for determining whether n asset maintenance requests with asset change conflicts exist based on the initial information corresponding to the m asset change execution requests if the m asset maintenance requests comprise the m asset change execution requests. Or the asset maintenance conflict second determining unit is used for determining whether n asset maintenance requests with asset rollback conflicts exist based on the rollback results corresponding to the m asset change rollback requests if the m asset maintenance requests comprise the m asset change rollback requests. Or if the m asset maintenance requests comprise p asset change execution requests and q asset change rollback requests, determining whether n asset maintenance requests with an asset completion conflict exist based on the initial information corresponding to the p asset change execution requests and the rollback results corresponding to the q asset change rollback requests, wherein p and q are positive integers, and p + q is m.

As an alternative embodiment, the target maintenance information determination module includes: and the asset maintenance conflict determination submodule is used for determining whether the asset maintenance conflict is a field information conflict or a semantic information conflict or not according to the initial information of the n asset maintenance requests. And the initial information merging submodule is used for merging the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests if the initial information is not merged, wherein the merged information comprises merged maintenance operation and merged maintenance information executed on the service architecture description model. And the first target maintenance information determining submodule is used for determining the merging information corresponding to the n asset maintenance requests and the initial information of the m-n asset maintenance requests as the target information corresponding to the m asset maintenance requests.

As an alternative embodiment, the initial information merging sub-module includes: and the intelligent contract calling unit is used for calling the intelligent contracts of the block chain nodes in response to the n asset maintenance requests, wherein the intelligent contracts are configured with a merging mechanism. And the initial information merging unit is used for merging the initial information of the n asset maintenance requests based on a merging mechanism.

As an optional embodiment, the target maintenance information determining module further includes: and the initial information returning submodule is used for returning the initial information of the n asset maintenance requests if the initial information is the same as the initial information of the n asset maintenance requests. And the second target maintenance information determining submodule is used for determining the initial information of the m-n asset maintenance requests as the target information corresponding to the m asset maintenance requests.

As an alternative embodiment, in the case where the asset maintenance request includes an asset change execution request, the maintenance result information processing module includes: and the first change result obtaining module is used for executing asset change operation on the business architecture description model based on the merging information corresponding to the n asset maintenance requests so as to obtain a first change result. And the second change result obtaining module is used for executing asset change operation on the business architecture description model based on the initial information of the m-n asset maintenance requests to obtain a second change result.

As an alternative embodiment, in the case where the asset maintenance request includes an asset change rollback request, the maintenance result information processing module includes: and the first completion result obtaining module is used for executing asset completion operation on the service architecture description model based on the merging information corresponding to the n asset maintenance requests so as to obtain a first completion result. And the second completion result obtaining module is used for executing asset completion operation on the business architecture description model based on the initial information of the m-n asset maintenance requests to obtain a second completion result.

As an alternative embodiment, the apparatus further comprises: and the target information storage module is used for storing the target information corresponding to the m asset maintenance requests in the block link points.

As an alternative embodiment, the asset maintenance conflict determination module is further configured to: and if the approval result shows that the m asset maintenance requests are not approved, storing the initial information and the approval result of the m asset maintenance requests in the blockchain node.

It should be noted that the implementation, solved technical problems, implemented functions, and achieved technical effects of each module in the information apparatus part embodiment based on the blockchain network are respectively the same as or similar to the implementation, solved technical problems, implemented functions, and achieved technical effects of each corresponding step in the information method part embodiment based on the blockchain network, and are not described herein again.

Any number of modules, sub-modules, units, or at least part of the functionality of any number thereof according to embodiments of the present disclosure may be implemented in one module. Any one or more of the modules and sub-modules according to the embodiments of the present disclosure may be implemented by being split into a plurality of modules. Any one or more of the modules, sub-modules, units according to the embodiments of the present disclosure may be implemented at least partially as a hardware circuit, such as a field programmable gate array (FNGA), a programmable logic array (NLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in any other reasonable manner of hardware or firmware by integrating or packaging a circuit, or in any one of three implementations of software, hardware, and firmware, or in any suitable combination of any of them. Alternatively, one or more of the modules, sub-modules, units according to embodiments of the disclosure may be implemented at least partly as computer program modules, which, when executed, may perform corresponding functions.

For example, an initial maintenance information receiving module, an asset maintenance conflict determining module, a target maintenance information determining module, a maintenance result information processing module, an approval information sending submodule, an approval result receiving submodule, an asset maintenance conflict determining submodule, an asset maintenance conflict first determining unit, an asset maintenance conflict second determining unit, an asset maintenance conflict third determining unit, an asset maintenance conflict determining submodule, an initial information merging submodule, a target maintenance information first determining submodule, an intelligent contract calling unit, an initial information merging unit, an initial information returning submodule, a target maintenance information second determining submodule, a first change result obtaining module, a second change result obtaining module, a first completion result obtaining module, a second completion result obtaining module, and a target information storing module may be combined in one module, or any one of them may be split into a plurality of modules. Alternatively, at least part of the functionality of one or more of these modules may be combined with at least part of the functionality of the other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of an initial maintenance information receiving module, an asset maintenance conflict determining module, a target maintenance information determining module, a maintenance result information processing module, an approval information transmitting submodule, an approval result receiving submodule, an asset maintenance conflict determining submodule, an asset maintenance conflict first determining unit, an asset maintenance conflict second determining unit, an asset maintenance conflict third determining unit, an asset maintenance conflict determining submodule, an initial information merging submodule, a target maintenance information first determining submodule, an intelligent contract calling unit, an initial information merging unit, an initial information returning submodule, a target maintenance information second determining submodule, a first change result obtaining module, a second change result obtaining module, a first completion result obtaining module, a second completion result obtaining module, and a target information storing module may be at least partially implemented as a hardware circuit, such as a field programmable gate array (FNGA), a programmable logic array (NLA), a system on a chip, a system on a substrate, a system on a package, an Application Specific Integrated Circuit (ASIC), or may be implemented in hardware or firmware in any other reasonable manner of integrating or packaging a circuit, or in any one of or any suitable combination of software, hardware, and firmware. Or, at least one of the initial maintenance information receiving module, the asset maintenance conflict determining module, the target maintenance information determining module, the maintenance result information processing module, the approval information sending submodule, the approval result receiving submodule, the asset maintenance conflict determining submodule, the asset maintenance conflict first determining unit, the asset maintenance conflict second determining unit, the asset maintenance conflict third determining unit, the asset maintenance conflict determining submodule, the initial information merging submodule, the target maintenance information first determining submodule, the intelligent contract calling unit, the initial information merging unit, the initial information returning submodule, the target maintenance information second determining submodule, the first change result obtaining module, the second change result obtaining module, the first complement result obtaining module, the second complement result obtaining module and the target information storing module may be at least partially implemented as a computer program module, when the computer program modules are run, corresponding functions may be performed.

Fig. 7 schematically illustrates a schematic diagram of a computer-readable storage medium product adapted to implement the above-described blockchain network-based information processing method according to an embodiment of the present disclosure.

In some possible embodiments, aspects of the present invention may also be implemented in the form of a program product including program code for causing an apparatus to perform the aforementioned operations (or steps) in the information processing method according to the various exemplary embodiments of the present invention described in the above-mentioned "exemplary method" section of this specification, when the program product is run on the apparatus. For example, the electronic device may perform operations S310 to S340 as shown in fig. 3, may also perform operations S411 and S412, and operations S421 to S427 as shown in fig. 4. As shown in fig. 5, operations S511 to S514, and operations S521 to S528.

The program product may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. A readable storage medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, or device, or any combination of the foregoing. More specific examples (a non-exhaustive list) of the readable storage medium include: an electrical connection having one or more wires, a portable disk, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ENROM or flash memory), an optical fiber, a portable compact disk read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing.

As shown in fig. 7, an information processing program product 700 according to an embodiment of the present invention is described, which may employ a portable compact disc read only memory (CD-ROM) and include program code, and may be run on a device, such as a personal computer. However, the program product of the present invention is not limited in this respect, and in this document, a readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, or device.

A readable signal medium may include a propagated data signal with readable program code embodied therein, for example, in baseband or as part of a carrier wave. Such a propagated data signal may take any of a variety of forms, including, but not limited to, electro-magnetic, optical, or any suitable combination thereof. A readable signal medium may also be any readable medium that is not a readable storage medium and that can communicate, propagate, or transport a program for use by or in connection with an instruction execution system, or device. Program code embodied on a readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing.

Program code for carrying out operations for aspects of the present invention may be written in any combination of one or more programming languages, including an object oriented programming language such as Java, C + + or the like and conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user computing device, partly on a remote computing device, or entirely on the remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user computing device through any kind of network, including a local area network (LAA) or a wide area network (WAA), or may be connected to an external computing device (e.g., through the internet using an internet service provider).

Fig. 8 schematically shows a block diagram of an electronic device adapted to implement the above-described blockchain network-based information processing method according to an embodiment of the present disclosure. The electronic device shown in fig. 8 is only an example, and should not bring any limitation to the functions and the scope of use of the embodiments of the present disclosure.

As shown in fig. 8, an electronic device 800 according to an embodiment of the present disclosure includes a processor 801 that can perform various appropriate actions and processes according to a program stored in a Read Only Memory (ROM)802 or a program loaded from a storage section 808 into a Random Access Memory (RAM) 803. The processor 801 may include, for example, a general purpose microprocessor (e.g., CNU), an instruction set processor and/or associated chipset(s) and/or a special purpose microprocessor (e.g., Application Specific Integrated Circuit (ASIC)), and so forth. The processor 801 may also include onboard memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flows according to embodiments of the present disclosure.

In the RAM803, various programs and data necessary for the operation of the electronic apparatus 800 are stored. The processor 801, the ROM802, and the RAM803 are connected to each other by a bus 804. The processor 801 performs various operations of the method flows according to the embodiments of the present disclosure by executing programs in the ROM802 and/or RAM 803. Note that the programs may also be stored in one or more memories other than the ROM802 and RAM 803. The processor 801 may also perform operations S310 through S340 illustrated in fig. 3 according to the embodiment of the present disclosure by executing programs stored in the one or more memories. The electronic device may also perform operations S411 and S412, and operations S421 to S427 as shown in fig. 4. The electronic device may also perform operations S511 through S514, and operations S521 through S528 as shown in fig. 5.

Electronic device 800 may also include input/output (I/O) interface 805, input/output (I/O) interface 805 also connected to bus 804, according to an embodiment of the present disclosure. The system 800 may also include one or more of the following components connected to the I/O interface 805: an input portion 806 including a keyboard, a mouse, and the like; an output section 807 including a signal such as a Cathode Ray Tube (CRT), a Liquid Crystal Display (LCD), and the like, and a speaker; a storage portion 808 including a hard disk and the like; and a communication section 809 including a network interface card such as an LAA card, modem, or the like. The communication section 809 performs communication processing via a network such as the internet. A drive 810 is also connected to the I/O interface 805 as necessary. A removable medium 811 such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, or the like is mounted on the drive 810 as necessary, so that a computer program read out therefrom is mounted on the storage section 808 as necessary.

According to embodiments of the present disclosure, method flows according to embodiments of the present disclosure may be implemented as computer software programs. For example, embodiments of the present disclosure include a computer program product comprising a computer program embodied on a computer readable storage medium, the computer program containing program code for performing the method illustrated by the flow chart. In such an embodiment, the computer program can be downloaded and installed from a network through the communication section 809 and/or installed from the removable medium 811. The computer program, when executed by the processor 801, performs the above-described functions defined in the system of the embodiments of the present disclosure. The systems, devices, apparatuses, modules, units, etc. described above may be implemented by computer program modules according to embodiments of the present disclosure.

The present disclosure also provides a computer-readable storage medium, which may be contained in the apparatus/device/system described in the above embodiments; or may exist separately and not be assembled into the device/apparatus/system. The above-mentioned computer-readable storage medium carries one or more programs which, when executed, implement the information processing method according to an embodiment of the present disclosure, including operations S310 to S340 shown in fig. 3. The electronic device may also perform operations S411 and S412, and operations S421 to S427 as shown in fig. 4. The electronic device may also perform operations S511 through S514, and operations S521 through S528 as shown in fig. 5.

According to embodiments of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, which may include, for example but is not limited to: a portable computer diskette, a hard disk, a Random Access Memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (ENROM or flash memory), a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. In the present disclosure, a computer readable storage medium may be any tangible medium that can contain, or store a program for use by or in connection with an instruction execution system, apparatus, or device. For example, according to embodiments of the present disclosure, a computer-readable storage medium may include the ROM802 and/or RAM803 described above and/or one or more memories other than the ROM802 and RAM 803.

The flowchart and block diagrams in the figures illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment, or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams or flowchart illustration, and combinations of blocks in the block diagrams or flowchart illustration, can be implemented by special purpose hardware-based systems which perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

Those skilled in the art will appreciate that various combinations and/or combinations of features recited in the various embodiments and/or claims of the present disclosure can be made, even if such combinations or combinations are not expressly recited in the present disclosure. In particular, various combinations and/or combinations of the features recited in the various embodiments and/or claims of the present disclosure may be made without departing from the spirit or teaching of the present disclosure. All such combinations and/or associations are within the scope of the present disclosure.

The embodiments of the present disclosure have been described above. However, these examples are for illustrative purposes only and are not intended to limit the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in the embodiments cannot be used in advantageous combination. The scope of the disclosure is defined by the appended claims and equivalents thereof. Various alternatives and modifications can be devised by those skilled in the art without departing from the scope of the present disclosure, and such alternatives and modifications are intended to be within the scope of the present disclosure.

Claims

1. An information processing method based on a block chain network comprises the following steps:

receiving initial information of m asset maintenance requests by using a blockchain node of the blockchain network, wherein the initial information comprises initial maintenance operation and initial maintenance information executed on a service architecture description model, and m is a positive integer greater than or equal to 2;

determining whether n asset maintenance requests with asset maintenance conflicts exist in the m asset maintenance requests, wherein n is a positive integer greater than or equal to 2 and is less than or equal to m;

if so, processing initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, wherein the target information comprises target maintenance operation and target maintenance information used for indicating the execution of the business architecture description model;

and based on the target maintenance information, executing the target maintenance operation on the business architecture description model to obtain maintenance result information, and storing the maintenance result information in the block chain node.

2. The method of claim 1, wherein the asset maintenance request comprises:

an asset change execution request, wherein the asset change execution request is used for indicating that a change operation is executed on a business architecture description model; and/or

An asset change rollback request, wherein the asset change rollback request is used for indicating that a change rollback operation is executed on the business architecture description model.

3. The method of claim 2, wherein said determining whether there are n asset maintenance requests of said m asset maintenance requests that have an asset maintenance conflict comprises:

in response to the m asset maintenance requests, sending the approval information corresponding to the m asset maintenance requests to an approval node so that the approval node can return an approval result based on the approval information;

receiving the approval result returned by the approval node;

and if the approval result shows that the m asset maintenance requests are approved, determining whether n asset maintenance requests with asset maintenance conflict exist in the m asset maintenance requests.

4. The method of claim 3, wherein said determining whether there are n asset maintenance requests of said m asset maintenance requests that have an asset maintenance conflict comprises:

if the m asset maintenance requests comprise m asset change execution requests, determining whether n asset maintenance requests with asset change conflict exist based on initial information corresponding to the m asset change execution requests; or

If the m asset maintenance requests comprise m asset change rollback requests, determining whether n asset maintenance requests with asset rollback conflicts exist based on rollback results corresponding to the m asset change rollback requests; or

If the m asset maintenance requests comprise p asset change execution requests and q asset change rollback requests, determining whether n asset maintenance requests in asset completion conflict exist based on initial information corresponding to the p asset change execution requests and rollback results corresponding to the q asset change rollback requests, wherein p and q are positive integers, and p + q is m.

5. The method of claim 1, wherein said processing initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests comprises:

determining whether the asset maintenance conflict is a field information conflict or a semantic information conflict or not according to the initial information of the n asset maintenance requests;

if not, merging the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, wherein the merged information comprises merged maintenance operation and merged maintenance information executed on a business architecture description model;

and determining the merged information corresponding to the n asset maintenance requests and the initial information of m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

6. The method of claim 5, wherein the merging the initial information of the n asset maintenance requests comprises:

in response to the n asset maintenance requests, invoking intelligent contracts of the blockchain nodes, wherein the intelligent contracts are configured with a merging mechanism; and

and merging the initial information of the n asset maintenance requests based on the merging mechanism.

7. The method of claim 5, wherein the method further comprises:

if yes, returning the initial information of the n asset maintenance requests;

and determining the initial information of the m-n asset maintenance requests as target information corresponding to the m asset maintenance requests.

8. The method of claim 5, wherein, in the event that the asset maintenance request comprises an asset change execution request, the performing the targeted maintenance operation on the business architecture description model to obtain maintenance result information based on the targeted maintenance information comprises:

based on the merging information corresponding to the n asset maintenance requests, performing asset change operation on the business architecture description model to obtain a first change result;

based on the initial information of the m-n asset maintenance requests, performing asset change operation on the business architecture description model to obtain a second change result.

9. The method of claim 5, wherein, in the event that the asset maintenance request comprises an asset change fallback request, the performing the target maintenance operation on the business architecture description model to obtain maintenance result information based on the target maintenance information comprises:

based on the merging information corresponding to the n asset maintenance requests, performing asset completion operation on the business architecture description model to obtain a first completion result;

and performing asset completion operation on the business architecture description model based on the initial information of the m-n asset maintenance requests to obtain a second completion result.

10. The method of any of claims 1-9, wherein the method further comprises: and storing the target information corresponding to the m asset maintenance requests in the blockchain node.

11. The method of claim 3, wherein the method further comprises:

and if the approval result shows that the m asset maintenance requests are not approved, storing the initial information of the m asset maintenance requests and the approval result in the block chain node.

12. An information processing apparatus based on a blockchain network, comprising:

an initial maintenance information receiving module, configured to receive initial information of m asset maintenance requests by using a blockchain node of the blockchain network, where the initial information includes an initial maintenance operation and initial maintenance information performed on a service architecture description model, and m is a positive integer greater than or equal to 2;

the asset maintenance conflict determining module is used for determining whether n asset maintenance requests with asset maintenance conflicts exist in the m asset maintenance requests, wherein n is a positive integer greater than or equal to 2 and is less than or equal to m;

a target maintenance information determining module, configured to process initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests if the initial information of the n asset maintenance requests exists, where the target information includes target maintenance operation and target maintenance information used for indicating execution of the business architecture description model;

and the maintenance result information processing module is used for executing the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information and storing the maintenance result information in the block chain node.

13. An electronic device, comprising:

one or more processors; and

a memory for storing one or more programs,

wherein the one or more programs, when executed by the one or more processors, cause the one or more processors to implement the method of any of claims 1-11.

14. A computer-readable storage medium storing computer-executable instructions for implementing the method of any one of claims 1 to 11 when executed.