Method and device for managing identification of connected vehicle equipment

Abstract

The present disclosure discloses a method and apparatus for managing identification of Internet of Vehicles devices, which are used to solve the problem that there is no unified identification management of Internet of Vehicles devices under related technologies. The method is as follows: a V2X device management subject sends a configuration request containing device parameters of an Internet of Vehicles device to a VID registration agency to obtain an identification of the Internet of Vehicles device, and then based on the identification of the Internet of Vehicles device, obtains a corresponding identification authentication key of the Internet of Vehicles device from a VID authentication agency, and writes the identification of the Internet of Vehicles device and the identification authentication key of the Internet of Vehicles device into the Internet of Vehicles device; in this way, an identification management and authentication architecture of Internet of Vehicles devices that conforms to actual application scenarios is constructed, and the V2X device management subject coordinates the management of various V2X devices. In combination with the above architecture, the management mechanism of Internet of Vehicles devices and the identification coding standard of Internet of Vehicles devices can be unified, which is more conducive to large-scale application and intercommunication of Internet of Vehicles.

Description

Technical Field

[0001] The present disclosure relates to the field of communication technology, and in particular to a method and device for managing identification of connected vehicle equipment. Background Art

[0002] With the gradual development of the Internet of Things technology, vehicle to everything (V2X) wireless communication technology (i.e., vehicle networking technology) has also been developed accordingly. Vehicle networking technology is a new generation of information and communication technology that achieves all-round network connection within the car, between cars, between cars and roads, between cars and people, and between cars and service platforms, improving the level of car intelligence and autonomous driving capabilities, building a new form of car and transportation services, thereby improving traffic efficiency, improving car driving experience, and providing users with intelligent, comfortable, safe, energy-saving, and efficient comprehensive services.

[0003] Under the relevant technology, major manufacturers are building their own Internet of Vehicles platforms. As a result, devices produced by different equipment manufacturers and devices belonging to different Internet of Vehicles application service providers have appeared in the Internet of Vehicles. Correspondingly, there are also many Internet of Vehicles equipment identifiers. Since the Internet of Vehicles equipment identifier is the information stored in the Internet of Vehicles equipment that uniquely identifies the Internet of Vehicles equipment, and the above information contains the specific equipment parameter information of each Internet of Vehicles equipment, in order to protect their own interests, major manufacturers will not share their own Internet of Vehicles equipment identifier management methods and encoding methods. Therefore, there is confusion in the management of Internet of Vehicles equipment identifiers and inconsistency in the Internet of Vehicles equipment identifier encoding standards.

[0004] Furthermore, due to the confusion in the management of IoV equipment identification and the lack of uniformity in IoV equipment identification coding standards, the following two problems arise when IoV equipment applies for IoV equipment certification: (1) IoV application service providers need to customize an authentication method for each type of IoV equipment identification; (2) Equipment from different manufacturers or operators cannot be authenticated.

[0005] It can be seen from this that a new technical solution needs to be designed to overcome the above-mentioned defects. Summary of the invention

[0006] The present disclosure provides a method and apparatus for managing identification of an Internet of Vehicles device, so as to solve the problem that there is no unified identification management of Internet of Vehicles device in the related art.

[0007] The specific technical solutions provided by the embodiments of the present disclosure are as follows:

[0008] In a first aspect, a method for managing identification of an Internet of Vehicles device includes:

[0009] The V2X device management entity sends a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0010] The V2X device management entity obtains a vehicle networking device identifier corresponding to the vehicle networking device fed back by the VID registration agency based on the device parameters;

[0011] The V2X device management entity obtains the corresponding vehicle networking device identification authentication key from the VID authentication agency based on the vehicle networking device identification;

[0012] The V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device.

[0013] Optionally, the device parameters of the Internet of Vehicles device include at least any one or combination of the following information:

[0014] The device manufacturer of the Internet of Vehicles device;

[0015] The device category of the Internet of Vehicles device;

[0016] The device model of the Internet of Vehicles device;

[0017] The product serial number of the Internet of Vehicles device.

[0018] Optionally, the V2X device management entity obtains a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency based on the Internet of Vehicles device identification, including:

[0019] receiving a vehicle networking device identification authentication key issued by the VID authentication agency based on the vehicle networking device identification, wherein the vehicle networking device identification is sent to the VID authentication agency by the VID registration agency; or

[0020] Send a vehicle networking device identification authentication key request carrying the vehicle networking device identification to the VID authentication agency, and receive a corresponding vehicle networking device identification authentication key issued by the VID authentication agency.

[0021] Optionally, the V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device, including:

[0022] Writing the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device identification card VIM included in the Internet of Vehicles device; or,

[0023] The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into a security module included in the Internet of Vehicles device, wherein the security module is used to securely store the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key.

[0024] In a second aspect, a method for managing identification of an Internet of Vehicles device includes:

[0025] The vehicle networking device identification VID registration agency receives a configuration request sent by the vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0026] The VID registration agency generates a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy;

[0027] The VID registration agency feeds back the Internet of Vehicles device identifier corresponding to the Internet of Vehicles device to the V2X device management entity;

[0028] The VID registration agency sends the Internet of Vehicles device identifier to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identifier authentication key based on the Internet of Vehicles device identifier, and sends the Internet of Vehicles device identifier authentication key to the V2X device management entity.

[0029] Optionally, the device parameters of the Internet of Vehicles device include at least any one or combination of the following information:

[0030] The device manufacturer of the Internet of Vehicles device;

[0031] The device category of the Internet of Vehicles device;

[0032] The device model of the Internet of Vehicles device;

[0033] The product serial number of the Internet of Vehicles device.

[0034] Optionally, after the VID registration agency generates a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy, the method further includes:

[0035] The Internet of Vehicles device identifier is sent to a V2X service entity, so that the V2X service entity uniquely identifies the Internet of Vehicles device based on the Internet of Vehicles device identifier.

[0036] In a third aspect, a method for managing identification of an Internet of Vehicles device includes:

[0037] The vehicle networking device identification VID authentication agency receives the vehicle networking device identification sent by the VID registration agency, where the vehicle networking device identification is generated by the VID registration agency based on the device parameters of the vehicle networking device in the configuration request sent by the vehicle networking V2X device management entity and according to the vehicle networking device identification generation strategy;

[0038] The VID authentication agency generates a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification;

[0039] The VID authentication agency sends the vehicle networking device identification authentication key to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

[0040] Optionally, the VID authentication agency sends the Internet of Vehicles device identification authentication key to the V2X device management entity, including:

[0041] Based on the IoV device identification, directly send the corresponding IoV device identification authentication key to the V2X device management entity; or,

[0042] In response to the vehicle networking device identity authentication key request sent by the V2X device management entity, the vehicle networking device identity authentication key is sent to the V2X device management entity, wherein the vehicle networking device identity authentication key request includes the vehicle networking device identity.

[0043] In a fourth aspect, a method for managing identification of an Internet of Vehicles device includes:

[0044] The vehicle networking device identification VID authentication function entity receives an authentication request sent by the vehicle networking device, wherein the authentication request at least includes the vehicle networking device identification;

[0045] The VID authentication function entity sends an authentication vector request to the VID authentication authority, wherein the authentication vector request at least includes the Internet of Vehicles device identifier;

[0046] The VID authentication function entity receives the authentication vector sent by the VID authentication agency, and sends the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key;

[0047] The VID authentication function entity receives the authentication response parameters fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameters are generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

[0048] Optionally, the VID authentication function entity receives an authentication response parameter fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key, including:

[0049] Receiving authentication response parameters fed back by the Internet of Vehicles device;

[0050] Based on the authentication response parameter, perform corresponding operations with other parameters included in the authentication vector;

[0051] If the information obtained based on the operation is the same as the ciphertext information included in the authentication vector, it is determined that the authentication result representation is passed.

[0052] In a fifth aspect, a method for managing identification of an Internet of Vehicles device includes:

[0053] The vehicle networking V2X device sends an authentication request to the vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification;

[0054] The V2X device receives the authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on the authentication vector fed back by the VID authentication authority;

[0055] The V2X device determines the corresponding authentication response parameter based on the authentication parameter and according to the stored vehicle networking device identification authentication key; and sends the authentication response parameter to the VID authentication function entity;

[0056] The V2X device receives a service response from the V2X service entity, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

[0057] According to a sixth aspect, a computer device comprises:

[0058] A memory for storing executable instructions;

[0059] The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes:

[0060] Sending a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0061] Obtaining a connected vehicle device identifier corresponding to the connected vehicle device fed back by the VID registration agency based on the device parameters;

[0062] Based on the IoV device identification, obtaining a corresponding IoV device identification authentication key from a VID authentication agency;

[0063] The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into the Internet of Vehicles device.

[0064] Optionally, the device parameters of the Internet of Vehicles device include at least any one or combination of the following information:

[0065] The device manufacturer of the Internet of Vehicles device;

[0066] The device category of the Internet of Vehicles device;

[0067] The device model of the Internet of Vehicles device;

[0068] The product serial number of the Internet of Vehicles device.

[0069] Optionally, the V2X device management entity obtains a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency based on the Internet of Vehicles device identification, and the processor is used to:

