Method and apparatus for controlling peripheral device of head unit, and vehicle, system and storage medium

Abstract

Provided in the embodiments of the present application are a method and apparatus for controlling a peripheral device of a head unit, and a vehicle, a system and a storage medium. The method comprises: in response to a user operation, acquiring information of a peripheral device to be added; on the basis of the information of said peripheral device, sending network configuration information to the said peripheral device; on the basis of the information of said peripheral device, sending peripheral device binding request information to an IoT platform; and on the basis of an update of an H5 control page of the IoT platform, completing peripheral device addition. In the method, by means of integrating an IoT SDK and a Wi-Fi networking function into a derivative device, the derivative device is directly connected to an IoT backend; the IoT SDK is also integrated into a connected head unit terminal, such that a connected head unit is in communication with the derivative device; in addition, an H5 webpage is used in an HMI interface of the head unit terminal, such that when a new device is to be added and a control function is operated to add a new device, only the H5 page and the IoT backend need to be modified, and it is not necessary to update connected head unit software. Moreover, each device can independently access an IoT platform by means of Wi-Fi, and thus the number of devices accessing the IoT platform is not limited by interface resources of the connected heat unit.

Description

Control method and device for vehicle peripherals, vehicle, system and storage medium Technical Field

[0001] The present application relates to the field of intelligent network technology, and in particular to a control method and device for vehicle peripherals, a vehicle, a system and a storage medium. Background Art

[0002] With the continuous development of vehicles, the functions provided by the vehicle side are also increasing, and the corresponding vehicle-mounted peripheral derivatives (referred to as peripherals) are increasing. As shown in Figure 1, the vehicle side generally uses the networked car machine 20 as the main node, and peripherals (including USB peripherals 30 or Bluetooth peripherals 30) can be connected to the vehicle multimedia through USB serial ports, Bluetooth, WIFI and other protocols, so that users can control the connected peripherals through the networked car machine. On the basis of the above architecture, if a new type of peripheral is to be added, the networked car machine needs to adapt to the new control signal and complete the development of the HMI interactive interface and control logic, that is, the networked car machine software needs to be upgraded to access the new device, and even if the upgrade is completed, the USB port and Bluetooth channel of the networked car machine are limited, which will greatly affect the number of peripherals connected, thereby affecting the user experience.

[0003] Application Contents

[0004] The present application provides a method and device for controlling vehicle-mounted peripherals, as well as a vehicle, system, and storage medium. This method integrates an IoT SDK and Wi-Fi networking capabilities through a derivative device, allowing direct connection to the IoT backend. The connected vehicle-mounted terminal also integrates the IoT SDK, enabling connectivity between the connected vehicle-mounted terminal and the derivative device. Furthermore, the vehicle-mounted terminal's HMI interactive interface utilizes an HTML5 webpage to enable the addition of new devices and operational control functions. Adding a new device requires modifying only the HTML5 page and the IoT backend, without requiring updates to the connected vehicle-mounted terminal software. Furthermore, each device can independently access the IoT platform via Wi-Fi, and the number of connected devices is not limited by the connected vehicle-mounted terminal's interface resources.

[0005] In a first aspect, embodiments of the present application provide a method for controlling vehicle-mounted peripherals, applicable to a vehicle-mounted computer. The method comprises: obtaining information about a to-be-added peripheral in response to a user operation; sending network configuration information to the to-be-added peripheral based on the to-be-added peripheral information; sending a peripheral binding request to an IoT platform based on the to-be-added peripheral information; and completing the peripheral addition based on an update of an H5 control page on the IoT platform. This method allows each peripheral to independently connect to the IoT platform via Wi-Fi, and the number of connected devices is not limited by the networked vehicle-mounted computer interface resources.

[0006] In one possible implementation, the information of the peripheral device to be added includes the device ID of the peripheral device to be added; and sending the network configuration information to the peripheral device to be added based on the information of the peripheral device to be added includes: sending the vehicle-mounted WiFi hotspot information of the vehicle computer to the peripheral device to be added based on the device ID of the peripheral device to be added, so that the peripheral device to be added connects to the WiFi hotspot of the vehicle computer based on the vehicle-mounted WiFi hotspot information to complete the network connection configuration.

