Electronic control device, function restriction management system, function restriction management method, and function restriction management program
The functional restriction management system sets priorities for vehicle theft prevention, ensuring that thieves cannot cancel restrictions, effectively preventing vehicle operation and use during theft, thus protecting the vehicle's functionality and limiting damage.
Patent Information
- Application Number
- PCT/JP2024/016888
- Authority / Receiving Office
- WO · WO
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-05-30
- Filing Date
- 2024-05-02
- Publication Date
- 2024-12-05
AI Technical Summary
Existing vehicle theft prevention systems fail to effectively prevent thieves from canceling functional restrictions set by vehicle owners, allowing stolen vehicles to be operated or used without limitations.
A functional restriction management system that sets priorities for functional restrictions, determining whether they can be canceled based on predefined operation types and routes, ensuring that thieves cannot lift restrictions set by owners, even if they attempt to do so using different operation routes.
Prevents thieves from canceling functional restrictions, maintaining the effectiveness of vehicle theft prevention measures by ensuring that only authorized owners can lift restrictions, thereby protecting the vehicle's functionality and limiting damage during theft.
Smart Images

Figure JP2024016888_05122024_PF_FP_ABST
Abstract
Description
Electronic control device, function restriction management system, function restriction management method, and function restriction management program CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is based on Japanese Application No. 2023-88684, filed on May 30, 2023, the contents of which are incorporated herein by reference.
[0002] The present disclosure relates to an electronic control device, a function restriction management system, a function restriction management method, and a function restriction management program.
[0003] Anti-theft devices for preventing vehicle theft have been available. For example, Patent Document 1 discloses a system that allows a vehicle to travel within a predetermined area such as a valet parking lot, but restricts the vehicle's travel when the vehicle is outside the predetermined area, thereby preventing the vehicle from leaving the predetermined area.
[0004] JP 2010-922 A
[0005] In recent years, there have been features that aim not only to prevent vehicle theft but also to mitigate damage if the vehicle is stolen, by setting functional restrictions when the vehicle is stolen and then releasing the functional restrictions when the theft is resolved. However, even if the owner of a stolen vehicle sets functional restrictions, if the thief who stole the vehicle can release the functional restrictions, the functional restrictions will not be effective against vehicle theft.
[0006] The present disclosure aims to appropriately obtain the effect of restricting functions against vehicle theft.
[0007] According to one aspect of the present disclosure, a function restriction setting unit sets function restrictions against vehicle theft. A release possibility determination unit determines whether the function restrictions set by the function restriction setting unit can be released based on a priority. A function restriction release unit releases the function restrictions set by the function restriction setting unit on the condition that the release possibility determination unit has determined that the function restrictions can be released.
[0008] Whether or not a function restriction can be released is determined based on a priority, and the function restriction is released only if it is determined that the function restriction can be released. By setting a priority for determining whether or not a function restriction can be released, it is possible to prevent a situation in which a thief who has stolen a vehicle can release a function restriction that was set by the owner of the stolen vehicle. This allows the effect of the function restriction against vehicle theft to be appropriately achieved.
[0009] The above and other objects, features and advantages of the present disclosure will become more apparent from the following detailed description taken in conjunction with the accompanying drawings. 1 is a functional block diagram showing the overall configuration of the first embodiment, FIG. 2 is a functional block diagram of an electronic control unit, FIG. 3 is a diagram showing routes corresponding to function restriction setting operations or release operations, FIG. 4 is a diagram showing the relationship between priority and release possibility, FIG. 5 is a flowchart showing function restriction setting processing by a first route, FIG. 6 is a flowchart showing function restriction setting processing by the first route, FIG. 7 is a flowchart showing function restriction setting processing by the first route, FIG. 8 is a flowchart showing function restriction setting processing by the first route, FIG. 9 is a flowchart showing function restriction setting processing by the second route, FIG. 10 is a flowchart showing function restriction setting processing by the second route, FIG. 11 is a flowchart showing function restriction setting processing by the second route, FIG. 12 is a flowchart showing function restriction setting processing by the second route, FIG. 13 is a flowchart showing function restriction setting processing by the third route, FIG. 14 is a flowchart showing function restriction setting processing by the third route, and 5 is a flowchart showing the function restriction release process, FIG. 16 is a diagram showing the transition of display accompanying the setting of function restriction by the first route, FIG. 17 is a diagram showing the transition of display accompanying the setting of function restriction by the first route, FIG. 18 is a diagram showing the transition of display accompanying the setting of function restriction by the first route, FIG. 19 is a diagram showing the transition of display accompanying the setting of function restriction by the first route, FIG. 20 is a diagram showing the transition of display accompanying the release of function restriction by the first route, and FIG. 21 is a diagram showing the transition of display accompanying the release of function restriction by the first route. 22 is a diagram showing a transition of display accompanying the release of functional restrictions via the first route, FIG. 23 is a diagram showing a transition of display accompanying the release of functional restrictions via the first route, FIG. 24 is a diagram showing a transition of display accompanying the setting of functional restrictions via the second route, FIG. 25 is a diagram showing a transition of display accompanying the setting of functional restrictions via the second route, FIG. 26 is a diagram showing a transition of display accompanying the setting of functional restrictions via the second route, FIG. 27 is a diagram showing a transition of display accompanying the setting of functional restrictions via the second route, and FIG. 28 is a diagram showing a transition of display accompanying the setting of functional restrictions via the second route.36 is a diagram showing the display transition when functional restrictions are released by the third route; FIG. 37 is a diagram showing the display transition when functional restrictions are released by the third route; FIG. 38 is a flowchart showing the function restriction release processing of the second embodiment; FIG. 39 is a flowchart showing the function restriction release processing of the third embodiment; and FIG. 40 is a flowchart showing the function restriction release processing. ,
[0010] Hereinafter, several embodiments will be described with reference to the drawings. In the following embodiments, descriptions of parts that overlap with the preceding embodiments will be omitted. (First Embodiment)
[0011] The first embodiment will be described with reference to Figures 1 to 37. A function restriction management system 1 mounted on a vehicle is configured so that a vehicle system 2 mounted on the vehicle and a server 3 can communicate data with each other via a communication network 4. The vehicle system 2 is configured so that an on-board communication device (hereinafter referred to as a DCM (Data Communication Module)) 5, electronic control units (hereinafter referred to as ECUs (Electronic Control Units)) 6 to 9, and an HMI (Human Machine Interface) control unit (hereinafter referred to as an HCU (HMI Control Unit)) 10 can communicate data with each other via an on-board network 11.
[0012] The in-vehicle network 11 is, for example, a Controller Area Network (CAN) (registered trademark). The in-vehicle network 11 may be a FLEXRAY (registered trademark), a Clock Extension Peripheral Interface (CXPI) (registered trademark), an Ethernet (registered trademark), or the like. In this embodiment, a configuration in which four ECUs 6 to 9 are connected to the in-vehicle network 11 is illustrated as an example, but the number of ECUs connected to the in-vehicle network 11 is arbitrary. Furthermore, the number of in-vehicle networks 11 is also arbitrary.
[0013] The DCM 5 is wirelessly connected to the server 3 via the communication network 4, and is also wirelessly connected to an external device 15 (described later) without using the communication network 4. The ECU 6 is a device that controls the setting and release of function restrictions against vehicle theft. Functions against vehicle theft are functions that would cause disadvantage to the owner of a stolen vehicle, such as functions related to driving, and functions related to charges for using paid services or downloading paid apps.
[0014] Setting a function restriction means enabling the relevant function restriction and prohibiting the use of all or part of the function. For example, if the relevant function is related to driving, it means prohibiting engine start or motor start or limiting the driving speed to a low speed. For example, if the relevant function is related to charges such as the use of paid services or the download of paid apps, it means prohibiting the use of paid services or the download of paid apps in whole or in part.
[0015] Lifting a function restriction means disabling the relevant function restriction and allowing the use of all or part of a function that was previously prohibited. For example, if the relevant function is related to driving, it means allowing the engine or motor to start or lifting restrictions on driving speed. For example, if the relevant function is related to charges such as the use of paid services or the download of paid apps, it means allowing the use of paid services or the download of paid apps in whole or in part.
[0016] That is, by setting the function restrictions on the stolen vehicle by the owner of the stolen vehicle, even if the thief attempts to start the engine or motor, the thief can prohibit the engine or motor from starting. Furthermore, even if the thief attempts to use a paid service that requires payment or download a paid app, the use of the paid service or the download of the paid app can be prohibited. After the theft is resolved, the vehicle owner can cancel the function restrictions, allowing the vehicle owner to start the engine or motor, for example. Furthermore, the use of paid services and the download of paid apps can be permitted. The ECU 6 is connected to a battery power supply (+B) supplied from the vehicle battery and can operate even when the vehicle power is off.
[0017] The other ECUs 7 to 9 are, for example, a device that controls the drive system, a device that controls the ADAS (Advanced Driving Assistant System), a device that controls the multimedia system, and the like.
[0018] The HCU 10 is connected to a center information display (CID) 12, a meter device 13, and a head-up display (HUD) 14. The CID 12 is located in front of the driver's seat and displays, for example, a map used for the navigation function, camera images for the parking assist function, audio information, and air conditioning information. The meter device 13 is located in front of the driver's seat and includes various indicators that display vehicle speed, shift position, remaining fuel level, warnings, etc. The HUD 14 projects information such as vehicle speed, shift position, and route guidance onto the windshield as a virtual image in front of the driver's seat. Like the ECU 6 described above, the HCU 10 is also connected to a battery power supply (+B) supplied from the vehicle battery and can operate even when the vehicle power supply is off.
[0019] The external device 15 is capable of data communication with the vehicle system 2 by wirelessly connecting to the DCM 5 via the communication network 4. The external device 15 is a portable information terminal such as a smartphone or a tablet terminal that can be carried by the occupant, and is a terminal that can be used by the occupant inside or outside the vehicle.
[0020] An operation input unit 16 that can be operated and input by the occupant is connected to the HCU 10. The operation input unit 16 is, for example, a touch panel of the CID 12, a steering switch disposed on the steering wheel, or the like.
[0021] As shown in FIG. 2 , the ECU 6 includes a control unit 17 and a CAN communication unit 18. The control unit 17 is primarily configured as a microcomputer having a CPU (Central Processing Unit), ROM (Read Only Memory), RAM (Random Access Memory), and I / O (Input / Output). The functions provided by the control unit 17 can be provided by software recorded in a physical memory device and a computer that executes the software, software alone, hardware alone, or a combination thereof. For example, if the control unit 17 is provided by a hardware electronic circuit, the hardware can be a digital circuit or analog circuit including multiple logic circuits. When the control unit 17 executes a program stored in a non-transient physical recording medium, processing corresponding to the control program is performed, and a method corresponding to the program is executed.
[0022] The CAN communication unit 18 controls the transmission and reception of CAN signals to and from the in-vehicle network 11 .
[0023] The control unit 17 includes a function restriction setting unit 17a, a priority setting unit 17b, a priority holding unit 17c, a priority updating unit 17d, a release possibility determination unit 17e, a determination result notification unit 17f, and a function restriction release unit 17g. The units 17a to 17g constitute a function restriction management program.
[0024] The function restriction setting unit 17a sets function restrictions to prevent vehicle theft. The functions to be restricted may be selectable in advance by the vehicle owner, or may be set in advance when the vehicle is shipped from the factory or sold. For example, when setting a function restriction related to driving, the function restriction setting unit 17a transmits a function restriction setting signal to the ECU that controls engine start, the ECU that controls motor start, the ECU that controls driving, etc., and prohibits engine start or motor start or limits the driving speed to a low speed, as described above. The priority setting unit 17b sets a priority, which will be described later, based on the operation type corresponding to the operation to set or release the function restriction. The operation type will be described later.
[0025] When the priority is set by the priority setting unit 17b, the priority holding unit 17c holds the set priority as priority information. The priority update unit 17d updates the priority information held by the priority holding unit 17c. That is, when the priority information is updated by the priority update unit 17d, the priority holding unit 17 holds the updated priority information. Priorities will also be described later.
[0026] The release possibility determination unit 17e determines whether the function restriction set by the function restriction setting unit 17a can be released based on the priority according to the operation type stored in the priority storing unit 17c. When the release possibility determination unit 17e determines whether the function restriction can be released, the determination result notifying unit 17f notifies the determination result.
[0027] When the release possibility determination unit 17e determines whether the function restriction should be released, the function restriction release unit 17g does not release the function restriction set by the function restriction setting unit 17a. When the release possibility determination unit 17e determines whether the function restriction should be released, the function restriction release unit 17g releases the function restriction set by the function restriction setting unit 17a. When the function restriction release unit 17g releases the function restriction related to driving, for example, the function restriction release unit 17g transmits a function restriction release signal to the ECU that controls engine start, the ECU that controls motor start, the ECU that controls driving, etc., and allows engine start or motor start or releases the limit on driving speed as described above.
[0028] Operation types corresponding to the setting operation or the release operation of the function restriction will be described. As shown in FIG. 3 , there are three types of operation corresponding to the setting operation or the release operation of the function restriction: an operation via communication from the external device 15 through the communication network 4 (hereinafter, this may be referred to as an operation via a first route), an operation via short-range wireless communication from the external device 15 (hereinafter, this may be referred to as an operation via a second route), and an operation from the operation input unit 16 (hereinafter, this may be referred to as an operation via a third route). The short-range wireless communication is communication in which the external device 15 and the DCM 5 are directly connected wirelessly, such as Bluetooth (registered trademark) or Wi-Fi (registered trademark). If the DCM 5 is configured to be connectable via a wired connection, the second route may be communication in which the external device 15 and the DCM 5 are directly connected via a wired connection, such as a USB (Universal Serial Bus) interface. Each operation will be described below.
[0029] In the operation via the first route, the vehicle owner operates the external device 15 to transmit a function restriction setting request or a function restriction release request from the external device 15 to the HCU 10 of the vehicle system 2 via the server 3. Since the function restriction setting request or the function restriction release request is transmitted from the external device 15 to the HCU 10 via the server 3, user authentication is performed in three stages: the external device 15, the server 3, and the vehicle system 2. In this case, it is assumed that, for example, the vehicle owner notices that the vehicle has been stolen some time after getting out of the vehicle, and the external device 15 is unable to communicate with the DCM 5 via short-range wireless communication.
[0030] For example, if a vehicle owner leaves a parking spot after parking and returns to the parking spot only to find that the vehicle that should have been parked is not there, the owner can operate external device 15 to wirelessly connect to server 3 and cause external device 15 to transmit a function restriction setting request to server 3. When server 3 receives the function restriction setting request from external device 15, it transmits the received function restriction setting request to DCM 5 associated with external device 15 that sent the function restriction setting request. When DCM 5 receives the function restriction setting request from server 3, it transmits the received function restriction setting request to HCU 10. That is, in an operation to set function restrictions via the first route, a function restriction setting request is transmitted from external device 15 to HCU 10 via server 3. The above describes the operation to set function restrictions. The same applies to an operation to release function restrictions. When releasing function restrictions via the first route, a function restriction release request is transmitted from external device 15 to HCU 10 via server 3. The operation via the first route performs user authentication in three stages, and therefore has the highest authentication accuracy.
[0031] The operation via the second route is an operation in which the vehicle owner operates the external device 15 to send a function restriction setting request or a function restriction release request from the external device 15 to the HCU 10 of the vehicle system 2 without going through the server 3. Because the function restriction setting request or the function restriction release request is sent from the external device 15 to the HCU 10 without going through the server 3, user authentication is performed in two stages: the external device 15 and the vehicle system 2. In this case, it is assumed that the vehicle is stolen immediately after the vehicle owner parks or gets out of the vehicle, and that the external device 15 is capable of short-range wireless communication with the DCM 5.
[0032] For example, if the vehicle owner is threatened after parking and exits the vehicle, the vehicle owner operates the external device 15 to send a function restriction setting request from the external device 15 to the DCM 5. When the DCM 5 receives the function restriction setting request from the server 3, it transmits the received function restriction setting request to the HCU 10. That is, in the operation to set a function restriction via the second route, the function restriction setting request is sent from the external device 15 to the HCU 10 without going through the server 3. The above describes the operation to set a function restriction. The operation to release a function restriction is similar. In the operation to release a function restriction via the second route, the function restriction release request is sent from the external device 15 to the HCU 10 without going through the server 3. Because the operation via the second route involves two-stage user authentication, the authentication accuracy is second only to the operation via the first route. Note that, for example, the vehicle owner may first set a function restriction via the second route and then set a function restriction via the first route. By performing an operation to set function restrictions via the second route and then performing an operation to set function restrictions via the first route, it is possible to increase the accuracy of authentication.
[0033] The operation via the third route is an operation in which the vehicle owner operates the operation input unit 16 to directly transmit a function restriction setting request or a function restriction release request from the operation input unit 16 to the HCU 10. Since the function restriction setting request or the function restriction release request is transmitted from the operation input unit 16 to the HCU 10, user authentication is performed at a single stage in the vehicle system 2. In this case, it is assumed that, for example, the vehicle is stolen before the vehicle owner gets out of the vehicle, and the operation input unit 16 is operable.
[0034] For example, if the vehicle owner is threatened before getting out of the vehicle, the vehicle owner operates the operation input unit 16 to send a function restriction setting request from the operation input unit 16 to the HCU 10. That is, the function restriction setting request is sent directly from the operation input unit 16 to the HCU 10. The above describes the operation for setting function restrictions, but the operation for releasing function restrictions is similar. In the operation for releasing function restrictions via the third route, the function restriction release request is sent directly from the operation input unit 16 to the HCU 10. The operation via the third route performs user authentication in one step, and therefore has the lowest authentication accuracy. Note that, for example, the vehicle owner may perform the operation for setting function restrictions via the third route, and then the operation for setting function restrictions via the first route or the second route. By performing the operation for setting function restrictions via the third route, and then the operation for setting function restrictions via the first route or the second route, the authentication accuracy can be increased. Furthermore, for example, the owner of the vehicle may park the vehicle and operate the operation input unit 16 to send a function restriction setting request from the operation input unit 16 to the HCU 10 for preventive safety reasons, not just in cases where the owner has been threatened, before getting out of the vehicle.
[0035] As described above, function restriction setting requests and function restriction release requests are aggregated at the HCU 10 regardless of the route. Therefore, the priority setting unit 17b acquires information about the routes of the function restriction setting requests and function restriction release requests from the HCU 10. After acquiring the route information from the HCU 10, the priority setting unit 17b sets priorities for three routes corresponding to the function restriction setting or release operations. The priority setting unit 17b sets the priority of the first route to "1," the priority of the second route to "2," and the priority of the third route to "3." Here, the smaller the priority number, the higher the priority and the higher the priority should be, and the larger the priority number, the lower the priority and the lower the priority should be. Once the priorities are set by the priority setting unit 17b in this manner, the priority holding unit 17c holds the set priorities as priority information.
[0036] 4, the release possibility determination unit 17e determines whether the function restriction can be released by comparing the priority of the function restriction release request with the priority of the function restriction setting request for the function restriction setting request. If the release possibility determination unit 17e determines that the priority of the function restriction release request is higher than the priority of the function restriction setting request or that the priority of the function restriction release request matches the priority of the function restriction setting request, the release possibility determination unit 17e determines whether the function restriction can be released. On the other hand, if the priority of the function restriction release request is lower than the priority of the function restriction setting request, the release possibility determination unit 17e determines whether the function restriction can be released.
[0037] For example, if the function restriction setting request is via the first route and the function restriction release request is via the first route, the release possibility determination unit 17e determines that the priority of the function restriction release request matches the priority of the function restriction setting request, and specifies whether the function restriction set via the first route can be released. On the other hand, if the function restriction setting request is via the first route and the function restriction release request is via the second or third route, the release possibility determination unit 17e determines that the priority of the function restriction release request is lower than the priority of the function restriction setting request, and specifies whether the function restriction set via the first route can be released. In other words, if the owner of a stolen vehicle sets a function restriction via the first route, the function restriction will not be released even if the thief who stole the vehicle attempts to release the function restriction via the third route.
[0038] For example, if the function restriction setting request is via the second route and the function restriction release request is via the first or second route, the release possibility determination unit 17e determines that the priority of the function restriction release request is higher than the priority of the function restriction setting request or that the priority of the function restriction release request matches the priority of the function restriction setting request, and specifies whether the function restriction set via the second route can be released. On the other hand, if the function restriction setting request is via the second route and the function restriction release request is via the third route, the release possibility determination unit 17e determines that the priority of the function restriction release request is lower than the priority of the function restriction setting request, and specifies whether the function restriction set via the second route can be released. In other words, if the owner of a stolen vehicle sets a function restriction via the second route, the function restriction will not be released even if the thief who stole the vehicle attempts to release the function restriction via the third route.
[0039] In this way, the owner of a stolen vehicle can operate the external device 15 to set the function restriction via the first route or the second route, so that even if the stolen vehicle operates the operation input unit 16 to release the function restriction via the third route, the function restriction can continue to be set without releasing the function restriction, thereby minimizing damage caused by the theft. Furthermore, after the theft is resolved, the owner of the vehicle can release the function restriction via the first route or the second route by operating the external device 15.
[0040] Next, the operation of the above-described configuration will be described with reference to Figures 5 to 37. Here, the function restriction setting process according to the first route, the function restriction setting process according to the second route, the function restriction setting process according to the third route, and the function restriction release process will be described in this order.
[0041] (1-1) Function Restriction Setting Process via First Route (See FIGS. 5 to 8) The external device 15, the server 3, and the vehicle system 2 cooperate to perform the function restriction setting process via the first route. When the vehicle owner activates an app for setting function restrictions on the external device 15, the external device 15 activates the app for setting function restrictions (S1), displays a password entry screen, for example, and waits for the password entry operation. When the vehicle owner enters the password, the external device 15 transmits authentication information required for user authentication, including the password entered by the vehicle owner, to the server 3 (S2).
[0042] When the server 3 receives the authentication information from the external device 15, it compares the received authentication information with pre-registered information and determines whether the authentication is successful (S3). If the server 3 determines that the authentication information does not match the registered information and determines that the authentication has failed (S3: NO), it transmits authentication failure information indicating that the authentication has failed and the reason for the authentication failure to the external device 15 (S4). When the external device 15 receives the authentication failure information from the server 3, it displays that the authentication has failed and the reason for the authentication failure (S5).
[0043] The external device 15 determines whether to retry user authentication (S6). If it determines that the vehicle owner has performed an operation on the external device 15 not to retry user authentication, or that the external device 15 has timed out without performing any operation (S6: NO), the application for setting function restrictions is terminated, and the function restriction setting process via the first route is terminated.
[0044] If it is determined that the vehicle owner has performed an operation to retry user authentication on the external device 15 (S6: YES), the process returns to step S2, and the external device 15 displays, for example, a password input screen again and waits for the password input operation again. When the vehicle owner performs the password input operation again, the external device 15 repeats step S3 and subsequent steps. Note that the number of times user authentication is retried may be limited, and if the number of user authentication retries exceeds a predetermined number, the external device 15 may forcibly terminate the application that sets the function restriction and forcibly terminate the function restriction setting process via the first route.
[0045] When the server 3 determines that the authentication information matches the registration information and determines that the authentication has been successful (S3: YES), it transmits authentication success information indicating that the authentication has been successful to the external device 15 (S7).
[0046] When the external device 15 receives the authentication success information from the server 3, it displays a message indicating that the authentication has been successful (S8). The external device 15 displays a function restriction setting screen and waits for a function restriction setting operation (S9). When the vehicle owner performs a function restriction setting operation, the external device 15 accepts the function restriction setting by the vehicle owner's setting operation (S10) and transmits a function restriction setting request indicating the accepted function restriction setting to the server 3 (S11).
[0047] The external device 15 determines whether the transmission of the function restriction setting request to the server 3 was successful (S12). If the external device 15 determines that the transmission of the function restriction setting request to the server 3 failed (S12: NO), for example, by determining that a timeout has occurred without receiving a response confirmation for the function restriction setting request from the server 3, the external device 15 displays a message indicating that the transmission of the function restriction setting request failed (S13), terminates the application that sets the function restrictions, and terminates the function restriction setting process via the first route.
[0048] Furthermore, the external device 15 determines whether to retry sending the function restriction setting request to the server 3, and if it determines that the vehicle owner has performed an operation on the external device 15 that does not retry sending the function restriction setting request to the server 3, or that the vehicle owner has timed out without performing any operation, it may terminate the app that sets the function restrictions and end the function restriction setting process via the first route.
[0049] If it is determined that the vehicle owner has performed an operation on the external device 15 to retry sending the function restriction setting request to the server 3, the process may return to step S9 and repeat step S9 and subsequent steps. Alternatively, the number of retries may be limited, and if the number of retries exceeds a predetermined number, the external device 15 may forcibly terminate the application that sets the function restrictions and forcibly terminate the function restriction setting process via the first route.
[0050] For example, when the external device 15 determines that it has received a response confirmation for the function restriction setting request from the server 3 and determines that the transmission of the function restriction setting request to the server 3 was successful (S12: YES), it displays a message indicating that the transmission of the function restriction setting request was successful.
[0051] When the server 3 receives a function restriction setting request from the external device 15, it transmits the received function restriction setting request to the DCM 5 associated with the external device 15 (S14). The server 3 determines whether the transmission of the function restriction setting request to the DCM 5 was successful (S15). If the server 3 determines that the transmission of the function restriction setting request to the DCM 5 failed (S15: NO), for example, by determining that a timeout has occurred without receiving a response confirmation for the function restriction setting request from the DCM 5, the server 3 transmits a transmission failure notification indicating the failure of the transmission of the function restriction setting request to the external device 15.
[0052] When the external device 15 receives the transmission failure notification from the server 3, it displays a message indicating that the transmission of the function restriction setting request has failed (S16), terminates the application for setting the function restrictions, and terminates the function restriction setting process via the first route. Note that the external device 15 may determine whether to retry transmission of the function restriction setting request from the server 3 to the DCM 5, and if it determines that the vehicle owner has performed an operation in the external device 15 not to retry transmission of the function restriction setting request from the server 3 to the DCM 5, or that a timeout has occurred without the vehicle owner performing an operation, it may terminate the application for setting the function restrictions and terminate the function restriction setting process via the first route.
[0053] If it is determined that the vehicle owner has performed an operation in the external device 15 to retry transmission of the function restriction setting request from the server 3 to the DCM 5, the process may return to step S11 and repeat step S11 and subsequent steps. Alternatively, the number of retries may be limited, and if the number of retries exceeds a predetermined number, the external device 15 may forcibly terminate the application that sets the function restrictions and forcibly terminate the function restriction setting process via the first route.
[0054] For example, when server 3 determines that it has received a response confirmation of the function restriction setting request from DCM 5 and determines that the transmission of the function restriction setting request to DCM 5 was successful (S15: YES), server 3 transmits a transmission success notification indicating the successful transmission of the function restriction setting request to external device 15. When external device 15 receives the transmission success notification from server 3, it displays that the transmission of the function restriction setting request was successful (S17).
[0055] When the DCM 5 receives a function restriction setting request from the server 3, the DCM 5 transmits the received function restriction setting request to the HCU 10. When the HCU 10 receives a function restriction setting request from the DCM 5, the HCU 10 transmits the received function restriction setting request to the ECU 6.
[0056] When the ECU 6 receives the function restriction setting request from the HCU 10, the ECU 6 determines whether or not it holds priority information at that time (S18). If the ECU 6 determines that it does not hold priority information (S18: NO), it sets function restrictions based on the received function restriction setting request (S19, which corresponds to the function restriction setting procedure), and determines whether or not the function restriction setting was successful (S20).
[0057] For example, after transmitting a function restriction setting signal to a corresponding ECU, the ECU 6 determines that a timeout has occurred without receiving a response signal to the function restriction setting signal from the ECU, and when it determines that the function restriction setting has failed (S20: NO), it transmits a setting failure notice indicating that the function restriction setting has failed to the external device 15. When the external device 15 receives the setting failure notice from the ECU, it displays that the function restriction setting has failed (S21), terminates the application that sets the function restriction, and terminates the function restriction setting process via the first route.
[0058] For example, after transmitting a function restriction setting signal to a corresponding ECU, the ECU 6 determines that it has received a response signal to the function restriction setting signal from the corresponding ECU, and if it determines that the function restriction setting was successful (S20: YES), it transmits a setting success notice indicating that the function restriction setting was successful to the external device 15. When the external device 15 receives the setting success notice from the ECU, it displays that the function restriction setting was successful (S22).
[0059] The ECU 6 determines the route of the function restriction setting request. If the ECU 6 determines that the function restriction setting request is the first route (S23: YES), it sets the priority information to "1" (S24). If the ECU 6 determines that the function restriction setting request is the second route (S25: YES), it sets the priority information to "2" (S26). If the ECU 6 determines that the function restriction setting request is the third route (S27: YES), it sets the priority information to "3" (S28).
[0060] When the ECU 6 sets the priority information, it transmits a priority setting notification indicating that the priority information has been set to the HCU 10, and also causes the DCM 5 to transmit the same to the server 3. When the HCU 10 receives the priority setting notification from the ECU 6, it causes the CID 12 and the meter device 13 to display that the priority information has been set (S29). When the server 3 receives the priority setting notification from the DCM 5, it causes the server 3 to transmit the received priority setting notification to the external device 15 (S30). When the external device 15 receives the priority setting notification from the server 3, it displays that the priority information has been set (S31), and ends the function restriction setting process via the first route.
[0061] On the other hand, if the ECU 6 determines that it holds priority information (S18: YES), it identifies the route of the function restriction setting request (S32), sets the priority of the identified route of the function restriction setting request as the current priority, and compares the current priority with the priority of the held priority information (S33). If the ECU 6 determines that the current priority is higher than the priority of the priority information (S33: YES), it updates the priority information to the current priority (S34) and performs step S29 and subsequent steps. If the ECU 6 determines that the current priority matches the priority of the priority information or that the current priority is lower than the priority of the priority information (S33: NO), it does not update the priority information to the current priority and performs step S29 and subsequent steps.
[0062] (1-2) Function Restriction Setting Process via Second Route (See FIGS. 9 to 12) The external device 15 and the vehicle system 2 cooperate to perform the function restriction setting process via the second route. When the vehicle owner activates an application for setting function restrictions on the external device 15, the external device 15 activates the application for setting function restrictions (S41), displays a password entry screen, for example, and waits for the password entry operation. When the vehicle owner enters the password, the external device 15 transmits authentication information required for user authentication, including the password entered by the vehicle owner, to the DCM 5 (S42).
[0063] When the DCM 5 receives authentication information from the external device 15, it transmits the received authentication information to the HCU 10. When the HCU 10 receives the authentication information from the DCM 5, it compares the received authentication information with pre-registered registration information and determines whether the authentication was successful (S43). When the HCU 10 determines that the authentication information does not match the registration information and determines that the authentication has failed (S43: NO), it transmits authentication failure information to the DCM 5 indicating that the authentication has failed and indicating the reason for the authentication failure. When the DCM 5 receives the authentication failure information from the HCU 10, it transmits the received authentication failure information to the external device 15 (S44). When the external device 15 receives the authentication failure information from the DCM 5, it displays that the authentication has failed and the reason for the authentication failure (S45).
[0064] In this case, the external device 15 also determines whether to retry user authentication (S46). If it determines that the vehicle owner has performed an operation on the external device 15 not to retry user authentication, or that the external device 15 has timed out without the vehicle owner performing any operation (S46: NO), the application for setting function restrictions is terminated, and the function restriction setting process via the second route is terminated.
[0065] If it is determined that the vehicle owner has performed an operation to retry user authentication on the external device 15 (S46: YES), for example, the password input screen is displayed again and the external device 15 waits for the password input operation again. When the vehicle owner performs the password input operation again, the external device 15 returns to step S42 and repeats step S42 and subsequent steps. Note that the number of times user authentication is retried may be limited, and if the number of user authentication retries exceeds a predetermined number, the external device 15 may forcibly terminate the application that sets the function restriction and forcibly terminate the function restriction setting process via the second route.
[0066] When the HCU 10 determines that the authentication information matches the registration information and determines that the authentication is successful (S43: YES), it transmits authentication success information indicating that the authentication is successful to the DCM 5 (S47). When the DCM 5 receives the authentication success information from the HCU 10, it transmits the received authentication success information to the external device 15.
[0067] When the external device 15 receives the authentication success information from the DCM 5, it displays a message that the authentication has been successful (S48), displays a function restriction setting screen, and waits for a function restriction setting operation (S49).
[0068] When the vehicle owner performs a function restriction setting operation, the external device 15 accepts the function restriction setting by the setting operation from the vehicle owner (S50), and transmits a function restriction setting request indicating the accepted function restriction setting to the DCM 5 (S51).
[0069] The external device 15 determines whether the transmission of the function restriction setting request to the DCM 5 was successful (S52). If the external device 15 determines that the transmission of the function restriction setting request to the DCM 5 failed (S52: NO), it displays a message indicating that the transmission of the function restriction setting request to the DCM 5 failed (S53), terminates the application for setting the function restrictions, and terminates the function restriction setting process via the second route. Note that the external device 15 may also determine whether to retry the transmission of the function restriction setting request to the DCM 5, and if it determines that the vehicle owner has performed an operation on the external device 15 that does not retry the transmission of the function restriction setting request to the DCM 5, or that a timeout has occurred without the vehicle owner performing an operation, it may terminate the application for setting the function restrictions and terminate the function restriction setting process via the second route.
[0070] If it is determined that the vehicle owner has performed an operation on the external device 15 to retry sending the function restriction setting request to the DCM 5, the process may return to step S51 and repeat step S51 and subsequent steps. Alternatively, the number of retries may be limited, and if the number of retries exceeds a predetermined number, the external device 15 may forcibly terminate the application that sets the function restrictions and forcibly terminate the function restriction setting process via the second route.
[0071] When the external device 15 determines that the transmission of the function restriction setting request to the DCM 5 has been successful (S52: YES), it displays a message indicating that the transmission of the function restriction setting request has been successful. After this, steps S55 to S65 are performed in the same manner as steps S18 to S28 described in the function restriction setting process via the first route.
[0072] When the ECU 6 sets the priority information, it transmits a priority setting notification indicating that the priority information has been set to the HCU 10, and also causes the DCM 5 to transmit the same to the external device 15. When the HCU 10 receives the priority setting notification from the ECU 6, it causes the CID 12 and the meter device 13 to display that the priority information has been set (S66). When the external device 15 receives the priority setting notification from the DCM 5, it displays that the priority information has been set (S67), and the function restriction setting process via the second route ends.
[0073] When the ECU 6 determines that priority information is held (S55: YES), it performs steps S68 to S70 in the same manner as steps S32 to S34 described in the function restriction setting process according to the first route.
[0074] (1-3) Function Restriction Setting Process via the Third Route (See FIGS. 13 and 14) The vehicle system 2 independently performs the function restriction setting process via the third route. When the operation input unit 16 accepts a function restriction setting via a setting operation from the vehicle owner (S71), it transmits a function restriction setting request indicating the accepted function restriction setting to the HCU 10. When the HCU 10 receives the function restriction setting request from the operation input unit 16, it transmits the received function restriction setting request to the ECU 6. From this point on, steps S72 to S82 are performed in the same manner as steps S18 to S28 described in the function restriction setting process via the first route above. In this case, if the ECU 6 determines that the function restriction setting has failed (S74: NO), it transmits a setting failure notice indicating that the function restriction setting has failed to the HCU 10. When the HCU 10 receives the setting failure notice from the ECU, it displays a message indicating that the function restriction setting has failed on the CID 12 and the meter device 13 (S75). When the ECU 6 determines that the function restriction has been successfully set (S74: YES), it transmits a setting success notification indicating that the function restriction has been successfully set to the HCU 10. When the HCU 10 receives the setting success notification from the ECU, it displays on the CID 12 and the meter device 13 that the function restriction has been successfully set (S76).
[0075] When the ECU 6 sets the priority information, it transmits a priority setting notification indicating that the priority information has been set to the HCU 10. When the HCU 10 receives the priority setting notification from the ECU 6, it causes the CID 12 and the meter device 13 to display that the priority information has been set (S83), and ends the function restriction setting process via the third route.
[0076] When the ECU 6 determines that priority information is held (S72: YES), it performs steps S84 to S86 in the same manner as steps S32 to S34 described in the function restriction setting process according to the first route.
[0077] (1-4) Function Restriction Release Process (See FIG. 15) The ECU 6 identifies the route of the function restriction release request (S91) and compares the priority of the identified route of the function restriction release request with the priority of the route of the function restriction setting request (S92, S93, corresponding to the release possibility determination procedure). If the ECU 6 determines that the priority of the route of the function restriction release request is higher than the priority of the route of the function restriction setting request (S92: YES), or if the ECU 6 determines that the priority of the route of the function restriction release request matches the priority of the route of the function restriction setting request (S93: YES), the ECU 6 releases the function restriction (S94, corresponding to the function restriction release procedure). The ECU 6 deletes the priority information (S95) and saves history information indicating that the function restriction has been released (S96).
[0078] The ECU 6 determines whether the DCM 5 can be wirelessly connected to the server 3 (S97). If the ECU 6 determines that the DCM 5 can be wirelessly connected to the server 3 (S97: YES), the ECU 6 wirelessly connects the DCM 5 to the server 3, causes the DCM 5 to transmit history information to the server 3 (S98), and ends the function restriction release process.
[0079] On the other hand, if the ECU 6 determines that the priority of the route of the function restriction release request is lower than the priority of the route of the function restriction setting request (S92: NO, S93: NO), the ECU 6 does not release the function restriction, does not delete the priority information, and ends the function restriction release process. By comparing the priority of the route of the function restriction release request with the priority of the route of the function restriction setting request in this way, even if, for example, the owner of a stolen vehicle operates the external device 15 to set function restrictions using the first or second route, and then the thief of the stolen vehicle operates the operation input unit 16 to release function restrictions using the third route, the function restriction setting will continue without being released.
[0080] Next, the transition of the display will be described with reference to Fig. 16 to Fig. 37. Here, the transition of the display accompanying the setting of function restrictions by each route and the transition of the display accompanying the release of function restrictions will be described.
[0081] (1) Transition of display accompanying setting of function restriction by first route (see FIGS. 16 to 19) The external device 15 waits for the operation input of an ID and password while displaying the login screen, and performs authentication upon receiving the operation input of an ID and password. If the authentication fails, the external device 15 displays a message saying "ID or password is incorrect." If the external device 15 cannot wirelessly connect to the server 3, it displays a message saying "Cannot connect wirelessly to the server. Please check your communication environment."
[0082] If the authentication is successful, the external device 15 displays a main menu screen, and when the function restriction management application is launched, the external device 15 displays a message "Do you want to set function restrictions?" and waits for an operation input. When the external device 15 receives an operation input to set function restrictions by pressing the "YES" button, it displays a message "Setting function restrictions."
[0083] If the external device 15 fails to set function restrictions due to an inability to connect wirelessly with the server 3, it displays a message saying "Failed to connect wirelessly with the server. Failed to set function restrictions." If the external device 15 fails to set function restrictions due to an inability to connect wirelessly between the server 3 and the DCM 5, it displays a message saying "Failed to connect wirelessly with the DCM. Failed to set function restrictions." If the external device 15 fails to set function restrictions due to an access error to the HCU 10 in the vehicle system 2, it displays a message saying "An error has occurred in the vehicle system. Failed to set function restrictions." If the external device 15 fails to set function restrictions because function restrictions have already been set, it displays a message saying "Function restrictions have already been set."
[0084] If the external device 15 successfully sets the function restriction, it displays a message saying, "Function restriction has been set. If you want to cancel the function restriction, please perform the cancel operation." The HCU 10 also displays a message on the CID 12 saying, "A registered terminal has instructed you to set a function restriction. The function restriction has been set." For example, if a function restriction on the navigation function is set, the HCU 10 changes the navigation screen from a normal display to a grayed-out display, or if an icon indicating the function for which the function restriction has been set is displayed, it erases the icon. If a speed restriction is set, the HCU 10 displays a message saying, "The speed has been limited to XX km / h." Note that, for example, if a map screen is displayed while driving, graying out the map screen may affect driving, so the HCU 10 sets function restrictions for destination setting, route guidance, viewing registered addresses, etc. However, the map screen may continue to be displayed without setting a function restriction on the map screen display.
[0085] (2) Transition of display accompanying release of function restriction via first route (see Figs. 20 to 23) The external device 15 waits for the operation input of an ID and password while displaying the login screen, and performs authentication upon receiving the operation input of an ID and password. If the authentication fails, the external device 15 displays the message "ID or password is incorrect," and if wireless connection to the server 3 is not possible, the external device 15 displays the message "Cannot connect wirelessly to the server. Please check your communication environment."
[0086] If the authentication is successful, the external device 15 displays a main menu screen, and when the function restriction management application is launched, the external device 15 displays a message "Do you want to release the function restriction?" and waits for an operation input. When the external device 15 receives an operation input indicating that the function restriction is to be released by pressing the "YES" button, it displays a message "Removing the function restriction."
[0087] If the external device 15 fails to release the function restriction due to an inability to connect wirelessly with the server 3, it displays a message saying "Failed to connect wirelessly with the server. Failed to release the function restriction." If the external device 15 fails to release the function restriction due to an inability to connect wirelessly between the server 3 and the DCM 5, it displays a message saying "Failed to connect wirelessly with the DCM. Failed to release the function restriction." If the external device 15 fails to release the function restriction due to an access error to the HCU 10 in the vehicle system 2, it displays a message saying "An error has occurred in the vehicle system. Failed to release the function restriction." If the external device 15 fails to release the function restriction because the function restriction has already been released, it displays a message saying "The function restriction has been released."
[0088] When the external device 15 has successfully released the function restriction, it displays the message "The function restriction has been released. If you want to set the function restriction, please perform the setting operation." In addition, the HCU 10 displays the message "A registered terminal has instructed to release the function restriction. The function restriction has been released" on the CID 12, and for example, when the function restriction on the navigation function has been released, it returns the navigation screen from a grayed-out display to a normal display, when an icon indicating the function for which the function restriction has been released has been erased, it displays the icon, and when the driving speed restriction has been released, it displays the message "The driving speed restriction has been released."
[0089] (3) Display transitions accompanying the setting of functional restrictions via the second route (see Figures 24 to 27) In this case, the parts related to the server 3 are omitted from the explanation of "(1) Display transitions accompanying the setting of functional restrictions via the first route" above, and the rest is the same.
[0090] (4) Display transitions following the removal of functional restrictions via the second route (see Figures 28 to 31) In this case, the parts related to server 3 are omitted from the explanation of "(2) Display transitions following the removal of functional restrictions via the first route" above, but the rest is the same.
[0091] (5) Transition of display accompanying setting of function restriction via third route (see FIGS. 32 to 34) The HCU 10 displays the message "Do you want to set function restriction?" on the CID 12 and waits for operation input from the operation input unit 16. When the "YES" button is pressed and operation input to set function restriction is received from the operation input unit 16, the HCU 10 displays the message "Setting function restriction" on the CID 12.
[0092] If the HCU 10 fails to set the function restriction due to an access error to the HCU 10 in the vehicle system 2, it displays a message saying "An error has occurred in the vehicle system. Setting of function restriction has failed" on the CID 12. If the HCU 10 fails to set the function restriction because the function restriction has already been set, it displays a message saying "Function restriction has already been set" on the CID 12.
[0093] When the HCU 10 has successfully set the function restriction, it displays the message "Function restriction has been set. If you want to cancel the function restriction, please perform the cancel operation" on the CID 12. In this case, as in the above-mentioned "(1) Display transition accompanying setting of function restriction by the first route," for example, when a function restriction on the navigation function is set, the HCU 10 changes the navigation screen from a normal display to a grayed-out display, when an icon indicating the function for which the function restriction has been set is displayed, it erases the icon, and when a travel speed limit is set, it displays the message "Travel speed has been limited to XX km / h."
[0094] (6) Transition of display accompanying setting of function restriction by third route (see FIGS. 35 to 37) The HCU 10 displays the message "Do you want to release the function restriction?" on the CID 12 and waits for operation input from the operation input unit 16. When the "YES" button is pressed and the operation input unit 16 accepts operation input indicating that the function restriction is to be released, the HCU 10 displays the message "Removing function restriction" on the CID 12.
[0095] If the HCU 10 fails to release the function restriction due to an access error to the HCU 10 in the vehicle system 2, it displays a message saying "An error has occurred in the vehicle system. Release of function restriction has failed" on the CID 12. If the HCU 10 fails to release the function restriction because the function restriction has already been released, it displays a message saying "The function restriction has been released" on the CID 12.
[0096] When the HCU 10 has successfully released the function restriction, it displays the message "Function restriction has been released. If you want to set a function restriction, please perform the setting operation" on the CID 12. In this case, the HCU 10 may, for example, return the navigation screen from a grayed-out display to a normal display when the function restriction on the navigation function has been released, display the icon indicating the function for which the function restriction has been released if the icon has been erased, or display the message "Speed restriction has been released" when the driving speed restriction has been released.
[0097] The ECU 6 may store the date and time when a function restriction is set or released as history information in association with the route, and may display the history information on the external terminal 15, the CID 12, etc. Alternatively, the ECU 6 may synchronize the display outside the vehicle with the display inside the vehicle, i.e., the display on the external terminal 15 with the display on the CID 12, etc. For example, when a function restriction is set or released via the first or second route by operating the external terminal 15, the ECU 6 may notify the CID 12, etc., of the setting or release. Alternatively, when a function restriction is set or released via the third route by operating the operation input unit 16, the ECU 6 may notify the CID 12, etc. of the setting or release. It may also be possible to select whether or not to synchronize the display on the external terminal 15 with the display on the CID 12, etc. The setting or release of a function restriction may be notified in any manner. Instead of or in addition to the display on the external terminal 15 and the CID 12, an indicator on the meter device 13 may be displayed. Alternatively, instead of or in addition to a visual notification, an audio notification may be displayed.
[0098] According to the first embodiment described above, the following advantageous effects can be obtained. The ECU 6 determines whether or not a function restriction can be released based on a priority, and releases the function restriction only if it is determined that the function restriction can be released. By setting a priority for determining whether or not a function restriction can be released, it is possible to prevent a situation in which a thief who has stolen a vehicle can release a function restriction set by the owner of the stolen vehicle. This makes it possible to appropriately obtain the effect of the function restriction against vehicle theft.
[0099] A priority is set based on the operation type corresponding to the operation for setting or releasing the function restriction, and whether or not the function restriction can be released is determined based on the priority according to the operation type. By associating the operation type with the priority, it is possible to determine whether or not the function restriction can be released by determining the operation type.
[0100] Priorities are set according to a first route for an operation via communication from the external device 15 over the communication network 4, a second route for an operation via short-range wireless communication from the external device 15, and a third route for an operation from the operation input unit 16. Whether the function restriction is to be released can be determined by determining whether the route is the first, second, or third route.
[0101] For example, by setting a function restriction by the setting operation of the setting restriction via the second route and then setting a function restriction by the setting operation of the setting restriction via the first route, the accuracy of authentication can be increased, and a situation in which a thief who has stolen a vehicle can cancel the setting can be more appropriately prevented.
[0102] Whether or not to release the function restriction is determined by comparing the priority of the function restriction setting request for each route with the priority of the function restriction release request for each route. By assigning the priority of the function restriction setting request for each route and the priority of the function restriction setting request, it is possible to determine whether or not to release the function restriction.
[0103] When the priority of the function restriction release request is higher than the priority of the function restriction setting request, or when the priority of the function restriction release request and the priority of the function restriction setting request match, it is determined that the function restriction can be released, and when the priority of the function restriction release request is lower than the priority of the function restriction setting request, it is determined that the function restriction cannot be released. For example, if the owner of a stolen vehicle sets a function restriction using the first or second route, even if the thief who stole the vehicle attempts to release the function restriction using the third route, the function restriction will not be released, thereby allowing the effect of the function restriction to be appropriately obtained.
[0104] Second Embodiment A second embodiment will be described with reference to Fig. 38. The second embodiment differs from the first embodiment in that additional authentication is performed even when the priority of the route of the function restriction release request is lower than the priority of the route of the function restriction setting request.
[0105] (2-1) Function Restriction Release Process (See FIG. 38) When the ECU 6 determines that the priority of the route of the function restriction release request is lower than the priority of the route of the function restriction setting request (S92: NO, S93: NO), it determines whether or not additional authentication, for example, by password input, is required (S101). When the ECU 6 determines that additional authentication is not required (S101: NO), it terminates the function restriction release process. When the ECU 6 determines that additional authentication is required (S101: YES), it determines whether or not the additional authentication was successful (S102). When the ECU 6 determines that the additional authentication failed (S102: NO), it terminates the function restriction release process. When the ECU 6 determines that the additional authentication was successful (S102: YES), it performs step S94 and subsequent steps.
[0106] That is, even if the priority of the route of the function restriction release request is lower than the priority of the route of the function restriction setting request, if the ECU 6 determines that the additional authentication is successful, the ECU 6 releases the function restriction in the same way as when it determines that the priority of the route of the function restriction release request is higher than the priority of the route of the function restriction setting request or that the priority of the route of the function restriction release request and the priority of the route of the function restriction setting request match. Note that the additional authentication may be, for example, a one-time password or the like.
[0107] According to the second embodiment described above, the following advantageous effects can be obtained. In the ECU 6, even if the priority of the route of the function restriction release request is lower than the priority of the route of the function restriction setting request, the function restriction is released on the condition that the additional authentication is successful. For example, even if a request to release the function restriction is made from a route with a low priority due to a mistake on the part of the vehicle owner, the function restriction can be released if the additional authentication is successful.
[0108] Third Embodiment A third embodiment will be described with reference to Fig. 39 and Fig. 40. The third embodiment differs from the first embodiment in that additional authentication is performed when the route priority of the function restriction setting request is "3".
[0109] (3-1) Function Restriction Release Processing (See FIGS. 39 to 40) When the ECU 6 determines that the priority of the route of the function restriction release request is higher than the priority of the route of the function restriction setting request (YES at S92), or when the ECU 6 determines that the priority of the route of the function restriction release request matches the priority of the route of the function restriction setting request (YES at S93), the ECU 6 determines whether the priority of the route of the function restriction setting request is "3" (S201). When the ECU 6 determines that the priority of the route of the function restriction setting request is not "3" (NO at S201), the ECU 6 performs step S94 and subsequent steps.
[0110] When the ECU 6 determines that the priority of the route of the function restriction setting request is "3" (YES in S201), it determines whether or not additional authentication, such as password entry, is required (S202). When the ECU 6 determines that additional authentication is not required (NO in S202), it releases the function restriction in a limited manner (S204) and terminates the function restriction release process. Release of the function restriction in a limited manner means re-setting the function restriction after a certain time has elapsed since the function restriction was released, re-setting the function after the number of times the corresponding function has been used reaches a predetermined number of times since the function restriction was released, or releasing part of the function restriction, for example, releasing the function restriction not related to driving while not releasing the function restriction related to driving.
[0111] When the ECU 6 determines that additional authentication is necessary (S202: YES), it determines whether the additional authentication was successful (S203). When the ECU 6 determines that the additional authentication was unsuccessful (S203: NO), it also releases the function restriction in a limited manner (S204) and ends the function restriction release process. When the ECU 6 determines that the additional authentication was successful (S203: YES), it performs step S94 and subsequent steps.
[0112] That is, when the priority of the route of the function restriction release request is higher than the priority of the route of the function restriction setting request, or when the priority of the route of the function restriction release request matches the priority of the route of the function restriction setting request and the priority of the route of the function restriction setting request is "3," the ECU 6 determines that additional authentication is not necessary, or that additional authentication is necessary but failed, and releases the function restriction in a limited manner, and when it determines that the additional authentication was successful, releases the function restriction without any limited conditions. Note that in this case as well, the additional authentication may be a one-time password or the like.
[0113] According to the third embodiment described above, the following advantageous effects can be obtained. When a function restriction is released in the ECU 6 by an operation from the operation input unit 16, the function restriction is released on the condition that additional authentication is successful. By adding additional authentication, it is possible to prevent a situation in which a function restriction set by a setting operation via the third route is unconditionally released by a release operation via the third route, and it is possible to more appropriately prevent a situation in which a thief who has stolen a vehicle can release the function restriction. Furthermore, when the vehicle owner properly performs additional authentication, the function restriction can be appropriately released.
[0114] In the ECU 6, when the function restriction is released by operation from the operation input unit 16, if additional authentication is not required or if the additional authentication fails, the function restriction is released in a limited manner. By releasing the function restriction in a limited manner, even if a thief who has stolen the vehicle is able to release the function restriction, the damage caused by releasing the function restriction can be reduced by setting a limited condition.
[0115] The present disclosure includes the following in addition to what is set forth in the claims: [1] An electronic control device (6) including: a function restriction setting unit (17a) that sets function restrictions against vehicle theft, a release possibility determination unit (17e) that determines whether the function restrictions set by the function restriction setting unit can be released based on a priority, and a function restriction release unit (17g) that releases the function restrictions set by the function restriction setting unit on the condition that the release possibility determination unit has determined that the function restrictions can be released.
[0116] [2] An electronic control device according to [1], comprising: a priority setting unit (17b) that sets a priority based on an operation type corresponding to a function restriction setting operation or a function restriction release operation; and a priority holding unit (17c) that holds the priority set by the priority setting unit, wherein the release possibility determination unit determines whether or not the function restriction set by the function restriction setting unit can be released based on the priority held by the priority holding unit.
[0117] [3] The electronic control device according to [2], wherein the priority setting unit sets the priority based on one of the following operation types: an operation via communication from an external device via a communication network, an operation via short-range wireless communication or wired communication from an external device, and an operation from an operation input unit.
[0118] [4] The electronic control device according to claim [2] or [3], further comprising a priority update unit (17d) that updates the priorities held by the priority holding unit.
[0119] [5] The electronic control device according to any one of [2] to [4], wherein the release possibility determination unit determines whether the function restriction set by the function restriction setting unit can be released by comparing the priority of the function restriction setting request for each operation type with the priority of the function restriction release request for each operation type.
[0120] [6] The electronic control device described in [5], wherein the release possibility determination unit determines whether the function restriction can be released when it determines that the priority of the function restriction release request is higher than the priority of the function restriction setting request, or that the priority of the function restriction release request matches the priority of the function restriction setting request.
[0121] [7] The electronic control device according to [5] or [6], wherein the release possibility determination unit determines whether to release the function restriction when it determines that the priority of the function restriction release request is lower than the priority of the function restriction setting request.
[0122] [8] An electronic control device according to any one of [5] to [7], wherein the release possibility determination unit determines whether the function restriction can be released, provided that the authentication result is positive, even if it determines that the priority of the function restriction release request is lower than the priority of the function restriction setting request.
[0123] [9] An electronic control device according to any one of [3] to [8], wherein the function restriction release unit releases the function restriction on the condition that the authentication result is positive when the function restriction is released by operation from the operation input unit.
[0124]
[10] The electronic control device according to any one of [3] to [9], wherein the function restriction release unit releases the function restriction in a limited manner when the function restriction is released by an operation from the operation input unit.
[0125]
[11] An electronic control device according to any one of [1] to
[10] , further comprising a judgment result notification unit (17f) that notifies the judgment result of the release possibility determination unit, wherein the judgment result notification unit notifies the reason for whether or not the function restriction is to be released when the release possibility determination unit determines whether or not the function restriction is to be released.
[0126] (Other Embodiments) While the present disclosure has been described with reference to examples, it is understood that the present disclosure is not limited to these examples or structures. The present disclosure also encompasses various modifications and modifications within the scope of equivalents. In addition, various combinations and forms, as well as other combinations and forms including only one element, more than one element, or less than one element, are also within the scope and spirit of the present disclosure.
[0127] The control unit and the method described herein may be implemented by a special-purpose computer configured by configuring a processor and memory programmed to perform one or more functions embodied in a computer program. Alternatively, the control unit and the method described herein may be implemented by a special-purpose computer configured by configuring a processor with one or more dedicated hardware logic circuits. Alternatively, the control unit and the method described herein may be implemented by one or more special-purpose computers configured by combining a processor and memory programmed to perform one or more functions with a processor configured with one or more hardware logic circuits. Furthermore, the computer program may be stored as instructions executed by a computer on a computer-readable non-transitory tangible storage medium.
Claims
1. An electronic control device (6) comprising: a function restriction setting unit (17a) that sets function restrictions against vehicle theft; a release possibility determination unit (17e) that determines whether the function restrictions set by the function restriction setting unit can be released based on a priority; and a function restriction release unit (17g) that releases the function restrictions set by the function restriction setting unit on condition that the release possibility determination unit has specified that the function restrictions can be released.
2. An electronic control device as described in claim 1, comprising: a priority setting unit (17b) that sets a priority based on an operation type corresponding to a function restriction setting operation or release operation; and a priority holding unit (17c) that holds the priority set by the priority setting unit, wherein the release feasibility determination unit determines whether or not the function restriction set by the function restriction setting unit can be released based on the priority held by the priority holding unit.
3. An electronic control device as described in claim 2, wherein the priority setting unit sets the priority based on any one of the following operation types: operation via communication over a communication network from an external device, operation via short-range wireless communication or wired communication from an external device, and operation from an operation input unit.
4. The electronic control device according to claim 2, further comprising a priority update section (17d) for updating the priorities held by the priority holding section.
5. An electronic control device as described in claim 2, wherein the release possibility determination unit determines whether or not the function restrictions set by the function restriction setting unit can be released by comparing the priority of the function restriction setting request for each operation type with the priority of the function restriction release request for each operation type.
6. An electronic control device as described in claim 5, wherein the release possibility determination unit determines whether the function restriction can be released when it determines that the priority of the function restriction release request is higher than the priority of the function restriction setting request, or that the priority of the function restriction release request matches the priority of the function restriction setting request.
7. The electronic control device according to claim 5, wherein the release possibility determination unit determines whether or not to release the function restriction when it determines that the priority of the function restriction release request is lower than the priority of the function restriction setting request.
8. An electronic control device as described in claim 5, wherein the release possibility determination unit determines whether the function restriction can be released, provided that the authentication result is positive, even if it determines that the priority of the function restriction release request is lower than the priority of the function restriction setting request.
9. The electronic control device according to claim 3, wherein the function restriction release section releases the function restriction on condition that the authentication result is positive when the function restriction is released by an operation from the operation input section.
10. The electronic control device according to claim 3, wherein the function restriction release section releases the function restriction in a limited manner when the function restriction is released by an operation from the operation input section.
11. An electronic control device as described in claim 1, further comprising a judgment result notification unit (17f) that notifies the judgment result of the release possibility judgment unit, wherein the judgment result notification unit notifies the reason for whether or not the functional restriction can be released when the release possibility judgment unit specifies whether or not the functional restriction can be released.
12. A function restriction management system (1) comprising an electronic control unit (6) mounted on a vehicle, an external device (15), and an operation input unit (16), wherein the electronic control unit comprises: a function restriction setting unit (17a) that sets function restrictions against vehicle theft; a priority setting unit (17b) that sets a priority based on an operation type corresponding to an operation for setting or releasing a function restriction; a release possibility determination unit (17e) that determines whether or not the function restriction set by the function restriction setting unit can be released based on the priority set by the priority setting unit; and a function restriction release unit (17g) that releases the function restriction set by the function restriction setting unit on condition that the release possibility determination unit has specified that the function restriction can be released; and wherein the priority setting unit sets a priority based on any one of operation types among operation via communication from the external device via a communication network, operation via short-range wireless communication or wired communication from the external device, and operation from the operation input unit.
13. A function restriction management method in an electronic control device (6) mounted on a vehicle, comprising: a function restriction setting procedure for setting function restrictions against vehicle theft; a release possibility determination procedure for determining whether the function restrictions set by the function restriction setting procedure can be released based on priority; and a function restriction release procedure for releasing the function restrictions set by the function restriction setting procedure, on condition that it has been determined by the release possibility determination procedure that the function restrictions can be released.
14. A function restriction management program that performs, in a control unit (17) of an electronic control device (6) mounted in a vehicle, a function restriction setting procedure for setting function restrictions against vehicle theft, a release possibility determination procedure for determining whether the function restrictions set by the function restriction setting procedure can be released based on priority, and a function restriction release procedure for releasing the function restrictions set by the function restriction setting procedure, on the condition that the release possibility determination procedure has determined that the function restrictions can be released.
Citation Information
Patent Citations
Electronic key system for vehicle
JP2012087528A
Authentication method and authentication device
JP2017223068A
Supporting apparatus, supporting method, program and supporting system
JP2019121369A
Lock control system and method for working machine, working machine, lock control device and lock control management device for working machine
WO2006075562A1
