Vehicle management method and related apparatus

Abstract

A vehicle management method and a related apparatus, which are applied to the technical field of vehicle certification. The vehicle management method is applied to a vehicle management system, and the vehicle management system comprises a first vehicle and a management device. The vehicle management method comprises: a first vehicle receiving a first message; a management device sending a second message to the first vehicle; and the first vehicle sending a third message to the management device in response to the second message, wherein the first message comprises a first vehicle identification number and a first certificate, the second message is used for requesting the acquisition of vehicle information of the first vehicle, and the third message comprises the first vehicle identification number and the first certificate. In the present method, the first correlation, which is comprised in a third message, between a first vehicle identification number and a first certificate is unique, such that the legitimacy of a first vehicle can be verified by using the first correlation, and the whole verification process does not need to rely heavily on manual means for execution, thereby achieving intelligent vehicle verification and improving the efficiency of vehicle management.

Description

Vehicle management methods and related devices Technical Field

[0001] This application relates to the field of vehicle authentication technology, and in particular to a vehicle management method and related apparatus. Background Technology

[0002] Currently, with the widespread application of new technologies such as artificial intelligence in the vehicle field, intelligent vehicles are developing rapidly and their applications are becoming increasingly widespread. Therefore, vehicle management has become crucial.

[0003] In routine vehicle management tasks such as checking for counterfeit license plates and verifying vehicle color changes, a significant amount of manual work is still required. Law enforcement officers must complete the entire process by stopping vehicles on-site, checking vehicle documents, and verifying them through a platform. This process is time-consuming, labor-intensive, and inefficient, and can also disrupt normal traffic flow in situations with high traffic volume.

[0004] Therefore, a feasible solution is urgently needed to improve vehicle management efficiency.

[0005] Summary of the Invention

[0006] This application provides a vehicle management method and related apparatus, which can improve vehicle management efficiency.

[0007] In a first aspect, embodiments of this application provide a vehicle management method, which is applied to a vehicle management system including a first vehicle and management equipment. The vehicle management method includes:

[0008] The first vehicle receives a first message, which includes a first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes an equipment certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer and is used to verify the legitimacy of the first component. There is a first correspondence between the first VIN and the first certificate, which is used to verify the legitimacy of the first vehicle.

[0009] The management device sends a second message to the first vehicle, which requests the vehicle information of the first vehicle.

[0010] In response to the second message, the first vehicle sends a third message to the management device, which includes the first vehicle identification number and the first certificate.

[0011] In this embodiment of the application, a vehicle management method is provided. The vehicle management method is applied to a vehicle management system. A first vehicle in the vehicle management system receives a first message from a first vehicle manufacturer and a second message from a management device. In response to the second message, the first vehicle sends a third message to the management device. The legitimacy of the first vehicle is verified through message interaction between the first vehicle and the management device. The verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0012] The first vehicle identification number (VIN) is assigned to the first vehicle by the first vehicle manufacturer. The VIN is a set of characters assigned to a vehicle by the vehicle manufacturer to identify it. Optionally, the first VIN can be written into all or some of the important components of the first vehicle. The first certificate is an equipment certificate issued by the first vehicle manufacturer to the first component in the first vehicle based on the first vehicle manufacturer's root certificate. It indicates that the first component in the first vehicle is a component manufactured by the first vehicle manufacturer, and therefore, the first certificate can be used to verify the legitimacy of the first component. There is a first correspondence between the first VIN and the first certificate. Since the equipment certificate issued by the manufacturer to each component in the vehicle is unique, this first correspondence is also unique, and therefore can be used to verify the legitimacy of the first vehicle. Optionally, this first correspondence can be maintained by the first vehicle manufacturer.

[0013] Through the embodiments of this application, the first vehicle, the management device, and the first vehicle manufacturer in the vehicle management system interact with each other via messages. When the first vehicle receives a second message from the management device requesting to obtain the vehicle information of the first vehicle, it can send a third message to the management device. The first correspondence between the first vehicle identification number and the first certificate included in the third message is unique. The first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for digital identity, ensuring the binding relationship between the first component of the first vehicle and the vehicle (or the first vehicle identification number). Thus, the legitimacy of the first vehicle can be verified by using the first correspondence between the first vehicle identification number and the first certificate. Moreover, the entire verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0014] In one possible implementation, the vehicle management method further includes:

[0015] The management device verifies the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and verifies the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate.

[0016] This embodiment provides a possible specific implementation for verifying the legality of a first vehicle. Optionally, the verification scenario can be the verification of the vehicle's legality when a user applies for vehicle registration (or applies for a digital identity) with the vehicle management department after purchasing the vehicle. Specifically, since the first certificate is issued based on the root certificate of the first vehicle manufacturer, the management device can verify the legality of the first certificate based on the root certificate of the first vehicle manufacturer. Furthermore, since the first correspondence between the first vehicle identification number (VIN) and the first certificate is unique, the management device can verify the correctness of the first correspondence between the first VIN and the first certificate by interacting with the first vehicle manufacturer. Through this embodiment, the first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for a digital identity. While verifying the legality of the first component of the first vehicle, the binding relationship between the first component and the vehicle (or the first VIN) can be ensured, thereby verifying the legality of the first vehicle.

[0017] In one possible implementation, the legitimacy of the first vehicle is verified based on a first correspondence between the first vehicle identification number and the first certificate, including:

[0018] The management device verifies the legitimacy of the first vehicle after verifying the validity of the first certificate and the correctness of the first correspondence; or,

[0019] If the management device verifies that the first certificate is invalid or the first correspondence is incorrect, it will verify that the first vehicle is invalid.

[0020] In this embodiment, if the management device verifies that the first certificate is legitimate and the first correspondence is correct, it can determine that the first component in the first vehicle is a legitimate component manufactured by the original manufacturer and has not undergone illegal modification, thus verifying the legitimacy of the first vehicle. Conversely, if the management device verifies that the first certificate is invalid or the first correspondence is incorrect, it can determine that the first component in the first vehicle is not a legitimate component manufactured by the original manufacturer and may have undergone illegal operations such as modification or replacement, thus verifying the legitimacy of the first vehicle. Through this application embodiment, the first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for digital identity, verifying the legitimacy of the first component of the first vehicle while ensuring the binding relationship between the first component and the first vehicle (or the first vehicle identification number), thereby verifying the legitimacy of the first vehicle.

[0021] In one possible implementation, the vehicle management method further includes:

[0022] If the management device verifies the legitimacy of the first vehicle, it issues a first digital identity to the first vehicle based on the root certificate of the management device. The first digital identity is used to verify the legitimacy of the first vehicle.

[0023] In this embodiment, the first vehicle applies to the vehicle management department (management device) for a license plate (or applies for a digital identity). After verifying the legitimacy of the first vehicle, the management device issues a first digital identity to the first vehicle based on the root certificate of the management department. The first digital identity proves the legitimacy of the first vehicle. The first digital identity can be used to verify the legitimacy of the first vehicle after it obtains a legal license plate and is driven on the road.

[0024] In one possible implementation, the first message also includes the root certificate for the management device; the vehicle management method further includes:

[0025] The first vehicle verifies the legitimacy of the first digital identity based on the root certificate of the management device;

[0026] The first vehicle writes the first digital identity after verifying its legitimacy.

[0027] In this embodiment, the first message received by the first vehicle from the first vehicle manufacturer may also include the root certificate of the management device. If the first vehicle applies for a digital identity from the management device and obtains a first digital identity issued by the management device, the first vehicle can further verify the legitimacy of the first digital identity based on the root certificate of the management device. If the legitimacy of the first digital identity is verified, it is then written into the system. Through this embodiment, the legitimacy of the organization issuing the first digital identity can be verified, ensuring vehicle information security.

[0028] In one possible implementation, the first digital identity and / or the first vehicle identification number is stored in the first component.

[0029] In this embodiment, the first digital identity and / or the first vehicle identification number are stored in the first component, which can bind the first component and the first vehicle. This allows the legitimacy of the first vehicle to be verified by verifying the binding relationship between the first certificate and the first vehicle identification number during the digital identity application stage, and the legitimacy of the first vehicle to be verified by verifying the binding relationship between the first digital identity and the first vehicle identification number during the digital identity usage stage.

[0030] In one possible implementation, a second correspondence exists between the first digital identity and the first vehicle identification number, and the second correspondence is used to verify the legitimacy of the first vehicle.

[0031] In this embodiment, a second correspondence exists between the first digital identity and the first vehicle identification number. Since the digital identity issued by the management device to each vehicle is unique, this second correspondence is also unique. Therefore, the second correspondence can be used to verify the legitimacy of the first vehicle during the digital identity usage phase. Optionally, this second correspondence can be maintained by the management device.

[0032] In one possible implementation, the vehicle management method further includes:

[0033] The management device sends a fourth message to the first vehicle, which is used to request management of the first vehicle.

[0034] In response to the fourth message, the first vehicle sends a fifth message to the management device. The fifth message includes a first digital identity and a second vehicle identification number. The second vehicle identification number is a vehicle identification number stored in a second component of the first vehicle, and the first component and the second component are different components in the first vehicle.

[0035] In this embodiment, the first vehicle receives a fourth message from the management device and, in response to the fourth message, sends a fifth message to the management device. The legitimacy of the first vehicle is verified through message interaction between the first vehicle and the management device. This eliminates the need for extensive manual verification during the digital identity usage phase, enabling intelligent vehicle verification and improving vehicle management efficiency. Furthermore, the fifth message sent by the first vehicle includes the second vehicle identification number (VIN) stored in the second component of the first vehicle, rather than the first VIN stored in the first component. By using the VIN stored in other components (different from the first component) as the reporting source when the first vehicle uses its digital identity, this embodiment prevents the use of the original vehicle's legitimate digital identity when the first and / or second components are replaced or modified. This ensures the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby verifying the legitimacy of the first vehicle.

[0036] In one possible implementation, the vehicle management method further includes:

[0037] The first vehicle responds to the fourth message and obtains the second vehicle identification number stored in the second component based on the pre-configured first strategy.

[0038] In this embodiment, the first vehicle does not directly report the first vehicle identification number stored in the first component. Instead, it reports a vehicle identification number stored in other components that are different from the first component based on a pre-configured strategy. This can prevent the first vehicle from illegally replacing the first component and using the legitimate digital identity of the original vehicle corresponding to the first component. It ensures the binding relationship between the component (first component) storing the digital identity and the vehicle when the first vehicle uses the digital identity, thereby verifying the legitimacy of the first vehicle.

[0039] In one possible implementation, the fourth message is also used to instruct the second component; the vehicle management method further includes:

[0040] The first vehicle responds to the fourth message and retrieves the second vehicle identification number stored in the second component based on the instruction of the fourth message.

[0041] In this embodiment, the management device instructs the first vehicle to report the vehicle identification number stored in a component other than the first component (the second component). This can prevent the first vehicle from illegally replacing the first component and then using the legitimate digital identity of the original vehicle corresponding to the first component. It ensures the binding relationship between the component (the first component) that stores the digital identity and the vehicle when the first vehicle uses the digital identity, thereby verifying the legitimacy of the first vehicle.

[0042] In one possible implementation, the vehicle management method further includes:

[0043] The management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number.

[0044] This embodiment provides a possible specific implementation for verifying the legality of a first vehicle. Optionally, the verification scenario can be the verification of the first vehicle's legality after it has obtained a valid license plate and is on the road. Specifically, since the first digital identity and the vehicle identification number (VIN) of the first vehicle are unique, the management device can verify the legality of the first vehicle based on the consistency of the second correspondence between the first digital identity and the first VIN and the third correspondence between the first digital identity and the second VIN. Through this application embodiment, using the VIN stored by other components (other components different from the first component) as the reporting source when the first vehicle uses its digital identity can prevent the original vehicle's legal digital identity from being used when the first component and / or the second component are replaced or modified. This ensures the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby enabling the verification of the first vehicle's legality.

[0045] In one possible implementation, the management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number, including:

[0046] If the management equipment verifies that the second and third correspondences are the same, it verifies that the first vehicle is legitimate; or,

[0047] If the management equipment verifies that the second and third correspondences are different, it verifies that the first vehicle is illegal.

