Access method and device of vehicle-mounted equipment, vehicle and medium

Abstract

The embodiment of the invention provides a vehicle-mounted equipment access method and device, a vehicle and a medium, and the method comprises the steps: obtaining any vehicle-mounted equipment developed according to a development specification, enabling the vehicle-mounted equipment to be connected with the vehicle, enabling the vehicle to confirm the basic information of the vehicle-mounted equipment according to an equipment description file of the vehicle-mounted equipment, and enabling the basic information of the vehicle-mounted equipment to access the vehicle-mounted equipment; the method comprises the following steps: acquiring basic information of a vehicle-mounted device, performing access and authentication of the vehicle-mounted device based on the basic information, if the access and authentication of the vehicle-mounted device are completed, receiving a function discovery request of the vehicle-mounted device by the vehicle, comparing a function, needing to be supported by the vehicle, of the vehicle-mounted device in a device description file with a function provided by the vehicle, generating a comparison result, and sending the comparison result to the vehicle-mounted device; and the vehicle receives a function calling request sent by the vehicle-mounted equipment according to the comparison result, and executes a corresponding function according to the function calling request. According to the embodiment of the invention, different devices of different manufacturers can actively find functions provided by the vehicle, and linkage is realized.

Description

Technical Field

[0001] The present invention relates to the field of automobile technology, and in particular to an access method, device, vehicle and medium for vehicle-mounted equipment. Background Art

[0002] There are two types of existing in-vehicle intelligent hardware devices: one is the pre-installed solution, and the other is the post-installed solution.

[0003] Automaker pre-installed solutions: usually customized and developed by automakers and parts manufacturers to achieve certain specific functions and scenarios of the vehicle.

[0004] After-sales user solution: developed by third-party parts manufacturers for different car companies' models. In this solution, users can purchase hardware products that meet their needs, but they are basically unable to interact with the vehicle, that is, control some functions of the vehicle through the device or control some functions of the device through the vehicle. Of course, there are currently some solutions that physically connect to the car's OBD (On Board Diagnostics, the communication protocol standard of the on-board diagnostic system) to interact with the vehicle, such as controlling the locking of the car and raising the windows, driving the car and locking, and folding the rearview mirrors, but the functions realized by this control are limited, and it needs to be customized for different models of different car companies and even different brands.

[0005] However, through the analysis of the interaction mode between existing in-vehicle intelligent hardware and vehicles, it is not difficult to find the following shortcomings:

[0006] 1. Although the pre-installation solution can well realize the two-way interaction between smart devices and vehicles, if users want to obtain other new hardware products or functions in the future, car companies cannot meet their needs, which is not conducive to improving user experience and expanding product ecological diversity.

[0007] 2. After-sales solutions, such as tire pressure monitoring smart devices and after-sales dashcams, are all "independent" and do not interact with other car systems. This so-called intelligence has lagged behind the current market development needs of the Internet of Everything.

[0008] 3. Even the OBD protocols are not consistent. First, different models of the same brand may use different OBD protocols. For example, the OBD protocols of trucks and cars may be different. Second, the OBD standards of different countries may not be consistent. For example, the United States, Europe, and China all have their own OBD standards, which may be different and will limit the compatibility of smart hardware developed by this method.

[0009] The root cause is the lack of relevant function discovery standard protocols and development specifications between vehicles and smart hardware, which makes it difficult for on-board smart hardware and vehicles to discover each other's capabilities. Furthermore, there is no unified API (Application Programming Interface) for interoperability. Faced with different user scenarios and smart hardware product requirements, it is impossible for car companies to customize and develop all smart hardware to meet the various needs of consumers. Similarly, under this model, it is impossible for smart hardware manufacturers to fully adapt to all brands and models on the market. Summary of the invention

[0010] In view of the above problems, an embodiment of the present invention proposes an access method, device, vehicle and medium for an in-vehicle device.

[0011] In a first aspect of the implementation of the present invention, a method for accessing a vehicle-mounted device is first provided, wherein the method comprises:

[0012] Obtain any vehicle-mounted device developed according to the development specification; the development specification is obtained from the open platform through the vehicle-mounted device manufacturing platform, and the open platform is used to obtain the development specification and device interface description file template uploaded by the original device manufacturing platform;

[0013] The vehicle-mounted device is connected to the vehicle, and the vehicle confirms basic information of the vehicle-mounted device according to a device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information; the device description file includes basic information of the vehicle-mounted device and functions of the vehicle-mounted device that the vehicle needs to support;

[0014] If the access and authentication of the vehicle-mounted device are completed, the vehicle receives the function discovery request of the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device;

[0015] The vehicle receives a function call request issued by the on-board device according to the comparison result, and executes a corresponding function according to the function call request.

[0016] Optionally, the development specification includes an interface specification; and the method further includes:

[0017] determining a standard application programming interface to be deployed to the vehicle based on the interface specification;

[0018] The vehicle communicates with the on-board device via the standard application programming interface.

[0019] Optionally, the device description file also includes connection information of the vehicle-mounted device;

[0020] The vehicle-mounted device is connected to the vehicle, the vehicle confirms basic information of the vehicle-mounted device according to a device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information, including:

[0021] The vehicle detects access to the vehicle-mounted device via a power interface;

[0022] The vehicle provides power to the on-board device for access and authentication;

[0023] The vehicle sends a request to read the device description file to the on-board device through a standard application programming interface;

[0024] The vehicle receives and parses the device description file returned by the vehicle-mounted device to obtain basic information and connection information of the vehicle-mounted device;

[0025] The vehicle accesses and authenticates the on-board device according to the basic information and the connection information.

[0026] Optionally, before the vehicle accesses and authenticates the on-board device according to the basic information and the connection information, the process further includes:

[0027] The vehicle supplies power to the on-board device for a preset period according to the power supply requirement of the on-board device in the basic information;

[0028] If the vehicle fails to complete the access and authentication of the on-board device within a preset period, the power supply is stopped;

[0029] If the vehicle completes the access and authentication of the on-board device within a preset period, power supply continues.

[0030] Optionally, if the access and authentication of the vehicle-mounted device are completed, the vehicle receives a function discovery request of the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device, including:

[0031] The vehicle receives a function discovery request sent by the on-board device through a standard application programming interface;

