Information Processing Method, Apparatus, Electronic Device, and Medium

Abstract

The present disclosure provides an information processing method, including receiving, by a blockchain node of a blockchain network, initial information of m asset maintenance requests, including an initial maintenance operation and initial maintenance information performed on a business architecture description model, where m is a positive integer greater than or equal to 2, determining whether there are n asset maintenance requests with asset maintenance conflicts, where n is a positive integer greater than or equal to 2 and n ≤ m, and if so, processing the initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, which is used to indicate a target maintenance operation and target maintenance information performed on the business architecture description model; based on the target maintenance information, performing a target maintenance operation on the business architecture description model to obtain maintenance result information and storing the maintenance result information in the blockchain node. An information processing device, an electronic device, and a medium are also provided. The method and device provided by the present disclosure can be applied to, for example, the financial field or other fields.

Description

Technical Field

[0001] The present disclosure relates to the field of blockchain technology, and in particular, to an information processing method, apparatus, electronic device, and medium based on a blockchain network. Background Art

[0002] The accuracy of the business architecture description model is of great significance for understanding the production and operation status of an enterprise. With the continuous expansion of the business of large enterprises and the continuous improvement of each business of the enterprise, it is manifested that while the existing business is continuously iterated and updated, new businesses will also be successively developed and launched, so that the business architecture description model also needs to be iterated and improved synchronously with the iteration and development of the business. Therefore, it is very important to effectively manage the business architecture description model, so as to timely grasp the changes in the enterprise's business architecture and the corresponding changes in the business.

[0003] At present, for the business architecture description model, related technologies also provide some management methods. For example, a centralized database is used for management, and users browse and use it through the B / S (Browser / Server) mode. However, in the process of implementing the concept of the present disclosure, the inventors found that there are at least the following problems in the related technologies: Since agile development and rapid iteration projects have gradually become important ways for business system development and launch, the update of the business architecture description model has become more frequent and concentrated. If a centralized database is still used to manage the business architecture description model with more frequent and concentrated updates, technical problems such as asset update conflicts and the lack of a mechanism for filling back missing assets will inevitably occur. If these technical problems cannot be effectively solved, it will seriously affect the normal operation of each business of the enterprise. Summary of the Invention

[0004] In view of this, in order to at least partially overcome the technical problems that when using a centralized database to manage the business architecture description model with more frequent and concentrated updates, asset update conflicts and the lack of a mechanism for filling back missing assets will inevitably occur, the present disclosure provides an information processing method, apparatus, electronic device, and medium based on a blockchain network.

[0005] To achieve the above object, an aspect of the present disclosure provides an information processing method based on a blockchain network, which may include: receiving, by a blockchain node of the blockchain network, initial information of m asset maintenance requests, where the initial information includes an initial maintenance operation and initial maintenance information performed on a business architecture description model, and m is a positive integer greater than or equal to 2. Determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, where n is a positive integer greater than or equal to 2 and n ≤ m. If so, processing the initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, where the target information includes a target maintenance operation and target maintenance information for indicating the execution on the business architecture description model. And based on the target maintenance information, performing the target maintenance operation on the business architecture description model to obtain maintenance result information, and storing the maintenance result information in the blockchain node.

[0006] According to an embodiment of the present disclosure, the asset maintenance request may include: an asset change execution request, where the asset change execution request is used to indicate a change operation to be performed on a business architecture description model. And / or an asset change rollback request, where the asset change rollback request is used to indicate a change rollback operation to be performed on the business architecture description model.

[0007] According to an embodiment of the present disclosure, determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests may include: in response to receiving the m asset maintenance requests, sending 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 indicates that the m asset maintenance requests are approved, determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests.

[0008] According to an embodiment of the present disclosure, the n asset maintenance requests for determining whether there is an asset maintenance conflict among the m asset maintenance requests may include: If the m asset maintenance requests include m asset change execution requests, then based on the initial information corresponding to the m asset change execution requests, determine the n asset maintenance requests for whether there is an asset change conflict. Or if the m asset maintenance requests include m asset change rollback requests, then based on the rollback results corresponding to the m asset change rollback requests, determine the n asset maintenance requests for whether there is an asset rollback conflict. Or if the m asset maintenance requests include p asset change execution requests and q asset change rollback requests, then 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, determine the n asset maintenance requests for whether there is an asset filling conflict, where p and q are positive integers and p + q = m.

[0009] According to an embodiment of the present disclosure, the processing of the initial information of the n asset maintenance requests to determine the target information corresponding to the m asset maintenance requests may include: For the initial information of the n asset maintenance requests, determine whether the asset maintenance conflict is a field information conflict or a semantic information conflict. If not, then merge the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, where the merged information includes the merge maintenance operations and merge maintenance information performed on the business architecture description model. And determine the merged 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.

[0010] According to an embodiment of the present disclosure, the merging of the initial information of the n asset maintenance requests may include: In response to the n asset maintenance requests, call the smart contract of the blockchain node, where the smart contract is configured with a merging mechanism. And based on the merging mechanism, merge the initial information of the n asset maintenance requests.

[0011] According to an embodiment of the present disclosure, the method may further include: If so, return the initial information of the n asset maintenance requests. And determine the initial information of the m - n asset maintenance requests as the target information corresponding to the m asset maintenance requests.

[0012] According to an embodiment of the present disclosure, when 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: performing an asset change operation on the business architecture description model based on the merged information corresponding to the n asset maintenance requests to obtain a first change result. And performing an 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.

[0013] According to an embodiment of the present disclosure, when 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: performing an asset complement operation on the business architecture description model based on the merged information corresponding to the n asset maintenance requests to obtain a first complement result. And performing an asset complement operation on the business architecture description model based on the initial information of the m - n asset maintenance requests to obtain a second complement result.

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

[0015] According to an embodiment of the present disclosure, the method may further include: if the approval result indicates 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 blockchain node.

[0016] 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 the 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 business architecture description model, and m is a positive integer greater than or equal to 2. An asset maintenance conflict determination module, configured to determine whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, where n is a positive integer greater than or equal to 2, and n ≤ m. A target maintenance information determination module, configured to, if any, process the initial information of the n asset maintenance requests to determine the target information corresponding to the m asset maintenance requests, where the target information includes a target maintenance operation and target maintenance information used to indicate performing on the business architecture description model. And a maintenance result information processing module, configured to perform the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information, and store the maintenance result information in the blockchain node.

[0017] According to an embodiment of the present disclosure, the above asset maintenance request may include: an asset change execution request, where the asset change execution request is used to indicate to perform a change operation on the business architecture description model; and / or an asset change rollback request, where the asset change rollback request is used to indicate to perform a change rollback operation on the business architecture description model.

[0018] According to an embodiment of the present disclosure, the above asset maintenance conflict determination module may include: an approval information sending sub-module, configured to, in response to receiving the above m asset maintenance requests, send the approval information corresponding to the above m asset maintenance requests to an approval node, so that the approval node can return an approval result based on the above approval information; an approval result receiving sub-module, configured to receive the above approval result returned by the approval node; and an asset maintenance conflict determination sub-module, configured to, if the above approval result indicates that the above m asset maintenance requests are approved, determine whether there are n asset maintenance requests with asset maintenance conflicts among the above m asset maintenance requests.

[0019] According to an embodiment of the present disclosure, the above asset maintenance conflict determination sub-module may include: an asset maintenance conflict first determination unit, configured to, if the above m asset maintenance requests include m asset change execution requests, determine whether there are n asset maintenance requests with asset change conflicts based on the initial information corresponding to the above m asset change execution requests; or an asset maintenance conflict second determination unit, configured to, if the above m asset maintenance requests include m asset change rollback requests, determine whether there are n asset rollback conflict requests based on the rollback results corresponding to the above m asset change rollback requests; or an asset maintenance conflict third determination unit, configured to, if the above m asset maintenance requests include p asset change execution requests and q asset change rollback requests, determine whether there are n asset complement conflicts based on the initial information corresponding to the above p asset change execution requests and the rollback results corresponding to the above q asset change rollback requests, where p and q are positive integers and p + q = m.

