Information processing apparatus, vehicle, information processing method, and recording medium

Abstract

The present application relates to an information processing device, a vehicle, an information processing method, and a recording medium recording a program, the information processing device including: an acceptance unit (130) that accepts a user operation for disabling a vehicle control function related to a first key that can be used to control a vehicle; a confirmation unit (132) that confirms whether or not a predetermined communication with a second key that is a key different from the first key among keys that can be used to control the vehicle is possible; and a processing unit (134) that performs processing for suppressing the disabling of the vehicle control function related to the first key corresponding to the user operation, in a case where the confirmation unit cannot confirm that the predetermined communication with the second key is possible.

Description

Technical Field

[0001] This disclosure relates to an information processing device, a vehicle equipped with the information processing device, an information processing method, and a procedure. Background Technology

[0002] Japanese Patent Application Publication No. 2014-054902 discloses a notification device that informs a user that a mobile terminal is being used as a vehicle key. In this device, when a smartphone is used as a vehicle key, the user is notified that it is being used as a vehicle key. The device displays the message "Smartphone is being used as a vehicle key" along with a picture of the smartphone, and also displays a message to prevent the smartphone from being taken away.

[0003] In recent years, technologies have emerged that use digital keys registered on smartphones to control vehicles, such as locking, unlocking, and starting the engine.

[0004] Here, we consider disabling the digital key function in the vehicle by having the user configure the vehicle settings. In this case, if the user only has a smartphone, they will be unable to lock and unlock the vehicle, start the engine, or perform other vehicle controls, which could lead to problems. Summary of the Invention

[0005] The purpose of this disclosure is to suppress the occurrence of adverse conditions even if the vehicle control functions involved in the key are disabled.

[0006] The first method is an information processing device comprising: a receiving unit that receives a user operation to disable a vehicle control function related to a first key that can be used to control a vehicle; a confirmation unit that confirms whether a specified communication can be established with a second key, which is a key different from the first key that can be used to control the vehicle; and a processing unit that, if the confirmation unit cannot confirm the specified communication with the second key, performs processing to suppress the disabling of the vehicle control function related to the first key corresponding to the user operation.

[0007] In the information processing device of the first method, the confirmation unit confirms whether the prescribed communication can be established with the second key, which is a key different from the first key used to control the vehicle. Furthermore, if the confirmation unit cannot confirm the prescribed communication with the second key, the processing unit performs processing to suppress the invalidation of vehicle control functions related to the first key corresponding to the user operation. Here, "vehicle control functions related to the key" refers to functions that control the vehicle through key operation, such as locking and unlocking the opening and closing mechanism, power on / off, and engine start. According to this information processing device, even if the vehicle control functions related to the key are invalidated, the occurrence of adverse conditions can be suppressed.

[0008] The information processing device of the second method is completed based on the information processing device of the first method, and the receiving unit accepts the pressing operation of the button installed in the vehicle among the buttons for invalidating the vehicle control function involved in the first key.

[0009] The second type of information processing device disables the vehicle control functions associated with the first key by accepting the pressing operation of a button located inside the vehicle. According to this information processing device, the vehicle control functions associated with the key can be easily disabled.

[0010] The information processing device of the third method is completed based on the information processing device of the first method, and the aforementioned receiving unit accepts user operations on the user interface displayed on the display unit for invalidating the vehicle control functions involved in the aforementioned first key.

[0011] The third type of information processing device disables the vehicle control functions related to the first key by accepting user operations on the user interface displayed on the display unit. According to this information processing device, the vehicle control functions related to the key can be easily disabled.

[0012] The information processing device of the fourth method is completed based on the information processing device of the third method. If the above-mentioned confirmation unit cannot confirm the above-mentioned communication with the second key as specified above, the processing unit controls the user operation to be unacceptable in the user interface.

[0013] In the information processing device of the fourth method, if the specified communication with the second key cannot be confirmed, the user operation is controlled to be unacceptable in the user interface. According to this information processing device, in the event that the specified communication with the second key cannot be confirmed, the invalidation of the vehicle control function related to the first key corresponding to the user operation can be reliably prevented.

[0014] The information processing device of the fifth method is completed based on the information processing device of any of the methods 1 to 4. If the above-mentioned confirmation unit cannot confirm the above-mentioned communication with the second key as specified above, the above-mentioned processing unit reports a message indicating that the above-mentioned user operation cannot be accepted.

[0015] In the information processing device of the fifth method, when the prescribed communication with the second key cannot be confirmed, a message indicating that the user operation is not acceptable is reported. Thus, when the prescribed communication with the second key cannot be confirmed, the user can be notified that a user operation to disable the vehicle control function related to the first key corresponding to the user operation is not acceptable.

[0016] The information processing device of the sixth method is completed based on the information processing device of any of the methods 1 to 5. The confirmation unit confirms whether the communication specified above can be performed with the second key by comparing the identification information of the second key that can realize the above-specified communication in the vehicle with the identification information of the second key that was pre-registered.

[0017] In the information processing device of the sixth method, if the identification information of the second key capable of the aforementioned communication within the vehicle does not match the identification information of the pre-registered second key, it cannot be confirmed that the aforementioned communication with the second key is possible. According to this information processing device, when the identification information of the second key capable of the aforementioned communication within the vehicle does not match the identification information of the pre-registered second key, the invalidation of vehicle control functions related to the first key corresponding to user operation can be suppressed.

[0018] The information processing device of the seventh method is based on the information processing device of any of the methods 1 to 5. The confirmation unit confirms whether the above-mentioned communication can be performed with the second key by comparing the identification information of the second key that the user brings close to the proximity communication unit installed in the vehicle with the identification information of the second key that has been pre-registered.

[0019] In the information processing device of the seventh method, if the identification information of the second key, which the user brings close to the proximity communication unit installed in the vehicle, does not match the pre-registered identification information of the second key, it cannot be confirmed that the aforementioned communication with the second key is possible. According to this information processing device, when the identification information of the second key, which the user brings close to the proximity communication unit installed in the vehicle, does not match the pre-registered identification information of the second key, the invalidation of the vehicle control functions related to the first key corresponding to the user's operation can be suppressed.

[0020] The information processing device of the eighth method is completed based on the information processing device of any of the methods 1 to 5. The confirmation unit sends a response request signal to the pre-registered second key and confirms whether the above-mentioned communication can be performed with the second key based on whether a response signal from the second key is received.

[0021] In the information processing device of the eighth method, if a response request signal is sent to the pre-registered second key and no response signal is received from the second key, it cannot be confirmed that the aforementioned communication with the second key is possible. According to this information processing device, if a response request signal is sent to the pre-registered second key and no response signal is received from the second key, the invalidation of the vehicle control function related to the first key corresponding to the user operation can be suppressed.

[0022] The information processing device of the ninth method is completed based on the information processing device of any of the methods 1 to 5. The confirmation unit confirms whether the above-mentioned communication can be performed with the second key based on whether a signal transmitted from the pre-registered second key is received.

[0023] In the information processing device of the ninth method, if no signal is received from the pre-registered second key, it cannot be confirmed that the aforementioned communication with the second key is possible. According to this information processing device, in the absence of a signal received from the pre-registered second key, the invalidation of vehicle control functions related to the first key corresponding to user operation can be suppressed.

[0024] The tenth method is a vehicle equipped with: an information processing device of any one of the methods 1 to 9; and a locking unit for locking and unlocking the opening and closing parts that separate the interior and exterior of the vehicle.

[0025] The tenth method involves locking and unlocking the key-related opening and closing parts of the vehicle. According to this vehicle, even if the function of locking and unlocking the key-related opening and closing parts is disabled, the occurrence of adverse situations can be suppressed.

