Vehicle-mounted device registration method, system and storage medium

Abstract

This application provides a method, system, and storage medium for registering in-vehicle devices. The in-vehicle device registration method is applied to an in-vehicle device registration system, which includes: multiple in-vehicle devices of the same model to be registered, a local in-vehicle device management node, and a cloud-based in-vehicle device management node. The method includes: using the local in-vehicle device management node to burn the product number and product key corresponding to the model of the device to be registered to a first in-vehicle device; the model of the device to be registered is the device model of the first in-vehicle device; the first in-vehicle device represents each of the multiple in-vehicle devices to be registered; using the first in-vehicle device, sending a registration request carrying the product number and product key to the cloud-based in-vehicle device management node; and using the cloud-based in-vehicle device management node, in response to successful verification of the product number and product key in the registration request, generating and sending device authentication information to the first in-vehicle device.

Description

Technical Field

[0001] This application relates to the field of vehicle network communication technology, and in particular to a method, system and storage medium for registering vehicle-mounted devices. Background Technology

[0002] In related technologies, a unique identifier and corresponding authentication information are applied for for each connected vehicle device on the vehicle networking platform, and the unique identifier and authentication information are burned into the vehicle device. This allows the vehicle device to use the unique identifier and authentication information to authenticate with the vehicle networking platform during registration and activation. However, in the case of multiple vehicle devices produced in batches, each vehicle device must first apply for its own unique identifier and authentication information when registering on the vehicle networking platform, and then register and activate based on the applied unique identifier and authentication information. Furthermore, a local vehicle device management module is required to uniformly manage the unique identifiers, authentication information, and device information of multiple vehicle devices. As a result, the registration and activation process is cumbersome and requires high management costs to manage a large amount of information. Summary of the Invention

[0003] One of the objectives of this application is to provide a method, system, and storage medium for registering in-vehicle devices, which can uniformly manage product numbers and product keys for the same device type. Based on the product number and product key, multiple in-vehicle devices of the same model can adaptively and automatically register and generate their corresponding device authentication information on the cloud-based in-vehicle device management node. This facilitates information management and production for multiple in-vehicle devices of the same model in the cloud, such as in the registration process of a vehicle networking platform, thereby reducing the management cost of the local in-vehicle device management node and simplifying the overall process of registering and filing in-vehicle devices in the cloud.

[0004] This application provides a method for registering in-vehicle devices, applied to an in-vehicle device registration system. The in-vehicle device registration system includes: multiple in-vehicle devices of the same model to be registered, a local in-vehicle device management node, and a cloud-based in-vehicle device management node. The method includes: Using the local vehicle-mounted device management node, the product number and product key corresponding to the device model to be registered are burned to the first vehicle-mounted device; wherein, the device model to be registered is the device model of the first vehicle-mounted device; the first vehicle-mounted device represents each of the plurality of vehicle-mounted devices to be registered; Using the first vehicle-mounted device, a registration request carrying the product number and the product key is sent to the cloud-based vehicle-mounted device management node; Using the cloud-based vehicle device management node, in response to successful verification of the product number and product key in the registration request, device authentication information is generated and sent to the first vehicle device.

[0005] This application provides a vehicle-mounted device registration system, which includes: multiple vehicle-mounted devices of the same model to be registered, a local vehicle-mounted device management node, and a cloud-based vehicle-mounted device management node; wherein: The local vehicle-mounted device management node is used to burn the product number and product key corresponding to the model of the device to be registered to the first vehicle-mounted device; wherein, the model of the device to be registered is the device model of the first vehicle-mounted device; the first vehicle-mounted device represents each of the plurality of vehicle-mounted devices to be registered; The first vehicle-mounted device is used to send a registration request carrying the product number and the product key to the cloud-based vehicle-mounted device management node; The cloud-based vehicle device management node is used to generate and send device authentication information to the first vehicle device in response to successful verification of the product number and the product key in the registration request.

[0006] Accordingly, this application provides a computer storage medium storing computer-executable instructions, which, when executed, can implement the vehicle-mounted device registration method described above.

