Implementation method and system of motor vehicle pre-inspection data aggregation and fusion

Abstract

The application relates to the technical field of data processing, and particularly discloses a kind of implementation methods of motor vehicle pre-inspection data convergence, which comprises the following steps: system record in advance is carried out to motor vehicle production enterprises and inspection area, the time range that control motor vehicle production enterprises can access, access frequency, server IP address, interface permission list, limit the inspection area list that motor vehicle production enterprises can upload motor vehicle inspection data; motor vehicle inspection data is formatted, digitally signed and encoded; motor vehicle inspection data is digitally signed and verified, legality and validity are checked, and the second verification is carried out to vehicle identification code overprint film PDF file; motor vehicle pre-inspection data and announcement, qualified certificate information are compared.The application also discloses a kind of implementation systems of motor vehicle pre-inspection data convergence.The application can guarantee the reliability and accuracy of motor vehicle pre-inspection data, effectively improve the efficiency of motor vehicle pre-inspection data convergence.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, and more specifically, to a method and system for the aggregation and fusion of motor vehicle pre-inspection data. Background Technology

[0002] Article 14 of the "Regulations on Motor Vehicle Registration" (No. 164) of the People's Republic of China stipulates that "when vehicle management offices establish a network with motor vehicle manufacturers to verify the information of new vehicles before they leave the factory, motor vehicle owners applying for registration of small and micro non-commercial passenger vehicles are exempt from submitting their vehicles for inspection." This regulation is an important measure taken by the Ministry of Public Security and the Ministry of Industry and Information Technology to promote the reform and innovation of automobile sales registration models, strengthen the management of vehicle production consistency, facilitate business for the public and enterprises, promote the development of the automobile industry, and create a favorable marketing environment.

[0003] Before leaving the factory, new vehicles undergo inspection by the vehicle manufacturer, a process that generates a large amount of structured data and images. To ensure the availability of inspection data and images nationwide and to guarantee the security and reliability of the data exchange links, this invention proposes to aggregate and integrate vehicle inspection data and images into a unified national pre-inspection service system. This system must conduct a standardization check on the data submitted by vehicle manufacturers and perform security verification on the data exchange links between manufacturers. Summary of the Invention

[0004] To address the security and reliability issues of data aggregation from different vehicle manufacturers, this invention provides a method and system for the aggregation and fusion of pre-inspection vehicle data. This method effectively ensures the security and immutability of inspection data transmission, reduces the time required for cross-platform system integration, and improves the efficiency of data aggregation and fusion.

[0005] As a first aspect of the present invention, a method for realizing the aggregation and fusion of motor vehicle pre-inspection data is provided, comprising:

[0006] Step S1: Register all motor vehicle manufacturers and their inspection areas that have accessed the pre-inspection service system;

[0007] Step S2: The pre-verification service system assigns an interface serial number, public and private keys, and access time limits to the connected motor vehicle manufacturers, and registers the digital certificate root certificate of the motor vehicle manufacturers.

[0008] Step S3: Associate the motor vehicle manufacturer with the inspection area, and allow the motor vehicle manufacturer to upload motor vehicle data inspected in its associated inspection area;

[0009] Step S4: The motor vehicle manufacturer converts the motor vehicle data inspected in its associated inspection area into a pre-set string format, signs the string using the private key allocated in step S2, encodes the obtained digital signature and motor vehicle inspection data, and finally uploads the encoded data to the pre-inspection service system.

[0010] Step S5: The pre-inspection service system decodes the received encoded data, verifies the decoded digital signature using the public key allocated in step S2, and verifies the legality and authorization of the decoded motor vehicle inspection data based on the registration information of the motor vehicle manufacturer and its inspection area.

[0011] Step S6: The pre-inspection service system performs announcement comparison, certificate comparison and data aggregation processing on the decoded motor vehicle inspection data.

[0012] Furthermore, the registration information of the motor vehicle manufacturer includes the unified social credit code, the expiration date of the unified social credit code, the postal code, the manufacturer's address, the manufacturer's contact information, the name of the legal representative, the contact information of the legal representative, the expiration date of access, the allowed IP address, a photo of the business license, a photo of the legal representative's ID card, a digital certificate, and the associated inspection area; the registration information of the inspection area includes the inspection area code, the inspection area name, the name of the company to which it belongs, the city where it is located, the contact person, the contact number, the detailed address, the postal code, the brand of the vehicles produced, and the vehicle model.

[0013] Furthermore, step S3 also includes:

[0014] The inspection area inspects each vehicle coming off the production line to determine its type, model, body color, approved passenger capacity, vehicle identification number, engine number, vehicle appearance and tire condition. It also generates PDF files containing photos of the vehicle from the left front 45 degrees, the right rear 45 degrees, the front of the vehicle, the rear of the vehicle, and a vehicle identification number imprint, in order to generate vehicle inspection data.