[0032] The vehicle queries the device description file for the functions that the vehicle needs to support according to the function discovery request, and compares the functions with the functions provided by the vehicle;

[0033] The vehicle generates a comparison result and sends it to the vehicle-mounted device through the standard application programming interface.

[0034] Optionally, the vehicle receives a function call request issued by the vehicle-mounted device according to the comparison result, and executes a corresponding function according to the function call request, including:

[0035] The vehicle receives a function call request from the vehicle-mounted device through a standard application programming interface; the function call request is a function specifically provided by the vehicle confirmed by the vehicle-mounted device according to the comparison result;

[0036] The vehicle executes a corresponding function according to the function call request.

[0037] Optionally, the method further comprises:

[0038] The vehicle receives a custom command set by the vehicle-mounted device;

[0039] The vehicle recognizes the custom command issued by the user;

[0040] The vehicle sends the identified custom command to the vehicle-mounted device; the vehicle-mounted device is used to execute a corresponding function according to the custom command;

[0041] The vehicle receives a response indicating that the in-vehicle device has been successfully executed.

[0042] In a second aspect of the present invention, there is also provided an access device for a vehicle-mounted device, characterized in that the device comprises:

[0043] An acquisition module, used to acquire any vehicle-mounted device developed according to a development specification; the development specification is acquired from an open platform by the vehicle-mounted device manufacturing platform, and the open platform is used to acquire the development specification and device interface description file template uploaded by the original device manufacturing platform;

[0044] An access authentication module, used to connect the vehicle-mounted device to the vehicle, the vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and performs access and authentication of the vehicle-mounted device based on the basic information; the device description file includes the basic information of the vehicle-mounted device and the functions that the vehicle-mounted device needs to support from the vehicle;

[0045] A function discovery module, configured to, if the access and authentication of the vehicle-mounted device are completed, cause the vehicle to receive a function discovery request of the vehicle-mounted device, compare the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generate a comparison result and send it to the vehicle-mounted device;

[0046] The function calling module is used for the vehicle to receive a function calling request issued by the vehicle-mounted device according to the comparison result, and execute a corresponding function according to the function calling request.

[0047] In the third aspect of the implementation of the present invention, a vehicle is also provided, characterized in that it includes a processor, a memory, and a computer program stored in the memory and capable of running on the processor, and when the computer program is executed by the processor, the access method of the vehicle-mounted device as described above is implemented.

[0048] In the fourth aspect of the implementation of the present invention, a computer-readable storage medium is also provided, characterized in that a computer program is stored on the computer-readable storage medium, and when the computer program is executed by a processor, the access method of the vehicle-mounted device as described above is implemented.

[0049] The embodiments of the present invention have the following advantages:

[0050] In an embodiment of the present invention, the vehicle-mounted device is connected to the vehicle by acquiring any vehicle-mounted device developed in accordance with the development specifications. The vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information. The device description file includes the basic information of the vehicle-mounted device and the functions of the vehicle-mounted device that the vehicle needs to support. If the access and authentication of the vehicle-mounted device are completed, the vehicle receives a function discovery request from the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file that the vehicle needs to support with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device. The vehicle receives a function call request issued by the vehicle-mounted device based on the comparison result, and executes the corresponding function according to the function call request. Therefore, the embodiments of the present invention use unified device description files and development specifications, so that cars of different brands and models can be compatible with various smart hardware, thereby solving the problem of protocol inconsistency. Users can also choose and access different smart hardware according to their own needs to achieve a personalized driving experience without being restricted by the vehicle's pre-installed solution. Standardized development specifications and device description files simplify the manufacturer's development process and reduce the development cost and time for adapting to different vehicles. In addition, the device can automatically discover and call the vehicle's functions to achieve more intelligent and automated operations, such as automatically adjusting the in-vehicle environment to suit the user's preferences. At the same time, the smart hardware can automatically adjust its functions according to the function list provided by the vehicle to adapt to different environments and conditions, thereby improving the adaptability and flexibility of the device. BRIEF DESCRIPTION OF THE DRAWINGS

[0051] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the following briefly introduces the drawings required for use in the embodiments or the description of the prior art.

[0052] Figure 1is a flowchart of a method for accessing a vehicle-mounted device provided by an embodiment of the present invention;

[0053] Figure 2 It is a logic diagram of a vehicle-mounted device access method provided by an embodiment of the present invention;

[0054] Figure 3 is a flow chart of vehicle function discovery and invocation provided by an embodiment of the present invention;

[0055] Figure 4 It is a structural schematic diagram of an access device for a vehicle-mounted device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0056] In order to make the purpose, technical scheme and advantages of the embodiments of the present invention clearer, the embodiments of the present invention will be described in detail below in conjunction with the accompanying drawings. However, it can be understood by those skilled in the art that in the embodiments of the present invention, many technical details are proposed in order to enable readers to better understand the present invention. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present invention can also be implemented. The division of the following embodiments is for the convenience of description and should not constitute any limitation on the specific implementation of the present invention. The various embodiments can be combined and referenced with each other without contradiction.

[0057] The present invention provides an access method for vehicle-mounted devices. The OEM (Original Equipment Manufacturer) provides a set of standard development specifications, device interface description files and vehicle function list files, so that the equipment of the parts manufacturer (hereinafter referred to as "equipment") can obtain these specifications and files, and then develop according to the development specifications. After accessing the vehicle, the device can automatically discover and call the functions provided by the vehicle according to the standard API interface, including but not limited to large screen, voice, power supply, windows, etc., and finally realize the operation of the vehicle functions by the device, so that the personalized needs of users can be realized according to the settings of different scenarios.

[0058] Reference Figure 1 , shows a flowchart of a method for accessing a vehicle-mounted device provided by an embodiment of the present invention, which may specifically include the following steps:

[0059] Step 101, obtain any vehicle-mounted device developed according to the development specification; the development specification is obtained from the open platform through the vehicle-mounted device manufacturing platform, and the open platform is used to obtain the development specification and device interface description file template uploaded by the original equipment manufacturing platform.

