Vehicle canning system, method, vehicle and storage medium

Abstract

The application provides a vehicle canning system, method, vehicle and storage medium, the system comprises: a vehicle management platform, an information integration platform and a flashing platform; the vehicle management platform is used for generating a corresponding target vehicle identifier for a target vehicle when the target vehicle is produced, and matching a target vehicle code and a target sales area corresponding to the target vehicle identifier from a pre-stored correspondence relationship among vehicle identifiers, vehicle codes and sales areas; the information integration platform is used for obtaining a target binding relationship of a target device identifier, target certificate data and target key data corresponding to the target vehicle code from the target sales area, and sending the target binding relationship to the vehicle management platform; and the flashing platform is used for obtaining the target device identifier, the target certificate data and the target key data corresponding to the target binding relationship based on the target vehicle identifier when the target vehicle is flashed, so as to fill the target vehicle.

Description

Technical Field

[0001] This application relates to the field of vehicle data canning technology, specifically to a vehicle canning system, method, vehicle, and storage medium. Background Technology

[0002] The relevant technology sends a certificate application to the relevant data system through a flashing device. After receiving the certificate data, the flashing device flashes the data into the device. This can lead to a high installation error rate for vehicle manufacturers when the same car model needs to be sold to multiple regions. Summary of the Invention

[0003] This application provides a vehicle filling system, method, vehicle, and storage medium that can reduce filling error rates and vehicle assembly error rates.

[0004] The technical solution of this application embodiment is implemented as follows: This application provides a vehicle filling system, which includes: a vehicle management platform, an information integration platform, and a data processing platform; wherein... The vehicle management platform is used to generate a corresponding target vehicle identifier for the target vehicle when the target vehicle is produced, and based on the target vehicle identifier, match the target vehicle code and target sales region corresponding to the target vehicle identifier from the pre-stored correspondence between vehicle identifier, vehicle code and sales region; and send the target vehicle code and target sales region to the information integration platform. The information integration platform is used to obtain the target binding relationship of target device identifier, target certificate data, and target key data corresponding to the target vehicle code from the target sales area, and send the target binding relationship to the vehicle management platform. The flashing platform is used to read the target vehicle identifier of the target vehicle through the flashing device when the target vehicle is being flashed, and to obtain the target device identifier, target certificate data and target key data corresponding to the target binding relationship from the vehicle management platform based on the target vehicle identifier, so as to flash the target vehicle.

[0005] In this embodiment, the vehicle management platform matches the target vehicle identifier with the target vehicle code and the target sales region, and sends the target vehicle code and target sales region to the information integration platform. The information integration platform obtains the target binding relationship of the corresponding target device identifier, target certificate data, and target key data from the target sales region based on the target vehicle code, and sends it to the vehicle management platform. Thus, the vehicle management platform can establish the correspondence between the target vehicle identifier, target device identifier, target certificate data, and target key data. In this way, when filling and installing on the target vehicle, filling can be performed based on the corresponding target device identifier, target certificate data, and target key data, which can reduce the filling error rate. When installing at the vehicle manufacturer, the corresponding target vehicle identifier can be determined based on the filled target device identifier, thereby reducing the vehicle manufacturer's installation error rate.

[0006] Furthermore, the system also includes a data management platform; The information integration platform is used to determine the sales region corresponding to each vehicle based on the sales information of multiple vehicles, and to send a data request to the data management platform. The data management platform is used to generate device identifiers, certificate data, and key data for each sales region in response to data request requests, as well as the binding relationship between the device identifiers, certificate data, and key data, and then send the binding relationship between the device identifiers, certificate data, and key data to the information integration platform.

[0007] Based on the above technical means, the sales area corresponding to each vehicle can be determined through the information integration platform, and the binding relationship of the device identifier, certificate data and key data corresponding to each sales area can be obtained from the data management platform. This can avoid the problem of low filling efficiency caused by network latency and other reasons.

[0008] Furthermore, the flashing platform is also used to match the target device identifier, target certificate data, and target key data with the built-in regional parameters and device private key to obtain a first matching result; if the first matching result indicates that the matching is successful, a target verification value is calculated based on the target certificate data and target key data; if the target verification value is the same as the preset verification value, the target vehicle is determined to have been successfully flashed.

[0009] Based on the above technical means, the correctness of vehicle filling is verified by matching and verifying the built-in regional parameters and device private key, ensuring that the data is completely written to the vehicle.

[0010] Furthermore, the flashing platform is also used to match the target device identifier, target certificate data, and target key data with the regional parameters to obtain a second matching result; if the second matching result indicates that the target device identifier, target certificate data, and target key data are passed, the platform will match the target device identifier, target certificate data, and target key data with the device private key to obtain a first matching result.

[0011] Based on the above technical means, by matching the regional parameters and the device private key in sequence, dual constraints on the legality of the device and the sales location can be achieved, avoiding cross-regional security data mismatch filling.

[0012] Furthermore, the system also includes an alarm and problem handling platform; The alarm and problem handling platform is used to determine the anomaly level based on the anomaly information when an anomaly occurs, and to determine the corresponding handling strategy based on the anomaly level; the anomaly information includes at least one of the following: unable to obtain the target device identifier, target certificate data, and target key data; target vehicle filling failure; the handling strategy includes at least one of the following: timed reminder to retry; push the anomaly information to the responsible personnel.

[0013] Based on the above technical means, by identifying anomalies through the alarm and problem handling platform and determining different handling strategies based on the anomaly level, the goal of precise handling can be achieved and the efficiency of anomaly handling can be improved.

[0014] Furthermore, the system also includes a front-end platform; The vehicle management platform is also used to send the target vehicle code to the front-end platform; The front-end platform is used to determine the production testing condition corresponding to the target vehicle based on the target vehicle code and the sending time; the production testing condition is either a production condition or a testing condition; if the production testing condition is a production condition, it sends a data request to the information integration platform corresponding to the production condition; if the production testing condition is a testing condition, it sends a data request to the information integration platform corresponding to the testing condition.

[0015] Based on the above technical means, by distinguishing between production and testing conditions through the front-end platform, the production and testing environments can be differentiated without the OEM's awareness. This allows data request to be sent to the information integration platform corresponding to either the production or testing conditions, thus achieving the isolation of test safety data from mass production safety data. This prevents test key data and test certificate data from being mistakenly flashed into mass production vehicles, which could cause overseas use certification failures.

[0016] Furthermore, the front-end platform is also used to configure a corresponding vehicle code for each vehicle based on the sales information of multiple vehicles and record the configuration time; if the target vehicle code is successfully configured and the sending time is less than the configuration time, the production test condition is determined to be the test condition; if the target vehicle code configuration fails, the production test condition is determined to be the production condition.

[0017] Based on the above technical means, a method for determining production and testing conditions is proposed by first configuring a corresponding vehicle code for each vehicle and then distinguishing between production and testing conditions based on the configuration of the vehicle codes.

[0018] Furthermore, the target certificate data and target key data include at least one or more of the following: target certificate, target certificate identifier, target key, target key identifier, target certificate verification value, and target key verification value.