[0070] receiving a vehicle networking device identification authentication key issued by the VID authentication agency based on the vehicle networking device identification, wherein the vehicle networking device identification is sent to the VID authentication agency by the VID registration agency; or

[0071] Send a vehicle networking device identification authentication key request carrying the vehicle networking device identification to the VID authentication agency, and receive a corresponding vehicle networking device identification authentication key issued by the VID authentication agency.

[0072] Optionally, the V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device, and the processor is used to:

[0073] Writing the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device identification card VIM included in the Internet of Vehicles device; or,

[0074] The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into a security module included in the Internet of Vehicles device, wherein the security module is used to securely store the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key.

[0075] A seventh aspect is a network device, comprising:

[0076] A memory for storing executable instructions;

[0077] The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes:

[0078] Receiving a configuration request sent by a vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0079] Based on the device parameters of the Internet of Vehicles device, generating a corresponding Internet of Vehicles device identifier according to an Internet of Vehicles device identifier generation strategy;

[0080] Feedback the V2X device management entity with the V2X device identifier corresponding to the V2X device;

[0081] The Internet of Vehicles device identification is sent to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification, and sends the Internet of Vehicles device identification authentication key to a V2X device management entity.

[0082] Optionally, the device parameters of the Internet of Vehicles device include at least any one or combination of the following information:

[0083] The device manufacturer of the Internet of Vehicles device;

[0084] The device category of the Internet of Vehicles device;

[0085] The device model of the Internet of Vehicles device;

[0086] The product serial number of the Internet of Vehicles device.

[0087] Optionally, after the VID registration agency generates a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy, the processor is further configured to:

[0088] The Internet of Vehicles device identifier is sent to a V2X service entity, so that the V2X service entity uniquely identifies the Internet of Vehicles device based on the Internet of Vehicles device identifier.

[0089] According to an eighth aspect, a network device includes:

[0090] A memory for storing executable instructions;

[0091] The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes:

[0092] Receiving the vehicle networking device identifier sent by the VID registration agency, where the vehicle networking device identifier is generated by the VID registration agency based on the device parameters of the vehicle networking device in the configuration request sent by the vehicle networking V2X device management subject and according to the vehicle networking device identifier generation strategy;

[0093] Based on the Internet of Vehicles device identifier, generating a corresponding Internet of Vehicles device identifier authentication key;

[0094] The vehicle networking device identification authentication key is sent to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

[0095] Optionally, the VID authentication agency sends the Internet of Vehicles device identification authentication key to the V2X device management entity, and the processor is used to:

[0096] Based on the IoV device identification, directly send the corresponding IoV device identification authentication key to the V2X device management entity; or,

[0097] In response to the vehicle networking device identity authentication key request sent by the V2X device management entity, the vehicle networking device identity authentication key is sent to the V2X device management entity, wherein the vehicle networking device identity authentication key request includes the vehicle networking device identity.

[0098] A ninth aspect is a network device, comprising:

[0099] A memory for storing executable instructions;

[0100] The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes:

[0101] Receiving an authentication request sent by a connected vehicle device, wherein the authentication request at least includes an identification of the connected vehicle device;

[0102] Sending an authentication vector request to the VID authentication authority, wherein the authentication vector request at least includes the IoV device identifier;

[0103] Receiving the authentication vector sent by the VID authentication agency, and sending the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key;

[0104] Receive the authentication response parameter fed back by the Internet of Vehicles device, and determine the corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

[0105] Optionally, the VID authentication function entity receives an authentication response parameter fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key, and the processor is used to:

[0106] Receiving authentication response parameters fed back by the Internet of Vehicles device;

[0107] Based on the authentication response parameter, perform corresponding operations with other parameters included in the authentication vector;

[0108] If the information obtained based on the operation is the same as the ciphertext information included in the authentication vector, it is determined that the authentication result representation is passed.

[0109] A tenth aspect, a computer device, comprising:

[0110] A memory for storing executable instructions;

[0111] The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes:

[0112] Sending an authentication request to a vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification;

[0113] receiving an authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on an authentication vector fed back by the VID authentication authority;

[0114] Based on the authentication parameters, determining corresponding authentication response parameters according to the stored Internet of Vehicles device identification authentication key; and sending the authentication response parameters to the VID authentication function entity;

[0115] receiving a service response from the V2X service entity, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

[0116] In an eleventh aspect, a device for managing identification of an Internet of Vehicles device includes:

[0117] A sending unit, configured to send a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0118] A first acquisition unit, configured to acquire a connected vehicle device identifier corresponding to the connected vehicle device fed back by the VID registration agency based on the device parameter;

[0119] A second acquisition unit, configured to acquire a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency based on the Internet of Vehicles device identification;

[0120] A writing unit is used to write the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device, so that the VID authentication agency authenticates the Internet of Vehicles device based on the Internet of Vehicles device identifier.

[0121] In a twelfth aspect, a device for managing identification of an Internet of Vehicles device includes:

[0122] A receiving unit, configured to receive a configuration request sent by a vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0123] A generating unit, configured to generate a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy;

[0124] A feedback unit, configured to feed back a vehicle networking device identifier corresponding to the vehicle networking device to a V2X device management entity;

[0125] The sending unit is used to send the Internet of Vehicles device identifier to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identifier authentication key based on the Internet of Vehicles device identifier, and sends the Internet of Vehicles device identifier authentication key to a V2X device management entity.

[0126] In a thirteenth aspect, a device for managing identification of an Internet of Vehicles device includes:

[0127] a receiving unit, configured to receive the vehicle networking device identifier sent by the VID registration agency, wherein the vehicle networking device identifier is generated by the VID registration agency based on the device parameters of the vehicle networking device in the configuration request sent by the vehicle networking V2X device management subject and according to the vehicle networking device identifier generation strategy;

[0128] A generating unit, configured to generate a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification;

[0129] The sending unit is used to send the vehicle networking device identification authentication key to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

[0130] In a fourteenth aspect, a device for managing identification of an Internet of Vehicles device includes:

[0131] A first receiving unit, configured to receive an authentication request sent by an Internet of Vehicles device, wherein the authentication request at least includes an identifier of the Internet of Vehicles device;

[0132] A sending unit, configured to send an authentication vector request to the VID authentication authority, wherein the authentication vector request at least includes the vehicle networking device identifier;

[0133] A second receiving unit is used to receive the authentication vector sent by the VID authentication agency, and send the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key;

[0134] The third receiving unit is used to receive the authentication response parameter fed back by the Internet of Vehicles device and determine the corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

[0135] In a fifteenth aspect, a device for managing identification of an Internet of Vehicles device includes:

[0136] A sending unit, configured to send an authentication request to a vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification;

[0137] A first receiving unit, configured to receive an authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on an authentication vector fed back by the VID authentication authority;

[0138] A determination unit, configured to determine a corresponding authentication response parameter based on the authentication parameter and according to the stored vehicle networking device identification authentication key; and send the authentication response parameter to the VID authentication function entity;

[0139] The second receiving unit is configured to receive a service response from the V2X service entity, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

[0140] In the sixteenth aspect, a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a processor, enables the processor to execute any one of the methods described in the first aspect.

[0141] In the seventeenth aspect, a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a processor, enables the processor to execute any one of the methods described in the second aspect.

[0142] In aspect 18, a computer-readable storage medium, when instructions in the computer-readable storage medium are executed by a processor, enables the processor to execute any one of the methods described in aspect 3 above.

[0143] In the nineteenth aspect, a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a processor, enables the processor to execute any one of the methods described in the fourth aspect.

[0144] In the twentieth aspect, a computer-readable storage medium, when the instructions in the computer-readable storage medium are executed by a processor, enables the processor to execute the method described in the fifth aspect above.

[0145] In the disclosed embodiment, the V2X device management subject sends a configuration request containing device parameters of the Internet of Vehicles device to the Internet of Vehicles device identification VID registration agency, and obtains the corresponding Internet of Vehicles device identification, and then obtains the corresponding Internet of Vehicles device identification authentication key from the VID authentication agency based on the Internet of Vehicles device identification, and writes the Internet of Vehicles device identification and the Internet of Vehicles device identification authentication key into the Internet of Vehicles device; in this way, a Internet of Vehicles device identification management and authentication architecture that conforms to actual application scenarios can be constructed, and the V2X device management subject coordinates the management of each V2X device, and the Internet of Vehicles device identification management and authentication architecture can unify the management mechanism of the Internet of Vehicles device and the Internet of Vehicles device identification coding standard, thereby solving the problem of confusion in the Internet of Vehicles device identification management under related technologies, and also solving the problem of customization or inability to authenticate in the process of Internet of Vehicles device identification authentication, which is more conducive to large-scale application and interoperability of the Internet of Vehicles. BRIEF DESCRIPTION OF THE DRAWINGS

[0146] Figure 1 A schematic diagram of an Internet of Vehicles device identification management and authentication architecture in an embodiment of the present disclosure;

[0147] Figure 2 A schematic diagram of the process of managing vehicle networking device identification in an embodiment of the present disclosure;

[0148] Figure 3 A schematic diagram of a process of application interaction between a vehicle networking device and a V2X service entity in an embodiment of the present disclosure;