[0026] The 11th method is an information processing method in which a receiving unit receives a user operation to disable the vehicle control function of a first key that can be used to control the vehicle, and a confirmation unit confirms whether a specified communication can be made with a second key, which is a key that is different from the first key among the keys that can be used to control the vehicle. If the confirmation unit cannot confirm the specified communication with the second key, the processing unit performs processing to suppress the invalidation of the vehicle control function of the first key corresponding to the user operation.

[0027] In the information processing method of the eleventh method, the confirmation unit confirms whether the prescribed communication with the second key is possible. This second key is a key different from the first key used to control the vehicle. Furthermore, if the confirmation unit cannot confirm the prescribed communication with the second key, the processing unit performs processing to suppress the invalidation of vehicle control functions related to the first key corresponding to the user operation. According to this information processing method, even if the vehicle control functions related to the key are invalidated, the occurrence of adverse conditions can be suppressed.

[0028] The 12th method is a non-transitory recording medium that records a program for causing a computer to perform the following processing: accepting a user operation to disable the vehicle control function related to a first key that can be used to control the vehicle, confirming whether a specified communication can be made with a second key, which is a key that is different from the first key among the keys that can be used to control the vehicle, and if the specified communication with the second key cannot be confirmed, performing processing to suppress the disabling of the vehicle control function related to the first key corresponding to the user operation.

[0029] The program recorded in the non-transitory recording medium of the 12th method confirms whether the prescribed communication with the second key is possible. This second key is a different key from the first key used to control the vehicle. Furthermore, if the prescribed communication with the second key cannot be confirmed, a process is performed to suppress the vehicle control functions related to the first key corresponding to the user operation. According to this program, even if the vehicle control functions related to the key are disabled, the occurrence of adverse conditions can be suppressed.

[0030] According to this disclosure, even if the vehicle control functions involved in the key are disabled, the occurrence of adverse conditions can be suppressed. Attached Figure Description

[0031] Embodiments of this disclosure will be described in detail with reference to the following accompanying drawings, wherein:

[0032] Figure 1 This is a diagram showing a simplified structure of the vehicle system according to the first embodiment.

[0033] Figure 2 This is a block diagram illustrating the hardware structure of the vehicle according to the first embodiment.

[0034] Figure 3 This is a block diagram illustrating an example of the functional structure of the CPU of the physical key control ECU in the vehicle-mounted device of the first and second embodiments.

[0035] Figure 4 This is a block diagram illustrating an example of the functional structure of the CPU of the digital key control ECU in the vehicle-mounted device of the first embodiment.

[0036] Figure 5 This is a block diagram illustrating an example of the functional structure of the CPU of the control ECU in the vehicle-mounted device according to the first embodiment.

[0037] Figure 6 This is an example of a custom settings screen.

[0038] Figure 7 It is a block diagram representing the hardware structure of a physical key.

[0039] Figure 8 This is a block diagram showing the hardware structure of the smartphone according to the first embodiment.

[0040] Figure 9 This is a flowchart illustrating an example of the custom setting process executed in the CPU of the control ECU of the vehicle-mounted device in the first embodiment.

[0041] Figure 10 This is a diagram showing a simplified structure of the vehicle system according to the second embodiment.

[0042] Figure 11 This is a block diagram illustrating the hardware structure of the vehicle according to the second embodiment.

[0043] Figure 12 This is a flowchart illustrating an example of the custom setting process executed in the CPU of the control ECU of the vehicle-mounted device in the second embodiment.

[0044] Figure 13 This is a flowchart illustrating an example of the custom setting process executed in the CPU of the control ECU of the vehicle-mounted device in a variant of the second embodiment.

[0045] Figure 14 This is a diagram showing a simplified structure of the vehicle system according to the third embodiment.

[0046] Figure 15This is a block diagram illustrating the hardware structure of the smartphone according to the third embodiment.

[0047] Figure 16 This is a block diagram illustrating an example of the functional structure of the CPU of the control device in a smartphone according to the third embodiment.

[0048] Figure 17 This is a block diagram illustrating the hardware structure of the management server in the third embodiment.

[0049] Figure 18 This is a timing diagram illustrating the processing flow in the vehicle system of the third embodiment.

[0050] Figure 19 This is a timing diagram illustrating the processing flow in the vehicle system of a modified example of the third embodiment. Detailed Implementation

[0051] use Figures 1 to 19 The vehicle system involved in the embodiments of this disclosure will be described.

[0052] [First Implementation]

[0053] Figure 1 This is a block diagram showing a simplified structure of the vehicle system 10 according to the first embodiment.

[0054] (Overall structure)

[0055] like Figure 1 As shown, the vehicle system 10 according to this embodiment is configured to include a vehicle 12 and a smartphone 14 as a terminal for controlling the vehicle 12. Additionally, the vehicle system 10 includes a vehicle-specific portable device, i.e., a physical key 50, for controlling the vehicle 12. The physical key 50 is an example of a second key.

[0056] The vehicle 12 is configured to directly receive local communications from the smartphone 14 and the physical key 50 without going through a network. These communications include wireless and infrared communications.

[0057] The door locking device 28 locks and unlocks the driver's side door, passenger side door, rear door, and tailgate.

[0058] like Figure 2As shown, the vehicle-mounted unit 11 installed in vehicle 12 includes a physical key control ECU (Electronic Control Unit) 20, a digital key control ECU 21, an LF (Low Frequency) communication unit 22, a control ECU 23, an RF (Radio Frequency) communication unit 24, a display unit 25, and a BLE (Bluetooth Low Energy) communication unit 26.

[0059] The LF communication unit 22 is a communication unit that performs wireless communication over the LF band and sends request signals to the LF communication unit 42 described later. The LF communication unit 22 of this embodiment is provided for the driver's side door, passenger side door, rear door, and tailgate.

[0060] The RF communication unit 24 is a communication unit that performs wireless communication over the RF band and receives response signals from the RF communication unit 44 described later.

[0061] BLE communication unit 26 is a communication unit that performs wireless communication using Bluetooth (registered trademark) and communicates with BLE communication unit 14C described later.

[0062] The physical key control ECU 20 is configured to include a CPU (Central Processing Unit) 20A, a ROM (Read-Only Memory) 20B, a RAM (Random Access Memory) 20C, and an input / output (I / F) 20D. The CPU 20A, ROM 20B, RAM 20C, and I / F 20D are connected to each other via an internal bus (not shown) and are capable of communicating with each other.

[0063] CPU20A is the central processing unit, which executes various programs and controls other components. Specifically, CPU20A reads programs from ROM20B and uses RAM20C as its working area to execute the programs.

[0064] ROM20B stores various programs and various data. In this embodiment, ROM20B stores ID (Identification) information 100.

[0065] ID information 100 stores information about the ID inherent to the physical key 50.

[0066] RAM20C is used as a working area to temporarily store programs or data.

[0067] The input / output I / F20D is an interface used to communicate with the LF communication unit 22, the RF communication unit 24, and the door locking device 28, respectively.

[0068] Furthermore, the physical key control ECU 20 may include a storage unit in addition to or in place of the ROM 20B. This storage unit may be, for example, an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0069] like Figure 3 As shown, in the physical key control ECU20 of this embodiment, the CPU20A performs functions as the physical key authentication unit 110 and the physical key function management unit 112 by executing a program.