[0019] Based on the above technical means, by carrying identifiers and verification values, it supports lightweight data interaction, fast retrieval and data integrity verification, optimizes cross-border communication efficiency, prevents the risk of data damage and tampering, and facilitates operation and maintenance traceability.

[0020] This application provides a vehicle filling method, the method comprising: When a target vehicle is produced, a corresponding target vehicle identifier is generated for the target vehicle through the vehicle management platform. Based on the target vehicle identifier, the target vehicle code and target sales region corresponding to the target vehicle identifier are matched from the pre-stored correspondence between vehicle identifier, vehicle code and sales region. The information integration platform is used to obtain the target binding relationship between the target device identifier, target certificate data, and target key data corresponding to the target vehicle code from the target sales area. When the target vehicle is being flashed, the flashing device in the flashing platform reads the target vehicle identifier and, based on the target vehicle identifier, retrieves the target device identifier, target certificate data, and target key data corresponding to the target binding relationship from the vehicle management platform to flash the target vehicle.

[0021] This application provides a vehicle, which includes at least a vehicle controller. The vehicle controller stores a computer program or instructions, and when the computer program or instructions are executed by the vehicle controller, the above-described method is implemented.

[0022] This application provides a computer-readable storage medium storing a computer program or computer-executable instructions for implementing the above-described method when executed by a processor.

[0023] This application provides a computer program product, including a computer program or computer executable instructions, which, when executed by a processor, implement the above-described method.

[0024] In this embodiment, the vehicle management platform matches the target vehicle identifier with the target vehicle code and the target sales region, and sends the target vehicle code and target sales region to the information integration platform. The information integration platform obtains the target binding relationship of the corresponding target device identifier, target certificate data, and target key data from the target sales region based on the target vehicle code, and sends it to the vehicle management platform. Thus, the vehicle management platform can establish the correspondence between the target vehicle identifier, target device identifier, target certificate data, and target key data. In this way, when filling and installing on the target vehicle, filling can be performed based on the corresponding target device identifier, target certificate data, and target key data, which can reduce the filling error rate. When installing at the vehicle manufacturer, the corresponding target vehicle identifier can be determined based on the filled target device identifier, thereby reducing the vehicle manufacturer's installation error rate. Attached Figure Description

[0025] Figure 1 This is a schematic diagram of a vehicle filling system provided in an embodiment of this application; Figure 2 This is a flowchart illustrating the steps of a vehicle filling method provided in an embodiment of this application; Figure 3 This is a flowchart of the steps of a data writing method provided by a related technology. Figure 4 This is a flowchart of a data writing method provided by related technology 2; Figure 5 This is a schematic diagram of another vehicle filling system provided in an embodiment of this application; Figure 6 This is a flowchart of another vehicle filling method provided in an embodiment of this application; Figure 7 This is a schematic diagram of a vehicle assembly provided in an embodiment of this application. Detailed Implementation

[0026] To gain a more detailed understanding of the features and technical content of the embodiments of this application, the implementation of the embodiments of this application will be described in detail below with reference to the accompanying drawings. The accompanying drawings are for reference only and are not intended to limit the embodiments of this application.

[0027] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing the embodiments only and is not intended to limit the scope of this application.

[0028] In the following description, references to "some embodiments," "this embodiment," "this embodiment," and examples, etc., describe a subset of all possible embodiments. However, it is understood that "some embodiments" may be the same subset or different subset of all possible embodiments and may be combined with each other without conflict.

[0029] If similar descriptions such as "first / second" appear in the application documents, the following explanation shall be added: In the following description, the terms "first / second / third" are used only to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first / second / third" may be interchanged in a specific order or sequence where permitted, so that the embodiments described herein can be implemented in an order other than that illustrated or described herein.

[0030] In this embodiment, the term "and / or" is merely a description of the relationship between related objects, indicating that there can be three relationships. For example, object A and / or object B can represent three situations: object A exists alone, object A and object B exist simultaneously, and object B exists alone.

[0031] Figure 1 This application provides a vehicle filling system, see [link to relevant documentation]. Figure 1 The vehicle filling system 10 includes: a vehicle management platform 101, an information integration platform 102, and a writing platform 103.

[0032] The vehicle management platform is used to generate a corresponding target vehicle identifier for the target vehicle when the target vehicle is produced, and based on the target vehicle identifier, match the target vehicle code and target sales region corresponding to the target vehicle identifier from the pre-stored correspondence between vehicle identifier, vehicle code and sales region; and send the target vehicle code and target sales region to the information integration platform.

[0033] In some embodiments, before vehicle production begins, the vehicle management platform pre-stores vehicle codes, the number of vehicles produced for each vehicle code, factory numbers, sales countries, regions, etc. When vehicle production begins, the vehicle management platform generates vehicle identifiers and matches vehicle codes with sales regions.

[0034] The information integration platform is used to obtain the target binding relationship of target device identifier, target certificate data, and target key data corresponding to the target vehicle code from the target sales area, and send the target binding relationship to the vehicle management platform.

[0035] In some embodiments, when applying for vehicle equipment identification and security data, the vehicle management platform uploads the target vehicle identification, target vehicle code, and target sales region to the information integration platform. The information integration platform retrieves a set of target equipment identification, target certificate data, and target key data from the equipment manufacturer pool corresponding to the sales region, matches the target vehicle code, target equipment identification, target certificate data, and target key data, and stores the matching relationship in the vehicle management platform. Subsequent vehicles retrieve the corresponding equipment identification, certificate data, and key data from the relevant region in sequence for matching.

[0036] In some embodiments, the information integration platform automatically configures equipment manufacturer pools based on sales information of multiple vehicles. For example, if a vehicle model project involves three regions, both domestic and international, and all involve equipment manufacturer A, then the equipment manufacturer pools and the required data types are configured in each of the three regions, and the equipment manufacturer's encryption keys are also configured in the relevant pools.

[0037] In some embodiments, the information integration platform maintains vehicle configuration information across various regions, and this maintenance can be automated. Vehicle codes contain regional information; a one-to-one matching process is required to determine which code should be maintained in which region. The information integration platform establishes a matching relationship between which region and which code, preventing situations where a vehicle intended for sale in region A is mistakenly maintained in region B. Maintaining vehicle configuration data also includes information on the devices included in that configuration, their manufacturers, and their data types.

[0038] In some embodiments, the target certificate data and target key data include at least one or more of the following: target certificate, target certificate identifier, target key, target key identifier, target certificate verification value, and target key verification value.

[0039] In some embodiments, the target device identifier, target certificate data, and target key data include: target device identifier, target device identifier verification value, target certificate, target certificate identifier, target certificate verification value, target key, and target key verification value.

[0040] The flashing platform is used to read the target vehicle identifier of the target vehicle through the flashing device when the target vehicle is being flashed, and to obtain the target device identifier, target certificate data and target key data corresponding to the target binding relationship from the vehicle management platform based on the target vehicle identifier, so as to flash the target vehicle.