[0015] Furthermore, steps S5 and S6 also include:

[0016] When the decoded digital signature verification is valid, the pre-inspection service system determines whether the decoded motor vehicle inspection data is valid based on the registration information of the motor vehicle manufacturer and its inspection area;

[0017] When the decoded vehicle inspection data is valid, the pre-inspection service system converts the decoded vehicle inspection data into a pre-defined inspection object, obtains a unique vehicle announcement object based on the vehicle model and announcement batch in the inspection object, and compares the inspection object and the vehicle announcement object from multiple perspectives.

[0018] If the object to be inspected is the same as the object to be announced in the motor vehicle announcement, the pre-inspection service system queries the corresponding certificate object of the motor vehicle based on the certificate number in the decoded motor vehicle inspection data, and compares the decoded motor vehicle inspection data with the certificate object.

[0019] If the decoded vehicle inspection data matches the certificate of conformity, the decoded vehicle inspection data is saved to the database.

[0020] Furthermore, it also includes:

[0021] When the decoded digital signature verification is valid, the pre-inspection service system determines whether the number of times the motor vehicle manufacturer uploads and writes within a unit of time exceeds the prescribed value;

[0022] If the value is not exceeded, the pre-inspection service system determines whether the decoded vehicle inspection data meets the conditions. The detailed steps are as follows:

[0023] a1: Query the registration information of the motor vehicle manufacturer based on the interface serial number in the inspection data to determine whether the current motor vehicle manufacturer is registered;

[0024] If it is not in the filing information, skip directly and no further action is required;

[0025] If it is in the filing information, then proceed to step a2;

[0026] a2: Determine whether the current motor vehicle manufacturer has the relevant interface permissions;

[0027] If it is not in the interface permission list, skip directly and do not need to perform subsequent steps;

[0028] If it is in the interface permission list, then proceed to step a3;

[0029] a3: Determine if the requested server address is in the address registration list;

[0030] If your address is not on the address registration list, skip this step and do not proceed.

[0031] If the address is in the registration list, proceed to step a4;

[0032] a4: Determine if the request time is within the filing period;

[0033] If it is outside the filing period, skip directly and do not need to perform the following steps;

[0034] If it is within the filing period, proceed to step a5;

[0035] a5: Determine whether the inspection area in the inspection data is in the inspection area filing list;

[0036] If it is not on the inspection area's registration list, skip directly and do not need to perform the following steps;

[0037] If it is in the inspection area's registration list, proceed to step a6;

[0038] a6: Determine whether the motor vehicle manufacturer in the inspection data is in the write permission list of the inspection area;

[0039] If it is not in the write permission list of the inspection area, skip directly and do not need to perform subsequent steps;

[0040] If it is in the write permission list of the inspection area, then proceed to step a7;

[0041] a7: Query the database based on the interface serial number in the inspection data, obtain the registered digital certificate root certificate, and verify the vehicle identification number imprint PDF file.

[0042] If the signature verification fails, skip directly and do not need to perform the following steps;

[0043] If the verification is successful, the object being inspected will be compared with the object in the vehicle announcement from multiple perspectives.

[0044] Furthermore, the multi-angle comparison of the inspection object and the vehicle announcement object also includes:

[0045] b1: Determine whether the manufacturer's name, gross weight, wheelbase, number of axles, tire specifications, engine displacement, overall dimensions, environmental compliance status, engine model, fuel type, steering type, and vehicle type in the inspection data are consistent with the motor vehicle announcement object;

[0046] If any data item is inconsistent, skip it and do not proceed with the next step.

[0047] If all data content is consistent, proceed to step b2;

[0048] b2: If the inspected vehicle is a new energy vehicle, it shall be compared with the new energy vehicle category of the vehicle announcement object;

[0049] If the types of new energy sources are inconsistent, skip this step and do not need to proceed.

[0050] If the types of new energy sources are the same, proceed to step b3;

[0051] b3: If the production cessation date in the motor vehicle announcement is not empty, then determine the relationship between the current date and the production cessation date;

[0052] If the current date is later than the production stop date, skip this step and do not proceed.

[0053] If the current date is not greater than the production stop date, the pre-inspection service system queries the corresponding certificate of conformity for the motor vehicle based on the certificate of conformity number in the decoded motor vehicle inspection data.

[0054] Furthermore, the pre-inspection service system, based on the certificate number in the decoded vehicle inspection data, queries the corresponding certificate object for the vehicle, and also includes:

[0055] If no certificate of conformity is obtained, skip this step and do not proceed.

[0056] If a certificate of conformity is obtained, the decoded vehicle inspection data and the certificate of conformity are compared.

[0057] Furthermore, the comparison of the decoded vehicle inspection data and the certificate of conformity also includes:

[0058] c1: Determine whether the certificate of conformity being checked is valid;

