Method for controlling on-vehicle system, controller for on-vehicle system, and control program

Abstract

To provide a method for controlling an on-vehicle system, a controller for an on-vehicle system, and a control program which improve the convenience of a user.SOLUTION: In a control flow in an on-vehicle system, an ECU acquires a key ID provided to an electronic key (S1); specifies a user ID which is related to the key ID (S2); selects a security technique which is related to the specified user ID (S3); sends the specified user ID to another ECU (S4); displays a selected authentication screen on a display (S5); and executes system authentication processing S7 on the basis of an operation input. The ECU unlocks the on-vehicle system (S10) in a case where the result of the authentication is approval (Y in S8).SELECTED DRAWING: Figure 3

Description

[Technical field]

[0001] The present invention relates to a control method for an in-vehicle system, a control device for an in-vehicle system, and a control program. [Background technology]

[0002] Conventionally, information processing devices that provide telematics services have been known. For example, an information processing device described in Patent Document 1 sets an email address designated by a user as a login ID for the telematics service when a contract for use of the telematics service is made, and registers the set login ID in a storage unit by linking it to a vehicle that the user owns or has the right to use. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Patent Publication No. 2023-3185 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the above information processing device has a problem of inconvenience since the user must input an e-mail address every time he logs in.

[0005] An object of the present invention is to provide a method for controlling an in-vehicle system, a control device for an in-vehicle system, and a control program that improve user convenience. [Means for solving the problem]

[0006] The present invention solves the above-mentioned problems by obtaining a key ID assigned to an electronic key, initiating login to an in-vehicle system using a user ID associated with the key ID, and after logging in to the in-vehicle system, executing a system authentication process using a security method set in association with the user ID to authenticate whether or not to permit use of the in-vehicle system, and unlocking the system if permission is granted in the system authentication process. Effect of the Invention

[0007] According to the present invention, it is possible to improve user convenience. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram showing an example of a vehicle including a control device of an in-vehicle system and a server according to the present embodiment. [Diagram 2] FIG. 2 is a table for explaining the association between key IDs and user IDs. [Diagram 3] FIG. 3 is a flowchart showing a control flow of the in-vehicle system executed by the ECU. [Figure 4] FIG. 4 shows an example of the authentication screen displayed on the display. [Diagram 5] FIG. 5 shows an example of a welcome screen that is displayed on the display. [Figure 6] FIG. 6 shows an example of a user change screen displayed on the display. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] A control method and a control device for an in-vehicle system according to the present invention will be described with reference to the drawings. Fig. 1 is a block diagram showing an example of a vehicle and a server including a control device for an in-vehicle system according to the present embodiment. The control device for the in-vehicle system is mounted on the vehicle and controls the in-vehicle system.

[0010] An in-vehicle system is a system that provides information and entertainment to a user in a vehicle, and can also communicate with the outside via a communication line. An example of an in-vehicle system is an IVI (In-Vehicle Infotainment) system. An in-vehicle system functions as a system that presents information like a navigation system, or a system that provides entertainment content such as music and video. An in-vehicle system also has a function as an operating system for a vehicle, and can, for example, send and receive emails, view videos, play games, and the like, and can also be customized by downloading applications that the user likes. An in-vehicle system can also communicate with a server or a user-owned terminal via a communication network such as Ethernet. Furthermore, operation systems are not limited to those for vehicles, and there are also operation systems designed for other devices such as smartphones and PCs, and it is possible for devices equipped with the same type of operation system to cooperate with each other and share customized software such as applications and contents.

[0011] To start up the operating system and access services to use applications, etc., a user must register an ID (account) and information required for authentication processing (e.g., a password). The user logs into the system with the registered ID, and if permitted by the authentication processing, the user can access the services and, for example, use customized applications.

