Data verification method, central cloud end, source end, destination end, electronic equipment and storage medium

Abstract

The embodiment of the invention provides a data verification method, a central cloud end, a source end, a destination end, electronic equipment and a storage medium, the data verification method is applied to the central cloud end, and the data verification method comprises the following steps: receiving a data packet sent by the source end, an abstract of the data packet and a first evidence storage identifier corresponding to the abstract; the abstract of the received data packet is determined as a first abstract, the source end is any one of a plurality of side ends connected with the central cloud end, and the first evidence storage identifier is a corresponding identifier generated according to the abstract of the data packet when the source end calls a target service running on the source end; calling a target service running on the central cloud, and obtaining a corresponding abstract as a second abstract according to the first evidence storage identifier; and if the first abstract is the same as the second abstract, determining that data verification of the data packet received by the central cloud is passed. According to the scheme, the data transmission efficiency can be improved.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of data processing, and in particular to a data verification method, a central cloud, a source end, a destination end, an electronic device and a storage medium. Background Art

[0002] When business data flows between multiple business departments, data transmission is usually based on a cloud-edge-end model taking business needs into consideration.

[0003] At present, when data is transmitted in a cloud-edge mode, in order to ensure the security of data transmission as much as possible, the transmitted data is generally encrypted and decrypted to realize data verification during data transmission. For example, in the process of transmitting data from any edge such as the procuratorate, the court, and the judicial bureau to another edge, the data must be transmitted through the Political and Legal Affairs Commission end which is the central cloud. And whether the edge transmits data to the central cloud or the central cloud transmits data to the edge, the operator on the sending end will encrypt the data before sending it, and the operator on the receiving end must decrypt the data before subsequent sending or processing.

[0004] However, when data is encrypted during data transmission, the corresponding staff encrypts the data on the corresponding edge or central cloud according to the pre-set encryption rules. When data is decrypted during data transmission, the corresponding staff decrypts the data on the corresponding edge or central cloud according to the pre-acquired key or decryption rules, which makes the data verification process during data transmission more complicated. Therefore, the efficiency of data transmission is low. Summary of the invention

[0005] In view of this, an embodiment of the present application provides a data verification method, a central cloud, a source end, a destination end, an electronic device and a storage medium to at least partially solve the above-mentioned problems.

[0006] According to a first aspect of an embodiment of the present application, a data verification method is provided, which is applied to a central cloud. The data verification method includes: after receiving a data packet sent by a source end, a summary of the data packet and a first evidence identifier corresponding to the summary, determining the summary of the received data packet as a first summary, wherein the source end is any one of a plurality of edge ends connected to the central cloud, and the first evidence identifier is a corresponding identifier generated by the source end calling a target service running on the source end according to the summary of the data packet; calling the target service running on the central cloud, and obtaining the corresponding summary as a second summary according to the first evidence identifier; if the first summary is the same as the second summary, determining that the data verification of the data packet received by the central cloud has passed.

[0007] According to the second aspect of an embodiment of the present application, a data verification method is provided, which is applied to a source end, and the source end is any one of a plurality of edge ends connected to the central cloud end. The data verification method includes: obtaining a summary of a data packet whose destination end is any one of the plurality of edge ends; calling a target service running on the source end, and generating a corresponding first evidence identifier based on the summary of the data packet; and sending the data packet, the summary of the data packet, and the first evidence identifier to the central cloud end, so that the central cloud end performs data verification on the received data packet based on the first evidence identifier.

[0008] According to a third aspect of an embodiment of the present application, a data verification method is provided, which is applied to a destination end.

[0009] [HZTC-HXJKJD241004][HS2411166CCN] is any of the multiple edge ends connected to the central cloud, and the data verification method includes: after receiving a data packet sent by the central cloud, a summary of the data packet and a second evidence identifier corresponding to the summary, determining the summary of the received data packet as a third summary, wherein the second evidence identifier is a corresponding identifier generated by the central cloud calling a target service running on the central cloud according to the summary of the data packet; calling the target service running on the destination end, and obtaining the corresponding summary as a fourth summary according to the second evidence identifier; if the third summary is the same as the fourth summary, it is determined that the data verification of the data packet received by the destination end has passed.

[0010] According to the fourth aspect of an embodiment of the present application, a central cloud is provided, comprising: a first determination unit, for determining the summary of the received data packet as a first summary after receiving a data packet sent by a source end, a summary of the data packet and a first evidence identifier corresponding to the summary, wherein the source end is any one of a plurality of edge ends connected to the central cloud end, and the first evidence identifier is a corresponding identifier generated by the source end calling a target service running on the source end according to the summary of the data packet; a first acquisition unit, for calling the target service running on the central cloud end, and obtaining the corresponding summary as a second summary according to the first evidence identifier; and a first verification unit, for determining that the data packet received by the central cloud end has passed data verification when the first summary is the same as the second summary.

[0011] According to the fifth aspect of the embodiment of the present application, a source end is provided, and the source end is any one of the multiple edge ends connected to the central cloud, and the source end includes: a summary acquisition unit, used to obtain a summary of a data packet whose destination end is any one of the multiple edge ends; an identification generation unit, used to call a target service running on the source end, and generate a corresponding first evidence identification according to the summary of the data packet; a data sending unit, used to send the data packet, the summary of the data packet and the first evidence identification to the central cloud, so that the central cloud performs data verification on the received data packet according to the first evidence identification.

[0012] According to the sixth aspect of an embodiment of the present application, a destination end is provided, and the destination end is any one of the multiple edge ends connected to the central cloud, and the destination end includes: a second determination unit, which is used to determine the summary of the received data packet as a third summary after receiving a data packet sent by the central cloud, a summary of the data packet and a second evidence identifier corresponding to the summary, wherein the second evidence identifier is a corresponding identifier generated by the central cloud calling a target service running on the central cloud according to the summary of the data packet; a second acquisition unit, which is used to call the target service running on the destination end, and obtain the corresponding summary as a fourth summary according to the second evidence identifier; and a second verification unit, which is used to determine that the data verification of the data packet received by the destination end has passed when the third summary is the same as the fourth summary.