[0059] If the certificate of conformity is invalid, skip this step and do not proceed.

[0060] If the certificate of conformity is valid, proceed to step c2;

[0061] c2: Determine whether the vehicle identification number, vehicle brand, vehicle model, manufacturing date, vehicle manufacturer name, engine number, engine model, chassis certificate number, and body color in the inspection data are consistent with the certificate of conformity.

[0062] If any data item is inconsistent, skip it and do not proceed with the next step.

[0063] If all the information is consistent, the decoded vehicle inspection data will be saved to the database.

[0064] As a second aspect of the present invention, a system for the aggregation and fusion of motor vehicle pre-inspection data is provided, comprising:

[0065] The registration module is used to register all motor vehicle manufacturers and their inspection areas that have accessed the pre-inspection service system;

[0066] The allocation module is used by the pre-verification service system to allocate interface serial numbers, public and private keys and access time limits to the connected motor vehicle manufacturers, and to register the digital certificate root certificate of the motor vehicle manufacturers.

[0067] The association module is used to associate the motor vehicle manufacturers with the inspection areas, and allows the motor vehicle manufacturers to upload motor vehicle data inspected in their associated inspection areas;

[0068] The encoding module is used by the motor vehicle manufacturer to convert the motor vehicle data inspected in the associated inspection area into a preset string format, sign the string using the private key allocated in step S2, encode the obtained digital signature and motor vehicle inspection data, and finally upload the encoded data to the pre-inspection service system.

[0069] The verification module is used by the pre-inspection service system to decode the received encoded data, verify the decoded digital signature using the public key allocated in step S2, and verify the legality and authorization of the decoded motor vehicle inspection data based on the registration information of the motor vehicle manufacturer and its inspection area.

[0070] The processing module is used by the pre-inspection service system to perform announcement comparison, certificate comparison and data aggregation processing on the decoded motor vehicle inspection data.

[0071] Furthermore, the registration information of the motor vehicle manufacturer includes the unified social credit code, the expiration date of the unified social credit code, the postal code, the manufacturer's address, the manufacturer's contact information, the name of the legal representative, the contact information of the legal representative, the expiration date of access, the allowed IP address, a photo of the business license, a photo of the legal representative's ID card, a digital certificate, and the associated inspection area; the registration information of the inspection area includes the inspection area code, the inspection area name, the name of the company to which it belongs, the city where it is located, the contact person, the contact number, the detailed address, the postal code, the brand of the vehicles produced, and the vehicle model.

[0072] The method for merging and integrating pre-inspection vehicle data provided by this invention has the following advantages: It registers vehicle manufacturers and inspection areas, assigns interface serial numbers and private keys, and controls the interfaces, server addresses, and time ranges accessed by vehicle manufacturers, thereby improving the security and reliability of system integration; it digitally signs and encodes vehicle inspection data to ensure the reliability of data sources and the integrity and security of vehicle inspection data; and it effectively improves the efficiency of merging and integrating vehicle inspection data from different vehicle manufacturers and enhances the accuracy of data collection. Attached Figure Description

[0073] The accompanying drawings are provided to further illustrate the invention and form part of the specification. They are used together with the following detailed description to explain the invention, but do not constitute a limitation thereof.

[0074] Figure 1 The flowchart illustrates the implementation method for the aggregation and fusion of motor vehicle pre-inspection data provided by this invention.

[0075] Figure 2 The flowchart for the aggregation and fusion of motor vehicle inspection data provided by this invention.

[0076] Figure 3 The present invention provides a flowchart for verifying motor vehicle inspection data.

[0077] Figure 4 This is a structural diagram of the system for realizing the aggregation and fusion of motor vehicle pre-inspection data provided by the present invention.

[0078] Figure 5 This invention provides an interactive flowchart between motor vehicle manufacturers and the pre-inspection service system. Detailed Implementation

[0079] To further illustrate the technical means and effects adopted by the present invention to achieve its intended purpose, the following, in conjunction with the accompanying drawings and preferred embodiments, details the specific implementation methods, structures, features, and effects of the method and system for the convergence and fusion of motor vehicle pre-inspection data proposed according to the present invention. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the protection scope of the present invention.

[0080] This embodiment provides a method for the aggregation and fusion of motor vehicle pre-inspection data, such as... Figure 1 As shown, the method for realizing the aggregation and fusion of motor vehicle pre-inspection data includes:

[0081] Step S1: As Figure 5 As shown, all motor vehicle manufacturers 2 and their inspection areas connected to the pre-inspection service system 1 are registered; the vehicle brands and models allowed to be written to the inspection area are authorized, and the server address and time range for data uploaded by motor vehicle manufacturers are restricted;