[0007] In one possible implementation, after the added peripheral connects to the vehicle's WiFi hotspot based on the vehicle-mounted WiFi hotspot information and completes the network connection configuration, the peripheral to be added is wirelessly connected to the IoT platform based on its own integrated IoT SDK and wireless network function.

[0008] In one possible implementation, the information of the peripheral to be added includes the device ID of the peripheral to be added; the vehicle computer sends the peripheral binding request information to the IoT platform based on the information of the peripheral to be added, including: sending the device ID of the peripheral to be added and the vehicle VIN of the vehicle to be added to the IoT platform, so that the IoT platform saves the associated information of the peripheral to be added to the database of the IoT platform based on the device ID of the peripheral to be added and the vehicle VIN of the vehicle.

[0009] In one possible implementation, based on the update of the H5 control page of the IoT platform, completing the peripheral addition includes: when it is confirmed that the IoT platform has completed the binding of the peripheral and the vehicle and completed the update of the H5 control page, completing the addition of the new peripheral.

[0010] In one possible implementation, after completing the peripheral addition by updating the H5 control page based on the IoT platform, it also includes: sending control instructions to the target peripheral through the IoT platform in response to user operations; and displaying the control interface of the target peripheral on the vehicle display screen based on the execution results and status information reported by the target peripheral.

[0011] In one possible implementation, the sending of control instructions to the target peripheral device through the IoT platform in response to user operation includes: displaying the control interface of the target peripheral device on the vehicle display screen in response to the user clicking the corresponding icon of the target peripheral device on the H5 control page displayed on the vehicle display screen; sending peripheral control information to the IoT platform in response to the user clicking the target control on the control interface of the target peripheral device, and controlling the IoT platform to send control instructions to the target peripheral device based on the peripheral control information; wherein, the peripheral control information includes the vehicle VIN, user ID, the device ID of the target peripheral device, and control information.

[0012] In one possible implementation, displaying the control interface of the target peripheral on the vehicle display screen based on the execution result and status information reported by the target peripheral includes: obtaining the execution result and status information of the target peripheral fed back by the IoT platform; and updating the execution status of the target peripheral in the control interface of the target peripheral based on the execution result and status information of the target peripheral; wherein the execution status of the target peripheral includes: the working mode and consumables information of the target peripheral.

[0013] In a second aspect, an embodiment of the present application further provides a method for controlling a vehicle peripheral device, which is applied to a mobile terminal and includes:

[0014] In a third aspect, an embodiment of the present application further provides a control device for a vehicle peripheral device, comprising a processor and a memory, wherein the memory is used to store at least one instruction, and when the instruction is loaded and executed by the processor, the control method for the vehicle peripheral device provided in the first aspect and / or the second aspect is implemented.

[0015] In a fourth aspect, an embodiment of the present application further provides a vehicle, the vehicle including the control device for the vehicle peripheral device provided in the third aspect. In one embodiment, the vehicle computer of the vehicle includes the control device for the vehicle peripheral device.

[0016] In a fifth aspect, an embodiment of the present application further provides a mobile terminal, which includes the control device for the vehicle peripheral device provided in the third aspect.

[0017] In a sixth aspect, an embodiment of the present application further provides a vehicle-connected system, comprising a user terminal, a vehicle computer, an IoT platform, and an external derivative device (peripheral). The user terminal may be the mobile terminal provided in the fifth aspect. Both the user terminal and the vehicle computer include the control device for the vehicle computer peripheral provided in the third aspect.

[0018] In the seventh aspect, an embodiment of the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the control method of the vehicle peripheral device provided in the first aspect and / or the second aspect is implemented.

[0019] In an eighth aspect, an embodiment of the present application further provides a computer program product, comprising a computer program or instructions, which, when executed by a processor, implements the control method of the vehicle peripherals provided in the first aspect and / or the second aspect. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, a brief introduction will be given below to the drawings required for use in the embodiments or the description of the prior art. Obviously, the drawings described below are some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.

