Remote awakening method and device

Abstract

The invention discloses a remote wakeup method and device, which are applied to a target cloud platform, the target cloud platform is in communication connection with a vehicle-mounted gateway and a mobile terminal, the vehicle-mounted gateway comprises a vehicle-mounted communication and management TCAM controller and a digital cockpit host DHU, and the method comprises the following steps: receiving a remote wakeup instruction sent from the mobile terminal; and in response to the situation that the DHU is in a dormant state, sending the remote wake-up instruction to the TCAM controller so as to wake up the DHU by using the TCAM controller. According to the scheme, on the basis that the TCAM + DHU in the vehicle serves as the vehicle-mounted gateway, the remote wakeup instruction is transmitted to the TCAM controller through the target cloud platform, then the TCAM controller is used for waking up the DHU, and therefore the vehicle can be waken up conveniently and reliably.

Description

Technical Field

[0001] Embodiments of the present application relate to the field of vehicle technology, and more specifically, to a remote wake-up method and device. Background Art

[0002] At present, vehicles are developing towards networking, automation, sharing and electrification, all of which are pointing to intelligence. The driving force behind this is mainly from technological progress, the strengthening of environmental protection policies and consumers' demand for environmentally friendly and efficient energy.

[0003] In the related art, when the digital cockpit head unit (DHU) meets the sleep condition, it will enter the sleep state (that is, the vehicle will enter the sleep state), and then waking up the vehicle after the sleep state becomes important. Therefore, how to wake up the vehicle conveniently and reliably is a technical problem to be solved urgently. Summary of the invention

[0004] The embodiments of the present application provide a remote wake-up method and device. The following introduces various aspects involved in the embodiments of the present application.

[0005] In a first aspect, a remote wake-up method is provided, which is applied to a target cloud platform, wherein the target cloud platform is communicatively connected to a vehicle gateway and a mobile terminal, wherein the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, and the method includes: receiving a remote wake-up instruction sent from the mobile terminal; in response to the DHU being in a sleep state, sending the remote wake-up instruction to the TCAM controller to wake up the DHU using the TCAM controller.

[0006] As a possible implementation manner, the method further includes: receiving device status information of the DHU sent from the TCAM controller; and judging whether the DHU is in a sleep state according to the device status information of the DHU.

[0007] As a possible implementation method, the vehicle-mounted gateway is communicatively connected with the vehicle-domain IOT device, and the DHU is used to send connection parameters to the vehicle-domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; the vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

[0008] As a possible implementation method, the DHU is used to establish a target wireless communication connection with the vehicle-domain IOT device, receive device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, and send the connection parameters to the vehicle-domain IOT device through the target wireless communication connection, wherein the device parameters include the device identification of the vehicle-domain IOT device and the wireless fidelity Wi-Fi list supported by the vehicle-domain IOT device, and the Wi-Fi name is in the Wi-Fi list.

[0009] As a possible implementation manner, the DHU is further used to select the Wi-Fi name in the Wi-Fi list and enter the Wi-Fi password after receiving the device parameters sent by the vehicle-domain IOT device.

[0010] As a possible implementation manner, the vehicle-domain IOT device is used to receive the connection result of the Wi-Fi connection sent from the TCAM controller, and send the connection result to the DHU to instruct the DHU to perform the target operation.

[0011] As a possible implementation manner, the target wireless communication connection is a Bluetooth connection, an infrared connection, or a Zigbee connection.

[0012] As a possible implementation method, the vehicle-domain IOT device includes multiple IOT devices; the DHU is used to perform mesh networking for the multiple IOT devices; the TCAM controller is used to cache network connection parameters of the vehicle-domain IOT device, and the network connection parameters include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device.

[0013] In a second aspect, a remote wake-up method is provided, which is applied to a mobile terminal, wherein the mobile terminal includes a target application, and the mobile terminal is communicatively connected to a vehicle gateway through a target cloud platform. The vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU. The method includes: triggering a remote wake-up instruction in the target application; sending a remote wake-up instruction to the TCAM controller through the target cloud platform to wake up the DHU using the TCAM controller.

[0014] As a possible implementation manner, before triggering the remote wake-up instruction in the target application, the method also includes: receiving, through the target cloud platform, device status information of the DHU sent from the TCAM controller; judging whether the DHU is in a sleep state according to the device status information of the DHU; triggering the remote wake-up instruction in the target application includes: in response to the DHU being in a sleep state, triggering the remote wake-up instruction in the target application.

[0015] As a possible implementation method, the vehicle-mounted gateway is communicatively connected with the vehicle-domain IOT device, and the DHU is used to send connection parameters to the vehicle-domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; the vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

[0016] As a possible implementation method, the DHU is used to establish a target wireless communication connection with the vehicle-domain IOT device, receive device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, and send the connection parameters to the vehicle-domain IOT device through the target wireless communication connection, wherein the device parameters include the device identification of the vehicle-domain IOT device and the wireless fidelity Wi-Fi list supported by the vehicle-domain IOT device, and the Wi-Fi name is in the Wi-Fi list.