[0082] Specifically, the registration information of the motor vehicle manufacturers includes the unified social credit code, the expiration date of the unified social credit code, the postal code, the manufacturer's address, the manufacturer's contact information, the name of the legal representative, the legal representative's contact information, the expiration date of access, the number of times allowed to access within a unit of time, the allowed IP address, a photo of the business license, a photo of the legal representative's ID card, a list of accessible interfaces, digital certificates, and associated inspection areas; the registration information of the inspection areas includes the inspection area code, the inspection area name, the name of the company to which it belongs, the city where it is located, the contact person, the contact number, the detailed address, the postal code, the brand and model of the vehicles produced.

[0083] It should be noted that the interface serial number is generated randomly by the system and consists of 18 characters including uppercase and lowercase letters and numbers. The public and private key generation method is as follows: to enhance the randomness of the public and private key generation, the product of the current system time and two random numbers is used as the seed, and an asymmetric encryption RSA algorithm is used to generate a byte stream of length 2048 bits. The byte stream is then encoded using Base64 to finally generate the private key assigned to the motor vehicle manufacturing enterprise.

[0084] Step S2: The pre-verification service system assigns an interface serial number, public and private keys, and access time limits to the connected motor vehicle manufacturers, and registers the digital certificate root certificate of the motor vehicle manufacturers.

[0085] Step S3: Associate the motor vehicle manufacturer with the inspection area, and allow the motor vehicle manufacturer to upload motor vehicle data inspected in its associated inspection area;

[0086] Preferably, step S3 further includes:

[0087] The inspection area inspects each vehicle coming off the production line according to the "Motor Vehicle Inspection Work Procedures," determining the vehicle type, model, body color, approved passenger capacity, vehicle identification number (VIN), engine / drive motor number, Chinese brand, announcement batch, certificate of conformity number, fuel type, displacement and power, steering type, track width, tire specifications, gross vehicle weight, manufacturer's name, date of manufacture, inspection date, vehicle appearance, and tire condition. It also generates photographic data, including photos of the vehicle at a 45-degree angle from the left front, a 45-degree angle from the right rear, a front view, a rear view, and a PDF file containing a VIN rubbing, to form the vehicle inspection data. The date of manufacture and inspection date are in string format, the photographic data are in Base64 string format, and other fields are in JSON string format.

[0088] Specifically, the tilt angle of the photos taken from the front and rear of the motor vehicle should be between 30 and 45 degrees, and the horizontal rotation angle should be less than 10 degrees; the vehicle content should occupy more than 2 / 3 of the entire image content, and there should only be one vehicle in a single image, and the photo should include the complete front or rear view of the vehicle; the horizontal pixel ratio of the photo should be 4:3, and the number of pixels in the photo should not be less than 2 million; the photo should be a three-channel RGB color image stored in JPG format, and the size should not exceed 300KB; the background of the road surface should preferably be a single light color.

[0089] Step S4: As Figure 2 As shown, the inspection area aggregates the generated motor vehicle inspection data to the unified motor vehicle inspection system of the motor vehicle manufacturer. Then, the inspector manually confirms the data. The motor vehicle manufacturer converts the motor vehicle data inspected in its associated inspection area into a pre-defined JSON string "params" using Fastjson. The manufacturer then signs the string using SHA256withRSA with the private key allocated in step S2. The resulting digital signature string "sign" and the motor vehicle inspection data JSON string are then Base64 encoded. Finally, the encoded data is uploaded to the pre-inspection service system through a unified external gateway.

[0090] Specifically, the private key string is converted into a byte stream using Base64 decoding, and the verification data is digitally signed using the PKCS8 standard, SHA256withRSA algorithm, and UTF-8 encoding format.

[0091] Step S5: The pre-inspection service system performs Base64 decoding on the received encoded data and verifies the decoded digital signature using the public key allocated in step S2. If the signature is valid, the system verifies the legality and authorization of the decoded motor vehicle inspection data based on the registration information of the motor vehicle manufacturer and its inspection area. If the signature is invalid, the system skips the step and does not need to perform subsequent steps.

[0092] Specifically, the database table is queried based on the interface serial number to obtain information such as filing information, authorized interface list, accessible server address, and associated inspection area. This information is then used to verify the filing of motor vehicle manufacturers, determine interface permissions, check server addresses, verify request time and frequency, compare the association of inspection areas, and verify the signature of vehicle identification number imprint documents.

[0093] Step S6: The pre-inspection service system performs announcement comparison, certificate comparison and data aggregation processing on the decoded motor vehicle inspection data.

[0094] Specifically, it also includes:

[0095] Signature verification involves querying the database to obtain the corresponding public key based on the pre-verification data, converting the public key string and signature string into a byte stream using Base64 decoding, and verifying the signature data using X509, SHA256withRSA algorithms and UTF-8 encoding format.