[0013] According to the seventh aspect of the embodiments of the present application, an electronic device is provided, comprising: a processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other through the communication bus; the memory is used to store at least one executable instruction, and the executable instruction enables the processor to perform operations corresponding to the above-mentioned first aspect, second aspect or third aspect method.

[0014] According to an eighth aspect of the embodiments of the present application, a computer storage medium is provided, on which a computer program is stored, and the program is executed by a processor to perform the method of the first aspect.

[0015] According to a sixth aspect of an embodiment of the present application, a computer program product is provided, comprising computer instructions, wherein the computer instructions instruct a computing device to execute the method of the first aspect, the second aspect or the third aspect mentioned above.

[0016] [HZTC-HXJKJD241004][HS2411166CCN]

[0017] According to the data verification scheme provided in the embodiment of the present application, after receiving the data packet sent by the source end among the multiple connected edge ends, the digest of the data packet and the first evidence identifier corresponding to the digest, the central cloud can determine the digest of the received data packet as the first digest, and call the target service to obtain the corresponding digest as the second digest according to the first evidence identifier. If the first digest is the same as the second digest, it is determined that the data verification of the received data packet has passed. Thus, the central cloud performs data verification on the data packet received from the source end by comparing whether the first digest and the second digest are the same, that is, by comparing the digest received from the source end and the corresponding digest obtained according to the first evidence identifier received from the source end, data verification is achieved on the data packet received from the source end. This data verification process can be performed automatically without the staff's perception, without the need for staff to operate, thereby simplifying the data verification process when transmitting data from the source end to the central cloud, and therefore, the efficiency of data transmission can be improved. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments recorded in the embodiments of the present application. For ordinary technicians in this field, other drawings can also be obtained based on these drawings.

[0019] Figure 1 is a flow chart of a data verification method according to an embodiment of the present application;

[0020] Figure 2 is a flow chart of a data verification method according to another embodiment of the present application;

[0021] Figure 3 is a flow chart of a data verification method according to another embodiment of the present application;

[0022] Figure 4 is a schematic diagram of a central cloud in one embodiment of the present application;

[0023] Figure 5 is a schematic diagram of a source end of an embodiment of the present application;

[0024] Figure 6 is a schematic diagram of a destination end of an embodiment of the present application;

[0025] Figure 7 It is a schematic diagram of an electronic device according to an embodiment of the present application. DETAILED DESCRIPTION

[0026] Data Validation Methods

[0027] An embodiment of the present application provides a data verification method, which is applied to a central cloud. The central cloud is connected to multiple edge terminals. Target services and non-target services are running on both the central cloud and the edge terminals. Any two of the multiple edge terminals transmit data through the central cloud.

[0028] For example, the central cloud is the Political and Legal Affairs Commission end, and the multiple edge ends are three edge ends, which are the Procuratorate end, the Court end and the Justice Bureau end. Based on this, the target service can be a blockchain service. For example, the target service running on the central cloud can specifically be the service provided by the smart judicial alliance chain platform deployed in the central cloud, and the target service running on the edge can specifically be the service provided by the blockchain node corresponding to the smart judicial alliance chain platform deployed in the edge. The non-target service can be a collaborative service. For example, the non-target service running on the central cloud can specifically be the service provided by the smart judicial cross-departmental business collaboration platform deployed in the central cloud, and the non-target service running on the edge can specifically be the service provided by the business collaboration node corresponding to the smart judicial cross-departmental business collaboration platform deployed in the edge.

[0029] The central cloud can specifically be a data center, a server, a personal computer, an Internet of Things (IoT) device and / or an embedded device, etc. The data verification method in the embodiment of the present application and the computing device part executing the solution are

[0030] [HZTC-HXJKJD241004][HS2411166CCN] has nothing to do with the hardware deployed.

[0031] The data verification method in the embodiment of the present application is described in detail below through multiple embodiments.

[0032] Figure 1 FIG. 1 is a flow chart of a data verification method according to an embodiment of the present application. Figure 1 As shown, the data verification method includes the following steps:

[0033] Step 101: After receiving a data packet sent by a source, a summary of the data packet and a first evidence identifier corresponding to the summary, the summary of the received data packet is determined as a first summary.

[0034] Among them, the source end is any one of the multiple edges connected to the central cloud, and the destination end of the data packet is any one of the above multiple edges. Optionally, the destination end of the data packet is any one of the above multiple edges other than the source end.

[0035] The data packet may include case-related data of the case to be coordinated. For example, the data packet may include case details, related case information, case card information, case status information, document type, file type, monitoring path information, file parsing method information, destination information, case card metadata and / or verification rules, etc. of the case to be coordinated. The embodiments of the present application are not limited to this.

[0036] The summary of the data packet may be a hash value, and the summary of the data packet may be calculated using algorithms such as md5, sha1, sha256 and / or national encryption SM3, etc., which is not limited in the embodiments of the present application.

[0037] The first evidence identifier is a corresponding identifier generated by the source end calling the target service running on the source end according to the summary of the data packet. For example, the target service running on the source end is a service provided by the blockchain node corresponding to the smart judicial alliance chain platform deployed in the source end. Based on this, the first evidence identifier can be generated in the source end in the following manner: after determining the summary of the data packet, the source end can call the blockchain node smart contract to store the summary of the data packet on the chain to obtain the first evidence identifier, wherein the first evidence identifier can be an evidence hash, a transaction hash, an evidence ID (Identity document, unique code) or a transaction ID, etc., and the embodiments of the present application are not limited to this.