[0020] According to an embodiment of the present disclosure, the above-mentioned target maintenance information determination module may include: an asset maintenance conflict determination sub-module, configured to determine whether the above-mentioned asset maintenance conflict is a field information conflict or a semantic information conflict for the initial information of the above-mentioned n asset maintenance requests. An initial information merging sub-module, configured to, if not, merge the initial information of the above-mentioned n asset maintenance requests to generate merged information corresponding to the above-mentioned n asset maintenance requests, where the above-mentioned merged information includes a merged maintenance operation and merged maintenance information performed on the business architecture description model. And a first target maintenance information determination sub-module, configured to determine the above-mentioned merged information corresponding to the above-mentioned n asset maintenance requests and the initial information of m - n asset maintenance requests as target information corresponding to the above-mentioned m asset maintenance requests.

[0021] According to an embodiment of the present disclosure, the above-mentioned initial information merging sub-module may include: a smart contract invocation unit, configured to, in response to the above-mentioned n asset maintenance requests, invoke the smart contract of the above-mentioned blockchain node, where the above-mentioned smart contract is configured with a merging mechanism. And an initial information merging unit, configured to merge the initial information of the above-mentioned n asset maintenance requests based on the above-mentioned merging mechanism.

[0022] According to an embodiment of the present disclosure, the above-mentioned target maintenance information determination module may further include: an initial information return sub-module, configured to, if so, return the initial information of the above-mentioned n asset maintenance requests. And a second target maintenance information determination sub-module, configured to determine the initial information of the above-mentioned m - n asset maintenance requests as target information corresponding to the above-mentioned m asset maintenance requests.

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

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

[0025] According to an embodiment of the present disclosure, the above device may further include: a target information storage module, configured to store the target information corresponding to the above m asset maintenance requests in the above blockchain node.

[0026] According to an embodiment of the present disclosure, the above asset maintenance conflict determination module may further be configured to: if the above approval result indicates that the above m asset maintenance requests are not approved, store the initial information of the above m asset maintenance requests and the above approval result in the above blockchain node.

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

[0028] To achieve the above object, another aspect of the present disclosure provides a computer-readable storage medium storing computer-executable instructions, which are used to implement the information processing method based on a blockchain network as described above when executed.

[0029] To achieve the above object, another aspect of the present disclosure provides a computer program, the above computer program including computer-executable instructions, which are used to implement the information processing method based on a blockchain network as described above when executed.

[0030] Different from the prior art, the information processing method based on a blockchain network provided by the present disclosure relates to a method for dynamic storage and processing of assets related to asset conflicts in a business architecture description model based on a blockchain network. This method combines the business architecture description model with blockchain technology, and makes full use of the characteristics of immutability and traceability of blockchain technology to store the dynamically iterative update information of assets with asset conflicts in the business architecture description model on the blockchain, which can achieve the traceability of the iteration of the business architecture description model, ensure the timeliness of the model results, reduce asset maintenance conflicts, and ensure the normal operation of each business of the enterprise. BRIEF DESCRIPTION OF THE DRAWINGS

[0031] To more fully understand the present disclosure and its advantages, reference will now be made to the following description in conjunction with the accompanying drawings, in which:

[0032] Figure 1 Schematically shows a system architecture of an information processing method and device based on a blockchain network applicable to an embodiment of the present disclosure;

[0033] Figure 2 Schematically shows a schematic diagram of a business architecture description model according to an embodiment of the present disclosure;

[0034] Figure 3 Schematically shows a flowchart of an information processing method based on a blockchain network according to an embodiment of the present disclosure;

[0035] Figure 4 Schematically shows a flowchart of an information processing method for performing asset change on a business architecture description model based on a blockchain network according to an embodiment of the present disclosure;

[0036] Figure 5 Schematically shows a flowchart of an information processing method for performing asset rollback on a business architecture description model based on a blockchain network according to an embodiment of the present disclosure;

[0037] Figure 6 Schematically shows a block diagram of an information processing apparatus based on a blockchain network according to an embodiment of the present disclosure;

[0038] Figure 7 Schematically shows a schematic diagram of a computer-readable storage medium product suitable for implementing the information processing method based on a blockchain network described above; and

[0039] Figure 8 Schematically shows a block diagram of an electronic device suitable for implementing the information processing method based on a blockchain network described above.

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

[0041] It should be noted that the drawings are not drawn to scale, and for illustrative purposes, elements with similar structures or functions are generally denoted by similar reference numerals throughout the drawings. Detailed Description of the Embodiment

[0042] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. However, it should be understood that these descriptions are merely exemplary and are not intended to limit the scope of the present disclosure. In the following detailed description, for the sake of explanation, numerous specific details are set forth to provide a comprehensive understanding of the embodiments of the present disclosure. However, it is obvious that one or more embodiments may be implemented without these specific details. In addition, in the following description, descriptions of well-known structures and technologies are omitted to avoid unnecessarily obscuring the concepts of the present disclosure.

[0043] The terms used herein are merely for describing specific embodiments and are not intended to limit the present disclosure. The terms "including", "comprising", etc. as used herein indicate the presence of the above-mentioned features, steps, operations, and / or components, but do not exclude 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 meanings commonly understood by those skilled in the art, unless otherwise defined. It should be noted that the terms used herein should be interpreted to have a meaning consistent with the context of this specification and should not be interpreted in an idealized or overly rigid manner.

[0044] In cases where expressions similar to "at least one of A, B, and C, etc." are used, generally, it should be interpreted according to the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, and C" should include, but not be limited to, a system having only A, only B, only C, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.). In cases where expressions similar to "at least one of A, B, or C, etc." are used, generally, it should be interpreted according to the meaning commonly understood by those skilled in the art (for example, "a system having at least one of A, B, or C" should include, but not be limited to, a system having only A, only B, only C, having A and B, having A and C, having B and C, and / or having A, B, and C, etc.).

[0045] Some block diagrams and / or flowcharts are shown in the accompanying drawings. It should be understood that some blocks or combinations of blocks in the block diagrams and / or flowcharts can be implemented by computer program instructions. These computer program instructions can be provided to the processor of a general-purpose computer, a special-purpose computer, or other programmable information processing device, so that when executed by the processor, these instructions can create a device for implementing the functions / operations illustrated in these block diagrams and / or flowcharts. The technology of the present disclosure can be implemented in the form of hardware and / or software (including firmware, microcode, etc.). Additionally, the technology of the present disclosure can take the form of a computer program product on a computer-readable storage medium storing instructions, which can be used by or in conjunction with an instruction execution system.

[0046] With the continuous expansion of the business of large enterprises, each business of the enterprise is also constantly improving, manifested in the continuous iteration and update of the existing business while new businesses will be successively developed and launched, making the business architecture description model also need to be iteratively updated and improved synchronously with the iteration and development of the business. Therefore, it is very important to effectively manage the business architecture description model, which can timely grasp the changes in the enterprise's business architecture and the corresponding changes in the business. Since agile development and rapid iteration projects have gradually become important ways for business system development and launch, the update of the business architecture description model has become more frequent and concentrated. If a centralized database is still used to manage the business architecture description model with more frequent and concentrated updates, technical problems such as asset update conflicts and the lack of a mechanism to supplement missing rollback assets will inevitably occur. If these technical problems are not effectively solved, they will seriously affect the normal operation of each business of the enterprise.

[0047] In view of this, the embodiments of the present disclosure provide an information processing method, device, electronic device, and computer-readable storage medium based on a blockchain network. Among them, the information processing method includes a stage of determining asset maintenance conflicts and a stage of processing asset maintenance information. In the stage of determining asset maintenance conflicts, first, the blockchain nodes of the blockchain network receive the initial information of m asset maintenance requests. The initial information includes the initial maintenance operations and initial maintenance information performed on the business architecture description model, where m is a positive integer greater than or equal to 2. Then, it is determined whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, where n is a positive integer greater than or equal to 2 and n ≤ m. If so, it enters the stage of processing asset maintenance information. First, the initial information of the n asset maintenance requests is processed to determine the target information corresponding to the m asset maintenance requests. The target information includes the target maintenance operations and target maintenance information used to indicate the operations performed on the business architecture description model. Finally, based on the target maintenance information, target maintenance operations are performed on the business architecture description model to obtain maintenance result information, and the maintenance result information is stored in the blockchain node.

[0048] Different from the prior art, the information processing method based on a blockchain network provided by the present disclosure relates to a method for dynamic storage and processing of assets with conflicts in the business architecture description model assets based on a blockchain network. This method combines the business architecture description model with blockchain technology, makes full use of the characteristics of immutability and traceability of blockchain technology, and stores the dynamic iterative update information of assets with conflicts in the business architecture description model on the blockchain, which can achieve the traceability of the iteration of the business architecture description model, ensure the timeliness of the model results, reduce asset maintenance conflicts, and guarantee the normal operation of each business of the enterprise.