[0096] The announcement comparison involves retrieving a unique and valid announcement from the database based on the vehicle brand, announcement batch, and vehicle model in the inspection data. The inspection data and announcement information are then compared to the manufacturer's name, gross weight, track width, wheelbase, number of axles, tire specifications, engine displacement, overall dimensions, environmental compliance status, engine model, fuel type, steering type, and whether it is a new energy vehicle. Only if all of these match can the next step be carried out.

[0097] The certificate of conformity comparison involves comparing the vehicle identification number, vehicle brand, vehicle model, manufacturing date, vehicle manufacturer name, engine number, engine model, chassis certificate of conformity number, and body color in the inspection data and certificate of conformity information based on the certificate number in the pre-inspection data. Only if all of them match can the next step be carried out.

[0098] Preferably, steps S5 and S6 further include:

[0099] When the decoded digital signature verification is valid, the pre-inspection service system determines whether the decoded motor vehicle inspection data is valid based on the registration information of the motor vehicle manufacturer and its inspection area;

[0100] When the decoded vehicle inspection data is valid, the pre-inspection service system converts the decoded vehicle inspection data into a pre-defined inspection object, obtains a unique vehicle announcement object based on the vehicle model, vehicle brand, and announcement batch in the inspection object, and compares the inspection object and the vehicle announcement object from multiple perspectives; if the source of the decoded vehicle inspection data is invalid, an error message is returned to the vehicle manufacturer, and the current step ends.

[0101] If the object to be inspected matches the object announced in the vehicle announcement, the pre-inspection service system queries the corresponding certificate of conformity for the vehicle based on the certificate number in the decoded vehicle inspection data, and compares the decoded vehicle inspection data with the certificate of conformity. If the object to be inspected does not match the object announced in the vehicle announcement, an error message is returned to the vehicle manufacturer, and the current step ends.

[0102] If the decoded vehicle inspection data matches the certificate of conformity, the decoded vehicle inspection data is saved to the database; if the inspection data does not match the certificate of conformity, an error message is returned to the vehicle manufacturer, and the current step ends.

[0103] Preferably, it further includes:

[0104] When the decoded digital signature verification is valid, the pre-verification service system determines whether the number of times the motor vehicle manufacturer uploads and writes within a unit of time exceeds the prescribed value; if it exceeds the value, it skips directly without performing subsequent steps.

[0105] If the value is not exceeded, the pre-inspection service system determines whether the decoded vehicle inspection data meets the conditions. The detailed steps are as follows:

[0106] a1: Query the registration information of the motor vehicle manufacturer based on the interface serial number in the inspection data to determine whether the current motor vehicle manufacturer is registered;

[0107] If it is not in the filing information, skip directly and no further action is required;

[0108] If it is in the filing information, then proceed to step a2;

[0109] a2: Determine whether the current motor vehicle manufacturer has the relevant interface permissions;

[0110] If it is not in the interface permission list, skip directly and do not need to perform subsequent steps;

[0111] If it is in the interface permission list, then proceed to step a3;

[0112] a3: Determine if the requested server address is in the address registration list;

[0113] If your address is not on the address registration list, skip this step and do not proceed.

[0114] If the address is in the registration list, proceed to step a4;

[0115] a4: Determine if the request time is within the filing period;

[0116] If it is outside the filing period, skip directly and do not need to perform the following steps;

[0117] If it is within the filing period, proceed to step a5;

[0118] a5: Determine whether the inspection area in the inspection data is in the inspection area filing list;

[0119] If it is not on the inspection area's registration list, skip directly and do not need to perform the following steps;

[0120] If it is in the inspection area's registration list, proceed to step a6;

[0121] a6: Determine whether the motor vehicle manufacturer in the inspection data is in the write permission list of the inspection area;

[0122] If it is not in the write permission list of the inspection area, skip directly and do not need to perform subsequent steps;

[0123] If it is in the write permission list of the inspection area, then proceed to step a7;

[0124] a7: Query the database based on the interface serial number in the inspection data, obtain the registered digital certificate root certificate, and verify the vehicle identification number imprint PDF file.

[0125] If the signature verification fails, skip directly and do not need to perform the following steps;

[0126] If the verification is successful, the object being inspected will be compared with the object in the vehicle announcement from multiple perspectives.

[0127] Preferably, the step of comparing the inspection object and the vehicle announcement object from multiple perspectives further includes:

[0128] b1: Determine whether the manufacturer's name, gross weight, wheelbase, number of axles, tire specifications, engine displacement, overall dimensions, environmental compliance status, engine model, fuel type, steering type, and vehicle type in the inspection data are consistent with the motor vehicle announcement object;

[0129] If any data item is inconsistent, skip it and do not proceed with the next step.

[0130] If all data content is consistent, proceed to step b2;

[0131] b2: If the inspected vehicle is a new energy vehicle, it shall be compared with the new energy vehicle category of the vehicle announcement object;

[0132] If the types of new energy sources are inconsistent, skip this step and do not need to proceed.