[0038] In a specific embodiment, based on the deployment of blockchain nodes and business collaboration nodes in the source end, and the deployment of a smart judicial alliance chain platform and a smart judicial cross-departmental business collaboration platform in the central cloud, after the source end obtains a summary of the data packet based on the data packet and determines the first evidence identifier based on the summary of the data packet, the data packet, the summary of the data packet and the first evidence identifier corresponding to the summary can be sent to the smart judicial cross-departmental business collaboration platform in the central cloud through the business collaboration node. After receiving the data packet, the summary of the data packet and the first evidence identifier corresponding to the summary sent by the source end, the smart judicial cross-departmental business collaboration platform in the central cloud can determine the summary of the received data packet as the first summary.

[0039] Step 102: Call the target service running on the central cloud, and obtain the corresponding digest as the second digest according to the first evidence identifier.

[0040] In a specific embodiment, based on the deployment of blockchain nodes and business collaboration nodes in the source end, and the deployment of a smart judicial alliance chain platform and a smart judicial cross-departmental business collaboration platform in the central cloud, after the target service running on the source end is called in the source end to generate a first evidence identifier, the correspondence between the first evidence identifier and the summary can be queried on the smart judicial alliance chain platform, so that the smart judicial cross-departmental business collaboration platform on the central cloud can initiate a query request to the smart judicial alliance chain platform according to the first evidence identifier after receiving the data packet, the summary of the data packet and the first evidence identifier corresponding to the summary, that is, send the first evidence identifier to the smart judicial alliance chain platform, so that the smart judicial alliance chain platform obtains the summary corresponding to the first evidence identifier, thereby realizing the call of the target service running on the central cloud to obtain the summary corresponding to the first evidence identifier, and then the smart judicial alliance chain platform can return the summary corresponding to the first evidence identifier to the smart judicial cross-departmental business collaboration platform. Platform, the smart judicial cross-departmental business collaboration platform then determines the summary corresponding to the first evidence identifier as the second summary, or the smart judicial alliance chain platform directly determines the summary corresponding to the second evidence identifier as the fourth summary. The embodiment of the present application is not limited to this. After the smart judicial alliance chain platform determines the fourth summary, the smart judicial alliance chain platform can perform a data verification process on the data packet, for example, including executing step 303 below, etc., or the smart judicial alliance chain platform sends the fourth summary to the smart judicial cross-departmental business collaboration platform, and then the smart judicial cross-departmental business collaboration platform performs a data verification process on the data packet, for example, including executing step 303 below, etc. The embodiment of the present application is not limited to this. Based on this, if there is a page for performing data verification on the data packet in the central cloud, the page for performing data verification on the data packet can be set in the smart judicial cross-departmental business collaboration platform, or it can be set in the smart judicial cross-departmental business collaboration platform.

[0041] Step 103: If the first digest is the same as the second digest, it is determined that the data packet received by the central cloud has passed the data verification.

[0042] In a specific embodiment, after determining the first digest and the second digest, it is determined whether the first digest and the second digest are the same; if the first digest and the second digest are the same, that is, the digest of the data packet received by the central cloud from the source end and the digest obtained by the central cloud according to the first evidence identifier received from the source end are the same, indicating that the first digest received by the central cloud is recorded on the chain, and then the data packet received by the central cloud is highly likely not to have been tampered with. At this time, the data verification performed by the central cloud on the received data packet passes, that is, the data packet is credible; if the first digest and the second digest are different, it means that the first digest received by the central cloud is not recorded on the chain, and then the data packet received by the central cloud is highly likely to have been tampered with, that is, the digest of the data packet received by the central cloud from the source end and the digest obtained by the central cloud according to the first evidence identifier received from the source end are not the same. At this time, the data verification performed by the central cloud on the received data packet fails, that is, the data packet is unreliable. Therefore, the accuracy, security and reliability of data transmitted from the edge to the central cloud can be ensured as much as possible.

[0043] In an embodiment of the present application, after receiving a data packet sent by a source end among multiple connected edges, a digest of the data packet, and a first evidence identifier corresponding to the digest, the central cloud can determine the digest of the received data packet as the first digest, and call the target service to obtain the corresponding digest as the second digest according to the first evidence identifier. If the first digest is the same as the second digest, it is determined that the data verification of the received data packet has passed. Thus, the central cloud performs data verification on the data packet received from the source end by comparing whether the first digest and the second digest are the same, that is, by comparing the digest received from the source end and the corresponding digest obtained according to the first evidence identifier received from the source end to verify whether they are the same, the data packet received from the source end is verified. This data verification process can be performed automatically without the staff's perception, and no staff operation is required, thereby simplifying the data verification process when transmitting data from the source end to the central cloud, and therefore, the efficiency of data transmission can be improved.

[0044] In one possible implementation, the central cloud is the Political and Legal Affairs Commission end, and three of the multiple ends are the Procuratorate end, the Court end, and the Justice Bureau end. Thus, the data verification method in this application can enable cross-departmental case data of the Law and Procuratorate to flow reliably.

[0045] In a possible implementation, the data verification method of the embodiment of the present application may also include the following specific processing: after determining that the data packet received by the central cloud has passed the data verification, obtaining a summary of the data packet; calling the target service running on the central cloud, and generating a corresponding second evidence identifier based on the summary of the data packet; sending the data packet, the summary of the data packet and the second evidence identifier to the destination end of the data packet in multiple edge ends, so that the destination end performs data verification on the received data packet based on the second evidence identifier.

[0046] In a specific implementation, the central cloud can obtain a summary of the data packet after the received data packet is verified. When the central cloud obtains the summary, the summary of the data packet received from the source end can be directly determined as the summary of the data packet obtained by the central cloud.

