WO2021196936A1 - 基于区块链的业务链数据校核方法、装置、存储介质、电子设备 - Google Patents

基于区块链的业务链数据校核方法、装置、存储介质、电子设备 Download PDF

Info

Publication number
WO2021196936A1
WO2021196936A1 PCT/CN2021/078134 CN2021078134W WO2021196936A1 WO 2021196936 A1 WO2021196936 A1 WO 2021196936A1 CN 2021078134 W CN2021078134 W CN 2021078134W WO 2021196936 A1 WO2021196936 A1 WO 2021196936A1
Authority
WO
WIPO (PCT)
Prior art keywords
data
node
service
network
relationship table
Prior art date
Application number
PCT/CN2021/078134
Other languages
English (en)
French (fr)
Other versions
WO2021196936A9 (zh
Inventor
刘恩科
王梦寒
赵达悦
谢丹力
Original Assignee
深圳壹账通智能科技有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 深圳壹账通智能科技有限公司 filed Critical 深圳壹账通智能科技有限公司
Publication of WO2021196936A1 publication Critical patent/WO2021196936A1/zh
Publication of WO2021196936A9 publication Critical patent/WO2021196936A9/zh

Links

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G06Q10/063—Operations research, analysis or management
    • G06Q10/0633—Workflow analysis
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06K—GRAPHICAL DATA READING; PRESENTATION OF DATA; RECORD CARRIERS; HANDLING RECORD CARRIERS
    • G06K17/00—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations
    • G06K17/0022—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device
    • G06K17/0029—Methods or arrangements for effecting co-operative working between equipments covered by two or more of main groups G06K1/00 - G06K15/00, e.g. automatic card files incorporating conveying and reading operations arrangements or provisious for transferring data to distant stations, e.g. from a sensing device the arrangement being specially adapted for wireless interrogation of grouped or bundled articles tagged with wireless record carriers
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/04—Forecasting or optimisation specially adapted for administrative or management purposes, e.g. linear programming or "cutting stock problem"
    • G06Q10/047—Optimisation of routes or paths, e.g. travelling salesman problem
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/083—Shipping
    • G06Q10/0833—Tracking
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/08—Logistics, e.g. warehousing, loading or distribution; Inventory or stock management
    • G06Q10/087—Inventory or stock management, e.g. order filling, procurement or balancing against orders

Definitions

  • the present disclosure relates to the field of blockchain, and in particular, to a blockchain-based business chain data verification method, a blockchain-based business chain data verification device, a computer-readable storage medium, and electronic equipment.
  • Business chain data verification is the activity of verifying and managing the data generated in the entire business process. For example, check whether the data of each component in the whole process data corresponds to the total data, etc.
  • In the actual business chain usually many processes can be used for the same business, and different businesses have different business processes, and different data generated in different business processes, especially for large-scale nodes, will generate a large amount of data.
  • business chain data verification is usually carried out through real-time monitoring and tracking of business processes, and the verification is carried out simultaneously with the business process.
  • the inventor realizes that there are problems in data verification and business processes that are difficult to guarantee, and usually require a lot of manpower. resource.
  • a business chain data verification method based on a blockchain includes a sub-network of business nodes and a data verification node connected to the sub-network of the business node, including :
  • the service link data is the service-related data uploaded by each service node in the closed-loop business process of the target service, and the service-related data includes Node path planning in the closed-loop business process uploaded by the path planning node;
  • the data relationship table is input into a preset verification module to obtain a verification result of the service link data.
  • a blockchain-based business chain data verification device including:
  • the obtaining module is used to obtain the service link data of the target service uploaded to the sub-network, where the service link data is the service-related data uploaded by each service node in the closed-loop service process of the target service.
  • the business-related data includes the node path plan in the closed-loop business process uploaded by the path planning node;
  • An extraction module configured to extract flow path data from the service link data according to the node path plan, where the flow path data is data related to service handover between service nodes in the node path plan;
  • the parsing module is used to analyze the flow path data of the target service to obtain the node relationship network of the target service to obtain the attribute relationship table corresponding to the node relationship network, and the attribute relationship table is corresponding to the node Relationship table of different attribute data of the relationship;
  • a mapping module configured to map the service link data into a data relationship table based on the attribute relationship table
  • the input module is used to input the data relationship table into a preset verification module to obtain the verification result of the service link data.
  • a computer-readable storage medium including a storage data area and a storage program area, the storage data area stores data created according to the use of blockchain nodes, and the storage program area stores computer programs, so
  • the block chain includes a sub-network of business nodes and a data verification node connected to the sub-network of the business nodes.
  • the service link data is the service-related data uploaded by each service node in the closed-loop business process of the target service, and the service-related data includes Node path planning in the closed-loop business process uploaded by the path planning node;
  • the data relationship table is input into a preset verification module to obtain a verification result of the service link data.
  • an electronic device is a data verification node in a blockchain, the blockchain including a sub-network of service nodes and a sub-network connected to the service node
  • the data verification node the electronic device includes:
  • a memory for storing executable instructions of the processor
  • the processor is configured to execute the following steps by executing the executable instructions:
  • the service link data is the service-related data uploaded by each service node in the closed-loop business process of the target service, and the service-related data includes Node path planning in the closed-loop business process uploaded by the path planning node;
  • the data relationship table is input into a preset verification module to obtain a verification result of the service link data.
  • Fig. 1 schematically shows a flow chart of a blockchain-based business chain data verification method.
  • Fig. 2 schematically shows a flow chart of a blockchain-based business chain data verification method.
  • Fig. 3 schematically shows a flow chart of a blockchain-based business chain data verification method.
  • Fig. 4 schematically shows a flow chart of a blockchain-based business chain data verification method.
  • Figure 5 schematically shows a flow chart of a blockchain-based business chain data verification method applied to the AOG aviation material maintenance business.
  • Fig. 6 schematically shows a block diagram of a blockchain-based business chain data verification device.
  • FIG. 7 schematically shows an example block diagram of an electronic device for implementing the above-mentioned blockchain-based business chain data verification method.
  • Fig. 8 schematically shows a computer-readable storage medium for implementing the above-mentioned blockchain-based business chain data verification method.
  • This example embodiment first provides a blockchain-based business chain data verification method.
  • the blockchain-based business chain data verification method can be run on a server, or on a server cluster or cloud server, etc., Of course, those skilled in the art can also run the method of this application on other platforms as required, which is not specifically limited in this exemplary embodiment.
  • the blockchain-based business chain data verification method may include the following steps:
  • Step S110 Obtain the service link data of the target service uploaded to the sub-network, where the service link data is the service-related data uploaded by each service node in the closed-loop business process of the target service, and the service is related
  • the data includes the node path plan in the closed-loop business process uploaded by the path planning node;
  • Step S120 Extracting flow path data from the service link data according to the node path plan, where the flow path data is data related to service handover between service nodes in the node path plan;
  • Step S130 Analyze the flow path data of the target service to obtain the node relationship network of the target service to obtain an attribute relationship table corresponding to the node relationship network, and the attribute relationship table is corresponding to the node relationship Relationship table of different attribute data;
  • Step S140 based on the attribute relationship table, map the service link data into a data relationship table
  • Step S150 Input the data relationship table into a preset verification module to obtain a verification result of the service link data.
  • step S110 the service link data of the target service uploaded to the sub-network is obtained, and the service link data is the service-related data uploaded by each service node in the closed-loop service process of the target service.
  • the business-related data includes the node path planning in the closed-loop business process uploaded by the path planning node.
  • the target service may be any service completed by the mutual cooperation of the nodes in the sub-network constituting the service node, for example, it may be an aviation material maintenance service or a system service on a certain workflow platform.
  • the sub-network of the business node may be a blockchain sub-network composed of interconnected multiple business nodes, which can share data.
  • the main participants of the blockchain are the sub-networks interconnected by the terminal equipment of airlines, maintenance companies, logistics companies, warehousing companies, and customs.
  • the business link data is the business-related data uploaded by each business node in the closed-loop business process of the target business.
  • the maintenance company provides data such as maintenance lease contracts, quotations, and work orders; Key nodes such as warehousing and maintenance points scan RFID to form closed-loop operation process information (product information, location information, process information); provide mail information for maintenance needs, maintenance confirmation information, and RFID scanning at entry and exit checkpoints Information; warehousing company's material and part storage information, etc.
  • the database nodes of different enterprises connected by the workflow platform can call data and various data produced in the workflow task. Among them, different business nodes upload their own data according to a predetermined standard format.
  • the path planning node uploads the node path planning in the closed-loop business process.
  • the path planning node receives the service start instruction, it decomposes the target service into sub-services, and then broadcasts the task on the sub-network of the service node for each sub-service.
  • the node set of all sub-businesses and the flow sequence of each node in the node set are obtained, and the node path planning can be encrypted in the sub-network of the blockchain. shared.
  • step S120 the flow path data is extracted from the service link data according to the node path plan, and the flow path data is data related to the service handover between service nodes in the node path plan.
  • the transfer path data is related data for the service handover between service nodes in the node path plan, and the location information of the target service plan that is transferred between the service nodes (for example, the information of the terminal corresponding to the service node) Geographic location information), the start time of the node's subtasks, the completion time of the node's subtasks, the subtask configuration information of each node (for example, the equipment information configured to complete the subtasks, etc.), the task process information within each node ( For example, data such as the circulation process data of the child nodes in each node.
  • the path planning node will plan different paths, and different paths will cause different costs in the business operation process and generate different data. For example, according to the actual situation of each node, paths such as ABCDE or ABDCDED can be generated, and because of the different paths, the corresponding data services are different when the services are handed over. The larger the order of magnitude of the business-related nodes, that is, the business nodes in the business node sub-network, the more circulation paths will be.
  • step S120 specifically includes:
  • Step S1201 according to the node order in the node path plan and the subtask identifier of each node, generate a flow path data extraction command corresponding to each node;
  • Step S1202 Send the flow path data extraction command to the business node corresponding to the flow path data extraction command, and obtain the data table returned by the business node corresponding to the flow path data extraction command;
  • Step S1203 Extract the flow path data from the service link data according to the data table.
  • the path planning node will plan different paths according to different real-time conditions. For example, according to the actual conditions of each node, paths such as ABCDE or ABDCDED can be generated, and different paths correspond to different node sequences.
  • the subtask identifier of the node is used to uniquely identify the subtask corresponding to the node, including but not limited to the start time of the subtask of the node, the completion time of the subtask of the node, and the subtask configuration information of the node.
  • the data extraction command of the circulation path corresponding to each node can be generated.
  • the circulation path data extraction command is used to instruct to extract the circulation path data.
  • step S1202 after the service node obtains the corresponding flow path data extraction command, it returns to the data table according to the command, and the flow path data is stored in the data table.
  • step S1203 after the data table is received in step S1202, the circulation path data can be extracted according to the data table.
  • step S130 the flow path data of the target service is parsed to obtain the node relationship network of the target service, so as to obtain the attribute relationship table corresponding to the node relationship network.
  • the table is a relationship table corresponding to different attribute data of the node relationship.
  • the analysis of the flow path data of the target service can be based on the node path plan, and two adjacent nodes are grouped into a set in turn.
  • AB and BC can be divided. .. EF and other node sets, and then each node set is used as an array element, and the business handover related data corresponding to each array element is stored in the corresponding element to obtain the node relationship network of the target business.
  • the node relationship network can also be passed Analyzed in the form of tables, matrices, etc.
  • the node business relationship network can reflect all the flow characteristics of the business process of the target business.
  • the rows and columns of the matrix correspond to nodes, and the data in the matrix unit is the comparison data of two nodes, such as location comparison data.
  • the attribute relationship table is a relationship table of different attribute data corresponding to the node relationship. According to the relationship between adjacent nodes, the relationship between the different attribute data generated by the two nodes before and after can be obtained. For example, for the material processing node and the equipment maintenance node, When adjacent, the node relationship can be the material preparation and consumption relationship, and then according to the characteristics reflected by the sub-relationship network of these two nodes (for example, the subtask configuration information of each node (for example, the device information configured to complete the corresponding subtask) Etc.), the task process information within each node (for example, the circulation process data of the child nodes in each node), etc., you can get the relationship between the various attribute data uploaded by the two nodes (for example, the number of use Data, such as information on the quantity of materials leaving and entering the area, information on the use of materials and parts of the maintenance company, etc.). That is, the attribute relationship table indicates the data attribute relationship that needs to be checked in the business chain data of the target business.
  • obtaining the attribute relationship table corresponding to the node relationship network includes:
  • Step S310 Input the node relationship network into a preset data feature extraction model to obtain data features of a closed-loop business process with the target business;
  • Step S320 Match the data feature with the data feature sample in the database to obtain a data feature sample that matches the data feature;
  • Step S330 Use the preset attribute relationship table corresponding to the data feature sample as the preset attribute relationship table corresponding to the node relationship network.
  • obtaining the attribute relationship table corresponding to the node relationship network includes:
  • Generate code by developing the attribute relationship table use the code to analyze the node relationship network of the target business, and generate the attribute relationship table.
  • the code in order to generate the attribute relationship table, can be developed by way of code development.
  • the code can be developed by writing and/or modifying the source code.
  • the source code can be edited according to a preset standard. Write and/or modify.
  • the code development may also directly receive the code written by the user.
  • the attribute relationship table is generated by analyzing the node relationship network of the target business by scanning the code library index and calling the developed attribute relationship table generating code.
  • the attribute relationship table includes: a relationship table of attributes of each data consistent with the order of the nodes in the node path planning.
  • the columns in the attribute relationship table correspond to various data attributes, such as the quantity of materials, the cost of consumption, and so on.
  • the columns in Table 1 may correspond to the relationship between the data attributes of two adjacent nodes, for example, addition or subtraction.
  • step S140 the service link data is mapped to a data relationship table based on the attribute relationship table.
  • Mapping the data of each business attribute to the corresponding unit of each attribute in the preset attribute relationship table can obtain a data relationship table that reliably organizes all data of the current target business according to path characteristics.
  • the preset attribute relationship table includes a comparison unit established based on the association relationship between each attribute. In this way, the data relationship table can reliably characterize the relationship between all the data of the target business.
  • a data relationship table 2 is:
  • step S150 the data relationship table is input to a preset verification module to obtain a verification result of the service link data.
  • the preset check module is a pre-developed check algorithm template, and the association relationship between the attributes in each preset attribute association table is different due to different business circulation paths.
  • the business flow path includes the sequence of execution, which affects the data change process. For example, by using RFID technology to build an IoT logistics monitoring module, real-time monitoring of the location and dynamics of aviation materials and equipment, forming a closed-loop material location data flow.
  • the check algorithm template the data in the data relation table can be continuously mapped to the corresponding parameters during the calculation process, and the check can be performed to obtain the comparison result.
  • the verification result can be accurately and reliably verified; Based on the non-tampering feature of the blockchain data, the authenticity and non-tampering of the data can be guaranteed, so that the data verification process is separated from the business process, and the business efficiency is guaranteed.
  • the method further includes:
  • the maintenance information matching the verification result is obtained from the maintenance information database and shared to the sub-network of the service node.
  • the maintenance information database is a database used to store maintenance information of the service link data on the service node sub-network, where the maintenance information can replace the service link data on the service node sub-network, so that The business node can perform secondary maintenance based on the maintenance information.
  • the maintenance information matching the check result can be obtained from the maintenance information database, and the obtained maintenance information can be shared to the service node sub-network.
  • the maintenance information matching the check result can be obtained by looking up the table.
  • the corresponding relationship table between the check result and the maintenance information is stored in the maintenance information database.
  • the matching maintenance information is calculated through a certain formula information.
  • the method further includes:
  • Step S410 Obtain the correction data uploaded by each business node in the sub-network of the business node according to the maintenance information
  • Step S420 After replacing the service-related data in the service link data of the target service in the service node sub-network with the correction data, perform secondary maintenance on the service link data.
  • step S410 after each service node in the service node sub-network receives the maintenance information, it can generate supplemental data based on the maintenance information.
  • the supplemental data is generated by comparing the business link data of the business node with the maintenance information. , Can be added, deleted, modified, etc.
  • step S420 because the corrected data is the data obtained by correcting the maintenance information after the verification result is obtained, it is more accurate and true. Therefore, the corrected data can be selected to replace the business of the target business in the service node sub-network.
  • the business-related data in the link data performs secondary maintenance on the business chain data. Among them, in the process of secondary maintenance, the service link data can be checked according to the method shown in Figure 1 to Figure 3.
  • Figure 5 schematically shows a flow chart of a blockchain-based business chain data verification method applied to the AOG aviation material maintenance business.
  • AOG Aircraft On Ground
  • AOG is a special cargo code in air transportation. It refers to the urgent order of aviation materials, which must be delivered to the destination as quickly as possible. The flight mission can only be continued after the failed aircraft has replaced its parts.
  • AOG emergency maintenance business it is necessary to establish a "real-time tracking and monitoring system", from the ordering of equipment, urging repair, requesting assistance, shipping, customs declaration, picking up the equipment to the final delivery of the equipment to the maintenance personnel, to achieve seamless control, to the greatest extent possible May shorten the repair time.
  • the customs declaration process of bonded aviation materials takes the longest time.
  • the business-related parties airlines, maintenance companies, logistics companies, warehousing companies and customs form alliances to build an AOG aviation material guarantee chain, and all parties
  • the information is on the chain to ensure the authenticity of the business, while real-time tracking and effective supervision of bonded goods are implemented to realize the business model of first leaving the zone and then declaring, which greatly enhances the timeliness and enhances the competitiveness of enterprises.
  • the maintenance company provides the maintenance lease contract, quotation, and work order; the logistics company uses the handheld PDA to scan RFID at key nodes such as warehouses and maintenance points to form closed-loop operation process information (product information, location Information, process information), assist customs officers to effectively supervise the aviation materials leaving the zone.
  • the airlines provide information on ordering, urging repairs, assistance requests, and maintenance confirmation information to assist customs officers in verifying the authenticity and necessity of the maintenance business from the side.
  • the RFID scanning information at the entry and exit of the bayonet, and the information on the entry and exit of the materials and parts of the warehousing company can also be used as additional data sources for cross-validation of the equipment use time and the number of materials.
  • the customs can effectively supervise the quantity and location of the bonded goods, and will be assured that the company will first transport the AOG aviation materials out of the special supervision area, and wait until the maintenance tasks are completed. Line customs declaration.
  • the main participants of the blockchain are airlines, maintenance companies, logistics companies, warehousing companies and customs.
  • maintenance companies provide maintenance lease contracts, quotations, and work orders; logistics companies use handheld PDAs to scan RFID at key nodes such as warehouses and maintenance points to form closed-loop operation process information (Commodity information, location information, process information), assist customs officers to effectively supervise the materials and equipment out of the zone.
  • the airline company provides maintenance request email information and maintenance confirmation information to assist customs officers in verifying the authenticity and necessity of the maintenance business from the side.
  • the RFID scanning information at the entry and exit of the bayonet, and the information on the entry and exit of the materials and parts of the warehousing company can also be used as additional data sources for cross-validation of the equipment use time and the number of materials.
  • the closed management of the maintenance process is completed through the verification list, verification release list, and material and part storage list.
  • RFID technology produces uniquely identifiable electronic seals, large materials are hung on the materials with disposable straps, small materials use turnover media, and turnover media are bound to electronic seals.
  • the bayonet inspector scans the electronic seal of the material, verifies the quantity and status of the material, forms a node for the bayonet of the material, and uploads the data of the bayonet to the blockchain;
  • the transportation path adopts GPS positioning technology to form the material transportation trajectory, form the material movement trajectory node, and upload the movement trajectory data to the blockchain;
  • the maintenance personnel After arriving at the airport, the maintenance personnel scan the electronic label before unpacking the materials to determine whether the quantity and condition of the materials are complete, and confirm the repair after unsealing. After the repair is completed, the customer confirms the number of materials used for the repair and performs an electronic signature.
  • the maintenance node forms material usage data and uploads it to the blockchain;
  • a complete link of aviation materials and equipment from out of zone-transportation-use-back to warehouse is formed, which can truly record the movement trajectory of materials and the data and status of each node, which is a block
  • the chain provides complete trajectory data after the materials leave the zone, which facilitates multi-party verification in the later stage, and better completes the monitoring and supervision of the bonded aviation materials after leaving the zone.
  • the present disclosure also provides a business chain data checking device based on the blockchain.
  • the blockchain-based business chain data verification device may include an acquisition module 610, an extraction module 620, an analysis module 630, a mapping module 640, and an input module 650. in:
  • the obtaining module 610 is configured to obtain the service link data of the target service uploaded to the sub-network, where the service link data is the service-related data uploaded by each service node in the closed-loop service process of the target service.
  • the business-related data includes the node path plan in the closed-loop business process uploaded by the path planning node;
  • the extraction module 620 is configured to extract flow path data from the service link data according to the node path plan, where the flow path data is data related to service handover between service nodes in the node path plan;
  • the parsing module 630 is configured to analyze the flow path data of the target service to obtain the node relationship network of the target service, so as to obtain the attribute relationship table corresponding to the node relationship network, and the attribute relationship table is corresponding to The relationship table of different attribute data of the node relationship;
  • a mapping module 640 configured to map the service link data into a data relationship table based on the attribute relationship table
  • the input module 650 is configured to input the data relationship table into a preset verification module to obtain a verification result of the service link data.
  • modules or units of the device for action execution are mentioned in the above detailed description, this division is not mandatory.
  • the features and functions of two or more modules or units described above may be embodied in one module or unit.
  • the features and functions of a module or unit described above can be further divided into multiple modules or units to be embodied.
  • the example embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which can be a personal computer, a server, a mobile terminal, or a network device, etc.) execute the method according to the embodiments of the present disclosure.
  • a non-volatile storage medium which can be a CD-ROM, U disk, mobile hard disk, etc.
  • Including several instructions to make a computing device which can be a personal computer, a server, a mobile terminal, or a network device, etc.
  • an electronic device capable of implementing the above method is also provided.
  • the electronic device 700 according to this embodiment of the present application will be described below with reference to FIG. 7.
  • the electronic device 700 shown in FIG. 7 is only an example, and should not bring any limitation to the functions and scope of use of the embodiments of the present application.
  • the electronic device 700 is represented in the form of a general-purpose computing device.
  • the components of the electronic device 600 may include, but are not limited to: the aforementioned at least one processing unit 710, the aforementioned at least one storage unit 720, and a bus 730 connecting different system components (including the storage unit 720 and the processing unit 710).
  • the storage unit stores program code, and the program code can be executed by the processing unit 710, so that the processing unit 710 executes the various exemplary methods described in the “Exemplary Method” section of this specification. Steps of implementation.
  • the processing unit 710 may perform step S110 as shown in FIG.
  • Step S130 Analyze the circulation path data of the target service to obtain the target The node relationship network of the service to obtain an attribute relationship table corresponding to the node relationship network, where the attribute relationship table is a relationship table corresponding to different attribute data of the node relationship; step S140: based on the attribute relationship table, all The service link data is mapped into a data relationship table; step S150: the data relationship table is input into a preset verification module to obtain a verification result of the service link data.
  • the storage unit 720 may include a readable medium in the form of a volatile storage unit, such as a random access storage unit (RAM) 7201 and/or a cache storage unit 7202, and may further include a read-only storage unit (ROM) 7203.
  • RAM random access storage unit
  • ROM read-only storage unit
  • the storage unit 720 may also include a program/utility tool 7204 having a set of (at least one) program module 7205.
  • program module 7205 includes but is not limited to: an operating system, one or more application programs, other program modules, and program data, Each of these examples or some combination may include the implementation of a network environment.
  • the bus 730 may represent one or more of several types of bus structures, including a storage unit bus or a storage unit controller, a peripheral bus, a graphics acceleration port, a processing unit, or a local area using any bus structure among multiple bus structures. bus.
  • the electronic device 700 may also communicate with one or more external devices 700 (such as keyboards, pointing devices, Bluetooth devices, etc.), and may also communicate with one or more devices that enable a user to interact with the electronic device 700, and/or communicate with Any device (eg, router, modem, etc.) that enables the electronic device 700 to communicate with one or more other computing devices. This communication can be performed through an input/output (I/O) interface 750.
  • the electronic device 600 may also communicate with one or more networks (for example, a local area network (LAN), a wide area network (WAN), and/or a public network, such as the Internet) through the network adapter 760. As shown in the figure, the network adapter 760 communicates with other modules of the electronic device 700 through the bus 730.
  • LAN local area network
  • WAN wide area network
  • public network such as the Internet
  • the example embodiments described here can be implemented by software, or can be implemented by combining software with necessary hardware. Therefore, the technical solution according to the embodiments of the present disclosure can be embodied in the form of a software product, which can be stored in a non-volatile storage medium (which can be a CD-ROM, U disk, mobile hard disk, etc.) or on the network , Including several instructions to make a computing device (which can be a personal computer, a server, a terminal device, or a network device, etc.) execute the method according to the embodiments of the present disclosure.
  • a non-volatile storage medium which can be a CD-ROM, U disk, mobile hard disk, etc.
  • Including several instructions to make a computing device which can be a personal computer, a server, a terminal device, or a network device, etc.
  • a computer-readable storage medium is also provided.
  • the computer-readable storage medium may be volatile or non-volatile.
  • the computer-readable storage medium includes storage The data area and the storage program area.
  • the storage data area stores data created based on the use of blockchain nodes.
  • the storage program area stores program products that can implement the above-mentioned methods in this specification.
  • the blockchain includes sub-networks of business nodes and A data verification node connected to the sub-network of the service node.
  • various aspects of the present application can also be implemented in the form of a program product, which includes program code. When the program product runs on a terminal device, the program code is used to make the The terminal device performs the following steps:
  • the service link data is the service-related data uploaded by each service node in the closed-loop business process of the target service, and the service-related data includes Node path planning in the closed-loop business process uploaded by the path planning node;
  • the data relationship table is input into a preset verification module to obtain a verification result of the service link data.
  • a program product 800 for implementing the above method according to an embodiment of the present application is described. It can adopt a portable compact disk read-only memory (CD-ROM) and include program code, and can be installed in a terminal device, For example, running on a personal computer.
  • CD-ROM compact disk read-only memory
  • the program product of this application is not limited to this.
  • the readable storage medium can 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.
  • the program product can use any combination of one or more readable media.
  • the readable medium may be a readable signal medium or a readable storage medium.
  • the readable storage medium may be, for example, but not limited to, an electrical, magnetic, optical, electromagnetic, infrared, or semiconductor system, device, or device, or a combination of any of the above. More specific examples (non-exhaustive list) of readable storage media include: electrical connections with one or more wires, portable disks, hard disks, random access memory (RAM), read only memory (ROM), erasable Type programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage device, magnetic storage device, or any suitable combination of the above.
  • the computer-readable signal medium may include a data signal propagated in baseband or as a part of a carrier wave, and readable program code is carried therein. This propagated data signal can take many forms, including but not limited to electromagnetic signals, optical signals, or any suitable combination of the foregoing.
  • the readable signal medium may also be any readable medium other than a readable storage medium, and the readable medium may send, propagate, or transmit a program for use by or in combination with the instruction execution system, apparatus, or device.
  • the program code contained on the readable medium can be transmitted by any suitable medium, including but not limited to wireless, wired, optical cable, RF, etc., or any suitable combination of the foregoing.
  • the program code used to perform the operations of the present application can be written in any combination of one or more programming languages.
  • the programming languages include object-oriented programming languages—such as Java, C++, etc., as well as conventional procedural programming languages. Programming language-such as "C" language or similar programming language.
  • the program code can be executed entirely on the user's computing device, partly on the user's device, executed as an independent software package, partly on the user's computing device and partly executed on the remote computing device, or entirely on the remote computing device or server Executed on.
  • the remote computing device can be connected to a user computing device through any kind of network, including a local area network (LAN) or a wide area network (WAN), or it can be connected to an external computing device (for example, using Internet service providers). Business to connect via the Internet).
  • LAN local area network
  • WAN wide area network
  • Internet service providers for example, using Internet service providers.