[0060] It should be noted that the original equipment manufacturing platform is the OEM (Original Equipment Manufacturer), which organizes the development specifications and device interface description file templates and uploads them to the open platform. The open platform is managed, operated and maintained by the OEM, which is the original editor of the development specifications and device interface description file templates. The vehicle-mounted equipment manufacturing platform is the vehicle-mounted equipment manufacturer, which obtains the development specifications and device interface description file templates through the open platform provided by the OEM, and develops the vehicle-mounted equipment according to the obtained development specifications and device interface description file templates. Among them, the vehicle-mounted equipment can be a variety of different vehicle-mounted equipment developed by multiple different vehicle-mounted equipment manufacturers.

[0061] First, the OEM will develop a set of development specifications and a set of standard device interface description file templates and upload them to the open platform, and upload the function list supported by different brands / models to the open platform. Among them, the development specifications include naming specifications, interface specifications, test specifications, etc. The device interface description file template provides the filling standard, including the basic information of the vehicle-mounted equipment, connection methods, and a list of functions that need to be supported by the vehicle.

[0062] After the OEM uploads the various files to the open platform, all vehicle equipment manufacturers can obtain development specifications, device interface description file templates and function lists from the open platform. After that, the vehicle equipment manufacturers analyze the functional requirements of their own vehicle equipment, determine what interactions and operations the vehicle equipment needs to perform with the vehicle, select appropriate vehicle functions from the function list provided by the OEM according to the functional requirements of the vehicle equipment, and develop the vehicle equipment according to the development specifications and device interface description file templates. Among them, the vehicle functions selected from the function list provided by the OEM need to meet the operational requirements of the vehicle equipment.

[0063] Specifically, in the embodiment of the present invention, the division of labor between the OEM and the vehicle-mounted equipment manufacturer is shown in Table 1:

[0064] Table 1 Division of work between OEMs and vehicle equipment manufacturers

[0065]

[0066] In the embodiment of the present invention, when developing a vehicle-mounted device, the vehicle-mounted device manufacturer needs to create a detailed device description file according to the device interface description file template obtained from the open platform. This file should contain the following information:

[0067] Basic information of vehicle-mounted equipment: including the name, model, manufacturer, version number, etc. of the equipment.

[0068] Connection method: The technical method used to connect the device to the vehicle, such as USB, Bluetooth, Wi-Fi, etc.

[0069] List of functions that the vehicle-mounted device needs to support: resources required for the device to operate, including power supply requirements (voltage, current, power, etc.), data transmission rate, required vehicle functions, etc.

[0070] Vehicle equipment manufacturers need to compile according to the format and filling standards specified in the device interface description file template. Take the vehicle-mounted intelligent environment detector as an example:

[0071] Basic functions of the vehicle-mounted intelligent environmental detector: real-time monitoring of the air quality environment in the vehicle, including carbon dioxide concentration, oxygen content, and PM2.5 value.

[0072] Equipment requirements for vehicle-mounted intelligent environmental detector: The vehicle needs to provide a 5V / 2A constant power supply interface.

[0073] Expanded capabilities of the vehicle-mounted intelligent environmental detector: You can call vehicle-related functions according to preset scenarios or user-defined scenarios, such as opening windows and turning on the air conditioning internal / external circulation. You can also register voice commands for the basic functions of your own products to the vehicle, so that users can control the vehicle-mounted intelligent environmental detector through voice commands, such as turning the device on and off.

[0074] The basic information of the vehicle-mounted intelligent environment detector is shown in Table 2:

[0075] Table 2 Basic information of vehicle-mounted intelligent environmental detector

[0076]

[0077] The connection method of the vehicle-mounted intelligent environment detector is shown in Table 3:

[0078] Table 3 Connection method

[0079]

[0080]

[0081] The list of functions that the vehicle-mounted equipment needs to support is shown in Table 4:

[0082] Table 4 List of functions that need to be supported by the vehicle

[0083]

[0084]

[0085] The above is a list of functions that the vehicle needs to support for the example vehicle-mounted intelligent environment detector. In fact, the vehicle can also support more other function calls, as shown in Table 5, which are other function calls supported by the vehicle. This is only an example to express that the functions provided by the vehicle are diverse, and does not mean that the following are all the functions that can be provided:

[0086] Table 5 Other function calls

[0087]

[0088] Specifically, the purpose of providing the basic information of the on-board equipment is to provide the vehicle with the basic information of the on-board equipment, to ensure that the vehicle can correctly identify the on-board equipment and further provide the required power supply function to the on-board equipment; the connection method is provided to provide the vehicle with the connection and authentication information of the on-board equipment, to ensure that the vehicle can be accessed and authenticated according to the connection authentication requirements of the on-board equipment; the provision of a list of functions that the on-board equipment requires the vehicle to support is to ensure that subsequent development work can be carried out strictly in accordance with the functions of this list. In principle, the content of the list of functions that different devices from different manufacturers require the vehicle to support is different.

[0089] In an embodiment of the present invention, after the manufacturer of the on-board intelligent environment detector obtains the development specifications, device interface description file template and vehicle function list through the open platform provided by the OEM, the manufacturer can develop according to the specifications and filled-in documents as a reference. After completing the test, the on-board intelligent environment detector can be deployed to the vehicle.

[0090] Step 102, connecting the vehicle-mounted device to the vehicle, the vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information; the device description file includes the basic information of the vehicle-mounted device and the functions that the vehicle-mounted device needs to support.

[0091] In an embodiment of the present invention, when the on-board device is normally connected to the vehicle, that is, after being deployed to the vehicle, the vehicle will actively send a request to the on-board device to read the device description file. When the on-board device receives the request, it will return its own device description file information to the vehicle. After the vehicle receives the device description file returned by the on-board device, it will parse it to obtain various types of information of the on-board device. The vehicle will correctly identify the on-board device through the basic information of the on-board device in the device description file, and access and authenticate according to the connection method in the device description file.

[0092] Step 103, if the access and authentication of the vehicle-mounted device is completed, the vehicle receives the function discovery request of the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file requires the vehicle to support with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device.

[0093] In the embodiment of the present invention, after the vehicle-mounted device completes the access process, it uses a unified API in accordance with the development specification to initiate a function discovery request to the vehicle. The purpose of the function discovery request is to confirm with the vehicle whether all the functions included in the function list required to be supported by the vehicle in the device description file are available to the vehicle. The following is an example of a request in JSON format:

[0094] After receiving the function discovery request, the vehicle will query the function list in the previously requested device description file that the vehicle needs to support, compare it with the functions currently provided by the vehicle, and respond to the comparison results to the vehicle device. In this way, the vehicle device can know which specific function calls the vehicle can provide.

[0095] Step 104: the vehicle receives a function call request issued by the vehicle-mounted device according to the comparison result, and executes a corresponding function according to the function call request.

[0096] Specifically, after the on-board device receives the comparison result obtained by the vehicle by comparing the functions in the function list that the vehicle needs to support in the device description file with the functions that the vehicle can currently provide, it can know what specific functions the vehicle can provide, and then send a function call request to the vehicle based on the confirmed functions that the vehicle can provide. After receiving the function call request, the vehicle will perform corresponding operations according to the content of the request, such as adjusting the vehicle speed, adjusting the opening and closing of the air conditioner and windows, etc.

[0097] In an embodiment of the present invention, the vehicle-mounted device is connected to the vehicle by acquiring any vehicle-mounted device developed in accordance with the development specifications. The vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information. The device description file includes the basic information of the vehicle-mounted device and the functions of the vehicle-mounted device that the vehicle needs to support. If the access and authentication of the vehicle-mounted device are completed, the vehicle receives a function discovery request from the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file that the vehicle needs to support with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device. The vehicle receives a function call request issued by the vehicle-mounted device based on the comparison result, and executes the corresponding function according to the function call request. Therefore, the embodiments of the present invention use unified device description files and development specifications, so that cars of different brands and models can be compatible with various smart hardware, thereby solving the problem of protocol inconsistency. Users can also choose and access different smart hardware according to their own needs to achieve a personalized driving experience without being restricted by the vehicle's pre-installed solution. Standardized development specifications and device description files simplify the manufacturer's development process and reduce the development cost and time for adapting to different vehicles. In addition, the device can automatically discover and call the vehicle's functions to achieve more intelligent and automated operations, such as automatically adjusting the in-vehicle environment to suit the user's preferences. At the same time, the smart hardware can automatically adjust its functions according to the function list provided by the vehicle to adapt to different environments and conditions, thereby improving the adaptability and flexibility of the device.

[0098] In an optional embodiment of the present invention, the following sub-steps are also included:

[0099] S1, determining a standard application programming interface to be deployed to the vehicle according to the interface specification;

[0100] S2, the vehicle communicates with the on-board device via the standard application programming interface.

[0101] In an embodiment of the present invention, the development specification includes an interface specification, which is used to provide a standard API interface and deploy it to the vehicle, so that the vehicle and the on-board equipment developed according to the development specification can communicate through a unified standard API interface.

[0102] In an optional embodiment of the present invention, step 102 further includes the following sub-steps:

[0103] S1021, the vehicle detects the access of the vehicle-mounted device through the power interface.

[0104] In the embodiment of the present invention, automatic identification of the load (i.e., the vehicle-mounted device) and supply of power can generally be achieved by using a power interface with intelligent identification or automatic switching function. Such an interface can detect the access of the load and automatically start the power supply accordingly.

[0105] Specifically, a load detection module can be integrated into the circuit. This module can monitor parameters such as current, voltage or power to determine whether there is a load connected and control the power switch. This solution is already very mature. Currently, there are many chips that integrate load detection and power management functions. These chips can automatically adjust the power output according to the load conditions, and even enter a low-power standby mode when there is no load.

[0106] S1022, the vehicle provides power to the on-board device for access and authentication.

[0107] After the vehicle-mounted device is installed, the vehicle will automatically discover the device and provide power support, but this power supply support will be subject to time and power limits. The vehicle-mounted device must complete device access and authentication within the specified time, otherwise the power supply will be disconnected and limited power supply will only be provided again when the vehicle-mounted device is connected next time.

[0108] S1023, the vehicle sends a request to read the device description file to the on-board device through a standard application programming interface.

[0109] Specifically, when the on-board device is normally connected to the vehicle, the vehicle will actively send a device description file reading request to the on-board device through the standard API interface.

[0110] S1024, the vehicle receives and parses the device description file returned by the vehicle-mounted device to obtain basic information and connection information of the vehicle-mounted device.

[0111] Specifically, when the on-board device receives a device description file reading request sent by the vehicle, it will return its own device description file to the vehicle. After the vehicle obtains the device description file of the on-board device, it will parse it and obtain various types of information about the on-board device, namely, the basic information of the on-board device, the connection method, and the list of functions that the vehicle needs to support.

[0112] S1025: The vehicle accesses and authenticates the on-board device according to the basic information and the connection information.

[0113] Specifically, after obtaining the basic information and connection method of the vehicle-mounted device, power is provided for access and authentication according to the power supply requirements in the basic information, and then access and authentication are performed according to the connection method of the vehicle-mounted device. Taking the above-mentioned vehicle-mounted intelligent environmental detector as an example, the power supply requirement PowerRequirements in its basic information is 5V / 2A, then 5V / 2A power supply is provided for access and authentication of the vehicle-mounted device, and AutoIdentityPairing can be used to authenticate the device, and the access and authentication of the device are automatically completed by identifying the UUID.

[0114] In an optional embodiment of the present invention, before S1024, the following sub-steps are also included:

[0115] S1024-1, the vehicle supplies power to the on-board device for a preset period according to the power supply requirement of the on-board device in the basic information;

[0116] S1024-2, if the vehicle fails to complete the access and authentication of the on-board device within a preset period, stop power supply;

[0117] S1024-3: If the vehicle completes the access and authentication of the on-board device within a preset period, the power supply continues.

[0118] In an embodiment of the present invention, after parsing various types of information of the on-board device (basic information of the on-board device, connection method, and a list of functions that the vehicle needs to support), the vehicle supplies power to the on-board device according to the power supply requirements in the basic information. Next, the on-board device can enter the normal access process and perform access and authentication according to the connection method in the device description file.

[0119] Taking the above-mentioned vehicle-mounted intelligent environment detector as an example, the power supply requirement PowerRequirements in its basic information is 5V / 2A, so the vehicle will provide a 5V / 2A power supply with a preset period of 3 minutes for the load power endpoint of the device. If the vehicle-mounted intelligent environment detector is normally connected and passes the authentication within the preset period of 3 minutes, the power supply will continue, otherwise the power supply will be stopped until the next time the vehicle-mounted device is connected.