[0017] As a possible implementation manner, the DHU is further used to select the Wi-Fi name in the Wi-Fi list and enter the Wi-Fi password after receiving the device parameters sent by the vehicle-domain IOT device.

[0018] As a possible implementation manner, the vehicle-domain IOT device is used to receive the connection result of the Wi-Fi connection sent from the TCAM controller, and send the connection result to the DHU to instruct the DHU to perform the target operation.

[0019] As a possible implementation manner, the target wireless communication connection is a Bluetooth connection, an infrared connection, or a Zigbee connection.

[0020] As a possible implementation method, the vehicle-domain IOT device includes multiple IOT devices; the DHU is used to perform mesh networking for the multiple IOT devices; the TCAM controller is used to cache network connection parameters of the vehicle-domain IOT device, and the network connection parameters include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device.

[0021] In a third aspect, a remote wake-up device is provided, which is applied to a target cloud platform, wherein the target cloud platform is communicatively connected to a vehicle gateway and a mobile terminal, wherein the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, and the device includes: a receiving module for receiving a remote wake-up instruction sent from the mobile terminal; a first sending module for sending the remote wake-up instruction to the TCAM controller in response to the DHU being in a sleep state, so as to wake up the DHU using the TCAM controller.

[0022] In a fourth aspect, a remote wake-up device is proposed, which is applied to a mobile terminal, wherein the mobile terminal includes a target application, and the mobile terminal is communicatively connected to a vehicle gateway through a target cloud platform. The vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU. The device includes: a trigger module, which is used to trigger a remote wake-up instruction in the target application; a second sending module, which is used to send a remote wake-up instruction to the TCAM controller through the target cloud platform, so as to use the TCAM controller to wake up the DHU.

[0023] According to a fifth aspect, a computer-readable storage medium is provided, on which an executable code is stored. When the executable code is executed, the method described in the first aspect or the second aspect can be implemented.

[0024] The embodiment of the present application provides a remote wake-up method, which is applied to a target cloud platform, the target cloud platform is connected to a vehicle gateway and a mobile terminal, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, and the remote wake-up method includes: receiving a remote wake-up instruction sent from a mobile terminal; in response to the DHU being in a dormant state, sending a remote wake-up instruction to the TCAM controller to wake up the DHU using the TCAM controller. Based on the "TCAM+DHU" in the vehicle as the vehicle gateway, this solution transmits a remote wake-up instruction to the TCAM controller through the target cloud platform, and then uses the TCAM controller to wake up the DHU, so that the vehicle can be woken up conveniently and reliably. BRIEF DESCRIPTION OF THE DRAWINGS

[0025] Figure 1 It is a flowchart of a remote wake-up method provided in an embodiment of the present application.

[0026] Figure 2 It is a schematic diagram of a communication system provided by an embodiment of the present application.

[0027] Figure 3 This is a flow chart of a method for establishing a vehicle domain IOT device connection provided by an embodiment of the present application.

[0028] Figure 4It is a schematic diagram of the structure of a remote wake-up device provided in one embodiment of the present application.

[0029] Figure 5 It is a structural diagram of a remote wake-up device provided in another embodiment of the present application.

[0030] Figure 6 It is a structural diagram of a communication device provided in one embodiment of the present application. DETAILED DESCRIPTION

[0031] In order to enable those skilled in the art to better understand the present application, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only embodiments of a part of the present application, not all embodiments. All other embodiments obtained by ordinary technicians in this field based on the embodiments of the present application should fall within the scope of protection of the present application.

[0032] Reference to "embodiments" herein means that a particular feature, structure, or characteristic described in conjunction with the embodiments may be included in at least one embodiment of the present application. The appearance of the phrase in various locations in the specification does not necessarily refer to the same embodiment, nor is it an independent or alternative embodiment that is mutually exclusive with other embodiments. It is explicitly and implicitly understood by those skilled in the art that the embodiments described herein may be combined with other embodiments.

[0033] In the description of the present application, it should be noted that the terms "center", "upper", "lower", "left", "right", "vertical", "horizontal", "inside", "outside" and the like indicate positions or positional relationships based on the positions or positional relationships shown in the accompanying drawings, and are only for the convenience of describing the present invention and simplifying the description, and do not indicate or imply that the device or element referred to must have a specific orientation, be constructed and operated in a specific orientation, and therefore cannot be understood as a limitation on the present invention; the terms "first", "second", and "third" are only used for descriptive purposes and cannot be understood as indicating or implying relative importance; in addition, unless otherwise clearly specified and limited, the terms "installed", "connected", and "connected" should be understood in a broad sense, for example, it can be a fixed connection or a detachable connection; it can be directly connected or indirectly connected through an intermediate medium, and it can be the internal connection of two elements. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0034] At present, vehicles are developing towards networking, automation, sharing and electrification, all of which are pointing to intelligence. The driving force behind this is mainly from technological progress, the strengthening of environmental protection policies and consumers' demand for environmentally friendly and efficient energy.

[0035] In the related art, when the DHU meets the sleep condition, it will enter the sleep state (that is, the vehicle will enter the sleep state), and then waking up the vehicle after the sleep state becomes important. Therefore, how to wake up the vehicle conveniently and reliably is a technical problem to be solved urgently.