[0133] If the types of new energy sources are the same, proceed to step b3;

[0134] b3: If the production cessation date in the motor vehicle announcement is not empty, then determine the relationship between the current date and the production cessation date;

[0135] If the current date is later than the production stop date, skip this step and do not proceed.

[0136] If the current date is not greater than the production stop date, the pre-inspection service system queries the corresponding certificate of conformity for the motor vehicle based on the certificate of conformity number in the decoded motor vehicle inspection data.

[0137] Preferably, the pre-inspection service system, based on the certificate number in the decoded vehicle inspection data, queries the corresponding certificate of conformity for the vehicle, and further includes:

[0138] If no certificate of conformity is obtained, skip this step and do not proceed.

[0139] If a certificate of conformity is obtained, the decoded vehicle inspection data and the certificate of conformity are compared.

[0140] Preferably, comparing the decoded vehicle inspection data with the certificate of conformity further includes:

[0141] c1: Determine whether the certificate of conformity being checked is valid;

[0142] If the certificate of conformity is invalid, skip this step and do not proceed.

[0143] If the certificate of conformity is valid, proceed to step c2;

[0144] c2: Determine whether the vehicle identification number, vehicle brand, vehicle model, manufacturing date, vehicle manufacturer name, engine number, engine model, chassis certificate number, and body color in the inspection data are consistent with the certificate of conformity.

[0145] If any data item is inconsistent, skip it and do not proceed with the next step.

[0146] If all the information is consistent, the decoded vehicle inspection data will be saved to the database.

[0147] In practical applications, the pre-inspection service system saves the received images of the vehicle from the left front 45 degrees, the right rear 45 degrees, the front of the vehicle, the rear of the vehicle, and the vehicle identification number imprint PDF file to HBase, reducing database storage consumption.

[0148] In embodiments of the present invention, such as Figure 3 As shown, the verification process for motor vehicle inspection data is as follows:

[0149] Step S301: Convert vehicle inspection data into a JSON string;

[0150] Step S302: Perform digital signature and Base64 encoding;

[0151] Step S303: Upload data to the pre-inspection service system;

[0152] Step S304: Decode and verify the received data;

[0153] Step S305: Determine if the data source is valid;

[0154] Step S306: Enterprise permission determination;

[0155] Step S307: Compare the inspection data with the vehicle announcement;

[0156] Step S308: Compare the inspection data with the certificate of conformity information;

[0157] Step S309: Save the verification data.

[0158] As another embodiment of the present invention, such as Figure 4 As shown, a system for the aggregation and fusion of motor vehicle pre-inspection data is provided. The system includes:

[0159] The registration module is used to register all motor vehicle manufacturers and their inspection areas that have accessed the pre-inspection service system;

[0160] The allocation module is used by the pre-verification service system to allocate interface serial numbers, public and private keys and access time limits to the connected motor vehicle manufacturers, and to register the digital certificate root certificate of the motor vehicle manufacturers.

[0161] The association module is used to associate the motor vehicle manufacturers with the inspection areas, and allows the motor vehicle manufacturers to upload motor vehicle data inspected in their associated inspection areas;

[0162] The encoding module is used by the motor vehicle manufacturer to convert the motor vehicle data inspected in the associated inspection area into a preset string format, sign the string using the private key allocated in step S2, encode the obtained digital signature and motor vehicle inspection data, and finally upload the encoded data to the pre-inspection service system.

[0163] The verification module is used by the pre-inspection service system to decode the received encoded data, verify the decoded digital signature using the public key allocated in step S2, and verify the legality and authorization of the decoded motor vehicle inspection data based on the registration information of the motor vehicle manufacturer and its inspection area.

[0164] The processing module is used by the pre-inspection service system to perform announcement comparison, certificate comparison and data aggregation processing on the decoded motor vehicle inspection data.

[0165] Preferably, the registration information of the motor vehicle manufacturer includes the unified social credit code, the expiration date of the unified social credit code, the postal code, the manufacturer's address, the manufacturer's contact information, the name of the legal representative, the contact information of the legal representative, the expiration date of access, the allowed IP address, a photo of the business license, a photo of the legal representative's ID card, a digital certificate, and the associated inspection area; the registration information of the inspection area includes the inspection area code, the inspection area name, the name of the company to which it belongs, the city where it is located, the contact person, the contact number, the detailed address, the postal code, the brand of the vehicles produced, and the vehicle model.

[0166] The method for merging and integrating motor vehicle pre-inspection data provided by this invention establishes standardized mechanisms for data encoding, data signing, data transmission, data decoding and verification, data restoration, permission verification, announcement comparison, and certificate comparison. During network transmission, motor vehicle inspection data undergoes SHA256WithRSA signing, Base64 encoding, and information decoding and verification using asymmetric keys, ensuring the security and integrity of the information data. During secure transmission via HTTPS, the data is connected according to the "Internet Traffic Safety Integrated Service Management Platform Data Access Specification GA / T 1504-2018," ensuring that only designated application servers can transmit data, thus providing secondary protection for data validity and network resource consumption.