Abstract

一种基于区块链的业务链数据校核方法、装置、计算机可读存储介质及电子设备。该方法包括：获取上传到区块链子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划（S110）；根据所述节点路径规划，从所述业务链路数据中提取流转路径数据（S120）；解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表（S130）；基于所述属性关系表，将所述业务链路数据映射为数据关系表（S140）；将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果（S150）。

Description

基于区块链的业务链数据校核方法、装置、存储介质、电子设备
本申请要求于2020年4月1日提交中国专利局、申请号为CN202010248516.3、名称为“基于区块链的业务链数据校核方法、装置、存储介质、电子设备”的中国专利申请的优先权，其全部内容通过引用结合在本申请中。
技术领域
本公开涉及区块链领域，具体而言，涉及一种基于区块链的业务链数据校核方法、基于区块链的业务链数据校核装置、计算机可读存储介质以及电子设备。
 背景技术
业务链数据校核就是对业务全流程产生的数据进行校核管理的活动。例如，校核全流程数据中各个分量的数据与总量数据是否对应等。在实际业务链中通常对于同一个业务可以采用很多的流程，同时不同的业务具有不同的业务流程，而不同业务流程中产生的不同的数据，特别对于大数量级的节点，会产生大量数据。
 技术问题
目前，进行业务链数据校核时通常通过实时监控追踪业务进程，校核与业务进程同步进行，发明人意识到这样存在数据校核困难、业务进程难以保证的问题，且通常需要耗费较多人力资源。
需要说明的是，在上述背景技术部分公开的信息仅用于加强对本公开的背景的理解，因此可以包括不构成对本领域普通技术人员已知的现有技术的信息。
 技术解决方案