[0149] Figure 4 A schematic diagram of a computer device physical architecture according to an embodiment of the present disclosure;

[0150] Figure 5 A schematic diagram of a logical architecture of a computer device in an embodiment of the present disclosure;

[0151] Figure 6 A schematic diagram of a physical architecture of a network device in an embodiment of the present disclosure;

[0152] Figure 7 A schematic diagram of a logical architecture of a network device in an embodiment of the present disclosure;

[0153] Figure 8 A schematic diagram of a physical architecture of a network device in an embodiment of the present disclosure;

[0154] Fig. 9 A schematic diagram of a logical architecture of a network device in an embodiment of the present disclosure;

[0155] Fig.10 A schematic diagram of a physical architecture of a network device in an embodiment of the present disclosure;

[0156] Fig.11 A schematic diagram of a logical architecture of a network device in an embodiment of the present disclosure;

[0157] Fig.12 A schematic diagram of a computer device physical architecture according to an embodiment of the present disclosure;

[0158] Fig.13 A schematic diagram of a logical architecture of a computer device in an embodiment of the present disclosure. DETAILED DESCRIPTION

[0159] In order to solve the problem that there is no unified management of Internet of Vehicles equipment identification under related technologies, in an embodiment of the present disclosure, a V2X equipment management subject sends a configuration request including device parameters of an Internet of Vehicles device to a V2X Equipment Identity (VID) registration agency, and obtains a corresponding Internet of Vehicles equipment identification; wherein the configuration request at least includes the device parameters of the Internet of Vehicles device; then based on the Internet of Vehicles equipment identification, a corresponding Internet of Vehicles equipment identification authentication key is obtained from a VID authentication agency; and the Internet of Vehicles equipment identification and the Internet of Vehicles equipment identification authentication key are written into the Internet of Vehicles device, thereby unifying the management mechanism of Internet of Vehicles equipment and the Internet of Vehicles equipment identification coding standard, which is beneficial to the large-scale application and interoperability of Internet of Vehicles.

[0160] The preferred embodiments of the present disclosure will be further described in detail below with reference to the accompanying drawings.

[0161] For the convenience of description, in the subsequent embodiments, the Internet of Vehicles devices are collectively referred to as V2X devices.

[0162] In an embodiment of the present disclosure, a vehicle networking device identification management and authentication architecture is provided. Figure 1 As shown, the IoV equipment identification management and authentication architecture 100 includes at least: a V2X device 101, a V2X Equipment Identity Module (VIM) 102, a V2X equipment management entity 103, a VID registration agency 104, a VID authentication agency 105, a VID authentication function entity 106, and a V2X service entity 107.

[0163] The V2X device 101 includes an on-board unit (OBU), a roadside unit (RSU), and a V2X service provider (VSP) in the Internet of Vehicles system.

[0164] VIM 102, a security module located in the V2X device 101, is used to securely store the VID and the vehicle networking device identification authentication key, and perform security calculations required for VID authentication.

[0165] The V2X device management entity 103 is used to apply for a VID from a VID registration agency 104 and obtain a key from a VID authentication agency 105 , and write the VID and the key into the VIM 102 of the V2X device 101 .

[0166] The VID registration agency 104 is an administrative agency for allocating and generating VIDs.

[0167] The VID authentication agency 105 is an agency for generating keys and authentication rules (authentication vectors).

[0168] The VID authentication function entity 106 is used to obtain a VID authentication vector from the VID authentication authority 105, and interact with the V2X device 101 based on the VID authentication vector to complete VID authentication (ie, device authentication).

[0169] The V2X service entity 107 is used to provide services for the V2X device 101 and is an entity in the Internet of Vehicles. For example, entities in the Internet of Vehicles include but are not limited to the following entities:

[0170] Internet of Vehicles certificate issuing agency;

[0171] Operators;

[0172] Manufacturer.

[0173] A V2X application in the entity needs to authenticate a V2X device 101 before providing services to the V2X device 101. For example, the Internet of Vehicles certificate issuing authority needs to first verify the true identity of the V2X device before issuing a certificate to the V2X device 101.

[0174] In the disclosed embodiment, refer to Figure 2 As shown in the figure, the specific process of managing the identification of connected vehicle equipment is as follows:

[0175] Step 201: The V2X device management entity sends a configuration request to a VID registration agency, wherein the configuration request at least includes device parameters of the V2X device.

[0176] In a specific implementation, when executing step 200, the V2X device management entity sends a configuration request to the VID registration agency, wherein the configuration request at least includes device parameters of the V2X device.

[0177] Optionally, the above device parameters include but are limited to one or a combination of the following information:

[0178] Equipment manufacturers of V2X equipment;

[0179] Device category of V2X devices;

[0180] Device model of the V2X device;

[0181] The product serial number of the V2X device.

[0182] In the disclosed embodiment, in order to better unify the vehicle networking device identification management mechanism, a V2X device management subject is set in the vehicle networking device identification management and authentication architecture. In this way, the V2X device management subject can be used to achieve coordinated management of multiple V2X devices, thereby avoiding the problem of chaotic management of vehicle networking devices.

[0183] Optionally, based on the needs of actual application scenarios, the VID certification agency and the V2X device management entity can be combined.

[0184] In the embodiments of the present disclosure, for ease of description, the VID authentication agency and the V2X device management entity are introduced separately.

[0185] Since VIM is a security module in the V2X device, in the embodiments of the present disclosure, for the convenience of description, VIM and V2X device are combined and collectively referred to as V2X device for introduction. If necessary, VIM will be described separately.

[0186] Step 202: The VID registration agency generates a corresponding VID based on the above device parameters and according to the vehicle networking device identification generation strategy.

[0187] In a specific implementation, the VID registration agency generates a corresponding VID based on the device parameters of the V2X device contained in the configuration request sent by the V2X device management entity and based on the locally stored vehicle networking device identification generation strategy.

[0188] For example, take V2X devices.

[0189] Assume that the device parameters of the V2X device include the device manufacturer of the V2X device, the device category of the V2X device, and the device model of the V2X device, and the device manufacturer of the V2X device is “express delivery manufacturer”, the device category of the V2X device is “automobile”, and the device model of the V2X device is “H84292”.

[0190] The device parameters provided by the V2X device to the V2X device management entity are "express manufacturer, car, H84292". Then, the device parameters of the V2X device included in the configuration request sent by the V2X device management entity to the VID registration authority are "express manufacturer, car, H84292".

[0191] Based on the configuration request, the VID registration agency obtains the device parameters of the corresponding V2X device as "express delivery manufacturer, car, H84292".

[0192] It is also assumed that the VID registration agency generates a corresponding VID of 556891sbfgdz^ based on the locally stored Internet of Vehicles device identification generation strategy.

[0193] The VID for the V2X device obtained by the VID registration agency is 556891sbfgdz^.

[0194] In the disclosed embodiment, the above-mentioned VID is only an example and does not represent the real VID generated by the VID registration agency based on the corresponding Internet of Vehicles device identification generation strategy in actual application. In actual application, the corresponding VID can be generated based on the Internet of Vehicles device identification generation strategy stored by the actual VID registration agency.

[0195] Step 203: The VID registration agency feeds back the above VID to the V2X device management entity.

[0196] In a specific implementation, the VID registration agency feeds back the corresponding generated VID to the V2X device management entity, so that the V2X device management entity can write the corresponding VID into the V2X device when executing step 208.

[0197] Step 204: The VID registration agency notifies the VID authentication agency of the obtained VID.

[0198] In a specific implementation, the VID registration agency notifies the VID authentication agency of the VID generated based on the device parameters of the V2X device so that the VID authentication agency can generate a corresponding key.

[0199] Optionally, in the embodiment of the present disclosure, the VID registration agency may also notify the V2X service entity of the VID generated based on the device parameters of the V2X device, so that the V2X service entity authenticates the V2X device before providing the V2X device with corresponding services.

[0200] Step 205: Based on the above VID, the VID authentication agency generates a corresponding key.

[0201] In a specific implementation, the VID authentication agency generates a key for the VID based on the VID notified by the VID authentication agency and the corresponding Internet of Vehicles device identification authentication key generation rule.

[0202] For example, still taking V2X equipment as an example.

[0203] Assume that the VID registration agency generates a VID of 556891sbfgdz^ based on the device parameters of the V2X device and the vehicle networking device identification generation strategy.

[0204] Then, the VID registration agency notifies the VID authentication agency of the above VID. The VID authentication agency generates a key for the VID based on the received VID and the corresponding vehicle networking device identification authentication key generation rules, such as the generated key is gah^dg4#9721.

[0205] In the disclosed embodiment, the above-mentioned VID is only an example and does not represent the real VID generated by the VID registration agency based on the corresponding Internet of Vehicles device identification generation strategy in actual application. In actual application, the corresponding VID can be generated based on the Internet of Vehicles device identification generation strategy stored by the actual VID registration agency.

[0206] Similarly, in the embodiments of the present disclosure, the above-mentioned key is only an example and does not represent the real key generated by the VID certification agency based on the corresponding Internet of Vehicles device identification authentication key generation rules in actual applications. In actual applications, the corresponding key can be generated based on the actual Internet of Vehicles device identification authentication key generation rules of the VID certification agency.