[0047] [HZTC-HXJKJD241004][HS2411166CCN] can also call the non-target service running on the central cloud to generate a corresponding summary based on the data packet received from the source end, and determine the summary as the summary obtained by the central cloud. The embodiment of the present application is not limited to this; then the central cloud can call the target service running on the central cloud to generate a second evidence identifier corresponding to the summary based on the summary obtained by the central cloud, and then send the data packet, the summary of the data packet obtained and the second evidence identifier to the destination end of the data packet in multiple edge ends, so that the destination end verifies the received data packet according to the second evidence identifier. The process of the destination end verifying the received data packet according to the second evidence identifier is the same as the process of the central edge end verifying the received data packet according to the first evidence identifier. The embodiment of the present application will not be repeated here.

[0048] In the embodiment of the present application, not only can the central cloud perform data verification on the data packets received from the source end, but the central cloud can also send a summary of the data packet and a second evidence identifier to the destination end, so that the destination end can perform data verification on the data packet received from the central cloud. The data verification process at the destination end can also be performed automatically without the staff's perception and without the need for staff operation, thereby simplifying the data verification process when transmitting data from the central cloud to the destination end, and therefore, the efficiency of data transmission can be further improved.

[0049] Data Validation Methods

[0050] An embodiment of the present application provides a data verification method, which is applied to a source end, and the source end is any edge end among multiple edge ends connected to a central cloud. The edge end of this embodiment is the edge end of the aforementioned method embodiment, and the central cloud of this embodiment is the central cloud of the aforementioned method embodiment. The edge end and the central cloud have been specifically described in the aforementioned method embodiment, and the embodiments of the present application will not be repeated here.

[0051] Among them, the source end can specifically be a data center, a server, a personal computer, an Internet of Things (IoT) device and / or an embedded device, etc. The data verification method in the embodiment of the present application is independent of the hardware deployed by the computing device that executes the solution.

[0052] It should be noted that the central cloud in this embodiment is used to implement the corresponding data verification method in the aforementioned method embodiment, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0053] The data verification method in the embodiment of the present application is described in detail below through multiple embodiments.

[0054] Figure 2 FIG. 1 is a flow chart of a data verification method according to another embodiment of the present invention. Figure 2 As shown, the data verification method includes the following steps:

[0055] Step 201: Obtain a summary of a data packet whose destination is any edge among multiple edges.

[0056] Among them, the data packet and the summary of the data packet have been introduced in the aforementioned method embodiment, and the embodiments of the present application will not be repeated here.

[0057] Optionally, the destination end of the data packet is any end other than the source end among the multiple ends mentioned above.

[0058] In a specific implementation, based on the deployment of blockchain nodes and business collaboration nodes in the source end, and the deployment of a smart judicial alliance chain platform and a smart judicial cross-departmental business collaboration platform in the central cloud, the business system in the source end can send a data packet to the business collaboration node in the source end, and then call the non-target service running on the source end through the business collaboration node to determine the summary of the data packet based on the data packet.

[0059] Step 202: Call the target service running on the source end, and generate a corresponding first evidence identifier according to the summary of the data packet.

[0060] The specific implementation method of generating the first evidence identifier at the source end and the first evidence identifier have been introduced in the aforementioned method embodiment, and will not be repeated here in the embodiment of the present application.

[0061] Step 203: Send the data packet, the summary of the data packet and the first evidence identification to the central cloud, so that the central cloud performs data verification on the received data packet according to the first evidence identification.

[0062] In a specific embodiment, after obtaining the data packet, the summary of the data packet and the first evidence identifier at the source end, the business collaboration node can call the non-target service running on the source end to send the data packet, the summary of the data packet and the first evidence identifier to the smart judicial cross-departmental business collaboration platform deployed in the central cloud. Subsequently, the central cloud can perform data verification on the received data packet according to the first evidence identifier. The specific implementation method of the central cloud performing data verification on the received data packet according to the first evidence identifier has been introduced in the aforementioned method embodiment and will not be repeated here in the embodiments of the present application.

[0063] In an embodiment of the present application, the source end can obtain a summary of a data packet whose destination end is any of the multiple edge ends, and then call the target service running on the source end, generate a corresponding first evidence identifier based on the summary of the data packet, and then send the data packet, the summary of the data packet and the first evidence identifier to the central cloud, so that the central cloud can perform data verification on the received data packet based on the first evidence identifier. Thus, the summary of the data packet and the first evidence identifier provided by the source end enable the central cloud to perform data verification on the data packet received from the source end. This data verification process can be performed automatically without the staff's perception, and no staff operation is required, thereby simplifying the data verification process when transmitting data from the source end to the central cloud, and therefore, the efficiency of data transmission can be improved.

[0064] Data Validation Methods

[0065] An embodiment of the present application provides a data verification method, which is applied to a destination end, and the destination end is any edge end among multiple edge ends connected to a central cloud. The edge end of this embodiment is the edge end of the aforementioned method embodiment, and the central cloud of this embodiment is the central cloud of the aforementioned method embodiment. The edge end and the central cloud have been specifically described in the aforementioned method embodiment, and the embodiments of the present application will not be repeated here.

[0066] Among them, the destination end can specifically be a data center, a server, a personal computer, an Internet of Things (IoT) device and / or an embedded device, etc. The data verification method in the embodiment of the present application is independent of the hardware deployed by the computing device that executes the solution.

[0067] It should be noted that the central cloud in this embodiment is used to implement the corresponding data verification method in the aforementioned method embodiment applied to the central cloud, and has the beneficial effects of the corresponding method embodiment. The source end in this embodiment is used to implement the corresponding data verification method in the aforementioned method embodiment applied to the source end, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0068] The data verification method in the embodiment of the present application is described in detail below through multiple embodiments.

[0069] Figure 3 FIG. 1 is a flow chart of a data verification method according to another embodiment of the present application. Figure 3 As shown, the data verification method includes the following steps:

[0070] Step 301: After receiving a data packet, a summary of the data packet, and a second evidence identifier corresponding to the summary, the summary of the received data packet is determined as a third summary.

[0071] Among them, the data packet and the summary of the data packet have been introduced in the aforementioned method embodiment, and the embodiments of the present application will not be repeated here; the second evidence identifier is the corresponding identifier generated by the central cloud calling the target service running on the central cloud according to the summary of the data packet. The specific generation process of the second evidence identifier has been introduced in the aforementioned method embodiment, and the embodiments of the present application will not be repeated here.

[0072] In a specific implementation, a blockchain node and a business collaboration node are deployed on the destination end, and the central cloud

[0073] [HZTC-HXJKJD241004][HS2411166CCN] deploys a smart judicial alliance chain platform and a smart judicial cross-departmental business collaboration platform. After the central cloud obtains the summary of the data packet based on the data packet and determines the second evidence identifier based on the summary of the data packet, the data packet, the summary of the data packet and the second evidence identifier corresponding to the summary can be sent to the business collaboration node at the destination end through the business collaboration node. After receiving the data packet, the summary of the data packet and the second evidence identifier corresponding to the summary sent by the central cloud, the business collaboration node at the destination end can determine the summary of the received data packet as the third summary.

[0074] Step 302: Call the target service running on the destination end, and obtain the corresponding digest as the fourth digest according to the second evidence identifier.

[0075] Based on the deployment of blockchain nodes and business collaboration nodes in the destination end, and the deployment of a smart judicial alliance chain platform and a smart judicial cross-departmental business collaboration platform in the central cloud, after calling the target service running on the central cloud in the central cloud to generate a second evidence identifier, the correspondence between the second evidence identifier and the summary can be queried at the blockchain node of the destination end, so that after receiving the data packet, the summary of the data packet and the second evidence identifier corresponding to the summary, the business collaboration node of the destination end can initiate a query request to the blockchain node of the destination end according to the second evidence identifier, that is, send the second evidence identifier to the blockchain node of the destination end, so that the blockchain node of the destination end obtains the summary corresponding to the second evidence identifier, thereby realizing the call of the target service running on the destination end to obtain the summary corresponding to the second evidence identifier, and then the blockchain node of the destination end can return the summary corresponding to the second evidence identifier to the destination end. The business collaboration node at the destination end, the business collaboration node at the destination end then determines the summary corresponding to the second evidence identifier as the fourth summary, or the blockchain node at the destination end directly determines the summary corresponding to the second evidence identifier as the fourth summary. The embodiment of the present application is not limited to this. After the blockchain node at the destination end determines the fourth summary, the blockchain node at the destination end can perform a data verification process on the data packet, for example, including executing step 303 below, etc., or the blockchain node at the destination end sends the fourth summary to the business collaboration node at the destination end, and then the business collaboration node performs data verification on the data packet, for example, including executing step 303 below, etc. The embodiment of the present application is not limited to this. Based on this, if there is a page for performing data verification on the data packet in the destination end, the page for performing data verification on the data packet can be set in the blockchain node, or in the business collaboration node.

[0076] Step 303: If the third digest is the same as the fourth digest, it is determined that the data packet received by the destination has passed the data verification.

[0077] In a specific embodiment, after determining the third digest and the fourth digest, it is determined whether the third digest and the fourth digest are the same; if the third digest and the fourth digest are the same, that is, the digest of the data packet received by the destination from the central cloud and the digest obtained by the destination according to the second evidence identifier received from the central cloud are the same, indicating that the third digest received by the destination is recorded on the chain, and then the data packet received by the destination is most likely not tampered with. At this time, the data verification performed by the destination on the received data packet passes, that is, the data packet is credible; if the third digest and the fourth digest are different, that is, the digest of the data packet received by the destination from the central cloud and the digest obtained by the destination according to the second evidence identifier received from the central cloud are different, indicating that the fourth digest received by the destination is not recorded on the chain, and then the data packet received by the destination is most likely tampered with. At this time, the data verification performed by the destination on the received data packet fails, that is, the data packet is unreliable. Therefore, the accuracy, security and reliability of data transmission from the central cloud to the edge can be ensured as much as possible.

[0078] In the embodiment of the present application, after receiving the data packet, the digest of the data packet and the second evidence identifier corresponding to the digest sent by the central cloud, the destination end can determine the digest of the received data packet as the third digest, and call the target service to obtain the corresponding digest as the fourth digest according to the second evidence identifier. If the third digest is the same as the fourth digest, it is determined that the received data packet has passed the data verification. Therefore, the destination end verifies the data received from the central cloud by comparing whether the third digest is the same as the fourth digest.

[0079] [HZTC-HXJKJD241004][HS2411166CCN] performs data verification on the data packets received by the end, that is, by comparing the summary of the data packet received from the central cloud with the summary obtained by the destination end according to the second evidence identifier received from the central cloud to see if they are the same, the data packet received from the central cloud is verified. This data verification process can be performed automatically without the staff's perception, and no operation is required by the staff, thereby simplifying the data verification process when transmitting data from the central cloud to the destination end, thereby improving the efficiency of data transmission.

[0080] It should be noted that the above three method embodiments are respectively applied to the central cloud, the source end and the destination end, and these three method embodiments can be used in combination, that is, when transmitting a data packet from the source end to the destination end through the central cloud, the source end can execute the above data verification method applied to the source end, the central cloud can execute the above data verification method applied to the central cloud, and the destination end can execute the above data verification method applied to the destination end. Therefore, through the above three method embodiments, the trusted flow of cross-departmental cases can be realized, and the trusted mechanism of blockchain services is combined with the online collaboration mechanism of collaborative services. Not only can the business initiator and the business recipient realize the full life cycle management and full process traceability of business data, but also efficient mutual trust and collaboration between cross-departmental businesses can be realized online, effectively breaking through the judicial "data island", linking the judicial cross-department to establish a strong trust relationship, and realizing the full process recording, full link trust and full node witnessing of case data.