[0012] The vehicle 1 includes ECUs 10 to 30, a short-range communication device 11, a lock mechanism 12, a display 21, and an in-vehicle device 31. The vehicle 1 is not limited to the configuration shown in FIG. 1, and may include, for example, a motor, a battery, or an inverter. The vehicle 1 is not limited to an electric vehicle, and may be a hybrid vehicle or an ICE vehicle using an internal combustion engine as a drive source. The ECUs 10 to 30 are connected to each other in a communicable state via a CAN communication network, and each has a memory that stores a program for controlling the vehicle 1, and a processor (CPU, etc.) for executing the program. The ECU 20 is connected to the server 2 in a communicable state via a communication network such as Ethernet. The device including the ECU 20 corresponds to a control device of the in-vehicle system in this embodiment.

[0013] The ECU 10 is a control unit that controls the keyless entry system, and controls the short-range communication device 11 and the locking mechanism 12. When a user carrying an electronic key is within a predetermined area around the vehicle 1, the keyless entry system communicates between the vehicle 1 and the electronic key via short-range communication, and locks or unlocks the locking mechanism of the doors of the vehicle 1, etc., depending on the result of the authentication process. Note that the electronic key does not necessarily have to be a dedicated terminal for the keyless entry system, and may be a communication terminal such as a smartphone.

[0014] When the lock mechanism 22 is in the locked state and a user carrying the electronic key enters the communication range of the short-range communication device 11, the ECU 20 wirelessly communicates with the electronic key using the short-range communication device 11 and transmits an ID request signal to the electronic key requesting a key ID. The electronic key reads out the key ID in response to the ID request signal and transmits a response signal including the key ID to the vehicle. The short-range communication device 11 receives the response signal. The key ID is a unique ID assigned to the electronic key. The ECU 20 performs an authentication process based on the key ID. If the result of the authentication process is "permitted", the ECU 20 outputs a command to the lock mechanism 22 to unlock the door. The lock mechanism 22 drives an actuator to unlock the door. If the result of the authentication process is "permitted", the ECU 20 transmits a key ID signal including the key ID after the authentication process to the ECU 10 via the CAN communication network.

[0015] The ECU 20 is a control unit that controls an in-vehicle system such as an IVI. The ECU 20 controls a display 21. The display 21 is, for example, a touch panel type display and is provided on an instrument panel. The display 21 may be integrated with a display that displays meters and the like and is located in front of the driver's seat.

[0016] When the main switch (ignition switch) of the vehicle is turned on, the ECU 20 receives a key ID signal from the ECU 10 to obtain the key ID. The ECU 20 identifies the user ID associated with the key ID. FIG. 2 is a table for explaining the association between the key ID and the user ID. In the example of FIG. 2, four electronic keys permitted in the authentication process are registered, and each electronic key is assigned a unique ID, ID1 to ID4. A user A is assigned to the electronic key (ID1), a user C is assigned to the electronic key (ID2) and the electronic key (ID3), and a user D is assigned to the electronic key (ID4). A table showing the correspondence as shown in FIG. 2 is stored in an in-vehicle memory or the like. The ECU 20 refers to the table to identify the user ID corresponding to the obtained key ID. For example, when a user carrying the electronic key (ID2) approaches the vehicle 1, the ECU 20 obtains the key ID (ID2) from the ECU 10 and identifies the user C corresponding to the ID2 as the user ID corresponding to the key ID.

[0017] The ECU 20 starts logging in to the in-vehicle system with the identified user ID. For example, after identifying the user ID, the ECU 20 transmits login information of the user ID to the server 2 via Ethernet. The server 2 checks whether user information corresponding to the user ID is registered. If the user information is registered, the server 2 transmits a signal to the vehicle 1 to permit the login state before authentication. The ECU 20 receives the signal from the server 2 and enters a state of being logged in to the system. However, since this state is before authentication, the use of the services of the in-vehicle system is limited, and the use of personalized customized applications and the provision of services through the Ethernet communication network are restricted. In other words, the in-vehicle system is in a locked state.