[0207] Step 206: The V2X device management entity sends a vehicle networking device identification authentication key request to the VID authentication agency, wherein the vehicle networking device identification authentication key request includes the VID of the V2X device.

[0208] In a specific implementation, the V2X device management entity may send a vehicle networking device identification authentication key request carrying the VID of the V2X device to the VID authentication agency, so that the VID authentication agency may learn that it needs to feed back the key corresponding to the V2X device to the V2X device management entity.

[0209] Step 207: The VID authentication agency responds to the above-mentioned Internet of Vehicles device identification authentication key request and feeds back the corresponding Internet of Vehicles device identification authentication key to the V2X device management entity.

[0210] In a specific implementation, the VID authentication agency responds to the vehicle networking device identification authentication key request sent from the V2X device management entity, and feeds back the corresponding vehicle networking device identification authentication key to the V2X device management entity.

[0211] Optionally, after executing step 205, the VID certification authority may also directly issue a key for the V2X device to the V2X device management entity based on the received VID, so that the V2X device management entity obtains the corresponding key, so that the V2X device management entity can write the corresponding key into the V2X device when executing step 208.

[0212] Step 208: The V2X device management entity writes the received VID and the received key into the V2X device.

[0213] In a specific implementation, after executing step 203, the V2X device management entity obtains the VID for the V2X device from the VID registration agency; after executing step 207, the V2X device management entity obtains the key for the V2X device from the VID authentication agency, and when executing step 208, the V2X device management entity writes the VID and key for the V2X device obtained above into the VIM contained in the corresponding V2X device, wherein the VIM is a security module inside the V2X device, which is used to securely store the VID and key, and provide the V2X device with the authentication response parameters required for authentication when performing VID authentication; or,

[0214] When executing step 208, the V2X device management entity writes the VID and key for the V2X device obtained above into a security module included in the corresponding V2X device, wherein the security module is used to securely store the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key.

[0215] For example, still taking V2X equipment as an example.

[0216] Assume that the VID received by the V2X device management entity from the VID registration agency is 556891sbfgdz^; and the key received from the VID certification agency is gah^dg4#9721.

[0217] Since VIM is a security module in the V2X device, it is used to securely store VID and key; therefore, when executing step 208, the V2X device management entity will write the VID and key of the V2X device into the VIM included in the V2X device, that is, write 556891sbfgdz^ and gah^dg4#9721 into the VIM included in the V2X device.

[0218] In the disclosed embodiment, the above-mentioned VID is only an example and does not represent the real VID generated by the VID registration agency based on the corresponding Internet of Vehicles device identification generation strategy in actual application. In actual application, the corresponding VID can be generated based on the Internet of Vehicles device identification generation strategy stored by the actual VID registration agency.

[0219] Similarly, in the embodiments of the present disclosure, the above-mentioned key is only an example and does not represent the real key generated by the VID certification agency based on the corresponding Internet of Vehicles device identification authentication key generation rules in actual applications. In actual applications, the corresponding key can be generated based on the actual Internet of Vehicles device identification authentication key generation rules of the VID certification agency.

[0220] In the disclosed embodiment, each V2X device provides its corresponding device parameters to the V2X device management subject, and then obtains the corresponding VID based on the interaction between the V2X device management subject and the VID registration agency, and then obtains the corresponding key through interaction with the VID certification agency. In this way, the VID registration agency and the VID certification agency only need to interact with the V2X device management subject, and do not need to interact with each V2X device one by one, thereby greatly improving the work efficiency of obtaining the corresponding VID and key. Due to the existence of the V2X device management subject, the V2X device management subject can also classify each V2X device based on the device parameters provided by each V2X device, such as classifying each V2X device according to the device manufacturer, etc., and then manage each V2X device with the same characteristics in a targeted manner.

[0221] See also Figure 3 As shown, in the embodiment of the present disclosure, based on the above-mentioned vehicle networking device identification management, the specific process of application interaction between the vehicle networking device and the V2X service entity is as follows:

[0222] Step 301: The V2X device sends a service request to a V2X service entity, wherein the service request at least includes a VID of the V2X device.

[0223] In a specific implementation, the service request sent by the V2X device to the V2X service entity may be a service request sent to any application in the V2X service entity, or may be an authentication request sent to the V2X service entity, wherein the service request and / or the authentication request both include the VID of the V2X device.

[0224] Optionally, based on the needs of actual application scenarios, the VID authentication function entity and the VID authentication agency can be combined and set.

[0225] Optionally, based on the needs of actual application scenarios, the VID authentication function entity and the V2X service entity can be combined and set.

[0226] In the embodiments of the present disclosure, for ease of description, the VID authentication agency, the VID authentication functional entity, and the V2X service entity are introduced separately.

[0227] Since VIM is a security module in the V2X device, in the embodiments of the present disclosure, for the convenience of description, VIM and V2X device are combined and collectively referred to as V2X device for introduction. If necessary, VIM will be described separately.

[0228] Step 302: The V2X service entity sends an authentication request to the VID authentication function entity based on the service request, wherein the authentication request at least includes the VID of the V2X device.

[0229] In the embodiment of the present disclosure, the V2X service entity needs to perform device authentication on the V2X device before providing a corresponding service response to the V2X device based on the received service request. Therefore, the V2X service entity sends an authentication request for the V2X device to the VID authentication function entity, wherein the authentication request includes at least the VID of the V2X device.

[0230] For example, still taking V2X equipment as an example.

[0231] Assume that the V2X device sends a service request to the V2X service entity, wherein the service request at least includes the VID of the V2X device and requires application A in the V2X service entity to provide application interaction service.

[0232] Then, after receiving the above service request, the V2X service entity needs to perform device authentication on the V2X device. Therefore, the V2X service entity sends an authentication request to the VID authentication function entity.

[0233] Assume that the VID of the V2X device is 556891sbfgdz^.

[0234] Then, the V2X service entity sends an authentication request including the VID of the V2X device to the VID authentication function entity, that is, the VID authentication function entity obtains the corresponding VID 556891sbfgdz^.

[0235] In the disclosed embodiment, the above-mentioned VID is only an example and does not represent the real VID generated by the VID registration agency based on the corresponding Internet of Vehicles device identification generation strategy in actual application. In actual application, the corresponding VID can be generated based on the Internet of Vehicles device identification generation strategy stored by the actual VID registration agency.

[0236] Step 303: The VID authentication function entity sends an authentication vector request to the VID authentication authority based on the authentication request, wherein the authentication vector request at least includes the VID of the V2X device.

[0237] In a specific implementation, the VID authentication function entity receives an authentication request sent by the V2X service entity, and then sends an authentication vector request to the VID authentication authority based on the authentication request, wherein the authentication vector request includes at least the VID of the V2X device.

[0238] For example, still taking V2X equipment as an example.

[0239] Assume that the VID authentication function entity obtains the VID of the V2X device as 556891sbfgdz^ based on the authentication request.

[0240] Then, the VID authentication function entity sends the authentication vector request containing the above VID to the VID authentication agency. Therefore, the VID of the V2X device that needs to be authenticated obtained by the VID authentication agency is 556891sbfgdz^.

[0241] In the disclosed embodiment, the above-mentioned VID is only an example and does not represent the real VID generated by the VID registration agency based on the corresponding Internet of Vehicles device identification generation strategy in actual application. In actual application, the corresponding VID can be generated based on the Internet of Vehicles device identification generation strategy stored by the actual VID registration agency.

[0242] Step 304: The VID authentication agency obtains a pre-stored corresponding key based on the VID included in the authentication vector request, and generates a corresponding authentication vector based on the key.

[0243] In a specific implementation, the VID authentication agency receives an authentication vector request sent from the VID authentication function entity, then obtains a pre-stored corresponding key from the local based on the VID included in the authentication vector request, and generates a corresponding authentication vector based on the key.

[0244] Optionally, the authentication vector generated by the VID authentication agency includes multiple security parameters, wherein the multiple security parameters include at least an authentication parameter for authenticating the V2X device.

[0245] Optionally, the above-mentioned multiple security parameters can be obtained through user signature, encryption and the like.

[0246] For example, still taking V2X equipment as an example.

[0247] Assume that the VID obtained by the VID certification agency is 556891sbfgdz^, and the corresponding pre-stored key is gah^dg4#9721.

[0248] Then, based on the above VID and key, the VID certification agency uses user signature to obtain the corresponding security parameters, where the authentication parameters used to authenticate the V2X device can be dfuafga464qi, agi4578%##, etc.

[0249] In the embodiment of the present disclosure, the above VID, key and authentication parameters are only examples and do not represent the real VID, key and authentication parameters obtained in actual applications. In actual applications, corresponding VID, key and authentication parameters can be generated based on actual conditions.

[0250] Step 305: The VID authentication agency feeds back the authentication vector to the VID authentication function entity.

[0251] In a specific implementation, after executing step 304, the VID authentication agency generates a corresponding authentication vector based on the VID of the V2X device and the corresponding key. Then, when executing step 305, the obtained authentication vector is fed back to the VID authentication function entity, so that the VID authentication function entity sends the corresponding authentication parameters to the V2X device, so that when executing subsequent steps, the authentication result for the V2X device can be obtained.