[0041] In some embodiments, when filling the target vehicle, the target vehicle carries its own decryption key. When the target vehicle arrives at the factory's writing station, the writing device reads the target vehicle's identifier and transmits it to the vehicle management platform. The vehicle management platform identifies the corresponding target device identifier, target certificate data, and target key data based on the target vehicle identifier, and feeds back the target device identifier, target certificate data, and target key data to the writing device. The writing device then writes the target device identifier, target certificate data, and target key data into the relevant target vehicle device.

[0042] In this embodiment, the vehicle management platform matches the target vehicle identifier with the target vehicle code and the target sales region, and sends the target vehicle code and target sales region to the information integration platform. The information integration platform obtains the target binding relationship of the corresponding target device identifier, target certificate data, and target key data from the target sales region based on the target vehicle code, and sends it to the vehicle management platform. Thus, the vehicle management platform can establish the correspondence between the target vehicle identifier, target device identifier, target certificate data, and target key data. In this way, when filling and installing on the target vehicle, filling can be performed based on the corresponding target device identifier, target certificate data, and target key data, which can reduce the filling error rate. When installing at the vehicle manufacturer, the corresponding target vehicle identifier can be determined based on the filled target device identifier, thereby reducing the vehicle manufacturer's installation error rate.

[0043] In some embodiments, the system also includes a data management platform; The information integration platform is used to determine the sales region corresponding to each vehicle based on the sales information of multiple vehicles, and to send a data request to the data management platform.

[0044] In some embodiments, the information integration platform divides the system into regions, each region is assigned to specific equipment manufacturers and the data types required by those manufacturers. Sufficient data for each data type needs to be requested in advance, and the number of data requests has a relevant threshold. This threshold can be flexibly configured based on the sales situation of the manufactured vehicles. After setting the threshold, the platform requests equipment identification, certificate data, and key data from the data management platform of each region, and sends the equipment manufacturer's encryption key. The requested data is then stored in the storage area of ​​each equipment manufacturer in each region.

[0045] In some embodiments, the information integration platform monitors the quantity of each storage area in real time. When the quantity of data in a storage area is less than the minimum threshold, it immediately pulls data from the relevant area until the quantity reaches the maximum threshold. Or, when the quantity of data has not reached the maximum preset value but is higher than the minimum threshold, it periodically pulls data from the relevant area until the quantity reaches the maximum threshold.

[0046] The data management platform is used to generate device identifiers, certificate data, and key data for each sales region in response to data request requests, as well as the binding relationship between the device identifiers, certificate data, and key data, and then send the binding relationship between the device identifiers, certificate data, and key data to the information integration platform.

[0047] In some embodiments, during the data generation stage of the data management platform, the data management platforms in each region receive data application requests from the information integration platform, generate device identifiers, certificate data, and key data, encrypt the generated sensitive data, such as keys, using the encryption keys of each device manufacturer, bind the relationship between the device identifiers, certificate data, and key data, and feed back the bound device identifiers, certificate data, and key data, as well as the binding relationship between the device identifiers, certificate data, and key data, to the information integration platform.

[0048] Based on the above technical means, the sales area corresponding to each vehicle can be determined through the information integration platform, and the binding relationship of the device identifier, certificate data and key data corresponding to each sales area can be obtained from the data management platform. This can avoid the problem of low filling efficiency caused by network latency and other reasons.

[0049] In some embodiments, the flashing platform is further configured to match the target device identifier, target certificate data, and target key data with the built-in regional parameters and device private key respectively to obtain a first matching result; if the first matching result indicates that the matching is successful, calculate a target verification value based on the target certificate data and target key data; and if the target verification value is the same as the preset verification value, determine that the target vehicle has been successfully flashed.

[0050] In some embodiments, a verification value is calculated for the target certificate data and the target key data, the key is decrypted using a pre-set decryption key, the verification value of the key is calculated, the key is stored in a secure area, and the verification value of the target certificate data and the target key data is fed back to the flashing device; the flashing device receives the verification value returned by the vehicle device and compares the verification value pulled from the vehicle management platform with the verification value returned by the vehicle device to ensure that the data is completely written to the vehicle device.

[0051] In some embodiments, after the data writing is completed and the data verification is successful, the vehicle data, including the target vehicle identifier, target device identifier, target certificate data, and target key data, is uploaded to the vehicle management platform. After all the vehicle data, including the target vehicle identifier, target device identifier, target certificate data, and target key data, is returned to the data management platform, a check mechanism is triggered to read whether the relevant vehicle identifiers match the data on the data management platform. If the data matches, a certificate and key function check is triggered to check whether the functions related to the certificate and key are normal, such as network connectivity and key functionality.

[0052] Based on the above technical means, the correctness of vehicle filling is verified by matching and verifying the built-in regional parameters and device private key, ensuring that the data is completely written to the vehicle.

[0053] In some embodiments, the flashing platform is further configured to match the target device identifier, target certificate data, and target key data with the region parameters to obtain a second matching result; and if the second matching result indicates that the matching is successful, match the target device identifier, target certificate data, and target key data with the device private key to obtain a first matching result.

[0054] In some embodiments, the target device identifier, target certificate data, and target key data are compared with the incoming region parameters to see if they match. If they match, i.e., if the second matching result indicates that the match is successful, the device certificate data and the device private key are verified to see if they match. For example, a piece of inherent data is signed using the private key, and the inherent data is verified using the public key.

[0055] Based on the above technical means, by matching the regional parameters and the device private key in sequence, dual constraints on the legality of the device and the sales location can be achieved, avoiding cross-regional security data mismatch filling.

[0056] In some embodiments, the system also includes an alarm and problem handling platform; The alarm and problem handling platform is used to determine the anomaly level based on the anomaly information when an anomaly occurs, and to determine the corresponding handling strategy based on the anomaly level; the anomaly information includes at least one of the following: unable to obtain the target device identifier, target certificate data, and target key data; target vehicle filling failure; the handling strategy includes at least one of the following: timed reminder to retry; push the anomaly information to the responsible personnel.

[0057] In some embodiments, each platform is equipped with automated alarm software, and all issues are reported and handled by the alarm and problem handling platform. For example, the alarm and problem handling platform can be divided into zones for management.

[0058] The inability to obtain the target device identifier, target certificate data, and target key data can include: failure of the vehicle management platform to retrieve the target device identifier, target certificate data, and target key data in a single attempt; and failure of a retry attempt by the vehicle management platform to retrieve the target device identifier, target certificate data, and target key data in a single attempt. Timed retry reminders can be automatic retries combined with timed reminders, requiring no manual intervention. For example, the alarm and problem handling platform can periodically remind the vehicle management platform to retrieve the target device identifier, target certificate data, and target key data again. In some embodiments, if the vehicle management platform fails to retrieve the target device identifier, target certificate data, and target key data in a single attempt, the alarm and problem handling platform can periodically remind the vehicle management platform to retrieve the target device identifier, target certificate data, and target key data again, without requiring manual intervention.