[0049] It should be noted that the information processing method and apparatus provided by the present disclosure can be used in the financial field, and can also be used in any field other than the financial field. Therefore, the application field of the information processing method and apparatus provided by the present disclosure is not limited.

[0050] The information processing method and apparatus provided by the present disclosure relate to a business architecture description model and blockchain technology. Blockchain is a new application mode of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm. Blockchain, an important concept of Bitcoin, is essentially a decentralized database. At the same time, as the underlying technology of Bitcoin, it is a string of data blocks generated by using cryptographic methods. Each data block contains information on a batch of Bitcoin network transactions, which is used to verify the validity (anti-counterfeiting) of the information and generate the next block. A block is a storage unit that records all the communication information of each block node within a certain period of time. Each block is linked through a random hash (also known as a hash algorithm). The latter block contains the hash value of the previous block. As the information exchange expands, one block follows another, and the resulting chain is called a blockchain.

[0051] Figure 1 Schematically shows a system architecture 100 of an information processing method and apparatus based on a blockchain network applicable to an embodiment of the present disclosure. It should be noted that Figure 1 The figure shown is only an example of a system architecture to which the embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure, but it does not mean that the embodiments of the present disclosure cannot be used in other devices, systems, environments or scenarios.

[0052] As Figure 1 shown, the 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.

[0053] In the present disclosure, the blockchain network 101 is a set of a series of blockchain nodes that incorporate new blocks into the blockchain through consensus. The blockchain network 101 may include blockchain nodes 1011, 1012, 1013, 1014, 1015, and a network 102. The network 102 is a medium for providing a communication link between multiple blockchain nodes. The network 102 may include various connection types, such as wired, wireless communication links, or fiber optic cables, etc.

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

[0055] It should be understood that Figure 1 the number of blockchain nodes, operation nodes, and approval nodes deployed in

[0056] Figure 2 is merely illustrative. According to implementation requirements, there may be any number of blockchain nodes, operation nodes, and approval nodes. Figure 2 is a schematic diagram of a business architecture description model according to an embodiment of the present disclosure. As

[0057] shown, the business architecture description model 200 may include literal descriptions and association relationships of a business architecture process model 201, a product model 202, and an entity model 203 currently used by an enterprise.

[0058] Process model 201: refers to the division of businesses in different business domains based on the planning, execution, and supervision value streams of the business, dividing each value stream into different activities, decomposing tasks from the activities, and the process description after the tasks are decomposed into steps according to business rules and conditions, with a total of five levels (business domain - value stream - activity - task - step).

[0059] For example, in the process model of banking business, the business domain generally includes but is not limited to: personal deposits, personal accounts, credit cards, personal loans, etc. The value stream generally includes but is not limited to: business planning, business preparation, serving customers, etc. The activity generally includes but is not limited to: formulating management systems, issuing credit cards, withdrawing credit card funds, repaying credit card debts, etc. The task generally includes but is not limited to: identifying individual customers, monitoring real-time fraud risks, accepting credit card fund withdrawal applications, settling foreign exchange, etc. The step generally includes but is not limited to: calculating the customer risk tolerance score, reviewing new individual customer information, initiating sensitive approval applications, account inspections, etc.

[0059] The product model 202 is a set of standard structures defining enterprise products, including product lines, product groups, basic products, salable products, and association relationships between products.

[0060] For example, in the product model of banking services, it generally includes but is not limited to: debit cards, credit cards, quasi-credit cards, international debit cards, etc.

[0061] The entity model 203 records the business content of each business object. Each business object includes a core entity, a life cycle (the state of the core entity), subordinate entities (describing the attribute information of the core entity), the association relationships between business objects, and constraints.

[0062] It should be noted that in addition to the aforementioned process model 201, product model 202, and entity model 203, the business architecture can also include one-to-one or one-to-many association relationships between components at each level.

[0063] It should be noted that Figure 2 The examples shown are only examples of the models included in the business architecture description model to which the embodiments of the present disclosure can be applied, to help those skilled in the art understand the technical content of the present disclosure. However, it does not mean that the business architecture description model of the embodiments of the present disclosure cannot include other models. With the update and continuous expansion of the business, the models included in the business architecture description model will also be continuously iterated and updated.

[0064] In this article, it should be understood that the terms involved in the present invention include blockchain, blockchain network, ledger, smart contract, and consensus. Among them, a blockchain is an encrypted, chained storage structure of transactions formed by blocks. The header of each block can include both the hash value of all transactions in the block and the hash value of all transactions in the previous block, so as to achieve anti-tampering and anti-forgery of transactions in the block based on the hash value; newly generated transactions are filled into the block and, after consensus by nodes in the blockchain network, are appended to the tail of the blockchain to form a chained growth. A blockchain network refers to a set of a series of nodes that incorporate new blocks into the blockchain through consensus. A ledger is a general term for a blockchain (also known as ledger data) and a state database synchronized with the blockchain. Among them, the blockchain records transactions in the form of files in a file system; the state database records transactions in the blockchain in the form of different types of key-value pairs, which is used to support fast query of transactions in the blockchain. A smart contract, also known as chain code or application code, is a program deployed in nodes of a blockchain network. This program is triggered and executed according to conditions. Nodes execute the smart contracts called in the received transactions to perform operations on updating or querying the key-value pair data in the state database. Consensus refers to the process of reaching an agreement on transactions in a block among multiple involved nodes. The blocks that reach an agreement will be appended to the tail of the blockchain. The mechanisms for achieving consensus include proof of work, proof of stake, delegated proof of stake, proof of elapsed time, etc.

[0065] Figure 3The flowchart of the information processing method based on the blockchain network according to an embodiment of the present disclosure is schematically shown. As Figure 3 shown, the method may include operation S310 to operation S340.

[0066] In operation S310, the blockchain nodes of the blockchain network are utilized to receive the initial information of m asset maintenance requests. In the present disclosure, the initial information includes the initial maintenance operations and initial maintenance information performed on the business architecture description model, and m is a positive integer greater than or equal to 2.

[0067] According to an embodiment of the present disclosure, the blockchain nodes may be any one or more of the blockchain nodes as Figure 2 shown. The operation nodes may be any one or more of the operation nodes as Figure 2 shown. The approval nodes may be any one or more of the approval nodes as Figure 2 shown.

[0068] According to an embodiment of the present disclosure, the initial information of the m asset maintenance requests may be sent by the modeling personnel to the blockchain nodes through the operation nodes. Each of the asset maintenance requests is used to indicate the maintenance operations for iteratively updating the business architecture description model, and may include, but is not limited to, adding, editing, deleting, rolling back, and complementing the model descriptions and the association relationships between the components of the model for the Figure 2 process model, entity model, and product model. These maintenance operations will reflect the latest business architecture changes, business project requirements, and the corresponding business changes. The maintenance information may include, but is not limited to, the asset components that describe the model descriptions and the association relationships between the components of the model for the Figure 2 process model, entity model, and product model, and the fields corresponding to the asset components, which are determined according to the business architecture description model.

[0069] Combined with Figure 2 the shown business architecture description model, taking the banking business as an example, assuming that according to the actual business requirements, the next updated version of the application software will provide support for the credit card system to apply for virtual digital credit card business on smartphones. Correspondingly, it is necessary to modify the process model, product model, and entity model in the business architecture description model. Specifically, modify the process model so that the modified process model contains the process of applying for virtual digital credit cards. Modify the product model so that the modified product model adds information such as virtual digital credit cards and product conditions. Modify the entity model so that the modified entity model adds information such as the medium information of digital virtual credit cards.

[0070] In operation S320, it is determined whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests. In the present disclosure, n is a positive integer greater than or equal to 2, and n ≤ m. In the related art, if there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, the n asset maintenance requests will be directly returned to the modeler. In the present disclosure, the following operation S330 will be performed.

[0071] According to an embodiment of the present disclosure, asset maintenance conflicts may include, but are not limited to, formal conflicts and substantive conflicts. Among them, formal conflicts include, but are not limited to, potential conflicts occurring in two or more asset updates, but in fact, no changes are made to the same asset component or field, or semantic conflicts occur in changes made to the same asset component, while substantive conflicts may include, but are not limited to, conflicts occurring in two or more asset updates and changes being made to the same asset component or field.