[0048] In this embodiment, if the management device verifies that the second and third correspondences are the same, it can determine that the first and second components in the first vehicle are legitimate components manufactured by the original manufacturer and have not been illegally modified, thus verifying the legitimacy of the first vehicle. Conversely, if the management device verifies that the second and third correspondences are different, it can determine that the first and / or second components in the first vehicle are not legitimate components manufactured by the original manufacturer and may have undergone illegal operations such as modification or replacement, thus verifying the legitimacy of the first vehicle. Through this application embodiment, using the vehicle identification number stored in other components (other components different from the first component) as the reporting source when the first vehicle uses its digital identity can prevent the original vehicle's legitimate digital identity from being used when the first and / or second components are replaced or modified. This ensures the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby verifying the legitimacy of the first vehicle.

[0049] In one possible implementation, the vehicle management method further includes:

[0050] The management device sends a sixth message to the first vehicle, which indicates whether the first vehicle is legitimate or illegitimate.

[0051] The first vehicle responds to the sixth message, indicating whether the first vehicle is legitimate or illegitimate.

[0052] In this embodiment, after verifying the legitimacy of the first vehicle, the management device can send a sixth message to the first vehicle, indicating whether the first vehicle is legitimate or illegitimate. In response to the sixth message, the first vehicle can display whether the first vehicle is legitimate or illegitimate through the vehicle's infotainment system or a terminal device connected to the first vehicle, and prompt the user whether there is a security risk to the first vehicle.

[0053] In one possible implementation, the first component includes at least one of the following: a vehicle terminal T-Box and a vehicle interactive system (IVI).

[0054] In this embodiment, the first component may include an in-vehicle terminal, such as a vehicle networking control unit (telematics box, T-Box), and may also include an in-vehicle interactive system, such as an in-vehicle infotainment system (IVI). Optionally, the first component may also be other in-vehicle components with high security, and this application embodiment does not limit this.

[0055] Secondly, embodiments of this application provide a vehicle management method applied to a first vehicle. The vehicle management method includes:

[0056] The first vehicle receives a first message, which includes a first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes an equipment certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate is used to verify the legitimacy of the first component. There is a first correspondence between the first VIN and the first certificate, which is used to verify the legitimacy of the first vehicle.

[0057] The first vehicle receives a second message, which is used to request the vehicle information of the first vehicle;

[0058] In response to the second message, the first vehicle sends a third message, which includes the first vehicle identification number and the first certificate.

[0059] In this embodiment of the application, a vehicle management method is provided. The vehicle management method is applied to a first vehicle. The first vehicle receives a first message from a first vehicle manufacturer and a second message from a management device. In response to the second message, the first vehicle sends a third message to the management device. The legitimacy of the first vehicle is verified through message interaction between the first vehicle and the management device. The verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0060] The first vehicle identification number (VIN) is assigned to the first vehicle by the first vehicle manufacturer. The VIN is a set of characters assigned to a vehicle by the vehicle manufacturer to identify it. Optionally, the first VIN can be written into all or some of the important components of the first vehicle. The first certificate is an equipment certificate issued by the first vehicle manufacturer to the first component in the first vehicle based on the first vehicle manufacturer's root certificate. It indicates that the first component in the first vehicle is a component manufactured by the first vehicle manufacturer, and therefore, the first certificate can be used to verify the legitimacy of the first component. There is a first correspondence between the first VIN and the first certificate. Since the equipment certificate issued by the manufacturer to each component in the vehicle is unique, this first correspondence is also unique, and therefore can be used to verify the legitimacy of the first vehicle. Optionally, this first correspondence can be maintained by the first vehicle manufacturer.

[0061] Through the embodiments of this application, the first vehicle interacts with the management device and the first vehicle manufacturer via message exchange. When the first vehicle receives a second message from the management device requesting to obtain the vehicle information of the first vehicle, it can send a third message to the management device. The first correspondence between the first vehicle identification number and the first certificate included in the third message is unique. The first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for digital identity, ensuring the binding relationship between the first component of the first vehicle and the vehicle (or the first vehicle identification number). Thus, the legitimacy of the first vehicle can be verified by using the first correspondence between the first vehicle identification number and the first certificate. Moreover, the entire verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0062] In one possible implementation, the vehicle management method further includes:

[0063] The first vehicle receives a first digital identity from the management device. The first digital identity is issued based on the root certificate of the management device and is used to verify the legitimacy of the first vehicle.

[0064] In one possible implementation, the first message also includes the root certificate for the management device; the vehicle management method further includes:

[0065] The first vehicle verifies the legitimacy of the first digital identity based on the root certificate of the management device;

[0066] The first vehicle writes the first digital identity after verifying its legitimacy.

[0067] In one possible implementation, the first digital identity and / or the first vehicle identification number is stored in the first component.

[0068] In one possible implementation, a second correspondence exists between the first digital identity and the first vehicle identification number, and the second correspondence is used to verify the legitimacy of the first vehicle.

[0069] In one possible implementation, the vehicle management method further includes:

[0070] The first vehicle receives a fourth message from the management device, which is used to request management of the first vehicle.

[0071] In response to the fourth message, the first vehicle sends a fifth message to the management device. The fifth message includes a first digital identity and a second vehicle identification number. The second vehicle identification number is a vehicle identification number stored in a second component of the first vehicle, and the first component and the second component are different components in the first vehicle.

[0072] In one possible implementation, the vehicle management method further includes:

[0073] The first vehicle responds to the fourth message and obtains the second vehicle identification number stored in the second component based on the pre-configured first strategy.

[0074] In one possible implementation, the fourth message is also used to instruct the second component; the vehicle management method further includes:

[0075] The first vehicle responds to the fourth message and retrieves the second vehicle identification number stored in the second component based on the instruction of the fourth message.

[0076] In one possible implementation, a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number are used to verify the legitimacy of the first vehicle.

[0077] In one possible implementation, the second correspondence between the first digital identity and the first vehicle identification number (VIN) and the third correspondence between the first digital identity and the second VIN are used to verify the legitimacy of the first vehicle, including:

[0078] The second and third correspondences are the same, and they are used to verify the legitimacy of the first vehicle; or,

[0079] The second and third correspondences are different; they are used to verify that the first vehicle is illegal.

[0080] In one possible implementation, the vehicle management method further includes:

[0081] The first vehicle receives a sixth message from the management device, which indicates whether the first vehicle is legitimate or illegitimate.

[0082] The first vehicle responds to the sixth message, indicating whether the first vehicle is legitimate or illegitimate.

[0083] In one possible implementation, the first component includes at least one of the following: a vehicle terminal T-Box and a vehicle interactive system (IVI).

[0084] Regarding the second aspect and any possible implementation, the steps for its execution can be referred to the corresponding implementation and implementation of the first aspect.

[0085] For the technical effects of the second aspect and any possible implementation, please refer to the description of the technical effects corresponding to the first aspect and the corresponding implementation.

[0086] Thirdly, embodiments of this application provide a vehicle management method applied to a management device. The vehicle management method includes:

[0087] The management device sends a second message to the first vehicle, which requests the vehicle information of the first vehicle.

[0088] The management device receives a third message from the first vehicle, which includes the first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to the first vehicle by the first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes an equipment certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer and is used to verify the legitimacy of the first component. There is a first correspondence between the first VIN and the first certificate, which is used to verify the legitimacy of the first vehicle.

[0089] In this embodiment of the application, a vehicle management method is provided. The vehicle management method is applied to a management device, which sends a second message to a first vehicle and receives a third message from the first vehicle. The legality of the first vehicle is verified through message interaction between the first vehicle and the management device. The verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0090] The first vehicle identification number (VIN) is assigned to the first vehicle by the first vehicle manufacturer. The VIN is a set of characters assigned to a vehicle by the vehicle manufacturer to identify it. Optionally, the first VIN can be written into all or some of the important components of the first vehicle. The first certificate is an equipment certificate issued by the first vehicle manufacturer to the first component in the first vehicle based on the first vehicle manufacturer's root certificate. It indicates that the first component in the first vehicle is a component manufactured by the first vehicle manufacturer, and therefore, the first certificate can be used to verify the legitimacy of the first component. There is a first correspondence between the first VIN and the first certificate. Since the equipment certificate issued by the manufacturer to each component in the vehicle is unique, this first correspondence is also unique, and therefore can be used to verify the legitimacy of the first vehicle. Optionally, this first correspondence can be maintained by the first vehicle manufacturer.

[0091] In this embodiment of the application, the management device and the first vehicle interact with each other via messages. When the first vehicle receives a second message from the management device requesting to obtain the vehicle information of the first vehicle, it can send a third message to the management device. The first correspondence between the first vehicle identification number and the first certificate included in the third message is unique. The first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for digital identity, ensuring the binding relationship between the first component of the first vehicle and the vehicle (or the first vehicle identification number). Thus, the legitimacy of the first vehicle can be verified by using the first correspondence between the first vehicle identification number and the first certificate. Moreover, the entire verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0092] In one possible implementation, the vehicle management method further includes:

[0093] The management device verifies the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and verifies the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate.

[0094] In one possible implementation, the legitimacy of the first vehicle is verified based on a first correspondence between the first vehicle identification number and the first certificate, including:

[0095] The management device verifies the legitimacy of the first vehicle after verifying the validity of the first certificate and the correctness of the first correspondence; or,

[0096] If the management device verifies that the first certificate is invalid or the first correspondence is incorrect, it will verify that the first vehicle is invalid.

[0097] In one possible implementation, the vehicle management method further includes:

[0098] If the management device verifies the legitimacy of the first vehicle, it issues a first digital identity to the first vehicle based on the root certificate of the management device. The first digital identity is used to verify the legitimacy of the first vehicle.

[0099] In one possible implementation, the first digital identity and / or the first vehicle identification number is stored in the first component.

[0100] In one possible implementation, a second correspondence exists between the first digital identity and the first vehicle identification number, and the second correspondence is used to verify the legitimacy of the first vehicle.

[0101] In one possible implementation, the vehicle management method further includes:

[0102] The management device sends a fourth message to the first vehicle, which is used to request management of the first vehicle.

[0103] The management device receives a fifth message from the first vehicle, the fifth message including a first digital identity and a second vehicle identification number; wherein, the second vehicle identification number is a vehicle identification number stored in a second component of the first vehicle, and the first component and the second component are different components in the first vehicle.

[0104] In one possible implementation, the fourth message is also used to request the second vehicle identification number stored in the second component.

[0105] In one possible implementation, the vehicle management method further includes:

[0106] The management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number.

[0107] In one possible implementation, the management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number, including:

[0108] If the management equipment verifies that the second and third correspondences are the same, it verifies that the first vehicle is legitimate; or,

[0109] If the management equipment verifies that the second and third correspondences are different, it verifies that the first vehicle is illegal.

[0110] In one possible implementation, the vehicle management method further includes:

[0111] The management device sends a sixth message to the first vehicle, which indicates whether the first vehicle is legitimate or illegitimate.

[0112] In one possible implementation, the first component includes at least one of the following: a vehicle terminal T-Box and a vehicle interactive system (IVI).

[0113] Regarding the third aspect and any possible implementation, the steps for its execution can be referred to the corresponding implementation and implementation of the first aspect.

[0114] For the technical effects of the third aspect and any possible implementation, please refer to the description of the technical effects corresponding to the first aspect and the corresponding implementation.

[0115] Fourthly, embodiments of this application provide a first vehicle including a unit for performing the method as described in any of the second aspects.

[0116] In one possible design, the device includes:

[0117] A communication unit is configured to receive a first message, the first message including a first vehicle identification number (VIN) and a first certificate; wherein, the first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, the first vehicle manufacturer being the manufacturer that produces the first vehicle; the first certificate includes a device certificate corresponding to a first component of the first vehicle, the first certificate being issued based on the root certificate of the first vehicle manufacturer, the first vehicle manufacturer being the manufacturer that produces the first vehicle, and the first certificate being used to verify the legitimacy of the first component; there is a first correspondence between the first VIN and the first certificate, the first correspondence being used to verify the legitimacy of the first vehicle;

[0118] The communication unit is also used to receive a second message, which is used to request vehicle information of the first vehicle;

[0119] The processing unit is configured to send a third message via the communication unit in response to the second message, the third message including a first vehicle identification number and a first certificate.

[0120] Regarding the processing unit and communication unit described in the fourth aspect and any possible implementation, the steps performed thereon can be referred to the corresponding implementation in the second aspect.

[0121] Regarding the technical effects of the fourth aspect and any possible implementation, refer to the description of the technical effects corresponding to the second aspect and the corresponding implementation.

[0122] Optionally, in the first vehicle described in the fourth aspect above and any possible implementation:

[0123] In one implementation, the first vehicle is an electronic device. When the first vehicle is an electronic device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0124] In another implementation, the first vehicle is a chip (system) or circuit used in an electronic device. When the first vehicle is a chip (system) or circuit used in an electronic device, the communication unit can be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0125] Fifthly, embodiments of this application provide a management device that includes units for performing the methods described in any of the third aspects.

[0126] In one possible design, the device includes:

[0127] A communication unit is used to send a second message to the first vehicle, the second message being used to request vehicle information of the first vehicle;

[0128] The communication unit is further configured to receive a third message from the first vehicle, the third message including a first vehicle identification number (VIN) and a first certificate; wherein, the first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, the first vehicle manufacturer being the manufacturer that produces the first vehicle, the first certificate including an equipment certificate corresponding to a first component of the first vehicle, the first certificate being issued based on the root certificate of the first vehicle manufacturer, the first certificate being used to verify the legitimacy of the first component, and a first correspondence relationship existing between the first VIN and the first certificate, the first correspondence relationship being used to verify the legitimacy of the first vehicle.

[0129] In one possible implementation, the device further includes:

[0130] The processing unit is used to verify the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and to verify the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate.

[0131] Regarding the processing unit and communication unit described in the fifth aspect and any possible implementation, the steps performed thereon can be referred to the corresponding implementation in the third aspect.

[0132] For the technical effects of the fifth aspect and any possible implementation, please refer to the description of the technical effects corresponding to the third aspect and the corresponding implementation.

[0133] Optionally, in the management device described in the fifth aspect above and any possible implementation:

[0134] In one implementation, the management device is an electronic device. When the management device is an electronic device, the communication unit can be a transceiver or an input / output interface; the processing unit can be at least one processor. Optionally, the transceiver can be a transceiver circuit. Optionally, the input / output interface can be an input / output circuit.

[0135] In another implementation, the management device is a chip (system) or circuit used in an electronic device. When the management device is a chip (system) or circuit used in an electronic device, the communication unit can be a communication interface (input / output interface), interface circuit, output circuit, input circuit, pin, or related circuit on the chip (system) or circuit; the processing unit can be at least one processor, processing circuit, or logic circuit.

[0136] Sixthly, embodiments of this application provide an electronic device including a processor. The processor is coupled to a memory and can be used to execute instructions in the memory to implement the methods of any one of the second to third aspects and any possible implementations described above. Optionally, the electronic device further includes a memory. Optionally, the electronic device further includes a communication interface, and the processor is coupled to the communication interface.

[0137] In a seventh aspect, embodiments of this application provide a chip, including: logic circuitry and a communication interface. The communication interface is used to receive or transmit information; the logic circuitry is used to receive or transmit information through the communication interface, causing the chip to execute the methods of any one of the second to third aspects and any possible implementations described above.

[0138] Eighthly, embodiments of this application provide a computer-readable storage medium for storing a computer program (also referred to as code or instructions); when the computer program is run on a computer, the method described in any of the first to third aspects and any possible implementations is implemented.

[0139] Ninthly, embodiments of this application provide a computer program product, the computer program product comprising: a computer program (also referred to as code or instructions); and, when the computer program is run, causing a computer to perform the method of any one of the first to third aspects and any one of the possible implementations described above.

[0140] In a tenth aspect, embodiments of this application provide a vehicle management system, which includes a first vehicle and a management device; wherein the first vehicle is configured to perform the method performed by the first vehicle as described in the first aspect and any possible implementation, and the management device is configured to perform the method performed by the management device as described in the first aspect and any possible implementation; or, the first vehicle is configured to perform the method as described in the second aspect and any possible implementation, and the management device is configured to perform the method as described in the third aspect and any possible implementation.

[0141] Among them, the first vehicle mentioned above is a vehicle in a broad sense, which can be a means of transportation, such as commercial vehicles, passenger cars, trains, etc., industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), robots, etc.

[0142] Optionally, the first vehicle is used to implement the method described in any possible implementation of the second aspect.

[0143] Furthermore, in the process of performing the methods described in any of the first to third aspects and any possible embodiments above, the processes related to sending and / or receiving information in the above methods can be understood as the process of the processor outputting information, and / or the process of the processor receiving input information. When outputting information, the processor can output the information to a transceiver (or communication interface, or transmitting module) so that the transceiver can transmit it. After the information is output by the processor, it may need to undergo other processing before reaching the transceiver. Similarly, when the processor receives input information, the transceiver (or communication interface, or transmitting module) receives the information and inputs it to the processor. Furthermore, after the transceiver receives the information, the information may need to undergo other processing before being input to the processor.

[0144] Based on the above principles, for example, the information sent mentioned in the aforementioned method can be understood as information output by the processor. Similarly, the information received can be understood as information received by the processor from input.

[0145] Optionally, unless otherwise specified, or unless they contradict their actual function or internal logic in the relevant description, the operations of the processor, such as transmitting, sending, and receiving, can be more generally understood as processor output and receiving, input, and other operations.

[0146] Optionally, in performing the methods described in the first aspect and any possible implementation above, the processor may be a processor specifically designed to perform these methods, or it may be a processor that performs these methods by executing computer instructions stored in memory, such as a general-purpose processor. The memory may be a non-transitory memory, such as read-only memory (ROM), which may be integrated with the processor on the same chip or disposed on different chips. This application does not limit the type of memory or the arrangement of the memory and processor.

[0147] In one possible implementation, at least one of the aforementioned memories is located outside the device.

[0148] In yet another possible implementation, at least one of the aforementioned memories is located within the device.

[0149] In another possible implementation, a portion of the memory of the at least one memory is located inside the device, while another portion is located outside the device.

[0150] In this application, the processor and memory may also be integrated into a single device, that is, the processor and memory can be integrated together. Attached Figure Description

[0151] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0152] Figure 1 is a flowchart illustrating a vehicle management method provided in an embodiment of this application;

[0153] Figure 2 is a flowchart illustrating another vehicle management method provided in an embodiment of this application;

[0154] Figure 3 is a flowchart illustrating another vehicle management method provided in an embodiment of this application;

[0155] Figure 4 is a flowchart illustrating another vehicle management method provided in an embodiment of this application;

[0156] Figure 5 is a structural schematic diagram of a first vehicle provided in an embodiment of this application;

[0157] Figure 6 is a structural schematic diagram of a management device provided in an embodiment of this application;

[0158] Figure 7 is a schematic diagram of the structure of an electronic device provided in an embodiment of this application;

[0159] Figure 8 is a schematic diagram of the structure of a chip provided in an embodiment of this application. Detailed Implementation

[0160] To make the objectives, technical solutions, and advantages of this application clearer, the embodiments of this application will be described below with reference to the accompanying drawings.

[0161] The terms "first" and "second," etc., used in the specification, claims, and drawings of this application are used to distinguish different objects, not to describe a specific order. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover non-exclusive inclusion. For example, a process, method, system, product, or apparatus that includes a series of steps or units is not limited to the listed steps or units, but may optionally include steps or units not listed, or may optionally include other steps or units inherent to these processes, methods, products, or apparatuses.

[0162] The term "embodiment" as used herein means that a specific feature, structure, or characteristic described in connection with an embodiment may be included in at least one embodiment of this application. The appearance of this phrase in various places in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment mutually exclusive with other embodiments. Those skilled in the art will explicitly and implicitly understand that, unless otherwise specified or logically conflicting, the terminology and / or descriptions between the various embodiments of this application are consistent and can be mutually referenced, and technical features in different embodiments can be combined to form new embodiments based on their inherent logical relationships.

[0163] It should be understood that in this application, "at least one (item)" means one or more, "more than one" means two or more, "at least two (items)" means two or three or more, and "and / or" is used to describe the relationship between related objects, indicating that there can be three relationships. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist simultaneously, where A and B can be singular or plural. The character " / " generally indicates that the related objects before and after are in an "or" relationship. "At least one (item) of the following" or similar expressions refer to any combination of these items, including any combination of single or plural items. For example, at least one (item) of a, b, or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, and c can be single or multiple.

[0164] It should be noted that, in this application, "instruction" can include direct instruction, indirect instruction, explicit instruction, and implicit instruction. When describing a certain instruction information for the purpose of instructing A, it can be understood that the instruction information carries A, directly instructs A, or indirectly instructs A.

[0165] In this application, the information indicated by the instruction information is called the information to be instructed. In specific implementations, there are many ways to indicate the information to be instructed, such as, but not limited to, directly indicating the information to be instructed, such as the information to be instructed itself or its index. It can also indirectly indicate the information to be instructed by indicating other information, where there is a correlation between the other information and the information to be instructed. It can also indicate only a part of the information to be instructed, while the other parts are known or pre-agreed upon. For example, the instruction of specific information can be achieved by using a pre-agreed (e.g., protocol-defined) arrangement of various information, thereby reducing instruction overhead to some extent. The information to be instructed can be sent as a whole or divided into multiple sub-information units, and the sending period and / or timing of these sub-information units can be the same or different. This application does not limit the specific sending method. The sending period and / or timing of these sub-information units can be predefined, for example, according to a protocol, or configured by the transmitting device by sending configuration information to the receiving device.

[0166] It should be noted that in this application, "send" can be understood as "output" and "receive" can be understood as "input". "Send information to A", where "to A" simply indicates the direction of information transmission, and A is the destination, does not limit "send information to A" to a direct transmission over the air interface. "Send information to A" includes sending information directly to A, as well as sending information indirectly to A through a transmitter. Therefore, "send information to A" can also be understood as "outputting information destined for A". Similarly, "receive information from A" indicates that the source of the information is A, including receiving information directly from A, as well as receiving information indirectly from A through a receiver. Therefore, "receive information from A" can also be understood as "inputting information from A".

[0167] This application provides a vehicle management method and related apparatus, applied in the field of vehicle authentication technology, such as a vehicle management method in a scenario of applying for a digital identity and / or a vehicle management method in a scenario of using a digital identity. To better understand the technical solution of this application, the relevant terms and concepts that may be involved in the embodiments of this application are introduced below.

[0168] Vehicle Identification Number (VIN): A unique set of characters assigned to a vehicle by the manufacturer to identify the vehicle itself. The VIN consists of 17 characters, commonly known as a 17-digit code. Correctly interpreting the VIN is crucial for accurately identifying the vehicle model, and consequently, for proper diagnosis and repair.

[0169] The first part of the VIN identifies the vehicle's manufacturer. When this code is assigned to a particular manufacturer, it serves as its identifier. When used in conjunction with the rest of the VIN, the World Manufacturer Identifier (WMI) is sufficient to ensure the uniqueness of the VIN for all vehicles manufactured worldwide within a 30-year period. The second part of the VIN describes general vehicle characteristics. The final part of the VIN is a set of codes assigned by the manufacturer to distinguish different vehicles. This set of codes, along with the Vehicle Descriptive Section (VDS), is sufficient to ensure the uniqueness of the VIN for every vehicle produced by each manufacturer within a 30-year period.

[0170] Currently, routine vehicle management tasks, such as checking for counterfeit license plates and verifying vehicle color changes, still rely heavily on manual methods. Law enforcement officers complete the entire process by stopping vehicles on-site, checking vehicle documents, and verifying them through a platform. This process is time-consuming, labor-intensive, and inefficient, and can disrupt normal traffic flow, especially in high-traffic situations.

[0171] Similarly, in accident tracing, management departments also need to obtain license plate and vehicle details manually. However, when the vehicle is severely damaged (license plate and vehicle VIN code cannot be obtained) or the accident site is difficult to investigate (road collapse, vehicle fall), relying on traditional manual methods may not be able to complete the routine information acquisition and vehicle accident tracing work.

[0172] Therefore, a feasible solution is urgently needed to improve vehicle management efficiency.

[0173] In view of this, embodiments of this application provide a vehicle management method, applied in the field of vehicle authentication technology, such as a vehicle management method in a scenario of applying for a digital identity and / or a vehicle management method in a scenario of using a digital identity. The core idea of ​​the vehicle management method provided in this application is to embed a chip or create a dedicated environment in a first vehicle, and store information related to the first vehicle (such as vehicle identification number, device certificates of components on the first vehicle, digital identity, etc.) in the chip or dedicated environment, so that when necessary, the relevant information of the first vehicle can be read wirelessly to quickly complete the verification of vehicle cloning, color change registration, etc., thereby improving vehicle management efficiency.