[0252] Step 306: The VID authentication function entity feeds back corresponding authentication parameters to the V2X device, wherein the authentication parameters are obtained by the VID authentication function entity based on the received authentication vector and are used to authenticate the V2X device.

[0253] In a specific implementation, the VID authentication function entity selects corresponding authentication parameters from the authentication vector, and feeds back the obtained authentication parameters to the V2X device, so that the V2X device feeds back authentication response parameters based on the authentication parameters when executing the subsequent step 307.

[0254] Optionally, the VID authentication function entity distinguishes the content in the above authentication vector based on the received authentication vector, obtains corresponding authentication parameters therefrom, and is used to authenticate the V2X device.

[0255] Step 307: The V2X device provides the received authentication parameters to the VIM in the V2X device. The VIM obtains corresponding authentication response parameters based on the authentication parameters and a pre-stored key, and feeds the authentication response parameters back to the V2X device.

[0256] In a specific implementation, the V2X device provides the authentication parameters fed back by the VID authentication function entity to the VIM. The VIM performs corresponding operations on the above authentication parameters based on the pre-stored key to obtain corresponding authentication response parameters, and feeds back the obtained authentication response parameters to the V2X device. The above operation can be a decryption operation based on the key, a decoding operation based on the key, or any other operation mode.

[0257] Step 308: The V2X device sends the corresponding authentication response parameters to the VID authentication function entity.

[0258] In a specific implementation, the V2X device sends the above authentication response parameters to the VID authentication function entity, so that the VID authentication function entity obtains the corresponding authentication result.

[0259] Step 309: The VID authentication function entity performs corresponding operations based on the received authentication response parameters and other parameters included in the authentication vector to obtain a corresponding authentication result.

[0260] In a specific implementation, the VID authentication function entity performs corresponding operations based on the authentication response parameters sent by the V2X device and other parameters included in the above authentication vector, wherein the above operations include but are not limited to the following operations:

[0261] Compare the authentication response parameters with other parameters included in the authentication vector;

[0262] Calculate based on the above authentication response parameters and other parameters included in the authentication vector;

[0263] Based on the above authentication response parameters, the authentication vector is integrated with other parameters;

[0264] etc.

[0265] Then, the VID authentication function entity compares the information obtained based on the above operation with the ciphertext information in the above authentication vector. If the information obtained based on the above operation is the same as the ciphertext information contained in the above authentication vector, the authentication result is determined to be passed; otherwise, if the information obtained based on the above operation is different from the ciphertext information contained in the above authentication vector, the authentication result is determined to be failed.

[0266] For example, still taking V2X equipment as an example.

[0267] Assume that after the VID authentication function entity performs corresponding operations based on the authentication response parameters sent by the obtained V2X device and other parameters contained in the above authentication vector, the corresponding information obtained is "whiaa##%&^&#", and the ciphertext information contained in the above authentication vector is "whiaa##%&^&#".

[0268] Since the information obtained based on the above operation is the same as the ciphertext information included in the above authentication vector, the VID authentication function entity determines that the authentication result indicates a pass.

[0269] For another example, let’s still take V2X equipment as an example.

[0270] Assume that after the authentication response parameters sent by the V2X device obtained by the VID authentication function entity are subjected to corresponding operations with other parameters contained in the above authentication vector, the corresponding information obtained is "whiaa#%&^&#", and the ciphertext information contained in the above authentication vector is "wgsgaa%#%&&#".

[0271] Since the information obtained based on the above operation is different from the ciphertext information included in the above authentication vector, the VID authentication function entity determines that the authentication result representation fails.

[0272] In the embodiments of the present disclosure, the above-mentioned authentication response parameters and ciphertext information contained in the authentication vector are only examples and do not represent the actual authentication response parameters and ciphertext information contained in the authentication vector obtained in actual applications. In actual applications, the corresponding ciphertext information can be obtained based on actual conditions.

[0273] Step 310: The VID authentication function entity feeds back the corresponding authentication result to the V2X service entity.

[0274] In a specific implementation, the VID authentication function entity feeds back the above authentication result to the V2X service entity, so that the V2X service entity makes a service response to the service request based on the received authentication result.

[0275] Step 311: The V2X service entity feeds back a service response to the V2X device based on the authentication result.

[0276] In a specific implementation, the V2X service entity feeds back a service response to the V2X device based on the authentication result, wherein the service response includes but is not limited to the following two situations:

[0277] In case 1, if the V2X service entity determines that the authentication result representation is passed based on the authentication result, it feeds back a service response based on the service request to the V2X device.

[0278] In case 2, if the V2X service entity determines that the above authentication result representation fails based on the authentication result, it feeds back a corresponding authentication response to the V2X device.

[0279] Step 312: The V2X device receives the above service response and performs application interaction with the V2X service entity.

[0280] In a specific implementation, the V2X device receives the above service response, obtains the corresponding service, and further performs application interaction. Optionally, based on the above vehicle network management memory and vehicle network device identification coding standard, the interaction between each V2X device and each V2X service entity can be realized, thereby realizing large-scale application and intercommunication of the vehicle network.

[0281] Based on the same inventive concept, refer to Figure 4As shown, a computer device (e.g., a V2X device management entity) in an embodiment of the present disclosure at least includes:

[0282] Memory 401, used to store executable instructions;

[0283] The processor 402 is used to read and execute the executable instructions stored in the memory 401 to perform the following process:

[0284] Sending a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0285] Obtaining a connected vehicle device identifier corresponding to the connected vehicle device fed back by the VID registration agency based on the device parameters;

[0286] Based on the IoV device identification, obtaining a corresponding IoV device identification authentication key from a VID authentication agency;

[0287] The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into the Internet of Vehicles device.

[0288] Optionally, the device parameters of the Internet of Vehicles device include at least any one or combination of the following information:

[0289] The device manufacturer of the Internet of Vehicles device;

[0290] The device category of the Internet of Vehicles device;

[0291] The device model of the Internet of Vehicles device;

[0292] The product serial number of the Internet of Vehicles device.

[0293] Optionally, the V2X device management entity obtains a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency based on the Internet of Vehicles device identification, and the processor 402 is used to:

[0294] receiving a vehicle networking device identification authentication key issued by the VID authentication agency based on the vehicle networking device identification, wherein the vehicle networking device identification is sent to the VID authentication agency by the VID registration agency; or

[0295] Send a vehicle networking device identification authentication key request carrying the vehicle networking device identification to the VID authentication agency, and receive a corresponding vehicle networking device identification authentication key issued by the VID authentication agency.

[0296] Optionally, the V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device, and the processor 402 is used to:

[0297] Writing the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device identification card VIM included in the Internet of Vehicles device; or,

[0298] The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into a security module included in the Internet of Vehicles device, wherein the security module is used to securely store the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key.

[0299] Among them, Figure 4 As shown, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 402 and various circuits of memory represented by memory 401 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver may be a plurality of components, i.e., including a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0300] The processor 402 is responsible for managing the bus architecture and general processing, and the memory 401 can store data used by the processor 402 when performing operations.

[0301] Based on the same inventive concept, refer to Figure 5 As shown, the embodiment of the present disclosure provides a vehicle networking device identification management device (e.g., a V2X device management subject), which at least includes a sending unit 501, a first acquisition unit 502, a second acquisition unit 503 and a writing unit 504, wherein:

[0302] The sending unit 501 is used to send a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0303] A first acquisition unit 502 is used to acquire a connected vehicle device identifier corresponding to the connected vehicle device fed back by the VID registration agency based on the device parameters;

[0304] A second acquisition unit 503 is used to acquire a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency based on the Internet of Vehicles device identification;

[0305] The writing unit 504 is used to write the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device.

[0306] In the embodiment of the present disclosure, the sending unit 501, the first obtaining unit 502, the second obtaining unit 503 and the writing unit 504 cooperate with each other to implement any one of the methods executed by the network device in the above-mentioned various embodiments.

[0307] Based on the same inventive concept, refer to Figure 6 As shown, a network device (e.g., a VID registration agency) in an embodiment of the present disclosure at least includes:

[0308] Memory 601, used to store executable instructions;

[0309] The processor 602 is used to read and execute the executable instructions stored in the memory 601 to perform the following process:

[0310] Receiving a configuration request sent by a vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0311] Based on the device parameters of the Internet of Vehicles device, generating a corresponding Internet of Vehicles device identifier according to an Internet of Vehicles device identifier generation strategy;

[0312] Feedback the V2X device management entity with the V2X device identifier corresponding to the V2X device;

[0313] The Internet of Vehicles device identification is sent to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification, and sends the Internet of Vehicles device identification authentication key to a V2X device management entity.

[0314] Optionally, the device parameters of the Internet of Vehicles device include at least any one or combination of the following information:

[0315] The device manufacturer of the Internet of Vehicles device;

[0316] The device category of the Internet of Vehicles device;

[0317] The device model of the Internet of Vehicles device;

[0318] The product serial number of the Internet of Vehicles device.