根据本公开的一个方面，提供一种基于区块链的业务链数据校核方法，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的数据校核节点，包括：
获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
基于所述属性关系表，将所述业务链路数据映射为数据关系表；
将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
根据本公开的一个方面，提供一种基于区块链的业务链数据校核装置，包括：
获取模块，用于获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
提取模块，用于根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
解析模块，用于解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
映射模块，用于基于所述属性关系表，将所述业务链路数据映射为数据关系表；
输入模块，用于将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
根据本公开的一个方面，提供一种计算机可读存储介质，包括存储数据区和存储程序区，存储数据区存储根据区块链节点的使用所创建的数据，存储程序区存储有计算机程序，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的数据校核节点，所述计算机程序被处理器执行时实现如下步骤：
获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
基于所述属性关系表，将所述业务链路数据映射为数据关系表；
将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
根据本公开的一个方面，提供一种电子设备，所述电子设备为区块链中的数据校核节点，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的所述数据校核节点，所述电子设备包括：
处理器；以及
存储器，用于存储所述处理器的可执行指令；
其中，所述处理器配置为经由执行所述可执行指令来执行如下步骤：
获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
基于所述属性关系表，将所述业务链路数据映射为数据关系表；
将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
 附图说明
此处的附图被并入说明书中并构成本说明书的一部分，示出了符合本公开的实施例，并与说明书一起用于解释本公开的原理。显而易见地，下面描述中的附图仅仅是本公开的一些实施例，对于本领域普通技术人员来讲，在不付出创造性劳动的前提下，还可以根据这些附图获得其他的附图。
图1示意性示出一种基于区块链的业务链数据校核方法的流程图。
图2示意性示出一种基于区块链的业务链数据校核方法的流程图。
图3示意性示出一种基于区块链的业务链数据校核方法的流程图。
图4示意性示出一种基于区块链的业务链数据校核方法的流程图。
图5示意性示出一种基于区块链的业务链数据校核方法应用在AOG航材维修业务中的流程图。
图6示意性示出一种基于区块链的业务链数据校核装置的方框图。
图7示意性示出一种用于实现上述基于区块链的业务链数据校核方法的电子设备示例框图。
图8示意性示出一种用于实现上述基于区块链的业务链数据校核方法的计算机可读存储介质。
 本发明的实施方式