[0072] In the related art, if there are n asset maintenance requests with asset maintenance conflicts, the n asset maintenance requests with asset maintenance conflicts will be directly returned to the sender. According to an embodiment of the present disclosure, the initial information with conflicts will be processed to obtain target information.

[0073] In operation S330, if any exist, the initial information of the n asset maintenance requests is processed to determine the target information corresponding to the m asset maintenance requests, where the target information includes the target maintenance operation and target maintenance information for indicating the execution of the business architecture description model.

[0074] 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. Different types of asset conflicts result in different processing methods for the initial information of the n asset maintenance requests.

[0075] In operation S340, based on the target maintenance information, the target maintenance operation is performed on the business architecture description model to obtain the maintenance result information, and the maintenance result information is stored in the blockchain node.

[0076] According to an embodiment of the present disclosure, if there are no n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, the initial maintenance operation can be directly performed on the business architecture description model based on the initial maintenance information included in the m asset maintenance requests in response to the received m asset maintenance requests to obtain the maintenance result information, and the maintenance result information is stored in the blockchain node.

[0077] Through the embodiments of the present disclosure, by making full use of the characteristics of immutability and traceability of blockchain technology, in the case of asset request conflicts, the initial information is processed to obtain target information, asset maintenance is performed 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 blockchain, which can realize the traceability of the business architecture description model iteration, ensure the timeliness of the model results, reduce asset maintenance conflicts, and guarantee the normal operation of each business of the enterprise.

[0078] After introducing the basic principles of the present disclosure, the various non-limiting embodiments of the present disclosure will be specifically introduced below.

[0079] As an optional embodiment, the asset maintenance request includes: an asset change execution request, where the asset change execution request is used to indicate to perform a change operation on the business architecture description model. And / or an asset change rollback request, where the asset change rollback request is used to indicate to perform a change rollback operation on the business architecture description model.

[0080] According to the embodiments of the present disclosure, the asset maintenance request may only include an asset change execution request, may only include an asset change rollback request, or may include both an asset change execution request and an asset change rollback request. According to the iterative update situation of the actual business, the corresponding asset maintenance request can be determined.

[0081] In the present disclosure, the change operation may include, but is not limited to, operations such as adding, editing, deleting, rollback, and complementing the model description and the association relationship between the components of the process model, entity model, and product model. Correspondingly, the change rollback operation may include, but is not limited to, the rollback operation of the operations such as adding, editing, deleting, rollback, and complementing the model description and the association relationship between the components of the process model, entity model, and product model, that is, performing an undo operation on the previously executed update operation.

[0082] Through the embodiments of the present disclosure, the information processing method based on the blockchain network supports asset maintenance requests with various change contents, making the iterative update management of the business architecture description model more comprehensive and improving the real-time performance and reliability of the business architecture description model.

[0083] As an alternative embodiment, determining the n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests includes: in response to receiving the m asset maintenance requests, 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. Receiving the approval result returned by the approval node. And if the approval result indicates that the m asset maintenance requests are approved, determining the n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests. This approval result can only confirm the business correctness of the asset maintenance request, but does not consider whether there are asset maintenance conflicts in the asset maintenance request.

[0084] As an alternative embodiment, if the approval result indicates that the m asset maintenance requests are not approved, store the initial information and approval result of the m asset maintenance requests in the blockchain node, and keep other asset information unchanged.

[0085] Through the embodiments of the present disclosure, when the asset maintenance request is approved, the asset maintenance conflict is detected to determine whether there is an asset maintenance conflict, and the asset maintenance requests that do not meet the requirements can be quickly feedback through approval, saving the resources of information processing.

[0086] It can be understood that the asset maintenance request for the business architecture model includes the maintenance operation information to be executed and the object to be maintained. The object can be one or more asset components in the business architecture description model, or one or more fields of the asset component.

[0087] As an alternative embodiment, determining the n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests may include: if the m asset maintenance requests include m asset change execution requests, determining the n asset maintenance requests with asset change conflicts based on the initial information corresponding to the m asset change execution requests.

[0088] Example 1: Receive 2 asset maintenance requests, namely Asset Change 1 and Asset Change 2. Among them, Asset Change 1 is used to indicate modifying the "cooperating party" field of the "credit card issuance" activity. The initial information corresponding to Asset Change 1 is modifying the "cooperating party" field of the "credit card issuance" activity. The initial maintenance operation is modification, and the initial maintenance information is the "cooperating party" field of the "credit card issuance" activity. Asset Change 2 is used to indicate modifying the "purpose" field of the "credit card issuance" activity. The initial information corresponding to Asset Change 2 is modifying the "purpose" field of the "credit card issuance" activity. The initial maintenance operation is also modification, and the initial maintenance information is the "purpose" field of the "credit card issuance" activity. Since both are for the same asset component or field, it can be determined that the asset maintenance conflict between Asset Change 1 and Asset Change 2 is a formal conflict.

[0089] Example 2: Two asset maintenance requests are received, namely Asset Change 3 and Asset Change 4. Asset Change 3 is used to indicate adding the association of the "stakeholder" between the "People's Bank" and the "credit card issuance" activity. The initial information corresponding to Asset Change 3 is adding the association of the "stakeholder" between the "People's Bank" and the "credit card issuance" activity. The initial maintenance operation is addition, and the initial maintenance information is the association of the "stakeholder" between the "People's Bank" and the "credit card issuance" activity. Asset Change 4 is used to indicate adding the association of the "stakeholder" between the "VISA organization" and the "credit card issuance" activity. The initial information corresponding to Asset Change 4 is adding the association of the "stakeholder" between the "VISA organization" and the "credit card issuance" activity. The initial maintenance operation is also addition, and the initial maintenance information is the association of the "stakeholder" between the "VISA organization" and the "credit card issuance" activity. Since both of them are making semantically conflicting changes to the same asset component, it can be determined that the asset maintenance conflict between Asset Change 3 and Asset Change 4 is a formal conflict.

[0090] Example 3: Two asset maintenance requests are received, namely Asset Change 5 and Asset Change 6. Asset Change 5 is used to indicate modifying the "cooperating party" field of the "credit card issuance" activity, changing "Airline Company" to "Transportation Enterprise". The initial information corresponding to Asset Change 5 is modifying the "cooperating party" field of the "credit card issuance" activity, changing "Airline Company" to "Transportation Enterprise". The initial maintenance operation is modification, and the initial maintenance information is that the "cooperating party" field of the "credit card issuance" activity changes from "Airline Company" to "Transportation Enterprise". Asset Change 6 is used to indicate modifying the "cooperating party" field of the "credit card issuance" activity, changing "Airline Company" to "Airline Company (Passenger Transport)". The initial information corresponding to Asset Change 6 is modifying the "cooperating party" field of the "credit card issuance" activity, changing "Airline Company" to "Airline Company (Passenger Transport)". The initial maintenance operation is also modification, and the initial maintenance information is that the "cooperating party" field of the "credit card issuance" activity changes from "Airline Company" to "Airline Company (Passenger Transport)". Since both of them are modifying the "cooperating party" field of the same "credit card issuance" activity and the modification content has a semantic conflict, it can be determined that the asset maintenance conflict between Asset Change 5 and Asset Change 5 is a substantial conflict.

[0091] It should be noted that the above several embodiments are only for better explaining how to determine whether there are conflicts among multiple asset maintenance requests and the types of conflicts according to asset components and fields, and are not the only conflict scenarios or types. According to the specific situation of the business architecture description model and asset maintenance requests, there can be initial information in any form, and the present disclosure does not make any limitations.

[0092] As an alternative embodiment, determining the n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests may include: if the m asset maintenance requests include m asset change rollback requests, determining the n asset maintenance requests with asset rollback conflicts based on the rollback results corresponding to the m asset change rollback requests.

[0093] As an alternative embodiment, determining the n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests may include: if the m asset maintenance requests include p asset change execution requests and q asset change rollback requests, determining the n asset maintenance requests with asset replenishment conflicts 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, where p and q are positive integers and p + q = m.