[0081] Optionally, a backend server can be deployed in the central cloud and a frontend server can be deployed at the edge. The backend server and the frontend server are connected to form a security boundary between the backend server and the frontend server, thereby improving the security of data packets transmitted between the central cloud and the edge.

[0082] Optionally, the smart judicial cross-departmental business collaboration platform and business collaboration node may include core functional modules such as receiving cases, transferring cases and / or collaborative configuration. The specific functions of receiving cases, transferring cases and collaborative configuration are introduced below:

[0083] Receive cases: During the collaborative process of a case, the case handling staff can use the [Receive Cases] function module to screen and view the received cases, verify the data, and process the accepted and returned cases. Exemplarily, the specific functions of the receive case module may include: case screening, case details, case association, case card information display, acceptance of existing cases, acceptance of new cases, returned cases, case acceptance status description and / or data verification, etc.

[0084] Transferring cases: During the collaborative process of a case, the case handling staff can use the [Transfer Case] ​​function module to upload the case data to the chain and transfer it to the recipient according to the configured flow node. They can also confirm the success of the case transfer or return the case if the transfer fails. For example, the specific functions of the case transfer module include: case screening, case management details, confirmation of transfer, return of case, transfer status description, checking case status and / or data uploading to the chain, etc.

[0085] Collaboration configuration: Before initiating online case collaboration, you can complete the case receiving configuration and case sending configuration in the [Collaboration Configuration] module. The key information that needs to be configured may include: configuring the document type and file type, for example, the document type can be doc, docx, pdf and / or jpg, and the file type can be jpg, jpeg, png, pdf, bmp and / or tiff; configuring the monitoring path, for example, supporting FTP monitoring, HTTP monitoring and / or FTP file monitoring; configuring the file parsing method, for example, configuring the data packet parsing rules according to the data packet naming rules, encryption method and / or verification method; configuring the source and destination, for example, configuring the name, code, case category, case type, whether to file a case and / or the received case card information of the source and destination; configuring the case card metadata, for example, implementing the specific case card data item configuration of the received data packet, such as the field name, field identifier and / or primary key involved in the collaborative case. This configuration can ensure the integrity of the case card data as much as possible; configuring the verification rules, for example, implementing the verification type of the case category, the verification cause, the verification data table, the verification keyword and / or the verification field, etc.

[0086] [HZTC-HXJKJD241004][HS2411166CCN] configuration, etc., where verification types can include cases, suspects, documents, and files, etc.

[0087] The central cloud and edge in the aforementioned three method embodiments can be deployed on the basis of the existing work network, with flexible deployment and convenient configuration; the interfaces of the smart judicial alliance chain platform, blockchain nodes, smart judicial cross-departmental business collaboration platform, and business collaboration nodes are friendly, concise, unified in style, and easy to understand, and the aforementioned three method embodiments can also be copied to other collaborative businesses to make the methods recorded in the aforementioned three method embodiments convenient, easy to use, and replicable.

[0088] Central Cloud

[0089] Corresponding to the above method embodiment, Figure 4 A schematic diagram of a central cloud of an embodiment of the present application is shown. Figure 4 As shown, the central cloud 400 includes:

[0090] A first determining unit 401 is configured to determine the digest of the received data packet as a first digest after receiving a data packet sent by a source end, a digest of the data packet, and a first evidence identifier corresponding to the digest, wherein the source end is any one of a plurality of edge ends connected to the central cloud, and the first evidence identifier is a corresponding identifier generated by the source end calling a target service running on the source end according to the digest of the data packet;

[0091] A first acquisition unit 402 is used to call the target service running on the central cloud, and obtain the corresponding digest as the second digest according to the first evidence identifier;

[0092] The first verification unit 403 is used to determine that the data packet received by the central cloud has passed the data verification when the first digest is the same as the second digest.

[0093] It should be noted that the central cloud of this embodiment is used to implement the corresponding data verification method in the aforementioned method embodiment applied to the central cloud, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0094] Source

[0095] Corresponding to the above method embodiment, the source end is any one of the multiple edge ends connected to the central cloud. Figure 5 A schematic diagram of a source end of an embodiment of the present application is shown, such as Figure 5 As shown, the source end 500 includes:

[0096] A summary acquisition unit 501 is used to acquire a summary of a data packet whose destination is any of the multiple edge ends;

[0097] An identification generating unit 502 is used to call a target service running on the source end and generate a corresponding first evidence identification according to the summary of the data packet;

[0098] The data sending unit 503 is used to send the data packet, the summary of the data packet and the first evidence identification to the central cloud, so that the central cloud performs data verification on the received data packet according to the first evidence identification.

[0099] It should be noted that the source end of this embodiment is used to implement the corresponding data verification method in the aforementioned method embodiment applied to the source end, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0100] Destination

[0101] Corresponding to the above method embodiment, the destination end is any one of the multiple edge ends connected to the central cloud. Figure 6 A schematic diagram of a destination end of an embodiment of the present application is shown, such as Figure 6 As shown, the destination end 600 includes:

[0102] The second determining unit 601 is used to determine the digest of the received data packet as a third digest after receiving the data packet sent by the central cloud, the digest of the data packet and the second evidence identifier corresponding to the digest, wherein the second evidence identifier is a corresponding identifier generated by the central cloud calling the target service running on the central cloud according to the digest of the data packet;

[0103] The second acquisition unit 602 is used to call the target service running on the destination end, and obtain the target service according to the second evidence identification.