[0007] This application provides a method, system, and storage medium for registering in-vehicle devices. The in-vehicle device registration system includes: multiple in-vehicle devices of the same model to be registered, a local in-vehicle device management node, and a cloud-based in-vehicle device management node. The corresponding in-vehicle device registration method includes: firstly, using the local in-vehicle device management node, burning the product number and product key corresponding to the model of the device to be registered to a first in-vehicle device; wherein, the model of the device to be registered is the device model of the first in-vehicle device; the first in-vehicle device represents each of the multiple in-vehicle devices to be registered; using the first in-vehicle device, sending a registration request carrying the product number and the product key to the cloud-based in-vehicle device management node; using the cloud-based in-vehicle device management node, in response to successful verification of the product number and the product key in the registration request, generating and sending device authentication information to the first in-vehicle device. In this way, product numbers and product keys of the same device type can be managed uniformly. Based on the product number and product key, any vehicle-mounted device of that model can adaptively and automatically register and generate its corresponding device authentication information on the cloud-based vehicle-mounted device management node. This facilitates information management and production for multiple vehicle-mounted devices of the same model to be registered in the cloud, such as in the registration process of a vehicle networking platform. This reduces the management cost of the local vehicle-mounted device management node and simplifies the overall process of registering and filing multiple vehicle-mounted devices of the same model in the cloud for mass production.

[0008] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit the technical solutions provided in the embodiments of this application. Attached Figure Description

[0009] To more clearly illustrate the technical solutions in the embodiments of this application, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort, wherein: Figure 1 A flowchart illustrating the first vehicle-mounted device registration method provided in this application embodiment; Figure 2 A flowchart illustrating the second vehicle-mounted device registration method provided in this application embodiment; Figure 3 A flowchart illustrating the third vehicle-mounted device registration method provided in this application embodiment; Figure 4 A schematic diagram of an in-vehicle device registration system corresponding to the in-vehicle device registration method provided in the embodiments of this application; Figure 5 A schematic diagram illustrating the process of registering an on-board device using the on-board device registration method provided in the embodiments of this application; Figure 6 This is a schematic diagram of the structural composition of an in-vehicle device registration system provided in an embodiment of this application. Detailed Implementation

[0010] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.

[0011] In the following description, references are made to “some embodiments,” which describe a subset of all possible embodiments. However, it is understood that “some embodiments” may be the same subset or different subsets of all possible embodiments and may be combined with each other without conflict.

[0012] In the following description, the terms "first, second, third" are used merely to distinguish similar objects and do not represent a specific ordering of objects. It is understood that "first, second, third" may be interchanged in a specific order or sequence where permitted, so that the embodiments of this application described herein can be implemented in an order other than that illustrated or described herein.

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

[0014] To address the problems mentioned in the background art, some embodiments of this application provide a method, system, and storage medium for registering in-vehicle devices. By uniformly managing product numbers and product keys for the same device type, any in-vehicle device of that model can adaptively and automatically register and generate its corresponding device authentication information on a cloud-based in-vehicle device management node based on the product number and product key. This facilitates information management and production for multiple in-vehicle devices of the same model to be registered in the cloud, such as in a vehicle networking platform, thereby reducing the management cost of local in-vehicle device management nodes and simplifying the overall process of registering and filing multiple in-vehicle devices of the same model in the cloud.

[0015] This application provides a method for registering in-vehicle devices, applied to an in-vehicle device registration system. The in-vehicle device registration system includes: multiple in-vehicle devices of the same model to be registered, a local in-vehicle device management node, and a cloud-based in-vehicle device management node; such as... Figure 1 The diagram shows a flowchart illustrating the first vehicle-mounted device registration method provided in this application embodiment; combined with... Figure 1 The steps shown are explained below: Step S101: Using the local vehicle-mounted device management node, the product number and product key corresponding to the device model to be registered are burned to the first vehicle-mounted device.

[0016] Wherein, the model of the device to be registered is the model of the first vehicle-mounted device; the first vehicle-mounted device represents each of the plurality of vehicle-mounted devices to be registered.

[0017] In some embodiments, the vehicle device registration system may be a vehicle device registration system capable of registering various types of vehicles; wherein, vehicle device may refer to a device deployed or applied to any vehicle, such as a monitoring device, display device, control device, etc.; for example, a Telematics Box (T-BOX).

[0018] The product number and product key corresponding to the device model to be registered can be obtained from the cloud-based vehicle device management node using the local vehicle device management node.

[0019] In some embodiments, a local vehicle device management node can be used to implement local information management for multiple vehicle devices; a cloud-based vehicle device management node can be used to manage, register, and activate relevant information of multiple vehicle devices in the cloud, and is deployed on a vehicle networking platform; wherein, multiple vehicle devices include, but are not limited to: multiple vehicle devices of the same device model, and multiple vehicle devices of different device models.

[0020] In some embodiments, the plurality of in-vehicle devices to be registered can be in-vehicle devices of any vehicle series or vehicle. In other embodiments of this application below, "plural" is used to refer to two or more.

[0021] In some embodiments, a local vehicle device management node can first apply for and obtain the product number and product key corresponding to the device model to be registered from the cloud vehicle device management node; then, the local vehicle device management node can burn the obtained product number and product key to each of the multiple vehicle devices to be registered; here, the device model to be registered is the device model of the multiple vehicle devices to be registered; for example, the device model to be registered can be described using any descriptive information, and similarly, the product key and product number can also be represented using any descriptive information.

[0022] It should be noted that the product key and product number are burned into the storage module of the vehicle device to be registered using a local vehicle device management node; among them, the product number and product key corresponding to the same device model are unique.

[0023] Step S102: Using the first vehicle-mounted device, a registration request carrying the product number and the product key is sent to the cloud-based vehicle-mounted device management node.

[0024] In some embodiments, when the first vehicle-mounted device stores a product number and a product key, it can send a registration request carrying the product number and product key to the cloud-based vehicle-mounted device management node based on its internal registration module, so as to realize the device registration and activation of the vehicle-mounted device to be registered in the cloud, i.e., on the vehicle networking platform side; here, the first vehicle-mounted device is each of the multiple vehicle-mounted devices to be registered described above.

[0025] Here, before the on-board device to be registered sends a registration request carrying the product number and product key to the cloud-based on-board device management node using the internal registration module, it is possible to further identify the historical registration records of the on-board device to be registered in order to reconfirm whether the on-board device to be registered has already been registered. Here, this can be done by querying the flag bit corresponding to the storage module of the on-board device to be registered, which is used to indicate whether the on-board device to be registered has been registered on the cloud-based on-board device management node.

[0026] Step S103: Using the cloud-based vehicle device management node, in response to the successful verification of the product number and the product key in the registration request, generate and send device authentication information to the first vehicle device.

[0027] In some embodiments, a cloud-based vehicle device management node is used. In response to the registration request sent by the first vehicle device, if the registration is successfully verified, device authentication information indicating that the first vehicle device has successfully registered is sent to the first vehicle device, so as to realize the successful registration and activation of the first vehicle device on the cloud-based vehicle device management node.

[0028] It should be noted that among multiple vehicle-mounted devices with the same model number to be registered, the device authentication information corresponding to each vehicle-mounted device to be registered is unique; here, among multiple vehicle-mounted devices with the same model number to be registered, the product number and product key corresponding to different vehicle-mounted devices to be registered are the same, but the device authentication information corresponding to them is different.

[0029] Here, a cloud-based vehicle management node can be used to compare and match the pre-stored verification number and verification key of the device model corresponding to the first vehicle device with the product number and product key carried in the registration request sent by the first vehicle device. Based on the comparison and matching results, it can be determined whether the registration request is successful. If successful, the device authentication information corresponding to the successful registration of the first vehicle device is sent to the first vehicle device. If unsuccessful, the registration failure information is sent to the first vehicle device.

[0030] It should be noted that the device authentication information includes the unique identifier of the vehicle-mounted device, key or certificate, and other device information.

[0031] The vehicle-mounted device registration method provided in this application embodiment is applied to a vehicle-mounted device registration system, which includes: multiple vehicle-mounted devices of the same model to be registered, a local vehicle-mounted device management node, and a cloud-based vehicle-mounted device management node. The corresponding vehicle-mounted device registration method includes: firstly, using the local vehicle-mounted device management node, burning the product number and product key corresponding to the model of the device to be registered to a first vehicle-mounted device; wherein, the model of the device to be registered is the device model of the first vehicle-mounted device; the first vehicle-mounted device represents each of the multiple vehicle-mounted devices to be registered; using the first vehicle-mounted device, sending a registration request carrying the product number and the product key to the cloud-based vehicle-mounted device management node; using the cloud-based vehicle-mounted device management node, in response to successful verification of the product number and the product key in the registration request, generating and sending device authentication information to the first vehicle-mounted device. In this way, product numbers and product keys of the same device type can be managed uniformly. Based on the product number and product key, any vehicle-mounted device of that model can adaptively and automatically register and generate its corresponding device authentication information on the cloud-based vehicle-mounted device management node. This facilitates information management and production for multiple vehicle-mounted devices of the same model to be registered in the cloud, such as in the registration process of a vehicle networking platform. This reduces the management cost of the local vehicle-mounted device management node and simplifies the overall process of registering and filing multiple vehicle-mounted devices of the same model in the cloud for mass production.

[0032] In some embodiments, a local vehicle device management node is used. When a vehicle device with the model number to be registered is obtained, an initial request carrying the model number to be registered is sent to the cloud vehicle device management node. Then, the cloud vehicle device management node responds to the initial request by sending the product number and product key corresponding to the model number to be registered to the local vehicle device management node. In this way, by uniformly managing the product number and product key of vehicle devices with the same model number, multiple related information of multiple vehicle devices with the same model number can be easily managed, and information management costs can be reduced. That is, the vehicle device registration method provided in the above embodiments can also perform the following steps S201 and S202 before performing step S101. As shown in Figure 2, it is a flowchart of the second vehicle device registration method provided in this application embodiment. Figure 1 and Figure 2 The steps shown are explained below: Step S201: In response to the acquisition of the vehicle device with the device model to be registered, the local vehicle device management node sends an initial request carrying the device model to be registered to the cloud vehicle device management node.

[0033] In some embodiments, a local vehicle device management node responds to the acquisition of a vehicle device with the device model to be registered. Here, the vehicle device with the device model to be registered may be registered at the local vehicle device management node after production, or after initial local registration at the local vehicle device management node, the local vehicle device management node may send an initial request carrying the device signal to be registered to the cloud vehicle device management node to obtain the product number and product key corresponding to the device model to be registered in the cloud, i.e., on the vehicle network side.

[0034] Step S202: In response to the initial request, the cloud-based vehicle device management node sends the product number and product key corresponding to the device model to be registered to the local vehicle device management node.

[0035] In some embodiments, a cloud-based vehicle device management node responds to the received initial request by generating a corresponding product number and product key for the device model to be registered, and then sends the product number and product key to the local vehicle device management node. Here, the management module in the cloud-based vehicle device management node may respond to the initial request by generating the corresponding product number and product key, and the information transmission module in the cloud-based vehicle device management node may send the product number and product key to the local vehicle device management node.

[0036] Here, a local vehicle device management node is further used to burn the product number and product key corresponding to the device model to be registered to multiple vehicle devices with the same model.

[0037] In some embodiments, before the first vehicle-mounted device sends a registration request carrying a product number and product key to the cloud-based vehicle-mounted device management node, the main control module of the first vehicle-mounted device can first identify the flag bit of its internal storage module. If the identification result indicates that the first vehicle-mounted device has not been registered, the first vehicle-mounted device registration module can initiate the registration request to the cloud-based vehicle-mounted device management node. This allows for the identification of the first vehicle-mounted device's registration status during the initiation of the relevant registration request, preventing duplicate registration and making the registration process of the first vehicle-mounted device to the cloud-based vehicle-mounted device management node more accurate. That is, step S102 provided in the above embodiments can be implemented by the following steps S301 and S302, such as... Figure 3 The diagram shows a flowchart illustrating the third vehicle-mounted device registration method provided in this application embodiment; combined with... Figure 1 and Figure 3 The steps shown are explained below: Step S301: Using the main control module of the first vehicle-mounted device, in response to the fact that the storage module of the first vehicle-mounted device stores the product number and the product key, the flag bit of the storage module is identified.

[0038] In some embodiments, the main control module of the first vehicle-mounted device is used. In response to the fact that the storage module of the first vehicle-mounted device stores the product number and product key corresponding to its device model, the flag bit of the storage module is identified accordingly. Here, the flag bit of the storage module can be represented by 1 or 0. For example, 1 indicates that it has been registered, and 0 indicates that it has not been registered.

[0039] Step S302: Using the first vehicle-mounted device registration module, if the flag indicates that the first vehicle-mounted device has not been registered, the registration request is sent to the cloud-based vehicle-mounted device management node.

[0040] Based on the above description, the first vehicle-mounted device is each of the multiple vehicle-mounted devices to be registered with the same device model. Among the multiple vehicle-mounted devices to be registered with the same device model, there may be a situation where vehicle-mounted device 1 to be registered has been registered, while vehicle-mounted device 2 to be registered has not been registered. Therefore, the first vehicle-mounted device registration module is used to send a registration request to the cloud vehicle-mounted device management node to register the device only when the flag indicates that the first vehicle-mounted device has not been registered.

[0041] Correspondingly, firstly, the cloud-based vehicle device management node, in response to successful verification of the product number and the product key, generates and sends device authentication information to the first vehicle device registration module; then, the vehicle device registration module to be registered stores the obtained device authentication information in the storage module of the first vehicle device, thereby completing the registration of the first vehicle device at the cloud-based vehicle device management node; thus, for multiple devices with the same model number as the device to be registered, the registration and filing process at the cloud-based vehicle management node (platform) can be simplified; that is, step S103 provided in the above embodiment can be implemented by the following steps S301 and S302: Step S303: Using the cloud-based vehicle device management node, in response to the successful verification of the product number and the product key, generate and send the device authentication information to the first vehicle device registration module.

[0042] In some embodiments, a cloud-based vehicle device management node is used. In response to successful verification of the product number and the product key, the generated device authentication information is sent to the first vehicle device registration module.

[0043] Step S304: Using the first vehicle-mounted device registration module, the obtained device authentication information is stored in the storage module of the first vehicle-mounted device, so that the registration of the first vehicle-mounted device on the cloud-based vehicle-mounted device management node is completed.

[0044] In some embodiments, the first vehicle-mounted device registration module stores the obtained device authentication information in the storage module of the first vehicle-mounted device to complete the registration and filing process of the first vehicle-mounted device on the cloud-based vehicle-mounted device management node; then, multiple vehicle-mounted devices of the same model can use the obtained device authentication information to connect and communicate with the vehicle network platform, i.e., the cloud-based vehicle-mounted device management node.

[0045] Here, at the cloud-based vehicle device management node, in response to the successful verification of the product number and product key in the registration request, before sending the device authentication information of the first vehicle device to the first vehicle device, the cloud registration module of the cloud-based vehicle device management node can also be used. In response to the registration request sent by the vehicle device to be registered, the device model of the first vehicle device is obtained from the cloud management module of the cloud-based vehicle device management node, that is, the verification number and verification key corresponding to the model of the device to be registered, which are stored in advance for registration verification. Then, the cloud registration module can be further used to verify the product number and product key carried in the registration request based on the obtained verification number and verification key, thereby determining the verification result of the product number and the verification result of the product key. In this way, before the registration process of multiple vehicle devices with the same device model on the cloud-based vehicle management platform, that is, the cloud-based vehicle device management node, that is, before step S103 or step S303 provided in the above embodiment, the following steps A1 and A2 are also performed in this application embodiment: Step A1: In response to the registration request, the cloud registration module of the cloud-based vehicle device management node obtains the verification number and verification key corresponding to the model of the device to be registered from the cloud management module of the cloud-based vehicle device management node.

[0046] Step A2: Using the cloud registration module, based on the verification number and the verification key, determine the first verification result for the product number and the second verification result for the product key.

[0047] In some possible implementations, a cloud registration module can be used. A verification number is used to verify the product number's validity, yielding a first verification result. Simultaneously, a verification key is used to verify the product key's validity, yielding a second verification result. That is, step A2 can be implemented using steps A21 and A22. Step A21: Using the cloud registration module, compare the verification number and the product number to obtain the first verification result.

[0048] Step A22: Using the cloud registration module, the verification key and the product key are matched to obtain a second verification result.

[0049] It should be noted that, in this embodiment, if a cloud-based vehicle device management node (cloud registration module) is used, and the verification of any information in the registration request, namely at least one of the product number and product key, fails, the corresponding authentication fails and is sent to the first vehicle device. Therefore, the vehicle device registration method provided in this embodiment can also implement the following process: The cloud-based vehicle device management node generates and sends registration failure information to the first vehicle device in response to the failure to verify the product number and / or the product key in the registration request.

[0050] In some embodiments, a cloud-based vehicle device management node is used to generate and send registration failure information to the first vehicle device registration module in response to the failure to verify the product number and / or product key in the registration request. The registration module then forwards the registration failure message to the control module of the first vehicle device to issue a prompt message.

[0051] It should be noted that among multiple in-vehicle devices of the same model to be registered, the registration results of different in-vehicle devices on the cloud in-vehicle device management node may be different. That is, some may be registered successfully, all may be registered successfully, or all may be registered unsuccessfully.

[0052] The following describes the vehicle-mounted device registration method with reference to a specific embodiment. However, it is worth noting that this specific embodiment is only for better illustrating the embodiments of this application and does not constitute an improper limitation on the embodiments of this application.

[0053] With the continuous development of connected vehicle services, connected vehicle platforms will provide services for different brands and types of in-vehicle devices. A common method for managing in-vehicle smart devices is for smart device suppliers to apply for a unique identifier and corresponding authentication information for each connected in-vehicle smart device (hereinafter referred to as the in-vehicle device, and also the in-vehicle device to be registered in the above embodiment) on the connected vehicle platform. Common authentication information includes certificates or keys. The unique identifier and authentication information are then burned into the in-vehicle smart device. Finally, when activated, the in-vehicle smart device uses this burned information to authenticate with the connected vehicle platform. While this method offers high security, for in-vehicle smart device manufacturers, mass production of multiple devices presents challenges. The registration process for each individual in-vehicle smart device is complex, and managing the relationship between the unique identifier, authentication information, and other device information required by the connected vehicle platform and the device's own information is crucial, resulting in high information management costs.

[0054] Based on this, this application proposes an automatic registration method and system for in-vehicle devices; wherein, the automatic registration system for in-vehicle devices includes: a cloud device management module 401, a cloud device registration module 402, a local device management module 403, an in-vehicle device registration module 404, and an in-vehicle device storage module 405; here, the method and system are described using one in-vehicle device as an example. Figure 4 The diagram shown is a schematic of an on-board device registration system corresponding to the on-board device registration method provided in the embodiments of this application; wherein: Cloud Device Management Module 401: Deployed on the vehicle networking platform, it is responsible for applying for and managing the product codes and product keys of a certain type of vehicle-mounted equipment; Cloud device registration module 402: Also deployed on the vehicle network platform, after receiving an automatic registration request containing product number and product key sent by local device registration module 404, it verifies the legality of product number and product key, and automatically creates specific device information for such product number and product key. The device information includes the device's unique identifier, key or certificate, and other device information. After creation, it returns this information to the device's local storage module 405 through local device registration module 404.

[0055] Local Device Management Module 403: Responsible for applying for product codes and product keys for a type of vehicle-mounted equipment, and uniformly burning the product codes and product keys into the corresponding vehicle-mounted equipment. The same product code and product key can be burned into multiple vehicle-mounted equipment.

[0056] Vehicle device registration module 404: It is responsible for initiating an automatic registration process to the cloud device registration module 402 based on the product code and product key stored in the vehicle device storage module 405. After successful registration, it obtains specific device information such as the device's unique identifier and device authentication information.

[0057] In addition to storing the product code and product key, the local device storage module 405 also stores the specific device information returned by the vehicle-to-everything (V2X) platform, i.e., the cloud-based device registration module 402, after the device has automatically registered. After registration, this specific device information will be used to connect and communicate with the V2X platform.

[0058] Furthermore, this application also proposes a method for automatic registration of in-vehicle devices, the corresponding process of which is as follows: Figure 5 The diagram shown is a flowchart illustrating the process of registering an on-board device using the on-board device registration method provided in this application embodiment; here, reference is also made to... Figure 4 and Figure 5First, step 501 is executed: Start; then step 502 is executed: Apply for product code (corresponding to the product number in the embodiment) and key, that is, the local device management module 403 applies for a product code and product key for a certain model of vehicle device in the vehicle network cloud device management module 401; then, after obtaining the product code and product key, step 503 is executed: Burn the product code and key to a batch of vehicle devices, that is, the local device management module 403 burns the product code and product key to a batch of vehicle devices and stores them in the vehicle device storage module 405; second, step 504 is executed: Initiate automatic registration based on the product code and key, that is, the vehicle device registration module 404, based on the product code and product key and other elements stored in the vehicle device storage module 405, sends a request to the vehicle network platform automatic registration module (cloud device registration module 402). The system initiates an automatic registration request. Next, step 505 is executed: verifying the product code and product key, generating specific device information. Specifically, the vehicle network platform automatic registration module (cloud device registration module 402) verifies the legality of the automatic registration request using the product number and product key stored in the vehicle network platform device management module (cloud device management module 402). If the verification fails, the automatic registration process ends. If the verification succeeds, a unique device identifier and device authentication information (including but not limited to certificates and keys) are automatically registered for the device, and this information is returned to the in-vehicle device registration module 404. Finally, step 506 is executed: completing cloud connection and communication based on the specific device information. After successful registration by the in-vehicle automatic module, the unique device identifier and device authentication information (including but not limited to certificates and keys) are stored in the in-vehicle device storage module 405, completing the automatic device registration. Subsequently, the in-vehicle device reads device information from the device storage module to complete connection and communication with the vehicle network platform, as well as step 507.

[0059] This application proposes a method and system for registering in-vehicle devices. It provides unified management of product numbers and product keys for the same device type. Based on these product numbers and keys, any in-vehicle device of that model can adaptively and automatically register and generate its corresponding device authentication information on a cloud-based in-vehicle device management node. This facilitates information management and production for multiple in-vehicle devices of the same model in the cloud, such as those on a vehicle networking platform. It also reduces the management costs of local in-vehicle device management nodes, thereby simplifying the registration and filing process for multiple in-vehicle devices of the same model produced in batches on the cloud.

[0060] This application provides a vehicle-mounted device registration system. Figure 6 This is a schematic diagram of the structural composition of an in-vehicle device registration system provided in an embodiment of this application, as shown below. Figure 6As shown, the vehicle-mounted device registration system 600 includes: multiple vehicle-mounted devices 601 of the same model to be registered, a local vehicle-mounted device management node 602, and a cloud-based vehicle-mounted device management node 603; The local vehicle-mounted device management node 602 is used to burn the product number and product key corresponding to the model of the device to be registered to the first vehicle-mounted device 601; wherein, the model of the device to be registered is the device model of the first vehicle-mounted device; the first vehicle-mounted device represents each of the plurality of vehicle-mounted devices to be registered. The first vehicle-mounted device 601 is used to send a registration request carrying the product number and the product key to the cloud-based vehicle-mounted device management node 603; The cloud-based vehicle device management node 603 is used to generate and send device authentication information to the first vehicle device 601 in response to successful verification of the product number and the product key in the registration request.

[0061] In some embodiments, the local vehicle device management node 602 is configured to send an initial request carrying the device model to be registered to the cloud vehicle device management node 603 in response to the acquisition of the vehicle device 601 with the device model to be registered; the cloud vehicle device management node 603 is configured to send the product number and the product key corresponding to the device model to be registered to the local vehicle device management node 602 in response to the initial request.

[0062] In some embodiments, the main control module of the first vehicle-mounted device 601 is used to identify the flag bit of the storage module in response to the storage module of the first vehicle-mounted device 601 storing the product number and the product key; and the registration module of the first vehicle-mounted device 601 is used to send the registration request to the cloud vehicle-mounted device management node 603 when the flag bit indicates that the first vehicle-mounted device has not been registered.

[0063] In some embodiments, the cloud registration module of the cloud-based vehicle device management node 603 is used to, in response to the registration request, obtain the verification number and verification key corresponding to the device model to be registered from the cloud management module of the cloud-based vehicle device management node 603; the cloud registration module is used to determine a first verification result for the product number and a second verification result for the product key based on the verification number and the verification key.

[0064] In some embodiments, the cloud registration module is used to compare the verification number and the product number to obtain a first verification result; the cloud registration module is used to match the verification key and the product key to obtain a second verification result.

[0065] In some embodiments, the cloud-based vehicle device management node 603 is configured to generate and send the device authentication information to the registration module of the first vehicle device 601 in response to successful verification of the product number and the product key; the registration module of the first vehicle device 601 stores the acquired device authentication information in the storage module of the first vehicle device 601, so that the registration of the first vehicle device 601 on the cloud-based vehicle device management node 603 is completed.

[0066] In some embodiments, the cloud-based vehicle device management node 603 is further configured to generate and send registration failure information to the first vehicle device 601 in response to the failure to verify the product number and / or the product key in the registration request.

[0067] It should be noted that the description of the above system embodiments is similar to the description of the above method embodiments, and has similar beneficial effects. For technical details not disclosed in the system embodiments of this application, please refer to the description of the method embodiments of this application for understanding.

[0068] It should be noted that, in the embodiments of this application, if the above-described object recognition method is implemented as a software functional module and sold or used as an independent product, it can also be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the embodiments of this application, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a terminal, server, etc.) to execute all or part of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, mobile hard drives, read-only memory (ROM), magnetic disks, or optical disks. Thus, the embodiments of this application are not limited to any specific hardware and software combination.

[0069] Correspondingly, this application embodiment further provides a computer program product, which includes computer-executable instructions. After the computer-executable instructions are executed, they can implement the vehicle device registration method provided in this application embodiment.

[0070] Accordingly, this application embodiment further provides a computer storage medium storing computer-executable instructions, which, when executed by a processor, implement the vehicle device registration method provided in the above embodiment.

[0071] The descriptions of the above embodiments of the vehicle-mounted device registration system and storage medium are similar to those of the above method embodiments, and have similar technical descriptions and beneficial effects. Due to space limitations, the descriptions of the above method embodiments can be followed, and therefore will not be repeated here. For technical details not disclosed in the embodiments of the vehicle-mounted device registration method, system, and storage medium of this application, please refer to the descriptions of the method embodiments of this application for understanding.

[0072] It should be understood that the phrase "an embodiment" or "one embodiment" throughout the specification means that a specific feature, structure, or characteristic related to the embodiment is included in at least one embodiment of the present application. Therefore, "in one embodiment" or "one embodiment" appearing throughout the specification does not necessarily refer to the same embodiment. Furthermore, these specific features, structures, or characteristics can be combined in any suitable manner in one or more embodiments. It should be understood that in the various embodiments of the present application, the sequence number of the above-described processes does not imply the order of execution; the execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of the present application. The sequence numbers of the above-described embodiments are merely for descriptive purposes and do not represent the superiority or inferiority of the embodiments. It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Without further limitations, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes that element.

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

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

[0075] Furthermore, in the embodiments of this application, all functional units can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or in a combination of hardware and software functional units. Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium, and when executed, it performs the steps of the above method embodiments.

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

Claims