[0059] The abnormal information includes: failure of three-layer verification for a single vehicle, loss of connection to the data management platform, and failure of batch verification. Pushing abnormal information to responsible personnel includes: pushing to the production line shift leader for real-time handling; pushing to maintenance engineers and production line managers, simultaneously triggering a switch to the backup cache pool, with tiered push and tiered handling, prioritizing major faults that would cause production line downtime. In some embodiments, in the case of failure of three-layer verification for a single vehicle, the information is pushed to the production line shift leader for real-time handling; in the case of loss of connection to the data management platform or failure of batch verification, the information is pushed to maintenance engineers and production line managers, simultaneously triggering a switch to the backup cache pool, with tiered push and tiered handling, prioritizing major faults that would cause production line downtime.

[0060] Based on the above technical means, by identifying anomalies through the alarm and problem handling platform and determining different handling strategies based on the anomaly level, the goal of precise handling can be achieved and the efficiency of anomaly handling can be improved.

[0061] In some embodiments, the system further includes a front-end platform; The vehicle management platform is also used to send the target vehicle code to the front-end platform; The front-end platform is used to determine the production testing condition corresponding to the target vehicle based on the target vehicle code and the sending time; the production testing condition is either a production condition or a testing condition; if the production testing condition is a production condition, it sends a data request to the information integration platform corresponding to the production condition; if the production testing condition is a testing condition, it sends a data request to the information integration platform corresponding to the testing condition.

[0062] In some embodiments, vehicles are divided into testing and production environments. For example, during the vehicle research and development and testing phases, the device identification, certificate data, and key data on the vehicle are required to be data from the testing environment. However, when producing user vehicles, the device identification, certificate data, and key data are data from the production environment. But in a vehicle manufacturing plant, there is no distinction between testing and production environments; the plant only receives vehicle production plans. Therefore, a front-end platform is needed to distinguish between the production and testing environments without the plant's awareness.

[0063] In some embodiments, if the target vehicle is a vehicle in the test environment, the relevant vehicle code and the production cutoff time of the vehicle code need to be configured in advance on the front-end platform so that the vehicle management platform can send a data request from the information integration platform corresponding to the test environment.

[0064] In some embodiments, when configuring vehicle coding in the test environment of the information integration platform, configuration on the front-end platform is triggered simultaneously.

[0065] In some embodiments, when applying for vehicle equipment identification and safety data, the vehicle management platform uploads the target vehicle identification, target vehicle code, and target sales region to the front-end platform. The front-end platform determines whether the vehicle is in production or testing condition, and then sends a data application request to the corresponding information integration platform.

[0066] Based on the above technical means, by distinguishing between production and testing conditions through the front-end platform, the production and testing environments can be differentiated without the OEM's awareness. This allows data request to be sent to the information integration platform corresponding to either the production or testing conditions, thus achieving the isolation of test safety data from mass production safety data. This prevents test key data and test certificate data from being mistakenly flashed into mass production vehicles, which could cause overseas use certification failures.

[0067] In some embodiments, the front-end platform is further configured to configure a corresponding vehicle code for each vehicle based on the sales information of multiple vehicles, and record the configuration time; if the target vehicle code is successfully configured and the sending time is less than the configuration time, the production testing condition is determined to be the test condition; if the target vehicle code configuration fails, the production testing condition is determined to be the production condition.

[0068] In some embodiments, the front-end platform is a platform located between the vehicle management platform and the information integration platform. The vehicle code and related time are configured on the front-end platform according to the vehicle plan. For example, if a certain model is a production test vehicle before time node A, then the vehicle code and time are configured on the front-end platform.

[0069] In some embodiments, when the vehicle management platform requests data, the front-end platform first determines whether the vehicle code is within the list. If it is, it then determines whether the request time is less than the configuration time. If it is, the front-end platform forwards the request to the information integration platform in the test environment. If the vehicle code is not within the list, it defaults to requesting the relevant data from the information integration platform in the production environment. The front-end platform receives data request requests from the vehicle management platform and forwards them to the information integration platform, and also receives data feedback from the information integration platform and forwards it to the vehicle management platform.

[0070] In some embodiments, when the target vehicle coding configuration fails and the operating condition type cannot be automatically identified, the production test condition is determined to be the production condition. If it is determined to be a test condition as a fallback, it is very likely that after mass-produced vehicles obtain device identification, certificate data, and key data from the vehicle management platform and install them into export vehicles, the vehicles will be unable to complete security certification overseas, causing serious quality risks. However, if it is determined to be a production condition, a strict data verification mechanism will be activated. If the verification fails, an alarm will be triggered and the filling process will be blocked to prevent erroneous security data from being written to the vehicle.

[0071] Based on the above technical means, a method for determining production and testing conditions is proposed by first configuring a corresponding vehicle code for each vehicle and then distinguishing between production and testing conditions based on the configuration of the vehicle codes.

[0072] Figure 2 This is a flowchart illustrating the steps of a vehicle filling method provided in an embodiment of this application. See also... Figure 2 The method includes: S201, When producing the target vehicle, a corresponding target vehicle identifier is generated for the target vehicle through the vehicle management platform, and based on the target vehicle identifier, the target vehicle code and target sales region corresponding to the target vehicle identifier are matched from the pre-stored correspondence between vehicle identifier, vehicle code and sales region. S202, through the information integration platform, obtain the target binding relationship of target device identifier, target certificate data, and target key data corresponding to the target vehicle code from the target sales area; S203, when the target vehicle is being flashed, the target vehicle identifier of the target vehicle is read by the flashing device in the flashing platform, and the target device identifier, target certificate data and target key data corresponding to the target binding relationship are obtained from the vehicle management platform based on the target vehicle identifier, so as to flash the target vehicle.

[0073] In some embodiments, the method further includes: S211, through the information integration platform, determines the sales area corresponding to each vehicle based on the sales information of multiple vehicles, and sends a data application request to the data management platform; S212, in response to a data request, generates device identifiers, certificate data, and key data for each sales region through the data management platform, as well as the binding relationship between the device identifiers, certificate data, and key data, and sends the binding relationship between the device identifiers, certificate data, and key data to the information integration platform.

[0074] In some embodiments, the method further includes: S221, the target device identifier, target certificate data, and target key data are matched with the built-in regional parameters and device private key respectively to obtain the first matching result; S222, if the first matching result indicates that the target verification value is passed, calculate the target verification value based on the target certificate data and the target key data; S223, if the target verification value is the same as the preset verification value, it is determined that the target vehicle has been successfully filled.

[0075] In some embodiments, step S221 involves matching the target device identifier, target certificate data, and target key data with the built-in region parameters and device private key to obtain a first matching result, including: S231, Match the target device identifier, target certificate data, and target key data with the area parameters to obtain a second matching result; S232, if the second matching result is successful, the target device identifier, target certificate data, and target key data are matched with the device private key to obtain the first matching result.

[0076] In some embodiments, the method further includes: S241, In the event of an anomaly, determine the anomaly level based on the anomaly information; S242, determine the corresponding handling strategy based on the anomaly level; the anomaly information includes at least one of the following: unable to obtain the target device identifier, target certificate data, and target key data; target vehicle filling failure; the handling strategy includes at least one of the following: timed reminder to retry; push the anomaly information to the responsible personnel.