[0174] Generally, this chip can be mounted on an in-vehicle terminal. When assigning a digital identity to the first vehicle, it is necessary to ensure the correct binding relationship between the digital identity and the first vehicle (to prevent unauthorized vehicles from obtaining legitimate digital identities), and when using the digital identity, it is also necessary to prevent the digital identity from being misused (to prevent unauthorized vehicles from using legitimate digital identities).

[0175] Please refer to Figure 1, which is a flowchart illustrating a vehicle management method provided in an embodiment of this application. This vehicle management method is applied in the field of vehicle authentication technology, such as vehicle management and / or vehicle management in scenarios involving digital identity applications or digital identity usage.

[0176] Specifically, the vehicle management method is applied to a vehicle management system, which includes a first vehicle and management equipment. Optionally, the vehicle management system may also include a first vehicle factory. The vehicle management method includes, but is not limited to, the following steps:

[0177] S101: The first vehicle manufacturer sends a first message to the first vehicle, and the first vehicle receives the first message accordingly.

[0178] The first message includes the first vehicle identification number and the first certificate.

[0179] It is understood that the first vehicle identification number (VIN) is a VIN assigned to the first vehicle by the first vehicle manufacturer, which is the manufacturer that produces the first vehicle. Optionally, the first VIN may be written into all or some of the important components of the first vehicle; for example, the first VIN may be written into a first component.

[0180] Understandably, the first certificate includes the equipment certificate corresponding to the first component of the first vehicle. This first certificate is issued by the first vehicle manufacturer based on its root certificate, indicating that the first component in the first vehicle is manufactured by the first vehicle manufacturer. Therefore, this first certificate can be used to verify the legitimacy of the first component. Optionally, this first certificate can be written into the first component.

[0181] It is understandable that there is a first correspondence between the first vehicle identification number and the first certificate. Since the equipment certificate issued by the vehicle manufacturer to each component in the vehicle is unique, this first correspondence is also unique. Therefore, the first correspondence can be used to verify the legitimacy of the first vehicle. Optionally, this first correspondence can be maintained by the first vehicle manufacturer.

[0182] Optionally, after receiving the first message, the first vehicle writes the first certificate in the first message into the first component, and writes the first vehicle identification number in the first message into all or part of the important components (e.g., the first component) in the first vehicle.

[0183] Optionally, the first component may include an in-vehicle terminal, such as a telematics box (T-Box), and may also include an in-vehicle interactive system, such as an in-vehicle infotainment system (IVI). Optionally, the first component may also be other in-vehicle components with high security, and this application embodiment does not limit this.

[0184] Optionally, step S101 can be performed when the first vehicle is produced at the first vehicle factory.

[0185] S102: The management device sends a second message to the first vehicle, and the first vehicle receives the second message accordingly.

[0186] The second message is used to request vehicle information of the first vehicle.

[0187] Optionally, the vehicle information of the first vehicle requested by the second message includes, but is not limited to: the first vehicle identification number assigned to the first vehicle by the first vehicle manufacturer, the first certificate issued by the first vehicle manufacturer to the first component of the first vehicle based on the first vehicle manufacturer's root certificate, etc., and this application embodiment does not limit this.

[0188] Understandably, in a scenario where the first vehicle applies for a digital identity from the management device (management department), the management device sends the second message to the first vehicle, requesting to obtain the vehicle information of the first vehicle to verify the legitimacy of the first vehicle.

[0189] S103: The first vehicle sends a third message to the management device, and the management device receives the third message accordingly.

[0190] The third message includes the aforementioned first vehicle identification number and first certificate.

[0191] Optionally, the above steps S102 to S103 can be performed when the first vehicle applies for a digital identity from the management device (management department).

[0192] Understandably, since the first vehicle identification number (VIN) is unique, the first certificate is also unique, and the first correspondence between the first VIN and the first certificate is also unique, in the scenario where the first vehicle applies for a digital identity from the management equipment (management department), the first certificate of the first component of the first vehicle and the first VIN of the first vehicle can be used as credentials when applying for a digital identity to ensure the binding relationship between the first component of the first vehicle and the vehicle (or the first VIN). Thus, the legitimacy of the first vehicle can be verified by using the first correspondence between the first VIN and the first certificate.

[0193] It is understood that the management device in this application embodiment may be a device equipped with a processor / chip that can execute computer execution instructions, or it may be a processor / chip that can execute computer execution instructions. Optionally, the management device may be an electronic device, or it may be a processor / chip within an electronic device, used to execute the vehicle management method in this application embodiment to improve vehicle management efficiency.

[0194] It is understood that the first vehicle in this application embodiment may be a device equipped with a processor / chip that can execute computer execution instructions, or it may be a processor / chip that can execute computer execution instructions. Optionally, the first vehicle may be an electronic device, or it may be a processor / chip within an electronic device, used to execute the vehicle management method in this application embodiment to improve vehicle management efficiency.

[0195] Optionally, the first vehicle, management device, and vehicle management method in the embodiments of this application can be applied to, but are not limited to, in-vehicle systems. The vehicle equipped with the in-vehicle system is an intelligent driving vehicle and can be replaced by a terminal device. The terminal device can be, but is not limited to, vehicles such as commercial vehicles, passenger cars, trains, industrial vehicles (such as forklifts, trailers, tractors, etc.), engineering vehicles (such as excavators, bulldozers, cranes, etc.), robots, etc. The embodiments of this application do not specifically limit this.

[0196] In the scenario where a first vehicle applies for a digital identity from a management device (management department) through the embodiments of this application, the first vehicle, the management device, and the first vehicle manufacturer in the vehicle management system interact with each other via messages. When the first vehicle receives a second message from the management device requesting to obtain the vehicle information of the first vehicle, it can send a third message to the management device. The first correspondence between the first vehicle identification number and the first certificate included in the third message is unique. The first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for a digital identity, ensuring the binding relationship between the first component of the first vehicle and the vehicle (or the first vehicle identification number). Thus, the legitimacy of the first vehicle can be verified by using the first correspondence between the first vehicle identification number and the first certificate. Moreover, the entire verification process does not require a large amount of manual work, thereby realizing intelligent vehicle verification and improving vehicle management efficiency.

[0197] In one possible embodiment, the vehicle management method described above may also perform the following steps, including but not limited to:

[0198] S104: The management device verifies the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and verifies the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate.

[0199] Optionally, the verification scenario could be the verification of the legality of the first vehicle when a user applies for a license plate (or applies for a digital identity) with the vehicle management department after purchasing the first vehicle.

[0200] Understandably, since the first certificate is issued based on the root certificate of the first vehicle manufacturer, the management equipment can verify the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer.

[0201] Optionally, the root certificate of the first car manufacturer can be stored in the management device in advance, or it can be sent to the management device when there is a verification requirement. This application embodiment does not limit this.

[0202] It is understandable that, since the first correspondence between the first vehicle identification number and the first certificate is unique, the management device can verify the correctness of the first correspondence between the first vehicle identification number and the first certificate by interacting with the first vehicle manufacturer.

[0203] Optionally, when the first vehicle manufacturer produces the first vehicle, it can simultaneously register the first vehicle identification number, the first certificate, and the first correspondence between the first vehicle identification number and the first certificate with the management equipment, so that the management equipment can verify the correctness of the first correspondence.

[0204] Optionally, the management device can also query the first vehicle manufacturer when there is a verification requirement to confirm the correctness of the first vehicle identification number, the first certificate, and the first correspondence between the first vehicle identification number and the first certificate. This application embodiment does not limit this.

[0205] Alternatively, the verification results of the management equipment can be categorized into the following types:

[0206] Scenario 1:

[0207] The management equipment verifies the legitimacy of the first vehicle after verifying that the first certificate is valid and the first correspondence is correct.

[0208] Understandably, if the management equipment verifies the legitimacy of the first certificate and the correctness of the first correspondence, it can determine that the first component in the first vehicle is a legitimate component manufactured by the original manufacturer of the first vehicle and has not been illegally modified, thus verifying the legitimacy of the first vehicle.

[0209] Scenario 2:

[0210] If the management device verifies that the first certificate is invalid or the first correspondence is incorrect, it will verify that the first vehicle is invalid.

[0211] Understandably, if the management equipment verifies that the first certificate is invalid or the first correspondence is incorrect, it can determine that the first component in the first vehicle is not a legitimate component manufactured by the original manufacturer of the first vehicle and may have undergone illegal operations such as modification or replacement, thus verifying that the first vehicle is invalid.

[0212] In the scenario where a first vehicle applies for a digital identity from a management device (management department) through the embodiments of this application, the first certificate of the first component of the first vehicle and the first vehicle identification number of the first vehicle can be used as credentials when applying for a digital identity. This verifies the legality of the first component of the first vehicle while ensuring the binding relationship between the first component of the first vehicle and the vehicle (or the first vehicle identification number), thereby verifying the legality of the first vehicle.

[0213] In one possible embodiment, the vehicle management method described above may also perform the following steps, including but not limited to:

[0214] S105: The management device sends a first digital identity to the first vehicle, and the first vehicle receives the first digital identity accordingly.

[0215] Understandably, when the management device verifies the legitimacy of the first vehicle, it issues a first digital identity to the first vehicle based on the root certificate of the management device. This first digital identity proves the legitimacy of the first vehicle and can be used to verify the legitimacy of the first vehicle after it obtains a legal license plate and is driven on the road.

[0216] Optionally, the first message may also include the root certificate for managing the device.

[0217] Optionally, the root certificate of the management device can be pre-stored in the first vehicle manufacturer. The first vehicle manufacturer sends the root certificate of the management device to the first vehicle through the aforementioned first message. Alternatively, the root certificate of the management device can be sent to the first vehicle when the first vehicle needs to verify its digital identity. This application embodiment does not limit this.

[0218] Optionally, the above vehicle management method may also include, but is not limited to, the following steps:

[0219] The first vehicle verifies the legitimacy of the first digital identity based on the root certificate of the management device.

[0220] The first vehicle writes the first digital identity after verifying its legitimacy.

[0221] Understandably, when the first vehicle applies for a digital identity from the management device and obtains a first digital identity issued by the management device, the first vehicle can also verify the legitimacy of the first digital identity based on the root certificate of the management device, and then write the first digital identity into the system after verifying its legitimacy.

[0222] The embodiments of this application can verify the legitimacy of the institution that issues the first digital identity and ensure the security of vehicle information.

[0223] Optionally, the aforementioned first digital identity and / or first vehicle identification number may be stored in the first component.

[0224] It is understood that the aforementioned first digital identity and / or first vehicle identification number is stored in the first component, which can bind the first component and the first vehicle, so that the legality of the first vehicle can be verified by verifying the binding relationship between the first certificate and the first vehicle identification number during the digital identity application stage, and the legality of the first vehicle can be verified by verifying the binding relationship between the first digital identity and the first vehicle identification number during the digital identity usage stage.

[0225] Optionally, there is a second correspondence between the first digital identity and the first vehicle identification number, which can be used to verify the legitimacy of the first vehicle.

[0226] Understandably, since the digital identity issued to each vehicle by the management device is unique, the second correspondence is also unique. Therefore, during the digital identity usage phase, the second correspondence can be used to verify the legitimacy of the first vehicle. Optionally, this second correspondence can be maintained by the management device.

[0227] In one possible embodiment, the vehicle management method described above may also perform the following steps, including but not limited to:

[0228] S106: The management device sends a fourth message to the first vehicle, and the first vehicle receives the fourth message accordingly.

[0229] The fourth message is used to request management of the first vehicle.

[0230] Understandably, in the scenario where the first vehicle obtains a valid license plate (a valid digital identity) and starts driving on the road, the management device sends this fourth message to the first vehicle, requesting management of the first vehicle on the road and verification of the first vehicle's legitimacy.

[0231] S107: The first vehicle sends a fifth message to the management device, and the management device receives the fifth message accordingly.

[0232] The fifth message includes the aforementioned first digital identity and second vehicle identification number.

[0233] The second vehicle identification number is the vehicle identification number stored in the second component of the first vehicle, and the first component and the second component are different components in the first vehicle.

[0234] Optionally, steps S106 to S107 can be performed when the digital identity is used in a scenario where the first vehicle has obtained a valid digital identity and is being checked by the management equipment (management department).

[0235] Understandably, the first vehicle receives a fourth message from the management device and, in response, sends a fifth message to the management device. The legitimacy of the first vehicle is verified through this message interaction between the first vehicle and the management device. This verification process during the digital identity usage phase eliminates the need for extensive manual intervention, thus enabling intelligent vehicle verification and improving vehicle management efficiency. Furthermore, the fifth message sent by the first vehicle includes the second vehicle identification number stored in the second component of the first vehicle, rather than the first vehicle identification number stored in the first component.