[0018] After logging in to the in-vehicle system, the ECU 20 executes a system authentication process for authenticating whether or not to permit use of the in-vehicle system using a security method set in association with the user ID. The security method can be selected in advance by the user, and is, for example, device authentication for authenticating with an external device, authentication using a PIN, pattern authentication, and password authentication. The security method may be at least one of these methods, or a combination of these methods. When using a service that utilizes the in-vehicle system, the user performs initial registration, and selects a security method during the initial registration. The security method can be changed after the initial registration. Moreover, the selection information of the security method is stored in the in-vehicle memory and / or the server 2 in association with the user ID.

[0019] The ECU 20 identifies a security method associated with the user ID, and displays an authentication screen for authentication using the security method on the display 21. For example, if the security method is authentication using a PIN, a screen for inputting the PIN (for example, a string of numbers from 0 to 9) is displayed on the display 21. Note that if the security method is device authentication, the input screen for authentication is not displayed on the display 21.

[0020] When the result of the system authentication process is "permitted", the ECU 20 unlocks the in-vehicle system. When the lock is released, the services that were limited before the authentication become available, and the user can use applications customized for himself / herself on the in-vehicle system, and can send / receive e-mails through the server 2. When the ECU 20 unlocks the in-vehicle system, the ECU 20 displays a welcome screen on the display 21 to notify the user that the lock has been released. When the result of the system authentication process is "not permitted", the ECU 20 displays the authentication screen on the display 21 again, or displays a screen for resetting registration information required for authentication, such as a password, on the display 21. The ECU 20 may also display a screen for selecting another user ID on the display 21.