[0077] In some embodiments, the method further includes: S251, the target vehicle code is sent to the front-end platform through the vehicle management platform; S252, the front-end platform determines the production test condition corresponding to the target vehicle based on the target vehicle code and the sending time; the production test condition is either the production condition or the test condition. S253, when the production test condition is the production condition, sends a data request to the information integration platform corresponding to the production condition. S254, when the production test condition is the test condition, sends a data request to the information integration platform corresponding to the test condition.

[0078] In some embodiments, S252, determining the production testing condition corresponding to the target vehicle through the front-end platform based on the target vehicle code and transmission time, includes: S261, based on the sales information of multiple vehicles, configures a corresponding vehicle code for each vehicle and records the configuration time; S262, if the target vehicle coding is successfully configured and the transmission time is less than the configuration time, the production test condition is determined as the test condition. S263, in the event that the target vehicle coding configuration fails, the production test condition is determined to be the production condition.

[0079] In some embodiments, the target certificate data and target key data include at least one or more of the following: target certificate, target certificate identifier, target key, target key identifier, target certificate verification value, and target key verification value.

[0080] Currently, all car manufacturers are involved in cross-border sales, which basically involves exporting complete vehicles. After producing the vehicles domestically, they sell them overseas. During vehicle production, it is necessary to import information from overseas systems, such as device IDs, certificates, and keys, into the vehicle's equipment to support the normal use of certain functions in overseas markets. Currently, there are two import methods in the industry: one is for equipment manufacturers to apply for data from various overseas systems and import it on the equipment production line, and the other is for the vehicle manufacturer to apply for data from overseas and import it at the vehicle manufacturer's factory.

[0081] One related technology proposes sending a certificate application to the relevant data system via a flashing device. After receiving the certificate data, the flashing device flashes the data into the device. A flowchart of this solution can be found here. Figure 3 ,include: S301, in response to the certificate application confirmation request sent by the flashing device, obtains certificate application information.

[0082] S302, the certificate application information is sent to the flashing device, so that the flashing device can send the certificate application information to the management server, so that the management server can obtain the certificate flashing information based on the certificate application information.

[0083] S303 receives certificate flashing information sent by the flashing device.

[0084] S304 performs the first security authentication on the certificate flashing information.

[0085] S305 performs a flashing action based on certificate flashing information when the first security authentication is successful.

[0086] The relevant technology relies on the status of the equipment. The certificate data needs to be applied for in the region where the equipment is to be sold. If the same car series needs to be sold in multiple regions, it is necessary to add the status of the parts to distinguish different regions and apply for different data. Moreover, for the car manufacturer, cars in different regions are produced together, which can easily lead to the wrong equipment being installed at the car manufacturer.

[0087] Related technology two proposes providing the vehicle's ID to the Telematics Service Provider (TSP) system in advance. The TSP then forwards the certificate request to the Public Key Infrastructure (PKI) system. After generating the certificate, the PKI system sends the data back to the TSP, which in turn sends it back to the factory. A flowchart for this solution can be found here. Figure 4 ,include: S401: When equipment is put into the warehouse in batches, the vehicle ID information is obtained and sent to the TSP platform for storage. S402, Before vehicle assembly, obtain a bulk certificate application request, which includes the ID information of each vehicle; S403 sends a batch certificate application request to the TSP platform so that the TSP platform can interact with the PKI platform to generate a factory certificate for each vehicle when it determines that the batch certificate application request meets the certificate application conditions based on the ID information of each vehicle and the stored vehicle ID information. S404 receives the factory certificate for each vehicle sent by the TSP platform and flashes the factory certificate for each vehicle to the corresponding vehicle through the certificate flashing station.

[0088] The second related technology is only applicable to situations where the factory and the TSP / PKI system are in the same area and the factory's production time is relatively long. This solution cannot meet the needs of scenarios where the factory and the PKI system are in different areas.

[0089] Figure 5 This is a schematic diagram of another vehicle filling system provided in an embodiment of this application. See also... Figure 5 The vehicle filling system includes: equipment, a safety data management system 501, an information integration system 502, a front-end system 503, a vehicle management system 504, a writing device 505, a vehicle 506, an inspection system 507, and an alarm and problem handling system 508. Among these, the equipment and safety data management system are equivalent to the aforementioned data management platform, the information integration system is equivalent to the aforementioned information integration platform, the front-end system is equivalent to the aforementioned front-end platform, the vehicle management system is equivalent to the aforementioned vehicle management platform, and the alarm and problem handling system is equivalent to the aforementioned alarm and problem handling platform. These will be described in detail below.

[0090] The Equipment and Security Data Management System is deployed in different regions. This system has the following functions: equipment management; security data management such as certificates and keys; management of relationships between vehicles, equipment, and security data; receiving device ID, certificate, and key requests from the information integration system. The device ID, certificate, and key data here includes the content of the device ID, certificate, and key themselves, the certificate ID, the key ID, the device ID checksum, the certificate checksum, and the key checksum, which will not be repeated hereafter. Sensitive key data is encrypted throughout the entire process from the Equipment and Security Data Management System to the vehicle equipment to ensure key security. The Equipment and Security Data Management System generates device ID, certificate, and key data, binds the device ID, certificate ID, and key ID, and sends the matched device ID, certificate, and key back to the information integration system; receives vehicle ID, device ID, certificate ID, and key ID information returned from the information integration system, confirms the relationship between the certificate ID, key ID, and device ID, and stores the relevant information upon successful confirmation; receives data verification requests from the information integration platform to verify whether the actual vehicle data matches the cloud data and whether the functions related to certificates and keys are functioning correctly. Device IDs, certificate IDs, and key IDs generated in the equipment and security data management system contain identifiers for region, production, and testing. For example, if a related ID is 6 bytes long, the first byte represents the region, and the second byte represents whether it is for production or testing, etc.

[0091] The information integration system includes management of vehicles, regions, device IDs, certificate IDs, key IDs, device ID verification values, certificate verification values, key verification values, and parts suppliers, including the management of encrypted certificates for parts suppliers. The system manages vehicles and their sales regions, configuring vehicle codes in each region so that the factory can retrieve device IDs, certificates, and keys from different regions. It also manages different regions and device manufacturers by region, with each region having a pre-set configuration. Device IDs, certificates, and keys are requested in advance from the device and security data management systems in different regions and stored to ensure that system failures in relevant regions do not affect the factory's production schedule. The system receives device ID, certificate, and key requests from the front-end system, matches the data with the corresponding device manufacturer in the relevant region, and sends it to the vehicle's front-end system. It receives vehicle data returned from the front-end system and distributes it to the relevant regions. It receives data verification requests from vehicles and forwards them to the device and data security management system. The system manages device manufacturers and their encryption keys. Here, the encryption keys are asymmetric public keys or public key certificates. When requesting sensitive data such as private keys or symmetric keys from the device manufacturer's pool, the device and security data management system uses the device manufacturer's encryption key to encrypt the sensitive data before transmission.