[0104] [HZTC-HXJKJD241004][HS2411166CCN] takes the corresponding abstract as the fourth abstract;

[0105] The second verification unit 603 is configured to determine that the data packet received by the destination has passed data verification when the third digest is the same as the fourth digest.

[0106] It should be noted that the destination end of this embodiment is used to implement the corresponding data verification method in the aforementioned method embodiment applied to the destination end, and has the beneficial effects of the corresponding method embodiment, which will not be repeated here.

[0107] Electronic devices

[0108] Figure 7 This is a schematic block diagram of an electronic device provided in an embodiment of the present application. The specific embodiment of the present application does not limit the specific implementation of the electronic device. Figure 7 As shown, the electronic device may include: a processor (processor) 702, a communication interface (Communications Interface) 704, a memory (memory) 706, and a communication bus 708. Among them:

[0109] The processor 702 , the communication interface 704 , and the memory 706 communicate with each other via a communication bus 708 .

[0110] The communication interface 704 is used to communicate with other electronic devices or servers.

[0111] The processor 702 is used to execute the program 710, and specifically can execute the relevant steps in any of the aforementioned data verification method embodiments.

[0112] Specifically, the program 710 may include program codes, which include computer operation instructions.

[0113] The processor 702 may be a CPU, or an application specific integrated circuit ASIC (Application Specific Integrated Circuit), or one or more integrated circuits configured to implement the embodiments of the present application. The one or more processors included in the smart device may be processors of the same type, such as one or more CPUs; or processors of different types, such as one or more CPUs and one or more ASICs.

[0114] RISC-V is an open source instruction set architecture based on the Reduced Instruction Set (RISC) principle. It can be applied to various aspects such as single-chip microcomputers and FPGA chips. Specifically, it can be applied to the fields of IoT security, industrial control, mobile phones, personal computers, etc., and because it is designed with small, fast, and low-power realities in mind, it is particularly suitable for modern computing devices such as warehouse-scale cloud computers, high-end mobile phones, and tiny embedded systems. With the rise of artificial intelligence Internet of Things (AIoT), the RISC-V instruction set architecture has also received more and more attention and support, and is expected to become the next generation of widely used CPU architecture.

[0115] The computer operation instructions in the embodiments of the present application may be computer operation instructions based on the RISC-V instruction set architecture, and correspondingly, the processor 702 may be designed based on the RISC-V instruction set. Specifically, the processor chip in the electronic device provided in the embodiments of the present application may be a chip designed using the RISC-V instruction set, and the chip may execute executable code based on the configured instructions, thereby implementing any of the data verification methods in the above embodiments.

[0116] The memory 706 is used to store the program 710. The memory 706 may include a high-speed RAM memory, and may also include a non-volatile memory (non-volatile memory), such as at least one disk memory.

[0117] The program 710 may be specifically used to enable the processor 702 to execute the data verification method in any of the aforementioned embodiments.

[0118] The specific implementation of each step in program 710 can refer to the corresponding description of the corresponding steps and units in any of the aforementioned data verification method embodiments, which will not be repeated here. Those skilled in the art can clearly understand that for the convenience and simplicity of description, the specific working process of the above-described devices and modules can refer to the corresponding process description in the aforementioned method embodiments, which will not be repeated here.

[0119] It should be noted that the electronic device of this embodiment is used to implement the corresponding data verification method in any of the aforementioned method embodiments, and has the beneficial effects of the corresponding method embodiments, which will not be described in detail here.

[0120] [HZTC-HXJKJD241004][HS2411166CCN]

[0121] Computer storage media

[0122] The present application also provides a computer-readable storage medium storing instructions for causing a machine to execute any of the data verification methods described herein. Specifically, a system or device equipped with a storage medium may be provided, on which a software program code implementing the functions of any of the above embodiments is stored, and a computer (or CPU or MPU) of the system or device is enabled to read and execute the program code stored in the storage medium.

[0123] In this case, the program code read from the storage medium itself can implement the function of any one of the above embodiments, so the program code and the storage medium storing the program code constitute part of the present application.

[0124] The storage medium embodiments for providing the program code include a floppy disk, a hard disk, a magneto-optical disk, an optical disk (such as CD-ROM, CD-R, CD-RW, DVD-ROM, DVD-RAM, DVD-RW, DVD+RW), a magnetic tape, a non-volatile memory card, and a ROM. Alternatively, the program code can be downloaded from a server computer by a communication network.

[0125] Computer program product

[0126] An embodiment of the present application also provides a computer program product, including computer instructions, which instruct a computing device to perform any corresponding operation in the above-mentioned multiple method embodiments.

[0127] It should be noted that the user-related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to sample data used to train the model, data used for analysis, stored data, displayed data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0128] It should be pointed out that, according to the needs of implementation, the various components / steps described in the embodiments of the present application can be split into more components / steps, or two or more components / steps or partial operations of components / steps can be combined into new components / steps to achieve the purpose of the embodiments of the present application.

[0129] The above-mentioned method according to the embodiment of the present application can be implemented in hardware, firmware, or implemented as software or computer code that can be stored in a recording medium (such as a CD ROM, RAM, floppy disk, hard disk or magneto-optical disk), or implemented as a computer code originally stored in a remote recording medium or a non-temporary machine-readable medium downloaded through a network and to be stored in a local recording medium, so that the method described herein can be stored in such software processing on a recording medium using a general-purpose computer, a special-purpose processor or programmable or special-purpose hardware (such as an ASIC or FPGA). It can be understood that a computer, a processor, a microprocessor controller or programmable hardware includes a storage component (e.g., RAM, ROM, flash memory, etc.) that can store or receive software or computer code, and when the software or computer code is accessed and executed by a computer, a processor or hardware, the method described herein is implemented. In addition, when a general-purpose computer accesses the code for implementing the method shown here, the execution of the code converts the general-purpose computer into a special-purpose computer for executing the method shown here.

