A real-time vehicle remote control method on a mobile terminal device

Abstract

The present invention provides a real-time vehicle remote control method on a mobile terminal device, which includes the following steps: The mobile terminal device sends a connection request to the vehicle networking platform TSP and establishes a long connection; The vehicle networking platform TSP sends an instruction to the in-vehicle communication terminal TBOX and establishes a long connection; The in-vehicle communication terminal TBOX sends an instruction to the body controller ECU, and the body controller ECU receives the instruction, controls the body to change its state, and transmits the control result to the in-vehicle communication terminal TBOX; The in-vehicle communication terminal TBOX then transmits this control result to the vehicle networking platform TSP and the mobile terminal device.

Description

Technical Field

[0001] The present invention relates to the technical field of vehicle communication, and particularly relates to a real-time vehicle remote control method on a mobile terminal device. Background Art

[0002] Currently, some vehicles on the market already support the function of remotely controlling the vehicle. The main method is to send control instructions from a mobile phone or a wearable device's App (hereinafter referred to as: App) to the vehicle networking platform (hereinafter referred to as: TSP), and then send them to the vehicle side to execute the instructions; and then layer by layer return the control result to the device side to display the control result. The main vehicle control functions include: turning on and off the air conditioner, headlights, unlocking the car door, starting the vehicle, etc.;

[0003] Currently, when experiencing related products, it is found that there are multiple repeated interactions in human-computer interaction, such as clicking to control, authorizing to wake up, and entering an authorization password; the instruction issuance needs to go through links such as control trigger, waiting to wake up, control issuance, control response, and result return. It takes several minutes to wait from the issuance to the return of the result. The general process is as Figure 1 shown. The disadvantages of the above technologies include:

[0004] 1. When the vehicle is powered off or after remote wake-up, the in-vehicle communication terminal (hereinafter referred to as: Tbox) only remains online for several minutes and then goes into sleep. When operating remote control again, the wake-up process needs to be done again, resulting in restarting the Tbox every time it wakes up. The user needs to authorize again, enter the authorization code, and wait for the Tbox to start. The interaction and communication logic are complex and the waiting time is long;

[0005] 2. After the control is issued, it takes several minutes to wait for the communication to return. There is no status synchronization mechanism in the current technical solution. If the vehicle side synchronizes operations during the waiting period, it is easy to cause inaccurate feedback results;

[0006] 3. In the vehicle, the communication mechanism from the Tbox to each controlled ECU is in a broadcast form. The Tbox needs to wait for the status change signal of the corresponding ECU to confirm the control result, and needs to judge the execution failure situation through timeout. This results in complex Tbox logic and long waiting time when it fails. Summary of the Invention

[0007] Therefore, it is necessary to provide a real-time vehicle remote control method on a mobile terminal device with simple Tbox logic and short waiting time.

[0008] To achieve the above object, the inventor provides a real-time vehicle remote control method on a mobile terminal device, including the following steps:

[0009] The mobile terminal device sends a connection request to the vehicle networking platform TSP and establishes a long connection;

[0010] The vehicle networking platform TSP issues an instruction to the in-vehicle communication terminal TBOX and establishes a long connection;

[0011] The in-vehicle communication terminal TBOX sends an instruction to the body controller ECU. After receiving the instruction, the body controller ECU controls the body to change its state and transmits the control result to the in-vehicle communication terminal TBOX; the in-vehicle communication terminal TBOX transmits the control result to the vehicle networking platform TSP, and the vehicle networking platform TSP transmits the control result to the mobile terminal device.

[0012] Furthermore, the in-vehicle communication terminal TBOX is divided into a non-logged-in state and a logged-in state. The logged-in state includes a response mode and a sleep mode; when the vehicle networking platform TSP issues an instruction to the in-vehicle communication terminal TBOX, if it is detected that the in-vehicle communication terminal TBOX is in the non-logged-in state, the vehicle networking platform TSP sends data to wake up the in-vehicle communication terminal TBOX and enter the response mode; if it is detected that the in-vehicle communication terminal TBOX is in the sleep mode, the vehicle networking platform TSP sends a short message to wake up the in-vehicle communication terminal TBOX and enter the response mode.

[0013] Furthermore, when the in-vehicle communication terminal TBOX in the response mode does not receive an instruction within the first set time, it enters the sleep mode from the response mode; when the in-vehicle communication terminal TBOX in the sleep mode does not receive a short message within the second set time, the in-vehicle communication terminal TBOX enters the non-logged-in state from the sleep mode.

[0014] Furthermore, the response time of the in-vehicle communication terminal TBOX for short message wake-up is 5s.

[0015] Furthermore, when in the sleep mode, the in-vehicle communication terminal TBOX periodically sends heartbeat packets to the vehicle networking platform TSP through the long connection.

[0016] Furthermore, the mobile terminal device establishes an MQTT long connection with the vehicle networking platform TSP.

[0017] Furthermore, the vehicle networking platform TSP establishes a TCP long connection with the in-vehicle communication terminal TBOX.

[0018] Furthermore, the in-vehicle communication terminal Tbox communicates with the body controller ECU through a question-and-answer diagnostic frame.

[0019] Furthermore, the mobile terminal device includes an APP of a mobile phone or a wearable device.

[0020] Different from the prior art, the above technical solution has at least the following beneficial effects: a method for real-time vehicle remote control on a mobile terminal device with reduced operation steps, simple Tbox logic, and short waiting time. Description of the Drawings

[0021] Figure 1 is a flowchart of the method for an existing technology system;

[0022] Figure 2 is a communication control diagram of Embodiment 1;

[0023] Figure 3 is a remote control flowchart of Embodiment 1;

[0024] Figure 4 is a real-time status monitoring diagram of Embodiment 1;

[0025] Figure 5 is Interaction Design Solution 1 for the App side;

[0026] Figure 6 is Interaction Design Solution 2 for the App side;

[0027] Figure 7 is Interaction Design Solution 3 for the App side. Detailed Description of the Invention

[0028] To elaborate on the technical content, structural features, achieved objectives, and effects of the technical solution in detail, the following will be described in detail in conjunction with specific embodiments and with reference to the accompanying drawings.

[0029] Embodiment 1 A Real-time Vehicle Remote Control Method on a Mobile Terminal Device

[0030] As Figures 2-4 shown, the mobile terminal device sends a connection request to the Telematics Service Provider (TSP) of the vehicle network and establishes an MQTT long connection; the TSP of the vehicle network sends an instruction to the In-Vehicle Communication Terminal (TBOX) and establishes a TCP long connection; the TBOX communicates with the Electronic Control Unit (ECU) of the vehicle body through a question-and-answer diagnostic frame, and transmits diagnostic frame instructions in a question-and-answer form. The ECU of the vehicle body receives the instruction, controls the vehicle body to change its state, and performs remote control. After the vehicle body state changes, the ECU of the vehicle body transmits the control result to the TBOX; the TBOX then transmits this control result to the TSP of the vehicle network and the mobile terminal device. The execution results of all remote control instructions forwarded by the Tbox will reply the execution results to the Tbox after being executed by each ECU, and then be transmitted transparently to the TSP and the mobile terminal for real-time status monitoring.

[0031] The in-vehicle communication terminal TBOX is divided into a non-login state and a login state. The login state includes a response mode and a sleep mode. When the in-vehicle communication terminal TBOX in the response mode does not receive an instruction within the first set time (usually defined as 30s - 1min), it enters the sleep mode from the response mode; when the in-vehicle communication terminal TBOX in the sleep mode does not receive a text message within the second set time (usually defined as 3 - 5min), it enters the non-login state from the sleep mode. When the in-vehicle communication terminal TBOX is in the sleep mode, it periodically sends heartbeat packets to the vehicle networking platform TSP through a long connection; in this way, when the TBOX is in the sleep mode, the TBOX can enter a low-power consumption mode, and only the working state of the 4G communication module is retained.

[0032] When the vehicle networking platform TSP sends an instruction to the in-vehicle communication terminal TBOX, if it detects that the in-vehicle communication terminal TBOX is in the non-login state, the vehicle networking platform TSP sends data to wake up the in-vehicle communication terminal TBOX and enter the response mode; if it detects that the in-vehicle communication terminal TBOX is in the sleep mode, the vehicle networking platform TSP sends a text message to wake up the in-vehicle communication terminal TBOX and enter the response mode. The text message wake-up or the ringing wake-up delay terminal is used. The above are all to directly wake up the TBOX through the TCP layer message, with high reliability and low power consumption during operation. The mobile terminal device includes the APP of a mobile phone or a wearable device.

[0033] The actual measurement of the present invention shows that the average power consumption of the TBOX in the sleep mode is less than 4mA, and the response time of the in-vehicle communication terminal TBOX for text message wake-up is 5s, which can achieve a fast response mode.

[0034] In terms of user experience, first, the remote control password adopts the form of a gesture password, and within a certain time range after the first successful input of the control password, such as 5 minutes (that is, the time from the response mode to the non-login state, which is the sum of the first set time and the second set time and can be customized by the user according to operation habits), the password can be omitted for control again. The design is to reduce the frequency of user password input, optimize the experience and the interaction frequency between the App and the platform;

[0035] In the App display design, the vehicle status of the key vehicle components is displayed. Combining the long connection link between the App and the platform, the App side can receive the status update messages sent by the platform at any time and display them on the interface in a timely manner; the interaction design scheme on the App side is as follows Figures 5-7 As shown, the status of the vehicle lock, vehicle lights, vehicle doors, etc. can be displayed in real time.

[0036] The above technical solutions optimize the user experience, reduce the operation steps, have a simple Tbox logic, short waiting time, and low energy consumption, and are a real-time vehicle remote control method on a mobile terminal device.

[0037] It should be noted that in this article, relational terms such as first and second are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any actual relationship or order between these entities or operations. Moreover, the term "comprising", "including" or any other variant thereof is intended to cover non-exclusive inclusion, so that a process, method, article or terminal device comprising a series of elements not only includes those elements, but also includes other elements not expressly listed, or further includes elements inherent to such process, method, article or terminal device. Without more limitations, elements defined by the statement "comprising..." or "including..." do not preclude the existence of additional elements in the process, method, article or terminal device comprising the said elements. In addition, in this article, "greater than", "less than", "exceeding", etc. are understood not to include the base number; "above", "below", "within", etc. are understood to include the base number.

[0038] It should be noted that although the above embodiments have been described in this article, this does not limit the scope of patent protection of the present invention. Therefore, based on the innovative concept of the present invention, changes and modifications made to the embodiments described in this article, or equivalent structural or equivalent process transformations made using the content of the specification and drawings of the present invention, directly or indirectly applying the above technical solutions to other related technical fields, are all included in the scope of patent protection of the present invention.

Claims

1. A real-time vehicle remote control method on a mobile terminal device, characterized in that, It includes the following steps: The mobile terminal device sends a connection request to the Telematics Service Provider (TSP) of the vehicle network platform and establishes a long connection; The Telematics Service Provider (TSP) of the vehicle network platform issues an instruction to the in-vehicle communication terminal TBOX and establishes a long connection; The in-vehicle communication terminal TBOX sends an instruction to the body controller ECU. After receiving the instruction, the body controller ECU controls the body to change its state, and the state includes the vehicle lock state, the headlight state, and the door state, and transmits the control result to the in-vehicle communication terminal TBOX; The in-vehicle communication terminal TBOX transmits the control result to the Telematics Service Provider (TSP) of the vehicle network platform, and the Telematics Service Provider (TSP) of the vehicle network platform transmits the control result to the mobile terminal device; The mobile terminal receives the status update message sent by the Telematics Service Provider (TSP) of the vehicle network platform in real time and displays it on the interface; The in-vehicle communication terminal TBOX is divided into a non-login state and a login state, and the login state includes a response mode and a sleep mode; when the Telematics Service Provider (TSP) of the vehicle network platform issues an instruction to the in-vehicle communication terminal TBOX, if it is detected that the in-vehicle communication terminal TBOX is in the non-login state, the Telematics Service Provider (TSP) of the vehicle network platform sends data to wake up the in-vehicle communication terminal TBOX to enter the response mode; if it is detected that the in-vehicle communication terminal TBOX is in the sleep mode, the Telematics Service Provider (TSP) of the vehicle network platform sends a short message to wake up the in-vehicle communication terminal TBOX to enter the response mode; when the in-vehicle communication terminal TBOX in the response mode does not receive an instruction within the first set time, it enters the sleep mode from the response mode; when the in-vehicle communication terminal TBOX in the sleep mode does not receive a short message within the second set time, the in-vehicle communication terminal TBOX enters the non-login state from the sleep mode; When in the sleep mode, the in-vehicle communication terminal TBOX periodically sends heartbeat packets to the Telematics Service Provider (TSP) of the vehicle network platform through the long connection; The in-vehicle communication terminal Tbox communicates with the body controller ECU through a question-and-answer diagnostic frame.

2. The real-time vehicle remote control method according to claim 1, characterized in that, The response time of the in-vehicle communication terminal TBOX for short message wake-up is 5s.

3. The real-time vehicle remote control method according to claim 1, characterized in that, The mobile terminal device establishes an MQTT long connection with the Telematics Service Provider (TSP) of the vehicle network platform.

4. The real-time vehicle remote control method according to claim 1, characterized in that, The Telematics Service Provider (TSP) of the vehicle network platform establishes a TCP long connection with the in-vehicle communication terminal TBOX.

5. The real-time vehicle remote control method according to claim 1, characterized in that, The mobile terminal device includes the APP of a mobile phone or a wearable device.

Images