Mobile support device

The mobility support device uses dual communication protocols to verify matching IDs from smartphones and electronic keys, ensuring only intended vehicles are moved by preventing control execution when IDs do not match, thus reducing the risk of moving unintended vehicles.

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

Patent Information

Application Number
JP2025078587
Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
Filing Date
2025-05-09
Publication Date
2026-11-19

AI Technical Summary

Technical Problem

Existing vehicle mobility assistance systems risk moving unintended vehicles due to successful smartphone-electronic key ID matching with nearby vehicles, even if the user intends to move a different vehicle.

Method used

Implementing a mobility support device that uses dual communication protocols (e.g., Bluetooth and Bluetooth Low Energy) to verify matching IDs from both a smartphone and electronic key, ensuring successful verification allows mobility assistance control only when both IDs match, and prohibiting it otherwise.

Benefits of technology

Reduces the likelihood of unintended vehicles being moved by ensuring that mobility assistance control is only executed when both smartphone and electronic key IDs correctly match, thereby preventing incorrect vehicle movement.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 2026182387000001_ABST
    Figure 2026182387000001_ABST
Patent Text Reader

Abstract

The present invention provides a mobility assistance device that can reduce the possibility of vehicles other than the vehicle the user intends to move moving. [Solution] The mobility support device is installed in the vehicle and performs mobility support control to move the vehicle in response to user operation on the mobility instruction device. The mobility support device establishes a first communication with the mobility instruction device and a second communication with an electronic key, which has a different communication protocol from the first communication. Based on the first verification information received from the mobility instruction device via the first communication and the second verification information received from the electronic key via the second communication, the device performs verification. If the verification is successful, it permits the execution of mobility support control; if the verification fails, it prohibits the execution of mobility support control.
Need to check novelty before this filing date? Find Prior Art

Description

TECHNICAL FIELD

[0001] The present invention relates to a movement assistance device that executes movement assistance control for moving a vehicle in response to a user's operation on a movement instruction device.

BACKGROUND ART

[0002] Conventionally, a movement assistance device that executes movement assistance control for moving a vehicle in response to a user's operation on a movement instruction device is known. For example, the movement assistance device described in Patent Document 1 (hereinafter referred to as "conventional device") has a registration table in which a smartphone ID of a smartphone and an electronic key ID of an electronic key are associated in advance. The conventional device collates the smartphone ID of the smartphone with the electronic key ID of the electronic key located outside the vehicle. According to the conventional device, when the collation is successful, the smartphone enters a state capable of accepting a movement assistance operation for moving the vehicle (that is, the conventional device permits execution of the movement assistance control). On the other hand, when the collation fails, the smartphone enters a state in which it does not accept the movement assistance operation (that is, the conventional device prohibits execution of the movement assistance control).

PRIOR ART DOCUMENTS

PATENT DOCUMENTS

[0003]

PATENT DOCUMENT 1

SUMMARY OF THE INVENTION

[0004] In recent years, it has become possible for a single user to use multiple vehicles with the same electronic key. In this case, the same smartphone ID and electronic key ID of this user are pre-associated with each of the vehicle's vehicle mobility assistance system registration tables. Let's assume that these multiple vehicles are parked close together, and a user carrying a smartphone and electronic key with the ID registered in the registration table is near these vehicles. There is a possibility that the smartphone may connect to a vehicle other than the vehicle the user intends to move (the vehicle to be moved). The conventional system of the vehicle to which the smartphone is connected will successfully match the user. When the user issues a movement command operation via smartphone, there is a possibility that a vehicle other than the intended vehicle will be moved.

[0005] This invention was made to address the aforementioned problems. Specifically, one of the objectives of this invention is to provide a mobility assistance device that can reduce the possibility of a vehicle other than the vehicle that the user intends to move moving.

[0006] The mobility support device of the present invention (hereinafter referred to as "the present invention device") is installed in a vehicle (VA) and performs mobility support control to move the vehicle in response to operations performed by the user on a mobility instruction device (SP). The aforementioned mobility support device is, A first communication is established with the movement instruction device, A second communication, which has a different communication protocol from the first communication, is established between the electronic key and the electronic key. Verification is performed based on the first verification information received from the movement instruction device via the first communication and the second verification information received from the electronic key via the second communication (steps 330, 510, 525, 535, and 540). If the verification is successful (step 335 "Yes"), the execution of the mobility assistance control is permitted (step 360), If the verification fails (step 335 "No"), the execution of the mobility support control is prohibited (step 340). It is structured in this way.