[0319] Optionally, after the VID registration agency generates a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy, the processor 602 is further configured to:

[0320] The Internet of Vehicles device identifier is sent to a V2X service entity, so that the V2X service entity uniquely identifies the Internet of Vehicles device based on the Internet of Vehicles device identifier.

[0321] Among them, Figure 6 As shown, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 602 and various circuits of memory represented by memory 601 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver may be a plurality of components, namely, a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. The processor 602 is responsible for managing the bus architecture and general processing, and the memory 601 may store data used by the processor 602 when performing operations.

[0322] Based on the same inventive concept, refer to Figure 7 As shown, the embodiment of the present disclosure provides a device for managing the identification of an Internet of Vehicles device (eg, a VID registration agency), which includes at least a receiving unit 701, a generating unit 702, a feedback unit 703 and a sending unit 704, wherein:

[0323] The receiving unit 701 is used to receive a configuration request sent by a vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device;

[0324] A generating unit 702, configured to generate a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy;

[0325] A feedback unit 703 is used to feed back the vehicle networking device identifier corresponding to the vehicle networking device to the V2X device management body;

[0326] The sending unit 704 is used to send the Internet of Vehicles device identifier to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identifier authentication key based on the Internet of Vehicles device identifier, and sends the Internet of Vehicles device identifier authentication key to a V2X device management entity.

[0327] In the embodiment of the present disclosure, the above-mentioned receiving unit 701, generating unit 702, feedback unit 703 and sending unit 704 cooperate with each other to implement any one of the methods executed by the network device in the above-mentioned various embodiments.

[0328] Based on the same inventive concept, refer to Figure 8 As shown, a network device (e.g., a VID authentication agency) in an embodiment of the present disclosure at least includes:

[0329] Memory 801, used to store executable instructions;

[0330] The processor 802 is used to read and execute the executable instructions stored in the memory 801 to perform the following process:

[0331] Receiving the vehicle networking device identifier sent by the VID registration agency, where the vehicle networking device identifier is generated by the VID registration agency based on the device parameters of the vehicle networking device in the configuration request sent by the vehicle networking V2X device management subject and according to the vehicle networking device identifier generation strategy;

[0332] Based on the Internet of Vehicles device identifier, generating a corresponding Internet of Vehicles device identifier authentication key;

[0333] The vehicle networking device identification authentication key is sent to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

[0334] Optionally, the VID authentication agency sends the Internet of Vehicles device identification authentication key to the V2X device management entity, and the processor 802 is used to:

[0335] Based on the IoV device identification, directly send the corresponding IoV device identification authentication key to the V2X device management entity; or,

[0336] In response to the vehicle networking device identity authentication key request sent by the V2X device management entity, the vehicle networking device identity authentication key is sent to the V2X device management entity, wherein the vehicle networking device identity authentication key request includes the vehicle networking device identity.

[0337] Among them, Figure 8 As shown, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 802 and various circuits of memory represented by memory 801 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver may be a plurality of components, namely, a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. The processor 802 is responsible for managing the bus architecture and general processing, and the memory 801 may store data used by the processor 802 when performing operations.

[0338] Based on the same inventive concept, refer to Fig. 9 As shown, the embodiment of the present disclosure provides a device for managing the identification of an Internet of Vehicles device (eg, a VID certification body), which includes at least a receiving unit 901, a generating unit 902, and a sending unit 903, wherein:

[0339] A receiving unit 901 is configured to receive the vehicle networking device identifier sent by the VID registration agency, where the vehicle networking device identifier is generated by the VID registration agency based on the device parameters of the vehicle networking device in the configuration request sent by the vehicle networking V2X device management subject and according to the vehicle networking device identifier generation strategy;

[0340] A generating unit 902, configured to generate a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification;

[0341] The sending unit 903 is configured to send the Internet of Vehicles device identification authentication key to the V2X device management entity, so that the V2X device management entity writes the Internet of Vehicles device identification authentication key into the Internet of Vehicles device.

[0342] In the embodiment of the present disclosure, the above-mentioned receiving unit 901, generating unit 902 and sending unit 903 cooperate with each other to implement any one of the methods executed by the network device in the above-mentioned various embodiments.

[0343] Based on the same inventive concept, refer to Fig.10 As shown, a network device (e.g., a VID authentication function entity) in an embodiment of the present disclosure at least includes:

[0344] Memory 1001, used for storing executable instructions;

[0345] The processor 1002 is used to read and execute the executable instructions stored in the memory 1001, and perform the following process:

[0346] Receiving an authentication request sent by a connected vehicle device, wherein the authentication request at least includes an identification of the connected vehicle device;

[0347] Sending an authentication vector request to the VID authentication authority, wherein the authentication vector request at least includes the IoV device identifier;

[0348] Receiving the authentication vector sent by the VID authentication agency, and sending the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key;

[0349] Receive the authentication response parameter fed back by the Internet of Vehicles device, and determine the corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

[0350] Optionally, the VID authentication function entity receives an authentication response parameter fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key, and the processor 1002 is used to:

[0351] Receiving authentication response parameters fed back by the Internet of Vehicles device;

[0352] Based on the authentication response parameter, perform corresponding operations with other parameters included in the authentication vector;

[0353] If the information obtained based on the operation is the same as the ciphertext information included in the authentication vector, it is determined that the authentication result representation is passed.

[0354] Among them, Fig.10 As shown, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1002 and various circuits of memory represented by memory 1001 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver may be a plurality of components, namely, a transmitter and a transceiver, providing a unit for communicating with various other devices on a transmission medium. The processor 1002 is responsible for managing the bus architecture and general processing, and the memory 1001 may store data used by the processor 1002 when performing operations.

[0355] Based on the same inventive concept, refer to Fig.11 As shown, the embodiment of the present disclosure provides a device for managing identification of an Internet of Vehicles device (eg, a VID authentication function entity), comprising at least a first receiving unit 1101, a sending unit 1102, a second receiving unit 1103 and a third receiving unit 1104, wherein:

[0356] The first receiving unit 1101 is configured to receive an authentication request sent by an Internet of Vehicles device, wherein the authentication request at least includes an identifier of the Internet of Vehicles device;

[0357] A sending unit 1102 is configured to send an authentication vector request to the VID authentication authority, wherein the authentication vector request at least includes the Internet of Vehicles device identifier;

[0358] The second receiving unit 1103 is used to receive the authentication vector sent by the VID authentication agency, and send the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key;

[0359] The third receiving unit 1104 is used to receive the authentication response parameter fed back by the Internet of Vehicles device and determine the corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

[0360] In the embodiment of the present disclosure, the first receiving unit 1101, the sending unit 1102, the second receiving unit 1103 and the third receiving unit 1104 cooperate with each other to implement any one of the methods executed by the network device in the above-mentioned embodiments.

[0361] Based on the same inventive concept, refer to Fig.12 As shown, a computer device (e.g., a V2X device) in an embodiment of the present disclosure at least includes:

[0362] Memory 1201, used for storing executable instructions;

[0363] The processor 1202 is used to read and execute the executable instructions stored in the memory 1201, and perform the following processes:

[0364] Sending an authentication request to a vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification;

[0365] receiving an authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on an authentication vector fed back by the VID authentication authority;

[0366] Based on the authentication parameters, determining corresponding authentication response parameters according to the stored Internet of Vehicles device identification authentication key; and sending the authentication response parameters to the VID authentication function entity;

[0367] receiving a service response from the V2X service entity, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

[0368] Among them, Fig.12As shown, the bus architecture may include any number of interconnected buses and bridges, specifically one or more processors represented by processor 1202 and various circuits of memory represented by memory 1201 are linked together. The bus architecture may also link together various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface. The transceiver may be a plurality of components, namely, a transmitter and a receiver, providing a unit for communicating with various other devices on a transmission medium. For different user devices, the user interface may also be an interface capable of externally connecting or internally connecting required devices, and the connected devices include but are not limited to a keypad, a display, a speaker, a microphone, a joystick, and the like.

[0369] The processor 1202 is responsible for managing the bus architecture and general processing, and the memory 1201 can store data used by the processor 1202 when performing operations.

[0370] Based on the same inventive concept, refer to Fig.13 As shown, the embodiment of the present disclosure provides a device for managing the identification of a vehicle networking device (e.g., a V2X device), which includes at least a sending unit 1301, a first receiving unit 1302, a determining unit 1303, and a second receiving unit 1304, wherein:

[0371] The sending unit 1301 is used to send an authentication request to the Internet of Vehicles device identifier VID authentication function entity, wherein the authentication request at least includes the Internet of Vehicles device identifier;

[0372] A first receiving unit 1302 is configured to receive an authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on an authentication vector fed back by the VID authentication authority;

[0373] The determination unit 1303 is used to determine the corresponding authentication response parameter based on the authentication parameter and the stored Internet of Vehicles device identification authentication key; and send the authentication response parameter to the VID authentication function entity;

[0374] The second receiving unit 1304 is configured to receive a service response from the V2X service entity, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

[0375] In the embodiment of the present disclosure, the sending unit 1301, the first receiving unit 1302, the determining unit 1303 and the second receiving unit 1304 cooperate with each other to implement any one of the methods executed by the network device in the above-mentioned embodiments.