[0167] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes, and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A method for realizing the aggregation and fusion of motor vehicle pre-inspection data, characterized in that, include: Step S1: Register all motor vehicle manufacturers and their inspection areas that have accessed the pre-inspection service system; Step S2: The pre-verification service system assigns an interface serial number, public and private keys, and access time limits to the connected motor vehicle manufacturers, and registers the digital certificate root certificate of the motor vehicle manufacturers. Step S3: Associate the motor vehicle manufacturer with the inspection area, and allow the motor vehicle manufacturer to upload motor vehicle data inspected in its associated inspection area; Step S4: The motor vehicle manufacturer converts the motor vehicle data inspected in its associated inspection area into a pre-set string format, signs the string using the private key allocated in step S2, encodes the obtained digital signature and motor vehicle inspection data, and finally uploads the encoded data to the pre-inspection service system. Step S5: The pre-inspection service system decodes the received encoded data, verifies the decoded digital signature using the public key allocated in step S2, and verifies the legality and authorization of the decoded motor vehicle inspection data based on the registration information of the motor vehicle manufacturer and its inspection area. Step S6: The pre-inspection service system performs announcement comparison, certificate comparison, and data aggregation processing on the decoded motor vehicle inspection data; Steps S5 and S6 further include: When the decoded digital signature verification is valid, the pre-inspection service system determines whether the decoded motor vehicle inspection data is valid based on the registration information of the motor vehicle manufacturer and its inspection area; When the decoded vehicle inspection data is valid, the pre-inspection service system converts the decoded vehicle inspection data into a pre-defined inspection object, obtains a unique vehicle announcement object based on the vehicle model and announcement batch in the inspection object, and compares the inspection object and the vehicle announcement object from multiple perspectives. If the object to be inspected is the same as the object to be announced for motor vehicles, the pre-inspection service system queries the certificate of conformity corresponding to the motor vehicle based on the certificate of conformity number in the decoded motor vehicle inspection data, and compares the decoded motor vehicle inspection data with the certificate of conformity. If the decoded vehicle inspection data matches the certificate of conformity, the decoded vehicle inspection data is saved to the database. This also includes: When the decoded digital signature verification is valid, the pre-inspection service system determines whether the number of times the motor vehicle manufacturer uploads and writes within a unit of time exceeds the prescribed value; If the value is not exceeded, the pre-inspection service system determines whether the decoded vehicle inspection data meets the conditions. The detailed steps are as follows: a1: Query the registration information of the motor vehicle manufacturer based on the interface serial number in the inspection data to determine whether the current motor vehicle manufacturer is registered; If it is not in the filing information, skip directly and no further action is required; If it is in the filing information, then proceed to step a2; a2: Determine whether the current motor vehicle manufacturer has the relevant interface permissions; If it is not in the interface permission list, skip directly and do not need to perform subsequent steps; If it is in the interface permission list, then proceed to step a3; a3: Determine if the requested server address is in the address registration list; If your address is not on the address registration list, skip this step and do not proceed. If the address is in the registration list, proceed to step a4; a4: Determine if the request time is within the filing period; If it is outside the filing period, skip directly and do not need to perform the following steps; If it is within the filing period, proceed to step a5; a5: Determine whether the inspection area in the inspection data is in the inspection area filing list; If it is not on the inspection area's registration list, skip directly and do not need to perform the following steps; If it is in the inspection area's registration list, proceed to step a6; a6: Determine whether the motor vehicle manufacturer in the inspection data is in the write permission list of the inspection area; If it is not in the write permission list of the inspection area, skip directly and do not need to perform subsequent steps; If it is in the write permission list of the inspection area, then proceed to step a7; a7: Query the database based on the interface serial number in the inspection data, obtain the registered digital certificate root certificate, and verify the vehicle identification number imprint PDF file. If the signature verification fails, skip directly and do not need to perform the following steps; If the verification is successful, the object being inspected will be compared with the object in the vehicle announcement from multiple perspectives. The step of comparing the inspection target and the vehicle announcement target from multiple perspectives also includes: b1: Determine whether the manufacturer's name, gross weight, track width, wheelbase, number of axles, tire specifications, engine displacement, overall dimensions, environmental compliance status, engine model, fuel type, steering type, and vehicle type in the inspection data are consistent with the motor vehicle announcement object; If any data item is inconsistent, skip it and do not proceed with the next step. If all data content is consistent, proceed to step b2; b2: If the inspected vehicle is a new energy vehicle, it shall be compared with the new energy vehicle category of the vehicle announcement object; If the types of new energy sources are inconsistent, skip this step and do not need to proceed. If the types of new energy sources are the same, proceed to step b3; b3: If the production cessation date in the motor vehicle announcement is not empty, then determine the relationship between the current date and the production cessation date; If the current date is later than the production stop date, skip this step and do not proceed. If the current date is not greater than the production stop date, the pre-inspection service system queries the corresponding certificate of conformity for the motor vehicle based on the certificate of conformity number in the decoded motor vehicle inspection data.