[0092] The front-end system is crucial because vehicles are divided into testing and production environments. For example, during vehicle R&D and testing, the device IDs, certificates, and keys on the vehicle must be data from the testing environment. When producing user vehicles, these same data are used for the production environment. However, vehicle manufacturing plants don't differentiate between testing and production environments; they simply receive production plans. Therefore, a system is needed to distinguish between the production and testing environments without the factory's awareness. The front-end system serves this purpose. It sits between the vehicle management system and the information integration system. Based on the vehicle plan, the front-end system configures the vehicle code and related times. For instance, if a certain vehicle model is a production test vehicle before time point A, its vehicle code and time are configured on the front-end system. When the vehicle management system requests data, the front-end system first checks if the vehicle code is in the list. If it is, it checks if the request time is less than the configured time. If it is, the front-end system forwards the request to the testing environment's information integration system. If the vehicle model code is not in the list, it defaults to requesting the relevant data from the production environment's information integration system. The front-end system receives data request applications from the vehicle management system and forwards them to the information integration system, and also receives data feedback from the information integration system and forwards it to the vehicle management system.

[0093] The vehicle management system manages data on factory vehicles, such as vehicle ID, vehicle code, sales region, and production plant information. It generates and manages vehicle IDs; matches vehicle sales regions and vehicle codes; integrates vehicle ID, vehicle code, and sales region information with the system to apply for device IDs, certificates, and key data; stores vehicle IDs, device IDs, certificates, keys, device ID verification values, certificate verifications, and key verification data; receives requests to retrieve device IDs, certificates, and keys from the flashing device and distributes the relevant data; if data retrieval fails, it transmits the relevant information to the alarm system and continues to retrieve data, issuing periodic alarms for early warning.

[0094] The system flashes the device, reads the vehicle ID, and uploads the vehicle ID to the vehicle management system, requesting data such as device ID, certificate, key, certificate verification, key verification, and region. After retrieving the data, it loads the data into the device. It receives the verification value returned by the vehicle device and compares the verification value retrieved from the vehicle management system with the verification value returned by the vehicle device to ensure that the data is completely written to the vehicle device. After the data flashing is completed and the data verification is successful, the system uploads the entire vehicle's data, including vehicle ID, certificate ID, device ID, and region information, to the vehicle management system.

[0095] The vehicle equipment receives data from the flashing device. After receiving the data, it performs the following operations: compares whether the key ID, certificate ID, device-related area fields and the input area match. If they match, it verifies the data written to the disk. The first step is to verify whether the device certificate and the device private key match. The second step is to calculate the verification value for the data written to the disk (certificate and key) and feed the verification value back to the flashing device.

[0096] The inspection system, after all the vehicle data, including vehicle ID, certificate ID, device ID, region, and other information, is sent back to the security and data management system, triggers an inspection mechanism to read whether the relevant vehicle ID matches the data in the security and data management system. If the data matches, it triggers a certificate and key function check to check whether the functions related to certificates and keys are normal.

[0097] The alarm and problem handling system is configured with a relevant problem database, which includes a known problem database and an unknown problem database. If the problem is in the known problem database, an automatic problem-solving program can be triggered to resolve the relevant problem automatically. If the problem is unknown, the relevant problem will be notified to the relevant professionals through the alarm service for handling. After the unknown problem is resolved, the solution path and solution will be provided to the known problem database, and this process will continue.

[0098] In this embodiment, the problems of needing to add equipment status application certificates and key data can be solved, the problems of incorrect IDs, certificates and keys of canning equipment in different regions of vehicle sales can be solved, the problems of production line shutdown due to poor network can be avoided, the problems of secure transmission of sensitive data can be solved, and the problems of vehicle manufacturers not being able to distinguish between testing and production environments can be solved.

[0099] The embodiments of this application are divided into four major processes: preparation work before data application, data application for information integration system, vehicle data application and filling process, and data verification process.

[0100] The preparation work before data application involves automatically configuring equipment manufacturer pools in the relevant areas of the information integration system based on the data from the order system. For example, if a vehicle model project involves three regions, both domestic and international, and all involve equipment manufacturer A, then equipment manufacturer pools and the data types to be applied for are configured in each of the three regions. Simultaneously, the equipment manufacturer's encryption key is configured in the relevant pool. Each pool can initially have an initial pre-application quantity S1.

[0101] The data application stage of the information integration system involves two steps: applying for data through the information integration system and generating data through the equipment and security data management system.

[0102] During the data application phase of the information integration system, the system is divided into regions. Each region is assigned to specific equipment manufacturers and the data types they require. Sufficient data for each data type needs to be applied for in advance, with a threshold for the amount of data requested. This threshold can be flexibly configured based on vehicle sales. After setting the threshold, the system requests equipment IDs, certificates, and key data from the equipment and security data management systems in each region, along with the equipment manufacturers' encryption keys. This data is then stored in the respective storage areas of each equipment manufacturer within each region. The system monitors the data quantity in each storage area in real time. When the data quantity in a storage area falls below the minimum threshold, it immediately retrieves data from the relevant areas until the quantity reaches the maximum threshold. Alternatively, if the data quantity is below the maximum preset threshold but above the minimum threshold, the system periodically retrieves data from the relevant areas until the maximum threshold is reached.

[0103] During the data generation phase of the equipment and security data management system, each region's equipment and security data management system receives data request requests from the information integration system, generates equipment ID, certificate, key, equipment ID verification value, certificate verification value, and key verification value, encrypts the generated sensitive data such as the key using the encryption keys of each equipment manufacturer, binds the relationship between equipment ID, certificate, and key, and feeds back the bound data and data binding relationship to the information integration system.

[0104] The vehicle data application and filling process consists of five steps: vehicle configuration data maintenance, vehicle environment maintenance, factory vehicle data generation, vehicle equipment ID and safety data application, and vehicle data filling.

[0105] Vehicle configuration data maintenance involves updating vehicle configuration information across different regions. This maintenance can be automated. Each vehicle's code contains region information, and a one-to-one match is required to determine which code should be updated to which region. The information integration system establishes a matching relationship between regions, preventing situations where a vehicle intended for sale in region A is incorrectly updated to region B. Errors are reported directly for incorrect code matching or missing codes. Maintaining vehicle configuration data also includes updating information on the devices included in that configuration, their manufacturers, and data types.

[0106] For vehicle environment maintenance, if the vehicle model is a test environment vehicle, the relevant vehicle code and its production expiration time need to be configured in the front-end system in advance to facilitate the vehicle management system in retrieving test environment data. To avoid omissions, configuring the vehicle code in the test environment of the information integration system will simultaneously trigger the configuration on the front-end system.

[0107] Before vehicle production begins, the vehicle management system stores the number of vehicles to be produced, vehicle codes, the number of vehicles produced for each vehicle code, factory number, and country and region of sale. At the start of vehicle production, the vehicle management system generates vehicle IDs and matches them with the vehicle ID, vehicle code, and country of sale.