现在将参考附图更全面地描述示例实施方式。然而，示例实施方式能够以多种形式实施，且不应被理解为限于在此阐述的范例；相反，提供这些实施方式使得本公开将更加全面和完整，并将示例实施方式的构思全面地传达给本领域的技术人员。所描述的特征、结构或特性可以以任何合适的方式结合在一个或更多实施方式中。在下面的描述中，提供许多具体细节从而给出对本公开的实施方式的充分理解。然而，本领域技术人员将意识到，可以实践本公开的技术方案而省略所述特定细节中的一个或更多，或者可以采用其它的方法、组元、装置、步骤等。在其它情况下，不详细示出或描述公知技术方案以避免喧宾夺主而使得本公开的各方面变得模糊。
此外，附图仅为本公开的示意性图解，并非一定是按比例绘制。图中相同的附图标记表示相同或类似的部分，因而将省略对它们的重复描述。附图中所示的一些方框图是功能实体，不一定必须与物理或逻辑上独立的实体相对应。可以采用软件形式来实现这些功能实体，或在一个或多个硬件模块或集成电路中实现这些功能实体，或在不同网络和/或处理器装置和/或微控制器装置中实现这些功能实体。
本示例实施方式中首先提供了一种基于区块链的业务链数据校核方法，该基于区块链的业务链数据校核方法可以运行于服务器，也可以运行于服务器集群或云服务器等，当然，本领域技术人员也可以根据需求在其他平台运行本申请的方法，本示例性实施例中对此不做特殊限定。参考图1所示，该基于区块链的业务链数据校核方法可以包括以下步骤：
步骤S110、获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
步骤S120、根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
步骤S130、解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
步骤S140、基于所述属性关系表，将所述业务链路数据映射为数据关系表；
步骤S150、将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
下面，将结合附图对本示例实施方式中上述基于区块链的业务链数据校核方法中的各步骤进行详细的解释以及说明。
在步骤S110中，获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划。
在本示例实施方式中，目标业务可以是任意由组成该业务节点的子网络中各节点相互配合所完成的业务，例如，可以是航材维修业务或者某个工作流平台上的系统业务。业务节点的子网络可以是由多个业务节点互联组成的区块链子网络，可以共享数据。例如，在航材维修业务中由区块链的主要参与方有航司、维修企业、物流企业、仓储企业和海关等单位的终端设备互联得到的子网络。业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，例如，由维修企业提供维修租赁合同、报价单、工单等数据；由物流企业通过手持PDA，在出入库及维修点等关键节点扫描RFID的方式，形成闭环作业流程信息（商品信息、位置信息、流程信息）；通过航司提供维修需求的邮件信息、维修确认信息，出入卡口时的RFID扫描信息；仓储企业的料件出入库信息等。在工作流平台上的系统业务中可以是工作流平台连接的不同企业的数据库节点在工作流任务中调用数据及产出的各种数据。其中，不同的业务节点按照预定标准格式上传各自的数据。
路径规划节点上传闭环业务流程中的节点路径规划，路径规划节点在接收到业务启动指令时，通过将目标业务分解为子业务，然后针对各子业务，在所述业务节点的子网络进行任务广播，接收到各业务节点返回的信息后，通过业务整体分析规划，得到所有子业务的节点集合，及节点集合中各节点的流转顺序等节点路径规划，在区块链的子网络中可以进行加密共享。
在步骤S120中，根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据。
在本示例实施方式中，流转路径数据为节点路径规划中各业务节点之间进行业务交接的相关数据，目标业务规划的在各个业务节点之间流转的位置信息（例如，业务节点对应的终端的地理位置信息）、节点的子任务启动时间、节点的子任务完成时间、每个节点的子任务配置信息（例如，完成子任务所配置的设备信息等）、每个节点内部的任务流程信息（例如，每个节点内子节点的流转流程数据）等数据。
根据不同的实时情况路径规划节点会规划出不同的路径，不同的路径会使得业务操作过程具有不同的代价，产生不同的数据。例如，根据各个节点的实际情况，可以产生ABCDE或者ABDCDED等路径，进而由于路径不同，业务交接时对应的数据业务不同。业务相关的节点，也就是业务节点子网络中的业务节点的数量级越大，流转路径会越多。
在一个具体实施例中，参见图2，步骤S120具体包括：
步骤S1201、按照所述节点路径规划中的节点顺序及每个节点的子任务标识，生成每个节点对应的流转路径数据提取命令；
步骤S1202、将所述流转路径数据提取命令发送到所述流转路径数据提取命令对应的业务节点，得到所述流转路径数据提取命令对应的业务节点返回的数据表；
步骤S1203、根据所述数据表，从所述业务链路数据中提取流转路径数据。
在步骤S1201中，根据不同的实时情况路径规划节点会规划出不同的路径，例如，根据各个节点的实际情况，可以产生ABCDE或者ABDCDED等路径，而不同的路径对应了不同的节点顺序。节点的子任务标识是用于唯一标识节点对应的子任务，包括但不限于节点的子任务启动时间、节点的子任务完成时间、节点的子任务配置信息。
根据节点顺序以及每个节点的子任务标识可以生成每个节点对应的流转路径数据提取命令。流转路径数据提取命令用于指示提取流转路径数据。
在步骤S1202中，业务节点获取到对应的流转路径数据提取命令后，会根据该命令返回数据表，在数据表中存储有流转路径数据。
在步骤S1203中，通过步骤S1202接收到数据表后，根据该数据表可以提取到流转路径数据。
继续参见图1，在步骤S130中，解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表。
在本示例实施方式中，解析目标业务的流转路径数据可以是按照节点路径规划，依次将相邻的两个节点归为一个集合，例如，对于ABCDEF这6个节点，可以划分得到AB、BC...EF等节点集合，然后将每个节点集合作为一个数组元素，将每个数组元素对应的业务交接相关数据存储至相应元素中，得到目标业务的节点关系网络，该节点关系网络也可以通过表格、矩阵等形式解析得到。
节点业务关系网络可以反映目标业务的业务流程的所有流转特征，例如，矩阵的行和列都对应于节点，矩阵单元中的数据即两个节点的对比数据，例如位置对比数据。这样可以基于流转网络准确描述当前流转路径节点的所有特征及与标准路径节点的对照特征。
属性关系表为对应于节点关系的不同属性数据的关系表，根据相邻节点的关系可以得到前后两个节点产生的不同属性数据之间的关系，例如，对于材料加工节点与设备维修节点，在相邻时，节点关系可以为材料准备与消耗关系，然后按照这两个节点的子关系网络反映的特征（例如，每个节点的子任务配置信息（例如，完成对应子任务所配置的设备信息等）、每个节点内部的任务流程信息（例如，每个节点内子节点的流转流程数据）等数据），可以得到这两个节点会上传的各种属性数据的关系（例如，使用数量的相关数据，如出区、进区的材料数量信息、维修企业的料件使用信息等）。即属性关系表指示了目标业务的业务链数据中需要校核的数据属性关系。
在一个具体实施例中，参见图3，获取与所述节点关系网络对应的属性关系表，包括：
步骤S310、将所述节点关系网络输入预设数据特征提取模型，得到与所述目标业务的闭环业务流程的数据特征；
步骤S320、将所述数据特征与数据库中的数据特征样本进行匹配，得到与所述数据特征匹配的数据特征样本；
步骤S330、将所述数据特征样本对应的预设属性关系表，作为所述节点关系网络对应的预设属性关系表。
在另一个具体实施例中，获取所述节点关系网络对应的属性关系表，包括：
通过开发属性关系表生成代码，利用该代码分析目标业务的节点关系网络，生成属性关系表。
在该实施例中，为了生成属性关系表，可以通过开发代码的方式，其中，可以通过对源代码进行编写和/或修改操作来进行代码开发，具体地，可按预设的标准对源代码进行编写和/或修改。在其它实施例中，该代码开发也可以是直接接收用户编写的代码。
当需要生成属性关系表时，通过扫描代码库索引，调取开发的属性关系表生成代码对目标业务的节点关系网络进行分析以生成属性关系表。
在一个实施例中，属性关系表包括：与节点路径规划中的节点顺序一致的各数据的属性的关系表。
例如，对于ADBEFJD的节点路径规划，属性关系表中的列对应于各种数据属性，例如材料数量、耗费价格等。表1中的列可以对应于相邻两个节点的数据属性之间的关系，例如，相加或者相减等。
例如表1
  A节点 数据关系 C节点