[0007] The present invention performs verification based on first verification information received via first communication and second verification information received via second communication using a different communication protocol than the first communication. If the verification is successful, the present invention permits the execution of mobility support control; if the verification fails, it prohibits the execution of mobility support control. As a result, even if the first communication is connected to a vehicle other than the vehicle to be moved, the verification will fail in the vehicle other than the vehicle to be moved, and the execution of mobility support control will be prohibited. Therefore, the possibility of a vehicle other than the vehicle to be moved being moved by mobility support control can be reduced. [Brief explanation of the drawing]

[0008] [Figure 1] This is a schematic system configuration diagram of a mobility support device and a smartphone according to an embodiment of the present invention. [Figure 2] This is an explanatory diagram illustrating an example of the operation of a mobility support device according to an embodiment of the present invention. [Figure 3] Figure 1 is a flowchart of the mobility assistance control authorization routine executed by the CPU of the ECU. [Figure 4] Figure 1 is a flowchart of the electronic key identification subroutine executed by the CPU of the ECU. [Figure 5] Figure 1 is a flowchart of the ID verification subroutine executed by the CPU of the ECU. [Modes for carrying out the invention]

[0009] As shown in Figure 1, the mobility support device 10 according to this embodiment (hereinafter referred to as "the device 10") is applied to a vehicle VA. The device 10 transmits and receives data with a smartphone SP operated by the user via first communication and second communication. For example, the first communication is Bluetooth®, and the second communication is Bluetooth® Low Energy (hereinafter referred to as "BLE").

[0010] The device 10 comprises the components shown in Figure 1. In this specification, "ECU30" is an electronic control device that primarily comprises a microcomputer. The ECU30 is also referred to as a control unit, controller, and computer. The microcomputer includes a CPU (processor), ROM, RAM, and interface (I / F), etc. The functions realized by the ECU30 may be realized by multiple ECUs.

[0011] The first communication interface (I / F) 22 is an interface for sending and receiving data with the smartphone SP via the first communication. The second communication interface (I / F) 24 is an interface for sending and receiving data with the smartphone SP via the second communication.

[0012] Camera 36 acquires image data by photographing the scenery around the vehicle VA. ECU 30 acquires image data from camera 36. Sonar 38 acquires sonar data representing the position of objects relative to the vehicle VA by scanning the environment around the vehicle VA. ECU 30 acquires sonar data from sonar 38.

[0013] The vehicle speed sensor 40 measures the vehicle speed Vs, which represents the speed of the vehicle VA. The steering angle sensor 42 measures the steering angle θ of the steering wheels of the vehicle VA. The ECU 30 acquires the measurements from these sensors 40 and 42.

[0014] The powertrain actuator 44 modifies the driving force generated by the vehicle VA's drive system (e.g., internal combustion engine and / or electric motor). The brake actuator 46 controls the braking force applied to the vehicle VA. The steering motor 48 is incorporated into the steering mechanism 49. The steering mechanism 49 is a mechanism for steering the steering wheels in response to the operation of the steering wheel. Furthermore, the steering motor 48 generates an automatic steering torque in the steering mechanism 49 to change the steering angle of the steering wheels in response to instructions from the ECU 30.

[0015] The smartphone SP includes the components shown in Figure 1. The first communication interface (I / F) 52 is an interface for transmitting and receiving data to and from the present apparatus 10 via first communication. The second communication interface (I / F) 54 is an interface for transmitting and receiving data to and from the present apparatus 10 via second communication.

[0016] A movement support application 56 and an electronic key application 58 are installed on the smartphone SP, and a CPU (not shown) of the smartphone SP executes these applications 56 and 58.

[0017] A first verification ID is set in the movement support application 56, and a second verification ID is set in the electronic key application 58. The movement support application 56 transmits the first verification ID to the movement support apparatus 10 via the first communication I / F 52 (that is, the first communication). The electronic key application 58 transmits the second verification ID to the movement support apparatus 10 via the second communication I / F (that is, the second communication). In the present embodiment, the same ID is used as the first verification ID and the second verification ID. For example, a vehicle ID for identifying the vehicle VA is used as the first verification ID and the second verification ID. Note that the first verification ID and the second verification ID may be referred to as first verification information and second verification information, respectively.

[0018] The display device 60 is a touch panel type display. The display device 60 displays various screens. A user can perform various inputs by touching the screens displayed on the display device 60.

[0019] <Establishment of First Communication> Once the smartphone SP and the vehicle VA are paired, the first communication is established when the smartphone SP approaches the vehicle VA. <Establishment of Second Communication> For example, the smartphone SP transmits an advertising packet including a smartphone ID representing the identifier of the smartphone at a predetermined cycle. When the vehicle VA detects the smartphone SP by receiving the advertising packet, it transmits a connection request to the smartphone SP. When the smartphone SP receives the connection request, the second communication is established. When the second communication is established, the smartphone SP transmits the second verification ID at a predetermined cycle until a success notification or a failure notification described later is received.

[0020] <Movement support control> When the movement support application 56 is activated on the smartphone SP, the smartphone SP displays a selection screen for selecting a "vehicle to be moved (hereinafter referred to as the 'movement target vehicle')" on the display device 60. When the user selects the movement target vehicle on the selection screen, the smartphone SP transmits a verification request to the movement target vehicle via the first communication. The smartphone SP transmits the first verification ID at a predetermined cycle from when the verification request is transmitted until a success notification or a failure notification described later is received.

[0021] The ECU 30 performs verification based on the first verification ID and the second verification ID, and when the verification is successful, permits execution of the movement support control and executes the movement support control. In the movement support control, the ECU 30 automatically moves the vehicle VA to the destination in response to a predetermined movement instruction operation performed by the user outside the vehicle on the smartphone SP. Examples of the movement support control include parking support control that automatically parks the vehicle VA in a parking space while the user is outside the vehicle, and exit support control that automatically moves the parked vehicle VA out to an exit space while the user is outside the vehicle. Note that the device with which the user performs the movement support operation (the smartphone SP in this example) may be referred to as a "movement instruction device".

[0022] When mobility assistance control is performed, a control screen with an operation input area is displayed on the display device 60 of the smartphone SP. When the user moves their finger touching the operation input area, the smartphone SP (mobility assistance application 56) determines that a movement instruction operation has been performed and transmits the movement instruction to this device 10. As long as the ECU 30 has received the movement instruction, it moves the vehicle VA toward the destination. Specifically, when mobility assistance control is started, the ECU 30 sets a route to the destination. The ECU 30 controls the steering motor 48 so that the vehicle VA travels along the route. Furthermore, the ECU 30 controls the powertrain actuator 44 and brake actuator 46 so that the acceleration G matches a target acceleration Gtgt such that the vehicle speed Vs is less than or equal to a preset vehicle speed. During the execution of mobility assistance control, if the ECU 30 determines, based on image data and sonar data, that there is an object that is in contact with the vehicle VA, it will stop the vehicle VA or drive to avoid that object.

[0023] (Summary of operation) The ECU30 permits the execution of mobility assistance control if the matching is successful, and prohibits the execution of mobility assistance control if the matching fails. Specifically, the ECU30 determines that the matching is successful if the first matching ID and the second matching ID are the same.

[0024] If the destination of the first communication and the destination of the second communication are different, the device 10 will not receive either the first or second verification ID. Therefore, the ECU 30 will determine that the verification has failed and will prohibit the execution of the mobility assistance control. Consequently, even if the first or second communication is connected to a vehicle other than the vehicle to be moved, the device 10 applied to that vehicle will prohibit the execution of the mobility assistance control. This reduces the possibility that a vehicle other than the vehicle to be moved may be moved by the mobility assistance control.

[0025] (Example of operation) An example of the operation of this device 10 will be explained with reference to Figure 2. In Figure 2, users A and B are located near vehicles VAa and VAb. User A is granted control over both vehicles VAa and VAb, while user B is granted control over only vehicle VAb.

[0026] First, let's explain an example where only user A is located near vehicles VAa and VAb, and user B is not located near vehicles VAa and VAb. A second communication is established between user A's smartphone SPa and vehicle VAa, and a first communication is established between smartphone SPa and vehicle VAb. Vehicle VAb receives a first matching ID ("A") from smartphone SPb via the first communication. Vehicle VAa receives a second matching ID ("A") from smartphone SPa via the second communication.

[0027] When user A selects vehicle VAa as the vehicle to be moved, smartphone SPa sends a matching request to vehicle VAb via the first communication. Since vehicle VAb has not received the second matching ID, the matching fails in vehicle VAb's mobility support device 10. Therefore, even if the first communication is established between vehicle VAb, which is different from the vehicle to be moved VAa, the matching fails in vehicle VAb. As a result, the execution of mobility support control is prohibited in vehicle VAb, thus reducing the possibility of vehicle VAb moving due to mobility support control.

[0028] Furthermore, since vehicle VAa has not received the first matching ID, even if it receives a matching request from a smartphone other than user A's smartphone SPa, the matching will fail. Therefore, the execution of mobility assistance control is prohibited for vehicle VAa, thus reducing the possibility of vehicle VAa moving due to mobility assistance control.

[0029] Next, we will describe an example where users A and B are located near vehicles VAa and VAb. In this case, as in the example above, a second communication is established between smartphone SPa and vehicle VAa, and a first communication is established between smartphone SPa and vehicle VAb. Furthermore, a second communication is established between user B's smartphone SPb and vehicle VAb. Smartphone SPa sends a matching request to vehicle VAb via the first communication.

[0030] In this case, vehicle VAb receives a second matching ID ("B") from smartphone SPb via the second communication and a first matching ID ("A") from smartphone SPa via the first communication. The first matching ID ("A") received by vehicle VAb is different from the second matching ID ("B"). Therefore, the matching fails in the vehicle VAb's mobility support device 10. As a result, the execution of mobility support control is prohibited in vehicle VAa, thus reducing the possibility that vehicle VAb, which is different from the vehicle VAa being moved, will be moved by mobility support control.

[0031] Similar to the example described above, since vehicle VAa does not receive the second matching ID, the matching fails in vehicle VAa's mobility support device 10, and the execution of mobility support control is prohibited in vehicle VAa.

[0032] (Specific operation) The CPU of ECU30 executes the routine shown in the flowchart in Figure 3 at predetermined intervals.

[0033] <Mobility Assistance Control Permission Routine> When the appropriate time arrives, the CPU starts processing from step 300 in Figure 3, and the process proceeds to step 305. In step 305, the CPU determines whether the specific flag Xver is "0". The specific flag Xver is set to "1" if the identification of the electronic key is successful, and to "0" if the identification of the electronic key fails. The identification of the electronic key is explained in detail in Figure 4. The specific flag Xver is set to "0" in the initialization routine. The initialization routine is executed by the CPU when the ignition key switch (not shown) of the vehicle VA is changed from the off position to the on position.

[0034] If the specific flag Xver is "0", the CPU determines "Yes" in step 305, and the process proceeds to step 310. In step 310, the CPU determines whether the device 10 has received a verification request from the smartphone SP.

[0035] If device 10 has not received a verification request, the CPU determines "No" in step 310, and the process proceeds to step 395. In step 395, the CPU terminates this routine.

[0036] On the other hand, if the device 10 receives a verification request, the CPU determines "Yes" in step 310 and executes steps 315 and 320. Step 315: The CPU executes an electronic key identification subroutine to identify the electronic key. Details of the electronic key identification subroutine are explained in Figure 4. Step 320: The CPU determines whether the electronic key identification subroutine was successful or not.

[0037] If the electronic key is successfully identified, the CPU determines "Yes" in step 320 and executes steps 325 through 335. Step 325: The CPU sets the specific flag Xver to "1", sets Timer T to "0", and sets the first receive flag Xrec1 and the second receive flag Xrec2 to "0". Timer T is a timer used to count the time elapsed since the successful identification of the electronic key but before the matching process was successful. The first receive flag Xrec1 is set to "1" when the first matching ID is received. The second receive flag Xrec2 is set to "1" when the second matching ID is received.

[0038] Step 330: The CPU executes an ID matching subroutine to perform matching based on the first matching ID and the second matching ID. Details of the ID matching subroutine are explained in Figure 5.

[0039] Step 335: The CPU determines whether the ID matching was successful using the ID matching subroutine.

[0040] If the matching fails, the CPU determines "No" in step 335, and the process proceeds to step 340. In step 340, the CPU prohibits the execution of movement assistance control and sets the specific flag Xver to "0". After that, the process proceeds to step 395, and the CPU terminates this routine.

[0041] If the specific flag Xver is "1" when the process proceeds to step 305, the CPU determines "No" in step 305 and executes steps 345 and 350. Step 345: The CPU adds "1" to Timer T. Step 350: The CPU determines whether timer T is greater than or equal to the threshold Tth.

[0042] If timer T is less than threshold Tth, the CPU determines "No" in step 350, and the process proceeds to step 330. If the matching is successful when the process proceeds to step 335, the CPU determines "Yes" in step 335, and executes steps 355 and 360.

[0043] Step 355: The CPU sends a success notification to the smartphone SP via the first communication. When the smartphone SP receives a success notification, it informs the user that the vehicle to be moved can now be moved due to successful matching. For example, the smartphone SP displays a screen on the display device 60 indicating that the vehicle to be moved can now be moved due to successful matching.

[0044] Step 360: The CPU authorizes the execution of mobility assistance control and sets the specific flag Xver to "0". The process then proceeds to step 395.

[0045] If the timer T is greater than or equal to the threshold Tth when the process proceeds to step 350, the CPU determines "Yes" in step 350, and the process proceeds to step 365. In step 365, the CPU sends a failure notification to the smartphone SP via the first communication and sets the specific flag Xver to "0". After that, the process proceeds to step 395.

[0046] In detail, the first failure condition is met when the first reception flag Xrec1 is "1" and the second reception flag Xrec2 is "0". In this case, the CPU sends a first failure notification to the smartphone SP. When the smartphone SP receives the first failure notification, it informs the user that the matching failed because the first failure condition was met (i.e., that the second matching ID was not received despite the first matching ID being received). For example, the smartphone SP displays a screen to that effect on the display device 60.

[0047] The second failure condition is met when the first reception flag Xrec1 is "0" and the second reception flag Xrec2 is "1". In this case, the CPU sends a second failure notification to the smartphone SP. When the smartphone SP receives the second failure notification, it informs the user that the matching failed because the second failure condition was met (i.e., that the second matching ID was received but the first matching ID was not).

[0048] If both the first reception flag Xrec1 and the second reception flag Xrec2 are "0", the third failure condition is met. In this case, the CPU sends a third failure notification to the smartphone SP. When the smartphone SP receives the third failure notification, it informs the user that the matching failed because the third failure condition was met (i.e., that neither the first matching ID nor the second matching ID was received).

[0049] On the other hand, if the identification of the electronic key fails when the process proceeds to step 320, the CPU determines that the matching has failed. In this case, the CPU determines "No" in step 320, and the process proceeds to step 340.

[0050] <Electronic Key Identification Subroutine>

[0051] When the process proceeds to step 320, the CPU starts processing from step 400 in Figure 4, and the process proceeds to step 405. In step 405, the CPU determines whether an electronic key implemented in a smartphone different from the smartphone SP that sent the verification request (hereinafter referred to as "the other electronic key") has already been identified. The verification request includes the smartphone ID. Specifically, the CPU stores the smartphone ID, which indicates the identifier of the smartphone of the electronic key that was successfully identified. If the CPU stores a smartphone ID different from the smartphone ID of the smartphone that sent the verification request, it determines that the other electronic key has already been identified.

[0052] If another electronic key has already been identified, the smartphone SP that sent the matching request cannot execute mobility assistance control. In this case, the CPU determines that it has failed to identify the electronic key. The CPU also determines that the matching has failed if it has failed to identify the electronic key. If another electronic key has already been identified, the CPU determines that the first identification failure condition has been met and determines "No" in step 405. The process then proceeds to step 410. In step 410, the CPU sends a first identification failure notification to the smartphone SP via the first communication. When the smartphone SP receives the first identification failure notification, it informs the user that the matching has failed because the first identification failure condition has been met. The process then proceeds to step 495, and the CPU terminates this routine and proceeds to step 320 shown in Figure 3.

[0053] On the other hand, if no other electronic key has already been identified, the CPU determines "No" in step 405, and the process proceeds to step 410. In step 410, the CPU determines whether the electronic key implemented in the smartphone SP that sent the verification request is authorized for mobility assistance control. Specifically, the device 10 pre-registers authorization information that associates an electronic key ID with information indicating whether the electronic key identified by that electronic key ID is authorized for mobility assistance control. When a second communication is established, the CPU refers to the authorization information and determines whether the electronic key to which the second communication is connected is authorized for mobility assistance control.