[0236] By using the vehicle identification number stored in other components (other components different from the first component) as the reporting source when the first vehicle uses its digital identity, it is possible to prevent the original vehicle's legitimate digital identity from being used when the first component and / or the second component are replaced or modified. This ensures the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby enabling the verification of the legitimacy of the first vehicle.

[0237] Optionally, the second vehicle identification number in the fifth message of step S107 above can be obtained through methods including but not limited to the following:

[0238] Method 1:

[0239] The first vehicle responds to the fourth message and obtains the second vehicle identification number stored in the second component based on the pre-configured first strategy.

[0240] Understandably, the first vehicle does not directly report the first vehicle identification number stored in the first component. Instead, it reports a vehicle identification number stored in other components that are different from the first component, based on a pre-configured strategy. This can prevent the first vehicle from illegally replacing the first component and then using the legitimate digital identity of the original vehicle corresponding to the first component. It ensures the binding relationship between the component (first component) that stores the digital identity and the vehicle when the first vehicle uses the digital identity, thereby verifying the legitimacy of the first vehicle.

[0241] Method 2:

[0242] The fourth message is also used to instruct the second component, and the first vehicle responds to the fourth message to retrieve the second vehicle identification number stored in the second component based on the instruction of the fourth message.

[0243] Understandably, the management device instructs the first vehicle to report the vehicle identification number stored in a component other than the first component (the second component). This can prevent the first vehicle from illegally replacing the first component and then using the legitimate digital identity of the original vehicle corresponding to the first component. It ensures the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby verifying the legitimacy of the first vehicle.

[0244] In one possible embodiment, the vehicle management method described above may also perform the following steps, including but not limited to:

[0245] S108: The management device verifies the legitimacy of the first vehicle based on the second correspondence between the first digital identity and the first vehicle identification number and the third correspondence between the first digital identity and the second vehicle identification number.

[0246] Optionally, the verification scenario can be the verification of the legitimacy of the first vehicle when it uses its digital identity for inspection by management equipment (management department) after obtaining a legitimate digital identity.

[0247] It is understandable that, since the first digital identity and the vehicle identification number of the first vehicle are unique, the management device can verify the legitimacy of the first vehicle based on the consistency of the second correspondence between the first digital identity and the first vehicle identification number and the third correspondence between the first digital identity and the second vehicle identification number.

[0248] Alternatively, the verification results of the management equipment can be categorized into the following types:

[0249] Scenario 1:

[0250] If the management equipment verifies that the second and third correspondences are the same, it verifies that the first vehicle is legitimate.

[0251] Understandably, if the management equipment verifies that the second and third correspondences are the same, it can determine that the first and second components in the first vehicle are legitimate components manufactured by the original manufacturer of the first vehicle and have not been illegally modified, thus verifying the legitimacy of the first vehicle.

[0252] Scenario 2:

[0253] If the management equipment verifies that the second and third correspondences are different, it verifies that the first vehicle is illegal.

[0254] It is understandable that if the management equipment verifies that the second and third correspondences are different, it can determine that the first component and / or the second component in the first vehicle are not legitimate components originally manufactured by the first vehicle manufacturer, and may have undergone illegal operations such as modification or replacement, thus verifying that the first vehicle is illegal.

[0255] By using the vehicle identification number stored in other components (other components different from the first component) as the reporting source when the first vehicle uses its digital identity, it is possible to prevent the original vehicle's legitimate digital identity from being used when the first component and / or the second component are replaced or modified. This ensures the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby enabling the verification of the legitimacy of the first vehicle.

[0256] In one possible embodiment, the vehicle management method described above may also perform the following steps, including but not limited to:

[0257] S109: The management device sends a sixth message to the first vehicle, and the first vehicle receives the sixth message accordingly.

[0258] S110: The first vehicle responds to the sixth message, indicating whether the first vehicle is legitimate or illegitimate.

[0259] Understandably, after verifying the legitimacy of the first vehicle, the management device can send a sixth message to the first vehicle, indicating whether the first vehicle is legitimate or illegitimate. In response to the sixth message, the first vehicle can display whether the first vehicle is legitimate or illegitimate through the vehicle's infotainment system or a terminal device connected to the first vehicle, and prompt the user whether there is a security risk associated with the first vehicle.

[0260] This application also provides a vehicle management method, as detailed in Figure 2, which is a flowchart illustrating another vehicle management method provided in an embodiment of this application. This vehicle management method is applied in the field of vehicle authentication technology, such as vehicle management and / or vehicle management in scenarios involving digital identity applications or digital identity usage.

[0261] It is understood that the steps in the embodiments of this application can be regarded as reasonable modifications or supplements to the embodiments in FIG1 above; or, it is understood that the vehicle management method in the embodiments of this application can also be regarded as an embodiment that can be executed independently, and this application does not limit it.

[0262] It is understood that the vehicle management system involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the vehicle management system involved in the vehicle management method shown in Figure 1 above, and will not be repeated here.

[0263] Specifically, the vehicle management method is applied to a vehicle management system, which includes a first vehicle and management equipment. Optionally, the vehicle management system may also include a first vehicle factory. The vehicle management method includes, but is not limited to, the following steps:

[0264] S201: The first vehicle manufacturer sends a first message to the first vehicle, and the first vehicle receives the first message accordingly.

[0265] The description is consistent with the above step S101, and will not be repeated here.

[0266] Optionally, step S201 can be performed when the first vehicle is produced at the first vehicle factory.

[0267] S202: The management device sends a second message to the first vehicle, and the first vehicle receives the second message accordingly.

[0268] The description is consistent with the above step S202, and will not be repeated here.

[0269] S203: The first vehicle sends a third message to the management device, and the management device receives the third message accordingly.

[0270] The description is consistent with the above-mentioned step S203, and will not be repeated here.

[0271] S204: The management device verifies the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and verifies the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate.

[0272] The description is consistent with that of step S204 above, and will not be repeated here.

[0273] S205: The management device sends a first digital identity to the first vehicle, and the first vehicle receives the first digital identity accordingly.

[0274] The description is consistent with that of step S205 above, and will not be repeated here.

[0275] Optionally, steps S202 to S205 can be performed when the first vehicle applies for a digital identity from the management device (management department) (i.e., the digital identity application stage).

[0276] S206: The management device sends a fourth message to the first vehicle, and the first vehicle receives the fourth message accordingly.

[0277] The description is consistent with the above-mentioned step S206, and will not be repeated here.

[0278] S207: The first vehicle sends a fifth message to the management device, and the management device receives the fifth message accordingly.

[0279] The description is consistent with the above-mentioned step S207, and will not be repeated here.

[0280] S208: The management device verifies the legitimacy of the first vehicle based on the second correspondence between the first digital identity and the first vehicle identification number and the third correspondence between the first digital identity and the second vehicle identification number.

[0281] The description is consistent with the above step S208, and will not be repeated here.

[0282] S209: The management device sends a sixth message to the first vehicle, and the first vehicle receives the sixth message accordingly.

[0283] The description is consistent with that of step S209 above, and will not be repeated here.

[0284] S210: The first vehicle responds to the sixth message, indicating whether the first vehicle is legitimate or illegitimate.

[0285] The description is consistent with that of step S210 above, and will not be repeated here.

[0286] Optionally, steps S206 to S210 can be performed when the digital identity is used in a scenario where the first vehicle has obtained a valid digital identity and is being checked by the management equipment (management department) (i.e., the digital identity usage stage).

[0287] In the scenario where a first vehicle applies for a digital identity from a management device (management department), the first certificate of the first component of the first vehicle and the first vehicle identification number (VIN) of the first vehicle can be used as credentials for applying for a digital identity. This verifies the legality of the first component of the first vehicle while ensuring the binding relationship between the first component and the vehicle (or the first VIN), thereby verifying the legality of the first vehicle. Furthermore, when the first vehicle uses its digital identity for inspection by the management device (management department) after obtaining a legitimate digital identity, the VIN stored in other components (other than the first component) can be used as the reporting source when the first vehicle uses its digital identity. This prevents the use of the original vehicle's legitimate digital identity when the first component and / or the second component are replaced or modified, ensuring the binding relationship between the component storing the digital identity (the first component) and the vehicle when the first vehicle uses its digital identity, thereby verifying the legality of the first vehicle. Moreover, the entire verification process does not rely heavily on manual methods, thus achieving intelligent vehicle verification and improving vehicle management efficiency.

[0288] This application also provides a vehicle management method, as detailed in Figure 3, which is a flowchart illustrating another vehicle management method provided in an embodiment of this application. This vehicle management method is applied in the field of vehicle authentication technology, such as vehicle management and / or vehicle management in scenarios involving digital identity application and / or digital identity usage.

[0289] It is understood that the steps in the embodiments of this application can be regarded as reasonable modifications or supplements to the embodiments in Figures 1 and 2 above; or, it is understood that the vehicle management method in the embodiments of this application can also be regarded as an embodiment that can be executed independently, and this application does not limit it.

[0290] Specifically, this vehicle management method is applied to a vehicle management system, which includes vehicle a, vehicle factory A, management device A, and management device B. It is understood that the vehicle management system involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the vehicle management system involved in the vehicle management method shown in Figure 1 above; vehicle a involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the first vehicle involved in the vehicle management method shown in Figure 1 above; vehicle factory A involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the first vehicle factory involved in the vehicle management method shown in Figure 1 above; and management device A (which may be a computer device) and management device B (which may be a roadside device or a handheld device, etc., used to communicate with management device A and vehicle a) involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the management device involved in the vehicle management method shown in Figure 1 above, and will not be repeated here.

[0291] The vehicle management method is mainly divided into the vehicle production stage, the digital identity application stage, and the digital identity usage stage.

[0292] The vehicle production stage includes, but is not limited to, the following steps:

[0293] Step 1a: Car factory A saves and manages the root certificate of device A.

[0294] Optionally, the root certificate of the management device A can be found in the relevant description of "root certificate of management device" in step S105 above, and will not be repeated here.

[0295] Step 1b: Manage device A to save the root certificate of vehicle manufacturer A.

[0296] Optionally, the root certificate of vehicle manufacturer A can be found in the relevant description of "root certificate of the first vehicle manufacturer" in step S104 above, and will not be repeated here.

[0297] Step 2: Vehicle manufacturer A assigns a VINa to vehicle a and maintains the correspondence between the VINa and equipment certificate a.

[0298] During the vehicle production phase, vehicle manufacturer A assigns a VINa to vehicle a, records, saves, and maintains the correspondence between the VINa and the equipment certificates of each component (e.g., equipment certificate a for component T-Box).

[0299] Optionally, the VINa can refer to the relevant description of "first vehicle identification number" in step S101 above, the component T-Box can refer to the relevant description of "first component" in step S101 above, and the device certificate a can refer to the relevant description of "first certificate" in step S101 above. These details will not be repeated here.

[0300] Step 3: Vehicle manufacturer A sends VINa, device certificate a, and root certificate of management device A to vehicle a. Accordingly, vehicle a receives the VINa, device certificate a, and root certificate of management device A.

[0301] Vehicle manufacturer A writes information to components (such as T-Boxes) in vehicle a on the production line. The information written includes, but is not limited to, VINa, the device certificate a of component T-Box, and the root certificate of management device A saved by vehicle manufacturer A in step 1a.

[0302] Step 4 (optional): Vehicle manufacturer A files VINa and equipment certificate a.

[0303] Vehicle manufacturer A transmits the VINa and component T-Box equipment certificate a to management device A (management platform) as the basis for management device A to issue the digital identity of vehicle a.

[0304] Optionally, the component in this application embodiment takes the vehicle terminal T-Box as an example. In reality, only the device certificate of the component carrying the chip / dedicated environment needs to be transmitted. This application embodiment does not limit this.

[0305] Optionally, step 4 above is an optional execution step, and either step 4 above or step 8 below can be performed. This application embodiment does not limit this.

[0306] The digital identity application process includes, but is not limited to, the following steps:

[0307] Step 5: Management device B sends a vehicle information read message to vehicle a, and vehicle a receives the vehicle information read message accordingly.

[0308] When vehicle A is registered, the management department (management device A and management device B) can assign a digital identity to vehicle A. Before this, the management department will first obtain the necessary information of vehicle A. Optionally, this step can be performed by the management department through a dedicated handheld device (management device B) to read the vehicle information.

[0309] Optionally, the vehicle information reading message can be referred to the relevant description of "second message" in step S102 above, and will not be repeated here.