[0376] Based on the same inventive concept, an embodiment of the present disclosure provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute any one of the methods executed by the V2X device management subject in the above-mentioned embodiments.

[0377] Based on the same inventive concept, an embodiment of the present disclosure provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute any one of the methods executed by the VID registration mechanism in the above-mentioned embodiments.

[0378] Based on the same inventive concept, an embodiment of the present disclosure provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute any one of the methods executed by the VID authentication agency in the above-mentioned embodiments.

[0379] Based on the same inventive concept, an embodiment of the present disclosure provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute any one of the methods executed by the VID authentication function entity in the above-mentioned embodiments.

[0380] Based on the same inventive concept, an embodiment of the present disclosure provides a computer-readable storage medium. When instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute any one of the methods executed by the V2X device in the above-mentioned embodiments.

[0381] To sum up, in the embodiment of the present disclosure, the V2X device management subject sends a configuration request containing device parameters of the Internet of Vehicles device to the Internet of Vehicles device identification VID registration agency, and obtains the corresponding Internet of Vehicles device identification, and then based on the Internet of Vehicles device identification, obtains the corresponding Internet of Vehicles device identification authentication key from the VID authentication agency, and writes the Internet of Vehicles device identification and the Internet of Vehicles device identification authentication key into the Internet of Vehicles device; in this way, a Internet of Vehicles device identification management and authentication architecture that conforms to the actual application scenario can be constructed, and the V2X device management subject coordinates the management of each V2X device, and the Internet of Vehicles device identification management and authentication architecture can unify the management mechanism of the Internet of Vehicles device and the Internet of Vehicles device identification coding standard, thereby solving the problem of confusion in the Internet of Vehicles device identification management under the relevant technology, and also solving the problem of customization or inability to authenticate in the process of Internet of Vehicles device identification authentication, which is more conducive to the large-scale application and interoperability of the Internet of Vehicles.

[0382] Those skilled in the art will appreciate that the embodiments of the present application may be provided as methods, systems, or computer program products. Therefore, the present application may adopt the form of a complete hardware embodiment, a complete software embodiment, or an embodiment in combination with software and hardware. Moreover, the present application may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage and optical storage, etc.) that contain computer-usable program code.

[0383] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the embodiments of the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the processes and / or boxes in the flowchart and / or block diagram, can be implemented by computer executable instructions. These computer executable instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to generate a machine, so that the instructions executed by the processor of the computer or other programmable data processing device generate instructions for implementing the processes in the flowchart and / or block diagram. Figure 1 A process or multiple processes and / or boxes Figure 1 A device that provides the functions specified in a block or multiple blocks.

[0384] These processor executable instructions may also be stored in a processor readable memory that can direct a computer or other programmable data processing device to operate in a specific manner, so that the instructions stored in the processor readable memory produce an article of manufacture including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

[0385] These processor-executable instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, thereby providing instructions for executing on the computer or other programmable device to implement the process. Figure 1 A process or multiple processes and / or boxes Figure 1 The steps for the functions specified in one or more boxes.

[0386] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also intended to include these modifications and variations.

Claims

1. A method for managing vehicle networking device identification, characterized in that: include: The V2X device management entity sends a configuration request to the VID registration authority for the V2X device, wherein the configuration request at least includes device parameters of the V2X device; The V2X device management entity obtains a vehicle networking device identifier corresponding to the vehicle networking device fed back by the VID registration agency based on the device parameters; The V2X device management entity obtains the corresponding vehicle networking device identification authentication key from the VID authentication agency based on the vehicle networking device identification; The V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device.

2. The method according to claim 1, characterized in that The device parameters of the Internet of Vehicles device include at least one or a combination of the following information: The device manufacturer of the Internet of Vehicles device; The device category of the Internet of Vehicles device; The device model of the Internet of Vehicles device; The product serial number of the Internet of Vehicles device.

3. The method according to claim 1, characterized in that The V2X device management entity obtains the corresponding vehicle networking device identification authentication key from the VID authentication agency based on the vehicle networking device identification, including: receiving a vehicle networking device identification authentication key issued by the VID authentication agency based on the vehicle networking device identification, wherein the vehicle networking device identification is sent to the VID authentication agency by the VID registration agency; or Send a vehicle networking device identification authentication key request carrying the vehicle networking device identification to the VID authentication agency, and receive a corresponding vehicle networking device identification authentication key issued by the VID authentication agency.

4. The method according to claim 1, characterized in that The V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device, including: Writing the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device identification card VIM included in the Internet of Vehicles device; or, The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into a security module included in the Internet of Vehicles device, wherein the security module is used to securely store the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key.

5. A method for managing vehicle networking equipment identification, characterized in that: include: The vehicle networking device identification VID registration agency receives a configuration request sent by the vehicle networking V2X device management entity, wherein the configuration request at least includes device parameters of the vehicle networking device; The VID registration agency generates a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy; The VID registration agency feeds back the Internet of Vehicles device identifier corresponding to the Internet of Vehicles device to the V2X device management entity; The VID registration agency sends the Internet of Vehicles device identifier to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identifier authentication key based on the Internet of Vehicles device identifier, and sends the Internet of Vehicles device identifier authentication key to the V2X device management entity.

6. The method according to claim 5, characterized in that The device parameters of the Internet of Vehicles device include at least one or a combination of the following information: The device manufacturer of the Internet of Vehicles device; The device category of the Internet of Vehicles device; The device model of the Internet of Vehicles device; The product serial number of the Internet of Vehicles device.

7. The method according to claim 5, characterized in that After the VID registration agency generates a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to the Internet of Vehicles device identifier generation strategy, the method further includes: The Internet of Vehicles device identifier is sent to a V2X service entity, so that the V2X service entity uniquely identifies the Internet of Vehicles device based on the Internet of Vehicles device identifier.

8. A method for managing vehicle networking device identification, characterized in that: include: The vehicle networking device identification VID authentication agency receives the vehicle networking device identification sent by the VID registration agency, wherein the vehicle networking device identification is generated by the VID registration agency based on the device parameters of the vehicle networking device in the configuration request sent by the vehicle networking V2X device management entity and according to the vehicle networking device identification generation strategy; The VID authentication agency generates a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification; The VID authentication agency sends the vehicle networking device identification authentication key to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

9. The method according to claim 8, characterized in that The VID authentication agency sends the vehicle networking device identification authentication key to the V2X device management entity, including: Based on the IoV device identification, directly send the corresponding IoV device identification authentication key to the V2X device management entity; or, In response to the vehicle networking device identity authentication key request sent by the V2X device management entity, the vehicle networking device identity authentication key is sent to the V2X device management entity, wherein the vehicle networking device identity authentication key request includes the vehicle networking device identity.

10. A method for managing identification of vehicle networking equipment, characterized in that: include: The vehicle networking device identification VID authentication function entity receives an authentication request sent by the vehicle networking device, wherein the authentication request at least includes the vehicle networking device identification, and the vehicle networking device identification is written after being obtained from the VID registration agency based on a configuration request including device parameters of the vehicle networking device sent to the vehicle networking device identification VID registration agency by the vehicle networking V2X device management subject; The VID authentication function entity sends an authentication vector request to a VID authentication authority, wherein the authentication vector request at least includes the Internet of Vehicles device identifier; The VID authentication function entity receives the authentication vector sent by the VID authentication agency, and sends the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key; The VID authentication function entity receives the authentication response parameters fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameters are generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

11. The method according to claim 10, characterized in that The VID authentication function entity receives the authentication response parameter fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key, including: Receiving authentication response parameters fed back by the Internet of Vehicles device; Based on the authentication response parameter, perform corresponding operations with other parameters included in the authentication vector; If the information obtained based on the operation is the same as the ciphertext information included in the authentication vector, it is determined that the authentication result representation is passed.

12. A method for managing identification of vehicle networking equipment, characterized in that: include: The vehicle networking V2X device sends an authentication request to the vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification, and the vehicle networking device identification is obtained from the VID registration agency and written after the vehicle networking V2X device management entity sends a configuration request including device parameters of the vehicle networking device to the vehicle networking device identification VID registration agency; The V2X device receives the authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on the authentication vector fed back by the VID authentication authority; The V2X device determines the corresponding authentication response parameter based on the authentication parameter and according to the stored vehicle networking device identification authentication key; and sends the authentication response parameter to the VID authentication function entity; The V2X device receives a service response from a V2X service entity, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

13. A computer device, characterized in that: include: A memory for storing executable instructions; The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes: Sending a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device; Obtaining a connected vehicle device identifier corresponding to the connected vehicle device fed back by the VID registration agency based on the device parameters; Based on the Internet of Vehicles device identification, obtaining a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency; The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into the Internet of Vehicles device.

14. The computer device of claim 13, wherein: The device parameters of the Internet of Vehicles device include at least one or a combination of the following information: The device manufacturer of the Internet of Vehicles device; The device category of the Internet of Vehicles device; The device model of the Internet of Vehicles device; The product serial number of the Internet of Vehicles device.