[0054] If the electronic key is authorized to perform mobility assistance control, the user of that electronic key cannot perform mobility assistance control. In this case, the CPU determines that the second identification failure condition has been met and that the identification of the electronic key has failed. Specifically, the CPU determines "Yes" in step 410. The process then proceeds to step 415. In step 415, the CPU sends a second identification failure notification to the smartphone SP via the first communication. When the smartphone SP receives the second identification failure notification, it informs the user that the matching failed because the second identification failure condition has been met. The process then proceeds to step 495.

[0055] On the other hand, when the authority for movement assistance control is granted to the electronic key, the CPU makes a "No" determination in step 410, and executes step 420 and step 425. Step 420: The CPU acquires the distance D to the electronic key installed in the smartphone SP that has transmitted the verification request, based on the second communication. Step 425: The CPU determines whether the distance D is equal to or less than a threshold distance Dth.

[0056] When the distance D is longer than the threshold distance Dth, the CPU determines that the third identification failure condition is satisfied, and determines that the identification of the electronic key has failed. Specifically, the CPU makes a "No" determination in step 425. Thereafter, the process proceeds to step 430. In step 430, the CPU transmits a third identification failure notification to the smartphone SP via the first communication. When receiving the third identification failure notification, the smartphone SP notifies the user that the verification has failed because the third identification failure condition is satisfied. Thereafter, the process proceeds to step 495.

[0057] On the other hand, when the distance D is equal to or less than the threshold distance Dth, the CPU makes a "Yes" determination in step 425, and the process proceeds to step 435. In step 435, the CPU determines that the identification of the electronic key has succeeded. Thereafter, the process proceeds to step 495.

[0058] <ID verification subroutine> When the process proceeds to step 330, the CPU starts the process from step 500 in FIG. 5, and the process proceeds to step 505. In step 505, it is determined whether or not the first reception flag Xrec1 is "0".

[0059] When the first reception flag Xrec1 is "0", the CPU makes a "Yes" determination in step 505, and the process proceeds to step 510. In step 510, the CPU determines whether or not the present device 10 has already received the first verification ID.

[0060] If device 10 has already received the first matching ID, the CPU determines "Yes" in step 510, and the process proceeds to step 515. In step 515, the CPU sets the first reception flag Xrec1 to "1". The process then proceeds to step 520.

[0061] If the first reception flag Xrec1 is "1", the CPU determines "No" in step 505 and proceeds to step 520. If the device 10 has not yet received the first matching ID, the CPU determines "No" in step 510 and proceeds to step 520.

[0062] In step 520, the CPU determines whether the second receive flag Xrec2 is "0". If the second receive flag Xrec2 is "0", the CPU determines "Yes" in step 520, and the process proceeds to step 525. In step 525, the CPU determines whether the device 10 has already received the second matching ID.

[0063] If device 10 has already received the second verification ID, the CPU determines "Yes" in step 525, and the process proceeds to step 530. In step 530, the CPU sets the second reception flag Xrec2 to "1". After that, the process proceeds to step 530.

[0064] If the second reception flag Xrec2 is "1", the CPU determines "No" in step 520, and the process proceeds to step 535. If the device 10 has not yet received the second matching ID, the CPU determines "No" in step 525, and the process proceeds to step 535.

[0065] In step 535, the CPU determines whether both the first receive flag Xrec1 and the second receive flag Xrec2 are "1". If both the first receive flag Xrec1 and the second receive flag Xrec2 are "1", the CPU determines "Yes" in step 535 and proceeds to step 540.

[0066] In step 540, the CPU determines whether the first matching ID is the same as the second matching ID. If the first matching ID is the same as the second matching ID, the CPU determines "Yes" in step 540, and the process proceeds to step 545. In step 545, the CPU determines that the matching was successful. The process then proceeds to step 595, where the CPU terminates this routine and proceeds to step 335 as shown in Figure 3.

[0067] On the other hand, if the first matching ID is different from the second matching ID, the fourth failure condition is met. In this case, the CPU determines "No" in step 540, and the process proceeds to step 550. In step 550, the CPU sends a fourth failure notification to the smartphone SP via the first communication. When the smartphone SP receives the fourth failure notification, it informs the user that the matching failed because the fourth failure condition was met (i.e., that the first matching ID is different from the second matching ID). The process then proceeds to step 595.

[0068] If at least one of the first receive flag Xrec1 and the second receive flag Xrec2 is "0" when the process proceeds to step 535, the CPU determines "No" in step 535 and the process proceeds to step 595.