[0036] In view of the above problems, an embodiment of the present application provides a remote wake-up method, which is applied to a target cloud platform, the target cloud platform is connected to a vehicle gateway and a mobile terminal, the vehicle gateway includes a vehicle communication and management (telematics control and management, TCAM) controller and a DHU, and the remote wake-up method includes: receiving a remote wake-up instruction sent from a mobile terminal; in response to the DHU being in a dormant state, sending a remote wake-up instruction to the TCAM controller to wake up the DHU using the TCAM controller. Based on the "TCAM+DHU" in the vehicle as the vehicle gateway, this solution transmits the remote wake-up instruction to the TCAM controller through the target cloud platform, and then uses the TCAM controller to wake up the DHU, so as to wake up the vehicle conveniently and reliably.

[0037] Figure 1 A flowchart of a remote wake-up method provided in an embodiment of the present application. Figure 1 The method is described from the perspective of the interaction between the target cloud platform and the mobile terminal. Figure 1 The method shown can be applied to a target cloud platform or to a mobile terminal.

[0038] In the embodiment of the present application, the target cloud platform is a cloud platform maintained by the manufacturer of the vehicle. In some implementations, the target cloud platform may also be referred to as a telematics service provider (TSP) cloud platform.

[0039] In the embodiment of the present application, the mobile terminal may refer to a terminal device outside the vehicle, and the mobile terminal may be, for example, a mobile phone, a tablet computer (Pad), a laptop computer, a PDA, etc., and the present application does not impose any specific restrictions on this.

[0040] In the embodiment of the present application, the target cloud platform is connected to the vehicle gateway in communication, the target cloud platform is connected to the mobile terminal in communication, and the vehicle gateway includes a TCAM controller and a DHU. It should be understood that the vehicle gateway in the embodiment of the present application can be a gateway formed by a combination of a TCAM controller and a DHU (TCAM+DHU). The TCAM controller can also be referred to as TCAM.

[0041] In some implementations, the TCAM controller is communicatively connected to the DHU. For example, the TCAM controller and the DHU may be communicatively connected via a controller area network (CAN) protocol or an Ethernet protocol. This application does not impose any specific limitation on this.

[0042] In some implementations, the vehicle-mounted gateway in this application can be connected to the vehicle-domain IOT device. Among them, the vehicle-domain IOT device can refer to an IOT device that can use sensors, network connections and data processing technologies to improve the safety, comfort, efficiency and other user experience of the vehicle. The vehicle-domain IOT device may include an IOT device installed in and / or near the vehicle, and the vehicle-domain IOT device includes but is not limited to: vehicle-mounted intelligent air-conditioning system, vehicle-domain multi-functional camping light, smart seat, smart multimedia player, smart key, smart vehicle refrigerator, etc.

[0043] Figure 1 The method shown includes steps S120 to S140.

[0044] In step 120: a remote wake-up instruction sent from a mobile terminal is received, wherein the remote wake-up instruction can be used to remotely wake up a DHU in a vehicle.

[0045] In some implementations, a target application is configured on the mobile terminal, and the target application may refer to an application for waking up the vehicle. The user may remotely wake up the DHU through the target application. It should be understood that the vehicle and the DHU may be pre-bound in the target application, for example, the vehicle identification number (VIN) of the vehicle may be used for vehicle binding in the target application, and the device identification of the DHU may be used for DHU binding.

[0046] The user can trigger a remote wake-up instruction in the target application, and then the mobile terminal sends the remote wake-up instruction to the target cloud platform. Then, the target cloud platform can send the remote wake-up instruction to the TCAM controller.

[0047] In step 140 : in response to the DHU being in the sleep state, a remote wake-up instruction is sent to the TCAM controller to wake up the DHU using the TCAM controller. It should be understood that the DHU is a host controller of the vehicle, and the DHU needs to be woken up before waking up the vehicle.

[0048] In some implementations, before sending the remote wake-up instruction to the TCAM controller, the method further includes: determining a state of the DHU.

[0049] In the embodiment of the present application, the status of the DHU may be determined by the mobile terminal or by the target cloud platform, and the present application does not impose any specific restrictions on this.

[0050] As an example, before triggering a remote wake-up instruction in a target application, the mobile terminal may receive the device status information of the DHU sent from the TCAM controller through the target cloud platform; then, based on the device status information of the DHU, determine whether the DHU is in a dormant state. The device status information of the DHU may be used to indicate whether the DHU is in a dormant state or an activated state (i.e., a running state).

[0051] As another example, the target cloud platform may be used to receive the device status information of the DHU sent from the TCAM controller, and then determine whether the DHU is in a dormant state according to the device status information of the DHU. The device status information of the DHU may be used to indicate whether the DHU is in a dormant state or an activated state (i.e., a running state).

[0052] It should be noted that the above remote wake-up method is mainly implemented based on the communication architecture of "TCAM+DHU" as the gateway. The communication architecture of "TCAM+DHU" as the gateway is described in detail below.

[0053] In an embodiment of the present application, the "TCAM+DHU" in the vehicle can be used as a gateway to connect the vehicle-domain IOT devices without setting up an additional gateway, which can save costs and provide reliable connections.