[0310] Step 6: Vehicle a sends a vehicle information response message to management device B. The vehicle information response message includes VINa and device certificate a. Accordingly, management device B receives the vehicle information response message.

[0311] After receiving the vehicle information read message sent by the handheld device (management device B), vehicle a responds by sending the VINa and the device certificate a of the component T-Box (assuming the component carrying the chip / dedicated environment is the vehicle terminal T-Box) to the handheld device. The device certificate a of the component T-Box is verified by the root certificate of vehicle manufacturer A.

[0312] Optionally, the vehicle information response message can be referred to the relevant description of "third message" in step S103 above, and will not be repeated here.

[0313] Step 7: Management device B interacts with management device A to obtain digital identity a.

[0314] The handheld device (management device B) interacts with the management platform (management device A) to obtain the digital identity a of vehicle a.

[0315] Step 8 (optional): The management device A interacts with the vehicle manufacturer A to confirm the binding relationship between VINa and device certificate a.

[0316] It is understandable that if step 4 above is not performed, then step 8 will be performed; otherwise, step 8 can be skipped.

[0317] Understandably, in step 8, the management platform (management device A) interacts with vehicle manufacturer A to confirm that the VINa and component T-Box equipment certificate a reported by vehicle a in step 6 are consistent with the information maintained by vehicle manufacturer A (i.e., vehicle a has not undergone unauthorized component replacement).

[0318] Step 9: Manage device A to maintain the correspondence between VINa, device certificate a, and digital identity a.

[0319] The management platform (managing device A) records, saves, and maintains the correspondence between VINa, device certificate a, and digital identity a.

[0320] Step 10: Management device B writes digital identity a to vehicle a, and vehicle a receives the digital identity a accordingly.

[0321] The handheld device (management device B) writes digital identity a into the chip / dedicated environment of vehicle a, and the legitimacy of digital identity a is verified by the root certificate of management device B.

[0322] The use of digital identity includes, but is not limited to, the following steps:

[0323] Step 11: Management device B sends a vehicle management message to vehicle a, and vehicle a receives the vehicle management message accordingly.

[0324] Assuming that roadside facilities are deployed at key locations such as intersections to interact with stored digital identity chips / dedicated environments, management device B (roadside facility) sends vehicle management messages to vehicle a.

[0325] Optionally, the vehicle management message can be referred to the relevant description of "Fourth Message" in step S106 above, which will not be repeated here.

[0326] Step 12: Vehicle a obtains the VINs of other components based on the configuration strategy and identifies them as VIN'.

[0327] Because the vehicle terminal T-Box stores the VINa and digital identity 'a', if this vehicle terminal T-Box is replaced in, for example, a vehicle b of the same brand and model, vehicle b can directly report the stored VINa and digital identity 'a', and the roadside infrastructure will not recognize that vehicle b has performed an unauthorized replacement operation. Similarly, if the vehicle terminal IVI of another vehicle c of the same brand and model stores a valid VIN and digital identity, and this vehicle terminal IVI from vehicle c is replaced in vehicle a, vehicle a can directly report the VIN and digital identity stored in the vehicle terminal IVI, and the roadside infrastructure will not recognize that vehicle a has performed an unauthorized replacement operation.

[0328] Therefore, vehicle a can obtain its stored VIN from other components based on a pre-configured strategy (such as obtaining it from a fixed component or randomly obtaining it from a component), and determine the VIN' to be reported later based on the obtained VIN (if the obtained VIN is the same as the VINa stored in the vehicle terminal T-Box, then VIN' is the obtained VIN or the VINa stored in the vehicle terminal; otherwise, VIN' is the obtained VIN).

[0329] Step 13: Vehicle a sends a vehicle management response message to management device B. The vehicle management response message includes digital identity a and VIN'. Accordingly, management device B receives the vehicle management response message.

[0330] Vehicle a sends its digital identity a and VIN' to the roadside facility (management device B).

[0331] Optionally, the vehicle management response message can be referred to the relevant description of "Fifth Message" in step S107 above, which will not be repeated here.

[0332] Step 14: Management device B sends a vehicle management confirmation message to vehicle a, and vehicle a receives the vehicle management confirmation message accordingly.

[0333] The roadside facility (management device B) determines the correspondence between digital identity a and VIN' based on the information maintained by the management department platform (management device A), and returns a confirmation message to vehicle a (management device A can quickly identify problematic vehicles and manage them).

[0334] Optionally, the vehicle management confirmation message can be found in the description of the "Sixth Message" in step S109 above, and will not be repeated here.

[0335] Step 15: Vehicle A's infotainment system displays an illegal parts replacement message.

[0336] Vehicle A may choose to provide a notification or not based on the message returned by the roadside facility (management equipment B). If the message returned by the roadside facility (management equipment B) indicates that vehicle A has engaged in unauthorized parts replacement, vehicle A should notify vehicle A of the unauthorized parts replacement through the vehicle's infotainment system or other means.

[0337] Through the embodiments of this application, in the scenario where vehicle a applies for a digital identity from management device A and management device B (management department), the device certificate a of the component T-Box of vehicle a and the VINa of vehicle a can be used as credentials when applying for a digital identity. This verifies the legality of the component T-Box of vehicle a and ensures the binding relationship between the component T-Box and vehicle a (or VINa), thereby verifying the legality of vehicle a. Furthermore, when vehicle a uses the digital identity a after obtaining a legal digital identity a for verification by management device A and management device B (management department), the VIN' stored in other components (other components different from the first component, such as IVI) can be used as the reporting source when vehicle a uses the digital identity a. This prevents the original legal digital identity a of vehicle a from being used when the component T-Box and / or component IVI are replaced or modified, ensuring the binding relationship between the component storing the digital identity a (component T-Box) and vehicle a, thereby verifying the legality of vehicle a. Furthermore, the entire verification process does not require extensive manual intervention, thus enabling intelligent vehicle verification and improving vehicle management efficiency.

[0338] This application also provides a vehicle management method, as detailed in Figure 4, which is a flowchart illustrating another vehicle management method provided in an embodiment of this application. This vehicle management method is applied in the field of vehicle authentication technology, such as vehicle management and / or vehicle management in scenarios involving digital identity application and / or digital identity usage.

[0339] It is understood that the steps in the embodiments of this application can be regarded as reasonable modifications or supplements to the embodiments in Figures 1, 2 and 3 above; or, it is understood that the vehicle management method in the embodiments of this application can also be regarded as an embodiment that can be executed independently, and this application does not limit it.

[0340] Specifically, this vehicle management method is applied to a vehicle management system, which includes vehicle a, vehicle factory A, management device A, and management device B. It is understood that the vehicle management system involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the vehicle management system involved in the vehicle management method shown in Figure 1 above; vehicle a involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the first vehicle involved in the vehicle management method shown in Figure 1 above; vehicle factory A involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the first vehicle factory involved in the vehicle management method shown in Figure 1 above; and management device A (which may be a computer device) and management device B (which may be a roadside device or a handheld device, etc., used to communicate with management device A and vehicle a) involved in the vehicle management method provided in this application embodiment can refer to the relevant description of the management device involved in the vehicle management method shown in Figure 1 above, and will not be repeated here.

[0341] The vehicle management method is mainly divided into the vehicle production stage, the digital identity application stage, and the digital identity usage stage.

[0342] The vehicle production stage includes, but is not limited to, the following steps:

[0343] Step 1a: Car factory A saves and manages the root certificate of device A.

[0344] The steps are the same as those in step 1a in Figure 3 above, and will not be repeated here.

[0345] Step 1b: Manage device A to save the root certificate of vehicle manufacturer A.

[0346] The steps are the same as step 1b in Figure 3 above, and will not be repeated here.

[0347] Step 2: Vehicle manufacturer A assigns a VINa to vehicle a and maintains the correspondence between the VINa and equipment certificate a.

[0348] The steps are the same as step 2 in Figure 3 above, and will not be repeated here.

[0349] Step 3: Vehicle manufacturer A sends VINa, device certificate a, and root certificate of management device A to vehicle a. Accordingly, vehicle a receives the VINa, device certificate a, and root certificate of management device A.

[0350] The steps are the same as step 3 in Figure 3 above, and will not be repeated here.

[0351] Step 4 (optional): Vehicle manufacturer A files VINa and equipment certificate a.

[0352] The steps are the same as step 4 in Figure 3 above, and will not be repeated here.

[0353] The digital identity application process includes, but is not limited to, the following steps:

[0354] Step 5: Management device B sends a vehicle information read message to vehicle a, and vehicle a receives the vehicle information read message accordingly.

[0355] The steps are the same as step 5 in Figure 3 above, and will not be repeated here.

[0356] Step 6: Vehicle a sends a vehicle information response message to management device B. The vehicle information response message includes VINa and device certificate a. Accordingly, management device B receives the vehicle information response message.

[0357] The steps are the same as step 6 in Figure 3 above, and will not be repeated here.

[0358] Step 7: Management device B interacts with management device A to obtain digital identity a.

[0359] The steps are the same as step 7 in Figure 3 above, and will not be repeated here.

[0360] Step 8 (optional): The management device A interacts with the vehicle manufacturer A to confirm the binding relationship between VINa and device certificate a.

[0361] The steps are the same as step 8 in Figure 3 above, and will not be repeated here.

[0362] Step 9: Manage device A to maintain the correspondence between VINa, device certificate a, and digital identity a.

[0363] The steps are the same as step 9 in Figure 3 above, and will not be repeated here.

[0364] Step 10: Management device B writes digital identity a to vehicle a, and vehicle a receives the digital identity a accordingly.

[0365] The steps are the same as in step 10 of Figure 3 above, and will not be repeated here.

[0366] The use of digital identity includes, but is not limited to, the following steps:

[0367] Step 11: Management device B sends a vehicle management message to vehicle a, which includes instruction information. Accordingly, vehicle a receives the vehicle management message.

[0368] Assuming that roadside facilities for interacting with stored digital identity chips / dedicated environments are deployed at key locations such as intersections, management device B (roadside facility) sends a vehicle management message to vehicle a. This vehicle management message carries instruction information, which instructs vehicle a to determine in step 12 which component to retrieve its stored VIN.

[0369] Optionally, the vehicle management message can be referred to the relevant description of "Fourth Message" in step S106 above, which will not be repeated here.

[0370] Step 12: Vehicle a obtains the VINs of other components based on the configuration strategy and identifies them as VIN'.

[0371] Because the vehicle terminal T-Box stores the VINa and digital identity 'a', if this vehicle terminal T-Box is replaced in, for example, a vehicle b of the same brand and model, vehicle b can directly report the stored VINa and digital identity 'a', and the roadside infrastructure will not recognize that vehicle b has performed an unauthorized replacement operation. Similarly, if the vehicle terminal IVI of another vehicle c of the same brand and model stores a valid VIN and digital identity, and this vehicle terminal IVI from vehicle c is replaced in vehicle a, vehicle a can directly report the VIN and digital identity stored in the vehicle terminal IVI, and the roadside infrastructure will not recognize that vehicle a has performed an unauthorized replacement operation.

[0372] Therefore, vehicle a can determine, based on the instruction information included in the received vehicle management message, to obtain the VIN stored in the corresponding component (such as the instruction information indicating that it is obtained from a certain component), and determine the VIN' to be reported subsequently based on the obtained VIN (if the obtained VIN is the same as the VINa stored in the vehicle terminal T-Box, then VIN' is the obtained VIN or the VINa stored in the vehicle terminal; otherwise, VIN' is the obtained VIN).

[0373] Step 13: Vehicle a sends a vehicle management response message to management device B. The vehicle management response message includes digital identity a and VIN'. Accordingly, management device B receives the vehicle management response message.

[0374] The steps are the same as in step 13 of Figure 3 above, and will not be repeated here.

[0375] Step 14: Management device B sends a vehicle management confirmation message to vehicle a, and vehicle a receives the vehicle management confirmation message accordingly.

[0376] The steps are the same as in step 14 of Figure 3 above, and will not be repeated here.

[0377] Step 15: Vehicle A's infotainment system displays an illegal parts replacement message.

[0378] The steps are the same as in step 15 of Figure 3 above, and will not be repeated here.