[0094] According to the embodiments of the present disclosure, the basic principle of the automatic asset replenishment process is similar to the aforementioned conflict resolution process. The replenishment process also needs to detect whether there are asset replenishment conflicts through a smart contract, and there are two cases at this time. Specifically, when implemented, if the rollback approval is passed, record the business architecture description model and model content (information such as asset components and fields) that were proposed for rollback when the application was submitted, and the desired rollback result. The above content is called rollback reference snapshot data, and the information of the business architecture description model after rollback is added to the blockchain. Trigger the automatic asset automatic replenishment process.

[0095] Case 1: The assets to be replenished have no association with the rollback reference snapshot data, or different asset components or fields are changed, or semantically conflicting changes are made to the same asset component. In this case, it can be considered that the replenishment action and the rollback asset do not conflict, and the content of the asset replenishment that does not actually conflict can be merged through the merge rules set in the smart contract, and the replenishment content is written into the block. For example, asset change 3, asset change 4, and asset change 5 as described above. The operation sequence of the asset changes is that after asset change 3, asset change 4 and asset change 5 occurred sequentially. Now it is necessary to roll back asset change 3. After the block data is rolled back, the block data has returned to the state before asset change 3 occurred. Judging from the actual change content, there are no field conflicts or semantic conflicts among these three changes, that is, the conflict type is a formal conflict, then the two block data change operations of asset change 4 and asset change 5 are automatically initiated sequentially, and the architecture assets can be replenished.

[0096] Case 2: The assets to be supplemented and the rollback reference snapshot data both need to make conflicting changes to the same asset component or field, or make opposite changes to the same asset component (equivalent to changing the rollback content back to before the rollback). Here, it can be considered that two or more asset updates conflict and cannot be automatically processed. At this time, the applicant needs to be prompted that automatic supplementation is not possible. If data needs to be supplemented, an asset change operation needs to be initiated separately to achieve the supplementation action. For example, as described above for Asset Change 4, Asset Change 5, and Asset Change 8, where Asset Change 8 is used to indicate the deletion of the partner "Airline (Passenger Transport)" for the "Credit Card Issuance" activity. The operation sequence of the asset changes is that after Asset Change 4, Asset Change 5 and Asset Change 8 occurred in sequence. Now it is necessary to roll back Asset Change 4. After the block data is rolled back, the block data has returned to the state before Asset Change 4 occurred. Judging from the actual change content, these three changes are all operations on the "partner" of the "Credit Card Issuance" activity, with field conflicts or semantic conflicts, that is, the conflict type is a substantial conflict, then the applicant will be notified and prompted that the assets cannot be automatically supplemented. It should be noted that the method for determining asset rollback conflicts and asset supplementation conflicts can refer to the method for determining asset change conflicts, which will not be elaborated here.

[0097] As an optional embodiment, processing the initial information of n asset maintenance requests to determine the target information corresponding to m asset maintenance requests includes: for the initial information of n asset maintenance requests, determining whether the asset maintenance conflict is a field information conflict or a semantic information conflict. If not, then merging the initial information of n asset maintenance requests to generate the merged information corresponding to n asset maintenance requests, where the merged information includes the merge maintenance operations and merge maintenance information performed on the business architecture description model, and determining the merged information corresponding to n asset maintenance requests and the initial information of m - n asset maintenance requests as the target information corresponding to m asset maintenance requests.

[0098] According to an embodiment of the present disclosure, if the 3 asset maintenance requests include, in addition to Asset Change 1 and Asset Change 2 in the foregoing Example 1, 1 Asset Change 7, and Asset Change 7 does not conflict with Asset Change 1 and Asset Change 2, then the merged information corresponding to these 2 asset maintenance requests can be generated by merging Asset Change 1 and Asset Change 2. The merged information is to modify the "partner" field and the "purpose" field of the "Credit Card Issuance" activity, that is, the merge maintenance operation is to modify, and the merge maintenance information is the "partner" field and the "purpose" field of the "Credit Card Issuance" activity. Determining the merged maintenance information and Asset Change 7 as the target information corresponding to 3 asset maintenance requests.

[0099] It should be noted that the generated merged information corresponding to n asset maintenance requests can be one piece of information or multiple pieces of information, and the present disclosure does not limit this.

[0100] Through the embodiments of the present disclosure, in the case where the asset maintenance conflict is a field information conflict or a semantic information conflict, the initial information of n asset maintenance requests can be processed to generate one or more merged information corresponding to the n asset maintenance requests, avoiding the technical problem in the related art of directly returning the n asset maintenance requests to the sender. This can not only reduce the number of model changes and avoid frequent changes, but also reduce the information storage burden on the blockchain by merging the asset maintenance requests.

[0101] As an alternative embodiment, merging the initial information of n asset maintenance requests includes: in response to the n asset maintenance requests, invoking the smart contract of the blockchain node, where the smart contract is configured with a merging mechanism. And based on the merging mechanism, merging the initial information of the n asset maintenance requests.

[0102] According to the embodiments of the present disclosure, for the information of asset maintenance requests that can be merged, the different fields or parameter data modified in the change can be merged through the merging mechanism set in the smart contract, merging multiple operations on the asset into one operation, and writing the update content into the block at one time. This can reduce the number of changes and improve the speed of model iteration and update.

[0103] As an alternative embodiment, the method further includes: if it is determined that the asset maintenance conflict is a field information conflict or a semantic information conflict, then returning the initial information of the n asset maintenance requests. And determining the initial information of the m - n asset maintenance requests as the target information corresponding to the m asset maintenance requests.

[0104] According to the embodiments of the present disclosure, in the case where the change field information conflict or semantic information conflict is determined, it is considered that it needs to be returned to the applicant, so that the applicant can modify the change, submit a change request again, or wait for the blockchain to automatically synchronize and then re - apply with the latest asset as the baseline.

[0105] Through the embodiments of the present disclosure, all the full - volume change information of the business architecture description model is uploaded to the blockchain, and the change path of the business architecture description model can be made public. The blockchain technology ensures that the information will not be tampered with, realizing the automatic processing of conflicts between changes, thereby improving the timeliness and reliability of the business architecture description model data.

[0106] As an optional embodiment, in the case where the asset maintenance request includes an asset change execution request, based on the target maintenance information, performing a target maintenance operation on the business architecture description model to obtain maintenance result information includes: based on the merged information corresponding to 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 mn asset maintenance requests, performing an asset change operation on the business architecture description model to obtain a second change result.

[0107] According to an embodiment of the present disclosure, if the three asset maintenance requests include not only asset change 1 and asset change 2 in the aforementioned example 1, but also one asset change 7, then an asset change operation can be performed on the business architecture description model once to complete the asset changes of asset change 1 and asset change 2. Then, asset change 7 is executed to complete the asset change corresponding to asset change request 7.

[0108] Figure 4 The flowchart of executing asset changes on the business architecture description model based on the blockchain network according to an embodiment of the present disclosure is schematically shown.

[0109] like Figure 4 As shown, the information processing method 400 for executing asset changes on the business architecture description model involves the interaction between the modeler 410, the approval personnel 430 and the blockchain network 420, which may include operations S411 and S412, as well as operations S421 to S427. In specific implementation, the modeler 410 performs operation S411 to submit a model change request to the blockchain network 420. 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. Then, operation S422 is performed to send the change approval information to the approval personnel 430. Then, operation S423 is performed to receive the change approval result. Then, operation S424 is performed to associate and map the model change request with the approval information. If the approval result indicates that the approval is passed, that is, the change is agreed, operation S425 is performed to add the modified business architecture description model information to the blockchain. Then, operation S426 is performed to identify and handle conflicts. If the identified conflict indicates that the change request can be merged and does not cause field conflicts or semantic conflicts, then merge the change requests that do not cause field conflicts or semantic conflicts. If the identified conflict indicates that the change request cannot be merged and cannot be processed automatically, then execute operation S412 and return to the modeler for manual processing. If the approval result indicates that the approval is not passed, that is, the change is not approved, then execute operation S427 to add the business architecture description model information and approval results before this modification to the blockchain.

[0110] Through the embodiments of the present disclosure, the problem of update conflicts of multiple business architecture assets during model maintenance is solved, and the change result information is uploaded to the blockchain, enabling automated management of information related to asset maintenance.

[0111] As an alternative embodiment, when the asset maintenance request includes an asset change rollback request, performing a target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information includes: performing an asset supplementation operation on the business architecture description model based on the merge information corresponding to n asset maintenance requests to obtain a first supplementation result. And performing an asset supplementation operation on the business architecture description model based on the initial information of m - n asset maintenance requests to obtain a second supplementation result.