[0070] The physical key authentication unit 110 performs authentication of the physical key 50 by comparing its ID with the ID information 100 through wireless communication with the physical key 50 via the LF communication unit 22 and the RF communication unit 24. Specifically, if the physical key 50 sends a response request signal to the physical key 50 with the same ID as the ID information 100 via the LF communication unit 22, and receives a response signal from the physical key 50 via the RF communication unit 24, the physical key authentication unit 110 determines that the authentication of the physical key 50 is successful.

[0071] If the physical key 50 is successfully authenticated, the physical key authentication unit 110 performs vehicle control functions, including locking and unlocking the door lock device 28, turning on the power to the vehicle 12, and starting the engine, based on the wireless communication between the physical key 50 and the LF communication unit 22 and the RF communication unit 24.

[0072] The physical key function management unit 112 enables or disables the vehicle control functions involved in the physical key 50 based on the settings based on user operation.

[0073] The digital key control ECU 21 is configured to include a CPU 21A, a ROM 21B, a RAM 21C, and an input / output I / F 21D. The CPU 21A, ROM 21B, RAM 21C, and input / output I / F 21D are connected to each other via an internal bus (not shown) and are able to communicate with each other.

[0074] The functions of CPU21A, ROM21B, RAM21C, and I / F21D are the same as those of CPU20A, ROM20B, RAM20C, and I / F20D mentioned above.

[0075] In this embodiment, ROM 21B stores ID information 102. ID information 102 stores information about the ID inherent to the digital key registered in smartphone 14. The digital key is an example of a first key.

[0076] The input / output I / F21D is an interface used for communication with the BLE communication unit 26 and the door locking device 28, respectively.

[0077] Furthermore, the digital key control ECU 21 may include a storage unit in addition to or instead of ROM 21B. This storage unit may be, for example, an HDD or an SSD.

[0078] like Figure 4 As shown, in the digital key control ECU21 of this embodiment, the CPU21A performs functions as the digital key authentication unit 120 and the digital key function management unit 122 by executing programs.

[0079] The digital key authentication unit 120 performs digital key authentication by comparing the ID of the digital key registered on the smartphone 14 with the ID information 102 via wireless communication with the smartphone 14 through the BLE communication unit 26. If the digital key authentication is successful, the digital key authentication unit 120 performs vehicle control functions, including locking and unlocking the door lock device 28, turning on the power to the vehicle 12, and starting the engine, based on the wireless communication between the BLE communication unit 26 and the smartphone 14.

[0080] The digital key function management unit 122 enables or disables the vehicle control functions involved in the digital key based on user operation settings.

[0081] The control ECU 23 is configured to include a CPU 23A, a ROM 23B, a RAM 23C, and an input / output I / F 23D. The CPU 23A, ROM 23B, RAM 23C, and input / output I / F 23D are connected to each other via an internal bus (not shown) and are capable of communicating with each other. The CPU 23A is an example of a processor, and the RAM 23C is an example of a memory.

[0082] The functions of CPU23A, ROM23B, RAM23C, and I / F23D are the same as those of CPU20A, ROM20B, RAM20C, and I / F20D mentioned above.

[0083] In this embodiment, ROM23B stores an information processing program 104.

[0084] The input / output I / F23D is an interface used for communication with the display unit 25.

[0085] Furthermore, the control ECU 23 may include, in addition to or in place of ROM 23B, a memory device as a storage unit. This memory device may be, for example, an HDD or an SSD.

[0086] Even without a physical key, as long as there is a smartphone with a registered digital key, it is possible to control the vehicle, such as locking and unlocking the doors, turning on the vehicle power, and starting the engine.

[0087] Here, when a user wants to disable the digital key's function through vehicle settings, and only has a smartphone without the physical key, disabling the digital key's function prevents them from locking and unlocking the doors, turning on the vehicle's power, and starting the engine. Furthermore, since the vehicle's power cannot be turned on, the digital key's function also cannot be enabled.

[0088] Therefore, in this embodiment, when the vehicle unit 11 and the physical key 50 cannot communicate as required, the vehicle control function using the digital key cannot be disabled.

[0089] Specifically, such as Figure 5 As shown, in the control ECU23 of this embodiment, the CPU23A functions as the receiving unit 130, the confirmation unit 132, and the processing unit 134 by executing the information processing program 104.

[0090] The receiving unit 130 accepts user operations for disabling vehicle control functions related to the digital key. Specifically, the receiving unit 130 accepts user operations for disabling vehicle control functions related to the digital key displayed on the display unit 25.

[0091] For example, Figure 6 The customized settings screen 25A shown is displayed on the display unit 25 to handle user operations. Figure 6 The image shows an example of a custom settings screen 25A including a digital key function off button 25B for disabling vehicle control functions related to the digital key, a smart entry function off button 25C for disabling the smart entry function, and a power tailgate function off button 25D for disabling the power tailgate function.

[0092] The confirmation unit 132 confirms whether the prescribed communication with the physical key 50 is possible. Specifically, if the physical key 50 is successfully authenticated by the physical key authentication unit 110 that controls the ECU 20 via the physical key, the confirmation unit 132 determines that the prescribed communication with the physical key 50 is possible.

[0093] If the confirmation unit 132 cannot confirm the prescribed communication with the physical key 50, the processing unit 134 performs processing to suppress the invalidation of vehicle control functions related to the digital key corresponding to the user operation. Specifically, if the confirmation unit 132 cannot confirm the prescribed communication with the physical key 50, the processing unit 134 controls the user operation to invalidate the vehicle control functions related to the digital key on the user interface displayed on the display unit 25. For example, as Figure 6 As shown, the processing unit 134 turns down the display of the digital key function off button 25B on the customization setting screen 25A and disables the digital key function off button 25B.

[0094] (Physical key)

[0095] like Figure 7 As shown, the physical key 50 is an electronic device that can be carried by the user of vehicle 12. The physical key 50 includes a microcomputer 40, an LF communication unit 42, and an RF communication unit 44. The microcomputer 40 is configured to include at least a non-volatile memory 40B. The memory 40B stores information inherent to the physical key 50, namely ID information 106.

[0096] LF communication unit 42 is a communication unit that performs wireless communication over the LF band, and receives response request signals from LF communication unit 22. RF communication unit 44 is a transmitting unit that performs wireless communication over the RF band, and sends response signals to RF communication unit 24.

[0097] The microcomputer 40 compares the ID information 100 included in the response request signal received from the LF communication unit 22 with the ID information 106 in the memory 40B. If they match, it sends a response signal through the RF communication unit 44. Additionally, if a user operation is received on the physical key 50 for locking / unlocking the door lock device 28, turning on the power to the vehicle 12, and starting the engine (not shown), the microcomputer 40 sends the signal corresponding to that user operation to the RF communication unit 24 of the vehicle unit 11 through the RF communication unit 44.

[0098] (Smartphone)

[0099] The smartphone 14 is a communication terminal held by the user. In this embodiment, the smartphone 14 is configured to, upon successful authentication of the digital key registered through communication with the vehicle-mounted device 11, accept user operations for locking and unlocking the door lock device 28, turning on the power to the vehicle 12, and starting the engine, thereby enabling the locking and unlocking of the door lock device 28, the turning on of the power to the vehicle 12, and the starting of the engine. Figure 8As shown, the smartphone 14 is configured to include a control device 70, a touch panel 14A, a communication unit 14B, and a BLE communication unit 14C.

[0100] The control device 70 includes, as an example, a processor (CPU 72), ROM 73, RAM 74, memory 75, and input / output (I / F) 76. The CPU 72, ROM 73, RAM 74, memory 75, and I / F 76 are interconnected via a bus 78.

[0101] The functions of CPU 72, ROM 73, RAM 74, and I / O 76 are the same as those of CPU 20A, ROM 20B, RAM 20C, and I / O 20D described above. Furthermore, the storage 75 in this embodiment can be either the internal storage of the smartphone 14 or a micro SD card.

[0102] CPU 72 reads the program from ROM 73 and executes the program using RAM 74 as the working area. In this embodiment, digital key 140 is registered in memory 75. ROM 73 stores a vehicle control application program used for vehicle control involving user operations using digital key 140.

[0103] In this embodiment, the control device 70 is connected to a touch panel 14A, a communication unit 14B, and a BLE communication unit 14C via an input / output I / F 76. Furthermore, the touch panel 14A, communication unit 14B, and BLE communication unit 14C can also be directly connected to the bus 78.

[0104] If the vehicle control application is executed, the CPU 72 causes the touch panel 14A to display icons for locking / unlocking the door lock device 28, powering on the vehicle 12, and starting the engine. If the user operates on these icons, the BLE communication unit 14C sends a signal indicating the vehicle control (locking / unlocking the door lock device 28, powering on the vehicle 12, or starting the engine) corresponding to the operated icon to the BLE communication unit 26 of the vehicle unit 11.

[0105] (Processing flow)

[0106] Next, use Figure 9 The flowchart illustrates the processing flow in the vehicle system 10 of this embodiment.

[0107] First, based on the operation of a user located near the vehicle 12, the smartphone 14 launches the vehicle control application. Then, based on the user's operation, the smartphone 14 or the physical key 50 handles the door unlocking operation, sending a signal corresponding to the door unlocking operation to the vehicle unit 11, which then unlocks the door locking device 28.

[0108] Then, if the user enters the vehicle 12, the physical key control ECU 20 of the vehicle unit 11 authenticates the physical key 50. In addition, the digital key control ECU 21 authenticates the digital key 140 registered in the smartphone 14.

[0109] Then, if the user instructs the vehicle-mounted unit 11 to perform customized settings, the CPU 23A of the control ECU 23 of the vehicle-mounted unit 11 executes the information processing program 104. Figure 9 The customized settings shown are processed.

[0110] First, in step S100, CPU 23A, acting as verification unit 132, verifies the authentication status of physical key 50 and digital key 140. If both physical key 50 and digital key 140 fail to authenticate, CPU 23A terminates the customization settings process. Alternatively, if physical key 50 fails to authenticate but digital key 140 succeeds, CPU 23A proceeds to step S102. Conversely, if physical key 50 succeeds to authentication, CPU 23A proceeds to step S106.

[0111] In step S102, CPU 23A acts as receiving unit 130 to transfer the screen displayed on display unit 25 to custom setting screen 25A.

[0112] In step S104, CPU 23A, as processing unit 134, reduces the display of the digital key function off button 25B on the custom setting screen 25A and disables the digital key function off button 25B, and then moves to step S110.

[0113] In step S106, CPU 23A acts as receiving unit 130 to transfer the screen displayed on display unit 25 to custom setting screen 25A.

[0114] In step S108, CPU 23A, as processing unit 134, turns up the display of the digital key function off button 25B on the custom setting screen 25A and activates the digital key function off button 25B, and then moves to step S110.

[0115] In step S110, CPU23A, as receiving unit 130, receives the user operation in the customization setting screen 25A, sets it to disable the digital key function, smart entry function, or electric tailgate function, and then ends the customization setting process.

[0116] (Summary of the first implementation method)

[0117] In this embodiment, the vehicle 12 is configured such that the control ECU 23 checks whether it can establish the required communication with the physical key 50. If the required communication with the physical key 50 cannot be established, processing is performed to disable the vehicle control functions related to the digital key 140 corresponding to user operations. Thus, when the required communication with the physical key 50 cannot be established, the control ECU 23 cannot disable the vehicle control functions using the digital key 140. This reduces the possibility of vehicle control failure due to misoperation when the user only possesses a smartphone 14 registered with the digital key 140.

[0118] Furthermore, in this embodiment, the physical key authentication unit 110 determines that the authentication of the physical key 50 is successful when it sends a response request signal to the physical key 50 having the same ID as the ID information 100 via the LF communication unit 22 and receives a response signal from the physical key 50 via the RF communication unit 24. However, this is not a limitation. For example, the physical key 50 may be configured to periodically transmit signals, and the physical key authentication unit 110 may perform authentication processing of the physical key 50 by comparing the ID of the physical key 50 included in the signal transmitted from the physical key 50 within the vehicle 12 with the ID information 100.

[0119] Furthermore, in this embodiment, the example described is the case where the screen displayed on the display unit 25 is moved to the customization setting screen 25A after the authentication status of the physical key 50 and the digital key 140 has been confirmed, but this is not a limitation. The authentication status of the physical key 50 and the digital key 140 may also be confirmed when the screen displayed on the display unit 25 is moved to the customization setting screen 25A.

[0120] [Second Implementation]

[0121] In the first embodiment, the physical key performs vehicle control via wireless communication over both the LF and RF bands. In contrast, the second embodiment differs from the first embodiment in that it uses a card that communicates via NFC (Near Field Communication). The differences from the first embodiment will be described below. The same reference numerals are used for the same structures, and descriptions are omitted as they are not explicitly stated.

[0122] (Overall structure)

[0123] like Figure 10 As shown, the vehicle system 210 involved in this embodiment includes a vehicle 212, a smartphone 14, and a vehicle-specific card, namely an NFC card 250, for controlling the vehicle 212. The NFC card 250 is an example of a second key.

[0124] Vehicle 212 is configured to directly receive local communication from smartphone 14 and NFC card 250 without going through a network. This communication includes wireless communication and infrared communication.

[0125] like Figure 11 As shown, the vehicle-mounted unit 211 installed in vehicle 212 includes a physical key control ECU 220, a digital key control ECU 21, an NFC communication unit 224, a control ECU 23, a display unit 25, and a BLE communication unit 26.

[0126] The NFC communication unit 224 is a communication unit that performs wireless communication over the NFC band and communicates with the NFC card 250 when it is near the user. In this embodiment, the NFC communication unit 224 is installed inside the vehicle 212.

[0127] The physical key control ECU 220 is configured to include a CPU 220A, a ROM 220B, a RAM 220C, and an input / output I / F 220D. The CPU 220A, ROM 220B, RAM 220C, and input / output I / F 220D are connected to each other via an internal bus (not shown) and are able to communicate with each other.

[0128] The functions of CPU220A, ROM220B, RAM220C, and I / O220D are the same as those of CPU20A, ROM20B, RAM20C, and I / O20D mentioned above.

[0129] In this embodiment, ROM 220B stores ID information 100. ID information 100 stores the ID information inherent to the NFC card 250.

[0130] As mentioned above Figure 3 As shown, in the physical key control ECU 220 of this embodiment, the CPU 220A functions as the physical key authentication unit 110 and the physical key function management unit 112 by executing a program. Furthermore, in the digital key control ECU 21, the CPU 21A can also function as the physical key authentication unit 110 and the physical key function management unit 112 by executing a program.

[0131] The physical key authentication unit 110 performs authentication of the NFC card 250 by comparing its ID with the ID information 100 through wireless communication with the NFC card 250 via the NFC communication unit 224. Specifically, if the physical key authentication unit 110 receives a response request signal with the same ID as the ID information 100 from the NFC card 250 via the NFC communication unit 224, it determines that the NFC card 250 has been successfully authenticated.

[0132] If the NFC card 250 is successfully authenticated, the physical key authentication unit 110 performs vehicle control functions, including powering on the vehicle 212 and starting the engine.

[0133] The physical key function management unit 112 enables or disables the vehicle control functions related to the NFC card 250 based on settings based on user operation.

[0134] As mentioned above Figure 5 As shown, in the control ECU23 of this embodiment, the CPU23A functions as the receiving unit 130, the confirmation unit 132, and the processing unit 134 by executing the information processing program 104.

[0135] The receiving unit 130 accepts user operations for disabling the vehicle control functions related to the digital key 140. Specifically, the receiving unit 130 accepts user operations for disabling the vehicle control functions related to the digital key 140 displayed on the display unit 25.

[0136] For example, the above Figure 6 The customized settings screen 25A shown is displayed on the display unit 25 to handle user operations.

[0137] The verification unit 132 verifies whether the specified communication with the NFC card 250 is possible. Specifically, if the NFC card 250 is successfully authenticated by the physical key authentication unit 110 of the ECU 220 controlled by the physical key, the verification unit 132 determines that the specified communication with the NFC card 250 is possible.

[0138] If the verification unit 132 cannot confirm the specified communication with the NFC card 250, the processing unit 134 performs processing to suppress the invalidation of vehicle control functions related to the digital key 140 corresponding to the user operation. Specifically, if the verification unit 132 cannot confirm the specified communication with the NFC card 250, the processing unit 134 controls the user operation to invalidate the vehicle control functions related to the digital key 140 in the user interface displayed on the display unit 25. For example, the processing unit 134 is as described above. Figure 6As shown, the display of the digital key function off button 25B on the custom settings screen 25A is reduced, and the digital key function off button 25B is disabled.

[0139] (Processing flow)

[0140] Next, use Figure 12 The flowchart illustrates the processing flow in the vehicle system 210 of this embodiment.

[0141] First, based on the operation of a user located near the vehicle 212, the smartphone 14 launches the vehicle control application. Furthermore, based on the user's operation, the smartphone 14 processes a door unlocking operation, sending a signal corresponding to the door unlocking operation to the vehicle unit 211, which then unlocks the door locking device 28.

[0142] Then, if the user enters the vehicle 212, the digital key control ECU 21 of the vehicle unit 211 authenticates the digital key 140 registered in the smartphone 14.

[0143] Then, if the user sets a custom setting for the vehicle-mounted unit 211, the CPU 23A of the control ECU 23 of the vehicle-mounted unit 211 executes the information processing program 104. Figure 12 The customized settings shown are processed.

[0144] First, in step S200, CPU 23A, acting as confirmation unit 132, confirms the authentication status of digital key 140. If authentication of digital key 140 fails, CPU 23A terminates the customization setting process. Conversely, if authentication of digital key 140 is successful, CPU 23A proceeds to step S202.

[0145] In step S202, CPU 23A acts as receiving unit 130 to transfer the screen displayed on display unit 25 to custom setting screen 25A.

[0146] In step S204, CPU 23A, acting as confirmation unit 132, determines whether smartphone 14 is a smartphone pre-registered as having owner rights. Here, a smartphone with owner rights refers to a smartphone registered to vehicle 212 as the owner of vehicle 212. If it is not pre-registered as a smartphone with owner rights, CPU 23A proceeds to step S206. On the other hand, if it is a smartphone pre-registered as a smartphone with owner rights, CPU 23A proceeds to step S212.

[0147] In step S206, CPU 23A, acting as confirmation unit 132, receives a message from the user requesting that NFC card 250 be brought close to NFC communication unit 224. Then, the user brings the held NFC card 250 close to NFC communication unit 224. If NFC card 250 is close to NFC communication unit 224, physical key authentication unit 110 performs authentication processing of NFC card 250 by comparing the ID of NFC card 250 with ID information 100 based on wireless communication between NFC communication unit 224 and NFC card 250.

[0148] In step S208, CPU 23A, acting as confirmation unit 132, determines whether the authentication of NFC card 250 is successful by controlling the physical key authentication unit 110 of ECU 220A via the physical key. If the NFC card 250 is successfully authenticated, CPU 23A proceeds to step S212. Conversely, if the NFC card 250 is unauthenticated, CPU 23A proceeds to step S210.

[0149] In step S210, CPU 23A, as processing unit 134, reduces the display of the digital key function off button 25B on the customization setting screen 25A and disables the digital key function off button 25B, and then moves to step S214.

[0150] In step S212, CPU 23A, as processing unit 134, deepens the display of the digital key function off button 25B on the customization setting screen 25A and activates the digital key function off button 25B, and then moves to step S214.

[0151] In step S214, CPU 23A, acting as receiving unit 130, accepts the user operation in the customization setting screen 25A, sets the digital key function, smart entry function, or power tailgate function to be disabled, and then ends the customization setting process. Here, when the digital key function is set to be disabled, the user selects to enable vehicle control functions related to the NFC card 250, or vehicle control functions related to communication with the NFC communication unit (not shown) of the smartphone 140 with owner permissions.

[0152] (Summary of the second implementation method)

[0153] In this embodiment, the vehicle 212 is configured such that the control ECU 23 checks whether the required communication with the NFC card 250 is possible. If the required communication with the NFC card 250 cannot be confirmed, processing is performed to suppress the invalidation of vehicle control functions related to the digital key 140 corresponding to user operations. Thus, if the required communication with the NFC card 250 cannot be achieved, the control ECU 23 cannot invalidate the vehicle control functions using the digital key 140. This reduces the possibility of vehicle control failure due to accidental operation when the user only possesses a smartphone 14 registered with the digital key 140. Furthermore, if a smartphone without ownership rights is used for digital key authentication, and authentication related to the NFC card 250 fails, the vehicle control functions using the digital key 140 cannot be invalidated. This is because: when using a smartphone without ownership rights, the likelihood of not possessing the NFC card 250 is high. On the other hand, when using a smartphone with ownership rights, the likelihood of possessing the NFC card 250 is high, so the risk of vehicle control failure is low, and trouble can be reduced by prioritizing the omission of authentication.

[0154] (A variation of the second embodiment)

[0155] In the second embodiment, an example was given where an NFC card is not required if the smartphone 14 registered with the digital key 140 is an owner-authorized smartphone. However, even if the smartphone is an owner-authorized smartphone, an NFC card can still be required. In a modified example, the CPU 23A of the control ECU 23 of the vehicle unit 211 performs... Figure 13 The customized settings shown above replace the above. Figure 12 The customized settings shown are processed.

[0156] First, in step S300, CPU 23A, acting as confirmation unit 132, confirms the authentication status of digital key 140. If authentication of digital key 140 fails, CPU 23A terminates the customization setting process. Conversely, if authentication of digital key 140 is successful, CPU 23A proceeds to step S302.

[0157] In step S302, CPU 23A acts as receiving unit 130 to transfer the screen displayed on display unit 25 to custom setting screen 25A.

[0158] In step S304, CPU 23A, acting as confirmation unit 132, receives a message from the user requesting that NFC card 250 be brought close to NFC communication unit 224. Then, the user brings the held NFC card 250 close to NFC communication unit 224. If NFC card 250 is close to NFC communication unit 224, physical key authentication unit 110 performs authentication processing of NFC card 250 by comparing the ID of NFC card 250 with ID information 100 based on wireless communication between NFC communication unit 224 and NFC card 250.

[0159] In step S306, CPU 23A, acting as confirmation unit 132, determines whether the authentication of NFC card 250 is successful by controlling the physical key authentication unit 110 of ECU 220A via the physical key. If the NFC card 250 is successfully authenticated, CPU 23A proceeds to step S308. Conversely, if the NFC card 250 is unauthenticated, CPU 23A proceeds to step S310.

[0160] In step S308, CPU 23A, acting as confirmation unit 132, determines whether smartphone 14 is a smartphone pre-registered as having friend permissions. Here, a smartphone with friend permissions refers to a smartphone registered to vehicle 212 that is owned by someone different from the owner of vehicle 212. If the smartphone is not pre-registered as having friend permissions, CPU 23A proceeds to step S312. On the other hand, if the smartphone is pre-registered as having friend permissions, CPU 23A proceeds to step S310.

[0161] In step S312, CPU 23A, acting as confirmation unit 132, determines whether smartphone 14 is a smartphone pre-registered as a smartphone with owner rights. If it is not a smartphone pre-registered as a smartphone with owner rights, CPU 23A proceeds to step S316. On the other hand, if it is a smartphone pre-registered as a smartphone with owner rights, CPU 23A proceeds to step S314.

[0162] In step S310, CPU 23A, as processing unit 134, reduces the display of the digital key function off button 25B on the custom setting screen 25A and disables the digital key function off button 25B, and then moves to step S322.

[0163] In step S314, CPU 23A, as processing unit 134, deepens the display of the digital key function off button 25B on the custom setting screen 25A and activates the digital key function off button 25B, and then moves to step S322.

[0164] In step S316, CPU 23A, acting as verification unit 132, determines whether the authenticated NFC card 250 was an NFC card registered at the factory. If the authenticated NFC card 250 was an NFC card registered at the factory, CPU 23A proceeds to step S320. On the other hand, if the authenticated NFC card 250 was not an NFC card registered at the factory, CPU 23A proceeds to step S318.

[0165] In step S318, CPU 23A, as processing unit 134, reduces the display of the digital key function off button 25B on the custom setting screen 25A and disables the digital key function off button 25B, and then moves to step S322.

[0166] In step S320, CPU 23A, as processing unit 134, deepens the display of the digital key function off button 25B on the custom setting screen 25A and activates the digital key function off button 25B, and then moves to step S322.

[0167] In step S322, CPU 23A, acting as receiving unit 130, accepts the user operation in the customization setting screen 25A, sets the digital key function, smart entry function, or power tailgate function to be disabled, and then ends the customization setting process. Here, if smartphone 14 is a smartphone with ownership rights and the digital key function is set to be disabled, vehicle control functions related to communication with the NFC communication unit (not shown) of the smartphone with ownership rights 140 can be enabled. Alternatively, vehicle control functions related to the digital key registered on a smartphone 140 different from the smartphone with ownership rights can be disabled, while vehicle control functions related to the digital key registered on the smartphone with ownership rights can be enabled.

[0168] In a variation of the second embodiment, the NFC card 250 is required even if the smartphone 14 is a smartphone with ownership rights. Therefore, even if the smartphone has ownership rights, the NFC card 250 is verified, reducing the possibility of vehicle control failure due to accidental operation when only the smartphone 14 is in hand. Furthermore, even if the smartphone 14 is not a smartphone with ownership rights, if the NFC card 250 is a card registered at the factory, the vehicle control function using the digital key 140 can be disabled. This is because NFC cards registered at the factory are used in business environments such as within the manufacturer or dealership before shipment.

[0169] As a further variation of the second embodiment, the first embodiment and the second embodiment described above can be combined. In this case, it is sufficient to attempt both physical key authentication and NFC card authentication in step S100. At this time, failure of physical key authentication means that both physical key authentication and NFC card authentication fail, while success of physical key authentication means that at least one of the physical key authentication and NFC card authentication succeeds. Furthermore, success of physical key authentication can be defined as success of both physical key authentication and NFC card authentication, or failure of physical key authentication can be defined as failure of either physical key authentication or NFC card authentication. The user can set which of the above situations is considered a success of physical key authentication.

[0170] Furthermore, in step S100 above, the user can set which of the following authentication methods to perform: physical key authentication in the first embodiment, NFC card authentication in the second embodiment, or both physical key authentication and NFC card authentication.

[0171] [Third Implementation]

[0172] In the first and second embodiments, customization settings are received in the vehicle-mounted device. In contrast, in the third embodiment, customization settings are received in a smartphone, which differs from the first and second embodiments. The differences from the first embodiment will be described below. The same reference numerals are used to refer to the same structures, and descriptions are omitted.

[0173] (Overall structure)

[0174] like Figure 14 As shown, the vehicle system 410 involved in this embodiment includes a vehicle 12, a smartphone 414, a physical key 50, and a management server 416.

[0175] Vehicle 12, smartphone 414, and management server 416 are configured to communicate via network N. Vehicle 12 includes a communication device 444 connected to network N. Network N includes mobile communication services such as 3G and LTE, and internet lines.

[0176] (Smartphone)

[0177] like Figure 15 As shown, the smartphone 414 is configured to include a control device 470, a touch panel 14A, a communication unit 14B, and a BLE communication unit 14C.

[0178] The control device 470 is an example of a processor as hardware, namely CPU 472, ROM 473, RAM 74, memory 75, and input / output I / F 76. CPU 472, ROM 473, RAM 74, memory 75, and input / output I / F 76 are interconnected via bus 78. RAM 74 is an example of a memory.

[0179] The functions of CPU472, ROM473, RAM74 and I / F76 are the same as those of CPU20A, ROM20B, RAM20C and I / F20D mentioned above.

[0180] CPU 472 reads information processing program 473A from ROM 473 and executes information processing program 473A using RAM 74 as the working area. In this embodiment, information processing program 473A is stored in ROM 473. This information processing program 473A is an application program for vehicle control involving user operations using digital key 140.

[0181] like Figure 16 As shown, the CPU 472 functions as the receiving unit 490, the confirmation unit 492, and the processing unit 494 by executing the information processing program 473A.

[0182] The receiving unit 490 accepts user operations for disabling the vehicle control functions related to the digital key 140. Specifically, the receiving unit 490 accepts user operations for the user interface displayed on the touch panel 14A for disabling the vehicle control functions related to the digital key 140.

[0183] For example, the above Figure 6 The customized settings screen 25A shown is displayed on the touch panel 14A to handle user operations.

[0184] The confirmation unit 492 confirms whether the prescribed communication with the physical key 50 is possible. Specifically, when the confirmation unit 492 receives information indicating that the physical key 50 has been successfully authenticated by the physical key authentication unit 110, which indicates that the physical key controls the ECU 20 via the physical key of the vehicle loader 11, it determines that the prescribed communication with the physical key 50 is possible.

[0185] If the confirmation unit 492 cannot confirm the prescribed communication with the physical key 50, the processing unit 494 performs processing to suppress the invalidation of vehicle control functions related to the digital key 140 corresponding to the user operation. Specifically, if the confirmation unit 492 cannot confirm the prescribed communication with the physical key 50, the processing unit 494 controls the user operation to invalidate the vehicle control functions related to the digital key 140 in the user interface displayed on the touch panel 14A. For example, the processing unit 494 is as described above. Figure 6 As shown, the display of the digital key function off button 25B on the custom settings screen 25A is reduced, and the digital key function off button 25B is disabled.

[0186] (Management Server)

[0187] The management server 416 has the function of mediating (interceing) the data exchange between the smartphone 414 and the vehicle-mounted device 11. For example... Figure 17 As shown, the management server 416 is configured to include a control device 480 and a communication unit 416B.

[0188] The control device 480 includes a CPU 482, a ROM 483, a RAM 484, a memory 485, and an input / output (I / F) 486. The CPU 482, ROM 483, RAM 484, memory 485, and I / F 486 are interconnected via a bus 488.

[0189] The functions of CPU482, ROM483, RAM484, memory 485, and I / O 486 are the same as those of CPU72, ROM73, RAM74, memory 75, and I / O 76 mentioned above.

[0190] CPU 482 reads the program from storage 485 and executes the program using RAM 484 as its working area. In this embodiment, storage 485 stores a program for mediating data exchange between smartphone 414 and vehicle-mounted device 11.

[0191] In this embodiment, the control device 480 is connected to a communication unit 416B via an input / output I / O 486. Alternatively, the communication unit 416B can also be directly connected to the bus 488.

[0192] (Processing flow)

[0193] Next, use Figure 18 The timing diagram illustrates the processing flow in the vehicle system 410 of this embodiment.

[0194] First, in step S400, based on the operation of a user located near the vehicle 12, the smartphone 414 activates the information processing program 473A. Furthermore, based on the user's operation, the smartphone 414 or the physical key 50 handles the door unlocking operation, sending a signal corresponding to the door unlocking operation to the vehicle-mounted unit 11, which then unlocks the door locking device 28.

[0195] Then, if the user enters the vehicle 12, in step S402, the digital key control ECU 21 authenticates the digital key 140 registered in the smartphone 414. Additionally, in step S404, the physical key control ECU 20 of the vehicle unit 11 authenticates the physical key 50.

[0196] Then, in step S406, the CPU23A of the control ECU23 of the vehicle unit 11 sends information indicating the authentication status of the digital key 140 and the authentication status of the physical key 50 to the management server 416 through the communication device 444.

[0197] In step S408, the management server 416 sends the received information indicating the authentication status of the digital key 140 and the physical key 50 to the smartphone 414 via the communication unit 416B.

[0198] Then, if the user instructs the smartphone 414 to make custom settings according to the user's operation, in step S410, the CPU 472 of the control device 470 of the smartphone 414 causes the screen displayed on the touch panel 14A to be moved to the custom settings screen 25A.

[0199] In step S412, the CPU 472 of the control device 470 of the smartphone 414 acts as a confirmation unit 492 to confirm the authentication status of the digital key 140 and the physical key 50. Furthermore, if the confirmation unit 492 cannot confirm that the required communication with the physical key 50 can be performed, the CPU 472 acts as a processing unit 494 to dim the display of the digital key function off button 25B on the customization setting screen 25A and disable the digital key function off button 25B.

[0200] In step S414, the CPU 472 of the control device 470 of the smartphone 414 acts as a receiving unit 490 to receive user operations in the customization setting screen 25A.

[0201] In step S416, the CPU 472 of the control device 470 of the smartphone 414, acting as the receiving unit 490, sends setting information for disabling the digital key function, smart entry function, or electric tailgate function to the management server 416 via the communication unit 14B.

[0202] In step S418, the management server 416 sends the received setting information to the vehicle unit 11 through the communication unit 416B.

[0203] In step S420, the CPU23A of the control ECU23 of the vehicle unit 11 is set to disable the digital key function, smart entry function or electric tailgate function according to the received setting information.

[0204] (Summary of the third implementation method)

[0205] In this embodiment, the smartphone 414 is configured such that the control device 470 confirms whether the prescribed communication can be established between the physical key 50 and the vehicle 12. If the prescribed communication between the physical key 50 and the vehicle 12 cannot be confirmed, processing is performed to suppress the invalidation of vehicle control functions related to the digital key 140 corresponding to user operation. Thus, when the prescribed communication between the physical key 50 and the vehicle 12 cannot be established, the control device 470 cannot invalidate the vehicle control functions using the digital key 140. This reduces the possibility of vehicle control failure due to misoperation when the user only possesses the smartphone 414 registered with the digital key 140.

[0206] (A variation of the third embodiment)

[0207] In the third embodiment, an example was described where information indicating the authentication status of the digital key 140 and the physical key 50 is sent from the vehicle-mounted device 11 to the management server 416, but this is not a limitation. Control information for controlling the customized setting screen 25A of the smartphone 414 based on the information indicating the authentication status of the digital key 140 and the physical key 50 may also be sent from the vehicle-mounted device 11. In a variant, instead of the above... Figure 18 The processing flow shown becomes Figure 19 The processing flow is shown. In addition, the CPU23A of the control ECU23 of the vehicle unit 11 functions as the receiving unit 130, the confirmation unit 132, and the processing unit 134 by executing the information processing program 104.

[0208] First, in step S500, based on the operation of a user located near the vehicle 12, the smartphone 414 launches the vehicle control application. Furthermore, based on the user's operation, the smartphone 414 or the physical key 50 handles the door unlocking operation, sending a signal corresponding to the door unlocking operation to the vehicle-mounted unit 11, which then unlocks the door locking device 28.

[0209] Then, if the user enters the vehicle 12, in step S502, the digital key control ECU 21 authenticates the digital key 140 registered in the smartphone 414. Additionally, in step S504, the physical key control ECU 20 of the vehicle unit 11 authenticates the physical key 50.

[0210] Then, if the user instructs the smartphone 414 to make custom settings, in step S506, the CPU 472 of the control device 470 of the smartphone 414 causes the screen displayed on the touch panel 14A to be moved to the custom settings screen 25A.

[0211] Then, in step S508, the CPU 23A of the control ECU 23 of the vehicle unit 11, acting as a verification unit 132, verifies the authentication status of the digital key 140 and the physical key 50. Furthermore, if the verification unit 132 cannot confirm the required communication with the physical key 50, the CPU 23A, acting as a processing unit 134, sends a display control signal to the management server 416 via the communication device 444. This display control signal is used to control the display of the digital key function deactivation button 25B on the custom setting screen 25A of the touch panel 14A of the smartphone 414 to be reduced and to disable the digital key function deactivation button 25B.

[0212] In step S510, the management server 416 sends the received display control signal to the smartphone 414 through the communication unit 416B.

[0213] In step S512, the CPU 472 of the control device 470 of the smartphone 414 controls the display of the custom setting screen 25A on the touch panel 14A based on the received display control signal.

[0214] In step S514, the CPU 472 of the control device 470 of the smartphone 414 accepts user operations in the customized setting screen 25A.

[0215] In step S516, the CPU 472 of the control device 470 of the smartphone 414 sends setting information for disabling the digital key function, smart entry function, or electric tailgate function to the management server 416 via the communication unit 14B.

[0216] In step S518, the management server 416 sends the received setting information to the vehicle unit 11 through the communication unit 416B.

[0217] In step S520, the CPU23A of the control ECU23 of the vehicle unit 11 is set to disable the digital key function, smart entry function or electric tailgate function according to the received setting information.

[0218] In the above-described modified embodiment, the vehicle 12 is configured such that the control ECU 23 checks whether it can perform the prescribed communication with the physical key 50. If the prescribed communication with the physical key 50 cannot be confirmed, processing is performed to suppress the invalidation of vehicle control functions related to the digital key 140 corresponding to user operations. Thus, in the absence of the prescribed communication with the physical key 50, the control ECU 23 cannot invalidate vehicle control functions using the digital key 140. This reduces the possibility of vehicle control failure due to misoperation when the user only possesses a smartphone 414 registered with the digital key 140.

[0219] [Remark]

[0220] In the above embodiments, the terminal registered with digital key 140 is used as smartphone 14, 414, but it is not limited to this. The digital key 140 can also be registered for devices with communication functions such as tablet computers and wearable computers.

[0221] Furthermore, in the vehicle 12 or smartphone 414 of each embodiment, the case where the display of the digital key function deactivation button 25B on the customization setting screen 25A is reduced and the digital key function deactivation button 25B is disabled is described as an example, but it is not limited to this. For example, a message indicating that a user operation to disable the vehicle control function of the digital key 140 cannot be accepted may also be reported. As an example, an error message "The vehicle control function of the digital key cannot be disabled because there is no physical key" may be reported. In addition, in this case, after receiving a user operation to disable the vehicle control function of the digital key 140, the control ECU 23 may confirm whether the prescribed communication with the physical key 50 is possible.

[0222] Furthermore, in each embodiment, an example is shown where a user operation to disable the vehicle control function of the digital key 140 is performed on the customized setting screen 25A displayed on the display unit 25 of the vehicle-mounted device 11 or the touch panel 14A of the smartphone 414, but this is not a limitation. The user operation to disable the vehicle control function of the digital key 140 can also be performed by pressing a button located inside the vehicle.

[0223] Furthermore, in each embodiment, the example described is the case where the physical key 50 communicates wirelessly with the vehicle unit 11 via the LF band and RF band, but this is not a limitation. For example, the physical key 50 may also use Bluetooth (registered trademark), NFC, or UWB (Ultra Wide Band) to communicate wirelessly with the vehicle unit 11.

[0224] Furthermore, in each embodiment, the example described is that smartphones 14 and 414 use Bluetooth (registered trademark) to communicate wirelessly with the vehicle-mounted device 11, but this is not a limitation. For example, smartphones 14 and 414 may also use NFC or UWB to communicate wirelessly with the vehicle-mounted device 11.

[0225] Furthermore, the various processes executed by the CPU23A and 472 reading the software (program) in the above embodiments can also be executed by various processors other than the CPU. Examples of processors in this case include FPGAs (Field-Programmable Gate Arrays) and processors with dedicated circuit structures designed for specific processes, such as PLDs (Programmable Logic Devices) and ASICs (Application Specific Integrated Circuits), whose circuit structures can be modified after manufacturing. Additionally, various processes can be executed by one of these processors, or by a combination of two or more processors of the same or different types (e.g., multiple FPGAs, or a combination of a CPU and an FPGA). More specifically, the hardware structure of these processors is a circuit that incorporates circuit elements such as semiconductor components.

[0226] Furthermore, in the above embodiments, the description assumes that each program is pre-stored (installed) on a computer-readable non-transitory recording medium. For example, in the vehicle-mounted device 11, the information processing program 104 is pre-stored in ROM 23B. Similarly, in the smartphone 414, for example, the information processing program 473A is pre-stored in ROM 473. However, this is not a limitation; programs may also be provided on non-transitory recording media such as CD-ROM (Compact Disc Read Only Memory), DVD-ROM (Digital Versatile Disc Read Only Memory), and USB (Universal Serial Bus) memory. Additionally, programs may be downloaded from an external device via a network.

[0227] The processing flow described in the above embodiments is only an example. Unnecessary steps can be deleted, new steps can be added, and the processing order can be changed without departing from the main idea.

[0228] In addition, the structures of each vehicle-mounted device, smartphone, physical key, and management server described in the above embodiments are only examples and can be changed according to the circumstances without departing from the main idea.

Claims

1. An information processing device, wherein, have: The receiving department handles user operations related to the user interface displayed on the display unit, which disables vehicle control functions related to the first key that can be used to control the vehicle. The confirmation unit, when the user instructs the display unit to display a screen showing customized settings for vehicle control functions, confirms whether the authentication process with the second key is successful or unsuccessful. This second key is a key that is different from the first key among the keys that can be used to control the vehicle. as well as If the processing unit confirms through the confirmation unit that the prescribed authentication process with the second key has failed, it causes the display unit to display a screen indicating that the vehicle control function related to the first key corresponding to the user operation has been disabled. If the confirmation unit confirms through the confirmation unit that the prescribed authentication process with the second key has been successful, it causes the display unit to display a screen indicating that the vehicle control function related to the first key corresponding to the user operation has been disabled. The first key is a smartphone used as a terminal for controlling the vehicle, and the second key is a vehicle-specific portable device, i.e., a physical key, or a vehicle-specific card, i.e., an NFC card, used for controlling the vehicle.

2. The information processing apparatus according to claim 1, wherein, The receiving unit accepts the pressing operation of the button located in the vehicle among the buttons used to disable the vehicle control functions involved in the first key.

3. The information processing apparatus according to claim 1, wherein, If the confirmation unit confirms that the authentication process with the second key has failed, the processing unit controls the user operation to be unacceptable in the user interface.

4. The information processing apparatus according to any one of claims 1 to 3, wherein, If the confirmation unit confirms that the authentication process with the second key has failed, the processing unit reports a message indicating that the user operation cannot be accepted.

5. The information processing apparatus according to any one of claims 1 to 3, wherein, The confirmation unit confirms whether the prescribed authentication process with the second key is successful or unsuccessful by comparing the identification information of the second key, which enables the prescribed authentication process to be performed in the vehicle, with the identification information of the second key that was previously registered.

6. The information processing apparatus according to any one of claims 1 to 3, wherein, The confirmation unit confirms whether the authentication process with the second key is successful or unsuccessful by comparing the identification information of the second key when the user brings it close to the proximity communication unit located in the vehicle with the pre-registered identification information of the second key.

7. The information processing apparatus according to any one of claims 1 to 3, wherein, The confirmation unit sends a response request signal to the pre-registered second key, and confirms whether the prescribed authentication process with the second key is successful or unsuccessful based on whether a response signal is received from the second key.

8. The information processing apparatus according to any one of claims 1 to 3, wherein, The confirmation unit determines whether the prescribed authentication process with the second key is successful or unsuccessful based on whether it receives a signal emitted from the pre-registered second key.

9. A vehicle, wherein, have: The information processing apparatus according to any one of claims 1 to 8; and The locking mechanism is used to lock and unlock the opening and closing parts that separate the interior and exterior of the vehicle.

10. An information processing method, wherein, The reception department accepts user operations for the user interface displayed on the display unit, which disables the vehicle control functions related to the first key that can be used to control the vehicle. When the user instructs the display unit to show a screen displaying customized settings for vehicle control functions, the confirmation unit confirms whether the authentication process with the second key, which is different from the first key, is successful or failed. If the confirmation unit confirms that the prescribed authentication process with the second key has failed, the display unit shows a screen indicating that the vehicle control function related to the first key corresponding to the user operation has been disabled. If the confirmation unit confirms that the prescribed authentication process with the second key has been successful, the display unit shows a screen indicating that the vehicle control function related to the first key corresponding to the user operation has been disabled. The first key is a smartphone used as a terminal for controlling the vehicle, and the second key is a vehicle-specific portable device, i.e., a physical key, or a vehicle-specific card, i.e., an NFC card, used for controlling the vehicle.

11. A recording medium, wherein, It stores programs for causing the computer to perform the following processes: Accept user operations for the user interface displayed on the display unit, which disables vehicle control functions related to the first key that can be used to control the vehicle. When the user instructs the display unit to show a screen displaying customized settings for vehicle control functions, the system confirms whether the authentication process with the second key, which is different from the first key, is successful or failed. If the authentication process with the second key fails, the display unit shows a screen indicating that the vehicle control function related to the first key corresponding to the user operation has been disabled. If the authentication process with the second key succeeds, the display unit shows a screen indicating that the vehicle control function related to the first key corresponding to the user operation has been disabled. The first key is a smartphone used as a terminal for controlling the vehicle, and the second key is a vehicle-specific portable device, i.e., a physical key, or a vehicle-specific card, i.e., an NFC card, used for controlling the vehicle.

Images