[0021] FIG1 is a schematic diagram of a vehicle multimedia system connected to peripherals in the related art;

[0022] FIG2 is a schematic diagram of a vehicle peripheral control system architecture provided by one embodiment of the present application;

[0023] FIG3 is a flow chart of a method for controlling a vehicle peripheral device according to an embodiment of the present application;

[0024] FIG4 is a flow chart of a method for controlling a vehicle peripheral device according to another embodiment of the present application;

[0025] FIG5 is a flow chart of a method for controlling a vehicle peripheral device according to another embodiment of the present application;

[0026] FIG6 is a schematic structural diagram of a control device for a vehicle peripheral device according to an embodiment of the present application. DETAILED DESCRIPTION

[0027] To make the purpose, technical solutions, and advantages of the embodiments of this application more clear, the technical solutions in the embodiments of this application will be clearly and completely described below in conjunction with the drawings in the embodiments of this application. Obviously, the described embodiments are part of the embodiments of this application, not all of the embodiments. Based on the embodiments in this application, all other embodiments obtained by ordinary technicians in this field without making creative efforts are within the scope of protection of this application.

[0028] An embodiment of the present application provides a method for controlling vehicle computer peripherals. Through this method, when a new peripheral type is added to the vehicle computer, the peripheral can be connected to the network and establish a connection with the IoT platform, so that it can receive control instructions sent by the networked vehicle computer through the IoT platform and complete the connection and interaction with the networked vehicle computer. That is, as the number of peripheral types increases, the workload of research and development work on related protocols, signal processing, logic control, and interactive interfaces for the networked vehicle computer is reduced, and this connection method can increase the number of peripherals connected to the vehicle computer.

[0029] In order to implement the above-mentioned control method of vehicle peripherals, an embodiment of the present application also provides a vehicle peripheral control system. Figure 2 is a schematic diagram of the vehicle peripheral control system architecture provided by an embodiment of the present application. As shown in Figure 2, the system may include a user terminal 10, a vehicle 20, an IoT platform, and an external derivative device (peripheral) 30. Among them, the user terminal 10 is connected to the IoT platform for mobile communication, wherein an on-board IoT APP is installed in the vehicle 20, and the vehicle 20 can be a networked vehicle. In one embodiment, a mobile communication module is configured in the vehicle 20. Such as a 4G module or a 5G module, after the vehicle 20 starts the on-board IoT APP, it can connect and interact with the user terminal 10.

[0030] In some embodiments, the vehicle computer 20 is also configured with a vehicle-mounted wireless module, exemplarily, a vehicle-mounted WiFi hotspot module, so that the peripheral device 30 can connect to and interact with the vehicle computer by connecting to the WiFi hotspot of the vehicle computer 20.

[0031] In some embodiments, the peripheral device 30 has the function of independently connecting to WiFi to access the Internet, and the peripheral device 30 is also integrated with an IoT SDK. The peripheral device 30 achieves network connection by connecting to the WiFi hotspot of the vehicle computer 20, and then the peripheral device 30 can establish a connection with the IoT platform through the network connection, that is, after the vehicle computer 20 starts the on-board IoT APP, it can send control instructions or other information to the peripheral device through the IoT platform.

[0032] In some embodiments, the front-end interactive interface of the vehicle-mounted IoT app of the vehicle computer 20 uses an H5 page. After the vehicle-mounted IoT app is launched, the H5 page is displayed on the display screen of the vehicle computer 20. In response to user operations on the display screen interface, the corresponding information is sent to the IoT platform via the H5 protocol. The IoT platform then sends the corresponding control instructions to the peripheral device 30 through the IoT SDK of the peripheral device 30.