[0054] In some implementations, the DHU is used to send connection parameters to the vehicle-domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; the vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

[0055] It should be understood that the Wi-Fi name and Wi-Fi password of the TCAM controller may also be referred to as the hotspot name and hotspot password of the TCAM controller.

[0056] In some implementations, before using DHU to send connection parameters to the vehicle-domain IOT device, it also includes: using DHU to establish a target wireless communication connection with the vehicle-domain IOT device; then, using DHU to receive the device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, the device parameters including the device identifier of the vehicle-domain IOT device and the Wi-Fi list supported by the vehicle-domain IOT device. It should be understood that the Wi-Fi name of the TCAM controller must be in the Wi-Fi list. It should be understood that if the Wi-Fi name of the TCAM controller is not in the Wi-Fi list, it means that the vehicle-domain IOT device has not searched for the Wi-Fi name of the TCAM controller, and the vehicle-domain IOT device will not be able to establish a Wi-Fi connection with the TCAM controller later.

[0057] The present application does not impose any specific limitation on the target wireless communication connection. For example, the target wireless communication connection may be a Bluetooth connection, an infrared connection, or a Zigbee connection.

[0058] As an example, if the target wireless communication connection is a Bluetooth connection, using the DHU to establish the target wireless communication connection with the vehicle-domain IOT device includes: using the DHU to receive a Bluetooth pairing request sent by the vehicle-domain IOT device; in response to a successful Bluetooth pairing, using the DHU to establish a Bluetooth connection with the vehicle-domain IOT device. In some implementations, the vehicle-domain IOT device may send a Bluetooth pairing request to the DHU in a broadcast manner.

[0059] In some implementations, after receiving the device parameters sent by the vehicle-domain IOT device through the target wireless communication connection using the DHU, the method further includes: selecting a Wi-Fi name in the Wi-Fi list using the DHU and entering a Wi-Fi password. Then, the DHU can be used to send the connection parameters to the vehicle-domain IOT device.

[0060] In some implementations, the user can select a Wi-Fi name from a Wi-Fi list and enter a Wi-Fi password on the DHU. In other implementations, the user can also trigger the Wi-Fi connection with one click. For example, the user can click a trigger button on the DHU to trigger the connection with one click. Based on the device parameters of the vehicle-domain IOT device, the DHU can automatically select a Wi-Fi name from the Wi-Fi list and enter a Wi-Fi password. It should be understood that the Wi-Fi name and Wi-Fi password of the TCAM controller need to be pre-stored in the DHU.

[0061] In some implementations, the TCAM controller may be used to feed back the connection result of the Wi-Fi connection to the DHU to instruct the DHU to perform a target operation.

[0062] As an example, if the connection result is a connection failure, the DHU can be used to perform the following target operations: reselect the Wi-Fi name in the Wi-Fi list and re-enter the Wi-Fi password so that the vehicle-domain IOT device can re-establish a Wi-Fi connection with the TCAM controller.

[0063] In some implementations, the TCAM controller is used to feed back the connection result of the Wi-Fi connection to the DHU, including: using the TCAM controller to feed back the connection result of the Wi-Fi connection to the vehicle-domain IOT device, and then the vehicle-domain IOT device feeds back the connection result of the Wi-Fi connection to the DHU to instruct the DHU to perform the target operation.

[0064] In some implementations, after using DHU to receive the device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, it also includes: using DHU to send the device identifier of the vehicle-domain IOT device and the vehicle identification number VIN of the vehicle where the vehicle gateway is located to the target cloud platform, so that the target cloud platform creates a mapping relationship table with the vehicle-domain IOT device. Further, the vehicle-domain IOT device can be remotely controlled by the corresponding target cloud platform.

[0065] In some implementations, the vehicle domain IOT device includes multiple IOT devices; the DHU can be used to network multiple IOT devices into a mesh network; the mesh network can also be referred to as MESH networking.

[0066] In the embodiments of the present application, the networking modes supported by multiple IOT devices include: ordinary Bluetooth MESH networking, low-power Bluetooth (blue-tooth low energy, BLE) MESH networking, and Wi-Fi MESH networking.

[0067] In some implementations, the TCAM controller is used to cache the network connection parameters of the vehicle-domain IOT device, which include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device. The device node address of the vehicle-domain IOT device may refer to a number or code used to uniquely identify each vehicle-domain IOT device in the network.

[0068] In some implementations, after the DHU enters a dormant state, if the user triggers a wake-up signal in a target application or issues a remote control command to a vehicle-domain IOT device, the DHU can be remotely woken up through a mobile terminal or a target cloud platform.

[0069] In some implementations, the DHU has an application for managing vehicle-domain IOT devices, and the DHU is used to manage the vehicle-domain IOT devices through the application; managing the vehicle-domain IOT devices through the application includes one or more of the following: adding new vehicle-domain IOT devices through the application; deleting vehicle-domain IOT devices through the application; viewing the data of vehicle-domain IOT devices through the application.

[0070] In some implementations, a user can remotely control and manage vehicle-domain IOT devices through a communication link formed by the mobile terminal, the target platform, and the vehicle gateway in a corresponding application of the mobile terminal.

[0071] As an example, the mobile terminal is communicatively connected to the target cloud platform, the target cloud platform is communicatively connected to the vehicle gateway, the mobile terminal has a target application for managing vehicle-domain IOT devices, and the mobile terminal is used to manage the vehicle-domain IOT devices through the target application; managing the vehicle-domain IOT devices through the target application includes one or more of the following: adding new vehicle-domain IOT devices through the target application; deleting vehicle-domain IOT devices through the target application; viewing the data of vehicle-domain IOT devices through the target application.

[0072] In some implementations, the application for remote wake-up and the application for remote management of IOT devices can be the same application (such as the target application in this application). Of course, the two can also be different applications, and this application does not impose specific restrictions on this.

[0073] The following describes the embodiments of the present application in more detail with reference to specific examples. Figure 2 It is only to help those skilled in the art understand the embodiments of the present application, rather than to limit the embodiments of the present application to the specific values ​​or specific scenarios illustrated. Those skilled in the art can obviously make various equivalent modifications or changes based on the examples given, and such modifications or changes also fall within the scope of the embodiments of the present application.

[0074] Figure 2 A schematic diagram of a communication system provided in an embodiment of the present application. Figure 2 The communication system includes a mobile terminal, a target cloud platform, a vehicle and a vehicle-domain IOT device. The vehicle includes a TCAM controller and a DHU. The present application can combine the TCAM controller and the DHU as a gateway, and the vehicle connects to the vehicle-domain IOT device through the "TCAM+DHU" gateway.

[0075] In the embodiment of the present application, the mobile terminal is configured with a target application, and the user performs a vehicle DHU remote wake-up operation and an IOT device remote management operation in the target application. It should be understood that before performing a remote management operation on the IOT device, the IOT device information synchronization is also included.

[0076] In some implementations, remotely waking up the DHU includes: (1) a user may trigger a target application on a mobile terminal and send a remote wake-up instruction to a target cloud platform, where the remote wake-up instruction is used to remotely wake up the DHU; (2) the target cloud platform sends the remote wake-up instruction to a TCAM controller; (3) the TCAM controller is used to wake up the DHU based on the remote wake-up instruction.

[0077] In some implementations, the device information synchronization of IOT devices includes: ① The vehicle-domain IOT device is connected to the TCAM in the vehicle gateway; ② The device information of the vehicle-domain IOT device can be synchronized to the DHU through the TCAM controller; ③ The device information of the vehicle-domain IOT device can be synchronized to the target cloud platform through the TCAM controller; ④ The target cloud platform can be used to synchronize the device information of the vehicle-domain IOT device to the mobile terminal.

[0078] It should be noted that the device information of an IOT device includes but is not limited to: device operating status (such as sleep state or activation state), device node address, device name / identification, etc.

[0079] In some implementations, remote management of IOT devices includes: ⑤ A user can trigger a remote management instruction of an IOT device through a target application on a mobile terminal, and send a remote management instruction to a target cloud platform, which is used to remotely manage the vehicle domain IOT device; ⑥ The target cloud platform sends the remote management instruction to the TCAM controller; ⑧ The IOT instruction is issued and executed through the TCAM controller. Among them, remote management of IOT devices includes but is not limited to: remotely adding new vehicle domain IOT devices, remotely deleting vehicle domain IOT devices, and remotely viewing the data of vehicle domain IOT devices.

[0080] In some implementations, corresponding applications can also be configured on the DHU, and vehicle domain IOT device management can also be performed on the DHU. For example, using the DHU to manage vehicle domain IOT devices includes: ⑦ Users can trigger management instructions for IOT devices through applications on the DHU and send management instructions to the TCAM controller; ⑧ IOT instructions are issued and executed through the TCAM controller. Among them, managing IOT devices includes but is not limited to: adding new vehicle domain IOT devices, deleting vehicle domain IOT devices, and viewing the data of vehicle domain IOT devices.

[0081] In some implementations, the target cloud platform can also directly manage the vehicle domain IOT devices. For example, the target cloud platform directly manages the vehicle domain IOT devices including: ⑤ The user can trigger the remote management instruction of the IOT device through the target application on the mobile terminal, and send the remote management instruction to the target cloud platform, which is used to remotely manage the vehicle domain IOT devices; ⑨ Directly send the remote management instruction to the vehicle domain IOT device through the target cloud platform. Among them, remote management of IOT devices includes but is not limited to: remotely adding new vehicle domain IOT devices, remotely deleting vehicle domain IOT devices, and remotely viewing the data of vehicle domain IOT devices.

[0082] As mentioned above, the vehicle gateway is used to communicate with the vehicle domain IOT devices. Figure 3 The connection method between the vehicle gateway and the vehicle domain IOT devices is described in detail.

[0083] Figure 3 A flowchart of a method for establishing a vehicle-domain IOT device connection provided in an embodiment of the present application. Figure 3 The method shown includes steps S301 to S310.

[0084] In step S301, the vehicle-domain IOT device sends Bluetooth broadcast information. It should be understood that the Bluetooth broadcast information includes a Bluetooth pairing request and the Bluetooth name of the vehicle-domain IOT device.