A材料数量   相减  
继续参见图1，在步骤S140中，基于所述属性关系表，将所述业务链路数据映射为数据关系表。
将各个业务属性的数据映射到预设属性关系表中每个属性相应的单元就可以得到对当前目标业务的所有数据根据路径特征进行可靠的整理的数据关系表。预设属性关系表中包括基于各个属性之间的关联关系建立的对照单元。这样数据关系表可以可靠的表征该目标业务所有的数据之间的关联关系。
例如，一个数据关系表2为：
  A节点 数据关系 C节点
A材料数量 50 相减 30
继续参见图1，在步骤S150中，将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
预设校核模块为预先开发的校核算法的模板，每个预设属性关联关系表中属性之间的关联关系由于业务的流转路径不同而不同。业务的流转路径包括了执行的先后顺序，影响数据变化过程，例如，通过运用RFID技术搭建物联网物流监控模块，实时监控航空料件和设备的位置及动态，形成闭环的料件位置数据流。利用校核算法模板，可以将数据关系表中的数据在计算过程不断映射为相应的参数，进行校验，得到较验结果。
以这种方式通过建立可以准确表征路径特征的流转网络，进行匹配对应的预设属性关系表，然后基于预设属性关系表对应的校核算法模板，可以准确可靠的校核得到校核结果；基于区块链数据的不可篡改特性，可以保证数据的真实性和不可篡改，使得数据校核过程与业务进程分开，保证业务高效性。
在一个具体实施例中，在将数据关系表数据预设校核模块，得到业务链路数据的校核结果之后，还包括：
从维护信息库中获取与所述校核结果匹配的维护信息后共享至所述业务节点的子网络。
在本实施例中，维护信息库是用于存储业务节点子网络上的业务链路数据的维护信息的数据库，其中，维护信息可以对业务节点子网络上的业务链路数据进行替换，从而使得业务节点能够根据维护信息进行二次维护。在得到业务链路数据的校核结果之后，可以从维护信息库中获取与校核结果匹配的维护信息，并将获取到的维护信息共享到业务节点子网络。
获取与校核结果相匹配的维护信息可以是通过查表的方式获取，在维护信息库中存储有校核结果与维护信息之间的对应关系表，在已知校核结果的情况下，通过查询对应关系表获取相匹配的维护信息；获取与校核结果相匹配的维护信息还可以是通过动态计算的方式获取，当得到校核结果之后，通过一定的公式计算得出与其相匹配的维护信息。当然还可以是通过其他方式获取与校核结果相匹配的维护信息，本申请在此不做限定。
在一个具体实施例中，参见图4，在从维护信息库中获取与所述校核结果匹配的维护信息后共享至所述业务节点的子网络之后，还包括：
步骤S410、获取业务节点的子网络中各个业务节点根据维护信息上传的补正数据；
步骤S420、用所述补正数据替换所述业务节点子网络中的目标业务的业务链路数据中业务相关数据后，对所述业务链数据进行二次维护。
在步骤S410中，业务节点子网络中的各个业务节点接收到维护信息后，可以根据维护信息生成补正数据，补正数据是通过业务节点的业务链路数据与维护信息之间进行比较后所生成的，可以是增加、删除、修改等方式。
在步骤S420中，因为补正数据是得到校核结果后，根据维护信息进行修正而得到的数据，是更为准确真实的，因此，可以选择用补正数据替换业务节点子网络中的目标业务的业务链路数据中的业务相关数据，对业务链数据进行二次维护。其中，在二次维护的过程中可以按照图1-图3所示的方法进行业务链路数据的校核。
图5示意性示出一种基于区块链的业务链数据校核方法应用在AOG航材维修业务中的流程图。
AOG(Aircraft On Ground)指飞机停场待用航材。AOG是航空运输中的特种货物代码，指紧急订货的航材，必须以最快速度运达目的地。故障飞机更换完航材零件后，才能继续执行飞行任务。AOG紧急维修业务中，需建立“实时跟踪和监控制度”，从器材的订购、催修、求援、发运、报关、提货直到器材最终交付给维修人员的各个环节，做到无缝隙控制，尽最大可能缩短维修时间。其中保税航材的报关环节耗时最长，这个环节里，由于材料繁多，手续复杂，流程冗长，加上监管严格，保税状态下的航材必须申报海关批复后才能运出海关特殊监管区域，这势必会延长维修时间，满足不了航空AOG场景下的需求，时效性无法保证。采用出区保函、保证金的形式能稍微加快报关流程，效果并不显著，这种非技术的解决方案也会大大增加企业的经营压力，同时海关也无法对出区的保税航材进行有效监管，不能真正的放心。
基于此，利用本申请中的基于区块链的业务链数据校核方法，由业务相关方航空公司、维修企业、物流企业、仓储企业和海关组建联盟，搭建AOG航材保障链，将各方信息上链，保证业务真实性的同时，对保税货物进行实时跟踪和有效监管，实现先出区后报关的业务模式，大大增强时效性，提高企业的竞争力。
在这个联盟链网络里，航空公司、维修企业、物流企业、仓储企业和海关作部署区块链节点，底层按照约定的共识算法，共同维护账本数据，每个节点的上层跟各自的业务系统对接，实现数据导入。
具体来说，由维修商企业提供维修租赁合同、报价单、工单；由物流企业通过手持PDA，在出入库及维修点等关键节点扫描RFID的方式，形成闭环作业流程信息(商品信息、位置信息、流程信息)，辅助关员对出区的航空料件进行有效监管。此外，通过航司提供订购、催修、求援的信息、维修确认信息，从侧面辅助关员验证维修业务的真实性与必要性。出入卡口时的RFID扫描信息，仓储企业的料件出入库信息，也可作为额外的数据源，用于设备使用时间和料件数量的交叉验证。
由于区块链保证了上链数据的真实性，海关对保税货物的数量以及位置都能有效监管，才会放心的让企业先行将AOG航材运出特殊监管区域，待完成维修任务后，再行报关。
区块链的主要参与方有航司、维修企业、物流企业、仓储企业和海关。使用区块链加物联网技术，由维修商企业提供维修租赁合同、报价单、工单；由物流企业通过手持PDA，在出入库及维修点等关键节点扫描RFID的方式，形成闭环作业流程信息(商品信息、位置信息、流程信息)，辅助关员对出区料件、设备进行有效监管。此外，通过航司提供维修需求的邮件信息、维修确认信息，从侧面辅助关员验证维修业务的真实性与必要性。出入卡口时的RFID扫描信息，仓储企业的料件出入库信息，也可作为额外的数据源，用于设备使用时间和料件数量的交叉验证。后期与金二系统实现数据互通后，通过核注清单、核放单、以及料件出入库单，完成维修流程的闭合管理。
其中通过运用RFID技术搭建保税区区内及区外物联网物流监控模块，实时监控航空料件和设备的位置及动态，形成闭环的料件位置数据流，为区块链提供可靠的基础数据。
1） RFID技术制作唯一可识别的电子签封，大型料件采用一次性绑带悬挂于料件上，小型料件采用周转介质，周转介质绑定电子签封。
2）基于企业仓库管理系统，制作并划分电子库位，实时显示料件的库存位置和库存状态，方便监管部门抽检核验；
3）出库时扫描料件签封，核查并记录料件出库数量、出库状态及出库时间，形成料件出库节点，出库数据上传区块链；
4）料件到达保税区卡口时，卡口核查人员扫描料件电子签封，核查料件数量及状态，形成料件出卡口节点，出卡口数据上传区块链；
5）运输路径采用GPS定位技术形成料件运输轨迹，形成料件运动轨迹节点，运动轨迹数据上传区块链；
6）到达机场后，维修人员启封料件前，扫描电子标签，确定料件数量及状态是否完整，确认启封后进行维修，维修完成后，客户确认维修使用料件数量，并进行电子签名。维修节点形成料件使用数据，并上传区块链；
7）如存在未使用的料件，则未使用的料件由维修人员确认数量后建立新的电子签封，依次完成运输——卡口扫描——入库扫描等节点；所有节点数据上传区块链；
通过以上各个节点，形成完整的航空料件和设备从出区——运输——使用——回仓的链路，可真实的记录料件的运动轨迹及各个节点的数据及状态，为区块链提供料件出区后完整的轨迹数据，方便后期多方验证，更好的完成保税航材出区后的监控监管。
本公开还提供了一种基于区块链的业务链数据校核装置。参考图5所示，该基于区块链的业务链数据校核装置可以包括获取模块610、提取模块620、解析模块630、映射模块640以及输入模块650。其中：
获取模块610，用于获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
提取模块620，用于根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
解析模块630，用于解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
映射模块640，用于基于所述属性关系表，将所述业务链路数据映射为数据关系表；
输入模块650，用于将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
上述基于区块链的业务链数据校核装置中各模块的具体细节已经在对应的基于区块链的业务链数据校核方法中进行了详细的描述，因此此处不再赘述。
应当注意，尽管在上文详细描述中提及了用于动作执行的设备的若干模块或者单元，但是这种划分并非强制性的。实际上，根据本公开的实施方式，上文描述的两个或更多模块或者单元的特征和功能可以在一个模块或者单元中具体化。反之，上文描述的一个模块或者单元的特征和功能可以进一步划分为由多个模块或者单元来具体化。
此外，尽管在附图中以特定顺序描述了本公开中方法的各个步骤，但是，这并非要求或者暗示必须按照该特定顺序来执行这些步骤，或是必须执行全部所示的步骤才能实现期望的结果。附加的或备选的，可以省略某些步骤，将多个步骤合并为一个步骤执行，以及/或者将一个步骤分解为多个步骤执行等。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本公开实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质（可以是CD-ROM，U盘，移动硬盘等）中或网络上，包括若干指令以使得一台计算设备（可以是个人计算机、服务器、移动终端、或者网络设备等）执行根据本公开实施方式的方法。
在本公开的示例性实施例中，还提供了一种能够实现上述方法的电子设备。
所属技术领域的技术人员能够理解，本申请的各个方面可以实现为系统、方法或程序产品。因此，本申请的各个方面可以具体实现为以下形式，即：完全的硬件实施方式、完全的软件实施方式（包括固件、微代码等），或硬件和软件方面结合的实施方式，这里可以统称为“电路”、“模块”或“系统”。
下面参照图7来描述根据本申请的这种实施方式的电子设备700。图7显示的电子设备700仅仅是一个示例，不应对本申请实施例的功能和使用范围带来任何限制。
如图7所示，电子设备700以通用计算设备的形式表现。电子设备600的组件可以包括但不限于：上述至少一个处理单元710、上述至少一个存储单元720、连接不同系统组件（包括存储单元720和处理单元710）的总线730。
其中，所述存储单元存储有程序代码，所述程序代码可以被所述处理单元710执行，使得所述处理单元710执行本说明书上述“示例性方法”部分中描述的根据本申请各种示例性实施方式的步骤。例如，所述处理单元710可以执行如图1中所示的步骤S110：获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；S120：根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；步骤S130：解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；步骤S140：基于所述属性关系表，将所述业务链路数据映射为数据关系表；步骤S150：将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
存储单元720可以包括易失性存储单元形式的可读介质，例如随机存取存储单元（RAM）7201和/或高速缓存存储单元7202，还可以进一步包括只读存储单元（ROM）7203。
存储单元720还可以包括具有一组（至少一个）程序模块7205的程序/实用工具7204，这样的程序模块7205包括但不限于：操作系统、一个或者多个应用程序、其它程序模块以及程序数据，这些示例中的每一个或某种组合中可能包括网络环境的实现。
总线730可以为表示几类总线结构中的一种或多种，包括存储单元总线或者存储单元控制器、外围总线、图形加速端口、处理单元或者使用多种总线结构中的任意总线结构的局域总线。
电子设备700也可以与一个或多个外部设备700（例如键盘、指向设备、蓝牙设备等）通信，还可与一个或者多个使得用户能与该电子设备700交互的设备通信，和/或与使得该电子设备700能与一个或多个其它计算设备进行通信的任何设备（例如路由器、调制解调器等等）通信。这种通信可以通过输入/输出（I/O）接口750进行。并且，电子设备600还可以通过网络适配器760与一个或者多个网络（例如局域网（LAN），广域网（WAN）和/或公共网络，例如因特网）通信。如图所示，网络适配器760通过总线730与电子设备700的其它模块通信。应当明白，尽管图中未示出，可以结合电子设备700使用其它硬件和/或软件模块，包括但不限于：微代码、设备驱动器、冗余处理单元、外部磁盘驱动阵列、RAID系统、磁带驱动器以及数据备份存储系统等。
通过以上的实施方式的描述，本领域的技术人员易于理解，这里描述的示例实施方式可以通过软件实现，也可以通过软件结合必要的硬件的方式来实现。因此，根据本公开实施方式的技术方案可以以软件产品的形式体现出来，该软件产品可以存储在一个非易失性存储介质（可以是CD-ROM，U盘，移动硬盘等）中或网络上，包括若干指令以使得一台计算设备（可以是个人计算机、服务器、终端装置、或者网络设备等）执行根据本公开实施方式的方法。
在本公开的示例性实施例中，还提供了一种计算机可读存储介质，所述计算机可读存储介质可以是易失性，也可以是非易失性，所述计算机可读存储介质包括存储数据区和存储程序区，存储数据区存储根据区块链节点的使用所创建的数据，存储程序区存储有能够实现本说明书上述方法的程序产品，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的数据校核节点。在一些可能的实施方式中，本申请的各个方面还可以实现为一种程序产品的形式，其包括程序代码，当所述程序产品在终端设备上运行时，所述程序代码用于使所述终端设备执行如下步骤：
获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
基于所述属性关系表，将所述业务链路数据映射为数据关系表；
将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
参考图8所示，描述了根据本申请的实施方式的用于实现上述方法的程序产品800，其可以采用便携式紧凑盘只读存储器(CD-ROM)并包括程序代码，并可以在终端设备，例如个人电脑上运行。然而，本申请的程序产品不限于此，在本文件中，可读存储介质可以是任何包含或存储程序的有形介质，该程序可以被指令执行系统、装置或者器件使用或者与其结合使用。
所述程序产品可以采用一个或多个可读介质的任意组合。可读介质可以是可读信号介质或者可读存储介质。可读存储介质例如可以为但不限于电、磁、光、电磁、红外线、或半导体的系统、装置或器件，或者任意以上的组合。可读存储介质的更具体的例子（非穷举的列表）包括：具有一个或多个导线的电连接、便携式盘、硬盘、随机存取存储器（RAM）、只读存储器（ROM）、可擦式可编程只读存储器（EPROM或闪存）、光纤、便携式紧凑盘只读存储器(CD-ROM)、光存储器件、磁存储器件、或者上述的任意合适的组合。
计算机可读信号介质可以包括在基带中或者作为载波一部分传播的数据信号，其中承载了可读程序代码。这种传播的数据信号可以采用多种形式，包括但不限于电磁信号、光信号或上述的任意合适的组合。可读信号介质还可以是可读存储介质以外的任何可读介质，该可读介质可以发送、传播或者传输用于由指令执行系统、装置或者器件使用或者与其结合使用的程序。
可读介质上包含的程序代码可以用任何适当的介质传输，包括但不限于无线、有线、光缆、RF等等，或者上述的任意合适的组合。
可以以一种或多种程序设计语言的任意组合来编写用于执行本申请操作的程序代码，所述程序设计语言包括面向对象的程序设计语言—诸如Java、C++等，还包括常规的过程式程序设计语言—诸如“C”语言或类似的程序设计语言。程序代码可以完全地在用户计算设备上执行、部分地在用户设备上执行、作为一个独立的软件包执行、部分在用户计算设备上部分在远程计算设备上执行、或者完全在远程计算设备或服务器上执行。在涉及远程计算设备的情形中，远程计算设备可以通过任意种类的网络，包括局域网（LAN）或广域网（WAN），连接到用户计算设备，或者，可以连接到外部计算设备（例如利用因特网服务提供商来通过因特网连接）。
此外，上述附图仅是根据本申请示例性实施例的方法所包括的处理的示意性说明，而不是限制目的。易于理解，上述附图所示的处理并不表明或限制这些处理的时间顺序。另外，也易于理解，这些处理可以是例如在多个模块中同步或异步执行的。
本领域技术人员在考虑说明书及实践这里公开的发明后，将容易想到本公开的其他实施例。本申请旨在涵盖本公开的任何变型、用途或者适应性变化，这些变型、用途或者适应性变化遵循本公开的一般性原理并包括本公开未公开的本技术领域中的公知常识或惯用技术手段。说明书和实施例仅被视为示例性的，本公开的真正范围和精神由权利要求指出。