[0021] Note that the ECU 20 does not necessarily need to communicate with the server 2 when executing login processing to the in-vehicle system or system authentication processing, and may simply transmit the authentication result to the server 2 when the result of the system authentication processing is "permitted." For example, in addition to the security method selection information, authentication information required for the system authentication processing (user's personal information, password information, etc.) may be stored in the in-vehicle memory, and the ECU 20 may execute the login processing and system authentication processing using the authentication information stored in the in-vehicle memory.

[0022] During the login process to the in-vehicle system, the ECU 20 transmits the user ID associated with the key ID to another ECU such as the ECU 30. The ECU 20 may transmit the user ID associated with the key ID to another ECU such as the ECU 30 before starting the login process to the in-vehicle system or during the system authentication process. In other words, the ECU 20 transmits the user ID associated with the key ID to another ECU before completing the system authentication process.

[0023] The ECU 30 controls the in-vehicle device 31. The in-vehicle device 31 is an actuator that controls an air conditioner, a seat position, a steering wheel position, a mirror inclination, etc. The user can set the air conditioning temperature setting, the seat position, the steering wheel position, the mirror inclination, the display in front of the driver's seat (display of speed, remaining energy, etc.), etc. according to preference, and the user setting information is stored in the in-vehicle memory in association with the user ID. When the ECU 30 acquires the user ID associated with the key ID via CAN communication, it operates the in-vehicle device 31 according to the user setting corresponding to the key ID. Since the ECU 30 acquires the user ID before the completion of the system authentication process, for example, during the login process to the in-vehicle system or during the system authentication, it can operate the actuator, the air conditioner, etc. included in the in-vehicle device 31 according to the user setting. As a result, for example, even if the login process or the system authentication process takes time, the in-vehicle device 31 can be operated according to the user's preference in a short time after the user gets into the vehicle.

[0024] Next, a control method for the in-vehicle system executed by the ECU 20 will be described with reference to Fig. 3. Fig. 3 is a flowchart showing a control process flow of the ECU 20. When the main switch is turned on, the ECU 20 executes the following control flow.

[0025] In step S1, the ECU 20 acquires a key ID from the ECU 10. In step S2, the ECU 20 identifies a user ID associated with the key ID. In step S3, the ECU 20 selects a security method associated with the user ID. In step S4, the ECU 20 transmits the user ID associated with the key ID to another ECU such as the ECU 30.

[0026] In step S5, the ECU 20 displays an authentication screen for authentication using a security method on the display 21. Fig. 4 shows an example of the authentication screen. The authentication screen includes a display 41 for accepting an operational input for the system authentication process, a guide display 42 for guiding the input operation, and a cancel button 43 for accepting an operation to cancel the system authentication process. For example, the user may touch the cancel button 43 if he or she wishes to change the security method, if he or she does not wish to use a service restricted by the system authentication process, or if he or she wishes to change the user.

[0027] Note that, prior to the control flow of step S5, the user ID associated with the key ID is transmitted to the ECU 30 by the control flow of step S4. Therefore, while the display 21 is displaying the authentication screen, the ECU 30 can control the in-vehicle device 31 in accordance with the user settings. That is, the operation of the in-vehicle device 31 in accordance with the user settings is executed while the authentication screen is being displayed.

[0028] In step S6, the ECU 20 determines whether or not a cancel operation has been input. If a cancel operation has been input, the ECU 20 executes the control process of steps S21 to S23. Note that if a certain period of time has elapsed (timeout) while the authentication screen of Fig. 4 is displayed on the display 21, the ECU 20 may execute the control process of steps S21 to S23, similarly to when a cancel operation has been input. The details of the control process of steps S21 to S23 will be described later.

[0029] In step S7, the ECU 20 executes a system authentication process based on the operation input entered on the display 41. In step S8, the ECU 20 determines whether the authentication result is permission. If the authentication result is not permission (step S8 "No"), in step S9, the ECU 20 displays an authentication result screen indicating that the authentication result is not permission. The authentication result screen includes, for example, a message indicating the authentication result "not permission", a display for accepting an operation input for changing the user, and a display for confirming whether or not to perform authentication again. Then, the ECU 20 determines whether or not an operation input for changing the user has been made. If there is no operation input for changing the user (step S9 "No"), that is, if a predetermined time has elapsed without an operation input while the authentication result screen is displayed, or if there is an operation input for performing authentication again, the ECU 20 executes the control flow of step S5. On the other hand, if there is an operation input for changing the user (step S9 "Yes"), the ECU 20 executes the control process of steps S21 to S23.

[0030] If the authentication result is permitted (step S8 "Yes"), in step S10, ECU 20 unlocks the in-vehicle system. In step S11, ECU 20 displays a welcome screen. FIG. 5 shows an example of a welcome screen. The welcome screen is a screen for notifying the user that the system authentication process has been permitted. The welcome screen includes a welcome message 51 including user information, and a user change display 52 for accepting changes to the user. In the example of FIG. 5, the welcome screen includes an icon 53 for a user for whom system authentication has been permitted. The welcome message includes a message "Welcome" welcoming use of the system, and a user name "AAAA".

[0031] Note that, prior to the control flow of step S11, the user ID associated with the key ID is transmitted to the ECU 30 by the control flow of step S4. Therefore, the ECU 30 can control the in-vehicle device 31 in accordance with the user settings before the display 21 displays the welcome screen. That is, the operation of the in-vehicle device 31 in accordance with the user settings may be executed before the system authentication process is completed.

[0032] In step S12, the ECU 20 determines whether or not there has been an operational input for changing the user (corresponding to a touch operation on the "user change display 52"). If there has been an operational input for changing the user ("Yes" in step S12), the ECU 20 executes the control process of steps S21 to S23. If there has been no operational input for changing the user ("No" in step S11), the ECU 20 ends the control flow shown in FIG. 3.

[0033] When it is determined in step S6 that a cancel operation has been input, or when it is determined in step S9 or S12 that a user change operation has been input, in step S21, the ECU 21 displays a user change screen. FIG. 6 shows an example of the user change screen. The user change screen is a screen that displays a list of user names registered in the in-vehicle system. In the example of FIG. 6, each user name is represented by an icon, and the user can change the user by touching the icon. Note that a display such that a logged-in user is highlighted may be used. In addition, the display in FIG. 6 includes an icon for a guest, and for example, a user who is not registered in the in-vehicle system can select a guest to use a part of the in-vehicle system in a limited manner. That is, when an operation input for canceling the system authentication process (corresponding to the touch operation of the cancel 43) has been input, or when an operation input for changing the user has been input (corresponding to the touch operation of the user change display 52) has been input, the ECU 20 displays a list of user names registered in the in-vehicle system on the display 21.

[0034] In step S22, the ECU 20 changes the user based on a touch operation on the user change screen. For example, assume that user B who owns an electronic key with a key ID (ID1) gets into the vehicle 1, and the ECU 20 executes the control flow up to step 21. In this case, as shown in FIG. 2, the key ID (ID1) corresponds to user A, so login to the in-vehicle system is performed with the user ID (user A). User B performs an operation to change the user, and selects the icon of user B on the user change screen. Based on the operation input of user B, the ECU 20 changes the user ID associated with the key ID (ID1) from user A to user B. In step S23, the ECU 20 updates the table so that the changed user ID and key ID are associated with each other. Then, the control flow returns to step S2.

[0035] After updating the table, the ECU 20 may transmit the changed user ID to another ECU such as the ECU 30. In the above description, the ECU 30 operates the in-vehicle device 31 according to the user setting corresponding to the key ID, but the ECU 30 may operate the in-vehicle device 31 according to the user setting corresponding to the user ID. In this case, the ECU 30 may first operate the in-vehicle device 31 according to the user setting corresponding to the user ID before the change, and then, after the user ID is changed, operate the in-vehicle device 31 according to the user setting corresponding to the changed user ID.

[0036] As described above, in this embodiment, the ECU 20 acquires the key ID assigned to the electronic key, and starts logging in to the in-vehicle system that outputs information to the occupant of the vehicle 1 using the user ID associated with the key ID. After logging in to the in-vehicle system, the ECU 20 executes a system authentication process to authenticate whether or not to permit use of the in-vehicle system using a security method set in association with the user ID, and unlocks the system if permission is granted in the system authentication process. This can eliminate the need to input a user ID to log in and to select a user ID each time, improving convenience. Furthermore, security can be ensured.

[0037] In the present embodiment, the security method is at least one of device authentication for authenticating with an external device, authentication using a PIN, pattern authentication, and password authentication, or a combination of these authentication methods, thereby ensuring security.

[0038] In this embodiment, when the system authentication process allows the ECU 20 to display a welcome message including user information and a user change display for accepting a change of the user on the display, the user ID can be changed when the lock is released with a wrong user ID.

[0039] In this embodiment, when an operation input is made to cancel the system authentication process or to change the user, the ECU 20 displays a list of user names registered in the in-vehicle system on the display, thereby allowing the user ID to be changed.

[0040] In this embodiment, the ECU 20 transmits at least one of the IDs, the key ID and the user ID, to another ECU before completing the system authentication process, so that the ECU 30 can operate the in-vehicle device 31 before completing the system authentication process.

[0041] In this embodiment, the ECU 20 receives a key ID signal from the ECU 10 that controls the lock mechanism of the vehicle via the in-vehicle communication network. This allows for a login process in which the key ID and the user ID are linked.

[0042] In this embodiment, the ECU 20 displays an authentication screen on the display 21 to receive an operation input for the system authentication process, and another ECU 30 that controls the in-vehicle device 31 operates the in-vehicle device 31 according to a user setting based on a user ID associated with a key ID, and the operation of the in-vehicle device 31 according to the user setting is executed while the authentication screen is displayed. This allows the ECU 30 to operate the in-vehicle device 31 before the system authentication process is completed. That is, the ECU 20 transmits a user ID associated with a key ID to the ECU 30 before unlocking the system by the system authentication process, so that the ECU 30 can operate the in-vehicle device 31 according to the user's preference in a short time.

[0043] In this embodiment, the ECU 20 transmits the user ID associated with the key ID to the other ECU such as the ECU 30 in the control flow of step S4, but the ECU 20 may transmit the key ID to the other ECU. The ECU 30 may identify the user ID associated with the key ID and operate the in-vehicle device 31 according to the user setting corresponding to the user ID. The ECU 20 in this embodiment corresponds to the "processor" or "controller" of the present invention. The ECU 20 does not need to execute all of the control flows shown in FIG. 3, and even if only a part of the flows is executed, the order of the control flows is not limited to the order of FIG. 3.

[0044] The control device of the in-vehicle system may be configured by a computer equipped with hardware and software, and may have a recording medium on which a program is recorded, and a processor for executing the program recorded on the recording medium. The location where the program is stored is not limited to a recording medium such as an in-vehicle memory, and for example, the program may be stored in a computer-readable and portable computer-readable recording medium (e.g., disk media, flash memory, etc.). In this case, the control device of the in-vehicle system may be configured to download the program from the computer-readable recording medium or the server 2 and execute the downloaded program.

[0045] The above-described embodiments are described for the purpose of facilitating understanding of the present invention, and are not described for the purpose of limiting the present invention. Therefore, the elements disclosed in the above embodiments are intended to include all design modifications and equivalents that fall within the technical scope of the present invention. [Explanation of symbols]

[0046] 1 vehicle 2 Server 10~30 ECU 11 Near field communication device 12 Locking mechanism 21 Display 31 In-vehicle equipment

Claims

1. A method for controlling an in-vehicle system, the method comprising: The processor, Obtain the key ID assigned to the electronic key, A login to the in-vehicle system that outputs information to a vehicle occupant is initiated using a user ID associated with the key ID; After logging in to the in-vehicle system, a system authentication process is executed to authenticate whether or not to permit use of the in-vehicle system using a security method set in correspondence with the user ID; The method of controlling an in-vehicle system further comprises unlocking the in-vehicle system if permitted by the system authentication process.

2. 2. A method for controlling an in-vehicle system according to claim 1, comprising: The security method is at least one of device authentication for authenticating with an external device, authentication using a PIN, pattern authentication, and password authentication, or a combination of these authentication methods.

3. A method for controlling an in-vehicle system according to claim 1 or 2, comprising: The processor, The vehicle system control method further comprises displaying, on a display, a welcome message including user information and a user change display for accepting changes made by the user, when authorization is granted in the system authentication process.

4. A method for controlling an in-vehicle system according to claim 1 or 2, comprising: The processor, A control method for a vehicle system, which displays a list of user names registered in the in-vehicle system on a display when an operational input is made to cancel the system authentication process or to change the user.

5. A method for controlling an in-vehicle system according to claim 1 or 2, comprising: The ECU having the processor includes: A control method for an in-vehicle system, comprising: transmitting at least one of the key ID and the user ID to another ECU before completing the system authentication process.

6. A method for controlling an in-vehicle system according to claim 1 or 2, comprising: The processor, The method of controlling an in-vehicle system includes receiving the key ID signal from an ECU that controls a lock mechanism of the vehicle via an in-vehicle communication network.

7. A method for controlling an in-vehicle system according to claim 1 or 2, comprising: the ECU having the processor displays an authentication screen on a display for receiving an operation input for the system authentication process; The other ECU that controls the in-vehicle device operates the in-vehicle device according to a user setting based on the user ID associated with the key ID, The method for controlling a vehicle system, wherein the operation of the in-vehicle device in accordance with the user setting is executed while the authentication screen is being displayed.

8. A controller for controlling an in-vehicle system is provided. The controller: Obtain the key ID assigned to the electronic key, A login to the in-vehicle system that outputs information to a vehicle occupant is initiated using a user ID associated with the key ID; After logging in to the in-vehicle system, a system authentication process is executed to authenticate whether or not to permit use of the in-vehicle system using a security method set in correspondence with the user ID; A control device for an in-vehicle system that unlocks the in-vehicle system when permission is granted in the system authentication process.

9. A control program for causing a controller included in a control device to execute a step of controlling an in-vehicle system, obtaining a key ID assigned to the electronic key; A step of initiating a login to the in-vehicle system that outputs information to a vehicle occupant using a user ID associated with the key ID; executing a system authentication process for authenticating whether or not to permit use of the in-vehicle system using a security method set in association with the user ID after logging in to the in-vehicle system; unlocking the in-vehicle system if permitted by the system authentication process; A computer-readable control program for causing the computer to execute the control program.

Images