[0033] In some embodiments, there is a binding relationship between the user terminal 10, the vehicle computer 20 and the peripheral device 30. In one embodiment, the account of the user terminal 10 (such as user ID), the device number (device ID) of the vehicle computer 20 and the user account (such as user ID), the vehicle identification number (VIN) and the device number (device ID) of the peripheral device 30 are associated, so that the IoT platform can accurately send the corresponding control instructions to the designated peripheral device after some logical processing. For easy identification, the above-mentioned user ID can be the same ID.

[0034] The following is a detailed description of the relevant technical solutions for adding new peripherals to the car computer.

[0035] FIG3 is a flow chart of a method for controlling a vehicle peripheral device according to an embodiment of the present application.

[0036] 3 , the method may include the following steps:

[0037] S301: In response to a user operation, the vehicle computer obtains information about the peripheral device to be added.

[0038] In some embodiments, when a user wants to add a new peripheral, he or she can perform the adding operation on the interactive interface of the car display screen. Specifically, the user can click to start the IoT APP on the car computer. After the IoT APP is started, the car computer sends an H5 control page request information to the IoT platform through the network, and the IoT platform sends the control page based on the request of the car computer. Then, the user can click the virtual button of "Add Peripheral" on the interactive interface of the car computer display screen to trigger the car computer to enter the peripheral adding process.

[0039] In some embodiments, both the vehicle computer and the peripheral device to be added are equipped with Bluetooth modules, i.e., have Bluetooth functionality. After entering the peripheral addition process, the vehicle computer can search for addable devices via Bluetooth. The vehicle computer display can display a list of addable devices to the user. In response to the user's operation, the vehicle computer determines the device selected by the user in the add device list and obtains information about the peripheral device to be added, illustratively, the device ID of the peripheral to be added.

[0040] S302: The vehicle computer sends network configuration information to the peripheral device to be added based on the information of the peripheral device to be added.

[0041] In some embodiments, after the vehicle computer enters the peripheral addition process, the vehicle computer may send network configuration information to the peripheral to be added, so that the peripheral to be added completes network configuration based on the received network configuration information. In one embodiment, the network configuration information may include the vehicle computer's onboard WiFi hotspot information. The peripheral to be added may connect to the vehicle computer's WiFi hotspot based on the onboard WiFi hotspot information sent by the vehicle computer to complete the network connection configuration, that is, complete the network configuration between the peripheral to be added and the vehicle computer.

[0042] In some embodiments, after the peripheral device to be added completes the network configuration, it can establish a connection with the IoT platform based on the IoT SDK integrated within the peripheral device.

[0043] S303: The vehicle computer sends a peripheral binding request message to the IoT platform based on the information of the peripheral to be added.

[0044] In some embodiments, after obtaining the device ID of the peripheral to be added, the vehicle computer may send a peripheral binding request message to the IoT platform. The peripheral binding request message may include the device ID of the peripheral to be added and the vehicle VIN of the vehicle in which the vehicle computer is located. After receiving the peripheral binding request message from the vehicle computer, the IoT platform triggers the peripheral and vehicle binding process. During this binding process, the IoT platform may associate the added peripheral based on the device ID and vehicle VIN, and save the corresponding association information to the IoT platform database, thus completing the peripheral and vehicle binding process.

[0045] In some embodiments, after completing the association between the peripheral device to be added and the vehicle, the IoT platform can also update the relevant information of the H5 control page based on the information of the peripheral device to be added (such as the device ID).

[0046] S304: Update the H5 control page based on the IoT platform and complete the addition of new peripherals to the vehicle IoT.

[0047] In some embodiments, after the IoT platform completes the binding of the peripherals to the vehicle and completes the update of the H5 control page, it implements the addition of the new peripherals. After the peripherals are added, the user can control the peripherals through the car computer. For example, if the new peripheral is a smart car fragrance, after the smart car fragrance is added, the car computer can add the icon of the smart car fragrance on the interface of the display screen. In response to the user clicking the icon of the smart car fragrance, the car computer can display the control page of the smart car fragrance, thereby responding to the user's operation on the control page of the smart car fragrance, controlling the smart car fragrance to perform corresponding actions, for example, controlling the smart car fragrance to enter or exit working mode.