Claims (20)

  1. 一种基于区块链的业务链数据校核方法，其中，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的数据校核节点，所述方法由数据校核节点执行，所述方法包括：
    获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
    根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
    解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
    基于所述属性关系表，将所述业务链路数据映射为数据关系表；
    将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
  2. 根据权利要求1所述的方法，其中，所述根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，包括：
    按照所述节点路径规划中的节点顺序及每个节点的子任务标识，生成每个节点对应的流转路径数据提取命令；
    将所述流转路径数据提取命令发送到所述流转路径数据提取命令对应的业务节点，得到所述所述流转路径数据提取命令对应的业务节点返回的数据表；
    根据所述数据表，从所述业务链路数据中提取流转路径数据。
  3. 根据权利要求1所述的方法，其中，所述获取与所述节点关系网络对应的属性关系表，包括：
    将所述节点关系网络输入预设数据特征提取模型，得到与所述目标业务的闭环业务流程的数据特征；
    将所述数据特征与数据库中的数据特征样本进行匹配，得到与所述数据特征匹配的数据特征样本；
    将所述数据特征样本对应的预设属性关系表，作为所述节点关系网络对应的预设属性关系表。
  4. 根据权利要求1所述的方法，其中，所述获取所述节点关系网络对应的属性关系表，包括：
    通过开发属性关系表生成代码，利用该代码分析目标业务的节点关系网络，生成属性关系表。
  5. 根据权利要求3或4所述的方法，其中，所述属性关系表包括与节点路径规划中的节点顺序一致的各数据的属性的关系表。
  6. 根据权利要求1所述的方法，其中，还包括：
    从维护信息库中获取与所述校核结果匹配的维护信息后共享至所述业务节点的子网络。
  7. 根据权利要求6所述的方法，其中，所述从维护信息库中获取与所述校核结果匹配的维护信息后共享至所述业务节点的子网络之后，还包括：
    获取业务节点的子网络中各个业务节点根据维护信息上传的补正数据；
    用所述补正数据替换所述业务节点子网络中的目标业务的业务链路数据中业务相关数据后，对所述业务链路数据进行二次维护。
  8. 一种基于区块链的业务链数据校核装置，其中，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的数据校核节点，所述装置包括：
    获取模块，用于获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
    提取模块，用于根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
    解析模块，用于解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
    映射模块，用于基于所述属性关系表，将所述业务链路数据映射为数据关系表；
    输入模块，用于将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
  9. 一种计算机可读存储介质，包括存储数据区和存储程序区，存储数据区存储根据区块链节点的使用所创建的数据，存储程序区存储有计算机程序，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的数据校核节点，其中，所述计算机程序被处理器执行时实现如下步骤：
    获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
    根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
    解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
    基于所述属性关系表，将所述业务链路数据映射为数据关系表；
    将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
  10. 根据权利要求9所述的计算机可读存储介质，其中，所述根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，包括：
    按照所述节点路径规划中的节点顺序及每个节点的子任务标识，生成每个节点对应的流转路径数据提取命令；
    将所述流转路径数据提取命令发送到所述流转路径数据提取命令对应的业务节点，得到所述所述流转路径数据提取命令对应的业务节点返回的数据表；
    根据所述数据表，从所述业务链路数据中提取流转路径数据。
  11. 根据权利要求9所述的计算机可读存储介质，其中，所述获取与所述节点关系网络对应的属性关系表，包括：
    将所述节点关系网络输入预设数据特征提取模型，得到与所述目标业务的闭环业务流程的数据特征；
    将所述数据特征与数据库中的数据特征样本进行匹配，得到与所述数据特征匹配的数据特征样本；
    将所述数据特征样本对应的预设属性关系表，作为所述节点关系网络对应的预设属性关系表。
  12. 根据权利要求9所述的计算机可读存储介质，其中，所述获取所述节点关系网络对应的属性关系表，包括：
    通过开发属性关系表生成代码，利用该代码分析目标业务的节点关系网络，生成属性关系表。
  13. 根据权利要求11或12所述的计算机可读存储介质，其中，所述属性关系表包括与节点路径规划中的节点顺序一致的各数据的属性的关系表。
  14. 根据权利要求9所述的计算机可读存储介质，其中，所述计算机程序被处理器执行时还实现如下步骤：
    从维护信息库中获取与所述校核结果匹配的维护信息后共享至所述业务节点的子网络。
  15. 根据权利要求14所述的计算机可读存储介质，其中，所述从维护信息库中获取与所述校核结果匹配的维护信息后共享至所述业务节点的子网络之后，所述计算机程序被处理器执行时还实现如下步骤：
    获取业务节点的子网络中各个业务节点根据维护信息上传的补正数据；
    用所述补正数据替换所述业务节点子网络中的目标业务的业务链路数据中业务相关数据后，对所述业务链路数据进行二次维护。
  16. 一种电子设备，所述电子设备为区块链中的数据校核节点，所述区块链包括业务节点的子网络以及与所述业务节点的子网络连接的所述数据校核节点，其中，所述电子设备包括：
    处理器；以及
    存储器，用于存储所述处理器的可执行指令；
    其中，所述处理器配置为经由执行所述可执行指令来执行如下步骤：
    获取上传到所述子网络中的目标业务的业务链路数据，所述业务链路数据为所述目标业务的闭环业务流程中由各业务节点上传的业务相关数据，所述业务相关数据中包括路径规划节点上传的所述闭环业务流程中的节点路径规划；
    根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，所述流转路径数据为所述节点路径规划中各业务节点之间进行业务交接的相关数据；
    解析所述目标业务的所述流转路径数据，得到所述目标业务的节点关系网络，以获取与所述节点关系网络对应的属性关系表，所述属性关系表为对应于节点关系的不同属性数据的关系表；
    基于所述属性关系表，将所述业务链路数据映射为数据关系表；
    将所述数据关系表输入预设校核模块，得到所述业务链路数据的校核结果。
  17. 根据权利要求16所述的电子设备，其中，所述根据所述节点路径规划，从所述业务链路数据中提取流转路径数据，包括：
    按照所述节点路径规划中的节点顺序及每个节点的子任务标识，生成每个节点对应的流转路径数据提取命令；
    将所述流转路径数据提取命令发送到所述流转路径数据提取命令对应的业务节点，得到所述所述流转路径数据提取命令对应的业务节点返回的数据表；
    根据所述数据表，从所述业务链路数据中提取流转路径数据。
  18. 根据权利要求16所述的电子设备，其中，所述获取与所述节点关系网络对应的属性关系表，包括：
    将所述节点关系网络输入预设数据特征提取模型，得到与所述目标业务的闭环业务流程的数据特征；
    将所述数据特征与数据库中的数据特征样本进行匹配，得到与所述数据特征匹配的数据特征样本；
    将所述数据特征样本对应的预设属性关系表，作为所述节点关系网络对应的预设属性关系表。
  19. 根据权利要求16所述的电子设备，其中，所述获取所述节点关系网络对应的属性关系表，包括：
    通过开发属性关系表生成代码，利用该代码分析目标业务的节点关系网络，生成属性关系表。
  20. 根据权利要求18或19所述的电子设备，其中，所述属性关系表包括与节点路径规划中的节点顺序一致的各数据的属性的关系表。