2. The method for realizing the convergence and fusion of motor vehicle pre-inspection data according to claim 1, characterized in that, The registration information of the motor vehicle manufacturers includes the unified social credit code, the expiration date of the unified social credit code, the postal code, the manufacturer's address, the manufacturer's contact information, the name of the legal representative, the contact information of the legal representative, the expiration date of access, the allowed IP address, a photo of the business license, a photo of the legal representative's ID card, a digital certificate, and the associated inspection area; the registration information of the inspection area includes the inspection area code, the inspection area name, the name of the company to which it belongs, the city where it is located, the contact person, the contact number, the detailed address, the postal code, the brand and model of the vehicles produced.

3. The method for realizing the convergence and fusion of motor vehicle pre-inspection data according to claim 1, characterized in that, Step S3 further includes: The inspection area inspects each vehicle coming off the production line to determine its type, model, body color, approved passenger capacity, vehicle identification number, engine number, vehicle appearance and tire condition. It also generates PDF files containing photos of the vehicle from the left front 45 degrees, the right rear 45 degrees, the front of the vehicle, the rear of the vehicle, and a vehicle identification number imprint, in order to generate vehicle inspection data.

4. The method for realizing the convergence and fusion of motor vehicle pre-inspection data according to claim 1, characterized in that, The pre-inspection service system, based on the certificate number in the decoded vehicle inspection data, queries the corresponding certificate object for the vehicle and also includes: If no certificate of conformity is obtained, skip this step and do not proceed. If a certificate of conformity is obtained, the decoded vehicle inspection data and the certificate of conformity are compared.

5. The method for realizing the convergence and fusion of motor vehicle pre-inspection data according to claim 4, characterized in that, The step of comparing the decoded vehicle inspection data with the certificate of conformity also includes: c1: Determine whether the certificate of conformity being checked is valid; If the certificate of conformity is invalid, skip this step and do not proceed. If the certificate of conformity is valid, proceed to step c2; c2: Determine whether the vehicle identification number, vehicle brand, vehicle model, manufacturing date, vehicle manufacturer name, engine number, engine model, chassis certificate number, and body color in the inspection data are consistent with the certificate of conformity. If any data item is inconsistent, skip it and do not proceed with the next step. If all the information is consistent, the decoded vehicle inspection data will be saved to the database.

6. A system for implementing the convergence and fusion of motor vehicle pre-inspection data, used to implement the method for implementing the convergence and fusion of motor vehicle pre-inspection data as described in any one of claims 1-5, characterized in that, The system for integrating and aggregating motor vehicle pre-inspection data includes: The registration module is used to register all motor vehicle manufacturers and their inspection areas that have accessed the pre-inspection service system; The allocation module is used by the pre-verification service system to allocate interface serial numbers, public and private keys and access time limits to the connected motor vehicle manufacturers, and to register the digital certificate root certificate of the motor vehicle manufacturers. The association module is used to associate the motor vehicle manufacturers with the inspection areas, and allows the motor vehicle manufacturers to upload motor vehicle data inspected in their associated inspection areas; The encoding module is used by the motor vehicle manufacturer to convert the motor vehicle data inspected in the associated inspection area into a preset string format, sign the string using the private key allocated in step S2, encode the obtained digital signature and motor vehicle inspection data, and finally upload the encoded data to the pre-inspection service system. The verification module is used by the pre-inspection service system to decode the received encoded data, verify the decoded digital signature using the public key allocated in step S2, and verify the legality and authorization of the decoded motor vehicle inspection data based on the registration information of the motor vehicle manufacturer and its inspection area. The processing module is used by the pre-inspection service system to perform announcement comparison, certificate comparison and data aggregation processing on the decoded motor vehicle inspection data.

7. The system for realizing the convergence and fusion of motor vehicle pre-inspection data according to claim 6, characterized in that, The registration information of the motor vehicle manufacturers includes the unified social credit code, the expiration date of the unified social credit code, the postal code, the manufacturer's address, the manufacturer's contact information, the name of the legal representative, the contact information of the legal representative, the expiration date of access, the allowed IP address, a photo of the business license, a photo of the legal representative's ID card, a digital certificate, and the associated inspection area; the registration information of the inspection area includes the inspection area code, the inspection area name, the name of the company to which it belongs, the city where it is located, the contact person, the contact number, the detailed address, the postal code, the brand and model of the vehicles produced.

Images