[0108] When requesting vehicle device IDs and security data, the vehicle management system uploads the vehicle ID, vehicle code, and country of sale information to the front-end system. The front-end system determines whether the vehicle is in a test or production environment and then sends a data request to the information integration system for the corresponding environment. The information integration system determines the region based on the vehicle code and retrieves a set of device IDs, certificates, keys, device ID verification values, certificate verification values, and key verification values ​​from the corresponding device manufacturer pool. It then matches the VIN, device ID, certificate ID, and key ID and stores the matching relationship in the vehicle management system. Subsequent vehicles retrieve device IDs, certificates, and keys sequentially from the relevant region for matching. If the vehicle management system fails to retrieve the relevant device ID, certificate, and key data, it will report an error message to the alarm and problem handling system for timely resolution of related issues.

[0109] During the vehicle data loading stage, the equipment in each vehicle carries its own decryption key. When a vehicle arrives at the factory's data writing station, the writing device reads the vehicle ID and transmits it to the vehicle management system. The vehicle management system identifies the corresponding device ID, certificate, key, device ID checksum, certificate checksum, key checksum, region, etc., based on the vehicle ID and feeds this data back to the writing device. The writing device then writes the data into the relevant vehicle equipment. After receiving the data, the vehicle equipment verifies and securely stores the relevant information.

[0110] The data verification process is as follows: After receiving relevant data from the flashing device, the vehicle equipment first compares the key ID, certificate ID, device-related area fields, and input area parameters for a match. If a match is found, the data is verified. The second step verifies the device's certificate and private key. For example, if a piece of proprietary data is signed using the private key, the signature is verified using the public key. The third step calculates the verification value for the data (certificate and key), decrypts the key using a pre-set decryption key, calculates the key's verification value, stores the key in a secure area, and sends the certificate and key verification values ​​back to the flashing device. The flashing device receives the verification value returned by the vehicle equipment and... The verification value retrieved from the vehicle management system is compared with the verification value returned by the vehicle device to ensure that the data is completely written to the vehicle device. After the data writing is completed and the data verification is successful, the vehicle data, including vehicle ID, certificate ID, device ID, region, and other information, is uploaded to the vehicle management system. After the vehicle data, including vehicle ID, certificate ID, device ID, region, and other information, is sent back to the security and data management system, a check mechanism is triggered to read whether the relevant IDs of the vehicle match the data in the security and data management system. If the data matches, a certificate and key function check is triggered to check whether the functions related to certificates and keys are normal, such as network function and key function.

[0111] Throughout the process, each system is equipped with automated alarm software. Problems at all stages are reported and handled by the alarm and problem-solving system, which manages each system by region. Alarms are categorized into several levels for differentiated handling. For example, Level 1 (low risk): If the vehicle management system fails to retrieve filling data for a single time, the system automatically retryes and sends a timed reminder, requiring no manual intervention. Level 2 (medium risk): If a single vehicle fails the three-layer verification, the alert is sent to the production line team leader for real-time handling. Level 3 (emergency) (production stoppage risk): If the regional security system loses connection or batch verification fails, the alert is sent to the operations engineer and production line manager, simultaneously triggering a switch to the backup cache pool. This tiered approach prioritizes critical faults that could lead to production stoppages. Alarms proactively address problems, while the processing system efficiently resolves them directly.

[0112] In this security design for this implementation case, sensitive data such as key data is encrypted throughout its generation, transmission, and storage, eliminating the risk of key leakage. Furthermore, each device manufacturer uses unique encryption and decryption keys, known only to the manufacturer. Therefore, the leakage of one decryption key does not lead to the leakage of all keys. Components are generated within the device and security data management system, and encryption occurs during generation. From the device, security data management system, information integration system, front-end system, vehicle management system, to the flashing device, the entire data chain is encrypted, with no plaintext appearing in between. Data decryption and verification calculations within the device are also performed within a secure area, effectively preventing the leakage of sensitive data.

[0113] Figure 6 This is a flowchart of another vehicle filling method provided in this application embodiment, see below. Figure 6 Specifically, it can include: S601, the information integration system divides regions, identifies equipment manufacturers in each region and configures corresponding encryption keys, and applies for device ID, certificate, key, device ID verification value, certificate verification value, and key verification value from each region's equipment and security data management system. If there are no problems, proceed to the next step; if there are problems, report the relevant issues to the alarm and problem handling system.

[0114] S602, the device and security data management system generates device ID, certificate, and key data and feeds them back to the information integration system. If there are no problems, proceed to the next step; if there are problems, report the relevant issues to the alarm and problem handling system.

[0115] S603: Configure vehicle configuration data in the information integration system. If there are no problems, proceed to the next step. If there are problems, report the relevant issues to the alarm and problem handling system.

[0116] S604: Configure the vehicle code and production time of the test vehicle in the front-end system. If it is a production environment vehicle, no configuration is required.

[0117] S605: During vehicle production, the vehicle management system generates a vehicle ID. The system matches the vehicle ID, vehicle code, and country of sale. If there are no issues, the system proceeds to the next step. If there are issues, the relevant issues are reported to the alarm and problem handling system.

[0118] S606, the vehicle management system integrates the vehicle ID, vehicle code, and country of sale information into the system. If there are no problems, proceed to the next step; if there are problems, report the relevant issues to the alarm and problem handling system.

[0119] S607, the information integration system retrieves the device ID, certificate, key, device ID verification value, certificate verification value, and key verification value of the corresponding region based on the vehicle code, and feeds the relevant data back to the vehicle management system. If there are no problems, proceed to the next step; if there are problems, report the relevant issues to the alarm and problem handling system.

[0120] S608 When a vehicle arrives at the factory's flashing station, the flashing device reads the vehicle ID and retrieves the device ID, certificate, key, device ID verification value, certificate verification value, and key verification value data from the vehicle management system. It then loads the device ID, certificate, and key data into the vehicle's device. If there are no problems, it proceeds to the next step. If there are problems, it sends the relevant issues to the alarm and problem handling system.

[0121] S609: The vehicle equipment verifies the received data, checks the matching relationship between the certificate and the private key, calculates the verification value of the data after the data is written to the disk, and feeds back the verification value to the flashing device. If there is no problem, proceed to the next step; if there is a problem, report the relevant problem to the alarm and problem handling system.

[0122] S610: The flashing device compares the verification value returned by the vehicle device with the verification value retrieved from the vehicle management system. If there are no problems, proceed to the next step; if there are problems, report the relevant issues to the alarm and problem handling system.

[0123] S611 After the flashing device verification is successful, the vehicle data is uploaded to the information integration platform. The information integration platform distributes the relevant information to each device and the safety data management system. If there are no problems, proceed to the next step. If there are problems, report the relevant issues to the alarm and problem handling system.

[0124] S612, the system checks the vehicle device ID, certificate ID, key ID and the device and security data management system's check function, triggering certificate and key-related function checks. If there are no problems, the check passes; if there are problems, the relevant issues are reported to the alarm and problem handling system.