[0120] After the vehicle provides power support for the on-board intelligent environment detector, it can be connected and authenticated according to the connection method in the device description file of the on-board intelligent environment detector. AutoIdentityPairing can be used to authenticate the device, and the device access and authentication are automatically completed by identifying the UUID.

[0121] In an optional embodiment of the present invention, step 103 further includes the following sub-steps:

[0122] S1031, the vehicle receives a function discovery request sent by the vehicle-mounted device through a standard application programming interface;

[0123] S1032, the vehicle queries the device description file for the functions that the vehicle needs to support according to the function discovery request, and compares the functions with the functions provided by the vehicle;

[0124] S1033: The vehicle generates a comparison result and sends it to the vehicle-mounted device through the standard application programming interface.

[0125] In the embodiment of the present invention, taking the vehicle-mounted intelligent environment detector as an example, after the vehicle-mounted intelligent environment detector completes the access process and successfully enters the network, it uses a unified API to initiate a function discovery request to the vehicle. The purpose of this request is to confirm with the vehicle whether all the functions included in the function list required to be supported by the vehicle in the device description file are available in the vehicle. The following is a simple request example in JSON format:

[0126] "features": [

[0127] {

[0128] "functionName":"sendCustomVoicecommand",

[0129] "description": / / Specific function list

[0130] },

[0131] {

[0132] "functionName":"OpenExternalCirculation",

[0133] "description": / / Specific function list

[0134] },

[0135] / / …other function points follow the same format

[0136] {

[0137] "functionName":"DisplayMainScreenNotification",

[0138] "description": / / Specific function list

[0139] } ]

[0141] }

[0142] This example contains a series of descriptions of features, each of which has a name (functionName) and a description (description). features: This is an array containing descriptions of multiple features; functionName: is a string indicating the name of the feature; description: is a string indicating a detailed description of the feature.

[0143] After receiving the function discovery request, the vehicle will query the function list in the device description file of the previously requested vehicle intelligent environment detector that needs to be supported by the vehicle, compare it with the functions currently provided by the vehicle, and respond with the comparison results. The following is a simple response example in JSON format. In this example, it is assumed that the vehicle does not support steering wheel heating and seat ventilation functions:

[0144]

[0145] This example shows the successful result of an API call and lists the supported function points and their status. 200OK: indicates that the HTTP request is successful; Content-Type: application / json: indicates that the content type of the response is in JSON format; status: is a string indicating the status of the request, "status": "success" indicates that the request is successful; supportedFeatures: This is an object containing the support status of multiple function points, with the name of each function point as the key and the corresponding value being a Boolean value (true or false) indicating whether the function is supported.

[0146] In this way, the on-board intelligent environment detector can know what specific function calls the vehicle can provide.

[0147] It should be noted that the capabilities of vehicles with different configurations may be different. This method allows the on-board equipment to dynamically confirm the function calls that the vehicle can provide, so as to facilitate better subsequent work without the need for separate coding for different vehicle models and configurations.

[0148] In an optional embodiment of the present invention, step 104 further includes the following sub-steps:

[0149] S1041, the vehicle receives a function call request from the vehicle-mounted device through a standard application programming interface; the function call request is a function specifically provided by the vehicle confirmed by the vehicle-mounted device according to the comparison result;

[0150] S1042: The vehicle executes a corresponding function according to the function call request.

[0151] In an embodiment of the present invention, the on-board device can confirm the function calls that the vehicle can provide by comparing the list of functions that the vehicle needs to support in the device description file returned by the vehicle with the functions that the vehicle can currently provide, and thus can send a function call request to the vehicle according to actual needs based on the confirmed function call. The vehicle receives the function call request issued by the on-board device and executes the response function according to the function call request.

[0152] In an optional embodiment of the present invention, the following sub-steps are also included:

[0153] S11, the vehicle receives a custom command set by the vehicle-mounted device;

[0154] S12, the vehicle recognizes the custom command issued by the user;

[0155] S13, the vehicle sends the identified custom command to the vehicle-mounted device; the vehicle-mounted device is used to execute a corresponding function according to the custom command;

[0156] S14, the vehicle receives a response indicating that the in-vehicle device has executed successfully.

[0157] In the embodiment of the present invention, taking the vehicle-mounted intelligent environment detector as an example, a function call is performed through a custom voice command. The vehicle-mounted intelligent environment detector itself also has some functions. The function list supported by the vehicle-mounted intelligent environment detector is shown in Table 6:

[0158] Table 6 Functions supported by the vehicle-mounted intelligent environment detector

[0159]

[0160]

[0161] It should be noted that the car APP, that is, the car information application (Car Infotainment App), is an application in the car device.

[0162] The vehicle can provide custom commands, and through the transparent transmission of commands, the user can control the device's functions through the vehicle's "custom voice control function". In essence, this is achieved by the device calling the functions provided by the vehicle.

[0163] Specifically, the corresponding voice control command is set through the CustomVoiceCommand (custom voice command) opened by the vehicle. After the vehicle receives the set value, once the user executes the voice command, the vehicle will send the specific 'CustomVoiceCommand' to the on-board intelligent environment detector through the standard API interface to realize the control of the device. Among them, the CustomVoiceCommand opened by the vehicle refers to a function provided by the vehicle infotainment system or intelligent voice assistant, which allows users to set specific voice commands according to their needs and preferences, so as to more conveniently control various functions of the vehicle or perform specific operations.

[0164] The following are the two main API interaction processes of this function. The first is the process of the vehicle intelligent environment detector setting a custom voice command to the vehicle. The second is the process of the vehicle passing the command to the vehicle intelligent environment detector after the user issues a voice command. The following are API examples of these two processes:

[0165] (a) API request and response for setting custom voice commands for the in-vehicle intelligent environment detector

[0166]

[0167] In this example, the request part is:

[0168] POST / api / vehicle / voice / command / set: indicates that the HTTP POST method is used to send a request to the URL / api / vehicle / voice / command / set, with the purpose of setting a custom voice command; Content-Type:application / json: indicates that the content type of the request body is in JSON format; voiceCommand: This is an object containing two properties: phrase: This is a string that represents the specific phrase of the voice command, such as "turn on the vehicle-mounted intelligent environment detector"; action: This is a string that represents the action corresponding to this voice command, such as "openDevice".