1. A method for registering an on-board device, characterized in that, An application is made in a vehicle-mounted device registration system, the system comprising: multiple vehicle-mounted devices of the same model to be registered, a local vehicle-mounted device management node, and a cloud-based vehicle-mounted device management node; the method includes: Using the local vehicle device management node, obtain the product number and product key corresponding to the model of the device to be registered. The product number and product key are the same for multiple vehicle devices with the same model to be registered. The product number and product key are burned to the first vehicle device using the local vehicle device management node; wherein, the model of the device to be registered is the device model of the first vehicle device; the first vehicle device represents each of the plurality of vehicle devices to be registered; the cloud vehicle device management node generates unique device authentication information for each successfully registered vehicle device; Using the main control module of the first vehicle-mounted device, in response to the storage module of the first vehicle-mounted device storing the product number and the product key, the flag bit of the storage module is identified; Using the first vehicle-mounted device registration module, when the flag indicates that the first vehicle-mounted device has not been registered, a registration request carrying the product number and the product key is sent to the cloud-based vehicle-mounted device management node; Using the cloud-based vehicle device management node, in response to successful verification of the product number and the product key in the registration request, the device authentication information is generated and sent to the first vehicle device registration module. The first vehicle-mounted device registration module is used to store the acquired device authentication information in the storage module of the first vehicle-mounted device, so that the registration of the first vehicle-mounted device on the cloud-based vehicle-mounted device management node is completed.

2. The vehicle-mounted device registration method according to claim 1, characterized in that, Before using the local vehicle-mounted device management node to burn the product number and product key corresponding to the device model to be registered to the first vehicle-mounted device, the method further includes: In response to the acquisition of an in-vehicle device with the device model to be registered, the local in-vehicle device management node sends an initial request carrying the device model to be registered to the cloud in-vehicle device management node. In response to the initial request, the cloud-based vehicle device management node sends the product number and product key corresponding to the device model to be registered to the local vehicle device management node.

3. The vehicle-mounted device registration method according to claim 1 or 2, characterized in that, Before generating and sending device authentication information to the first vehicle device in response to successful verification of the product number and product key in the registration request by the cloud-based vehicle device management node, the method further includes: The cloud registration module of the cloud-based vehicle device management node, in response to the registration request, obtains the verification number and verification key corresponding to the model of the device to be registered from the cloud management module of the cloud-based vehicle device management node; Using the cloud registration module, based on the verification number and the verification key, a first verification result for the product number and a second verification result for the product key are determined.

4. The vehicle-mounted device registration method according to claim 3, characterized in that, The process of using the cloud registration module to determine the first verification result for the product number and the second verification result for the product key based on the verification number and the verification key includes: The cloud registration module is used to compare the verification number and the product number to obtain a first verification result; The cloud registration module is used to match the verification key and the product key to obtain a second verification result.

5. The vehicle-mounted device registration method according to any one of claims 1 to 4, characterized in that, The method further includes: The cloud-based vehicle device management node generates and sends registration failure information to the first vehicle device in response to the failure to verify the product number and / or the product key in the registration request.

6. A vehicle-mounted device registration system, characterized in that, The vehicle-mounted device registration system includes: multiple vehicle-mounted devices of the same model to be registered, a local vehicle-mounted device management node, and a cloud-based vehicle-mounted device management node; wherein: The local vehicle-mounted device management node is used to obtain the product number and product key corresponding to the model of the device to be registered, wherein the product number and product key are the same for multiple vehicle-mounted devices of the same model; it is also used to burn the product number and product key to the first vehicle-mounted device; wherein the model of the device to be registered is the device model of the first vehicle-mounted device; the first vehicle-mounted device represents each of the multiple vehicle-mounted devices to be registered; the product number and product key are the same for multiple vehicle-mounted devices of the same model; the cloud-based vehicle-mounted device management node generates unique device authentication information for each successfully registered vehicle-mounted device; The main control module of the first vehicle-mounted device is used to identify the flag bit of the storage module in response to the storage module of the first vehicle-mounted device storing the product number and the product key; The first vehicle-mounted device registration module is used to send a registration request carrying the product number and the product key to the cloud-based vehicle-mounted device management node when the flag indicates that the first vehicle-mounted device has not been registered. The cloud-based vehicle device management node is used to generate and send the device authentication information to the first vehicle device registration module in response to successful verification of the product number and the product key in the registration request. The first vehicle-mounted device registration module is further configured to store the acquired device authentication information in the storage module of the first vehicle-mounted device, so that the registration of the first vehicle-mounted device on the cloud-based vehicle-mounted device management node is completed.

7. The vehicle-mounted device registration system according to claim 6, characterized in that, The local vehicle device management node is used to send an initial request carrying the device model to be registered to the cloud vehicle device management node in response to the acquisition of the vehicle device with the device model to be registered. The cloud-based vehicle device management node is used to respond to the initial request by sending the product number and product key corresponding to the device model to be registered to the local vehicle device management node.

8. A computer storage medium, characterized in that, The computer storage medium stores computer-executable instructions, which, when executed, enable the vehicle-mounted device registration method according to any one of claims 1 to 5.

Images