[0130] It should be noted that the user-related information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to sample data used to train the model, data used for analysis, stored data, displayed data, etc.) involved in the embodiments of the present application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data need to comply with relevant laws, regulations and standards of relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0131] Those skilled in the art will appreciate that the units and methods described in the embodiments disclosed herein may be used to

[0132] [HZTC-HXJKJD241004][HS2411166CCN] The steps of the method can be implemented by electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for specific applications, but such implementation should not be considered to be beyond the scope of the embodiments of the present application.

[0133] The above implementation methods are only used to illustrate the embodiments of the present application, and are not limitations on the embodiments of the present application. Ordinary technicians in the relevant technical field can make various changes and modifications without departing from the spirit and scope of the embodiments of the present application. Therefore, all equivalent technical solutions also belong to the scope of the embodiments of the present application. The scope of patent protection of the embodiments of the present application should be limited by the claims.

Claims

1. A data verification method, characterized in that: Applied to the central cloud, the data verification method includes: After receiving a data packet sent by a source end, a digest of the data packet and a first evidence identifier corresponding to the digest, determining the digest of the received data packet as the first digest, wherein the source end is any one of the multiple edge ends connected to the central cloud, and the first evidence identifier is a corresponding identifier generated by the source end calling a target service running on the source end according to the digest of the data packet; Calling the target service running on the central cloud, and obtaining the corresponding digest as the second digest according to the first evidence identifier; If the first digest is the same as the second digest, it is determined that the data packet received by the central cloud has passed the data verification.

2. The method according to claim 1, characterized in that The method further comprises: After determining that the data packet received by the central cloud has passed data verification, obtaining a summary of the data packet; Calling the target service running on the central cloud, and generating a corresponding second evidence identification according to the summary of the data packet; The data packet, a summary of the data packet and the second evidence identifier are sent to a destination end of the data packet among the multiple edges, so that the destination end performs data verification on the received data packet according to the second evidence identifier.

3. The method according to claim 1 or 2, characterized in that: The central cloud is the Political and Legal Affairs Commission end, and three of the multiple ends are the Procuratorate end, the Court end, and the Justice Bureau end.

4. A data verification method, characterized in that: Applied to a source end, the source end is any one of a plurality of edge ends connected to a central cloud, the data verification method includes: Obtain a summary of a data packet whose destination end is any of the multiple edge ends; Calling the target service running on the source end, and generating a corresponding first evidence identifier according to the summary of the data packet; The data packet, the summary of the data packet and the first evidence identification are sent to the central cloud, so that the central cloud performs data verification on the received data packet according to the first evidence identification.

5. A data verification method, characterized in that: Applied to a destination end, the destination end is any of a plurality of edge ends connected to a central cloud, the data verification method includes: After receiving the data packet sent by the central cloud, the digest of the data packet and the second evidence identifier corresponding to the digest, determining the digest of the received data packet as a third digest, wherein the second evidence identifier is a corresponding identifier generated by the central cloud calling the target service running on the central cloud according to the digest of the data packet; Invoke the target service running on the destination end, and obtain the corresponding digest as the fourth digest according to the second evidence identifier; If the third digest is the same as the fourth digest, it is determined that the data packet received by the destination has passed the data verification.

6. A central cloud, characterized in that: include: A first determination unit is configured to determine the digest of the received data packet as a first digest after receiving a data packet sent by a source end, a digest of the data packet, and a first evidence identifier corresponding to the digest, wherein the source end is any one of a plurality of edge ends connected to the central cloud, and the first evidence identifier is a corresponding identifier generated by the source end calling a target service running on the source end according to the digest of the data packet; A first acquisition unit is used to call the target service running on the central cloud, and acquire the corresponding digest as the second digest according to the first evidence identifier; A first verification unit is configured to determine that the data packet received by the central cloud has passed data verification when the first digest is the same as the second digest.

7. A source end, characterized in that: The source end is any one of the multiple edge ends connected to the central cloud, and the source end includes: A summary acquisition unit, used to acquire a summary of a data packet whose destination end is any of the multiple edge ends; An identification generating unit, configured to call a target service running on the source end and generate a corresponding first evidence identification according to a summary of the data packet; A data sending unit is used to send the data packet, the summary of the data packet and the first evidence identification to the central cloud, so that the central cloud performs data verification on the received data packet according to the first evidence identification.

8. A destination end, characterized in that: The destination end is any one of the multiple edge ends connected to the central cloud, and the destination end includes: A second determining unit is configured to determine the digest of the received data packet as a third digest after receiving the data packet sent by the central cloud, the digest of the data packet and the second evidence identifier corresponding to the digest, wherein the second evidence identifier is a corresponding identifier generated by the central cloud calling the target service running on the central cloud according to the digest of the data packet; A second acquisition unit, configured to call a target service running on the destination end, and acquire a corresponding digest as a fourth digest according to the second evidence identifier; The second verification unit is used to determine that the data packet received by the destination end has passed the data verification when the third digest is the same as the fourth digest.

9. An electronic device, characterized in that: include: A processor, a memory, a communication interface and a communication bus, wherein the processor, the memory and the communication interface communicate with each other via the communication bus; The memory is used to store at least one executable instruction, which enables the processor to perform an operation corresponding to the data verification method as described in any one of claims 1-3, or an operation corresponding to the data verification method as described in claim 4, or an operation corresponding to the data verification method as described in claim 5.

10. A computer storage medium, characterized in that: A computer program is stored thereon, which, when executed by a processor, implements the data verification method as claimed in any one of claims 1 to 3, or the data verification method as claimed in claim 4, or the data verification method as claimed in claim 5.

Images