Control methods, devices, vehicle electronic equipment and products for pluggable devices in vehicles
By using a device authentication and object model acquisition method that coordinates vehicle terminals and the cloud, the problem of inconsistent protocols for pluggable in-vehicle devices from different manufacturers has been solved. This has enabled unified command interoperability between vehicle terminals and pluggable devices, reducing adaptation costs and improving system compatibility and flexibility.
Patent Information
- Application Number
- CN202611238053.6
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-08-14
- Publication Date
- 2026-11-17
AI Technical Summary
Due to the lack of unified protocols among pluggable automotive devices from different manufacturers, it is difficult for vehicle terminals and pluggable devices to communicate with each other. Existing technologies cannot achieve a unified object model description, which means that vehicle terminals need to write parsing and control logic for each device separately, resulting in repetitive and costly adaptation work.
After the vehicle terminal detection device is inserted, the device's identity information is obtained and authenticated to the cloud. The cloud provides unified authentication and a physical model. The vehicle terminal generates control commands based on the physical model, realizing a unified processing link for device access, identity authentication, capability acquisition, and control execution, reducing reliance on private protocols.
It enables unified command interoperability between vehicle terminals for pluggable devices from different manufacturers and with different protocol versions, reducing the adaptation and expansion costs of vehicle terminals and improving the system's compatibility and flexibility.
Smart Images

