CN115086065B - Block chain-based data synchronization method and device, electronic equipment and medium - Google Patents
Block chain-based data synchronization method and device, electronic equipment and medium Download PDFInfo
- Publication number
- CN115086065B CN115086065B CN202210817131.3A CN202210817131A CN115086065B CN 115086065 B CN115086065 B CN 115086065B CN 202210817131 A CN202210817131 A CN 202210817131A CN 115086065 B CN115086065 B CN 115086065B
- Authority
- CN
- China
- Prior art keywords
- service
- data
- update data
- server
- owner information
- Prior art date
- Legal status (The legal status 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 status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 57
- 230000001360 synchronised effect Effects 0.000 claims abstract description 15
- 238000012795 verification Methods 0.000 claims description 24
- 230000004048 modification Effects 0.000 claims description 14
- 238000012986 modification Methods 0.000 claims description 14
- 238000004891 communication Methods 0.000 claims description 4
- 238000004590 computer program Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 6
- 230000007246 mechanism Effects 0.000 description 4
- 230000006855 networking Effects 0.000 description 4
- 230000008878 coupling Effects 0.000 description 3
- 238000010168 coupling process Methods 0.000 description 3
- 238000005859 coupling reaction Methods 0.000 description 3
- 230000008569 process Effects 0.000 description 3
- 230000006870 function Effects 0.000 description 2
- 238000012545 processing Methods 0.000 description 2
- 238000006467 substitution reaction Methods 0.000 description 2
- 230000001960 triggered effect Effects 0.000 description 2
- 230000003287 optical effect Effects 0.000 description 1
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/01—Protocols
- H04L67/10—Protocols in which an application is distributed across nodes in the network
- H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/10—Network architectures or network communication protocols for network security for controlling access to devices or network resources
- H04L63/105—Multiple levels of security
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L63/00—Network architectures or network communication protocols for network security
- H04L63/12—Applying verification of the received information
Landscapes
- Engineering & Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Computer Hardware Design (AREA)
- Computing Systems (AREA)
- General Engineering & Computer Science (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
- Traffic Control Systems (AREA)
Abstract
The application provides a data synchronization method, a device, electronic equipment and a medium based on a block chain, which are applied to a target server in the block chain, wherein the block chain also comprises service servers in different vehicle service links; the data synchronization method comprises the following steps: the target server receives service update data for the owner information sent by a first service server in the block chain; the target server checks the service update data and judges whether the service update data aiming at the same vehicle owner information accords with a preset synchronous condition when the check is passed; if yes, a second service server which does not store service update data of the same vehicle owner information is selected from the block chain, and the service update data is synchronized to the second service server, so that the second service server updates the current service data of the same vehicle owner information, and data exchange among different service servers is realized, and the data is updated timely.
Description
Technical Field
The application relates to the field of automobile information storage, in particular to a data synchronization method, device, electronic equipment and medium based on a block chain.
Background
At present, a vehicle owner identity recording and management system based on the vehicle networking exists in the market, a user uploads identity card and driving license information on a vehicle-mounted terminal or a mobile phone terminal, and a vehicle networking service platform records the binding relationship between the user and a vehicle, namely the user is the identity of the vehicle owner.
However, in different service links of the vehicle, there are often different management systems, so that a user needs to upload the owner information in each service link, and when the owner information is changed, the service information needs to be modified for each service link, which results in the problem that the service systems of the different service links have difficult data exchange and in untimely data update.
Disclosure of Invention
In view of this, an object of the present application is to provide a data synchronization method, apparatus, electronic device and medium based on a blockchain, which can enable a service system between different service links to perform data exchange in time, so that data of each service link can be updated in time.
The data synchronization method based on the block chain is applied to a target server in the block chain, and the block chain also comprises service servers in different vehicle service links; each service server corresponds to a front-end device, and the front-end device can collect service information in a vehicle service link; the data synchronization method comprises the following steps:
The target server receives service update data for the owner information sent by a first service server in the block chain; the service update data is: registration data of new car owner information or modification data for existing car owner information;
the target server checks the service update data sent by the first service server, and judges whether the service update data aiming at the same vehicle owner information accords with a preset synchronization condition when the service update data passes the check;
if yes, the target server selects a second service server which does not store the service update data of the same vehicle owner information from the blockchain, and synchronizes the service update data of the same vehicle owner information to the second service server so that the second service server updates the current service data of the same vehicle owner information based on the service update data.
In some embodiments, in the blockchain-based data synchronization method, the target server checks the service update data sent by the first service server, and determines that the service update data check passes, including:
The target server judges whether the verification parameters of the service update data in preset multi-dimension meet preset standard conditions of the verification parameters in each dimension;
if yes, determining that the service update data passes the verification; wherein, the verification parameters under the multi-dimension meet the preset standard conditions of the verification parameters under each dimension, and the preset standard conditions comprise at least one of the following:
the target server judges whether the service update data accords with a preset attribute rule;
the target server judges whether the service updating data contains a preset service server identifier or not;
the target server judges whether the service update data contains a target field conforming to a preset field rule;
and the target server judges whether the service update data contains a verification result aiming at preset information.
In some embodiments, in the blockchain-based data synchronization method, the target server determines whether service update data for the same owner information meets a preset synchronization condition, including:
determining a first service server for transmitting service update data of the same owner information and the weight of each first service server in a block chain aiming at each service update data of the same owner information;
Judging whether the service update data aiming at the same vehicle owner information accords with a preset synchronous condition according to the sum of weights of a first service server for transmitting the service update data of the vehicle owner information;
and judging whether the target data of the business update data aiming at the same car owner information are the same or not.
In some embodiments, in the blockchain-based data synchronization method, after acquiring service update data for owner information, the first service server updates current service data for the owner information into the service update data, and after updating, sends the service update data for the owner information to the target server;
or,
after the first service server acquires the service update data aiming at the vehicle owner information, the first service server directly transmits the service update data aiming at the vehicle owner information to the target server; the data synchronization method further comprises the following steps:
and when judging that the service update data aiming at the same vehicle owner information accords with a preset synchronous condition, the target server sends an update notification message to the first service server so as to notify the first service server that the current service data aiming at the vehicle owner information is updated into the service update data.
In some embodiments, in the blockchain-based data synchronization method, the updating, by the first service server and/or the second service server, the current service data of the same owner information based on the service update data includes:
when the service update data is the registration data of the new car main information, the first service server and/or the second service server store the service update data;
when the service update data is modification data of existing vehicle owner information, the first service server and/or the second service server modifies the existing vehicle owner information based on the service update data.
In some embodiments, in the blockchain-based data synchronization method, the first service server sends service update data to the target server, including the following steps:
the first service server receives service update data sent by front-end equipment and encrypted according to preset encryption rules preset in the front-end equipment;
and the first service server obtains decrypted service update data according to a preset decryption rule and sends the decrypted service update data to the target server.
In some embodiments, in the blockchain-based data synchronization method, different service servers correspond to different authority levels;
the data synchronization method further comprises the following steps:
when a target service server in the block chain receives a query request of front-end equipment for target owner information, calling the target owner information in the service server with authority level lower than that of the target service server, and sending the target owner information to the front-end equipment.
In some embodiments, a data synchronization device based on a blockchain is further provided, and is applied to a target server in the blockchain, wherein the blockchain further comprises service servers in different vehicle service links; each service server corresponds to a front-end device, and the front-end device can collect service information in a vehicle service link; the data synchronization device includes:
the first receiving module is used for receiving service update data for the owner information sent by a first service server in the block chain; the service update data is: registration data of new car owner information or modification data for existing car owner information;
the second receiving module is used for checking the service update data sent by the first service server and judging whether the service update data aiming at the same vehicle owner information accords with a preset synchronization condition when the service update data passes the check;
And the synchronization module is used for selecting a second service server which does not store the service update data of the same vehicle owner information from the block chain when judging whether the service update data of the same vehicle owner information accords with a preset synchronization condition, and synchronizing the service update data of the same vehicle owner information into the second service server so that the second service server updates the current service data of the same vehicle owner information based on the service update data.
In some embodiments, there is also provided an electronic device comprising: the system comprises a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, the processor and the memory are communicated through the bus when the electronic device runs, and the machine-readable instructions are executed by the processor to execute the steps of the block chain based data synchronization method.
In some embodiments, a computer readable storage medium having a computer program stored thereon, which when executed by a processor performs the steps of the blockchain-based data synchronization method is also provided.
The application provides a data synchronization method, a device, electronic equipment and a medium based on a blockchain, wherein service servers in different vehicle service links are manufactured into the blockchain, so that the owner identity data is synchronized to the service server of each service link based on a mechanism of the blockchain, thereby realizing data exchange of different service links, and timely modification and timely update of owner information; when data synchronization is realized, the same service update data sent by at least two front-end devices must be received to determine that the service update data is credible, so that errors in the data synchronization process are prevented, and the credible owner information stored in a service server of each service link is ensured; finally, after the data synchronization is completed, the data can be prevented from being tampered based on a mechanism of a block chain, and the safety and the reliability of the data are ensured.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings that are needed in the embodiments will be briefly described below, it being understood that the following drawings only illustrate some embodiments of the present application and therefore should not be considered limiting the scope, and that other related drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 illustrates a method flow diagram of a blockchain-based data synchronization method in accordance with embodiments of the present application;
fig. 2 is a flowchart of a method for determining whether service update data for the same owner information meets a preset synchronization condition by using a target server according to an embodiment of the present application;
FIG. 3 is a flowchart of a method for the first service server and/or the second service server to update current service data of the same owner information based on the service update data according to an embodiment of the present application;
FIG. 4 is a flowchart of a method for a first service server to send service update data to a target server according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a block chain based data synchronization device according to an embodiment of the present application;
fig. 6 shows a schematic structural diagram of an electronic device according to an embodiment of the present application.
Detailed Description
For the purpose of making the objects, technical solutions and advantages of the embodiments of the present application more clear, the technical solutions of the embodiments of the present application will be clearly and completely described below with reference to the accompanying drawings in the embodiments of the present application, and it should be understood that the accompanying drawings in the present application are only for the purpose of illustration and description, and are not intended to limit the protection scope of the present application. In addition, it should be understood that the schematic drawings are not drawn to scale. A flowchart, as used in this application, illustrates operations implemented according to some embodiments of the present application. It should be understood that the operations of the flow diagrams may be implemented out of order and that steps without logical context may be performed in reverse order or concurrently. Moreover, one or more other operations may be added to the flow diagrams and one or more operations may be removed from the flow diagrams as directed by those skilled in the art.
In addition, the described embodiments are only some, but not all, of the embodiments of the present application. The components of the embodiments of the present application, which are generally described and illustrated in the figures herein, may be arranged and designed in a wide variety of different configurations. Thus, the following detailed description of the embodiments of the present application, as provided in the accompanying drawings, is not intended to limit the scope of the application, as claimed, but is merely representative of selected embodiments of the application. All other embodiments, which can be made by those skilled in the art based on the embodiments of the present application without making any inventive effort, are intended to be within the scope of the present application.
It should be noted that the term "comprising" will be used in the embodiments of the present application to indicate the presence of the features stated hereinafter, but not to exclude the addition of other features.
At present, a vehicle owner identity recording and management system based on the vehicle networking exists in the market, a user uploads identity card and driving license information on a vehicle-mounted terminal or a mobile phone terminal, and a vehicle networking service platform records the binding relationship between the user and a vehicle, namely the user is the identity of the vehicle owner.
However, in different service links of the vehicle, there are often different management systems, so that a user needs to upload the owner information in each service link, and when the owner information is changed, the service information needs to be modified for each service link, which results in the problem that the service systems of the different service links have difficult data exchange and in untimely data update.
At present, users in the vehicle business links requiring the use of the vehicle owner identity management system mainly comprise vehicle owners, vehicle enterprises, insurance companies, traffic management departments, 4S shops and the like. The vehicle service links are respectively formed by front-end equipment and a server; for example, when a user goes to a traffic management department to register the identity information of the vehicle owner, the operator inputs the identity information of the vehicle owner on a working computer and stores the identity information of the vehicle owner on a server of the traffic management department; when a user goes to an insurance company to purchase insurance, inputting owner identity information on a flat plate provided by a worker, and storing the owner identity information on a service server of the insurance company; etc.;
therefore, the user needs to input the owner identity information in each vehicle service link. The owner identity information input in different links is stored in different service servers, the data exchange between the service servers is difficult, and the user is required to perform repeated operation for many times; and when the user changes the owner information, such as modifying the contact way or trading the second-hand vehicle, the user also needs to modify each business link respectively, which results in untimely data update.
Based on the above, the embodiment of the application provides a data synchronization method based on a blockchain, which is to make service servers in different vehicle service links into the blockchain, so that the owner identity data is synchronized to the service server of each service link based on a mechanism of the blockchain, thereby realizing data exchange of different service links, and timely modification and timely update of the owner data; when data synchronization is realized, the same service update data sent by at least two front-end devices must be received to determine that the service update data is credible, so that errors in the data synchronization process are prevented, and the credible owner information stored in a service server of each service link is ensured; finally, after the data synchronization is completed, the data can be prevented from being tampered based on a mechanism of a block chain, and the safety and the reliability of the data are ensured.
Referring to fig. 1, fig. 1 provides a data synchronization method based on a blockchain, which is applied to a target server in the blockchain, wherein the blockchain also comprises service servers in different vehicle service links; each service server corresponds to a front-end device, and the front-end device can collect service information in a vehicle service link; the data synchronization method comprises the following steps S101-S103:
S101, the target server receives service update data for owner information sent by a first service server in the blockchain; the service update data is: registration data of new car owner information or modification data for existing car owner information;
s102, the target server checks the service update data sent by the first service server, and judges whether the service update data aiming at the same vehicle owner information accords with a preset synchronization condition when the service update data passes the check;
and S103, if so, the target server selects a second service server which does not store the service update data of the same vehicle owner information from the block chain, and synchronizes the service update data of the same vehicle owner information into the second service server so that the second service server updates the current service data of the same vehicle owner information based on the service update data.
Here, the service update data actually corresponds to two scenarios: scene one: the user uploads the owner identity information for the first time, and at the moment, the service update data is the registration data of the new owner information; the registration data of the new car main information comprises: the name of the purchasing person, the number of the mobile phone, the number of the identification card, the face image, the voiceprint, the number of the vehicle type, the number of the vehicle-mounted terminal, the number of the vehicle frame, the number of the engine and the like; scene II: the user modifies existing owner information, for example, the owner contact, or the owner name, cell phone number, identification number, face image, voiceprint, etc. after the second hand vehicle transaction. At this time, the service update data is modification data for the existing owner information.
In the step S102, the target server checks the service update data sent by the first service server, and determines that the service update data passes the check, including:
the target server judges whether the verification parameters of the service update data in preset multi-dimension meet preset standard conditions of the verification parameters in each dimension;
if yes, determining that the service update data passes the verification; wherein, the verification parameters under the multi-dimension meet the preset standard conditions of the verification parameters under each dimension, and the preset standard conditions comprise at least one of the following:
the target server judges whether the service update data accords with a preset attribute rule;
the target server judges whether the service updating data contains a preset service server identifier or not;
the target server judges whether the service update data contains a target field conforming to a preset field rule;
and the target server judges whether the service update data contains a verification result aiming at preset information.
Specifically, the service update data accords with a preset attribute rule, that is, after the target server receives the service update data sent by the first service server, whether the attribute of the service update data accords with the preset attribute rule needs to be checked, and exemplary checking is performed to determine whether the data field is not null, whether each type of data attribute in the service update data is a preset attribute, for example, whether the size of a face image accords with the requirement or not.
And the target server judges whether the service update data contains a preset service server identifier or not, namely the target server judges whether the received service update data is sent by the service server in the block chain or not. If so, step S103 is triggered. Otherwise, the service update data received by the target server is not transmitted by the service servers in the blockchain, and only the received service update data is stored, and the step S103 is not triggered.
The target server judges whether the service updating data contains target fields conforming to preset field rules or not, namely after the target server receives the service updating data, the target server respectively judges whether the target fields in each data conform to the preset field rules of the data or not. For example, when the target server receives target vehicle owner data uploaded by a user for the first time, the name, the mobile phone number, the identification card number, the face image, the voiceprint, the vehicle type number, the vehicle-mounted terminal number, the vehicle frame number and the engine number of the vehicle purchase person are respectively one type of data; the target server respectively judges whether each type of data accords with a preset field rule of the data, for example, the mobile phone number should have 11 characters, and each character is a number; the identification card number, the vehicle-mounted terminal number, the vehicle frame number, the engine number and the like all comprise a preset number of characters and accord with a certain format and the like.
The target server judges whether the service updating data contains a verification result aiming at preset information; when the service server collects the information of the target car owner, some information needs to be checked, for example, aiming at the mobile phone number filled by the user, the service server sends a check code to the mobile phone number to ensure that the mobile phone number filled by the user is correct and is the own mobile phone number; here, when the target server receives the service update data sent by the service server, it needs to determine whether the service update data includes a verification result for the mobile phone number, so as to ensure that the mobile phone number is correct.
In this embodiment of the present application, after receiving service update data sent by a service server, the target server performs at least one check on the received service update data, so as to ensure that the data received by the target server is correct, prevent error and error in a subsequent synchronization process, and ensure that service servers of multiple service links perform accurate data exchange.
In the step S102, service update data of a plurality of first service servers of the same owner information is received within a preset period of time.
And after receiving the service information collected and sent by the front-end equipment, the first service server sends the service information to the target server. After receiving service update data aiming at the same vehicle owner information, the target server cannot ensure that the service update data is correct; therefore, the target server needs to check the correctness of the service update data according to the service update data for the same owner information sent by other first service servers. Here, preferably, the target server requests to receive service update data of a plurality of first service servers for the same owner information within a preset time period, and verifies the service update data in time to realize data update in time.
For example, after a user registers and records in a traffic management department, a service server of the traffic management department sends registration data of new car main information of the user to a target server, and simultaneously reminds the user to finish verification on a personal mobile phone app within 3 days; and uploading the registration data of the second new car main information by the user through the personal mobile phone app within 3 days, so that the target server receives the registration data of the second new car main information within a preset time period (within 3 days).
The target server judges whether the service update data aiming at the same vehicle owner information accords with a preset synchronous condition or not, and whether the target data aiming at the service update data of the same vehicle owner information is the same or not is required to be judged. Since the service update data is transmitted by a different service server, the service update data may further include data such as a service server identifier or data specific to the service link, in addition to the target data. Therefore, only the target data in the service updating data is required to be judged to be consistent, wherein the target data is the target vehicle owner data or the modified data which are common to all service servers and comprise the name of a vehicle purchaser, the number of a mobile phone, the number of an identity card, a face image, a voiceprint, the number of a vehicle type, the number of a vehicle-mounted terminal, the number of a vehicle frame, the number of an engine and the like.
Referring to fig. 2, in the embodiment of the present application, the target server determines whether service update data for the same owner information meets a preset synchronization condition, including the following steps S201 to S203:
s201, determining a first service server for transmitting service update data of the same owner information and the weight of each first service server in a block chain according to each service update data of the same owner information;
S202, judging whether the service update data aiming at the same owner information accords with a preset synchronization condition according to the sum of weights of a first service server for transmitting the service update data of the owner information;
s203, judging whether the target data of the business update data aiming at the same car owner information are the same.
Specifically, the target server may execute the synchronization conditions of steps S201 and S202 first, and then execute step S203; or the step S203 is performed first, and then the steps S201 and S202 are performed.
Specifically, in step S203, the target server compares the name, the mobile phone number, the identification card number, the face image, the voiceprint, the vehicle model number, the vehicle-mounted terminal number, the vehicle frame number and the engine number of the vehicle purchasing person in the service update data, and if the name, the mobile phone number, the identification card number, the face image, the voiceprint, the vehicle model number, the vehicle-mounted terminal number, the vehicle frame number and the engine number are the same, the service update data of the same vehicle owner information is consistent.
In the steps S201 and S202, the weights of different service servers in the blockchain are different, and the reliability of the data in the different service servers is different; therefore, the target server calculates the sum of the weights of the service servers transmitting the service update data, and the preset synchronization condition is met only when the sum of the weights is larger than a preset weight threshold value, thereby ensuring that the data synchronized into each service server is reliable.
The traffic management service server is obviously more reliable than the data of other service servers and is also necessary service update data, in other words, the service update data for the same owner information must include the service update data sent by the traffic management service server.
In the step S103, the target server selects a second service server that does not store the service update data of the same owner information from the blockchain, and synchronizes the service update data of the same owner information to the second service server, so that the second service server updates the current service data of the same owner information based on the update service.
In the block chain-based data synchronization method, after acquiring service update data for the owner information, the first service server updates current service update data for the owner information into the service update data, and after updating, the first service server sends the service update data for the owner information to the target server;
or,
after the first service server acquires the service update data aiming at the vehicle owner information, the first service server directly transmits the service update data aiming at the vehicle owner information to the target server; the data synchronization method further comprises the following steps:
When judging that the service update data aiming at the same vehicle owner information accords with a preset synchronous condition, the target server updates the current service data aiming at the vehicle owner information into the service update data after acquiring the service update data aiming at the vehicle owner information from the first service server, and sends the service update data aiming at the vehicle owner information to the target server after the update is finished;
here, according to the timing of updating the vehicle owner information based on the update service data by the first service server, two cases are classified. First case: the first service server receives the update service data and immediately updates the owner information in the service server, and then in step S103, only the data in the second service server may be updated.
Second case: only if the target service server judges whether the service update data aiming at the same vehicle owner information accords with the preset synchronous condition, the vehicle owner information in the first service server and the second service server is allowed to be updated, and the information is ensured not to be easily modified.
The first case mainly aims at registration data of new car main information; the second case is mainly directed to modification data of existing owner information.
Referring to fig. 3, fig. 3 provides a flowchart of a method for updating current service data of the same owner information by the first service server and/or the second service server according to the embodiment of the present application based on the service update data; specifically, the following S301 and S302 are included:
s301, when the service update data is the registration data of new car main information, the first service server and/or the second service server store the service update data;
s302, when the service updating data is the modification data of the existing owner information, the first service server and/or the second service server modifies the existing owner information based on the service updating data.
Referring to fig. 4, fig. 4 provides a flowchart of a method for a first service server to send service update data to a target server according to an embodiment of the present application; as shown in fig. 4, the first service server sends service update data to a target server, including the following steps S401 to S402:
s401, the first service server receives service update data sent by front-end equipment and encrypted according to preset encryption rules preset in the front-end equipment;
S402, the first service server obtains decrypted service update data according to a preset decryption rule, and sends the decrypted service update data to a target server.
In the existing vehicle owner identity management system, encryption processing on sensitive data is lacked, and the safety of the data is difficult to guarantee; therefore, in the embodiment of the application, when the front-end equipment collects the service update data, the service update data is encrypted, so that the sensitive data in the identity information of the vehicle owner is desensitized, and the data security is ensured. After the service server receives the encrypted service update data, decrypting the service update data to obtain decrypted service update data.
Here, preset encryption rules of different front-end devices may be the same or different; the preset decryption rules in the service server correspond to the preset encryption rules in the corresponding front-end equipment.
In this embodiment of the present application, the plurality of different servers correspond to different permission levels;
the data synchronization method based on the block chain further comprises the following steps:
when a target service server in the block chain receives a query request of front-end equipment for target owner information, calling the target owner information in the service server with authority level lower than that of the target service server, and sending the target owner information to the front-end equipment.
When some service servers have larger access quantity and the stored owner information is crashed, the user can be ensured to inquire the data in time by calling the owner information method in other service servers. Here, since the authority level of the traffic management department's service server is high, in general, the traffic management department's service server is allowed to call the owner information in the service server of the insurance company, the vehicle enterprise, etc., but the traffic management department's service server is not allowed to call the owner information in the service server of the insurance company, the vehicle enterprise, etc.
In the data synchronization method based on the blockchain, when the target server determines that the target data of the service update data for the same owner information is inconsistent, the target server sends a prompt message to each first service server, so that the first service server sends the prompt message to the corresponding front-end device.
That is, when the target server determines that the target data in the service update data for the same owner information is inconsistent, the data may be tampered, or the user uploads the data in error, so that prompt information is timely sent to the corresponding front-end device, so that the user can timely view the data and modify the data.
Referring to fig. 5, an embodiment of the present application further provides a data synchronization device based on a blockchain, which is applied to a target server in the blockchain, wherein the blockchain further includes service servers in different vehicle service links; each service server corresponds to a front-end device, and the front-end device can collect service information in a vehicle service link; the data synchronization device includes:
a first receiving module 501, configured to receive service update data for owner information sent by a first service server in the blockchain; the service update data is: registration data of new car owner information or modification data for existing car owner information;
the second receiving module 502 is configured to verify the service update data sent by the first service server, and determine whether service update data for the same owner information meets a preset synchronization condition when the service update data is verified;
and the synchronization module 503 is configured to select a second service server that does not store the service update data of the same owner information from the blockchain when determining whether the service update data of the same owner information meets a preset synchronization condition, and synchronize the service update data of the same owner information to the second service server, so that the second service server updates the current service data of the same owner information based on the service update data.
In some embodiments, the second receiving module in the data synchronization device is configured to check the service update data sent by the first service server, and determine that the service update data passes the check, and specifically is configured to:
judging whether the check parameters of the business update data in preset multiple dimensions meet preset standard conditions of the check parameters in each dimension or not;
if yes, determining that the service update data passes the verification; wherein, the verification parameters under the multi-dimension meet the preset standard conditions of the verification parameters under each dimension, and the preset standard conditions comprise at least one of the following:
judging whether the service update data accords with a preset attribute rule or not;
judging whether the service updating data contains a preset service server identifier or not;
judging whether the service update data contains a target field conforming to a preset field rule;
judging whether the service update data contains a check result aiming at preset information.
In some embodiments, the second receiving module in the data synchronization device is configured to, when determining whether the service update data for the same owner information meets a preset synchronization condition, specifically:
determining a first service server for transmitting service update data of the same owner information and the weight of each first service server in a block chain aiming at each service update data of the same owner information;
Judging whether the service update data aiming at the same vehicle owner information accords with a preset synchronous condition according to the sum of weights of a first service server for transmitting the service update data of the vehicle owner information;
and judging whether the target data of the business update data aiming at the same car owner information are the same or not.
In some embodiments, after acquiring service update data for the vehicle owner information, the first service server updates current service data for the vehicle owner information into the service update data, and after updating is finished, the first service server sends the service update data for the vehicle owner information to the target server;
or,
after the first service server acquires the service update data aiming at the vehicle owner information, the first service server directly transmits the service update data aiming at the vehicle owner information to the target server; the data synchronization device further includes:
and the first sending module is used for sending an update notification message to the first service server when judging that the service update data aiming at the same vehicle owner information accords with a preset synchronous condition so as to notify the first service server that the current service data aiming at the vehicle owner information is updated into the service update data.
In some embodiments, the blockchain-based data synchronization device further includes an update module, configured to enable the first service server and/or the second service server to update the current service data of the same owner information based on the service update data, specifically configured to:
when the service update data is the registration data of the new car main information, the first service server and/or the second service server store the service update data;
when the service updating data is the modification data of the existing owner information, the first service server and/or the second service server modifies the existing owner information based on the service updating data.
In some embodiments, the blockchain-based data synchronization device further includes:
the second sending module is used for enabling the first service server to send service update data to the target server; the method is particularly used for: the first service server receives service update data sent by front-end equipment and encrypted according to preset encryption rules preset in the front-end equipment;
and the first service server obtains decrypted service update data according to a preset decryption rule, and sends the decrypted service update data to a target server.
In some embodiments, different service servers correspond to different levels of authority;
the data synchronization device further includes:
and the calling module is used for calling the target car owner information in the service server with the authority level lower than that of the target service server when the target service server in the block chain receives the inquiry request of the front-end equipment for the target car owner information, and sending the target car owner information to the front-end equipment.
Referring to fig. 6, in some embodiments, an electronic device 600 is further provided, including: a processor 602, a memory 601 and a bus, said memory 601 storing machine readable instructions executable by said processor 602, said processor 602 and said memory 601 communicating via the bus when the electronic device 600 is running, said machine readable instructions when executed by said processor 602 performing the steps of said blockchain based data synchronization method.
In some embodiments, a computer readable storage medium having a computer program stored thereon, which when executed by a processor performs the steps of the blockchain-based data synchronization method is also provided.
It will be clearly understood by those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described system and apparatus may refer to corresponding procedures in the method embodiments, which are not described in detail in this application. In the several embodiments provided in this application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. The above-described apparatus embodiments are merely illustrative, and the division of the modules is merely a logical function division, and there may be additional divisions when actually implemented, and for example, multiple modules or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be through some communication interface, indirect coupling or communication connection of devices or modules, electrical, mechanical, or other form.
The modules described as separate components may or may not be physically separate, and components shown as modules may or may not be physical units, may be located in one place, or may be distributed over multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
In addition, each functional unit in each embodiment of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.
The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a non-volatile computer readable storage medium executable by a processor. Based on such understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, including several instructions for causing a computer device (which may be a personal computer, a platform server, or a network device, etc.) to perform all or part of the steps of the methods described in the embodiments of the present application. And the aforementioned storage medium includes: a usb disk, a removable hard disk, a ROM, a RAM, a magnetic disk, or an optical disk, etc.
The foregoing is merely a specific embodiment of the present application, but the protection scope of the present application is not limited thereto, and any person skilled in the art can easily think about changes or substitutions within the technical scope of the present application, and the changes or substitutions are covered in the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.
Claims (9)
1. The data synchronization method based on the block chain is characterized by being applied to a target server in the block chain, wherein the block chain also comprises service servers in different vehicle service links; each service server corresponds to a front-end device, and the front-end device can collect service information in a vehicle service link; the data synchronization method comprises the following steps:
the target server receives service update data for the owner information sent by a first service server in the block chain; the service update data is: registration data of new car owner information or modification data for existing car owner information;
the target server checks the service update data sent by the first service server, and determines the weight of the first service server and each first service server in a block chain for each service update data of the same owner information when the service update data passes the check, wherein the weights of different service servers in the block chain are different, and the reliability of the data in the different service servers is different; judging whether the service update data aiming at the same vehicle owner information accords with a preset synchronous condition according to the sum of weights of a first service server for transmitting the service update data of the vehicle owner information; when the sum of the weights is larger than a preset weight threshold value, a preset synchronization condition is met; judging whether target data of service update data aiming at the same vehicle owner information are the same or not;
If yes, the target server selects a second service server which does not store the service update data of the same vehicle owner information from the blockchain, and synchronizes the service update data of the same vehicle owner information to the second service server so that the second service server updates the current service data of the same vehicle owner information based on the service update data.
2. The blockchain-based data synchronization method of claim 1, wherein the target server checks the service update data sent by the first service server and determines that the service update data check passes, comprising:
the target server judges whether the verification parameters of the service update data in preset multi-dimension meet preset standard conditions of the verification parameters in each dimension;
if yes, determining that the service update data passes the verification; wherein, the verification parameters under the multi-dimension meet the preset standard conditions of the verification parameters under each dimension, and the preset standard conditions comprise at least one of the following:
the target server judges whether the service update data accords with a preset attribute rule;
the target server judges whether the service updating data contains a preset service server identifier or not;
The target server judges whether the service update data contains a target field conforming to a preset field rule;
and the target server judges whether the service update data contains a verification result aiming at preset information.
3. The method for blockchain-based data synchronization of claim 1, wherein,
after acquiring service update data aiming at the vehicle owner information, the first service server updates the current service data aiming at the vehicle owner information into the service update data, and after updating is finished, the first service server sends the service update data aiming at the vehicle owner information to the target server;
or,
after the first service server acquires the service update data aiming at the vehicle owner information, the first service server directly transmits the service update data aiming at the vehicle owner information to the target server; the data synchronization method further comprises the following steps:
and when judging that the service update data aiming at the same vehicle owner information accords with a preset synchronous condition, the target server sends an update notification message to the first service server so as to notify the first service server that the current service data aiming at the vehicle owner information is updated into the service update data.
4. The blockchain-based data synchronization method of claim 1, wherein the first service server and/or the second service server updates current service data of the same owner information based on the service update data, comprising:
when the service update data is the registration data of the new car main information, the first service server and/or the second service server store the service update data;
when the service update data is modification data of existing vehicle owner information, the first service server and/or the second service server modifies the existing vehicle owner information based on the service update data.
5. The method for blockchain-based data synchronization of claim 1, wherein,
the first service server sends service update data to the target server, and the method comprises the following steps:
the first service server receives service update data sent by front-end equipment and encrypted according to preset encryption rules preset in the front-end equipment;
and the first service server obtains decrypted service update data according to a preset decryption rule and sends the decrypted service update data to the target server.
6. The blockchain-based data synchronization method of claim 1, wherein different service servers correspond to different authority levels;
the data synchronization method further comprises the following steps:
when a target service server in the block chain receives a query request of front-end equipment for target owner information, calling the target owner information in the service server with authority level lower than that of the target service server, and sending the target owner information to the front-end equipment.
7. The data synchronization device based on the block chain is characterized by being applied to a target server in the block chain, wherein the block chain also comprises service servers in different vehicle service links; each service server corresponds to a front-end device, and the front-end device can collect service information in a vehicle service link; the data synchronization device includes:
the first receiving module is used for receiving service update data for the owner information sent by a first service server in the block chain; the service update data is: registration data of new car owner information or modification data for existing car owner information;
the second receiving module is used for checking the service update data sent by the first service server, determining the first service server for sending the service update data of the same owner information and the weight of each first service server in a block chain aiming at each service update data of the same owner information when the service update data passes the check, wherein the weights of different service servers in the block chain are different, and the reliability degree of the data in the different service servers is different; judging whether the service update data aiming at the same vehicle owner information accords with a preset synchronous condition according to the sum of weights of a first service server for transmitting the service update data of the vehicle owner information; when the sum of the weights is larger than a preset weight threshold value, a preset synchronization condition is met; judging whether target data of service update data aiming at the same vehicle owner information are the same or not;
And the synchronization module is used for selecting a second service server which does not store the service update data of the same vehicle owner information from the block chain when judging whether the service update data of the same vehicle owner information accords with a preset synchronization condition, and synchronizing the service update data of the same vehicle owner information into the second service server so that the second service server updates the current service data of the same vehicle owner information based on the service update data.
8. An electronic device, comprising: a processor, a memory and a bus, the memory storing machine-readable instructions executable by the processor, the processor and the memory in communication over the bus when the electronic device is running, the machine-readable instructions when executed by the processor performing the steps of the blockchain-based data synchronization method of any of claims 1 to 6.
9. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, performs the steps of the blockchain-based data synchronization method of any of claims 1 to 6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210817131.3A CN115086065B (en) | 2022-07-12 | 2022-07-12 | Block chain-based data synchronization method and device, electronic equipment and medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210817131.3A CN115086065B (en) | 2022-07-12 | 2022-07-12 | Block chain-based data synchronization method and device, electronic equipment and medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN115086065A CN115086065A (en) | 2022-09-20 |
| CN115086065B true CN115086065B (en) | 2024-01-19 |
Family
ID=83260567
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210817131.3A Active CN115086065B (en) | 2022-07-12 | 2022-07-12 | Block chain-based data synchronization method and device, electronic equipment and medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115086065B (en) |
Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826073A (en) * | 2009-03-06 | 2010-09-08 | 华为技术有限公司 | Synchronous method, apparatus and system for distributed database |
| CN103795754A (en) * | 2012-10-31 | 2014-05-14 | 中国电信股份有限公司 | Method and system for data synchronization among multiple systems |
| CN110427424A (en) * | 2019-07-09 | 2019-11-08 | 深圳壹账通智能科技有限公司 | Business datum checking method, device, computer equipment and storage medium |
| CN110457914A (en) * | 2019-07-09 | 2019-11-15 | 深圳壹账通智能科技有限公司 | Verification of data method, apparatus, computer equipment and storage medium |
| CN110569658A (en) * | 2019-09-12 | 2019-12-13 | 腾讯科技（深圳）有限公司 | User information processing method and device based on block chain network, electronic equipment and storage medium |
| CN111147392A (en) * | 2019-12-25 | 2020-05-12 | 腾讯科技（深圳）有限公司 | Data synchronization method, device and equipment based on block chain and readable storage medium |
| CN111639363A (en) * | 2020-05-24 | 2020-09-08 | 石高峰 | Data analysis method based on block chain and edge computing server |
| CN112035281A (en) * | 2020-08-31 | 2020-12-04 | 安徽江淮汽车集团股份有限公司 | Multi-laser radar data output method, device, equipment and storage medium |
| CN114268799A (en) * | 2021-12-23 | 2022-04-01 | 杭州阿启视科技有限公司 | Streaming media transmission method and device, electronic equipment and medium |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN108701324A (en) * | 2018-05-31 | 2018-10-23 | 深圳市元征科技股份有限公司 | A kind of management method and server of shared vehicle |
| CN111222165B (en) * | 2020-01-10 | 2022-09-23 | 北京百度网讯科技有限公司 | Multi-party computing method, device, equipment and medium based on block chain |
-
2022
- 2022-07-12 CN CN202210817131.3A patent/CN115086065B/en active Active
Patent Citations (9)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN101826073A (en) * | 2009-03-06 | 2010-09-08 | 华为技术有限公司 | Synchronous method, apparatus and system for distributed database |
| CN103795754A (en) * | 2012-10-31 | 2014-05-14 | 中国电信股份有限公司 | Method and system for data synchronization among multiple systems |
| CN110427424A (en) * | 2019-07-09 | 2019-11-08 | 深圳壹账通智能科技有限公司 | Business datum checking method, device, computer equipment and storage medium |
| CN110457914A (en) * | 2019-07-09 | 2019-11-15 | 深圳壹账通智能科技有限公司 | Verification of data method, apparatus, computer equipment and storage medium |
| CN110569658A (en) * | 2019-09-12 | 2019-12-13 | 腾讯科技（深圳）有限公司 | User information processing method and device based on block chain network, electronic equipment and storage medium |
| CN111147392A (en) * | 2019-12-25 | 2020-05-12 | 腾讯科技（深圳）有限公司 | Data synchronization method, device and equipment based on block chain and readable storage medium |
| CN111639363A (en) * | 2020-05-24 | 2020-09-08 | 石高峰 | Data analysis method based on block chain and edge computing server |
| CN112035281A (en) * | 2020-08-31 | 2020-12-04 | 安徽江淮汽车集团股份有限公司 | Multi-laser radar data output method, device, equipment and storage medium |
| CN114268799A (en) * | 2021-12-23 | 2022-04-01 | 杭州阿启视科技有限公司 | Streaming media transmission method and device, electronic equipment and medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN115086065A (en) | 2022-09-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107909416B (en) | Vehicle price evaluation method and vehicle price evaluation device | |
| US11531661B2 (en) | Vehicle incident documentation for blockchain | |
| CN109829621B (en) | Network appointment vehicle dispatching method and device | |
| US10284654B2 (en) | Trusted vehicle telematics using blockchain data analytics | |
| US11057426B2 (en) | Methods and systems providing cyber defense for electronic identification, vehicles, ancillary vehicle platforms and telematics platforms | |
| CN108694330B (en) | Internet of things data management method, platform and equipment | |
| US20230290195A1 (en) | Tracking of transport data | |
| US20230334918A1 (en) | Analysis of transport damage | |
| KR20190109804A (en) | Apparatus and method of car calling service in autonomous vehicle | |
| CN104464114A (en) | System and method for managing and monitoring safety of application of financial terminals | |
| CN111639836A (en) | Vehicle scheduling processing method and device based on block chain and computer equipment | |
| CN108540335B (en) | Management method and management device for equipment analysis report | |
| CN115086065B (en) | Block chain-based data synchronization method and device, electronic equipment and medium | |
| US11217041B2 (en) | Tracking of transport data | |
| US11500571B2 (en) | Tracking of transport data | |
| CN111475778A (en) | Music data processing method and device based on block chain | |
| US11978123B2 (en) | Analysis of transport damage | |
| CN113273159A (en) | Method and system for collecting and managing vehicle generated data | |
| US20030074557A1 (en) | Method and system for management of properties | |
| CN112636954B (en) | Server upgrading method and device | |
| CA2765987C (en) | Method for validating a road traffic control transaction | |
| CN111654591B (en) | Picture tamper-proof method, computer device and storage medium | |
| CN111901299A (en) | Application authentication method and device, electronic equipment and storage medium | |
| US11457000B2 (en) | Information intermediating apparatus, information providing apparatus, and information acquiring apparatus | |
| CN111815327A (en) | Data true checking method and device and electronic equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |