Remote driving device

By using the second communication protocol to communicate with the mobile terminal when the vehicle power is off, the start-up conditions are determined and the first communication and start-up control unit are established simultaneously, thus solving the problem of remote driving control delay in the prior art and realizing rapid remote driving control preparation.

CN123104643APending Publication Date: 2026-11-17TOYOTA JIDOSHA KK
View PDF 1 Cites 0 Cited by

Patent Information

Application Number
CN202610536646.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Priority Date
2025-05-14
Filing Date
2026-04-22
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

Existing remote driving devices require time to establish communication and start the control unit when the vehicle power is off, resulting in a delay in the start of remote driving control.

Method used

By using different communication protocols (second communication) to communicate with the mobile terminal when the vehicle power is off, the start-up conditions are determined, and when the conditions are met, the first communication and the start-up control unit are established simultaneously, thus shortening the preparation time for remote driving control.

Benefits of technology

It enables rapid establishment of communication and activation of the control unit when the vehicle power is disconnected, shortening the preparation time for remote driving control and improving operational efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123104643A_ABST
    Figure CN123104643A_ABST
Patent Text Reader

Abstract

The remote driving device enables the control unit to perform remote driving control. This remote driving control receives driving instructions via a first communication and causes the parked vehicle to move towards a designated target space according to the driving instructions. Even when the vehicle's power is off, the remote driving device can communicate with a mobile terminal or a user-carried electronic key terminal used for unlocking and locking the vehicle doors via a second communication protocol different from the first communication. When the vehicle's power is off, the device determines whether the prescribed start-up conditions are met based on the communication result of the second communication. If the start-up conditions are met, the first communication is established, and the control unit is activated by turning the vehicle's power on.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a remote driving device that performs remote driving control, wherein the remote driving control causes a parked vehicle to drive toward a specified target space based on a driving instruction sent by a mobile terminal when a user located outside the vehicle performs a specified remote operation on the mobile terminal. Background Technology

[0002] Previously, remote driving devices for performing remote driving control were known. For example, in the remote driving device described in Japanese Patent Application Publication No. 2022-048453 (hereinafter referred to as the "existing device"), if a legitimate user carrying an electronic key is located within the communication range of the electronic key while the vehicle's power supply (vehicle power) is off, a "communication (first communication) for performing data communication required for remote driving control" is established between the user and a "mobile terminal carried by the user and operated remotely by the user." Specifically, the existing device establishes the first communication by activating a data communication unit (DCU). Furthermore, in the prior art, the establishment of the first communication presupposes the activation of a remote driving application on the mobile terminal.

[0003] After the first communication is established, if the user performs the specified start operation on the mobile terminal, the mobile terminal will send a start instruction to the existing device. If the existing device receives the start instruction, it will start the "control unit (parking ECU) for performing remote driving control" by setting the vehicle's power supply to the on state. Summary of the Invention

[0004] The establishment of the first communication and the activation of the control unit require time. Since existing devices initiate the establishment of the first communication and the activation of the control unit at different time points, there may be time before remote driving control can begin. Specifically, the user must wait until the first communication is established before performing the startup operation, and then wait for the control unit to activate after performing the startup operation.

[0005] The present invention was made to solve the aforementioned problems. That is, one of the objects of the present invention is to provide a remote driving device that can shorten the time until remote driving control can be initiated.

[0006] The remote driving device of the present invention (hereinafter referred to as "the device of the present invention") causes the control unit (30) to perform remote driving control, which receives a driving instruction via a first communication and causes a parked vehicle to drive to a specified target space according to the driving instruction, which is sent by the mobile terminal when a user located outside the vehicle performs a specified remote operation on the mobile terminal (steps 500 to 595).

[0007] The remote driving device is configured as follows:

[0008] Even when the vehicle power supply (26) of the vehicle is disconnected, it is possible to communicate (204) with the mobile terminal or the electronic key terminal carried by the user for unlocking and locking the doors of the vehicle through a second communication protocol different from the first communication protocol.

[0009] If the vehicle power supply is off (step 305 "Yes"), determine whether the specified start-up conditions are met based on the communication result of the second communication (step 310).

[0010] If the startup condition is met (step 310 "Yes"), the first communication is established (step 315), and the control unit is started by setting the vehicle power supply to the on state (step 320).

[0011] Based on the communication results of the second communication, the device of the present invention establishes the first communication and starts the control unit when the prescribed start conditions are met. Thus, the establishment of the first communication and the start of the control unit begin simultaneously, thereby shortening the time until remote driving control can commence. Attached Figure Description

[0012] Hereinafter, with reference to the accompanying drawings, the features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will be described, in which the same reference numerals denote the same elements, and wherein:

[0013] Figure 1 This is a schematic system structure diagram of the remote driving device according to an embodiment of the present invention.

[0014] Figure 2 This is a timing diagram of the operation of the remote driving device according to an embodiment of the present invention.

[0015] Figure 3 yes Figure 1 The flowchart shown is of the startup routine executed by the CPU of the vehicle ECU.

[0016] Figure 4 yes Figure 1 The flowchart shown is a remote driving control preparation routine executed by the CPU of the remote driving ECU.

[0017] Figure 5 yes Figure 1 The flowchart shown is of the remote driving control routine executed by the CPU of the remote driving ECU. Detailed Implementation

[0018] like Figure 1As shown, the remote driving device 10 (hereinafter referred to as "the device 10") according to this embodiment is applicable to a vehicle VA. The device 10 sends and receives data with a user-operated mobile terminal SP via a first communication and a second communication. An electronic key application 12 and a remote driving application 14 are installed in the mobile terminal SP. The electronic key application 12 unlocks and locks the doors of the vehicle VA. The remote driving application 14 enables the device 10 to perform remote driving control as described later. The remote driving application 14 sends and receives data with the vehicle VA via the first communication, and the electronic key application 12 sends and receives data with the vehicle VA via the second communication. For example, the first communication is Bluetooth (registered trademark), and the second communication is Bluetooth Low Energy (hereinafter referred to as "BLE").

[0019] This device 10 has Figure 1 The components are shown below. In this specification, "ECU" refers to an electronic control device with a microcomputer as its main component. ECU is also referred to as a controller and computer. The microcomputer includes a CPU (processor), ROM, RAM, and interfaces (I / F), etc. The functions performed by an ECU can be implemented by multiple ECUs.

[0020] When a mobile terminal SP (e.g., a smartphone) is within range of being able to send and receive data via the second communication, the digital key ECU 20 verifies the mobile terminal SP. Specifically, the digital key ECU 20 obtains the electronic key ID set in the electronic key application 12. If this electronic key ID matches a valid electronic key ID set in the digital key ECU 20, the verification is considered successful. If the verification is successful, the digital key ECU 20 establishes the second communication with the mobile terminal SP.

[0021] The body ECU 22 changes the vehicle power supply 26, which serves as the power source for the vehicle VA, "from a disconnected state to an on state" or "from an on state to a disconnected state." For example, when the ignition key switch (not shown) of the vehicle VA is changed from the off position to the on position, the body ECU 22 changes the vehicle power supply 26 from the disconnected state to the on state.

[0022] When the vehicle power supply 26 is disconnected, it does not supply power to any ECU. However, since the battery 28 mounted on the vehicle VA supplies power to the digital key ECU 20, the body ECU 22, and the communication interface (I / F) 24, the digital key ECU 20, the body ECU 22, and the communication interface (I / F) 24 will still activate even when the vehicle power supply 26 is disconnected. Therefore, even when the vehicle power supply 26 is disconnected, the device 10 can still communicate with the mobile terminal SP via the second communication method. Normally, power is not supplied from the battery 28 to the data communication unit (DCU) 31, but power is supplied from the battery 28 to the DCU 31 when the activation conditions described later are met.

[0023] If the vehicle power supply 26 is turned on, power is supplied to the remote driving ECU 30, which does not receive power from the battery 28 when the vehicle power supply 26 is turned off, and the remote driving ECU 30 is activated. If power is supplied to the remote driving ECU 30, power is also supplied to the powertrain actuator 32, the brake actuator 34, and the steering motor 36.

[0024] The communication I / F24 and the mobile terminal SP send and receive data through the second communication.

[0025] The remote driving ECU 30 performs the remote driving control described later. The DCU 31 communicates with the mobile terminal SP via the first communication to send and receive data. Additionally, the remote driving ECU 30 is sometimes referred to as a "control unit".

[0026] Powertrain actuator 32 modifies the driving force generated by the vehicle VA's drive unit (e.g., internal combustion engine and / or electric motor). Brake actuator 34 controls the braking force applied to the vehicle VA. Steering motor 36 is assembled to steering mechanism 38. Steering mechanism 38 is a mechanism for steering the steering wheels according to the operation of the steering wheel. Moreover, steering motor 36, according to instructions from remote driving ECU 30, causes steering mechanism 38 to generate automatic steering torque for changing the steering angle of the steering wheels.

[0027] Remote driving control

[0028] Sometimes, a user located outside the vehicle VA remotely operates the mobile terminal SP. Remote driving control is performed as follows: in this case, based on driving instructions sent by the mobile terminal SP, the parked vehicle VA is driven towards a designated target space, thereby causing the vehicle VA to leave the parking space. In remote driving control, this device 10 and the remote driving application 14 of the mobile terminal SP communicate via a first communication to send and receive data required for remote driving control, such as driving instructions.

[0029] (Summary of the action)

[0030] When remote driving control is initiated, the vehicle VA is parked, therefore the vehicle power supply 26 is disconnected, and the DCU 31 is not activated. Therefore, a second communication can be established between the device 10 and the mobile terminal SP, but a first communication cannot be established. Therefore, when remote driving control is initiated, the first communication needs to be established by activating the DCU 31. Furthermore, when remote driving control is initiated, the remote driving ECU 30 needs to be activated by changing the vehicle power supply 26 from a disconnected state to an on state.

[0031] If the establishment of the first communication and the activation of the remote driving ECU 30 are performed at different time points, time will be required before remote driving control can begin. Therefore, when the vehicle power supply 26 is off, the device 10 determines whether the prescribed activation conditions are met based on the communication result of the second communication. If the device 10 determines that the activation conditions are met, it establishes the first communication by activating the DCU 31 and activates the remote driving ECU 30 by changing the vehicle power supply 26 from off to on.

[0032] Therefore, the device 10 can perform the establishment of the first communication and the start-up of the remote driving ECU 30 in parallel, thus shortening the time until remote driving control can begin.

[0033] (Action)

[0034] refer to Figure 2 The operation of this device 10 will be explained.

[0035] First, the mobile terminal SP approaches the vehicle VA (202), and the mobile terminal SP is within range where it can send and receive data via the second communication. In this case, if the verification is successful, the digital key ECU 20 establishes the second communication between the mobile terminal SP and the vehicle VA (204). With the second communication established, the digital key ECU 20 communicates with the mobile terminal SP via the second communication every predetermined time interval, thereby determining the distance D between the mobile terminal SP and the vehicle VA (206).

[0036] Then, the user operates the mobile terminal SP to launch the remote driving application 14 (208). If the remote driving application 14 is launched, the mobile terminal SP sends startup data to the vehicle VA via the first communication (210a). If the communication I / F 24 of the device 10 receives the startup data, the digital key ECU 20 sends the startup data to the body ECU 22 (210b).

[0037] Upon receiving startup data and with the distance D below the threshold distance Dth, the vehicle ECU 22 determines that the startup condition is met (212). If the startup condition is met, the vehicle ECU 22 sends a startup instruction to the DCU 31 (214) and starts the DCU 31 (216). Specifically, power from the battery 28 is supplied to the DCU 31. If the DCU 31 starts, a first communication is established between the mobile terminal SP and the vehicle VA (218).

[0038] If the activation conditions are met, the body ECU 22 sends an activation instruction to the vehicle power supply 26 (220) and changes the vehicle power supply 26 from the off state to the on state (222). If the vehicle power supply 26 becomes on, power is supplied to the remote driving ECU 30 (224), and the remote driving ECU 30 starts (226).

[0039] If the remote driving ECU 30 is activated due to the activation conditions being met, the remote driving ECU 30 determines at least one path (228) for the vehicle VA to exit the parking space. The remote driving ECU 30 transmits planning data including the determined path to the mobile terminal SP (230) via the first communication.

[0040] Upon receiving the planning data, the mobile terminal SP (remote driving application 14) displays a selection screen. The selection screen displays the routes included in the planning data. The user selects a route from the routes displayed on the selection screen (232). If the user selects a route, the mobile terminal SP (remote driving application 14) sends selection data including the selected route to the vehicle VA via the first communication (234).

[0041] If the device 10 receives selection data, the remote driving ECU 30 will determine the path contained in the received selection data as the driving path (236) of the vehicle VA.

[0042] Additionally, if a route is selected in the selection screen, the mobile terminal SP (remote driving application 14) displays an operation screen. The user places their finger on the operation input area of ​​the operation screen and continues to move the finger. This operation is referred to as "remote operation" (238). During the user's remote operation, the mobile terminal SP (remote driving application 14) sends a driving instruction to the device 10 via the first communication every predetermined time interval (240).

[0043] If the device 10 receives a driving instruction, the remote driving ECU 30 controls the powertrain actuator 32, the brake actuator 34 and the steering motor 36 to make the vehicle VA travel along the driving path (242).

[0044] (Specific actions)

[0045] <Startup routine>

[0046] The CPU of the vehicle ECU22 (hereinafter referred to as "CPU 1") executes at specified intervals. Figure 3 The routine shown in the flowchart.

[0047] If the appropriate time arrives, the first CPU will begin processing from step 300, proceeding to step 305. In step 305, the first CPU determines whether the vehicle power supply 26 is in a disconnected state.

[0048] When the vehicle power supply 26 is disconnected, the first CPU determines "yes" in step 305 and proceeds to step 310. In step 310, the first CPU determines whether the startup condition is met. The startup condition is that startup data is received and the distance D is below the threshold distance Dth.

[0049] If the startup conditions are not met, the first CPU determines "No" in step 310 and proceeds to step 395. In step 395, the first CPU temporarily terminates this routine.

[0050] On the other hand, if the startup conditions are met, the first CPU determines "yes" in step 310 and executes steps 315 and 320.

[0051] Step 315: The first CPU starts DCU31.

[0052] Step 320: The first CPU starts the remote driving ECU 30 by setting the vehicle power supply 26 to the on state.

[0053] Then, proceed to step 395.

[0054] If the vehicle power supply 26 is on when the process enters step 305, the first CPU determines "no" in step 305 and proceeds to step 395.

[0055] <Remote Driving Control Preparation Routine>

[0056] The CPU of the remote driving ECU 30 (hereinafter referred to as "second CPU") executes the following when the remote driving ECU 30 is started: Figure 4 The routine shown in the flowchart.

[0057] If the remote driving ECU 30 is activated, the second CPU will begin processing from step 400, proceeding to step 405. In step 405, the second CPU determines whether the activation conditions have been met.

[0058] If the starting conditions are not met, the remote driving ECU 30 is started by changing the ignition key switch to the ON position. Therefore, the remote driving ECU 30 does not need to perform remote driving control. Therefore, the second CPU determines "No" in step 405 and proceeds to step 408. In step 408, the second CPU sets the execution flag Xexe to "0". The execution flag Xexe is set to "1" when remote driving control is performed and set to "0" when remote driving control is not performed. Then, the process proceeds to step 495. In step 495, the second CPU temporarily terminates this routine.

[0059] On the other hand, if the start-up conditions are met, the remote driving ECU 30 needs to perform remote driving control. In this case, the second CPU determines "yes" in step 405 and executes steps 410 to 425.

[0060] Step 410: The second CPU sets the execution flag Xexe to "1".

[0061] Step 415: The second CPU determines the path for the vehicle VA to exit the parking space.

[0062] Specifically, the second CPU determines at least one parking space where the vehicle VA can park, based on images of the area surrounding the vehicle VA taken by a camera (not shown) mounted on the vehicle VA. Then, the second CPU determines at least one path from the parking space to each parking space based on the aforementioned images.

[0063] Step 420: The second CPU sends the planning data, including the path determined in step 415, to the mobile terminal SP via the first communication.

[0064] Step 425: The second CPU determines whether the device 10 has received selection data from the mobile terminal SP through the first communication.

[0065] Upon receiving the selection data, the second CPU determines "yes" in step 425 and proceeds to step 430. In step 430, the second CPU determines the driving path based on the user-selected route. Additionally, the second CPU determines the target space based on the parking space along the user-selected route. Then, the process proceeds to step 495.

[0066] On the other hand, if the device 10 does not receive selection data, the second CPU determines "no" in step 425 and executes step 425 again. Furthermore, if the state of the device 10 not receiving selection data continues for more than a predetermined time, the second CPU can cancel remote driving control by setting the execution flag Xexe to "0".

[0067] <Remote Driving Control Routine>

[0068] The second CPU executes at regular intervals. Figure 5 The routine shown in the flowchart.

[0069] If the appropriate time arrives, the second CPU will begin processing from step 500, proceeding to step 505. In step 505, the second CPU determines whether the execution flag Xexe is "1".

[0070] If the execution flag Xexe is "0", the second CPU determines "No" in step 505 and proceeds to step 595. In step 595, the second CPU temporarily terminates the current routine.

[0071] On the other hand, if the execution flag Xexe is "1", the second CPU determines "yes" in step 505 and proceeds to step 510. In step 510, the second CPU determines whether the vehicle VA has arrived at the target space.

[0072] If the vehicle VA has not reached the target space, the second CPU determines "no" in step 510 and proceeds to step 515. In step 515, the second CPU determines whether the device 10 has received a driving instruction from the mobile terminal SP through the first communication.

[0073] When the device 10 receives a driving instruction, the second CPU determines "yes" in step 515 and proceeds to step 520. In step 520, the second CPU controls the powertrain actuator 32, the brake actuator 34, and the steering motor 36 to make the vehicle VA travel along the driving path. Then, the process proceeds to step 595.

[0074] On the other hand, if the device 10 does not receive a driving instruction, the second CPU determines "no" in step 515 and proceeds to step 525. In step 525, the second CPU determines whether the non-reception time indicating that the device 10 has not received a driving instruction is above the prescribed termination threshold time Tend.

[0075] If the non-receiving time is less than the termination threshold time Tend, the second CPU determines "No" in step 525 and proceeds to step 530. In step 530, the second CPU controls the powertrain actuator 32 and the brake actuator 34 to decelerate the vehicle VA at a predetermined deceleration. Then, the process proceeds to step 595.

[0076] If the non-receiving time is above the termination threshold time Tend, the second CPU determines "yes" in step 525 and proceeds to step 535. In step 535, the second CPU sets the execution flag Xexe to "0". Then, the process proceeds to step 595.

[0077] According to this embodiment, when the activation conditions of the device 10 are met, first communication is established and the remote driving ECU 30 is activated. The activation conditions are receiving activation data and the distance D being less than or equal to a threshold distance Dth. This shortens the time until the remote driving ECU 30 can perform remote driving control.

[0078] Furthermore, if the remote driving application 14 is launched, the mobile terminal SP sends launch data. Therefore, the user can perform remote driving control simply by performing the operation to launch the remote driving application 14, without any other operation.

[0079] This invention is not limited to the above-described embodiments, and various modifications can be adopted within the scope of this invention.

[0080] The first CPU can determine that the startup condition is met if at least one of the following conditions is met: the first condition is that the device 10 receives startup data and the second condition is that the distance D is below the threshold distance Dth.

[0081] If the startup condition is met only when the first CPU determines that the second condition of the first and second conditions is met, the electronic key application 12 may not be installed in the mobile terminal SP. In this case, the functionality of the electronic key application 12 is installed in an electronic key terminal different from the mobile terminal SP. The electronic key terminal establishes first communication with the vehicle VA and sends and receives data.

[0082] The first communication and the second communication are not limited to Bluetooth (registered trademark) and BLE respectively; the first communication and the second communication can be any communication using different communication protocols.

[0083] This device 10 is applicable to vehicles such as engine-powered cars, hybrid electric vehicles, plug-in hybrid electric vehicles, fuel cell electric vehicles, and battery electric vehicles. Furthermore, remote driving control is a type of automated driving system used to assist the user's driving.

Claims

1. A remote driving device that causes a control unit to perform remote driving control, the remote driving control receiving a driving instruction via a first communication and causing a parked vehicle to drive toward a predetermined target space according to the driving instruction, the driving instruction being sent by the mobile terminal when a user located outside the vehicle performs a predetermined remote operation on the mobile terminal. The remote driving device is characterized by the following configuration: Even when the vehicle's power is off, communication can still be established with the mobile terminal or the electronic key terminal carried by the user for unlocking and locking the vehicle's doors via a second communication protocol different from the first communication protocol. When the vehicle power is off, the determination of whether the specified start-up conditions are met is based on the communication result of the second communication. When the startup conditions are met, the first communication is established, and the control unit is started by setting the vehicle power supply to the on state.

2. The remote driving device according to claim 1, characterized in that, The remote driving device is configured as follows: Even when the vehicle's power is off, it can still communicate with the mobile terminal via the second communication method. If startup data is received via the second communication, the startup condition is determined to be met. The startup data is sent by the mobile terminal when the remote driving application for enabling the remote driving device to perform the remote driving control is launched on the mobile terminal.

3. The remote driving device according to claim 1, characterized in that, The remote driving device is configured as follows: The distance between the user and the vehicle is determined based on the communication results of the second communication. If the distance becomes below the threshold distance, the activation condition is determined to be met.

4. A remote driving device that causes a control unit to perform remote driving control, the remote driving control receiving a driving instruction via a first communication and causing a parked vehicle to drive toward a predetermined target space according to the driving instruction, the driving instruction being sent by the mobile terminal when a user located outside the vehicle performs a predetermined remote operation on the mobile terminal. The remote driving device is characterized by the following configuration: It can communicate with the mobile terminal or the electronic key terminal carried by the user for unlocking and locking the vehicle doors via a second communication protocol different from the first communication protocol. The determination of whether the specified startup conditions are met is based on the communication results of the second communication. If the startup conditions are met, the first communication is established.

Citation Information

Patent Citations

  • Vehicle control system and vehicle

    JP2022048453A