[0085] In step S302, in response to the Bluetooth pairing request, the DHU is used to complete the Bluetooth pairing with the vehicle-domain IOT device, so that a Bluetooth communication connection is established between the vehicle-domain IOT device and the DHU.

[0086] In step S303, the vehicle domain IOT device sends the device parameters sent by the vehicle domain IOT device to the DHU through the Bluetooth communication connection, and the device parameters include the device identification of the vehicle domain IOT device and the Wi-Fi list supported by the vehicle domain IOT device.

[0087] In step S304, after receiving the device identification of the vehicle domain IOT device, the DHU can send the vehicle VIN code of the vehicle where the vehicle domain IOT device is located and the device identification of the vehicle domain IOT device to the target cloud platform, so that the target cloud platform can create a mapping table with each vehicle domain IOT device. Further, the mobile terminal outside the vehicle can remotely control the vehicle domain IOT device through the corresponding target cloud platform.

[0088] In step S305, the Wi-Fi name of the TCAM controller is selected from the Wi-Fi list using the DHU, and the Wi-Fi password of the TCAM controller is input. In some implementations, the DHU includes a touch screen, and the Wi-Fi name of the TCAM controller can be selected from the Wi-Fi list on the touch screen, and the Wi-Fi password of the TCAM controller can be input.

[0089] In step S306, the DHU sends connection parameters to the vehicle-domain IOT device through a Bluetooth communication connection, where the connection parameters include the Wi-Fi name and Wi-Fi password of the TCAM controller.

[0090] In step S307, after receiving the Wi-Fi connection parameters, the vehicle-domain IOT device may try to establish a Wi-Fi connection with the TCAM controller (ie, try to connect to the TACM hotspot).

[0091] In step S308, the TCAM controller feeds back the connection result of the Wi-Fi connection to the vehicle-domain IOT device.

[0092] In step S309, the vehicle-domain IOT device feeds back the connection result of the Wi-Fi connection to the DHU.

[0093] In step S310, if the Wi-Fi connection result is a connection failure, reconnect: use the DHU to reselect the Wi-Fi name in the Wi-Fi list and re-enter the Wi-Fi password so that the vehicle-domain IOT device can re-establish a Wi-Fi connection with the TCAM controller.

[0094] Combination of the above Figures 1 to 3 The method embodiment of the present application is described in detail. Figures 4 to 5 The device embodiment of the present application is described in detail. It should be understood that the description of the method embodiment corresponds to the description of the device embodiment, so the parts not described in detail can refer to the previous method embodiment.

[0095] Figure 4 This is a schematic diagram of the structure of a remote wake-up device provided in an embodiment of the present application. The device is applied to a target cloud platform, the target cloud platform is connected to a vehicle gateway and a mobile terminal, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, see Figure 4 The device 400 includes a receiving module 410 and a first sending module 420.

[0096] The receiving module 410 is configured to receive a remote wake-up instruction sent from the mobile terminal.

[0097] The first sending module 420 is configured to send the remote wake-up instruction to the TCAM controller in response to the DHU being in a sleep state, so as to wake up the DHU using the TCAM controller.

[0098] Optionally, the apparatus 400 further includes: a second receiving module, configured to receive device status information of the DHU sent from the TCAM controller; and a judging module, configured to judge whether the DHU is in a sleep state according to the device status information of the DHU.

[0099] Optionally, the vehicle-mounted gateway is communicatively connected to the vehicle-domain IOT device, and the DHU is used to send connection parameters to the vehicle-domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; the vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

[0100] Optionally, the DHU is used to establish a target wireless communication connection with the vehicle-domain IOT device, receive device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, and send the connection parameters to the vehicle-domain IOT device through the target wireless communication connection, wherein the device parameters include the device identification of the vehicle-domain IOT device and the wireless fidelity Wi-Fi list supported by the vehicle-domain IOT device, and the Wi-Fi name is in the Wi-Fi list.

[0101] Optionally, the DHU is further used to select the Wi-Fi name in the Wi-Fi list and enter the Wi-Fi password after receiving the device parameters sent by the vehicle-domain IOT device.

[0102] Optionally, the vehicle-domain IOT device is used to receive a connection result of the Wi-Fi connection sent from the TCAM controller, and send the connection result to the DHU to instruct the DHU to perform a target operation.

[0103] Optionally, the target wireless communication connection is a Bluetooth connection, an infrared connection, or a Zigbee connection.

[0104] Optionally, the vehicle-domain IOT device includes multiple IOT devices; the DHU is used to perform mesh networking for the multiple IOT devices; the TCAM controller is used to cache network connection parameters of the vehicle-domain IOT device, and the network connection parameters include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device.

[0105] Figure 5This is a schematic diagram of the structure of a remote wake-up device provided in another embodiment of the present application. The device is applied to a mobile terminal, the mobile terminal includes a target application, the mobile terminal is connected to a vehicle gateway through a target cloud platform, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, see Figure 5 The device 500 includes a trigger module 510 and a second sending module 520.