[0112] Through the embodiments of the present disclosure, all full - volume change information of the business architecture description model is uploaded to the blockchain, and the change path of the business architecture description model can be made public. Blockchain technology ensures that the information will not be tampered with, enabling automatic re - supplementation of rollback assets according to the change history path, thereby improving the timeliness and reliability of the data of the business architecture description model.

[0113] Figure 5 Schematically shows a flowchart of performing asset rollback on a business architecture description model based on a blockchain network according to an embodiment of the present disclosure.

[0114] As Figure 5As shown in the figure, the information processing method 500 for performing asset rollback on the business architecture description model involves the interaction between the modeler 410, the approver 430, and the blockchain network 420, and may include operations S511 to S514, and operations S521 to S528. Specifically, when implemented, the modeler 410 performs operation S511 to submit a model change rollback request to the blockchain network 420. After receiving the model change rollback request, the blockchain network 420 may first perform operation S521 to query in the smart contract. Then it performs operation S512 to return the asset change record that needs to be rolled back to the modeler 410. The modeler 410 performs operation S522 to send the asset change record that needs to be rolled back to the approver 430 so that the approver 430 can return an approval result based on the received asset change record that needs to be rolled back. Then it performs operation S523 to receive the change rollback approval result. It performs operation S524 to perform an associated mapping between the model change rollback request and the approval information. If the approval result indicates that the approval is passed, that is, the change rollback is agreed, then it performs operation S525 to add the rolled-back business architecture description model information to the blockchain. Then it performs operation S526 for conflict identification and asset supplementation. If the identified conflict indicates that the change request can be merged without causing field conflicts or semantic conflicts, then the asset change is automatically performed. It performs operation S513. If it cannot be automatically supplemented, it returns to the modeler for manual processing, prompting the modeler that it cannot be automatically supplemented. If the approval result indicates that the approval is not passed, that is, the change rollback is not agreed, then it performs operation S527 to add the current rollback request information and the approval result to the blockchain. Finally, it performs operation S528 to notify the approver of the rolled-back business architecture description model information, and performs operation S514 to notify the modeler of the rolled-back business architecture description model information.

[0115] Through the embodiments of the present 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, and the automatic backfill of assets after rollback can be realized, which can improve the timeliness and reliability of the business architecture description model data.

[0116] As an optional embodiment, the method further includes: storing the target information corresponding to m asset maintenance requests in the blockchain node. Optionally, the asset maintenance request can also be associated and mapped with the approval information, which can realize that all the full-scale change information of the business architecture description model is uploaded to the blockchain, facilitating the traceability of the asset maintenance information.

[0117] It should be noted that for other operations on the business architecture description model, such as query, backtracking the change history, block storage processing, etc., since they do not involve the conflict handling of asset changes, the present disclosure will not elaborate.

[0118] Figure 6A block diagram of an information processing apparatus based on a blockchain network according to an embodiment of the present disclosure is schematically shown. As Figure 6 shown, 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.

[0119] The initial maintenance information receiving module 610 is configured to receive initial information of m asset maintenance requests by using a blockchain node of the blockchain network. The initial information includes an initial maintenance operation and initial maintenance information performed on a business architecture description model, where m is a positive integer greater than or equal to 2. Optionally, the initial maintenance information receiving module 610 may be configured to perform, for example, Figure 3 the operation S310 described, which will not be elaborated here.

[0120] The asset maintenance conflict determination module 620 is configured to determine whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, where n is a positive integer greater than or equal to 2, and n ≤ m. Optionally, the asset maintenance conflict determination module 620 may be configured to perform, for example, Figure 3 the operation S320 described, which will not be elaborated here.

[0121] The target maintenance information determination module 630 is configured to, if any, process the initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, where the target information includes a target maintenance operation and target maintenance information for indicating an operation performed on the business architecture description model. Optionally, the target maintenance information determination module 630 may be configured to perform, for example, Figure 3 the operation S330 described, which will not be elaborated here.

[0122] The maintenance result information processing module 640 is configured to perform a target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information, and store the maintenance result information in the blockchain node. Optionally, the maintenance result information processing module 640 may be configured to perform, for example, Figure 3 the operation S340 described, which will not be elaborated here.

[0123] As an optional embodiment, the asset maintenance request includes: an asset change execution request, where the asset change execution request is used to indicate a change operation performed on the business architecture description model. And / or an asset change rollback request, where the asset change rollback request is used to indicate a change rollback operation performed on the business architecture description model.

[0124] As an alternative embodiment, the asset maintenance conflict determination module includes: an approval information sending sub-module, configured to send approval information corresponding to m asset maintenance requests to an approval node in response to receiving the m asset maintenance requests, so that the approval node can return an approval result based on the approval information; an approval result receiving sub-module, configured to receive the approval result returned by the approval node; and an asset maintenance conflict determination sub-module, configured to determine whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests if the approval result indicates that the m asset maintenance requests are approved.

[0125] As an alternative embodiment, the asset maintenance conflict determination sub-module includes: a first asset maintenance conflict determination unit, configured to determine whether there are n asset maintenance requests with asset change conflicts based on initial information corresponding to m asset change execution requests if the m asset maintenance requests include the m asset change execution requests; or a second asset maintenance conflict determination unit, configured to determine whether there are n asset rollback conflict asset maintenance requests based on rollback results corresponding to m asset change rollback requests if the m asset maintenance requests include the m asset change rollback requests; or a third asset maintenance conflict determination unit, configured to determine whether there are n asset replenishment conflict asset maintenance requests based on the initial information corresponding to p asset change execution requests and the rollback results corresponding to q asset change rollback requests if the m asset maintenance requests include p asset change execution requests and q asset change rollback requests, where p and q are positive integers and p + q = m.

[0126] As an alternative embodiment, the target maintenance information determination module includes: an asset maintenance conflict determination sub-module, configured to determine whether an asset maintenance conflict is a field information conflict or a semantic information conflict for initial information of n asset maintenance requests; an initial information merging sub-module, configured to, if not, merge the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, where the merged information includes merged maintenance operations and merged maintenance information performed on a business architecture description model; and a first target maintenance information determination sub-module, configured to determine 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.

[0127] As an alternative embodiment, the initial information merging sub-module includes: a smart contract calling unit, configured to call a smart contract of a blockchain node in response to the n asset maintenance requests, where the smart contract is configured with a merging mechanism; and an initial information merging unit, configured to merge the initial information of the n asset maintenance requests based on the merging mechanism.

[0128] As an alternative embodiment, the target maintenance information determination module further includes: an initial information return sub-module, configured to, if so, return the initial information of n asset maintenance requests. And a second target maintenance information determination sub-module, configured to determine the initial information of m - n asset maintenance requests as the target information corresponding to the m asset maintenance requests.

[0129] As an alternative embodiment, when the asset maintenance request includes an asset change execution request, the maintenance result information processing module includes: a first change result obtaining module, configured to perform an asset change operation on the business architecture description model based on the merged information corresponding to the n asset maintenance requests to obtain a first change result. And a second change result obtaining module, configured to perform an asset change operation on the business architecture description model based on the initial information of m - n asset maintenance requests to obtain a second change result.

[0130] As an alternative embodiment, when the asset maintenance request includes an asset change rollback request, the maintenance result information processing module includes: a first completion result obtaining module, configured to perform an asset completion operation on the business architecture description model based on the merged information corresponding to the n asset maintenance requests to obtain a first completion result. And a second completion result obtaining module, configured to perform an asset completion operation on the business architecture description model based on the initial information of m - n asset maintenance requests to obtain a second completion result.

[0131] As an alternative embodiment, the apparatus further includes: a target information storage module, configured to store the target information corresponding to the m asset maintenance requests in a blockchain node.

[0132] As an alternative embodiment, the asset maintenance conflict determination module is further configured to: if the approval result indicates that the approval of the m asset maintenance requests fails, store the initial information of the m asset maintenance requests and the approval result in a blockchain node.

[0133] It should be noted that, for some embodiments of the information apparatus based on the blockchain network, the implementation manners, the technical problems solved, the functions achieved, and the technical effects achieved by each module are respectively the same as or similar to those of the corresponding steps in some embodiments of the information method based on the blockchain network, and will not be elaborated herein.