[0169] Response section:

[0170] 200OK: indicates that the HTTP request is successful; Content-Type: application / json: indicates that the content type of the response is in JSON format; status: This is a string indicating the status of the request processing, "success" indicates success; message: This is a string that provides additional information about the request processing result, such as "custom voice command has been set successfully." indicating that the custom voice command has been successfully set; command: This is an object that contains the same two properties as in the request body: phrase: This is a string indicating the specific phrase of the voice command, such as "turn on the in-vehicle intelligent environment detector"; action: This is a string indicating the action corresponding to this voice command, such as openDevice.

[0171] (b) After the user issues a voice command, the vehicle transmits the command to the API request and response of the on-board intelligent environment detector

[0172] ##API Request from vehicle to Environmental Detector

[0173] ####Request

[0174] POST / api / environmental / detector / action

[0175] content-Type:application / json

[0176] {

[0177] "action": "openDevice"

[0178] }

[0179] ####Response

[0180] 200OK

[0181] content-Type:application / json

[0182] ```json

[0183] {

[0184] "status": "success",

[0185] "message":"Environmental detector has been activated successfully."}

[0186] }

[0187] In this example, the request part is:

[0188] POST / api / environmental / detector / action: means using HTTP POST method to send a request to the URL / api / environmental / detector / action, the purpose is to trigger an action of the environmental detector; action: This is a string that indicates the action to be performed, such as openDevice means opening the device.

[0189] Response part: status: This is a string indicating the status of the request processing, "success" means success; message: This is a string that provides additional information about the request processing results, such as "Environmentaldetector has been activated successfully." means that the environmental detector has been successfully activated.

[0190] In the first API example, the vehicle-mounted intelligent environment detector sets a custom voice command by sending a POST request to the ' / api / vehicle / voice / command / set' endpoint. The request body contains the voice phrase that the user is going to say and the corresponding action.

[0191] In the second API example, when the user speaks the set voice command, the vehicle recognizes the command and sends the command to the ' / api / environmental / detector / action' endpoint through a POST request to trigger the action of the on-board intelligent environment detector. The environment detector returns a successful response after executing the action.

[0192] In the embodiment of the present invention, in addition to the voice function call, there are other function calls, which are triggered according to the scene function of the vehicle-mounted intelligent environment detector itself or the user's settings. After the setting is successful, the vehicle will call the vehicle-side function through a unified API interface according to the specific function, and the vehicle-side will return the execution result after execution. For example, when the PM2.5 value exceeds the standard, the vehicle's large-screen notification function can be called to display the PM2.5 exceeding standard event notification on the user's large screen, or when the temperature in the car is high, the windows can be closed and the air conditioner can be turned on to the cooling mode according to the customized scene settings.

[0193] It should be noted that the present invention is not limited to the functions that can be realized by the vehicle-mounted intelligent environment detector in the embodiment. As long as it is a compliant vehicle-mounted device, it can realize the call of all functions possessed by the vehicle, and the vehicle itself does not need to know the specific information of the device in advance.

[0194] Reference Figure 2 , shows a logic diagram of a vehicle-mounted device access method provided by an embodiment of the present invention, which may specifically include the following contents:

[0195] Car manufacturer 1 (OEM) formulates a set of development specifications and a set of standard device interface description file templates and uploads them to open platform 2 managed, operated and maintained by car manufacturer 1. At the same time, it provides a list of atomic services that can be opened for the brand / model vehicle, that is, a list of supported functions uploaded to open platform 2. Among them, the filling standard is given in the device interface description file template, and its content includes the basic information of the vehicle-mounted equipment, the connection method, and the list of functions that the vehicle needs to support. At the same time, open platform 2 provides a standard function call interface API for the vehicle according to the interface specifications in the development specifications.

[0196] All development companies 3 (in-vehicle equipment manufacturers) obtain development specifications, device interface description file templates and function lists from the open platform 2 to develop in-vehicle intelligent terminal products (in-vehicle equipment), and deploy the products developed in accordance with the specifications to the vehicles of the car company 1.

[0197] Products deployed to vehicles can use a unified API interface to call the functions provided by the vehicle in accordance with development specifications.

[0198] Reference Figure 3 , shows a flow chart of vehicle function discovery and calling provided by an embodiment of the present invention, taking the vehicle-mounted intelligent environment detector as an example, which may specifically include the following contents:

[0199] 1. Install the vehicle-mounted intelligent environment detector in a fixed position on the vehicle. The vehicle-mounted intelligent environment detector is a normally powered device, so it needs to be installed in a position with a power supply bayonet. The power supply end of the device will contact the power supply metal contact provided by the vehicle during installation.

[0200] 2. The vehicle automatically identifies the load (on-board intelligent environmental detector) and provides the power required for basic communication, and sets a disconnection countdown.

[0201] If the device is not connected to the vehicle according to the normal process within the specified time, the vehicle will disconnect the power supply of the interface until the next time it actively recognizes the load connection.

[0202] 3. The vehicle sends a device description file read request to the device. After receiving the request, the device returns its own device description file to the vehicle. The vehicle can obtain basic information about the device through the read request and further provide power requirements according to the device description file requirements.

[0203] 4. The vehicle reads the power requirement description in the device description file and provides the device with the power requirement described in the device description file, that is, 5V / 2A.

[0204] 5. The vehicle reads the connection method information in the device description file, performs access authentication, executes the normal access process and completes the device access and authentication.

[0205] 6. The device sends a vehicle function list confirmation request, i.e., a function discovery request, to the vehicle. After receiving the request, the vehicle will query the functions in the "list of functions that need to be supported by the vehicle" in the device interface description file requested previously, and compare them with the functions that the vehicle can currently provide, and respond to the comparison results to the device.

[0206] The device confirms with the vehicle the list of functions supported by the vehicle to adapt to different vehicle models.

[0207] 7. Since the vehicle's voice control commands need to be called, the commands must be set through the voice control function provided by the vehicle.

[0208] The device sends a "custom voice control command setting request" to the vehicle, the vehicle receives the request and sets the custom voice command, and the vehicle feeds back the result of setting success or failure to the device.

[0209] 8. The call of other functions is triggered by user preset or device customized linkage scenes. A function call request is initiated to the vehicle according to the scene. The vehicle receives the request and executes the corresponding function call, and returns the execution result to the device, and the call is completed.

[0210] 9. Wait for the next user voice control or scene event trigger.

[0211] Reference Figure 4 , showing a schematic diagram of the structure of an access device for a vehicle-mounted device provided by an embodiment of the present invention, the device comprising:

[0212] An acquisition module 201 is used to acquire any vehicle-mounted device developed according to a development specification; the development specification is acquired by the vehicle-mounted device manufacturing platform from an open platform, and the open platform is used to acquire the development specification and device interface description file template uploaded by the original device manufacturing platform;

[0213] The access authentication module 202 is used to connect the vehicle-mounted device to the vehicle, and the vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and performs access and authentication of the vehicle-mounted device based on the basic information; the device description file includes the basic information of the vehicle-mounted device and the functions that the vehicle-mounted device needs to support;

[0214] The function discovery module 203 is used for, if the access and authentication of the vehicle-mounted device are completed, the vehicle receives the function discovery request of the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device;

[0215] The function calling module 204 is used for the vehicle to receive a function calling request sent by the vehicle-mounted device according to the comparison result, and execute a corresponding function according to the function calling request.

[0216] In an optional embodiment of the present invention, the development specification includes an interface specification; the device further includes:

[0217] a standard application programming interface determination module, configured to determine a standard application programming interface to be deployed to the vehicle according to the interface specification;

[0218] A communication module is used for communication between the vehicle and the on-board device via the standard application programming interface.

[0219] In an optional embodiment of the present invention, the device description file also includes connection information of the vehicle-mounted device; the access authentication module 202 includes:

[0220] A detection module, used for the vehicle to detect the access of the vehicle-mounted device through a power interface;

[0221] A first power supply module, used for the vehicle to provide power to the vehicle-mounted device for access and authentication;

[0222] A first sending module, configured for the vehicle to send a request to read the device description file to the vehicle-mounted device through a standard application programming interface;

[0223] A first receiving module, configured for the vehicle to receive and parse the device description file returned by the vehicle-mounted device to obtain basic information and connection information of the vehicle-mounted device;

[0224] The first access authentication module is used for the vehicle to access and authenticate the on-board device according to the basic information and the connection information.

[0225] In an optional embodiment of the present invention, before the first access authentication module, the method further includes:

[0226] A second power supply module, used for the vehicle to supply power to the on-board device for a preset period according to the power supply requirement of the on-board device in the basic information;

[0227] A first judgment module, configured to stop power supply if the vehicle fails to complete access and authentication of the vehicle-mounted device within a preset period;

[0228] The second judgment module is used to continue supplying power if the vehicle completes access and authentication of the on-board device within a preset period.

[0229] In an optional embodiment of the present invention, the function discovery module 203 includes:

[0230] A second receiving module, configured for the vehicle to receive a function discovery request sent by the vehicle-mounted device via a standard application programming interface;

[0231] A query and comparison module, configured for the vehicle to query the functions required to be supported by the vehicle by the on-board device in the device description file according to the function discovery request, and compare the functions with the functions provided by the vehicle;

[0232] The second sending module is used for the vehicle to generate a comparison result and send it to the vehicle-mounted device through the standard application programming interface.

[0233] In an optional embodiment of the present invention, the function calling module 204 includes:

[0234] A third receiving module is used for the vehicle to receive a function call request of the vehicle-mounted device through a standard application programming interface; the function call request is a function specifically provided by the vehicle confirmed by the vehicle-mounted device according to the comparison result;

[0235] An execution module is used for the vehicle to execute a corresponding function according to the function call request.

[0236] In an optional embodiment of the present invention, the device further includes:

[0237] A fourth receiving module, used for the vehicle to receive a custom command set by the vehicle-mounted device;

[0238] An identification module, used for the vehicle to identify the custom command issued by the user;

[0239] A third sending module is used for the vehicle to send the identified custom command to the vehicle-mounted device; the vehicle-mounted device is used to execute a corresponding function according to the custom command;

[0240] A response module is used for the vehicle to receive a response indicating that the vehicle-mounted device has successfully executed.

[0241] In an embodiment of the present invention, the vehicle-mounted device is connected to the vehicle by acquiring any vehicle-mounted device developed in accordance with the development specifications. The vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information. The device description file includes the basic information of the vehicle-mounted device and the functions of the vehicle-mounted device that the vehicle needs to support. If the access and authentication of the vehicle-mounted device are completed, the vehicle receives a function discovery request from the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file that the vehicle needs to support with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device. The vehicle receives a function call request issued by the vehicle-mounted device based on the comparison result, and executes the corresponding function according to the function call request. Therefore, the embodiments of the present invention use unified device description files and development specifications, so that cars of different brands and models can be compatible with various smart hardware, thereby solving the problem of protocol inconsistency. Users can also choose and access different smart hardware according to their own needs to achieve a personalized driving experience without being restricted by the vehicle's pre-installed solution. Standardized development specifications and device description files simplify the manufacturer's development process and reduce the development cost and time for adapting to different vehicles. In addition, the device can automatically discover and call the vehicle's functions to achieve more intelligent and automated operations, such as automatically adjusting the in-vehicle environment to suit the user's preferences. At the same time, the smart hardware can automatically adjust its functions according to the function list provided by the vehicle to adapt to different environments and conditions, thereby improving the adaptability and flexibility of the device.

[0242] An embodiment of the present invention further provides a vehicle, comprising a processor, a memory, and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the access method of the vehicle-mounted device as described above is implemented.

[0243] An embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, the access method of the vehicle-mounted device as described above is implemented.

[0244] As for the device embodiment, since it is basically similar to the method embodiment, the description is relatively simple, and the relevant parts can be referred to the partial description of the method embodiment.

[0245] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of the relevant countries and regions, and provide corresponding operation entrances for users to choose to authorize or refuse.

[0246] The various embodiments in this specification are described in a progressive manner, and each embodiment focuses on the differences from other embodiments. The same or similar parts between the various embodiments can be referenced to each other.

[0247] Those skilled in the art will appreciate that the embodiments of the present invention may be provided as methods, devices, or computer program products. Therefore, the embodiments of the present invention may take the form of a complete hardware embodiment, a complete software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of the present invention may take the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes.

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

[0249] These computer program instructions may also be stored in a computer-readable memory capable of directing a computer or other programmable data processing terminal device to operate in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product including an instruction device, which implements the process Figure 1 A process or multiple processes and / or boxes Figure 1 A function specified in one or more boxes.

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

[0251] Although the preferred embodiments of the present invention have been described, those skilled in the art may make additional changes and modifications to these embodiments once they have learned the basic creative concept. Therefore, the appended claims are intended to be interpreted as including the preferred embodiments and all changes and modifications that fall within the scope of the embodiments of the present invention.

[0252] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or terminal device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or terminal device. In the absence of further restrictions, the elements defined by the sentence "including one..." do not exclude the existence of other identical elements in the process, method, article or terminal device including the above elements.

[0253] The access method, device, vehicle and medium of the provided vehicle-mounted equipment are introduced in detail above. Specific examples are used in this article to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core idea; at the same time, for general technical personnel in this field, according to the idea of ​​the present invention, there will be changes in the specific implementation method and application scope. In summary, the content of this specification should not be understood as a limitation on the present invention.

Claims

1. A method for accessing a vehicle-mounted device, characterized in that: The method comprises: Obtain any vehicle-mounted device developed according to the development specification; the development specification is obtained from the open platform through the vehicle-mounted device manufacturing platform, and the open platform is used to obtain the development specification and device interface description file template uploaded by the original device manufacturing platform; The vehicle-mounted device is connected to the vehicle, and the vehicle confirms basic information of the vehicle-mounted device according to a device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information; the device description file includes basic information of the vehicle-mounted device and functions of the vehicle-mounted device that the vehicle needs to support; If the access and authentication of the vehicle-mounted device are completed, the vehicle receives the function discovery request of the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device; The vehicle receives a function call request issued by the on-board device according to the comparison result, and executes a corresponding function according to the function call request.

2. The method according to claim 1, characterized in that: The development specification includes an interface specification; the method further includes: determining a standard application programming interface to be deployed to the vehicle based on the interface specification; The vehicle communicates with the on-board device via the standard application programming interface.

3. The method according to claim 1 or 2, characterized in that: The device description file also includes connection information of the vehicle-mounted device; The vehicle-mounted device is connected to the vehicle, the vehicle confirms basic information of the vehicle-mounted device according to a device description file of the vehicle-mounted device, and accesses and authenticates the vehicle-mounted device based on the basic information, including: The vehicle detects access to the vehicle-mounted device via a power interface; The vehicle provides power to the on-board device for access and authentication; The vehicle sends a request to read the device description file to the on-board device through a standard application programming interface; The vehicle receives and parses the device description file returned by the vehicle-mounted device to obtain basic information and connection information of the vehicle-mounted device; The vehicle accesses and authenticates the on-board device according to the basic information and the connection information.

4. The method according to claim 3, characterized in that Before the vehicle accesses and authenticates the on-board device according to the basic information and the connection information, the method further includes: The vehicle supplies power to the on-board device for a preset period according to the power supply requirement of the on-board device in the basic information; If the vehicle fails to complete the access and authentication of the on-board device within a preset period, the power supply is stopped; If the vehicle completes the access and authentication of the on-board device within a preset period, power supply continues.

5. The method according to claim 1 or 2, characterized in that: If the access and authentication of the vehicle-mounted device are completed, the vehicle receives the function discovery request of the vehicle-mounted device, compares the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generates a comparison result and sends it to the vehicle-mounted device, including: The vehicle receives a function discovery request sent by the on-board device through a standard application programming interface; The vehicle queries the device description file for the functions that the vehicle needs to support according to the function discovery request, and compares the functions with the functions provided by the vehicle; The vehicle generates a comparison result and sends it to the vehicle-mounted device through the standard application programming interface.

6. The method according to claim 1, characterized in that The vehicle receives a function call request sent by the vehicle-mounted device according to the comparison result, and executes a corresponding function according to the function call request, including: The vehicle receives a function call request from the vehicle-mounted device through a standard application programming interface; the function call request is a function specifically provided by the vehicle confirmed by the vehicle-mounted device according to the comparison result; The vehicle executes a corresponding function according to the function call request.

7. The method according to claim 1, characterized in that The method further comprises: The vehicle receives a custom command set by the vehicle-mounted device; The vehicle recognizes the custom command issued by the user; The vehicle sends the identified custom command to the vehicle-mounted device; the vehicle-mounted device is used to execute a corresponding function according to the custom command; The vehicle receives a response indicating that the in-vehicle device has been successfully executed.

8. An access device for a vehicle-mounted device, characterized in that: The device comprises: An acquisition module, used to acquire any vehicle-mounted device developed according to a development specification; the development specification is acquired from an open platform by the vehicle-mounted device manufacturing platform, and the open platform is used to acquire the development specification and device interface description file template uploaded by the original device manufacturing platform; An access authentication module, used to connect the vehicle-mounted device to the vehicle, the vehicle confirms the basic information of the vehicle-mounted device according to the device description file of the vehicle-mounted device, and performs access and authentication of the vehicle-mounted device based on the basic information; the device description file includes the basic information of the vehicle-mounted device and the functions that the vehicle-mounted device needs to support from the vehicle; A function discovery module, configured to, if the access and authentication of the vehicle-mounted device are completed, cause the vehicle to receive a function discovery request of the vehicle-mounted device, compare the functions that the vehicle-mounted device in the device description file needs to be supported by the vehicle with the functions provided by the vehicle, generate a comparison result and send it to the vehicle-mounted device; The function calling module is used for the vehicle to receive a function calling request issued by the vehicle-mounted device according to the comparison result, and execute a corresponding function according to the function calling request.

9. A vehicle, characterized in that: The invention comprises a processor, a memory and a computer program stored in the memory and capable of running on the processor, wherein when the computer program is executed by the processor, the access method of the vehicle-mounted device as claimed in any one of claims 1 to 7 is implemented.

10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the access method for the vehicle-mounted device according to any one of claims 1 to 7 is implemented.

Images