[0379] Through the embodiments of this application, in the scenario where vehicle a applies for a digital identity from management device A and management device B (management department), the device certificate a of the component T-Box of vehicle a and the VINa of vehicle a can be used as credentials when applying for a digital identity. This verifies the legality of the component T-Box of vehicle a and ensures the binding relationship between the component T-Box and vehicle a (or VINa), thereby verifying the legality of vehicle a. Furthermore, when vehicle a uses the digital identity a after obtaining a legal digital identity a for verification by management device A and management device B (management department), the VIN' stored in other components (other components different from the first component, such as IVI) can be used as the reporting source when vehicle a uses the digital identity a. This prevents the original legal digital identity a of vehicle a from being used when the component T-Box and / or component IVI are replaced or modified, ensuring the binding relationship between the component storing the digital identity a (component T-Box) and vehicle a, thereby verifying the legality of vehicle a. Furthermore, the entire verification process does not require extensive manual intervention, thus enabling intelligent vehicle verification and improving vehicle management efficiency.

[0380] The methods of the embodiments of this application have been described in detail above. The following provides an apparatus for implementing any one of the methods in the embodiments of this application. For example, an apparatus is provided that includes a unit (or means) for implementing the steps performed by the device in any of the above methods.

[0381] Please refer to Figure 5, which is a structural schematic diagram of a first vehicle provided in an embodiment of this application.

[0382] As shown in Figure 5, the first vehicle 50 may include a communication unit 501 and a processing unit 502. The communication unit 501 and the processing unit 502 may be software, hardware, or a combination of software and hardware.

[0383] The communication unit 501 can implement sending and / or receiving functions, and can also be described as a transceiver unit. The communication unit 501 can also be a unit integrating an acquisition unit and a sending unit, wherein the acquisition unit is used to implement the receiving function, and the sending unit is used to implement the sending function. Optionally, the communication unit 501 can be used to receive information sent by other devices, and can also be used to send information to other devices.

[0384] In one possible design, the first vehicle 50 may correspond to the first vehicle in the method embodiments shown in Figures 1 to 4 above. For example, the first vehicle 50 may be an electronic device or a chip within the electronic device. The first vehicle 50 may include units for performing the operations performed by the first vehicle in the method embodiments shown in Figures 1 to 4 above, and each unit in the first vehicle 50 is for implementing the operations performed by the first vehicle in the method embodiments shown in Figures 1 to 4 above. The descriptions of each unit are as follows:

[0385] The communication unit 501 is used to receive a first message, which includes a first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to a first vehicle by a first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes a device certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate is used to verify the legitimacy of the first component. A first correspondence exists between the first VIN and the first certificate, and this first correspondence is used to verify the legitimacy of the first vehicle.

[0386] The communication unit 501 is also used to receive a second message, which is used to request vehicle information of the first vehicle;

[0387] The processing unit 502 is configured to send a third message through the communication unit 501 in response to the second message. The third message includes a first vehicle identification number and a first certificate.

[0388] Regarding the communication unit 501 and processing unit 502 described in this design, the steps they perform can be referred to the implementation corresponding to the first vehicle in the method embodiments shown in Figures 1 to 4 above.

[0389] Regarding the technical effects of the implementation methods performed by the communication unit 501 and processing unit 502 described in this design, please refer to the description of the technical effects corresponding to the method embodiments shown in Figures 1 to 4 above.

[0390] According to embodiments of this application, the various units in the device shown in FIG5 can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effect of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the electronic device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0391] It should be noted that the implementation of each unit can also refer to the corresponding descriptions of the method embodiments shown in Figures 1 to 4 above.

[0392] In the first vehicle 50 described in Figure 5, vehicle management efficiency can be improved.

[0393] Please refer to Figure 6, which is a structural schematic diagram of a management device provided in an embodiment of this application.

[0394] As shown in Figure 6, the management device 60 may include a communication unit 601 and a processing unit 602. The communication unit 601 and the processing unit 602 may be software, hardware, or a combination of software and hardware.

[0395] The communication unit 601 can implement sending and / or receiving functions, and can also be described as a transceiver unit. The communication unit 601 can also be a unit integrating an acquisition unit and a sending unit, wherein the acquisition unit is used to implement the receiving function, and the sending unit is used to implement the sending function. Optionally, the communication unit 601 can be used to receive information sent by other devices, and can also be used to send information to other devices.

[0396] In one possible design, the management device 60 may correspond to the management device in the method embodiments shown in Figures 1 to 4 above. For example, the management device 60 may be an electronic device or a chip within an electronic device. The management device 60 may include units for performing the operations performed by the management device in the method embodiments shown in Figures 1 to 4 above, and each unit in the management device 60 is for implementing the operations performed by the management device in the method embodiments shown in Figures 1 to 4 above. The descriptions of each unit are as follows:

[0397] The communication unit 601 is used to send a second message to the first vehicle, the second message being used to request vehicle information of the first vehicle;

[0398] The communication unit 601 is further configured to receive a third message from the first vehicle, the third message including a first vehicle identification number (VIN) and a first certificate; wherein, the first VIN is a VIN assigned to the first vehicle by a first vehicle manufacturer, the first vehicle manufacturer being the manufacturer that produces the first vehicle, the first certificate including an equipment certificate corresponding to a first component of the first vehicle, the first certificate being issued based on the root certificate of the first vehicle manufacturer, the first certificate being used to verify the legitimacy of the first component, and a first correspondence relationship existing between the first VIN and the first certificate, the first correspondence relationship being used to verify the legitimacy of the first vehicle.

[0399] In one possible implementation, the processing unit 602 is configured to verify the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and to verify the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate.

[0400] Regarding the communication unit 601 and processing unit 602 described in this design, the steps they perform can be referred to the implementation methods corresponding to the management devices in the method embodiments shown in Figures 1 to 4 above.

[0401] Regarding the technical effects of the implementation methods performed by the communication unit 601 and processing unit 602 described in this design, please refer to the description of the technical effects corresponding to the method embodiments shown in Figures 1 to 4 above.

[0402] According to embodiments of this application, the various units in the device shown in FIG6 can be individually or entirely merged into one or more other units, or some of the units can be further divided into multiple functionally smaller units. This achieves the same operation without affecting the technical effect of the embodiments of this application. The above units are based on logical function division. In practical applications, the function of one unit can also be implemented by multiple units, or the function of multiple units can be implemented by one unit. In other embodiments of this application, the electronic device may also include other units. In practical applications, these functions can also be implemented with the assistance of other units, and can be implemented collaboratively by multiple units.

[0403] It should be noted that the implementation of each unit can also refer to the corresponding descriptions of the method embodiments shown in Figures 1 to 4 above.

[0404] The management device 60 described in Figure 6 can improve vehicle management efficiency.

[0405] If the first vehicle 50 and / or management device 60 mentioned above can be electronic devices, please refer to the structural schematic diagram of the electronic device shown in Figure 7.

[0406] It should be understood that the electronic device 70 shown in FIG7 is only an example. The electronic device in the embodiments of this application may also include other components, or include components with functions similar to the various components in FIG7, or may not include all the components in FIG7.

[0407] Electronic device 70 includes a transceiver interface 701 and at least one processor 702.

[0408] The electronic device 70 may correspond to the first vehicle 50 and / or the management device 60. A transceiver interface 701 is used for transmitting and receiving signals, and at least one processor 702 executes program instructions, causing the electronic device 70 to implement the corresponding flow of the method executed by the corresponding device in the above method embodiments.

[0409] In one possible design, the electronic device 70 may correspond to the first vehicle in the method embodiments shown in Figures 1 to 4 above. For example, the electronic device 70 may be the first vehicle itself, or it may be a chip within the first vehicle. The electronic device 70 may include components for performing the operations performed by the first vehicle in the above method embodiments, and each component in the electronic device 70 is specifically designed to implement the operations performed by the first vehicle in the above method embodiments. Specifically, it may be as follows:

[0410] The transceiver interface 701 is used to receive a first message, which includes a first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes a device certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate is used to verify the legitimacy of the first component. A first correspondence exists between the first VIN and the first certificate, and this first correspondence is used to verify the legitimacy of the first vehicle.

[0411] The transceiver interface 701 is also used to receive a second message, which is used to request vehicle information of the first vehicle.

[0412] The processor 702 is configured to send a third message via the transceiver interface 701 in response to the second message, the third message including a first vehicle identification number and a first certificate.

[0413] Regarding the transceiver interface 701 and at least one processor 702 described in this design, the steps they perform can be referred to the implementation corresponding to the first vehicle in the method embodiments shown in Figures 1 to 4 above.

[0414] Regarding the technical effects of the implementation methods performed by the transceiver interface 701 and at least one processor 702 described in this design, please refer to the description of the technical effects corresponding to the method embodiments shown in Figures 1 to 4 above.

[0415] In another possible design, the electronic device 70 may correspond to the management device in the method embodiments shown in Figures 1 to 4 above. For example, the electronic device 70 may be a management device or a chip within a management device. The electronic device 70 may include components for performing the operations performed by the management device in the above method embodiments, and each component in the electronic device 70 is specifically designed to implement the operations performed by the management device in the above method embodiments. Specifically, it may be as follows:

[0416] The transceiver interface 701 is used to send a second message to the first vehicle. The second message is used to request the vehicle information of the first vehicle.

[0417] The transceiver interface 701 is further configured to receive a third message from the first vehicle, the third message including a first vehicle identification number (VIN) and a first certificate; wherein, the first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, the first vehicle manufacturer being the manufacturer that produces the first vehicle, the first certificate including an equipment certificate corresponding to a first component of the first vehicle, the first certificate being issued based on the root certificate of the first vehicle manufacturer, the first certificate being used to verify the legitimacy of the first component, and a first correspondence relationship existing between the first VIN and the first certificate, the first correspondence relationship being used to verify the legitimacy of the first vehicle.

[0418] In one possible implementation, the processor 702 is configured to verify the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and to verify the legitimacy of the first vehicle based on a first correspondence between the first vehicle identification number and the first certificate.

[0419] Regarding the transceiver interface 701 and at least one processor 702 described in this design, the steps performed can be referred to the implementation corresponding to the management device in the method embodiments shown in Figures 1 to 4 above.

[0420] Regarding the technical effects of the implementation methods performed by the transceiver interface 701 and at least one processor 702 described in this design, please refer to the description of the technical effects corresponding to the method embodiments shown in Figures 1 to 4 above.

[0421] The electronic device 70 described in Figure 7 can improve vehicle management efficiency.

[0422] If the first vehicle 50 and / or management device 60 can be a chip or a chip system, please refer to the schematic diagram of the chip structure shown in Figure 8.

[0423] As shown in Figure 8, chip 80 includes a processor 801 and an interface 802. The number of processors 801 can be one or more, and the number of interfaces 802 can be multiple. It should be noted that the functions of the processor 801 and interface 802 can be implemented through hardware design, software design, or a combination of both; no restrictions are placed here.

[0424] Optionally, chip 80 may also include memory 803 for storing necessary program instructions and data.

[0425] In this application, processor 801 can be used to call the implementation program of the vehicle management method provided in one or more embodiments of this application in the first vehicle 50 and / or management device 60 from memory 803, and execute the instructions included in the program. Interface 802 can be used to output the execution results of processor 801. In this application, interface 802 can be specifically used to output various messages or information of processor 801.

[0426] For the vehicle management method provided by one or more embodiments of this application, please refer to the various embodiments shown in Figures 1 to 4 above, which will not be repeated here.

[0427] The processor in this application embodiment can be a central processing unit (CPU), but it can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0428] The memory in this application embodiment is used to provide storage space, in which data such as operating system and computer programs can be stored. The memory includes, but is not limited to, random access memory (RAM), read-only memory (ROM), erasable programmable read-only memory (EPROM), or compact disc read-only memory (CD-ROM).

[0429] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer-readable storage medium storing a computer program. When the computer program is run on one or more processors, it can implement the method shown in Figures 1 to 4.

[0430] According to the method provided in the embodiments of this application, the embodiments of this application also provide a computer program product, which includes a computer program. When the computer program runs on a processor, it can implement the methods shown in Figures 1 to 4.

[0431] This application provides a vehicle management system, which includes a first vehicle and management equipment.

[0432] The first vehicle is used to perform the method as shown in Figures 1 to 4 above, and the management device is used to perform the method as shown in Figures 1 to 4 above.

[0433] Optionally, the first vehicle mentioned above is a vehicle in a broad sense, which can be a means of transportation, such as a car, truck, aircraft, drone, slow transport vehicle, spacecraft, or ship, etc., and this application embodiment does not limit this.

[0434] This application also provides a processing apparatus, including a processor and an interface; the processor is used to execute the method in any of the above method embodiments.