15. The computer device of claim 13, wherein: The V2X device management subject obtains the corresponding vehicle networking device identification authentication key from the VID authentication agency based on the vehicle networking device identification, and the processor is used to: receiving a vehicle networking device identification authentication key issued by the VID authentication agency based on the vehicle networking device identification, wherein the vehicle networking device identification is sent to the VID authentication agency by the VID registration agency; or Send a vehicle networking device identification authentication key request carrying the vehicle networking device identification to the VID authentication agency, and receive a corresponding vehicle networking device identification authentication key issued by the VID authentication agency.

16. The computer device of claim 13, wherein: The V2X device management entity writes the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device, and the processor is used to: Writing the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device identification card VIM included in the Internet of Vehicles device; or, The Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key are written into a security module included in the Internet of Vehicles device, wherein the security module is used to securely store the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key.

17. A network device, characterized in that: include: A memory for storing executable instructions; The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes: Receiving a configuration request sent by a vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device; Based on the device parameters of the Internet of Vehicles device, generating a corresponding Internet of Vehicles device identifier according to an Internet of Vehicles device identifier generation strategy; Feedback the V2X device management entity with the V2X device identifier corresponding to the V2X device; The Internet of Vehicles device identification is sent to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification, and sends the Internet of Vehicles device identification authentication key to a V2X device management entity.

18. The network device according to claim 17, characterized in that: The device parameters of the Internet of Vehicles device include at least one or a combination of the following information: The device manufacturer of the Internet of Vehicles device; The device category of the Internet of Vehicles device; The device model of the Internet of Vehicles device; The product serial number of the Internet of Vehicles device.

19. The network device according to claim 17, characterized in that: After the VID registration agency generates the corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to the Internet of Vehicles device identifier generation strategy, the processor is further configured to: The Internet of Vehicles device identifier is sent to a V2X service entity, so that the V2X service entity uniquely identifies the Internet of Vehicles device based on the Internet of Vehicles device identifier.

20. A network device, characterized in that: include: A memory for storing executable instructions; The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes: Receiving a vehicle networking device identifier sent by a VID registration agency, where the vehicle networking device identifier is generated by the VID registration agency based on device parameters of the vehicle networking device in a configuration request sent by a V2X device management entity and according to a vehicle networking device identifier generation strategy; Based on the Internet of Vehicles device identifier, generating a corresponding Internet of Vehicles device identifier authentication key; The vehicle networking device identification authentication key is sent to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

21. The network device according to claim 20, characterized in that The VID authentication agency sends the vehicle networking device identification authentication key to the V2X device management entity, and the processor is used to: Based on the IoV device identification, directly send the corresponding IoV device identification authentication key to the V2X device management entity; or, In response to the vehicle networking device identity authentication key request sent by the V2X device management entity, the vehicle networking device identity authentication key is sent to the V2X device management entity, wherein the vehicle networking device identity authentication key request includes the vehicle networking device identity.

22. A network device, characterized in that: include: A memory for storing executable instructions; The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes: Receiving an authentication request sent by a vehicle networking device, wherein the authentication request at least includes the vehicle networking device identifier, and the vehicle networking device identifier is obtained from the vehicle networking device identifier VID registration agency and written by the vehicle networking device V2X device management subject based on sending a configuration request including device parameters of the vehicle networking device to the vehicle networking device identifier VID registration agency; Sending an authentication vector request to a VID authentication authority, wherein the authentication vector request at least includes the IoV device identifier; Receiving the authentication vector sent by the VID authentication agency, and sending the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key; Receive the authentication response parameter fed back by the Internet of Vehicles device, and determine the corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

23. The network device according to claim 22, characterized in that The VID authentication function entity receives the authentication response parameter fed back by the Internet of Vehicles device, and determines a corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key, and the processor is used to: Receiving authentication response parameters fed back by the Internet of Vehicles device; Based on the authentication response parameter, perform corresponding operations with other parameters included in the authentication vector; If the information obtained based on the operation is the same as the ciphertext information included in the authentication vector, it is determined that the authentication result representation is passed.

24. A computer device, characterized in that: include: A memory for storing executable instructions; The processor is configured to read and execute the executable instructions stored in the memory to perform the following processes: Sending an authentication request to a vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification, and the vehicle networking device identification is written after being obtained from the VID registration agency by the vehicle networking V2X device management subject based on sending a configuration request including device parameters of the vehicle networking device to the vehicle networking device identification VID registration agency; Receiving an authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on an authentication vector fed back by a VID authentication authority; Based on the authentication parameters, determining corresponding authentication response parameters according to the stored Internet of Vehicles device identification authentication key; and sending the authentication response parameters to the VID authentication function entity; A service response from a V2X service entity is received, wherein the service response is made by the V2X service entity based on an authentication result fed back by the VID authentication function entity.

25. A device for managing identification of connected vehicle equipment, characterized in that: include: A sending unit, configured to send a configuration request to a vehicle networking device identification VID registration agency, wherein the configuration request at least includes device parameters of the vehicle networking device; A first acquisition unit, configured to acquire a connected vehicle device identifier corresponding to the connected vehicle device fed back by the VID registration agency based on the device parameter; A second acquisition unit, configured to acquire a corresponding Internet of Vehicles device identification authentication key from a VID authentication agency based on the Internet of Vehicles device identification; A writing unit is used to write the Internet of Vehicles device identifier and the Internet of Vehicles device identifier authentication key into the Internet of Vehicles device.

26. A device for managing identification of connected vehicle equipment, characterized in that: include: A receiving unit, configured to receive a configuration request sent by a vehicle networking V2X device management subject, wherein the configuration request at least includes device parameters of the vehicle networking device; A generating unit, configured to generate a corresponding Internet of Vehicles device identifier based on the device parameters of the Internet of Vehicles device and according to an Internet of Vehicles device identifier generation strategy; A feedback unit, configured to feed back a vehicle networking device identifier corresponding to the vehicle networking device to a V2X device management entity; The sending unit is used to send the Internet of Vehicles device identifier to a VID authentication agency, so that the VID authentication agency generates a corresponding Internet of Vehicles device identifier authentication key based on the Internet of Vehicles device identifier, and sends the Internet of Vehicles device identifier authentication key to a V2X device management entity.

27. A device for managing vehicle networking equipment identification, characterized in that: include: A receiving unit, configured to receive a vehicle networking device identifier sent by a VID registration agency, wherein the vehicle networking device identifier is generated by the VID registration agency based on device parameters of the vehicle networking device in a configuration request sent by a V2X device management entity and according to a vehicle networking device identifier generation strategy; A generating unit, configured to generate a corresponding Internet of Vehicles device identification authentication key based on the Internet of Vehicles device identification; The sending unit is used to send the vehicle networking device identification authentication key to the V2X device management entity, so that the V2X device management entity writes the vehicle networking device identification authentication key into the vehicle networking device.

28. A device for managing identification of connected vehicle equipment, characterized in that: include: A first receiving unit is configured to receive an authentication request sent by a vehicle networking device, wherein the authentication request at least includes the vehicle networking device identifier, and the vehicle networking device identifier is obtained from the VID registration agency and written by the vehicle networking V2X device management subject based on sending a configuration request including device parameters of the vehicle networking device to the vehicle networking device identifier VID registration agency; A sending unit, configured to send an authentication vector request to a VID authentication authority, wherein the authentication vector request at least includes the Internet of Vehicles device identifier; A second receiving unit is used to receive the authentication vector sent by the VID authentication agency, and send the authentication parameters contained in the authentication vector to the Internet of Vehicles device; wherein the authentication vector is generated by the VID authentication agency based on the Internet of Vehicles device identification authentication key; The third receiving unit is used to receive the authentication response parameter fed back by the Internet of Vehicles device and determine the corresponding authentication result, wherein the authentication response parameter is generated by the Internet of Vehicles device based on the Internet of Vehicles device identification authentication key.

29. A device for managing identification of connected vehicle equipment, characterized in that: include: A sending unit, configured to send an authentication request to a vehicle networking device identification VID authentication function entity, wherein the authentication request at least includes the vehicle networking device identification, and the vehicle networking device identification is written after being obtained from the VID registration agency based on a configuration request including device parameters of the vehicle networking device sent by the vehicle networking V2X device management subject to the vehicle networking device identification VID registration agency; A first receiving unit, configured to receive an authentication parameter fed back by the VID authentication function entity, wherein the authentication parameter is obtained by the VID authentication function entity based on an authentication vector fed back by a VID authentication authority; A determination unit, configured to determine a corresponding authentication response parameter based on the authentication parameter and according to a stored Internet of Vehicles device identification authentication key; and send the authentication response parameter to the VID authentication function entity; The second receiving unit is configured to receive a service response from the V2X service entity, wherein the service response is made by the V2X service entity based on the authentication result fed back by the VID authentication function entity.

30. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute the method according to any one of claims 1 to 4.

31. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute the method according to any one of claims 5 to 7.

32. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to execute the method according to any one of claims 8 to 9.

33. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to perform the method according to any one of claims 10 to 11.

34. A computer-readable storage medium, characterized in that: When the instructions in the computer-readable storage medium are executed by a processor, the processor is enabled to perform the method as claimed in claim 12 .

Images