[0134] Any plurality of modules, sub-modules, units according to embodiments of the present disclosure, or at least part of the functions of any of them may be implemented in one module. Any one or more of the modules and sub-modules according to embodiments of the present disclosure may be split into multiple modules for implementation. Any one or more of the modules, sub-modules, units according to embodiments of the present disclosure 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 by hardware or firmware in any other reasonable way of integrating or packaging circuits, or may be implemented in any one of the three implementation manners of software, hardware, and firmware, or in any appropriate combination of several of them. Alternatively, one or more of the modules, sub-modules, units according to embodiments of the present disclosure may be at least partially implemented as a computer program module, and when the computer program module is run, the corresponding functions may be executed.

[0135] For example, the initial maintenance information receiving module, the asset maintenance conflict determination module, the target maintenance information determination module, the maintenance result information processing module, the approval information sending sub-module, the approval result receiving sub-module, the asset maintenance conflict determination sub-module, the first asset maintenance conflict determination unit, the second asset maintenance conflict determination unit, the third asset maintenance conflict determination unit, the asset maintenance conflict determination sub-module, the initial information merging sub-module, the first target maintenance information determination sub-module, the smart contract calling unit, the initial information merging unit, the initial information returning sub-module, the second target maintenance information determination sub-module, the first change result obtaining module, the second change result obtaining module, the first complementing result obtaining module, the second complementing result obtaining module, and the target information storage module can be combined and implemented in one module, or any one of them can be split into multiple modules. Alternatively, at least part of the functions of one or more of these modules can be combined with at least part of the functions of other modules and implemented in one module. According to an embodiment of the present disclosure, at least one of the initial maintenance information receiving module, the asset maintenance conflict determination module, the target maintenance information determination module, the maintenance result information processing module, the approval information sending sub-module, the approval result receiving sub-module, the asset maintenance conflict determination sub-module, the first asset maintenance conflict determination unit, the second asset maintenance conflict determination unit, the third asset maintenance conflict determination unit, the asset maintenance conflict determination sub-module, the initial information merging sub-module, the first target maintenance information determination sub-module, the smart contract calling unit, the initial information merging unit, the initial information returning sub-module, the second target maintenance information determination sub-module, the first change result obtaining module, the second change result obtaining module, the first complementing result obtaining module, the second complementing result obtaining module, and the target information storage module can 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 can be implemented by any other reasonable way of integrating or packaging circuits, etc., by hardware or firmware, or can be implemented in any one of the three implementation ways of software, hardware, and firmware, or in any appropriate combination of several of them.Alternatively, at least one of the initial maintenance information receiving module, the asset maintenance conflict determination module, the target maintenance information determination module, the maintenance result information processing module, the approval information sending sub-module, the approval result receiving sub-module, the asset maintenance conflict determination sub-module, the first asset maintenance conflict determination unit, the second asset maintenance conflict determination unit, the third asset maintenance conflict determination unit, the asset maintenance conflict determination sub-module, the initial information merging sub-module, the first target maintenance information determination sub-module, the smart contract calling unit, the initial information merging unit, the initial information returning sub-module, the second target maintenance information determination sub-module, the first change result obtaining module, the second change result obtaining module, the first complementing result obtaining module, the second complementing result obtaining module, and the target information storage module can be at least partially implemented as a computer program module, and when the computer program module runs, it can execute corresponding functions.

[0136] Figure 7 FIG. schematically shows a schematic diagram of a computer-readable storage medium product suitable for implementing the information processing method based on a blockchain network described above according to an embodiment of the present disclosure.

[0137] In some possible implementation manners, various aspects of the present invention can also be implemented in the form of a program product, which includes program code. When the program product runs on a device, the program code is used to cause the device to execute the foregoing operations (or steps) in the information processing method according to various exemplary embodiments of the present invention described in the "Exemplary Method" section of this specification. For example, an electronic device can execute operations S310 to S340 as shown in Figure 3 , or can also execute operation S411 and operation S412, and operations S421 to S427 as shown in Figure 4 . Operations S511 to S514, and operations S521 to S528 as shown in Figure 5 .

[0138] The program product can adopt any combination of one or more readable media. The readable media can be a readable signal medium or a readable storage medium. The readable storage medium can be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any combination of the above. More specific examples (non-exhaustive list) of the readable storage medium include: an electrical connection with 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 disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the above.

[0139] As shown in Figure 7As shown, a program product 700 for information processing according to an embodiment of the present invention is described. It may be in the form of a portable compact disc read-only memory (CD-ROM) and include program code, and can run on a device such as a personal computer. However, the program product of the present invention is not limited thereto. In this document, a readable storage medium may be any tangible medium that contains or stores a program that can be used by or in conjunction with an instruction execution system, system, or device.

[0140] A readable signal medium may include a data signal propagated in a baseband or as part of a carrier wave, in which the readable program code is carried. Such a propagated data signal may take various forms, including - but not limited to - electromagnetic signals, optical signals, or any suitable combination of the above. A readable signal medium may also be any readable medium other than a readable storage medium that can send, propagate, or transmit a program for use by or in conjunction with an instruction execution system, system, or device. The program code contained on the readable medium may be transmitted using any appropriate medium, including - but not limited to - wireless, wired, optical fiber, RF, etc., or any suitable combination of the above.

[0141] The program code for performing the operations of the present invention may be written in any combination of one or more programming languages, including object-oriented programming languages such as Java, C++, etc., and also including conventional procedural programming languages such as "C", languages or similar programming languages. The program code may be executed entirely on the user's computing device, partially on the user's computing device and partially on a remote computing device, or entirely on a remote computing device or server. In the case of a remote computing device, the remote computing device may be connected to the user's computing device through any type of network - including a local area network (LAN) or a wide area network (WAN) - or, alternatively, may be connected to an external computing device (e.g., through the Internet using an Internet service provider).

[0142] Figure 8 A block diagram of an electronic device suitable for implementing the information processing method based on a blockchain network described above according to an embodiment of the present disclosure is schematically shown. Figure 8 The electronic device shown is only an example and should not impose any limitations on the functions and scope of use of the embodiments of the present disclosure.

[0143] As Figure 8As shown, the electronic device 800 according to an embodiment of the present disclosure includes a processor 801, which 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 (such as a CNU), an instruction set processor, and / or a related chipset, and / or a dedicated microprocessor (such as an application-specific integrated circuit (ASIC)), and so on. The processor 801 may also include on-board memory for caching purposes. The processor 801 may include a single processing unit or multiple processing units for performing different actions of the method flow according to an embodiment of the present disclosure.

[0144] In the RAM 803, various programs and data required for the operation of the electronic device 800 are stored. The processor 801, the ROM 802, and the RAM 803 are connected to each other via a bus 804. The processor 801 performs various operations of the method flow according to an embodiment of the present disclosure by executing the programs in the ROM 802 and / or the RAM 803. It should be noted that the program may also be stored in one or more memories other than the ROM 802 and the RAM 803. The processor 801 may also perform the operations S310 to S340 shown in Figure 3 an embodiment of the present disclosure by executing the program stored in the one or more memories. The electronic device may also perform the operations S411 and S412, and the operations S421 to S427 shown in Figure 4 an embodiment of the present disclosure. The electronic device may also perform the operations S511 to S514, and the operations S521 to S528 shown in Figure 5 an embodiment of the present disclosure.

[0145] According to an embodiment of the present disclosure, the electronic device 800 may further include an input / output (I / O) interface 805, and the input / output (I / O) interface 805 is also connected to the bus 804. The system 800 may further include one or more of the following components connected to the I / O interface 805: an input section 806 including a keyboard, a mouse, etc.; an output section 807 including, for example, a cathode ray tube (CRT), a liquid crystal display (LCD), etc., and a speaker, etc.; a storage section 808 including a hard disk, etc.; and a communication section 809 including a network interface card such as an LAA card, a modem, etc. 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 needed. A removable medium 811, such as a magnetic disk, an optical disk, a magneto-optical disk, a semiconductor memory, etc., is installed on the drive 810 as needed so that a computer program read from it can be installed into the storage section 808 as needed.