[0048] Through the above-described embodiment, peripherals are directly connected to the IoT backend through the integration of the IoT SDK and Wi-Fi networking capabilities. The vehicle-side IoT SDK is also integrated, enabling connectivity between the vehicle and external devices. Furthermore, the vehicle-side HMI interactive interface utilizes an HTML5 webpage to enable the addition of new peripherals and operational control functions. Adding new peripherals requires only modifying the HTML page and the IoT backend, without requiring updates to the connected vehicle software. This significantly improves device access efficiency and reduces development costs. Each peripheral can independently access the IoT platform via Wi-Fi, and the number of connected peripherals is not limited by the connected vehicle interface resources.

[0049] The following describes in detail the relevant technical solutions for vehicle computer control peripherals with reference to the accompanying drawings.

[0050] FIG4 is a flow chart of a method for controlling a vehicle peripheral device according to another embodiment of the present application.

[0051] As shown in FIG4 , the process of the method may further include the following steps:

[0052] S401: In response to user operations, the vehicle computer sends control instructions to the target peripheral device through the IoT platform.

[0053] In some embodiments, when the vehicle computer is turned on and the IoT app is started, the vehicle computer requests an H5 control page from the IoT platform. The IoT platform then issues the control page based on the vehicle computer's request, so that the vehicle computer can display the H5 control page on the display screen. The H5 control page displayed on the vehicle computer's display screen can include corresponding icons for added peripherals. The user can then click the icon of the target peripheral in the H5 control page displayed on the vehicle computer's display screen to enter the control interface of the target peripheral. For example, when the user clicks the icon of a smart car fragrance on the H5 control page, the control interface of the smart car fragrance can be entered.

[0054] In some embodiments, a user can click a target control on the control interface of a target peripheral device on an H5 control page displayed on the vehicle's display screen to control the target peripheral device to perform a corresponding action. In response to the user clicking a target control on the control interface of the target peripheral device, the vehicle computer can send a corresponding control instruction to the target peripheral device via the IoT platform. In one embodiment, in response to the user clicking a target control on the control interface of the target peripheral device, the vehicle computer can send peripheral control information to the IoT platform, where the peripheral control information can include the vehicle's VIN, user ID, peripheral device ID, and control information. The IoT platform can generate a corresponding target peripheral control instruction based on the received peripheral control information and send the target peripheral control instruction to the target peripheral device via the network. For example, when a user clicks the "Turn on" control on the smart car fragrance control interface, the vehicle computer will send peripheral control information to the IoT platform, where the peripheral control information can include the vehicle's VIN, user ID, the device ID of the smart car fragrance device, and the "Turn on" control information. The IoT platform will then send the control instruction to turn on the smart car fragrance device via the network.

[0055] S402: The vehicle computer displays the control interface of the target peripheral device on the vehicle computer display screen based on the execution result and status information reported by the target peripheral device.

[0056] In some embodiments, after receiving the control instruction, the target peripheral device performs a corresponding action based on the control instruction. Furthermore, the target peripheral device can feed back the execution result and the status information of the target peripheral device to the vehicle computer through the IoT platform. Thus, the vehicle computer can display the corresponding data on the control interface of the target peripheral device based on the execution result and status information fed back by the target peripheral device. In one embodiment, after the target peripheral device performs the corresponding action based on the control instruction, the execution result and the status information of the target peripheral device can be sent to the IoT platform, and then the IoT platform updates the execution status of the target peripheral device in the vehicle computer H5 control page based on the received execution result and the status information of the target peripheral device, and sends the updated H5 control page to the vehicle computer of the target vehicle (the vehicle corresponding to the vehicle VIN), and then the vehicle computer displays the execution status of the target peripheral device based on the received updated H5 control page. The execution status of the target peripheral device may include the working mode and consumables information of the target peripheral device. For example, after receiving the "turn on" control command, the smart car fragrance enters the working mode and sends the execution result of "working" and the remaining fragrance information (such as 60% of the fragrance remaining or 800 hours of remaining fragrance time) to the IoT platform. The IoT platform then updates the execution status of the target peripheral in the car computer H5 control page based on the received execution result of "working" and the remaining fragrance information, and sends the updated H5 control page to the car computer of the target vehicle (the vehicle corresponding to the vehicle VIN). The car computer then displays the execution status of the smart car fragrance based on the received updated H5 control page. The execution status may include information that the smart car fragrance is "working" and the remaining fragrance time is 800 hours.