[0069] As described above, the device 10 performs verification based on the first verification ID received via the first communication and the second verification ID received via the second communication using a different communication protocol than the first communication. If the verification is successful, the device 10 permits the execution of mobility assistance control; if the verification fails, it prohibits the execution of mobility assistance control. As a result, even if the first communication is connected to a vehicle other than the vehicle to be moved, the verification will fail in the vehicle other than the vehicle to be moved, and the execution of mobility assistance control will be prohibited. Therefore, the possibility of a vehicle other than the vehicle to be moved being moved by mobility assistance control can be reduced.

[0070] Furthermore, if the matching fails, the device 10 will inform the user of the reason for the matching failure, thereby increasing the likelihood that the user will take appropriate action according to the cause of the failure.

[0071] The present invention is not limited to the embodiments described above, and various modifications can be adopted within the scope of the present invention. The first and second communications are not limited to Bluetooth® and BLE, respectively; the first and second communications may use different communication protocols.

[0072] The electronic key app 58 was implemented in the mobile instruction device (smartphone SP), but it may be implemented in a different device from the mobile instruction device, as long as it is a device carried by the user.

[0073] In the above embodiment, the mobility support application 56 and the electronic key application 58 of the smartphone SP transmitted the same matching ID, but they may transmit different matching IDs. In this case, the mobility support device 10 needs to have a matching ID table that registers the correspondence between the first matching ID transmitted by the mobility support application 56 and the second matching ID transmitted by the electronic key application 58. The mobility support device 10 refers to the matching ID table and determines that the matching is successful if it determines that the received first matching ID and the received second matching ID have a correspondence.

[0074] This device 10 is applicable to vehicles such as engine-powered vehicles, hybrid vehicles, plug-in hybrid vehicles, fuel cell vehicles, and electric vehicles. Mobility assistance control is a type of autonomous driving that assists the user in driving. [Explanation of symbols]

[0075] 10...Mobility support device, 30...ECU, 32...First communication interface, 34...Second communication interface, 52...First communication interface, 54...Second communication interface, 56...Mobility support app, 58...Electronic key app, SP...Smartphone.

Claims

1. In a mobility support device that is installed in a vehicle and performs mobility support control to move the vehicle in response to user operation of a movement instruction device, The aforementioned mobility support device is A first communication is established with the movement instruction device, A second communication, with a different communication protocol from the first communication, is established between the electronic key and the electronic key. Verification is performed based on the first verification information received from the movement instruction device via the first communication and the second verification information received from the electronic key via the second communication. If the verification is successful, the execution of the mobility support control is permitted. If the aforementioned verification fails, the execution of the mobility support control is prohibited. A mobility support device configured in such a way.

2. In the mobility support device according to claim 1, The electronic key is mounted on the movement instruction device. The same information is transmitted as the first matching information and the second matching information. The mobility support device is configured to determine that the matching is successful if the first matching information and the second matching information are the same. Mobility support equipment.

3. In the mobility support device according to claim 2, The aforementioned mobility support device is If the matching fails, a failure notification is provided in a manner that allows the user to identify the cause of the matching failure. A mobility support device configured in such a way.

4. In the mobility support device according to claim 3, The aforementioned mobility support device is The first failure condition is that the first matching information has been received but the second matching information has not been received. The second failure condition is that the first matching information has not been received despite the second matching information being received. A third failure condition is that neither the first matching information nor the second matching information has been received, and A fourth failure condition occurs when, despite receiving both the first and second matching information, the first and second matching information are different. If any one of the following conditions is met, the verification fails. If the matching fails, the failure notification is provided in a manner that allows the user to identify which of the first to fourth failure conditions was met that caused the matching to fail. A mobility support device configured in such a way.

5. In the mobility support device according to claim 4, The aforementioned mobility support device is The first identification failure condition is that the vehicle has already identified another electronic key. A second specific failure condition is that the electronic key does not have the authority to execute the mobility assistance control, and The third specific failure condition is that the electronic key is not located within a predetermined distance from the vehicle. If any one of the above conditions is met, the verification will fail. The failure notification is provided in a manner that allows the user to identify which of the first to third specified failure conditions has been met, causing the verification to fail. A mobility support device configured in such a way.

Citation Information

Patent Citations

  • Vehicle, information processing device, parking support method, information processing method and program

    JP2023101336A