[0146] According to an embodiment of the present disclosure, the method flow according to the embodiment of the present disclosure can be implemented as a computer software program. For example, an embodiment of the present disclosure includes a computer program product, which includes a computer program carried on a computer-readable storage medium, and the computer program includes program codes for executing the method shown in the flowchart. In such an embodiment, the computer program can be downloaded and installed from the network through the communication part 809, and / or installed from the removable medium 811. When the computer program is executed by the processor 801, the above functions defined in the system according to the embodiment of the present disclosure are executed. According to an embodiment of the present disclosure, the above-described system, device, apparatus, module, unit, etc. can be implemented by computer program modules.

[0147] The present disclosure also provides a computer-readable storage medium, which may be included in the device / device / system described in the above embodiment; or may exist alone without being assembled into the device / device / system. The above computer-readable storage medium carries one or more programs, and when the above one or more programs are executed, an information processing method according to an embodiment of the present disclosure is implemented, including Figure 3 the operations S310 to S340 shown in. The electronic device can also execute operations such as Figure 4 the operations S411 and S412, and operations S421 to S427 shown in. The electronic device can also execute operations such as Figure 5 the operations S511 to S514, and operations S521 to S528 shown in.

[0148] According to an embodiment of the present disclosure, the computer-readable storage medium may be a non-volatile computer-readable storage medium, for example, it may include but is not limited to: portable computer disks, hard disks, random access memories (RAMs), read-only memories (ROMs), erasable programmable read-only memories (ENROMs or flash memories), portable compact disk read-only memories (CD-ROMs), optical storage devices, magnetic storage devices, or any suitable combination of the above. In the present disclosure, the computer-readable storage medium may be any tangible medium that contains or stores a program, and the program can be used by or in combination with an instruction execution system, device, or device. For example, according to an embodiment of the present disclosure, the computer-readable storage medium may include the above-described ROM 802 and / or RAM 803 and / or one or more memories other than ROM 802 and RAM 803.

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

[0150] Those skilled in the art can understand that the features described in the various embodiments and / or claims of the present disclosure can be combined and / or combined in various ways, even if such combinations or combinations are not explicitly described in the present disclosure. In particular, without departing from the spirit and teachings of the present disclosure, the features described in the various embodiments and / or claims of the present disclosure can be combined and / or combined in various ways. All such combinations and / or combinations fall within the scope of the present disclosure.

[0151] The above describes the embodiments of the present disclosure. However, these embodiments are merely for illustrative purposes and not for limiting the scope of the present disclosure. Although the embodiments are described separately above, this does not mean that the measures in each embodiment cannot be used advantageously in combination. The scope of the present disclosure is defined by the appended claims and their equivalents. Without departing from the scope of the present disclosure, those skilled in the art can make various substitutions and modifications, and all such substitutions and modifications should fall within the scope of the present disclosure.

Claims

1. An information processing method based on a blockchain network, comprising: Receiving, by a blockchain node of the blockchain network, initial information of m asset maintenance requests, where the initial information includes an initial maintenance operation and initial maintenance information performed on a business architecture description model, and m is a positive integer greater than or equal to 2; Determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, where n is a positive integer greater than or equal to 2 and n ≤ m; wherein the asset maintenance conflicts include formal conflicts and substantive conflicts; the formal conflicts include potential conflicts occurring in two or more asset updates, without changing the same asset component or field, or making semantically conflicting changes to the same asset component; the substantive conflicts include conflicts occurring in two or more asset updates and changing the same asset component or field; If so, processing the initial information of the n asset maintenance requests to determine target information corresponding to the m asset maintenance requests, where the target information includes a target maintenance operation and target maintenance information for indicating performing on the business architecture description model; Performing 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 blockchain node; Wherein the asset maintenance request includes: an asset change execution request, which is used to indicate performing a change operation on a business architecture description model; and / or an asset change rollback request, which is used to indicate performing a change rollback operation on a business architecture description model; the asset maintenance request includes maintenance operation information to be performed and an object to be maintained; Wherein determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests includes: in response to receiving the m asset maintenance requests, sending 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; if the approval result indicates that the m asset maintenance requests are approved, determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests.

2. The method according to claim 1, wherein, Determining whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests includes: If the m asset maintenance requests include m asset change execution requests, determining whether there are n asset maintenance requests with asset change conflicts based on the initial information corresponding to the m asset change execution requests; or If the m asset maintenance requests include m asset change rollback requests, determining whether there are n asset rollback requests with asset rollback conflicts based on the 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, then 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, determine whether there are n asset maintenance requests with asset replenishment conflicts, where p and q are positive integers and p + q = m.

3. The method according to claim 1, wherein, Processing the initial information of the n asset maintenance requests to determine the target information corresponding to the m asset maintenance requests includes: For the initial information of the n asset maintenance requests, determine whether the asset maintenance conflict is a field information conflict or a semantic information conflict; If not, then merge the initial information of the n asset maintenance requests to generate merged information corresponding to the n asset maintenance requests, where the merged information includes the merge maintenance operations and merge maintenance information performed on the business architecture description model; Determine the merged 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.

4. The method according to claim 3, wherein The merging of the initial information of the n asset maintenance requests includes: In response to the n asset maintenance requests, call the smart contract of the blockchain node, where the smart contract is configured with a merging mechanism; and Based on the merging mechanism, merge the initial information of the n asset maintenance requests.

5. The method according to claim 3, wherein, The method further includes: If so, then return the initial information of the n asset maintenance requests; Determine the initial information of the m - n asset maintenance requests as the target information corresponding to the m asset maintenance requests.

6. The method according to claim 3, wherein In the case where the asset maintenance request includes an asset change execution request, performing the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information includes: Based on the merged information corresponding to the n asset maintenance requests, perform an 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, perform an asset change operation on the business architecture description model to obtain a second change result.

7. The method according to claim 3, wherein In the case where the asset maintenance request includes an asset change rollback request, performing the target maintenance operation on the business architecture description model based on the target maintenance information to obtain maintenance result information includes: Based on the merged information corresponding to the n asset maintenance requests, perform an asset replenishment operation on the business architecture description model to obtain a first replenishment result; Based on the initial information of the m - n asset maintenance requests, perform an asset replenishment operation on the business architecture description model to obtain a second replenishment result.

8. The method according to any one of claims 1 to 7, wherein, The method further includes: storing the target information corresponding to the m asset maintenance requests in the blockchain node.

9. The method according to claim 1, wherein The method further includes: If the approval result indicates that the m asset maintenance requests are not approved, then store the initial information of the m asset maintenance requests and the approval result in the blockchain node.

10. An information processing device based on a blockchain network, including: An initial maintenance information receiving module, configured to receive initial information of m asset maintenance requests by using blockchain nodes of the blockchain network, where the initial information includes initial maintenance operations and initial maintenance information performed on a business architecture description model, and m is a positive integer greater than or equal to 2; An asset maintenance conflict determination module, configured to determine whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests, where n is a positive integer greater than or equal to 2 and n ≤ m; where the asset maintenance conflicts include formal conflicts and substantial conflicts; the formal conflicts include potential conflicts occurring in two or more asset updates, without changing the same asset component or field, or making semantically conflicting changes to the same asset component; the substantial conflicts include conflicts occurring in two or more asset updates, and changing the same asset component or the field; where the asset maintenance request includes: an asset change execution request, where the asset change execution request is used to indicate a change operation to be performed on the business architecture description model; and / or an asset change rollback request, where the asset change rollback request is used to indicate a change rollback operation to be performed on the business architecture description model; the asset maintenance request includes maintenance operation information to be performed and an object to be maintained; a target maintenance information determination module, configured to, if any, process the 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 operations and target maintenance information used to indicate performing on the business architecture description model; A maintenance result information processing module, configured to perform the target maintenance operations on the business architecture description model based on the target maintenance information to obtain maintenance result information, and store the maintenance result information in the blockchain node; The asset maintenance conflict determination module includes: an approval information sending sub-module, configured to, in response to receiving the m asset maintenance requests, send 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; an approval result receiving sub-module, configured to receive the approval result returned by the approval node; and an asset maintenance conflict determination sub-module, configured to, if the approval result indicates that the m asset maintenance requests are approved, determine whether there are n asset maintenance requests with asset maintenance conflicts among the m asset maintenance requests.

11. An electronic device, comprising: One or more processors; And A memory, configured to store one or more programs, Wherein, when the one or more programs are executed by the one or more processors, the one or more processors are caused to implement the method according to any one of claims 1 to 9.

12. A computer-readable storage medium, storing computer-executable instructions, where the instructions, when executed, are used to implement the method according to any one of claims 1 to 9.

Images