[0057] By integrating IoT SDK and Wi-Fi networking functions through derivative devices, it can be directly connected to the IoT backend; the IoT SDK is also integrated on the connected car machine to achieve connectivity between the connected car machine and derivative devices; at the same time, the HMI interactive interface on the car machine adopts H5 web pages to realize the addition of new devices and operation control functions. When adding new devices, only the H5 page and IoT backend need to be modified, and there is no need to update the connected car machine software, which greatly improves the efficiency of device access and reduces development costs.

[0058] The following describes in detail the relevant technical solutions for user terminal controlling peripherals with reference to the accompanying drawings.

[0059] FIG5 is a flowchart of a method for controlling a vehicle peripheral device according to another embodiment of the present application.

[0060] 5 , the process of the method may further include the following steps:

[0061] S501: In response to a user operation, the user terminal sends a control instruction to a target peripheral device via the IoT platform.

[0062] In some embodiments, when a user clicks to activate the smart IoT function of a user terminal, the user terminal requests an H5 control page from the IoT platform, and the IoT platform then issues the control page based on the user terminal's request, so that the user terminal can display the H5 control page on the display screen, wherein the H5 control page displayed on the user terminal display screen may include corresponding icons of added peripherals, and the user can click the icon of the target peripheral in the H5 control page displayed on the user terminal display screen to enter the control interface of the target peripheral. For example, when a user clicks the icon of a smart car fragrance in the H5 control page, the control interface of the smart car fragrance can be entered.

[0063] In some embodiments, a user can click a target control on the control interface of a target peripheral device on an H5 control page displayed on the user terminal's display screen to control the target peripheral device to perform a corresponding action. In response to the user clicking a target control on the control interface of the target peripheral device, the user terminal can send a corresponding control instruction to the target peripheral device via the IoT platform. In one embodiment, in response to the user clicking a target control on the control interface of the target peripheral device, the user terminal can send peripheral control information to the IoT platform, where the peripheral control information can include the vehicle VIN, user ID, peripheral device ID, and control information. The IoT platform can generate a corresponding target peripheral control instruction based on the received peripheral control information and send the target peripheral control instruction to the target peripheral device via the network. For example, after the user clicks the "Turn on" control on the smart car fragrance control interface, the user terminal will send the peripheral control information to the IoT platform, where the peripheral control information can include the vehicle VIN, user ID, device ID of the smart car fragrance, and "Turn on" control information. The IoT platform will then send the control instruction to turn on the smart car fragrance to the smart car fragrance via the network.

[0064] S502: The user terminal displays a control interface of the target peripheral device on a display screen of the user terminal based on the execution result and status information reported by the target peripheral device.

[0065] In some embodiments, after receiving the control instruction, the target peripheral device performs a corresponding action based on the control instruction. Furthermore, the target peripheral device can feed back the execution result and the status information of the target peripheral device to the user terminal through the IoT platform. Thus, the user terminal can display the corresponding data on the control interface of the target peripheral device based on the execution result and status information fed back by the target peripheral device. In one embodiment, after the target peripheral device performs the corresponding action based on the control instruction, the execution result and the status information of the target peripheral device can be sent to the IoT platform, and then the IoT platform updates the execution status of the target peripheral device in the H5 control page of the user terminal based on the received execution result and the status information of the target peripheral device, and sends the updated H5 control page to the user terminal, and then the user terminal displays the execution status of the target peripheral device based on the received updated H5 control page. For example, after receiving the "turn on" control command, the smart car fragrance enters the working mode, and sends the execution result of "working" and the remaining fragrance information (such as 60% of the fragrance remaining or 800 hours of remaining fragrance time) to the IoT platform. The IoT platform then updates the execution status of the target peripheral in the user terminal H5 control page based on the received execution result of "working" and the remaining fragrance information, and sends the updated H5 control page to the user terminal. The user terminal then displays the execution status of the smart car fragrance based on the received updated H5 control page. The execution status may include the information that the smart car fragrance is "working" and 60% of the fragrance remains.