Figure CN123122889A_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the technical field of vehicle control, and specifically to a control method, device, vehicle electronic equipment, and product for a pluggable in-vehicle device. Background Technology
[0002] With the rapid development of smart cockpits and vehicle-to-everything (V2X) technologies, pluggable in-vehicle devices (such as in-vehicle refrigerators, game controllers, external sensors, and expansion hardware) have become an important way to personalize vehicle functions. However, different manufacturers use different device protocols for their pluggable devices, resulting in a lack of a unified object model to standardize the description of device capabilities (such as attributes, services, and events) between the vehicle terminal and the pluggable devices, making command interoperability difficult. Therefore, how to provide a unified object model for pluggable in-vehicle devices to enable command interoperability between the vehicle terminal and the pluggable devices is an urgent problem to be solved. Summary of the Invention
[0003] One of the objectives of this invention is to provide a control method, device, vehicle electronic equipment, and product for vehicle-mounted pluggable devices, in order to solve the problem in the prior art of how to provide a physical model for vehicle-mounted pluggable devices in a unified manner to enable command interoperability between vehicle terminals and pluggable devices.
[0004] To achieve the above objectives, the technical solution adopted by the present invention is as follows:
[0005] In a first aspect, the present invention provides a control method for a vehicle-mounted pluggable device. The control method is applicable to a vehicle terminal, which is installed on a vehicle. The control method includes:
[0006] When device insertion information is detected, the device identity information of the device to be authenticated is obtained; where the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle.
[0007] Based on the device identity information, generate and send a device authentication request to the cloud;
[0008] When the first cloud response to the received device authentication request is an authentication pass response, the device to be authenticated is marked as an authenticated device, and a pull request for the object model corresponding to the authenticated device is generated and sent to the cloud.
[0009] Based on the second cloud response information corresponding to the received object model retrieval request, obtain the object model;
[0010] Based on the object model, control commands for certified devices are generated and issued.
[0011] Based on the aforementioned technical means, the vehicle terminal integrates the access, authentication, capability acquisition, and control execution of pluggable in-vehicle devices into a unified processing chain. First, a unified trusted entry point is established through cloud authentication, and then subsequent control adaptation is completed through the object model. Therefore, pluggable devices from different manufacturers and with different protocol versions can all use the same upper-layer processing flow after being connected to the vehicle. The vehicle terminal does not need to separately solidify and resolve control logic for each pluggable in-vehicle device. Furthermore, changes in device capabilities are primarily reflected in the vehicle terminal through the object model returned from the cloud, eliminating the need for repeated parsing and adaptation by the vehicle terminal.
[0012] Furthermore, after generating a device authentication request based on the device identity information, the control method also includes:
[0013] Based on the vehicle security token, timestamp, and random number, a message authentication code algorithm is used to perform a signature anti-tampering operation on the device authentication request. The device authentication request after the signature anti-tampering operation is then sent to the cloud.
[0014] Based on the above technical means, a vehicle security token, timestamp, and random number are introduced before the device authentication request is sent, and message authentication code calculation is performed. This ensures that the integrity, authenticity, and timeliness of the device authentication request are all constrained. After receiving the request, the cloud can directly complete the verification and enter the authentication process, thereby ensuring that the device access link between the vehicle and the cloud maintains a consistent security verification mechanism.
[0015] Furthermore, the object model includes at least model components and mapping relationships, wherein the model components include at least attributes, events, and services, and the mapping relationships are used to assign labels to attributes, events, and services.
[0016] Based on the above technical means, the object model can describe device capabilities with unified model components and tags. The tag mapping relationship enables a stable correspondence between device capability items and protocol messages. When facing different devices, the vehicle terminal only needs to convert according to the object model, which reduces the coupling of private protocol parsing logic and improves the compatibility and expansion consistency after external pluggable devices are connected.
[0017] Furthermore, the tag length is 2 bytes.
[0018] Furthermore, based on the object model, control commands for certified devices are generated and issued, specifically including:
[0019] Based on the object model, the device operation command is converted into the first TLV message, wherein the device operation command is a command generated in the vehicle's infotainment system for controlling the operation of the certified device;
[0020] The first TLV message is converted into the first binary data, and the converted first binary data is recorded as a control command;
[0021] Sending the control instruction to the authenticated device.
[0022] According to the above technical means, with the thing model as the unified carrier of control semantics, the device operation instruction formed on the vehicle terminal side can be converted into standardized binary control data through the TLV message structure, and then sent to the authenticated device, so that the vehicle-end control message is consistent with the device capability description, the dependence of the vehicle terminal side on the private protocol of the device is reduced, and the difference in the organization of control messages for devices from different manufacturers is lowered.
[0023] Further, the control method further comprises:
[0024] Converting the received second binary data into a second TLV message;
[0025] Converting the second TLV message into device uplink data according to the thing model, wherein the device uplink data is used for representing the operating state of the authenticated device.
[0026] According to the above technical means, the thing model is used as a unified parsing reference, so that the second TLV message can be decoded without relying on the private format of the device, and the device uplink data serves as a unified data bearing form for the vehicle terminal to perform display, recording or linkage control. By converting the original binary data into the second TLV message first, and then further generating the device uplink data based on the thing model, the operation information of authenticated devices from different manufacturers can be identified and utilized according to consistent data semantics, thereby realizing unified management and presentation of device states.
[0027] Further, the device identity information includes at least one of a device type, a unique device identifier, a device SN, a device certificate, a device private key signature, and a device public key certificate.
[0028] Further, the control method further comprises:
[0029] When device unplugging information is detected, generating and sending a device unbinding request to the cloud end based on the device identity information of the authenticated device, wherein the device unplugging information is information generated when the authenticated device is unplugged from the vehicle;
[0030] Clearing the thing model and the device cache information of the authenticated device according to the received third cloud response information of the device unbinding request.
[0031] According to the above technical means, when the vehicle-mounted pluggable device is unplugged, a device unbinding request is generated in a linkage manner, and the local thing model and device cache information are cleared according to the third cloud response information issued by the cloud end, so that the vehicle end can terminate the binding relationship of the authenticated device in time and release the occupied resources, and the authentication and capability acquisition process can be re-experienced when the device is inserted again later, thereby maintaining the consistency of the device state and reducing the interference of invalid configurations on the vehicle-end control link.
[0032] Secondly, the present invention provides a control method for a vehicle-mounted pluggable device, the control method being applicable to the cloud, and the control method comprising:
[0033] Receive device authentication requests sent by any vehicle terminal;
[0034] Extract device identity information from the device authentication request;
[0035] Based on the device identity information, device authentication is performed, which includes at least one of the following: device registration status authentication, certificate validity authentication, and access permission authentication.
[0036] Upon successful device authentication, a globally unique device identifier and the corresponding first cloud response information are generated. The globally unique device identifier is used to represent the correspondence between the pluggable device and the vehicle terminal corresponding to the device identity information.
[0037] Send the first cloud response information to the corresponding vehicle terminal;
[0038] Based on the received object model retrieval request, generate a second cloud response message;
[0039] Based on the response information from the second cloud, the object model corresponding to the object model retrieval request is sent to the corresponding vehicle terminal.
[0040] Based on the aforementioned technical means, the cloud establishes a unified authentication entry point for the access of pluggable in-vehicle devices. Using device identity information as a foundation, it implements device registration status authentication, certificate validity authentication, and access permission authentication. Upon successful authentication, a globally unique device identifier is generated to represent the correspondence between the device and the vehicle terminal. A matching object model is then distributed to the vehicle terminal according to this correspondence, ensuring that subsequent control processes revolve around a unified capability description. In this way, the vehicle terminal does not need to separately solidify parsing and control logic for devices from different manufacturers; when device protocol versions change, adaptation and updates are primarily completed through cloud-side model management.
[0041] Furthermore, the control methods also include:
[0042] Based on the received device unbinding request, clear the globally unique device identifier;
[0043] Generate and send third-party cloud response information to the corresponding vehicle terminal.
[0044] Based on the above technical means, the globally unique device identifier is promptly cleared after unbinding, and the third cloud response information feeds back the result to the vehicle terminal, so that the vehicle terminal can accurately complete the state synchronization and permission revocation, reduce the identification confusion caused by residual binding relationships, and enable subsequent devices to re-authenticate and re-establish the chain when they reconnect.
[0045] Furthermore, the control methods also include:
[0046] Based on the device identity information of any pluggable device received, the device is registered, and the legality of the certificate and access permissions corresponding to the pluggable device are determined.
[0047] Furthermore, the control methods also include:
[0048] After the device registration of the pluggable device is approved, a device certificate corresponding to the pluggable device is generated based on the device identity information. The device certificate is used to verify the legality of the certificate.
[0049] Based on the aforementioned technical means, by generating a device certificate associated with the device's identity information after the device registration is approved, and using it for certificate legality authentication, a stable correspondence can be established between the device identity and subsequent authentication credentials. This allows the device registration result to be directly incorporated into the access verification process, thereby enhancing the credibility and consistency of the pluggable device access process.
[0050] Thirdly, the present invention provides a control device for a vehicle-mounted pluggable device, the control device being suitable for a vehicle terminal installed on a vehicle, and the control device comprising:
[0051] The acquisition module is used to acquire the device identity information of the device to be authenticated when device insertion information is detected; wherein, the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle;
[0052] The request module is used to generate and send device authentication requests to the cloud based on device identity information;
[0053] The request module is also used to mark the device to be authenticated as an authenticated device when the first cloud response information of the received device authentication request is an authentication pass response information, and to generate and send the object model pull request corresponding to the authenticated device to the cloud.
[0054] The acquisition module is also used to acquire the object model based on the second cloud response information corresponding to the received object model pull request;
[0055] The first generation module is used to generate and issue control commands for certified devices based on the object model.
[0056] Furthermore, after generating a device authentication request based on the device identity information, the control device also includes:
[0057] The signature module is used to perform a signature anti-tampering operation on the device authentication request based on the vehicle security token, timestamp, and random number using a message authentication code algorithm. The device authentication request after the signature anti-tampering operation is then sent to the cloud.
[0058] Furthermore, the object model includes at least model components and mapping relationships, wherein the model components include at least attributes, events, and services, and the mapping relationships are used to assign labels to attributes, events, and services.
[0059] Furthermore, the tag length is 2 bytes.
[0060] Furthermore, the first generation module specifically includes:
[0061] The conversion submodule is used to convert the device operation instructions into the first TLV message according to the object model. The device operation instructions are the instructions generated in the vehicle's infotainment system for controlling the operation of certified devices.
[0062] The conversion submodule is also used to convert the first TLV message into first binary data and record the converted first binary data as a control command;
[0063] The sending submodule is used to send control commands to the authenticated device.
[0064] Furthermore, the conversion submodule is also used for:
[0065] Convert the received second binary data into a second TLV message;
[0066] Based on the object model, the second TLV message is converted into device uplink data, where the device uplink data is used to characterize the operating status of the certified device.
[0067] Furthermore, the device identity information includes at least one of the following: device type, device unique identifier, device serial number (SN), device certificate, device private key signature, and device public key certificate.
[0068] Furthermore, the request module is also used to generate and send a device unbinding request to the cloud based on the device identity information of the authenticated device when the device unbinding information is detected. The device unbinding information is the information generated when the authenticated device is unbound from the vehicle.
[0069] The control device also includes an unbinding module, which is used to clear the device cache information of the object model and the certified device based on the third cloud response information of the received device unbinding request.
[0070] Fourthly, the present invention provides a control device for a vehicle-mounted pluggable device, the control device being suitable for cloud computing, and the control device comprising:
[0071] The receiving module is used to receive device authentication requests sent by any vehicle terminal.
[0072] The extraction module is used to extract device identity information from device authentication requests;
[0073] The authentication module is used to authenticate devices based on their identity information. Device authentication includes at least one of the following: device registration status authentication, certificate validity authentication, and access permission authentication.
[0074] The second generation module is used to generate a globally unique device identifier and the first cloud response information corresponding to the globally unique device identifier when the device authentication is successful; wherein, the globally unique device identifier is used to represent the correspondence between the pluggable device corresponding to the device identity information and the vehicle terminal;
[0075] The sending module is used to send the first cloud response information to the corresponding vehicle terminal;
[0076] The second generation module is also used to generate a second cloud response information based on the received object model retrieval request;
[0077] The sending module is also used to send the object model corresponding to the object model pull request to the corresponding vehicle terminal based on the response information from the second cloud.
[0078] Furthermore, the control device also includes:
[0079] The clearing module is used to clear the globally unique device identifier based on the received device unbinding request;
[0080] The second generation module is also used to generate and send the third cloud response information to the corresponding vehicle terminal.
[0081] Furthermore, the control device also includes:
[0082] The registration module is used to register any pluggable device based on its device identity information and to determine the validity of the certificate and access permissions of the pluggable device.
[0083] Furthermore, the control device also includes:
[0084] The third generation module is used to generate a device certificate corresponding to the pluggable device based on the device identity information after the device registration of the pluggable device is approved. The device certificate is used to verify the legality of the certificate.
[0085] Fifthly, the present invention provides an in-vehicle electronic device, comprising: a memory and a processor;
[0086] The memory stores the instructions that the computer executes;
[0087] The processor executes computer execution instructions stored in memory, causing the processor to perform the first aspect and / or various possible implementations of the first aspect as described above, and / or to perform the second aspect and / or various possible implementations of the second aspect as described above.
[0088] In a sixth aspect, the present invention provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the first aspect and / or various possible embodiments thereof, and / or to implement the second aspect and / or various possible embodiments thereof.
[0089] In a seventh aspect, the present invention provides a computer program product comprising a computer program that, when executed by a processor, implements the first aspect and / or various possible implementations of the first aspect, and / or implements the second aspect and / or various possible implementations of the second aspect.
[0090] The beneficial effects of this invention are:
[0091] This invention, upon detecting the insertion of a device to be authenticated by the vehicle terminal, acquires the device identity information of the device to be authenticated and initiates device authentication to the cloud based on the device identity information. After successful authentication, the device is recorded as an authenticated device, and the corresponding object model is retrieved from the cloud. Then, control commands for the authenticated device are generated and issued based on the object model. In this way, device authentication, capability acquisition, and control generation are processed together, providing an object model for pluggable automotive devices from different manufacturers and with different protocols in a unified manner to adapt the command communication method between the vehicle terminal and the pluggable devices. This reduces the need for the vehicle terminal to adapt separately for each pluggable device and repeatedly modify the parsing logic as the protocol changes, thereby reducing adaptation and expansion costs and improving the system's compatibility and flexibility. Attached Figure Description
[0092] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0093] Figure 1 Flowchart of the control method for the vehicle-mounted pluggable device provided by the present invention Figure 1 ;
[0094] Figure 2 Flowchart of the control method for the vehicle-mounted pluggable device provided by the present invention Figure 2 ;
[0095] Figure 3 Flowchart of the control method for the vehicle-mounted pluggable device provided by the present invention Figure 3 ;
[0096] Figure 4 A schematic structural block of the control device for the vehicle-mounted pluggable device provided by the present invention. Figure 1 ;
[0097] Figure 5A schematic structural block of the control device for the vehicle-mounted pluggable device provided by the present invention. Figure 2 ;
[0098] Figure 6 A schematic structural block of the control device for the vehicle-mounted pluggable device provided by the present invention. Figure 3 ;
[0099] Figure 7 A schematic structural block of the control device for the vehicle-mounted pluggable device provided by the present invention. Figure 4 ;
[0100] Figure 8 This is a schematic block diagram of the structure of the vehicle-mounted electronic device provided by the present invention.
[0101] The accompanying drawings have illustrated specific embodiments of the invention, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the invention in any way, but rather to illustrate the concept of the invention to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0102] 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.
[0103] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.
[0104] Access control for pluggable external devices in vehicles involves the fields of smart cockpits, vehicle-to-everything (V2X) communication, and device management. Vehicle terminals are typically deployed in the vehicle's infotainment system and work in conjunction with cloud services and pluggable external devices. These devices can connect to the vehicle via Universal Serial Bus (USB) interfaces, Bluetooth, Wireless Fidelity (WiFi) networks, Controller Area Network (CAN) interfaces, and other methods to enable functional expansion, status acquisition, and interactive control.
[0105] In practical applications, vehicle terminals need to sense the device insertion status, identify the identity of the accessed device, and organize subsequent communication based on the device's capabilities. In this process, the cloud side typically handles device information management, authentication processing, and data distribution, while the vehicle side handles interface detection, device control, and interaction execution. Together, they constitute the access environment for pluggable in-vehicle devices.
[0106] Current methods for connecting external pluggable devices to vehicles are mostly based on interface identification, adapter conversion, or vehicle binding. After the device is plugged in, the vehicle's infotainment system identifies the interface information or device identifier, and then communicates with the device according to a preset parsing logic. Some solutions can upload device information to the cloud to complete registration or binding. The process typically revolves around establishing a physical connection, verifying identity, and receiving and sending control messages.
[0107] When multiple vendors' devices are connected in a mixed manner, the above methods can easily expose insufficient upper-layer compatibility issues because different vendors and devices use different device protocols. The description methods for the capabilities of different devices are inconsistent, and the formats of control commands and status data vary significantly. Vehicle terminals often need to write separate parsing and control logic for different devices. Furthermore, when device protocol versions change or new functions are added, the original logic on the vehicle terminal side is difficult to reuse directly, resulting in repeated adaptation work.
[0108] These defects will continuously increase the cost of device access and maintenance, and also weaken the dynamic expansion capability of vehicle terminals. In addition, as the number of devices increases, vehicle terminal management is prone to being decentralized, and the control link lacks a unified entry point. Therefore, how to provide a unified physical model for in-vehicle pluggable devices to enable command interoperability between vehicle terminals and pluggable devices is an urgent problem to be solved.
[0109] Based on the aforementioned technical issues, in this embodiment, upon detecting a device insertion, the vehicle terminal first obtains the device's identity information and delegates the authentication process to the cloud for collaborative handling, establishing a unified and trusted entry point before device access. After successful authentication, the vehicle terminal retrieves the corresponding object model for the device, enabling the object model to contain the device's capability description. Finally, the vehicle terminal organizes control commands based on the retrieved object model, helping to reduce direct coupling to device-specific differences. With the vehicle, cloud, and pluggable device forming a linkage, device access, authentication, capability acquisition, and control delivery can be completed within the same link, improving communication compatibility. By providing a unified object model for pluggable vehicle devices to facilitate command interoperability between the vehicle terminal and the pluggable device, the problem of the vehicle terminal repeatedly modifying its parsing logic as devices change is alleviated, and the access and expansion of external pluggable devices are easier to manage uniformly.
[0110] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.
[0111] Figure 1 Flowchart of the control method for the vehicle-mounted pluggable device provided by the present invention Figure 1 ,like Figure 1 As shown, this control method is applicable to vehicle terminals, which are installed on vehicles. The control method includes:
[0112] S101: When device insertion information is detected, obtain the device identity information of the device to be authenticated.
[0113] For example, the vehicle terminal is installed on the vehicle and is the subject of execution in step S101. The vehicle-mounted pluggable device refers to a device that connects to the vehicle via a physical interface or access link and performs subsequent authentication, control, and data interaction with the vehicle terminal. When the vehicle-mounted pluggable device is inserted into the vehicle, it becomes the device to be authenticated. The device insertion information is generated when the device to be authenticated is inserted into the vehicle; essentially, it is the detection result of the vehicle terminal on interface status changes or link establishment events. The device identity information is relevant data used to characterize the identity of the device to be authenticated.
[0114] In one example, after detecting the device insertion information, the vehicle terminal obtains the device identity information of the device to be authenticated and forms a corresponding identity data object locally for use in the subsequent authentication process.
[0115] Subsequently, the vehicle terminal performs an integrity check on the acquired device identity information during the data collection process. If the identity data is found to be missing, the reading process can be re-initiated. If the repeated reading still fails, the device's authentication status will be retained as pending authentication, and the device will not enter the subsequent device authentication request sending process.
[0116] Based on the above analysis, by completing device insertion detection and identity information collection at the same access point, the vehicle terminal can form unified identity data when the device is connected, and devices with different access methods can enter the same authentication entry point, thus being uniformly abstracted as devices to be authenticated in the upper-level management.
[0117] S102: Generate and send a device authentication request to the cloud based on the device identity information.
[0118] For example, a device authentication request is a request message constructed by the vehicle terminal based on the acquired device identity information and sent to the cloud, used to request the cloud to determine whether the device to be authenticated has legitimate access. The cloud is a remote system that works in conjunction with the vehicle terminal, and it is responsible for processing such as device registration verification, certificate validity verification, access permission determination, and authentication result return.
[0119] In one example, the vehicle terminal reads the device identity data object corresponding to the device identity information obtained in step S101 from the local cache and assembles it into a device authentication request. Subsequently, the vehicle terminal sends the device authentication request to the cloud via the vehicle-cloud communication channel. If no response is received from the cloud within a preset time period, the vehicle terminal can resend the request or continue waiting, depending on the actual situation. If the cloud returns a confirmation of receipt or a subsequent authentication result, the vehicle terminal updates the authentication status of the device to be authenticated to the corresponding status.
[0120] Based on the above analysis, it can be seen that the vehicle terminal generates and sends a device authentication request, enabling the device identity information of the device to be authenticated to be uploaded to the cloud. The cloud then uses unified rules to complete the legitimacy judgment. Therefore, the vehicle terminal no longer needs to implement local authentication strategies for each type of pluggable in-vehicle device; instead, the authentication standard is centralized in the cloud. In this way, when the device manufacturer, protocol version, or capability range changes, the vehicle terminal only needs to maintain a unified request authentication organization logic to collaboratively complete the authentication process with the cloud.
[0121] S103: When the first cloud response information of the received device authentication request is an authentication pass response, mark the device to be authenticated as an authenticated device, generate and send the object model retrieval request corresponding to the authenticated device to the cloud.
[0122] For example, the first cloud response information is the first type of response information returned by the cloud to the device authentication request, used to indicate whether the device has been successfully authenticated; the authentication success response information is the response content that represents successful authentication; the authenticated device is the device object marked by the vehicle terminal after being authenticated by the cloud; the object model retrieval request is a request sent by the vehicle terminal to the cloud for the authenticated device to obtain the device object model, wherein the object model is a digital abstract description of the device's capabilities, and the cloud uses a unified standard to define "what the device is, what it can do, and what information it can provide to the outside world". This step S103 is located at the intermediate hub position of the device access link, which connects the identity trust judgment with the subsequent capability description acquisition.
[0123] In one example, the vehicle terminal listens for authentication response channels from the cloud and matches the first cloud response with the previously sent device authentication request. When the first cloud response indicates successful authentication, the vehicle terminal switches the status field of the corresponding device to be authenticated to "authenticated" and writes an authentication success flag into the local device management table, thus designating it as an authenticated device. For the same device's control flow, only authenticated devices are subsequently allowed to enter the object model retrieval and control delivery stages locally.
[0124] After the state change is completed, the vehicle terminal generates a request to retrieve the object model corresponding to the authenticated device and sends the request to the cloud. After the vehicle terminal sends the request, it establishes the model retrieval task for the device locally and enters a state of waiting for the response information from the second cloud.
[0125] Based on the above analysis, it can be seen that by first clearly marking the devices that have passed cloud authentication as certified devices, and then initiating the object model retrieval request, the object model acquisition process is based on the confirmed and trusted device identity. Furthermore, since the object model retrieval request targets certified devices, the cloud can send the corresponding model according to the device situation, and the vehicle does not need to pre-configure the fixed capability parsing logic for each manufacturer's device.
[0126] S104: Obtain the object model based on the second cloud response information corresponding to the received object model retrieval request.
[0127] For example, the second cloud response information is a second type of response information returned by the cloud to the object model retrieval request, used to provide the vehicle terminal with object model content or retrieval results related to the object model. An object model is a standardized description of a device's capabilities. Retrieving an object model includes not only receiving model data but also processes such as model verification, parsing, caching, and binding to an authenticated device instance.
[0128] In one example, after receiving the second cloud response, the vehicle terminal first performs response matching. The second cloud response can directly carry the object model content, or it can carry the object model's location and related verification information; in the latter case, the vehicle terminal further obtains the model file and verifies the obtained result. After parsing the object model, the vehicle terminal writes it to its local cache or lightweight database and establishes a binding index with the device identifier of the authenticated device.
[0129] The vehicle terminal associates the parsed object model with the corresponding certified device. If the corresponding object model already exists locally, the vehicle terminal can directly reuse the cached model upon confirmation of its availability; if an update is required, the local model is updated with the model returned from the cloud, and the binding relationship is also updated. To ensure the stability of subsequent control, the vehicle terminal can perform corresponding checks before the object model is added to the database; if the check fails, the device status can be set to certified but the model unavailable, and model exception information can be sent back to the cloud.
[0130] Subsequently, the vehicle terminal can perform unified processing based on the object model, instead of directly writing control logic for manufacturer-private fields.
[0131] Based on the above analysis, it can be seen that the object model carried by the second cloud response information extracts the device capability description from the device's proprietary protocol, enabling the vehicle terminal to establish the capability description basis for subsequent control of the pluggable in-vehicle devices by parsing the object model. Thus, when pluggable in-vehicle devices from different manufacturers are connected, as long as the cloud can return the corresponding object model, the vehicle side can use the same object model parsing protocol framework to complete the capability access, helping to solve the problem of repeated adaptation caused by differences in device protocols.
[0132] S105: Based on the object model, generate and issue control commands for certified devices.
[0133] For example, the control command is a command generated by the vehicle terminal based on the object model and sent to the certified device to control the device's operation. Step S105, based on the acquired and parsed object model, converts the control intent generated by the vehicle terminal into control commands that the device can recognize and execute. The control intent can originate from user input on the cockpit interface, from automatic control logic triggered by changes in vehicle state, or from preset scenario strategies. The core of generating control commands lies in using the object model to convert standardized capability items into device control content.
[0134] In one example, the vehicle terminal first determines the target authenticated device and the type of operation to be performed, such as the user selecting a device's on / off control, mode switching, or parameter setting on the interface. Based on this operation type, the device control module retrieves the corresponding control content from the object model bound to the authenticated device and generates the corresponding control command based on the object model.
[0135] During the instruction generation phase, the vehicle terminal generates control instructions executable by the device based on the object model and sends these instructions to the certified device. For devices requiring feedback, the vehicle terminal receives the execution result returned by the device after issuing the control instruction and performs corresponding processing accordingly.
[0136] Based on the above analysis, it can be seen that the vehicle terminal does not directly rely on the proprietary device protocol logic of the equipment manufacturer to generate control messages. Instead, it first locates the corresponding capability items of the pluggable on-board devices based on the object model, and then completes the generation and issuance of control commands. Therefore, the expansion of device capabilities is mainly achieved through cloud-based updates to the object model. In this way, when new devices are added or device protocol versions change, the vehicle-side control link can still maintain a unified generation and issuance process, and the control entry point for the vehicle terminal to devices from multiple manufacturers can be centralized within the same model-driven framework.
[0137] In summary, this embodiment provides a control method for vehicle-mounted pluggable devices, applicable to vehicle terminals. The method includes: acquiring the device identity information of the device to be authenticated upon detecting device insertion; generating and sending a device authentication request to the cloud based on the device identity information; marking the device to be authenticated as an authenticated device and generating and sending a request to retrieve the corresponding object model to the cloud when the first cloud response information of the received device authentication request is an authentication pass response; acquiring the object model based on the second cloud response information corresponding to the received object model retrieval request; and generating and issuing control commands for the authenticated device based on the object model. In this way, the vehicle terminal organizes the access, authentication, capability acquisition, and control execution of vehicle-mounted pluggable devices into a unified processing link. A unified trusted entry point is first established through cloud authentication, and subsequent control adaptation is completed through the object model. Therefore, external pluggable devices from different manufacturers and with different protocol versions can use the same upper-layer processing flow after being connected to the vehicle. The vehicle terminal does not need to separately solidify and resolve control logic for each vehicle-mounted pluggable device. Furthermore, changes in device capabilities are mainly reflected in the vehicle terminal through the object model returned from the cloud, eliminating the need for repeated parsing and adaptation by the vehicle terminal.
[0138] In one possible implementation, after generating a device authentication request based on the device identity information, the control method further includes: performing a signature anti-tampering operation on the device authentication request using a message authentication code algorithm based on the vehicle security token, timestamp, and random number, wherein the device authentication request after the signature anti-tampering operation is used to send to the cloud.
[0139] For example, after generating a device authentication request, the vehicle terminal organizes the device identity information, timestamp, and random number into data to be signed according to a preset field order. Then, it combines this data with a vehicle security token input message authentication code algorithm (such as a hash algorithm) to generate an authentication code that corresponds one-to-one with the device authentication request content. This authentication code is then appended to the device authentication request to form a tamper-proof signed authentication message. The vehicle security token can use a symmetric key or a key material pre-negotiated with the cloud. Its length can be configured to 128 bits, 192 bits, or 256 bits to adapt to different security levels in vehicle environments. In practical applications, other models of this component can also be selected; this embodiment does not limit this.
[0140] In one example, the device authentication request is signed before being sent to the cloud. The cloud determines the timeliness of the request based on the received timestamp and recalculates and compares the authentication code against the same vehicle security token or corresponding verification materials to confirm whether the device authentication request has been tampered with during transmission and whether the source is trustworthy. Furthermore, because a random number is involved in the signature calculation, and each device authentication request contains a different dynamic value, the authentication message corresponding to the same device identity information is also unique. The cloud can use this to identify duplicate messages and prevent replay.
[0141] By introducing a vehicle-mounted security token, timestamp, and random number before sending the device authentication request and performing message authentication code calculation, the integrity, authenticity, and timeliness of the device authentication request are constrained. After receiving the request, the cloud can directly complete the verification and enter the authentication process, thereby ensuring a consistent security verification mechanism between the vehicle and the cloud for device access links.
[0142] In one possible implementation, the object model includes at least model components and mapping relationships, wherein the model components include at least attributes, events, and services, and the mapping relationships are used to assign labels to attributes, events, and services.
[0143] For example, the object model can be pre-generated in the cloud and distributed to the vehicle terminal. The model components are organized according to the device type, and the same device can contain multiple attributes, multiple events, and multiple services. When constructing the object model, the cloud configures a unique label for each attribute, event, and service. The label can be in the form of string identification, numerical encoding, or hierarchical encoding.
[0144] In one example, after receiving the object model, the vehicle terminal associates the tags with local protocol parsing rules. This allows it to locate the corresponding device capabilities based on the tags when generating control commands, and to reconstruct attribute values, event content, or service responses from the object model based on the tags when receiving uplink data from the device. For devices from different manufacturers or with different versions, the cloud only needs to adjust the mapping relationship between tags and capabilities, without changing the overall control framework of the vehicle terminal.
[0145] In another example, after acquiring the object model, the vehicle terminal first identifies the device capability boundaries based on the model components, and then encodes the business instructions into control data corresponding to the tags through mapping relationships, or decodes the device feedback data into object model semantics, thereby achieving unified management of capability description and protocol interaction. Since attributes, events, and services are all associated through tags, the vehicle terminal can complete control issuance and status parsing without directly relying on the device's proprietary format.
[0146] By adopting the above approach, the object model can describe device capabilities with unified model components and labels. The label mapping relationship enables a stable correspondence between device capability items and protocol messages. When facing different devices, the vehicle terminal only needs to convert according to the object model, which reduces the coupling of private protocol parsing logic and improves the compatibility and expansion consistency after external pluggable devices are connected.
[0147] In one possible implementation, the tag is 2 bytes long.
[0148] For example, this fixed length can be directly read by the vehicle terminal according to the two-byte boundary when parsing the object model, and a mapping relationship can be established between the read binary value and the corresponding model component, so that different types of attributes, events and services within the same object model can be uniformly identified. Since the tag length is fixed, the vehicle terminal can quickly locate the corresponding model item based on the two-byte tag when generating control commands, parsing data sent from the cloud and performing device interactions, reducing length judgment and field negotiation during parsing.
[0149] In one possible implementation, control instructions for the certified device are generated and issued based on the object model. Specifically, this includes: converting the device operation instruction into a first TLV message based on the object model, wherein the device operation instruction is an instruction generated in the vehicle's infotainment system for controlling the operation of the certified device; converting the first TLV message into first binary data and recording the converted first binary data as the control instruction; and sending the control instruction to the certified device.
[0150] For example, the TLV (Type-Length-Value) message in this embodiment is a triplet message format, where the T field indicates the message type, the L field indicates the message length, and the V field stores the message content. The lengths of the T and L fields are often fixed, while the length of the V field is variable.
[0151] In one example, the vehicle terminal can first generate control instructions in a standard format (such as JSON format), then read the tags and encoding rules corresponding to the target control object from the object model, and match the control semantics in the device operation instructions with the tags one by one, thereby generating a first TLV message containing tags, length and value. The TLV message can be a hexadecimal private message.
[0152] Subsequently, the vehicle terminal serializes the first TLV message into transmittable first binary data according to the preset byte order and frame format parsing rules, and directly caches this first binary data as a control command in the transmission queue. The vehicle terminal then sends the control command cached in the transmission queue to the authenticated device through the communication link established with the authenticated device, so that the device can complete the message decoding and execute the corresponding control action.
[0153] The tag length, field encoding method, and message serialization rules adopted can be adapted according to the device protocol version. In practical applications, other models of this component can also be selected, but this embodiment does not limit this.
[0154] This approach uses the object model as a unified carrier of control semantics, enabling the device operation commands generated on the vehicle terminal side to be converted into standardized binary control data via the TLV message structure and then sent to the certified device. This ensures that the vehicle-side control messages are consistent with the device capability descriptions, reduces the vehicle terminal side's dependence on device-specific protocols, and reduces the differences in control message organization between devices from different manufacturers.
[0155] In one possible implementation, the control method further includes: converting the received second binary data into a second TLV message; and converting the second TLV message into device uplink data according to the object model, wherein the device uplink data is used to characterize the operating status of the certified device.
[0156] For example, after receiving the second binary data sent by the authenticated device, the vehicle terminal can first perform frame header verification, length verification, and other related verifications to confirm the data's integrity and validity. Subsequently, the vehicle terminal reads the tag field, length field, and value field from the binary data according to preset parsing rules and organizes them into a second TLV message; when the second binary data contains multiple service fields, each field corresponds to a multiple TLV unit, so that subsequent mapping can be performed independently by field.
[0157] The vehicle terminal then calls the object model corresponding to the device. Based on the label and attribute relationship defined in the object model, it converts the labels and values in the second TLV message into device uplink data in a standard format (such as JSON format). For example, it maps the value corresponding to the temperature label to the temperature status required for the in-vehicle display, and maps the value corresponding to the fault label to the fault alarm status. The conversion result is then stored in the device status cache or reported to the vehicle application layer.
[0158] In the above process, the object model is used as a unified parsing benchmark, enabling the second TLV message to be decoded without relying on device-specific formats. The device uplink data serves as a unified data carrier format for display, recording, or linkage control by the vehicle terminal. By first converting the raw binary data into the second TLV message, and then further generating device uplink data based on the object model, the operational information of certified devices from different manufacturers can be identified and utilized according to consistent data semantics, thereby achieving unified management and presentation of device status.
[0159] In one possible implementation, the device identity information includes at least one of the following: device type, device unique identifier, device SN (Serial Number), device certificate, device private key signature, and device public key certificate.
[0160] For example, after detecting the insertion of a device, the vehicle terminal can read one or more of the above-mentioned identity information from the external pluggable device, interface controller, or device configuration storage area, and organize them into the identity field in the authentication message. Among them, the device type and device unique identifier are used to establish an association with the device file on the cloud side, the device serial number (SerialNumber, abbreviated as SN) is used to compare with the registration record, and the device certificate, device private key signature, and device public key certificate are used to complete the certificate chain verification and signature verification.
[0161] By adopting the above method, the vehicle terminal can obtain complete identity elements that can be used for authentication and association during the access phase. The cloud can complete the legality judgment, device binding and subsequent object model distribution based on the same identity information. The uniformity and verifiability of the device access link are improved, and the vehicle terminal's adaptation and coupling to different devices are reduced accordingly.
[0162] Figure 2 Flowchart of the control method for the vehicle-mounted pluggable device provided in this embodiment Figure 2 ,like Figure 2 As shown, in this embodiment... Figure 1 Based on the embodiments, a control method for vehicle-mounted pluggable devices is described in detail, and the control method further includes:
[0163] S201: When device insertion information is detected, obtain the device identity information of the device to be authenticated; wherein, the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle;
[0164] S202: Generate and send a device authentication request to the cloud based on the device identity information;
[0165] S203: When the first cloud response information of the received device authentication request is an authentication pass response information, mark the device to be authenticated as an authenticated device, generate and send the object model retrieval request corresponding to the authenticated device to the cloud;
[0166] S204: Obtain the object model based on the second cloud response information corresponding to the received object model retrieval request;
[0167] S205: Based on the object model, generate and issue control commands for certified devices.
[0168] S206: When device disconnection information is detected, a device unbinding request is generated and sent to the cloud based on the device identity information of the authenticated device. The device disconnection information is the information generated when the authenticated device is disconnected from the vehicle.
[0169] S207: Based on the third-party cloud response information received regarding the device unbinding request, clear the device cache information of the object model and the certified device.
[0170] For example, the object model is device capability description data sent from the cloud to the vehicle, used to carry the attributes, events, services, and corresponding mapping relationships of the authenticated devices. After the pluggable device in the vehicle is unplugged or disconnected, the vehicle terminal generates a device unbinding request based on the device's device identity information and sends the unbinding request to the cloud. Upon receiving the unbinding request, the cloud releases the binding relationship between the vehicle and the device, revokes the vehicle's relevant permissions during the device's operation, and generates a third-party cloud response information so that the vehicle can perform subsequent unbinding operations.
[0171] After receiving the response information from the third-party cloud, the vehicle terminal deletes the object model data associated with the device and clears the device cache information of the authenticated device. The device cache information may include object model parsing results, protocol mapping tables, command templates, status echo cache, and device control context. After unbinding, the storage device or memory storing the above data can be released and overwritten to prevent subsequent control processes from continuing to reference the expired device data.
[0172] Through the above process, when the pluggable device in the vehicle is unplugged, a device unbinding request is generated and the local object model and device cache information are cleared according to the third cloud response information sent by the cloud. This allows the vehicle to terminate the binding relationship of the authenticated device in a timely manner and release the occupied resources. When the device is plugged in again, it can go through the authentication and capability acquisition process again, thereby maintaining the consistency of the device status and reducing the interference of invalid configurations on the vehicle control link.
[0173] Figure 3 Flowchart of the control method for the vehicle-mounted pluggable device provided in this embodiment Figure 3 ,like Figure 3 As shown, this control method is applicable to the cloud and includes the following control methods:
[0174] S301: Receive device authentication requests sent by any vehicle terminal.
[0175] For example, the vehicle terminal is a vehicle-side processing entity deployed in the vehicle infotainment system. It forms a local connection with the pluggable device and maintains network communication with the cloud. The device authentication request is an authentication message sent by the vehicle terminal to the cloud after detecting the access of the pluggable in-vehicle device, used to trigger device access processing on the cloud side. The pluggable in-vehicle device is an external pluggable device that connects to the vehicle terminal via a USB interface, WiFi link, Bluetooth link, CAN interface, or other pluggable access methods. In this embodiment, this device enters the subsequent authentication and object model distribution process as an object to be authenticated.
[0176] In one example, the cloud can receive connections from multiple vehicle terminals and process the device authentication request uploaded by the vehicle terminal. The device authentication request carries at least the vehicle terminal identifier, device access channel type, device original identification data, request signature information, and other relevant information. The device original identification data may include one or more of the following: device serial number, device hardware ID, manufacturer identifier, product model, device certificate digest, and public key fingerprint.
[0177] The vehicle terminal can encapsulate a device authentication request after detecting an external pluggable device insertion event, a link online event, or a bus enumeration completion event. For example, in a USB access scenario, the vehicle terminal reads the vendor ID and product ID from the device descriptor and combines them with the device serial number to form the request payload; in a Bluetooth access scenario, the vehicle terminal reads the Bluetooth address, pairing information, and device broadcast capability field to form the request payload.
[0178] During the receiving phase, the cloud can also perform basic verification of message integrity, including message length verification, protocol version verification, required field verification, and signature field existence verification, in order to facilitate subsequent authentication processing.
[0179] Based on the above processing method, the cloud first establishes a unified access point and then undertakes subsequent identity resolution and authentication, which helps to unify device requests from different interfaces into the same processing channel.
[0180] S302: Extract device identity information from the device authentication request.
[0181] For example, device identity information is a set of data that can characterize the identity of a pluggable device and is the direct input for cloud-based device authentication. After receiving a device authentication request, the cloud performs protocol parsing on the message body, extracts the device identity information according to predefined field relationships, and converts it into a unified internal data structure. For example, the cloud can first parse the vehicle terminal identifier, timestamp, and signature algorithm identifier in the request header, and then parse the original device identifier data, device access method, device certificate content or certificate index, firmware version, protocol version, and device capability summary collected by the vehicle terminal in the request body.
[0182] To ensure consistency in subsequent authentication, the extracted device identity information can be organized into a structured object, which includes at least an identity primary key field, a certificate field, a device access channel field, a vehicle terminal field, and a protocol field. The identity primary key field is used to uniquely identify the device to be authenticated, the certificate field is used to implement certificate validity authentication, the device access channel field is used to match permission policies, the vehicle terminal field is used to represent the correspondence between the device and the vehicle terminal, and the protocol field is used to match the object model version in the future.
[0183] If some fields are missing, the cloud can complete them based on existing records. For example, when a request does not carry a manufacturer identifier but carries a valid manufacturer ID, the cloud can query the corresponding manufacturer information and populate it into the structured object. After extraction, the cloud generates a standardized device identity information instance as input for the next step of device authentication.
[0184] Based on the above analysis, it can be seen that by uniformly parsing and processing the request content from different vehicle terminals and different access media, the cloud can identify different pluggable devices with a consistent data structure, and the subsequent authentication logic does not need to rely on the proprietary message formats of each manufacturer.
[0185] S303: Based on the device identity information, device authentication shall be performed, which shall include at least one of the following: device registration status authentication, certificate validity authentication, and access permission authentication.
[0186] For example, device authentication is used to determine whether the pluggable vehicle device corresponding to the device identity information meets the conditions for accessing the cloud collaborative control link. Device registration status authentication is used to determine whether the device has established a registration record in the cloud device management database. Certificate validity authentication is used to determine whether the certificate submitted by the device is authentic, valid and has not been revoked. Access permission authentication is used to determine whether the device has the permission to access and retrieve object models in the current vehicle terminal, current vehicle account or current business scenario.
[0187] In one example, the cloud first performs device registration status authentication based on the standardized device identity information obtained from S302. When a valid registration record is found, the device registration status authentication is considered successful. If no record is found, or the record status is cancelled, frozen, or expired, the authentication process outputs a failure result. After successful device registration status authentication, the cloud reads the certificate fields and performs link verification, signature verification, validity period verification, and revocation status verification on the device certificate. Link verification verifies whether the certificate chain from the device certificate to the trusted root certificate is complete; signature verification verifies that the certificate content has not been tampered with; validity period verification compares whether the current server time falls within the certificate's effective and expiration time range; and revocation status verification confirms that the certificate has not been revoked.
[0188] When the request does not directly carry the certificate text but carries the certificate index, the cloud can extract the corresponding certificate based on the index and perform verification.
[0189] After the certificate validity is verified, the cloud further matches the vehicle terminal identifier, device identity key, device access channel type and business domain to determine whether the current device is authorized to access the corresponding vehicle terminal, whether it has the permission to pull the object model and the permission to use the subsequent control link.
[0190] In another example, cloud-based device authentication is configured so that all three authentication criteria—device registration status authentication, certificate validity authentication, and access permission authentication—pass, so that the cloud can use the overall authentication result for subsequent processing.
[0191] The above process directly defines the trust judgment rules in the access link. The cloud verifies the device identity through three dimensions: filing, certificate and permission. It can complete the unified access judgment in the early stage of device access, so that devices from different manufacturers can enter the management process on the basis of the same authentication result.
[0192] S304: When the device authentication is successful, a globally unique device identifier and the corresponding first cloud response information are generated; wherein, the globally unique device identifier is used to represent the correspondence between the pluggable device corresponding to the device identity information and the vehicle terminal.
[0193] For example, after obtaining the authentication result in the cloud, a globally unique device identifier is generated based on the device identity information and vehicle terminal information. The globally unique device identifier is a unique identifier uniformly assigned by the cloud. It is not directly equivalent to the original serial number of the device, but is used to uniquely represent the correspondence between a pluggable device and a vehicle terminal. Therefore, different globally unique device identifiers can be generated when the same physical device is connected to different vehicle terminals.
[0194] To enable the vehicle terminal to continue the subsequent object model retrieval process, the cloud also generates a first cloud response message. This first cloud response message is used to provide the corresponding vehicle terminal with the authentication success result and the generated globally unique device identifier. Its data content includes at least the authentication result code, the globally unique device identifier, and the response timestamp; the first cloud response message may also include validity period information and related fields required for subsequent object model retrieval.
[0195] Based on the above analysis, it can be seen that after authentication is successful, the cloud not only returns the authentication result, but also returns a globally unique device identifier to the vehicle terminal to represent the correspondence between the pluggable device and the vehicle terminal, so that the vehicle terminal can initiate a request to retrieve the subsequent object model.
[0196] S305: Send the first cloud response information to the corresponding vehicle terminal.
[0197] For example, the corresponding vehicle terminal is the vehicle entity that initiates the current device authentication request and participates in the device access process. After generating the first cloud response information, the cloud sends the response back to the vehicle terminal through a communication link consistent with the access session in S301, or locates the corresponding connection through the online connection table of vehicle terminals maintained by the cloud and actively pushes the response.
[0198] In one example, before sending the first cloud response, the cloud can perform signature processing or message authentication code calculation on the response body and add the protocol version, message length, compression flag, and tracking number to the response header. Upon receiving the response, the vehicle terminal can verify the signature, read the authentication result code and the globally unique device identifier, and establish a local device session record, associating and saving the unique identifier with the current physical access device instance. If the cloud does not receive a confirmation from the vehicle terminal within the predetermined retry time, it can resend the first cloud response according to the session reliability policy.
[0199] In another example, in addition to the globally unique device identifier, the first cloud response information may also carry a request entry identifier for pulling the object model, which the vehicle terminal uses to determine the subsequent pull interface address or message topic.
[0200] Through the above process, the vehicle terminal can obtain the authentication result and the unified device identifier assigned by the cloud. The device access process naturally transitions from the identity verification stage to the capability description acquisition stage, and the entire link maintains consistent data association under the control of the cloud.
[0201] S306: Generate a second cloud response based on the received object model retrieval request.
[0202] For example, the object model retrieval request is a request initiated by the vehicle terminal to the cloud to obtain the object model after receiving the first cloud response information and confirming the correspondence. The object model is used to represent the capability information of pluggable devices, and its content may include device attribute definitions, event definitions, service definitions, parameter types, units, value ranges, read and write permissions, command encoding mapping, and version information, etc. The vehicle terminal organizes subsequent control instructions and status parsing logic according to the object model.
[0203] In one example, the vehicle terminal includes at least a globally unique device identifier, a vehicle terminal identifier, a request version number, and a locally cached model version number in its object model retrieval request. Upon receiving the object model retrieval request, the cloud first verifies that the request corresponds to an authenticated device using the globally unique device identifier. Then, based on the device identity information, product field, protocol field, and policy version, it retrieves the target object model matching the current device from the object model repository.
[0204] The object model repository can be indexed and stored at multiple levels according to manufacturer, product model, protocol version, and capability version. After retrieving a matching model, the cloud organizes the model content into a second cloud response message. The second cloud response message carries the processing results related to this pull request, and its content may include the model retrieval result code, model version number, model summary value, complete model data or model download address, shard number, total number of shards, and signature field, etc.
[0205] When the object model data volume is large, the cloud can split the model into multiple fragments and write fragment control information into the second cloud response information, which can then be reassembled piece by piece by the vehicle terminal. If the current device is associated with multiple functional domain models, the cloud can also generate multiple corresponding second cloud response information based on the functional domain parameters in the request, or return an aggregated model directory in a single response.
[0206] After generating the second cloud response information, the cloud associates and saves the response with the current processing status, and records the model version and issuance time to support subsequent traceability.
[0207] Through step S306, the cloud abstracts the device's capability description from the manufacturer's proprietary protocol side to the unified object model side. The vehicle terminal only needs to adapt according to the object model content issued by the cloud, without needing to pre-fix the dedicated parsing logic for each type of device.
[0208] S307: Based on the second cloud response information, send the object model corresponding to the object model retrieval request to the corresponding vehicle terminal.
[0209] For example, based on the second cloud response information generated by S306, the cloud sends the object model content to the corresponding vehicle terminal that initiated the object model pull request. The corresponding vehicle terminal is still a vehicle terminal that corresponds to the globally unique device identifier. The cloud can verify the consistency of the request source again before sending to confirm that the device and vehicle terminal information corresponding to the current request are consistent.
[0210] In one example, when the second cloud response information directly carries the complete object model, the cloud sends the complete object model message to the vehicle terminal through the original request connection or downlink message channel; when the second cloud response information carries the model download address or fragment index, the cloud continues to push the content of each fragment according to the distribution scheme recorded in the response, or allows the vehicle terminal to initiate a controlled download based on the address, and verifies the download result through the digest value and signature field.
[0211] After receiving the object model, the vehicle terminal saves the globally unique device identifier and the model version together, and generates a control adaptation instance for the device locally. When it is necessary to send control commands to the pluggable device in the vehicle, the vehicle terminal can generate device-side messages based on the service items and parameter mappings defined in the object model. When it receives device status data, the vehicle terminal can also parse and standardize the data based on the attribute mappings in the object model.
[0212] If the cloud receives confirmation of model reception from the vehicle terminal after sending the object model, it updates the corresponding status; if no confirmation is received, it performs a resend based on the fragment sequence number or version information in the second cloud response information.
[0213] Based on the above analysis, this embodiment provides a control method for a vehicle-mounted pluggable device, including receiving a device authentication request sent by any vehicle terminal, extracting device identity information from the device authentication request, performing device authentication based on the device identity information, generating a globally unique device identifier and a first cloud response information corresponding to the globally unique device identifier when the device authentication is successful, sending the first cloud response information to the corresponding vehicle terminal, generating a second cloud response information based on the received object model retrieval request, and sending the object model corresponding to the object model retrieval request to the corresponding vehicle terminal based on the second cloud response information.
[0214] Through the methods described in this embodiment, the cloud establishes a unified authentication entry point for the access of pluggable in-vehicle devices. Based on device identity information, it implements device registration status authentication, certificate validity authentication, and access permission authentication. After successful authentication, a globally unique device identifier is generated to represent the correspondence between the device and the vehicle terminal. Then, a matching object model is distributed to the vehicle terminal according to this correspondence, so that subsequent control processes revolve around a unified capability description. In this way, the vehicle does not need to solidify parsing and control logic separately for devices from different manufacturers. When device protocol versions change, adaptation and updates are mainly completed through cloud-side model management.
[0215] In one possible implementation, the control method further includes: clearing the globally unique device identifier based on the received device unbinding request; generating and sending third-party cloud response information to the corresponding vehicle terminal.
[0216] For example, after receiving a device unbinding request from a vehicle terminal, the cloud first matches and verifies the identity information carried in the request, and locates the associated binding record based on the device identity information or globally unique device identifier corresponding to the unbinding request. Subsequently, the cloud performs invalidation processing on the globally unique device identifier. This invalidation processing can be removing the identifier from the binding relationship corresponding to the vehicle terminal, setting the identifier to an invalid state, or deleting the storage record associated with the identifier, so that the identifier no longer represents the correspondence between the pluggable device and the vehicle terminal. After this processing, even if the vehicle terminal subsequently receives access information from the same device again, it will not directly use the existing binding state based on the original identifier.
[0217] After the cleanup process is complete, the cloud generates a third-party cloud response and sends it to the corresponding vehicle terminal. This response may include a successful unbinding indicator, a globally unique device identifier that has been cleared, an unbinding timestamp, and prompts related to local permission revocation. Upon receiving the third-party cloud response, the vehicle terminal can update its local binding list, delete the cached device control context, and simultaneously revoke access permissions associated with the pluggable device. This process ensures that the unbinding result remains consistent between the cloud and the vehicle terminal.
[0218] The above method ensures that the globally unique device identifier is promptly cleared after unbinding, and the third-party cloud responds to the vehicle terminal with the result. This enables the vehicle terminal to accurately complete state synchronization and permission revocation, reduces identification confusion caused by residual binding relationships, and allows subsequent devices to re-authenticate and re-establish the chain when they reconnect.
[0219] In one possible implementation, the control method further includes: registering the device based on the device identity information of any pluggable device received, and determining the legality of the certificate and access permissions corresponding to the pluggable device.
[0220] For example, after receiving the device identity information, the cloud first queries the filing database for existing records that match the device identity information. When a matching record is found, the access time, device status, and certificate status in the record are updated. When no matching record is found, a new filing record is generated according to the device identity information, and the device identity information, certificate index, and permission index are written into it.
[0221] The cloud can also establish a mapping between device identity information, certificate information, and permission information. The legality of the certificate can be confirmed through certificate chain verification, issuing authority verification, validity period verification, or revocation status verification. Access permissions can be determined based on the permission fields, access control tables, or authorization policy tables preset in the filing record.
[0222] The aforementioned registration records can be stored in a cloud database. The database can adopt a relational storage structure or a key-value storage structure to facilitate quick retrieval based on device identity information. In practical applications, other methods can also be selected, and this embodiment does not limit this.
[0223] In one example, after the cloud completes device registration based on device identity information, it synchronously associates the device registration result with the certificate validity and access permission determination results under the same device identifier, and uses this information for subsequent device authentication and object model distribution. Therefore, when a vehicle terminal connects to a pluggable device, it can first obtain a unified device registration result from the cloud, and then complete access control based on certificate validity and access permissions. This forms a joint verification of device identity, certificate status, and authorization scope, ensuring consistency in device access judgment criteria, reducing processing differences caused by different devices establishing separate management logic, and improving the security and consistency of access control.
[0224] In one possible implementation, the control method further includes: after the device registration of the pluggable device is approved, generating a device certificate corresponding to the pluggable device based on the device identity information, wherein the device certificate is used for certificate legality authentication.
[0225] For example, after receiving the result of the device registration approval, the cloud first extracts the corresponding device identity information from the device registration record and uses the device identity information as the basis for certificate generation. Subsequently, the cloud can generate certificate content containing device identification field, certificate number, validity period field and signature verification field according to the preset certificate template, and encapsulate the certificate content with a signature to form a device certificate corresponding to the pluggable device.
[0226] The certificate number can be obtained from the device identity information through hashing or encoding mapping, establishing a one-to-one correspondence between the certificate and the device. The signature encapsulation can use a cloud-based private key to digitally sign the certificate body, facilitating subsequent verification in access control or access control systems. Regarding the storage method of the device certificate, the cloud can write the generated result into a certificate management table and save it in association with the device registration record. When the vehicle terminal subsequently requests access authentication, it can obtain the corresponding certificate based on the device identity information for performing a legitimacy comparison.
[0227] In this embodiment, by generating a device certificate associated with the device identity information after the device registration is approved, and using it for certificate legality authentication, a stable correspondence can be established between the device identity and subsequent authentication credentials. This allows the device registration result to be directly carried over to the access verification process, thereby enhancing the credibility and consistency of the pluggable device access process.
[0228] Figure 4 A schematic structural block diagram of the control device for the vehicle-mounted pluggable device provided in this embodiment. Figure 1,like Figure 4 As shown, the control device 40 for the vehicle-mounted pluggable device provided in this embodiment is suitable for a vehicle terminal, which is installed on a vehicle. The control device 40 includes:
[0229] The acquisition module 401 is used to acquire the device identity information of the device to be authenticated when device insertion information is detected; wherein, the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle;
[0230] Request module 402 is used to generate and send a device authentication request to the cloud based on the device identity information;
[0231] The request module 402 is also used to mark the device to be certified as a certified device when the first cloud response information of the received device authentication request is an authentication pass response information, and to generate and send the object model pull request corresponding to the certified device to the cloud.
[0232] The acquisition module 401 is also used to acquire the object model based on the second cloud response information corresponding to the received object model pull request;
[0233] The first generation module 403 is used to generate and issue control commands for certified devices based on the object model.
[0234] In this embodiment, after detecting a device insertion, the vehicle terminal first extracts the device identity information based on the device insertion information, and the request module 402 initiates an authentication request to the cloud, thereby establishing a unified trusted access point for the external pluggable device. After successful authentication, the device is marked as an authenticated device and the corresponding object model is retrieved from the cloud, abstracting the device capability description from a device-specific protocol to a unified object model. After the acquisition module 401 obtains the object model based on the second cloud response information, the first generation module 403 can generate and issue control commands based on the object model, thereby reducing the need for the vehicle terminal to develop control logic separately for devices from different manufacturers and with different protocols. In this way, device authentication, capability acquisition, and control generation are linked and processed in a unified manner to provide object models for pluggable vehicle devices from different manufacturers and with different protocols, enabling the adaptation of command communication methods between the vehicle terminal and pluggable devices. This reduces the need for the vehicle terminal to adapt separately for specific pluggable devices and repeatedly modify the parsing logic as the protocol changes, thereby reducing adaptation and expansion costs.
[0235] Figure 5 A schematic structural block diagram of the control device for the vehicle-mounted pluggable device provided in this embodiment. Figure 2 ,like Figure 5 As shown, in this embodiment... Figure 4 Based on the embodiments, the control device for the vehicle-mounted pluggable device will be described in detail. The control device 50 for the vehicle-mounted pluggable device includes:
[0236] The acquisition module 501 is used to acquire the device identity information of the device to be authenticated when device insertion information is detected; wherein, the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle;
[0237] Request module 502 is used to generate and send a device authentication request to the cloud based on the device identity information;
[0238] The request module 502 is also used to mark the device to be authenticated as an authenticated device when the first cloud response information of the received device authentication request is an authentication pass response information, and to generate and send the object model pull request corresponding to the authenticated device to the cloud.
[0239] The acquisition module 501 is also used to acquire the object model based on the second cloud response information corresponding to the received object model pull request;
[0240] The first generation module 503 is used to generate and issue control commands for certified devices based on the object model.
[0241] In one possible implementation, after generating a device authentication request based on the device identity information, the control device 50 further includes:
[0242] The signature module 504 is used to perform a signature anti-tampering operation on the device authentication request based on the vehicle security token, timestamp, and random number using a message authentication code algorithm. The device authentication request after the signature anti-tampering operation is used to send it to the cloud.
[0243] In one possible implementation, the object model includes at least model components and mapping relationships, wherein the model components include at least attributes, events, and services, and the mapping relationships are used to assign labels to attributes, events, and services.
[0244] In one possible implementation, the tag is 2 bytes long.
[0245] In one possible implementation, the first generation module 503 specifically includes:
[0246] The conversion submodule 5031 is used to convert the device operation instruction into a first TLV message according to the object model, wherein the device operation instruction is an instruction generated in the vehicle unit for controlling the operation of the certified device;
[0247] The conversion submodule 5031 is also used to convert the first TLV message into first binary data and record the converted first binary data as a control command;
[0248] The sending submodule 5032 is used to send control commands to the authenticated device.
[0249] In one possible implementation, the conversion submodule 5031 is also used for:
[0250] Convert the received second binary data into a second TLV message;
[0251] Based on the object model, the second TLV message is converted into device uplink data, where the device uplink data is used to characterize the operating status of the certified device.
[0252] In one possible implementation, the device identity information includes at least one of the following: device type, device unique identifier, device serial number (SN), device certificate, device private key signature, and device public key certificate.
[0253] In one possible implementation, the request module 502 is further configured to generate and send a device unbinding request to the cloud based on the device identity information of the authenticated device when the device unbinding information is detected. The device unbinding information is the information generated when the authenticated device is unbound from the vehicle.
[0254] The control device 50 also includes an unbinding module 505, which is used to clear the device cache information of the object model and the certified device based on the third cloud response information of the received device unbinding request.
[0255] The control device 50 for the vehicle-mounted pluggable device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0256] Figure 6 A schematic structural block diagram of the control device for the vehicle-mounted pluggable device provided in this embodiment. Figure 3 ,like Figure 6 As shown, the control device 60 for the vehicle-mounted pluggable device provided in this embodiment is suitable for cloud computing. The control device 60 includes:
[0257] The receiving module 601 is used to receive a device authentication request sent by any vehicle terminal.
[0258] Extraction module 602 is used to extract device identity information from device authentication requests;
[0259] The authentication module 603 is used to authenticate the device based on the device identity information. The device authentication includes at least one of the following: device registration status authentication, certificate validity authentication, and access permission authentication.
[0260] The second generation module 604 is used to generate a globally unique device identifier and the first cloud response information corresponding to the globally unique device identifier when the device authentication is successful; wherein, the globally unique device identifier is used to represent the correspondence between the pluggable device corresponding to the device identity information and the vehicle terminal.
[0261] The sending module 605 is used to send the first cloud response information to the corresponding vehicle terminal;
[0262] The second generation module 604 is also used to generate a second cloud response information based on the received object model retrieval request;
[0263] The sending module 605 is also used to send the object model corresponding to the object model pull request to the corresponding vehicle terminal based on the second cloud response information.
[0264] In this embodiment, after detecting the access of an external pluggable device, the vehicle terminal can encapsulate the device's identity information into a device authentication request and send it to the cloud. The cloud's receiving module 601 and extraction module 602 receive and parse the request. The authentication module 603 performs authentication based on at least one of the following: registration status, certificate validity, and access permissions. This establishes a unified and trusted access point, preventing unregistered, certificate-abnormal, or unauthorized devices from entering the vehicle's control link. After successful authentication, the second generation module 604 generates a globally unique device identifier and a first cloud response, enabling the cloud to stably associate the device with the corresponding vehicle terminal, facilitating subsequent management, tracking, and policy distribution. The vehicle terminal then initiates a property model retrieval request based on this association. The cloud generates a second cloud response and distributes the corresponding property model, allowing the vehicle to describe device capabilities and organize control and interaction based on a unified property model. This reduces the need for direct adaptation to differences in proprietary protocols from different manufacturers, thus improving compatibility, consistency, and scalability when multiple devices are accessed simultaneously.
[0265] Figure 7 A schematic structural block diagram of the control device for the vehicle-mounted pluggable device provided in this embodiment. Figure 4 ,like Figure 7 As shown, in this embodiment... Figure 6 Based on the embodiments, the control device for the vehicle-mounted pluggable device will be described in detail. The control device 70 for the vehicle-mounted pluggable device includes:
[0266] The receiving module 701 is used to receive a device authentication request sent by any vehicle terminal.
[0267] Extraction module 702 is used to extract device identity information from device authentication requests;
[0268] The authentication module 703 is used to authenticate the device based on the device identity information. The device authentication includes at least one of the following: device registration status authentication, certificate validity authentication, and access permission authentication.
[0269] The second generation module 704 is used to generate a globally unique device identifier and the first cloud response information corresponding to the globally unique device identifier when the device authentication is successful; wherein, the globally unique device identifier is used to represent the correspondence between the pluggable device corresponding to the device identity information and the vehicle terminal.
[0270] The sending module 705 is used to send the first cloud response information to the corresponding vehicle terminal;
[0271] The second generation module 704 is also used to generate a second cloud response information based on the received object model retrieval request;
[0272] The sending module 705 is also used to send the object model corresponding to the object model pull request to the corresponding vehicle terminal based on the second cloud response information.
[0273] In one possible implementation, the control device 70 further includes:
[0274] The clearing module 706 is used to clear the globally unique device identifier based on the received device unbinding request;
[0275] The second generation module 704 is also used to generate and send the third cloud response information to the corresponding vehicle terminal.
[0276] In one possible implementation, the control device 70 further includes:
[0277] The filing module 707 is used to file a device based on the device identity information of any pluggable device received, and to determine the legality of the certificate and access permissions corresponding to the pluggable device.
[0278] In one possible implementation, the control device 70 further includes:
[0279] The third generation module 708 is used to generate a device certificate corresponding to the pluggable device based on the device identity information after the device registration of the pluggable device is approved. The device certificate is used to verify the legality of the certificate.
[0280] The control device 70 for the vehicle-mounted pluggable device provided in this embodiment can execute the method provided in the above method embodiment. Its implementation principle and technical effect are similar, and will not be described in detail here.
[0281] Figure 8 This is a schematic diagram of the structure of the vehicle-mounted electronic device provided in this embodiment. Figure 8As shown, the vehicle-mounted electronic device 80 provided in this embodiment includes at least one processor 801 and a memory 802. Optionally, the vehicle-mounted electronic device 80 further includes a communication component 803. The processor 801, memory 802, and communication component 803 are connected via a bus 804.
[0282] In the specific implementation process, at least one processor 801 executes computer execution instructions stored in memory 802, causing at least one processor 801 to execute the control method of the above-mentioned vehicle-mounted pluggable device.
[0283] The specific implementation process of processor 801 can be found in the above method embodiments. The vehicle-mounted electronic device 80 can be deployed in the vehicle system or vehicle terminal. The memory is used to store device access control related programs, authentication processes, and object model processing rules. After the processor calls the computer to execute instructions, it can perform operations such as device identity acquisition, cloud authentication collaboration, object model retrieval, and control instruction organization when an external pluggable device is detected to be connected via USB, WiFi, Bluetooth, or CAN. This enables the vehicle terminal to complete device access and management around a unified trusted access link. Since the processor adopts object modeling to accommodate the capabilities of devices from different manufacturers according to the method, the vehicle terminal side does not need to continuously develop parsing logic for private protocols, thereby improving the compatibility, scalability, and access efficiency of multiple types of external pluggable devices. Therefore, it can reduce device adaptation and maintenance costs and enhance the unified management capability of vehicle-mounted external pluggable devices.
[0284] In the above embodiments, it should be understood that the processor can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), etc. The general-purpose processor can be a microprocessor or any conventional processor. The steps of the method disclosed in this invention can be directly implemented by a hardware processor, or implemented by a combination of hardware and software modules within the processor.
[0285] The memory may include random access memory (RAM) and non-volatile memory (NVM), such as at least one disk storage device.
[0286] The bus can be an Industry Standard Architecture (ISA) bus, a Peripheral Component Interconnect (PCI) bus, or an Extended Industry Standard Architecture (EISA) bus, etc. Buses can be categorized as address buses, data buses, control buses, etc. For ease of illustration, the buses shown in the accompanying drawings of this embodiment are not limited to a single bus or a single type of bus.
[0287] This embodiment also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described control method for a vehicle-mounted pluggable device.
[0288] In this embodiment, the computer program product can be stored in a non-transitory computer-readable storage medium and deployed on a vehicle terminal, vehicle controller, or a processing platform that collaborates with the cloud. When the processor executes the computer program, it can complete device insertion detection, device identity information acquisition, authentication request initiation, cloud authentication result reception, target device object model retrieval, and control command organization and issuance based on the object model. This allows device access, authentication, capability acquisition, and control execution to be completed in a unified processing link, thereby reducing the pressure on the vehicle terminal to directly adapt to different manufacturers' proprietary protocols. By abstracting device capabilities into a unified object model, the program logic can be reused as the device changes, eliminating the need to frequently rewrite the vehicle terminal's parsing process when adjusting protocol versions or expanding functions. This improves the consistency, scalability, and maintenance efficiency of external pluggable device access, thus facilitating unified and trusted management of in-vehicle external pluggable devices.
[0289] This embodiment also provides a computer-readable storage medium storing computer-executable instructions. When the processor executes the computer-executable instructions, the control method for the above-described vehicle-mounted pluggable device is implemented.
[0290] In this embodiment, the computer-readable storage medium can be deployed in the vehicle's infotainment system, gateway controller, or other vehicle terminals. The stored computer-executable instructions, when invoked by the processor, enable the vehicle terminal to obtain device identity information upon detecting the insertion of an external pluggable device. It then collaborates with the cloud to complete authentication. After successful authentication, it retrieves the object model corresponding to the device. The processor then organizes control instructions based on the object model, parses status data, and completes interactive execution. This integrates device access, authentication, capability acquisition, and control distribution into a unified software implementation chain, ensuring consistency in the access process for external pluggable devices from different interfaces and manufacturers. This reduces the need for repeated adaptation and modification of parsing logic for proprietary protocols on the vehicle side, thus improving the compatibility, scalability, and unified management efficiency of in-vehicle external pluggable device access.
[0291] The aforementioned readable storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk. The readable storage medium can be any available medium accessible to a general-purpose or special-purpose computer.
[0292] An exemplary readable storage medium is coupled to a processor, enabling the processor to read information from and write information to the readable storage medium. Of course, the readable storage medium can also be a component of the processor. The processor and the readable storage medium can reside in an Application Specific Integrated Circuit (ASIC). Alternatively, the processor and the readable storage medium can exist as discrete components in the device.
[0293] The division of units is merely a logical functional division; in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be indirect coupling or communication connection through some interfaces, devices, or units, and may be electrical, mechanical, or other forms.
[0294] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.
[0295] In addition, the functional units in the various embodiments of the present invention can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.
[0296] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.
[0297] Those skilled in the art will understand that all or part of the steps of the above-described method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When executed, the program performs the steps of the above-described method embodiments; and the aforementioned storage medium includes various media capable of storing program code, such as ROM, RAM, magnetic disks, or optical disks.
[0298] The above embodiments are merely preferred embodiments provided to fully illustrate the present invention, and the scope of protection of the present invention is not limited thereto. Equivalent substitutions or modifications made by those skilled in the art based on the present invention are all within the scope of protection of the present invention.
Claims
1. A control method for a vehicle-mounted pluggable device, characterized in that, The control method is applicable to a vehicle terminal, which is installed on a vehicle, and the control method includes: When device insertion information is detected, the device identity information of the device to be authenticated is obtained; wherein, the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle; Based on the device identity information, generate and send a device authentication request to the cloud; When the first cloud response information for the received device authentication request is an authentication pass response, the device to be authenticated is marked as an authenticated device, and a pull request for the object model corresponding to the authenticated device is generated and sent to the cloud. Based on the second cloud response information corresponding to the received object model retrieval request, obtain the object model; Based on the object model, control commands for the certified device are generated and issued.
2. The control method according to claim 1, characterized in that, After generating a device authentication request based on the device identity information, the control method further includes: Based on the vehicle security token, timestamp, and random number, a message authentication code algorithm is used to perform a signature anti-tampering operation on the device authentication request. The device authentication request after the signature anti-tampering operation is used to send to the cloud.
3. The control method according to claim 1, characterized in that, The object model includes at least model components and mapping relationships, wherein the model components include at least attributes, events, and services, and the mapping relationships are used to assign labels to the attributes, events, and services.
4. The control method according to claim 3, characterized in that, The label is 2 bytes long.
5. The control method according to claim 1, characterized in that, The step of generating and issuing control commands for the certified device based on the object model specifically includes: Based on the object model, the device operation instruction is converted into a first TLV message, wherein the device operation instruction is an instruction generated in the vehicle system for controlling the operation of the certified device; The first TLV message is converted into first binary data, and the converted first binary data is recorded as the control command. The control command is sent to the authenticated device.
6. The control method according to claim 5, characterized in that, The control method further includes: Convert the received second binary data into a second TLV message; According to the object model, the second TLV message is converted into device uplink data, wherein the device uplink data is used to characterize the operating status of the certified device.
7. The control method according to claim 1, characterized in that, The device identity information includes at least one of the following: device type, device unique identifier, device serial number (SN), device certificate, device private key signature, and device public key certificate.
8. The control method according to any one of claims 1-7, characterized in that, The control method further includes: When device disconnection information is detected, a device unbinding request is generated and sent to the cloud based on the device identity information of the authenticated device, wherein the device disconnection information is the information generated when the authenticated device disconnects from the vehicle; Based on the third cloud response information received regarding the device unbinding request, the device cache information of the object model and the certified device is cleared.
9. A control method for a vehicle-mounted pluggable device, characterized in that, The control method is applicable to the cloud and includes: Receive device authentication requests sent by any vehicle terminal; Extract the device identity information from the device authentication request; Based on the device identity information, device authentication is performed, wherein the device authentication includes at least one of device registration status authentication, certificate validity authentication, and access permission authentication; Upon successful device authentication, a globally unique device identifier and a corresponding first cloud response information are generated; wherein, the globally unique device identifier is used to characterize the correspondence between the pluggable device corresponding to the device identity information and the vehicle terminal; Send the first cloud response information to the corresponding vehicle terminal; Based on the received object model retrieval request, generate a second cloud response message; Based on the second cloud response information, the object model corresponding to the object model retrieval request is sent to the corresponding vehicle terminal.
10. The control method according to claim 9, characterized in that, The control method further includes: The globally unique device identifier is cleared based on the received device unbinding request; Generate and send third-party cloud response information to the corresponding vehicle terminal.
11. The control method according to claim 9, characterized in that, The control method further includes: Based on the device identity information of any pluggable device received, device registration is performed, and the legality of the certificate and access permissions corresponding to the pluggable device are determined.
12. The control method according to claim 11, characterized in that, The control method further includes: After the device registration of the pluggable device is approved, a device certificate corresponding to the pluggable device is generated based on the device identity information. The device certificate is used for certificate legality authentication.
13. A control device for a vehicle-mounted pluggable device, characterized in that, The control device is applicable to a vehicle terminal, the vehicle terminal being installed on a vehicle, and the control device includes: The acquisition module is used to acquire the device identity information of the device to be authenticated when device insertion information is detected; wherein, the device to be authenticated is the device inserted into the vehicle, and the device insertion information is the information generated when the device to be authenticated is inserted into the vehicle; The request module is used to generate and send a device authentication request to the cloud based on the device identity information; The request module is further configured to mark the device to be authenticated as an authenticated device when the first cloud response information of the received device authentication request is an authentication pass response information, and generate and send the object model pull request corresponding to the authenticated device to the cloud. The acquisition module is also used to acquire the object model based on the second cloud response information corresponding to the received object model pull request; The first generation module is used to generate and issue control commands for the certified device based on the object model.
14. A control device for a vehicle-mounted pluggable device, characterized in that, The control device is cloud-based and includes: The receiving module is used to receive device authentication requests sent by any vehicle terminal. The extraction module is used to extract the device identity information from the device authentication request; The authentication module is used to authenticate the device based on the device identity information, wherein the device authentication includes at least one of the following: device registration status authentication, certificate validity authentication, and access permission authentication. The second generation module is used to generate a globally unique device identifier and a first cloud response information corresponding to the globally unique device identifier when the device authentication is successful; wherein, the globally unique device identifier is used to characterize the correspondence between the pluggable device corresponding to the device identity information and the vehicle terminal; The sending module is used to send the first cloud response information to the corresponding vehicle terminal; The second generation module is also used to generate a second cloud response information based on the received object model retrieval request; The sending module is also used to send the object model corresponding to the object model retrieval request to the corresponding vehicle terminal according to the second cloud response information.
15. A vehicle-mounted electronic device, characterized in that, include: Memory, processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory, causing the processor to perform the method as described in any one of claims 1-8, or to perform the method as described in any one of claims 9-12.
16. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-8, or to implement the method as described in any one of claims 9-12.
17. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-8, or implements the method of any one of claims 9-12.