[0106] The trigger module 510 is used to trigger a remote wake-up instruction in the target application.

[0107] The second sending module 520 is used to send a remote wake-up instruction to the TCAM controller through the target cloud platform, so as to wake up the DHU using the TCAM controller.

[0108] Optionally, the device 400 also includes: a third receiving module, used to receive the device status information of the DHU sent from the TCAM controller through the target cloud platform before triggering the remote wake-up instruction in the target application; a second judgment module, used to judge whether the DHU is in a sleep state based on the device status information of the DHU; the trigger module 510 is used to: in response to the DHU being in a sleep state, trigger the remote wake-up instruction in the target application.

[0109] Optionally, the vehicle-mounted gateway is communicatively connected to the vehicle-domain IOT device, and the DHU is used to send connection parameters to the vehicle-domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; the vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

[0110] Optionally, the DHU is used to establish a target wireless communication connection with the vehicle-domain IOT device, receive device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, and send the connection parameters to the vehicle-domain IOT device through the target wireless communication connection, wherein the device parameters include the device identification of the vehicle-domain IOT device and the wireless fidelity Wi-Fi list supported by the vehicle-domain IOT device, and the Wi-Fi name is in the Wi-Fi list.

[0111] Optionally, the DHU is further used to select the Wi-Fi name in the Wi-Fi list and enter the Wi-Fi password after receiving the device parameters sent by the vehicle-domain IOT device.

[0112] Optionally, the vehicle-domain IOT device is used to receive a connection result of the Wi-Fi connection sent from the TCAM controller, and send the connection result to the DHU to instruct the DHU to perform a target operation.

[0113] Optionally, the target wireless communication connection is a Bluetooth connection, an infrared connection, or a Zigbee connection.

[0114] Optionally, the vehicle-domain IOT device includes multiple IOT devices; the DHU is used to perform mesh networking for the multiple IOT devices; the TCAM controller is used to cache network connection parameters of the vehicle-domain IOT device, and the network connection parameters include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device.

[0115] Combine the following Figure 6 The present invention introduces a communication device 600 in an embodiment of the present application. The communication device 600 may be the target cloud platform or mobile device mentioned above. In other words, the communication device 600 may be used to implement the method described in the above method embodiment.

[0116] The communication device 600 may include one or more processors 610. The processor 610 may support the communication device 600 to implement the method described in the foregoing method embodiment.

[0117] The processor 610 may be a general-purpose processor or a special-purpose processor. For example, the processor may be a central processing unit (CPU). Alternatively, the processor may be other general-purpose processors, digital signal processors (DSP), application-specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or the processor may be any conventional processor, etc.

[0118] The communication device 600 may further include one or more memories 620. The memory 620 stores a program, which can be executed by the processor 610 to control the communication device 600 to execute the method described in the above method embodiment. The memory 620 may be independent of the processor 610 or integrated in the processor 610.

[0119] The communication device 600 may further include a transceiver 630. The processor 610 may communicate with other devices through the transceiver 630. For example, the processor 610 may perform data transmission and reception with other devices through the transceiver 630.

[0120] The present application also provides a chip in an embodiment, including a processor, which can be used to call and run a computer program from a memory, so that a communication device equipped with the chip performs the method described in the above method embodiment. It is understood that the processor can be any type of processor mentioned above. It is understood that the memory can be independent of the chip or integrated in the chip.

[0121] The embodiment of the present application also provides a machine-readable storage medium for storing a program, and the program enables a computer to execute the method in each embodiment of the present application.

[0122] The embodiment of the present application also provides a computer program product. The computer program product includes a program. The program enables a computer to execute the method in each embodiment of the present application.

[0123] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any other combination. When implemented by software, it can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, the process or function described in the embodiment of the present disclosure is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a machine-readable storage medium, or transmitted from one machine-readable storage medium to another machine-readable storage medium. For example, the computer instructions can be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The machine-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrations. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state disk (SSD)).

[0124] Those of ordinary skill in the art will appreciate that the units and algorithm steps of each example described in conjunction with the embodiments of the present disclosure can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are performed in hardware or software depends on the specific application and design constraints of the technical solution. Professional and technical personnel can use different methods to implement the described functions for each specific application, but such implementation should not be considered to be beyond the scope of the present disclosure.

[0125] In the several embodiments provided in the present disclosure, 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 only schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.

[0126] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0127] In addition, each functional unit in each embodiment of the present disclosure may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0128] The above is only a specific embodiment of the present disclosure, but the protection scope of the present disclosure is not limited thereto. Any person skilled in the art who is familiar with the technical field can easily think of changes or substitutions within the technical scope disclosed in the present disclosure, which should be included in the protection scope of the present disclosure. Therefore, the protection scope of the present disclosure should be based on the protection scope of the claims.

Claims

1. A remote wake-up method, characterized in that: Applied to a target cloud platform, the target cloud platform is communicatively connected with a vehicle gateway and a mobile terminal, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, the method includes: receiving a remote wake-up instruction sent from the mobile terminal; In response to the DHU being in the sleep state, sending the remote wake-up instruction to the TCAM controller, so as to wake up the DHU by using the TCAM controller.