[0066] In this solution, each device can independently access the IoT platform via Wi-Fi, and the number of connected devices is not limited by the resources of the connected vehicle interface. At the same time, derivative devices can be connected to home Wi-Fi as home devices, expanding the scope of use of derivative devices.

[0067] Based on the peripheral control method provided by the embodiments shown in Figures 4 and 5, in some embodiments, the in-vehicle APP or the APP on the mobile terminal can also be an enterprise APP, wherein the IoT function can be turned on in the enterprise APP, and the H5 page can be pulled and displayed. Then, the user can perform corresponding operations on the operation interface on the H5 page, and transmit it to the IoT background through the H5 protocol. The IoT background then sends the control instructions to the corresponding peripheral through the IoT SDK of the peripheral, thereby sending the control instructions to the target peripheral to achieve corresponding control.

[0068] In some embodiments, the binding relationship between the peripheral device, the vehicle, and the user is achieved through the peripheral device ID, the vehicle VIN, the connected vehicle device ID, and the user account user ID. The IoT platform can accurately send control commands to the designated peripheral device after some logical processing.

[0069] FIG6 is a schematic structural diagram of a control device for a vehicle peripheral device provided in one embodiment of the present application.

[0070] As shown in Figure 6, the device may include a processor 601 and a memory 602, and the memory 602 is used to store at least one instruction. When the instruction is loaded and executed by the processor 601, the control method of the vehicle peripheral device provided in any embodiment of the present application is implemented.

[0071] The embodiment of the present application further provides a vehicle, which includes the control device for the vehicle peripheral device provided in the embodiment shown in Figure 6. In one implementation, the vehicle computer of the vehicle includes the control device for the vehicle peripheral device.

[0072] An embodiment of the present application further provides a mobile terminal, which includes the control device for the vehicle peripheral device provided in the embodiment shown in FIG6 .

[0073] The present application also provides a vehicle-connected system, which includes a user terminal, a vehicle computer, an IoT platform, and an external derivative device (peripheral). The user terminal can be the mobile terminal described above. The user terminal and the vehicle computer both include a control device for the vehicle computer peripheral provided in the embodiment shown in FIG6 .

[0074] An embodiment of the present application also provides a computer-readable storage medium having a computer program stored thereon. When the computer program is executed by a processor, the control method of the vehicle peripheral device provided in any embodiment of the present application is implemented.

[0075] An embodiment of the present application also provides a computer program product, including a computer program or instructions, which, when executed by a processor, implements the control method of the vehicle peripheral device provided in any embodiment of the present application.

[0076] It is understandable that the application may be an application program (nativeApp) installed on the terminal, or may be a web page program (webApp) of a browser on the terminal, and this embodiment of the present application does not limit this.

[0077] Those skilled in the art will clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0078] In the several embodiments provided in this application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of the units is merely a logical function 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. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed may be an indirect coupling or communication connection through some interface, device or unit, which may be electrical, mechanical or other forms.

[0079] The units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.

[0080] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or in the form of hardware plus software functional units.

[0081] The above-mentioned integrated unit implemented in the form of a software functional unit can be stored in a computer-readable storage medium. The above-mentioned software functional unit is stored in a storage medium and includes a number of instructions for causing a computer device (which can be a personal computer, server, or network device, etc.) or a processor to perform some steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk, and other media that can store program code.

[0082] The above description is only a preferred embodiment of the present application and is not intended to limit the present application. Any modifications, equivalent replacements, improvements, etc. made within the spirit and principles of the present application shall be included in the scope of protection of the present application.