PCT/CN2021/078134 2020-04-01 2021-02-26 基于区块链的业务链数据校核方法、装置、存储介质、电子设备 WO2021196936A1 (zh)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202010248516.3 2020-04-01
CN202010248516.3A CN111598382A (zh) 2020-04-01 2020-04-01 基于区块链的业务链数据校核方法、装置、存储介质、电子设备

Publications (2)

Publication Number Publication Date
WO2021196936A1 true WO2021196936A1 (zh) 2021-10-07
WO2021196936A9 WO2021196936A9 (zh) 2021-12-09

Family

ID=72188647

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2021/078134 WO2021196936A1 (zh) 2020-04-01 2021-02-26 基于区块链的业务链数据校核方法、装置、存储介质、电子设备

Country Status (2)

Country Link
CN (1) CN111598382A (zh)
WO (1) WO2021196936A1 (zh)

Cited By (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114050964A (zh) * 2021-11-24 2022-02-15 北京鼎兴达信息科技股份有限公司 基于数据网业务路径变化对网络异常进行预判的方法
CN115423381A (zh) * 2022-10-31 2022-12-02 国网浙江省电力有限公司金华供电公司 基于智链id码的电力物资全链协同预警方法及平台
CN116238834A (zh) * 2022-12-08 2023-06-09 湖北凯乐仕通达科技有限公司 立体仓库系统的作业路径规划方法、装置及计算机设备

Families Citing this family (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111598382A (zh) * 2020-04-01 2020-08-28 深圳壹账通智能科技有限公司 基于区块链的业务链数据校核方法、装置、存储介质、电子设备
CN112036751B (zh) * 2020-09-01 2023-08-22 中国银行股份有限公司 一种流程关键作业节点的识别方法及装置
CN114615169B (zh) * 2020-12-03 2023-10-20 腾讯科技（深圳）有限公司 路径监控方法、装置和计算机可读存储介质
CN112799673B (zh) * 2021-01-19 2022-03-25 烽火通信科技股份有限公司 一种网络协议数据的校核方法及装置
CN114071515B (zh) * 2021-11-08 2023-07-04 北京东土拓明科技有限公司 网络优化方法、装置、设备和存储介质

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110161243A1 (en) * 2009-12-28 2011-06-30 Frank Brunswig Consistency checks for business process data
CN110070359A (zh) * 2019-03-19 2019-07-30 阿里巴巴集团控股有限公司 基于区块链的数据核对系统、方法、计算设备及存储介质
CN110493268A (zh) * 2019-09-24 2019-11-22 腾讯科技（深圳）有限公司 一种基于区块链网络的数据处理方法及装置
CN110750530A (zh) * 2019-09-11 2020-02-04 口碑(上海)信息技术有限公司 一种业务系统及其数据核对方法
CN111598382A (zh) * 2020-04-01 2020-08-28 深圳壹账通智能科技有限公司 基于区块链的业务链数据校核方法、装置、存储介质、电子设备

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110161243A1 (en) * 2009-12-28 2011-06-30 Frank Brunswig Consistency checks for business process data
CN110070359A (zh) * 2019-03-19 2019-07-30 阿里巴巴集团控股有限公司 基于区块链的数据核对系统、方法、计算设备及存储介质
CN110750530A (zh) * 2019-09-11 2020-02-04 口碑(上海)信息技术有限公司 一种业务系统及其数据核对方法
CN110493268A (zh) * 2019-09-24 2019-11-22 腾讯科技（深圳）有限公司 一种基于区块链网络的数据处理方法及装置
CN111598382A (zh) * 2020-04-01 2020-08-28 深圳壹账通智能科技有限公司 基于区块链的业务链数据校核方法、装置、存储介质、电子设备

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN114050964A (zh) * 2021-11-24 2022-02-15 北京鼎兴达信息科技股份有限公司 基于数据网业务路径变化对网络异常进行预判的方法
CN114050964B (zh) * 2021-11-24 2024-02-23 北京鼎兴达信息科技股份有限公司 基于数据网业务路径变化对网络异常进行预判的方法
CN115423381A (zh) * 2022-10-31 2022-12-02 国网浙江省电力有限公司金华供电公司 基于智链id码的电力物资全链协同预警方法及平台
CN116238834A (zh) * 2022-12-08 2023-06-09 湖北凯乐仕通达科技有限公司 立体仓库系统的作业路径规划方法、装置及计算机设备
CN116238834B (zh) * 2022-12-08 2024-01-02 湖北凯乐仕通达科技有限公司 立体仓库系统的作业路径规划方法、装置及计算机设备

Also Published As

Publication number Publication date
WO2021196936A9 (zh) 2021-12-09
CN111598382A (zh) 2020-08-28

Similar Documents

Publication Publication Date Title
WO2021196936A1 (zh) 基于区块链的业务链数据校核方法、装置、存储介质、电子设备
Baralla et al. Ensure traceability in European food supply chain by using a blockchain system
WO2022160707A1 (zh) 结合rpa和ai的人机互动方法、装置、存储介质及电子设备
US11307913B2 (en) Systems and methods for automated application programming interface evaluation and migration
US7788237B2 (en) Method and system for tracking changes in a document
US20180324051A1 (en) User interface for automated flows within a cloud based developmental platform
Zimmermann Architectural decisions as reusable design assets
US10101972B1 (en) Data modelling and flow engine for building automated flows within a cloud based developmental platform
US20180321833A1 (en) User interface for automated flows within a cloud based developmental platform
US20090204452A1 (en) Managing a multi-supplier environment
Sahara et al. Real-time data integration of an internet-of-things-based smart warehouse: a case study
US10013429B2 (en) Computer-implemented methods and systems for facilitating business-to-business transactions on a collaborative business network and for system integration message routing and identifier mapping utilizing a shared workspace mechanism
US11954064B2 (en) Framework for migrating applications to cloud computing environment
Bayram et al. Hub network design problem with capacity, congestion, and stochastic demand considerations
US20220067659A1 (en) Research and development system and method
Ilie-Zudor et al. A solution for information management in logistics operations of modern manufacturing chains
CN112182089A (zh) 基于数据仓库模型的报表生成方法、装置和设备
US20170032299A1 (en) Web-based System and Method for Facilitating Off-loading of Design Requirements to a Supplier
Márquez et al. Evaluating frameworks assemblies in microservices-based systems using imperfect information
Vera et al. Technological architecture to consume On-Premise ERP services from a hybrid cloud platform
Puspita et al. Framework zachman for design information system logistics management
Enjalbert et al. Distributed simulation of virtual workshops for the multi-site scheduling feasibility evaluation
Ribeiro et al. Improving productive processes using a process mining approach
CN117240348B (zh) 基于软件定义卫星共享星座的虚拟卫星构建方法和系统
US20240095239A1 (en) Multi-layer extensibility for enterprise portal

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 21779048

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

32PN Ep: public notification in the ep bulletin as address of the adressee cannot be established

Free format text: NOTING OF LOSS OF RIGHTS PURSUANT TO RULE 112(1) EPC (EPO FORM 1205A DATED 17/01/2023)

122 Ep: pct application non-entry in european phase

Ref document number: 21779048

Country of ref document: EP

Kind code of ref document: A1