2. The method according to claim 1, characterized in that The method further comprises: receiving device status information of the DHU sent from the TCAM controller; According to the device status information of the DHU, it is determined whether the DHU is in a dormant state.

3. The method according to claim 1, characterized in that The vehicle-mounted gateway is connected to the vehicle-domain IOT device for communication. The DHU is used to send connection parameters to the vehicle domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; The vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

4. The method according to claim 3, characterized in that The DHU is used to establish a target wireless communication connection with the vehicle-domain IOT device, receive device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, and send the connection parameters to the vehicle-domain IOT device through the target wireless communication connection, wherein the device parameters include the device identification of the vehicle-domain IOT device and the wireless fidelity Wi-Fi list supported by the vehicle-domain IOT device, and the Wi-Fi name is located in the Wi-Fi list.

5. The method according to claim 4, characterized in that The DHU is also used to select the Wi-Fi name in the Wi-Fi list and enter the Wi-Fi password after receiving the device parameters sent by the vehicle-domain IOT device.

6. The method according to claim 4, characterized in that The vehicle domain IOT device is used to receive the connection result of the Wi-Fi connection sent from the TCAM controller, and send the connection result to the DHU to instruct the DHU to perform a target operation.

7. The method according to claim 4, characterized in that The target wireless communication connection is a Bluetooth connection, an infrared connection, or a Zigbee connection.

8. The method according to any one of claims 3 to 7, characterized in that The vehicle domain IOT device includes multiple IOT devices; The DHU is used to perform mesh networking for the multiple IOT devices; The TCAM controller is used to cache the network connection parameters of the vehicle-domain IOT device, where the network connection parameters include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device.

9. A remote wake-up method, characterized in that: Applied to a mobile terminal, the mobile terminal includes a target application, the mobile terminal is connected to a vehicle gateway through a target cloud platform, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, the method includes: triggering a remote wake-up instruction in the target application; A remote wake-up instruction is sent to the TCAM controller through the target cloud platform, so as to wake up the DHU using the TCAM controller.

10. The method according to claim 9, characterized in that Before triggering the remote wake-up instruction in the target application, the method further includes: Receiving, through the target cloud platform, device status information of the DHU sent from the TCAM controller; Determining whether the DHU is in a dormant state according to the device status information of the DHU; Triggering a remote wake-up command in the target application, including: In response to the DHU being in a dormant state, triggering the remote wake-up instruction in the target application.

11. The method according to claim 9, characterized in that The vehicle-mounted gateway is connected to the vehicle-domain IOT device for communication. The DHU is used to send connection parameters to the vehicle domain IOT device, where the connection parameters include the wireless fidelity Wi-Fi name and Wi-Fi password of the TCAM controller; The vehicle-domain IOT device is used to establish a Wi-Fi connection with the TCAM controller based on the connection parameters.

12. The method according to claim 11, characterized in that The DHU is used to establish a target wireless communication connection with the vehicle-domain IOT device, receive device parameters sent by the vehicle-domain IOT device through the target wireless communication connection, and send the connection parameters to the vehicle-domain IOT device through the target wireless communication connection, wherein the device parameters include the device identification of the vehicle-domain IOT device and the wireless fidelity Wi-Fi list supported by the vehicle-domain IOT device, and the Wi-Fi name is located in the Wi-Fi list.

13. The method according to claim 12, characterized in that The DHU is also used to select the Wi-Fi name in the Wi-Fi list and enter the Wi-Fi password after receiving the device parameters sent by the vehicle-domain IOT device.

14. The method according to claim 12, characterized in that The vehicle domain IOT device is used to receive the connection result of the Wi-Fi connection sent from the TCAM controller, and send the connection result to the DHU to instruct the DHU to perform a target operation.

15. The method according to claim 12, characterized in that The target wireless communication connection is a Bluetooth connection, an infrared connection, or a Zigbee connection.

16. The method according to any one of claims 11 to 15, characterized in that The vehicle domain IOT device includes multiple IOT devices; The DHU is used to perform mesh networking for the multiple IOT devices; The TCAM controller is used to cache the network connection parameters of the vehicle-domain IOT device, where the network connection parameters include the network connection status of the vehicle-domain IOT device and the device node address of the vehicle-domain IOT device.

17. A remote wake-up device, characterized in that: Applied to a target cloud platform, the target cloud platform is connected to a vehicle gateway and a mobile terminal, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, and the device includes: A receiving module, used for receiving a remote wake-up instruction sent from the mobile terminal; The first sending module is configured to send the remote wake-up instruction to the TCAM controller in response to the DHU being in a sleep state, so as to wake up the DHU by using the TCAM controller.

18. A remote wake-up device, characterized in that: Applied to a mobile terminal, the mobile terminal includes a target application, the mobile terminal is connected to a vehicle gateway through a target cloud platform, the vehicle gateway includes a vehicle communication and management TCAM controller and a digital cockpit host DHU, the device includes: A trigger module, used for triggering a remote wake-up instruction in the target application; The second sending module is used to send a remote wake-up instruction to the TCAM controller through the target cloud platform, so as to wake up the DHU using the TCAM controller.

Images