[0083] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present application, rather than to limit them. Although the present application has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that they can still modify the technical solutions described in the aforementioned embodiments, or make equivalent replacements for some or all of the technical features therein. These modifications or replacements do not deviate the essence of the corresponding technical solutions from the scope of the technical solutions of the embodiments of the present application.

Claims

1. A control method for a vehicle peripheral device, characterized in that: Applied to a vehicle computer, the method includes: In response to a user operation, obtaining information of a peripheral to be added; Based on the information of the peripheral device to be added, send the network configuration information to the peripheral device to be added; Based on the information of the peripheral to be added, send peripheral binding request information to the IoT platform; and Based on the update of the H5 control page of the IoT platform, the peripherals are added.

2. The method according to claim 1, characterized in that The information of the peripheral device to be added includes the device ID of the peripheral device to be added; The sending of network configuration information to the peripheral device to be added based on the information of the peripheral device to be added includes: Based on the device ID of the peripheral to be added, the vehicle-mounted WiFi hotspot information of the vehicle computer is sent to the peripheral to be added, so that the peripheral to be added is connected to the WiFi hotspot of the vehicle computer based on the vehicle-mounted WiFi hotspot information to complete the network connection configuration.

3. The method according to claim 2, characterized in that After the added peripheral is connected to the WiFi hotspot of the vehicle computer based on the vehicle-mounted WiFi hotspot information and the network connection configuration is completed, the peripheral to be added is wirelessly connected to the IoT platform based on its own integrated IoT SDK and wireless network function.

4. The method according to claim 1, characterized in that: The information of the peripheral device to be added includes the device ID of the peripheral device to be added; The vehicle computer sends peripheral binding request information to the IoT platform based on the peripheral information to be added, including: The device ID of the peripheral to be added and the vehicle VIN of the vehicle are sent to the IoT platform, so that the IoT platform saves the associated information of the peripheral to be added to the database of the IoT platform based on the device ID of the peripheral to be added and the vehicle VIN of the vehicle.

5. The method according to claim 1, characterized in that Based on the update of the H5 control page of the IoT platform, the peripheral addition is completed including: When it is confirmed that the IoT platform has completed the binding of the peripheral and the vehicle and completed the update of the H5 control page, the addition of the new peripheral is completed.

6. The method according to any one of claims 1 to 5, characterized in that: After the H5 control page based on the IoT platform is updated and the peripherals are added, it also includes: In response to a user operation, sending a control instruction to a target peripheral device through the IoT platform; and Based on the execution result and status information reported by the target peripheral device, a control interface of the target peripheral device is displayed on the vehicle display screen.

7. The method according to claim 6, characterized in that In response to the user operation, sending the control instruction to the target peripheral device through the IoT platform includes: In response to a user clicking an icon corresponding to a target peripheral device on an H5 control page displayed on a vehicle computer display screen, a control interface of the target peripheral device is displayed on the vehicle computer display screen; In response to a user clicking a target control on a control interface of a target peripheral, sending peripheral control information to an IoT platform, and controlling the IoT platform to send a control instruction to the target peripheral based on the peripheral control information; The peripheral control information includes the vehicle VIN, the user ID, the device ID of the target peripheral and the control information.

8. The method according to claim 6, characterized in that The displaying of the control interface of the target peripheral device on the vehicle display screen based on the execution result and status information reported by the target peripheral device includes: Obtaining the execution result and status information of the target peripheral device fed back by the IoT platform; and Based on the execution result and status information of the target peripheral device, updating the execution status of the target peripheral device in the control interface of the target peripheral device; The execution status of the target peripheral device includes: the working mode and consumables information of the target peripheral device.

9. A control device for a vehicle peripheral, characterized in that: The device comprises: A processor and a memory, wherein the memory is used to store at least one instruction, and when the instruction is loaded and executed by the processor, the control method of the vehicle peripheral device as described in any one of claims 1 to 8 is implemented.

10. A vehicle, characterized in that: The vehicle comprises the control device for vehicle peripherals according to claim 8.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the method for controlling a vehicle peripheral device as described in any one of claims 1 to 8 is implemented.

Images