[0435] It should be understood that the above-described processing device can be a chip. The units in the various device embodiments and the electronic devices in the method embodiments correspond completely, with corresponding modules or units executing corresponding steps. For example, the communication unit (transceiver) executes the receiving or sending steps in the method embodiments, while other steps besides sending and receiving can be executed by the processing unit (processor). The specific functions of each unit can be found in the corresponding method embodiments. There can be one or more processors.

[0436] It is understood that in the embodiments of this application, the electronic device may perform some or all of the steps in the embodiments of this application. These steps or operations are merely examples, and the embodiments of this application may also perform other operations or variations thereof. Furthermore, the steps may be performed in different orders as presented in the embodiments of this application, and it is not necessarily necessary to perform all the operations in the embodiments of this application.

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

[0438] The units described 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 can be selected to achieve the purpose of this embodiment according to actual needs.

[0439] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0440] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the contributing part, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0441] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any changes 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.

Claims

A vehicle management method, characterized in that, Applied to a vehicle management system, the vehicle management system includes a first vehicle and management equipment; the vehicle management method includes: The first vehicle receives a first message, which includes a first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes a device certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer and is used to verify the legitimacy of the first component. A first correspondence exists between the first VIN and the first certificate, and this first correspondence is used to verify the legitimacy of the first vehicle. The management device sends a second message to the first vehicle, the second message being used to request the vehicle information of the first vehicle; In response to the second message, the first vehicle sends a third message to the management device, the third message including the first vehicle identification number and the first certificate. The vehicle management method according to claim 1 is characterized in that, The vehicle management method also includes: The management device verifies the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and verifies the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate. The vehicle management method according to claim 2 is characterized in that, The verification of the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate includes: The management device verifies the legitimacy of the first vehicle after verifying the validity of the first certificate and the correctness of the first correspondence; or... If the management device verifies that the first certificate is invalid or that the first correspondence is incorrect, it verifies that the first vehicle is invalid. The vehicle management method according to claim 2 or 3 is characterized in that, The vehicle management method also includes: When the management device verifies the legitimacy of the first vehicle, it issues a first digital identity to the first vehicle based on the root certificate of the management device. The first digital identity is used to verify the legitimacy of the first vehicle. The vehicle management method according to claim 4 is characterized in that, The first message also includes the root certificate of the management device; the vehicle management method further includes: The first vehicle verifies the legitimacy of the first digital identity based on the root certificate of the management device; If the first vehicle verifies that the first digital identity is legitimate, it writes the first digital identity into the system. The vehicle management method according to claim 4 or 5 is characterized in that, The first digital identity and / or the first vehicle identification number are stored in the first component. The vehicle management method according to any one of claims 4 to 6 is characterized in that, There is a second correspondence between the first digital identity and the first vehicle identification number, and the second correspondence is used to verify the legitimacy of the first vehicle. The vehicle management method according to any one of claims 4 to 7 is characterized in that, The vehicle management method also includes: The management device sends a fourth message to the first vehicle, the fourth message being used to request management of the first vehicle; In response to the fourth message, the first vehicle sends a fifth message to the management device. The fifth message includes the first digital identity and the second vehicle identification number. The second vehicle identification number is a vehicle identification number stored in a second component of the first vehicle. The first component and the second component are different components in the first vehicle. The vehicle management method according to claim 8 is characterized in that, The vehicle management method also includes: In response to the fourth message, the first vehicle obtains the second vehicle identification number stored in the second component based on a pre-configured first strategy. The vehicle management method according to claim 8 is characterized in that, The fourth message is also used to instruct the second component; The aforementioned vehicle management methods also include: The first vehicle responds to the fourth message and retrieves the second vehicle identification number stored in the second component based on the instruction of the fourth message. The vehicle management method according to any one of claims 8 to 10 is characterized in that, The vehicle management method also includes: The management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number. The vehicle management method according to claim 11 is characterized in that, The management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number, including: The management device verifies the legitimacy of the first vehicle if the second and third correspondences are identical; or... If the management device verifies that the second correspondence and the third correspondence are different, it verifies that the first vehicle is illegal. The vehicle management method according to claim 11 or 12 is characterized in that, The vehicle management method also includes: The management device sends a sixth message to the first vehicle, the sixth message being used to indicate whether the first vehicle is legitimate or illegitimate; The first vehicle responds to the sixth message, indicating whether the first vehicle is legitimate or illegitimate. The vehicle management method according to any one of claims 1 to 13 is characterized in that, The first component includes at least one of the following: a vehicle terminal T-Box, and a vehicle interactive system (IVI). A vehicle management method, characterized in that, Applied to the first vehicle; The vehicle management method includes: The first vehicle receives a first message, which includes a first vehicle identification number (VIN) and a first certificate. The first VIN is a vehicle identification number assigned to the first vehicle by a first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate includes a device certificate corresponding to a first component of the first vehicle. The first certificate is issued based on the root certificate of the first vehicle manufacturer, which is the manufacturer that produces the first vehicle. The first certificate is used to verify the legitimacy of the first component. A first correspondence exists between the first VIN and the first certificate, and this first correspondence is used to verify the legitimacy of the first vehicle. The first vehicle receives a second message, which is used to request the vehicle information of the first vehicle; In response to the second message, the first vehicle sends a third message, which includes the first vehicle identification number and the first certificate. The vehicle management method according to claim 15 is characterized in that, The vehicle management method also includes: The first vehicle receives a first digital identity from the management device, the first digital identity being issued based on the root certificate of the management device, and the first digital identity being used to verify the legitimacy of the first vehicle. The vehicle management method according to claim 16 is characterized in that, The first message also includes the root certificate of the management device; the vehicle management method further includes: The first vehicle verifies the legitimacy of the first digital identity based on the root certificate of the management device; If the first vehicle verifies that the first digital identity is legitimate, it writes the first digital identity into the system. The vehicle management method according to claim 16 or 17 is characterized in that, The first digital identity and / or the first vehicle identification number are stored in the first component. The vehicle management method according to any one of claims 16 to 18 is characterized in that, There is a second correspondence between the first digital identity and the first vehicle identification number, and the second correspondence is used to verify the legitimacy of the first vehicle. The vehicle management method according to any one of claims 16 to 19 is characterized in that, The vehicle management method also includes: The first vehicle receives a fourth message from the management device, the fourth message being used to request management of the first vehicle; In response to the fourth message, the first vehicle sends a fifth message to the management device. The fifth message includes the first digital identity and the second vehicle identification number. The second vehicle identification number is a vehicle identification number stored in a second component of the first vehicle. The first component and the second component are different components in the first vehicle. The vehicle management method according to claim 20 is characterized in that, The vehicle management method also includes: In response to the fourth message, the first vehicle obtains the second vehicle identification number stored in the second component based on a pre-configured first strategy. The vehicle management method according to claim 20 is characterized in that, The fourth message is also used to instruct the second component; the vehicle management method further includes: The first vehicle responds to the fourth message and retrieves the second vehicle identification number stored in the second component based on the instruction of the fourth message. The vehicle management method according to any one of claims 20 to 22 is characterized in that, The second correspondence between the first digital identity and the first vehicle identification number and the third correspondence between the first digital identity and the second vehicle identification number are used to verify the legitimacy of the first vehicle. The vehicle management method according to claim 23 is characterized in that, The second correspondence between the first digital identity and the first vehicle identification number, and the third correspondence between the first digital identity and the second vehicle identification number, are used to verify the legitimacy of the first vehicle, including: The second correspondence and the third correspondence are the same, and the second correspondence and the third correspondence are used to verify the legitimacy of the first vehicle; or, The second correspondence is different from the third correspondence, and the second and third correspondences are used to verify that the first vehicle is illegal. The vehicle management method according to claim 23 or 24 is characterized in that, The vehicle management method also includes: The first vehicle receives a sixth message from the management device, the sixth message indicating whether the first vehicle is legitimate or illegitimate; The first vehicle responds to the sixth message, indicating whether the first vehicle is legitimate or illegitimate. The vehicle management method according to any one of claims 15 to 25 is characterized in that, The first component includes at least one of the following: a vehicle terminal T-Box, and a vehicle interactive system (IVI). A vehicle management method, characterized in that, Used in managing equipment; The vehicle management method includes: The management device sends a second message to the first vehicle, the second message being used to request the vehicle information of the first vehicle; The management device receives a third message from the first vehicle, the third message including a first vehicle identification number (VIN) and a first certificate; wherein, the first VIN is a VIN assigned to the first vehicle by a first vehicle manufacturer, the first vehicle manufacturer being the manufacturer that produces the first vehicle, the first certificate including a device certificate corresponding to a first component of the first vehicle, the first certificate being issued based on the root certificate of the first vehicle manufacturer, the first certificate being used to verify the legitimacy of the first component, and a first correspondence relationship existing between the first VIN and the first certificate, the first correspondence relationship being used to verify the legitimacy of the first vehicle. The vehicle management method according to claim 27 is characterized in that, The vehicle management method also includes: The management device verifies the legitimacy of the first certificate based on the root certificate of the first vehicle manufacturer, and verifies the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate. The vehicle management method according to claim 28 is characterized in that, The verification of the legitimacy of the first vehicle based on the first correspondence between the first vehicle identification number and the first certificate includes: The management device verifies the legitimacy of the first vehicle after verifying the validity of the first certificate and the correctness of the first correspondence; or... If the management device verifies that the first certificate is invalid or that the first correspondence is incorrect, it will verify that the first vehicle is not... Law. The vehicle management method according to claim 28 or 29 is characterized in that, The vehicle management method also includes: When the management device verifies the legitimacy of the first vehicle, it issues a first digital identity to the first vehicle based on the root certificate of the management device. The first digital identity is used to verify the legitimacy of the first vehicle. The vehicle management method according to claim 30 is characterized in that, The first digital identity and / or the first vehicle identification number are stored in the first component. The vehicle management method according to any one of claims 30 or 31 is characterized in that, There is a second correspondence between the first digital identity and the first vehicle identification number, and the second correspondence is used to verify the legitimacy of the first vehicle. The vehicle management method according to any one of claims 30 to 32 is characterized in that, The vehicle management method also includes: The management device sends a fourth message to the first vehicle, the fourth message being used to request management of the first vehicle; The management device receives a fifth message from the first vehicle, the fifth message including the first digital identity and the second vehicle identification number; wherein the second vehicle identification number is a vehicle identification number stored in a second component of the first vehicle, and the first component and the second component are different components in the first vehicle. The vehicle management method according to claim 33 is characterized in that, The fourth message is also used to request the second vehicle identification number stored in the second component. The vehicle management method according to claim 33 or 34 is characterized in that, The vehicle management method also includes: The management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number. The vehicle management method according to claim 35 is characterized in that, The management device verifies the legitimacy of the first vehicle based on a second correspondence between the first digital identity and the first vehicle identification number and a third correspondence between the first digital identity and the second vehicle identification number, including: The management device verifies the legitimacy of the first vehicle if the second and third correspondences are identical; or... If the management device verifies that the second correspondence and the third correspondence are different, it verifies that the first vehicle is illegal. The vehicle management method according to claim 35 or 36 is characterized in that, The vehicle management method also includes: The management device sends a sixth message to the first vehicle, the sixth message being used to indicate whether the first vehicle is legitimate or illegitimate. The vehicle management method according to any one of claims 27 to 37 is characterized in that, The first component includes at least one of the following: a vehicle terminal T-Box, and a vehicle interactive system (IVI). A vehicle characterized in that, Includes units for performing the method as described in any one of claims 15 to 26. A management device, characterized in that, Includes units for performing the method as described in any one of claims 27 to 38. An electronic device, characterized in that, Includes a processor for performing the method as claimed in any one of claims 15 to 26 or 27 to 38. A chip characterized in that, It includes logic circuits and interfaces, wherein the logic circuits and the interfaces are coupled; The interface is used for inputting and / or outputting information, and the logic circuit is used for performing the method as described in any one of claims 15 to 26 or 27 to 38. A vehicle management system, characterized in that, Including the first vehicle and management equipment; Wherein, the first vehicle is used to perform the method performed by the first vehicle as claimed in claims 1 to 14, and the management device is used to perform the method performed by the management device as claimed in claims 1 to 14. A computer-readable storage medium, characterized in that, The computer-readable storage medium is used to store a computer program, which, when executed, performs the method as described in any one of claims 1 to 38. A computer program product, characterized in that, The computer program product includes a computer program, which, when executed, performs the method as described in any one of claims 1 to 38.

Images