[0125] This application also provides a vehicle. Figure 7 This is a schematic diagram of a vehicle assembly provided in an embodiment of this application, such as... Figure 7 As shown, the vehicle 70 includes a vehicle controller 701, which stores computer programs or instructions. When the computer programs or instructions are executed by the vehicle controller 701, the method steps in the aforementioned embodiments are performed.

[0126] In practical applications, the aforementioned vehicle controller can be at least one of the following: Application-Specific Integrated Circuit (ASIC), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field-Programmable Gate Array (FPGA), controller, microcontroller, or micro-vehicle controller. It is understood that, for different devices, the electronic components used to implement the functions of the aforementioned vehicle controller can also be other types, and this application does not specifically limit the specific implementation.

[0127] The aforementioned memory can be volatile memory, such as random-access memory (RAM); or non-volatile memory, such as read-only memory (ROM), flash memory, hard disk drive (HDD), or solid-state drive (SSD); or a combination of the above types of memory, providing instructions and data to the processor.

[0128] In an exemplary embodiment, this application also provides a computer-readable storage medium for storing a computer program.

[0129] Optionally, the computer-readable storage medium can be applied to any of the methods in the embodiments of this application, and the computer program causes the computer to execute the corresponding processes implemented by the processor in the various methods of the embodiments of this application. For the sake of brevity, it will not be described in detail here.

[0130] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components can be combined, or integrated into another system, or some features can be ignored or not executed. In addition, the coupling, direct coupling, or communication connection between the various components shown or discussed can be through some interfaces, and the indirect coupling or communication connection between devices or units can be electrical, mechanical, or other forms.

[0131] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0132] Furthermore, in the various embodiments of this application, all functional units can be integrated into one processing module, or each unit can be a separate unit, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units. Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0133] The methods disclosed in the several method embodiments provided in this application can be arbitrarily combined without conflict to obtain new method embodiments.

[0134] The features disclosed in the several product embodiments provided in this application can be arbitrarily combined without conflict to obtain new product embodiments.

[0135] The features disclosed in the several method or device embodiments provided in this application can be arbitrarily combined without conflict to obtain new method or device embodiments.

[0136] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A vehicle filling system, characterized in that, The system includes: a vehicle management platform, an information integration platform, and a flashing platform; wherein... The vehicle management platform is used to generate a corresponding target vehicle identifier for the target vehicle when the target vehicle is produced, and based on the target vehicle identifier, match the target vehicle code and target sales region corresponding to the target vehicle identifier from the pre-stored correspondence between vehicle identifiers, vehicle codes, and sales regions; and send the target vehicle code and target sales region to the information integration platform. The information integration platform is used to obtain the target binding relationship of target device identifier, target certificate data, and target key data corresponding to the target vehicle code from the target sales area, and send the target binding relationship to the vehicle management platform. The flashing platform is used to read the target vehicle identifier of the target vehicle through the flashing device when the target vehicle is flashed, and obtain the target device identifier, the target certificate data and the target key data corresponding to the target binding relationship from the vehicle management platform based on the target vehicle identifier, so as to flash the target vehicle.

2. The system according to claim 1, characterized in that, The system also includes a data management platform; The information integration platform is used to determine the sales region corresponding to each vehicle based on the sales information of multiple vehicles, and to send a data application request to the data management platform. The data management platform is used to, in response to the data request, generate device identifier, certificate data, key data, and binding relationship between the device identifier, certificate data, and key data for each sales region, and send the binding relationship between the device identifier, certificate data, and key data to the information integration platform.

3. The system according to claim 1, characterized in that, The flashing platform is also used to match the target device identifier, the target certificate data, and the target key data with the built-in regional parameters and device private key to obtain a first matching result; If the first matching result is successful, a target verification value is calculated based on the target certificate data and the target key data. If the target verification value is the same as the preset verification value, it is determined that the target vehicle has been successfully filled.

4. The system according to claim 3, characterized in that, The flashing platform is also used to match the target device identifier, the target certificate data, and the target key data with the area parameters to obtain a second matching result; If the second matching result is successful, the target device identifier, the target certificate data, and the target key data are matched with the device private key to obtain the first matching result.

5. The system according to claim 4, characterized in that, The system also includes an alarm and problem handling platform; The alarm and problem handling platform is used to determine the anomaly level based on the anomaly information when an anomaly occurs, and to determine the corresponding handling strategy based on the anomaly level. The abnormal information includes at least one of the following: unable to obtain the target device identifier, the target certificate data, and the target key data; The target vehicle failed to be filled; the handling strategy includes at least one of the following: periodically reminding for retry; pushing the abnormal information to the responsible personnel.

6. The system according to any one of claims 1 to 5, characterized in that, The system also includes a front-end platform; The vehicle management platform is also used to send the target vehicle code to the front-end platform; The front-end platform is used to determine the production testing condition corresponding to the target vehicle based on the target vehicle code and the sending time; the production testing condition is either a production condition or a testing condition. When the production testing condition is the production condition, a data request is sent to the information integration platform corresponding to the production condition. When the production testing condition is the test condition, a data request is sent to the information integration platform corresponding to the test condition.

7. The system according to claim 6, characterized in that, The front-end platform is also used to configure a corresponding vehicle code for each vehicle based on the sales information of multiple vehicles, and record the configuration time; when the target vehicle code is successfully configured and the sending time is less than the configuration time, the production test condition is determined to be the test condition. If the target vehicle coding configuration fails, the production test condition is determined to be the production condition.

8. The system according to any one of claims 1 to 5, characterized in that, The target certificate data and the target key data include at least one or more of the following: target certificate, target certificate identifier, target key, target key identifier, target certificate verification value, and target key verification value.

9. A vehicle filling method, characterized in that, The method includes: When a target vehicle is produced, a corresponding target vehicle identifier is generated for the target vehicle through the vehicle management platform. Based on the target vehicle identifier, the target vehicle code and target sales region corresponding to the target vehicle identifier are matched from the pre-stored correspondence between vehicle identifiers, vehicle codes, and sales regions. The target binding relationship between the target device identifier, target certificate data, and target key data corresponding to the target vehicle code is obtained from the target sales region through the information integration platform. When the target vehicle is flashed, the target vehicle identifier of the target vehicle is read by the flashing device in the flashing platform, and the target device identifier, the target certificate data and the target key data corresponding to the target binding relationship are obtained from the vehicle management platform based on the target vehicle identifier, so as to flash the target vehicle.

10. The method according to claim 9, characterized in that, The method further includes: The information integration platform determines the sales region corresponding to each vehicle based on the sales information of multiple vehicles, and sends a data request to the data management platform. In response to the data request, the data management platform generates device identifiers, certificate data, and key data for each sales region, as well as the binding relationship between the device identifiers, certificate data, and key data, and sends the binding relationship between the device identifiers, certificate data, and key data to the information integration platform.

11. A vehicle, characterized in that, The vehicle includes at least a vehicle controller, which stores a computer program or instructions. When the computer program or instructions are executed by the vehicle controller, they implement the method of claim 9 or claim 10.

12. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the method of claim 9 or claim 10.

Images