Vehicle, server, and vehicle control system

Abstract

To inhibit a thief from taking away a vehicle to a distant place.SOLUTION: A vehicle 100 includes: an on-vehicle navigation device 10 for repeatedly obtaining a location of the vehicle 100 through a GPS 200; and an on-vehicle immobilizer device 20. The on-vehicle immobilizer device 20 turns on a remote immobilizer on the basis of the fact that the location of the vehicle 100, obtained from the on-vehicle navigation device 10, is outside a preset geographical region. The on-vehicle immobilizer device 20 prohibits operation of a drive system of the vehicle 100 while the remote immobilizer is in an on-state. Notification that the remote immobilizer has been turned on is provided to a terminal 300 of a legitimate user of the vehicle 100 via a server 400 or directly.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to a vehicle, a server, and a vehicle control system. [Background technology]

[0002] Immobilizers are known as devices for preventing vehicle theft. One example of an immobilizer is a system that communicates between an immobilizer key held by a user and a computer installed in the vehicle. The vehicle's engine can be started only if the identification information registered on the immobilizer key matches the identification information registered on the vehicle. In other words, even if the physical key of a vehicle equipped with an immobilizer is duplicated, the engine cannot be started unless the electronic identification information is verified. This prevents vehicle theft using a key that is only physically duplicated.

[0003] Using a remote immobilizer system in addition to the immobilizer key can further enhance security. Patent Document 1 discloses an example of a remote immobilizer system. The remote immobilizer system includes a vehicle, a server, and a user terminal. The user can request the server to turn on the remote immobilizer through the user terminal. For example, the user can request the server to turn on the remote immobilizer during times when the user does not plan to use the vehicle. The server turns on the remote immobilizer through communication with the vehicle in accordance with the request received from the user terminal. While the remote immobilizer is on, the engine cannot be started even with the immobilizer key. This can prevent theft by, for example, a relay attack, in which radio waves emitted by the immobilizer key are relayed to illicitly verify the vehicle's electronic identification information. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2003-146185 Summary of the Invention [Problem to be solved by the invention]

[0005] While the remote immobilizer is off, the security function is reduced. If a thief drives the vehicle far away while the remote immobilizer is off, it will be difficult to recover the vehicle from the thief. [Means for solving the problem]

[0006] The means for solving the above problems and their effects will be described below. According to one aspect of the present disclosure, there is provided a vehicle comprising: an on-board navigation device configured to acquire the position of the vehicle; and an on-board immobilizer device, wherein the on-board immobilizer device is configured to turn on a remote immobilizer function that remotely prohibits the execution of the vehicle's drive system based on the position of the vehicle acquired from the on-board navigation device being outside a predetermined geographical area, and the on-board immobilizer device is configured to prohibit the execution of the vehicle's drive system while the remote immobilizer function is on.

[0007] According to one aspect of the present disclosure, there is provided a server including a processing circuit configured to acquire a vehicle's location from the vehicle and, based on the acquired location of the vehicle being outside a predetermined geographical area, turn on a remote immobilizer function by remotely operating an on-board immobilizer device mounted on the vehicle, wherein the on-board immobilizer device is configured to prohibit execution of the vehicle's drive system while the remote immobilizer function is on.

[0008] According to one aspect of the present disclosure, there is provided a vehicle control system comprising a vehicle and a server, wherein the vehicle is configured to acquire the location of the vehicle and, based on the acquired location of the vehicle being outside a predetermined geographical area, request the server to send to the vehicle an instruction to turn on a remote immobilizer function that remotely prohibits the execution of the vehicle's drive system, and when the server receives the request, the server is configured to turn on the remote immobilizer function by remotely operating an on-board immobilizer device mounted on the vehicle by sending an instruction to the vehicle to turn on the remote immobilizer function, and the on-board immobilizer device is configured to prohibit the execution of the vehicle's drive system while the remote immobilizer function is on. [Effects of the Invention]

[0009] This configuration can prevent thieves from taking the vehicle far away from the geographical area. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a diagram showing a vehicle according to the first embodiment. [Figure 2] FIG. 2 is a flowchart showing a process executed by the vehicle of FIG. [Figure 3] FIG. 3 is a diagram showing a user interface for setting the days of the week and time periods referred to in the processing shown in FIG. [Figure 4] FIG. 4 is a flowchart showing a process executed by the vehicle of FIG. [Figure 5] FIG. 5 is a flowchart showing the process of transmitting the operation status of the remote immobilizer to the user's terminal. [Figure 6] FIG. 6 is a flowchart showing the process of turning off the remote immobilizer in response to a user request. [Figure 7]FIG. 7 is a diagram illustrating a server according to the second embodiment. [Figure 8] FIG. 8 is a flowchart showing the process executed by the server of FIG. [Figure 9] FIG. 9 is a diagram showing a vehicle control system according to the third embodiment. [Figure 10] FIG. 10 is a flowchart showing the processing executed by the vehicle control system of FIG. DETAILED DESCRIPTION OF THE INVENTION

[0011] A vehicle according to a first embodiment, a server according to a second embodiment, and a vehicle control system according to a third embodiment will be described below with reference to the drawings. (First embodiment) <Summary> An overview of the first embodiment will be described with reference to FIG. 1. The vehicle control system includes a vehicle 100 and a server 400. The vehicle 100 includes a control unit 50. The control unit 50 includes an in-vehicle navigation device 10, an in-vehicle immobilizer device 20, a display 30, and an in-vehicle communication device 40. The in-vehicle navigation device 10 is configured to repeatedly acquire the position of the vehicle 100 through a global positioning system (GPS) 200. The in-vehicle immobilizer device 20 acquires the position of the vehicle 100 from the in-vehicle navigation device 10. The in-vehicle immobilizer device 20 turns on a remote immobilizer based on the position of the vehicle 100 being outside a predetermined geographical area. The in-vehicle immobilizer device 20 prohibits the execution of the drive system of the vehicle 100 while the remote immobilizer is on.

[0012] The preset geographical area is set through machine learning based on the past driving history of the vehicle 100. For example, a range of a certain size centered on a location where the user frequently parks the vehicle 100 is set as the geographical area. For example, a range of a certain size centered on a location where the user regularly parks the vehicle 100 is set as the geographical area. For example, a range including a route connecting two locations where the user frequently or regularly parks the vehicle 100 that are several kilometers apart is set as the geographical area. The range including the route is, for example, a range obtained by overlapping multiple ranges of a certain size centered on multiple points on the route. The user may manually set the geographical area by selecting it themselves. For example, the user sets the geographical area by specifying a range on a map of the in-vehicle navigation device 10. Multiple geographical areas may be set as the preset geographical area. In such a case, the in-vehicle immobilizer device 20 turns on the remote immobilizer when the vehicle 100 moves from one of the multiple preset geographical areas to outside the geographical area.

[0013] When the remote immobilizer is on, the drive system of the vehicle 100 cannot be started even with a genuine immobilizer key 70. In other words, even if the identification information registered in the immobilizer key 70 matches the identification information registered in the vehicle 100, the drive system of the vehicle 100 cannot be started. The remote immobilizer can be turned off by inputting the identification information into the display 30 of the vehicle 100, as will be described later with reference to FIG. 4. The remote immobilizer can be turned off by requesting that the remote immobilizer be turned off from the user's terminal 300, as will be described with reference to FIG. 6.

[0014] The in-vehicle communication device 40 is configured to communicate with devices external to the vehicle 100. In the example shown in FIG. 1, when the in-vehicle immobilizer device 20 turns on the remote immobilizer, the in-vehicle communication device 40 notifies the server 400 that the remote immobilizer has been turned on. Then, the server 400 notifies the user's terminal 300 that the remote immobilizer has been turned on. Note that, instead of the example shown in FIG. 1, the in-vehicle communication device 40 may communicate directly with the user's terminal 300 without going through the server 400. In either case, when the in-vehicle immobilizer device 20 turns on the remote immobilizer, the in-vehicle communication device 40 is configured to notify the terminal 300 of the authorized user of the vehicle 100 that the remote immobilizer has been turned on.

[0015] <Turning on the remote immobilizer> The operation of turning on the remote immobilizer will be described with reference to Figures 2 and 3. The process shown in Figure 2 is automatically started after the drive system of the vehicle 100 is started. Furthermore, the process shown in Figure 2 is also automatically started when the remote immobilizer is switched from on to off while the drive system of the vehicle 100 is operating.

[0016] As described above, the in-vehicle immobilizer device 20 acquires the position of the vehicle 100 from the in-vehicle navigation device 10. However, if a thief removes the in-vehicle navigation device 10 from the vehicle 100, the in-vehicle immobilizer device 20 will not be able to acquire the position of the vehicle 100. In step S200, the in-vehicle immobilizer device 20 determines whether or not the position of the vehicle 100 can be acquired. If the position of the vehicle 100 can be acquired (S200: YES), the in-vehicle immobilizer device 20 proceeds to step S202. If the position of the vehicle 100 cannot be acquired (S200: NO), the in-vehicle immobilizer device 20 proceeds to step S206. In step S206, the in-vehicle immobilizer device 20 turns on the remote immobilizer.

[0017] In step S202, the in-vehicle immobilizer device 20 determines whether the location of the vehicle 100 is outside a preset geographical area. If the determination in step S202 is negative (S202: NO), the in-vehicle immobilizer device 20 returns to step S200. If the determination in step S202 is positive (S202: YES), the in-vehicle immobilizer device 20 proceeds to step S204.

[0018] In step S204, the in-vehicle immobilizer device 20 determines whether the current time falls within a time period of a preset day of the week. If the determination in step S204 is negative (S204: NO), the in-vehicle immobilizer device 20 returns to step S200. If the determination in step S204 is positive (S204: YES), the in-vehicle immobilizer device 20 proceeds to step S206.

[0019] Referring now to FIG. 3, the time periods of the preset days of the week referenced in step S204 will be described. FIG. 3 shows an example of an image displayed on the screen of the terminal 300 by an application installed on the user's terminal 300. FIG. 3 shows an example in which the remote immobilizer is turned on because the processing of step S204 was performed after 8:00 p.m. on Monday. In the example of FIG. 3, the display "RUNNING" indicates that the remote immobilizer is turned on. In the example of FIG. 3, the time periods for turning on the remote immobilizer based on the location of the vehicle 100 being outside the preset geographical area are displayed for each day of the week. In the example shown in FIG. 3, the display "OFF" indicates that no time periods for turning on the remote immobilizer based on the location of the vehicle 100 being outside the preset geographical area have been set. In other words, the display "OFF" indicates that the day is a day on which the function for turning on the remote immobilizer based on the location being outside the preset geographical area is not activated. The user can set a time period for each day of the week regarding whether or not to turn on the remote immobilizer when the location of the vehicle 100 is outside a predetermined geographical area. Therefore, the in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a predetermined time period on a predetermined day of the week is outside the predetermined geographical area. The in-vehicle immobilizer device 20 is configured not to turn on the remote immobilizer during a time period that does not correspond to a predetermined time period on a predetermined day of the week, even if the location of the vehicle 100 is outside the predetermined geographical area. The user can also set only a time period without specifying a day of the week. Therefore, the in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a predetermined time period is outside the predetermined geographical area.The in-vehicle immobilizer device 20 is configured not to turn on the remote immobilizer during a time period that does not fall within a preset time period, even if the vehicle 100 is located outside a preset geographical area. The user can also set only a day of the week without specifying a time period. Therefore, the in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired on a preset day of the week is outside the preset geographical area. The in-vehicle immobilizer device 20 is configured not to turn on the remote immobilizer during a day of the week that does not fall within a preset day of the week, even if the vehicle 100 is located outside the preset geographical area.

[0020] 2, the in-vehicle immobilizer device 20 turns on the remote immobilizer in step S206. Then, the in-vehicle immobilizer device 20 proceeds to step S208. In step S208, the in-vehicle immobilizer device 20 notifies the user's terminal 300, via the in-vehicle communication device 40 and the server 400, that the remote immobilizer has been turned on.

[0021] <Action when drive system startup is attempted> With reference to Figure 4, the operation when an attempt is made to start the drive system of the vehicle 100 will be described. The process shown in Figure 4 is initiated when an attempt is made to start the drive system of the vehicle 100. For example, the process shown in Figure 4 is initiated when an attempt is made to start the drive system of the vehicle 100 using the immobilizer key 70. Furthermore, the process shown in Figure 4 is also initiated when a thief attempts to start the drive system using a radio signal received from the immobilizer key 70. In step S400, the in-vehicle immobilizer device 20 determines whether the remote immobilizer is on. If the remote immobilizer is off (S400: NO), the in-vehicle immobilizer device 20 ends the process of Figure 4.

[0022] If the remote immobilizer is on (S400: YES), the in-vehicle immobilizer device 20 proceeds to step S402. In step S402, the in-vehicle immobilizer device 20 displays a message on the display 30 of the vehicle 100 prompting the user to enter authentication information. The authentication may be performed by the user manually entering identification information into the display 30. Alternatively, the authentication may be performed by the user using the terminal 300 to transmit identification information stored in the terminal 300 to the in-vehicle immobilizer device 20. In other words, the authentication may be performed using a digital key. Alternatively, the authentication may be performed by ear acoustic authentication, which is performed by the in-vehicle immobilizer device 20 through an earphone-type device worn on the user's ear. Here, ear acoustic authentication is biometric authentication using sound reverberation determined by the shape of the ear canal. In other words, the authentication may be performed using a hearable device. The in-vehicle immobilizer device 20 then proceeds to step S404. In step S404, the in-vehicle immobilizer device 20 determines whether or not preset identification information corresponding to the display has been input. The identification information input here may be, for example, a password preset by the user. The identification information input here may also be, for example, a personal identification number preset by the user. The identification information input here may also be biometric information such as the user's fingerprint, voice, or retina. If no identification information has been input (S404: NO), the in-vehicle immobilizer device 20 repeats the process of step S404. If identification information has been input (S404: YES), the in-vehicle immobilizer device 20 proceeds to step S406.

[0023] In step S406, the vehicle-mounted immobilizer device 20 turns off the remote immobilizer. According to steps S400 and S402, if an attempt is made to start the drive system of the vehicle 100 while the remote immobilizer is on, the in-vehicle immobilizer device 20 displays a message on the display 30 of the vehicle 100 prompting the user to enter authentication information. According to steps S404 and S406, if the user enters preset identification information corresponding to the message, the in-vehicle immobilizer device 20 turns off the remote immobilizer.

[0024] <Operations related to querying the remote immobilizer operation status> With reference to FIG. 5, the operation relating to the inquiry about the operation status of the remote immobilizer will be described. In step S500, the user's terminal 300 inquires about the operation status of the remote immobilizer to the vehicle 100 or the server 400. Specifically, the terminal 300 transmits a signal inquiring about the operation status of the remote immobilizer to the vehicle 100 or the server 400. The operation for transmitting this signal is performed via an application installed on the terminal 300. The in-vehicle communication device 40 or the server 400 receives the signal transmitted from the terminal 300. When the server 400 receives the signal, the server 400 notifies the vehicle 100 that the signal inquiring about the operation status of the remote immobilizer has been transmitted from the terminal 300. Next, in step S502, the operation status of the remote immobilizer is transmitted to the user's terminal 300. Specifically, the in-vehicle communication device 40 transmits information indicating the operation status of the remote immobilizer to the terminal 300 that transmitted the signal. In this way, the terminal 300 is notified of the operating status of the remote immobilizer.

[0025] In this way, the in-vehicle communication device 40 is configured to transmit the operating status of the remote immobilizer to the terminal 300 of the authorized user of the vehicle 100 in response to a request from the terminal 300 .

[0026] <Remote immobilizer off operation upon user request> Referring to FIG. 6, the operation of turning off the remote immobilizer in response to a user request will be described. In step S600, the user's terminal 300 requests the vehicle 100 or the server 400 to turn off the remote immobilizer. In this case, the vehicle 100 or the server 400 that receives the request appropriately authenticates the user. The authentication may be performed using, for example, the user's biometric information such as a fingerprint, voice, or retina, or may be performed using a password. If the authentication is unsuccessful, the request is not accepted. Specifically, a request to turn off the remote immobilizer is transmitted from the terminal 300 to the vehicle 100 or the server 400. The operation for transmitting this request is performed via an application installed on the terminal 300. If the user authentication is successful, the in-vehicle communication device 40 or the server 400 receives the request transmitted from the terminal 300. When the server 400 receives the request, the server 400 notifies the vehicle 100 that the request to turn off the remote immobilizer has been transmitted from the terminal 300. Next, in step S602, the remote immobilizer is turned off. Specifically, the in-vehicle communication device 40 notifies the in-vehicle immobilizer device 20 that it has received a request to turn off the remote immobilizer. Then, the in-vehicle immobilizer device 20 turns off the remote immobilizer. In other words, it deactivates the remote immobilizer that is currently on.

[0027] In this way, the in-vehicle communication device 40 is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from the terminal 300 of the authorized user of the vehicle 100 while the remote immobilizer is on.

[0028] <Operation of the First Embodiment> If the location of the vehicle 100 is outside the preset geographical area and during the preset time period on the day of the week (S202: YES and S204: YES), the remote immobilizer is turned on (S206). As described above, if the remote immobilizer is on, the drive system of the vehicle 100 cannot be started even with the genuine immobilizer key 70. If the location of the vehicle 100 cannot be obtained from the in-vehicle navigation device 10 (S200: NO), the remote immobilizer is turned on. In other words, the remote immobilizer is turned on regardless of whether the location of the vehicle 100 is outside the preset geographical area or not.

[0029] <Effects of the first embodiment> (1-1) The vehicle 100 includes an in-vehicle navigation device 10 configured to repeatedly acquire the position of the vehicle 100 through a global positioning system 200, and an in-vehicle immobilizer device 20. The in-vehicle immobilizer device 20 is configured to turn on a remote immobilizer based on the position of the vehicle 100 acquired from the in-vehicle navigation device 10 being outside a predetermined geographical area. The in-vehicle immobilizer device 20 is configured to prohibit the execution of the drive system of the vehicle 100 while the remote immobilizer is on.

[0030] For example, a user may preset a geographical area in which the user normally drives the vehicle 100. According to the above configuration, the remote immobilizer is turned on based on the vehicle 100 being located outside the preset geographical area. This prohibits the drive system from being activated. Therefore, even if a thief succeeds in activating the drive system once and takes the vehicle 100 outside the geographical area, once the drive system is stopped, the drive system cannot be activated. This prevents the thief from taking the vehicle 100 far from the geographical area.

[0031] (1-1-a) According to the above configuration, it is possible to turn on the remote immobilizer without communicating with devices outside the vehicle 100. This allows the remote immobilizer to be turned on even when communication between the vehicle 100 and devices outside the vehicle 100 is not possible.

[0032] (1-2) The vehicle 100 further includes an in-vehicle communication device 40 configured to communicate with devices outside the vehicle 100. When the in-vehicle immobilizer device 20 turns on the remote immobilizer, the in-vehicle communication device 40 is configured to notify the terminal 300 of the authorized user of the vehicle 100 that the remote immobilizer has been turned on.

[0033] According to the above configuration, the terminal 300 of the authorized user is notified that the remote immobilizer has been turned on. This makes it less likely that the user will be unaware that the remote immobilizer has been turned on. Furthermore, the user can quickly become aware that the vehicle 100 has been taken outside the geographical area.

[0034] (1-3) The in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a preset time period is outside a preset geographical area. The in-vehicle immobilizer device 20 is configured not to turn on the remote immobilizer during a time period that does not fall within the preset time period, even if the location of the vehicle 100 is outside the preset geographical area.

[0035] According to the above configuration, the user can set a time period as a condition for turning on the remote immobilizer. (1-4) The in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired on a preset day of the week is outside a preset geographical area. The in-vehicle immobilizer device 20 is configured not to turn on the remote immobilizer on days other than the preset day of the week, even if the location of the vehicle 100 is outside the preset geographical area.

[0036] According to the above configuration, the user can set the day of the week as a condition for turning on the remote immobilizer. (1-5) The in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a preset time period on a preset day of the week is outside a preset geographical area. The in-vehicle immobilizer device 20 is configured not to turn on the remote immobilizer during a time period that does not fall within the preset time period on a preset day of the week, even if the location of the vehicle 100 is outside the preset geographical area.

[0037] According to the above configuration, the user can set the day of the week and the time period as the conditions for turning on the remote immobilizer. (1-6) The pre-defined geographical area is set through machine learning based on the past driving history of the vehicle 100.

[0038] According to the above configuration, the user of the vehicle 100 can reduce the effort required to set a geographical region. (1-7) The in-vehicle immobilizer device 20 is configured to be able to set a plurality of geographical areas as the preset geographical area. The in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer when the vehicle 100 moves from one of the preset geographical areas to the outside of the geographical area.

[0039] According to the above configuration, it is possible to set a plurality of geographical regions in advance. (1-8) The in-vehicle immobilizer device 20 is configured to turn on the remote immobilizer when the position of the vehicle 100 cannot be acquired from the in-vehicle navigation device 10.

[0040] According to the above configuration, the remote immobilizer is turned on even if a thief removes the in-vehicle navigation device 10 from the vehicle 100. In other words, the remote immobilizer is turned on even if the thief performs an act that makes it impossible to obtain the location of the vehicle 100. This improves crime prevention performance.

[0041] (1-9) When an attempt is made to start the drive system of the vehicle 100 while the remote immobilizer is on, the in-vehicle immobilizer device 20 is configured to display a message on the display 30 of the vehicle 100 prompting the user to enter authentication information. The in-vehicle immobilizer device 20 is configured to turn off the remote immobilizer when preset identification information corresponding to the message is entered.

[0042] According to the above configuration, even if the remote immobilizer is in an on state, an authorized user who knows the identification information can turn off the remote immobilizer by inputting the identification information.

[0043] (1-10) The vehicle 100 is equipped with an in-vehicle communication device 40 configured to communicate with devices outside the vehicle 100. The in-vehicle communication device 40 is configured to transmit the operation status of the remote immobilizer to the terminal 300 in response to a request from the terminal 300 of the authorized user of the vehicle 100.

[0044] According to the above configuration, the user can inquire of the in-vehicle communication device 40 and check the operation status of the remote immobilizer. (1-11) The vehicle 100 is equipped with an in-vehicle communication device 40 configured to communicate with devices outside the vehicle 100. The in-vehicle communication device 40 is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from the terminal 300 of an authorized user of the vehicle 100 while the remote immobilizer is on.

[0045] According to the above configuration, the user of the vehicle 100 can turn off the remote immobilizer through the user's terminal 300. (Second embodiment) The second embodiment will be described below with reference to the drawings, and a description of the configuration common to the first and second embodiments will be omitted.

[0046] The first and second embodiments differ mainly in the following points: In the second embodiment, the server 400 acquires the position of the vehicle 100 from the vehicle 100, whereas in the first embodiment, the server 400 does not acquire the position of the vehicle 100. In the second embodiment, the server 400 determines whether the position of the vehicle 100 is outside a predetermined geographical area, whereas in the first embodiment, the vehicle 100 determines whether the position of the vehicle 100 is outside a predetermined geographical area.

[0047] <Summary> An overview of the second embodiment will be described with reference to FIG. 7. The vehicle 100 is equipped with an in-vehicle navigation device 10 configured to repeatedly acquire the position of the vehicle 100 through a global positioning system 200. A server 400 repeatedly acquires the position of the vehicle 100 from the vehicle 100. If the acquired position of the vehicle 100 is outside a predetermined geographical area, the server 400 remotely controls an in-vehicle immobilizer device 20 mounted on the vehicle 100 to turn on a remote immobilizer. The in-vehicle immobilizer device 20 is configured to prohibit execution of the drive system of the vehicle 100 while the remote immobilizer is on. When the server 400 turns on the remote immobilizer, it is configured to notify the terminal 300 of the authorized user of the vehicle 100 that the remote immobilizer has been turned on.

[0048] <Turning on the remote immobilizer> The operation of turning on the remote immobilizer will be described with reference to Fig. 8. The process shown in Fig. 8 is automatically started after the drive system of vehicle 100 is started. Furthermore, the process shown in Fig. 8 is also automatically started when the remote immobilizer is switched from on to off while the drive system of vehicle 100 is operating.

[0049] As described above, the server 400 acquires the position of the vehicle 100 from the vehicle 100. However, if a thief removes the in-vehicle navigation device 10 from the vehicle 100, the server 400 will not be able to acquire the position of the vehicle 100. In step S800, the server 400 determines whether or not the position of the vehicle 100 can be acquired. If the position of the vehicle 100 can be acquired (S800: YES), the server 400 proceeds to step S802. If the position of the vehicle 100 cannot be acquired (S800: NO), the server 400 proceeds to step S806.

[0050] In step S802, the server 400 determines whether the location of the vehicle 100 is outside a preset geographical area. If the determination in step S802 is negative (S802: NO), the server 400 returns to step S800. If the determination in step S802 is positive (S802: YES), the server 400 proceeds to step S804.

[0051] In step S804, the server 400 determines whether the current time falls within a time period of a preset day of the week. If the determination in step S804 is negative (S804: NO), the server 400 returns to step S800. If the determination in step S804 is positive (S804: YES), the server 400 proceeds to step S806.

[0052] In step S806, the server 400 transmits an instruction to turn on the remote immobilizer to the vehicle 100. Then, the server 400 proceeds to step S808. In step S808, the server 400 notifies the user terminal 300 that the remote immobilizer has been turned on.

[0053] <Action when drive system startup is attempted> The operation when an attempt is made to start the drive system in the first embodiment has been described above with reference to FIG. 4. The second embodiment differs from the first embodiment in that the processing in step S406 in FIG. 4 is changed to the processing described below. The vehicle 100 transmits a request to turn off the remote immobilizer to the server 400 via the in-vehicle communication device 40. The server 400 receives the request to turn off the remote immobilizer from the vehicle 100. Next, in response to the request, the server 400 remotely controls the in-vehicle immobilizer device 20 installed in the vehicle 100 to turn off the remote immobilizer.

[0054] <Operations related to querying the remote immobilizer operation status> In the second embodiment, a mode in which the server 400 transmits the operating status to the terminal 300 will be described with reference to FIG.

[0055] As shown in FIG. 5, in step S500, the user's terminal 300 inquires of the server 400 about the operation status of the remote immobilizer. Specifically, a signal inquiring about the operation status of the remote immobilizer is transmitted from the terminal 300 to the server 400. The operation for transmitting this signal is performed via an application installed on the terminal 300. The server 400 receives the signal transmitted from the terminal 300. Next, in step S502, the operation status of the remote immobilizer is transmitted to the user's terminal 300. Specifically, the server 400 transmits information indicating the operation status of the remote immobilizer to the terminal 300 that transmitted the signal. In this way, the operation status of the remote immobilizer is notified to the terminal 300.

[0056] <Remote immobilizer off operation upon user request> In the second embodiment, an operation in which the server 400 turns off the remote immobilizer in response to a user request will be described with reference to FIG.

[0057] As shown in FIG. 6 , in step S600, the user's terminal 300 requests the server 400 to turn off the remote immobilizer. In this case, the server 400 that receives the request appropriately authenticates the user. If the authentication is not successful, the request is not accepted. Specifically, the terminal 300 transmits a request to turn off the remote immobilizer to the server 400. The operation for transmitting this request is performed via an application installed on the terminal 300. If the user authentication is successful, the server 400 receives the request transmitted from the terminal 300. Next, in step S602, the remote immobilizer is turned off. Specifically, the server 400 transmits an instruction to turn off the remote immobilizer to the vehicle 100. As a result, the in-vehicle communication device 40 receives the instruction to turn off the remote immobilizer. The in-vehicle communication device 40 transmits the instruction received from the server 400 to the in-vehicle immobilizer device 20. Then, the in-vehicle immobilizer device 20 turns off the remote immobilizer, that is, it deactivates the remote immobilizer that is currently on.

[0058] <Operation of the Second Embodiment> If the location of the vehicle 100 is outside the preset geographical area and during the preset time period on the day of the week (S802: YES and S804: YES), the remote immobilizer is turned on (S806). As described above, if the remote immobilizer is on, the drive system of the vehicle 100 cannot be started even with the genuine immobilizer key 70. The server 400 is configured to turn on the remote immobilizer if the location of the vehicle 100 cannot be obtained (S800: NO). In other words, the remote immobilizer is turned on regardless of whether the location of the vehicle 100 is outside the preset geographical area or not.

[0059] <Effects of the second embodiment> (2-1) The server 400 repeatedly acquires the location of the vehicle 100 from the vehicle 100. Based on the acquired location of the vehicle 100 being outside a predetermined geographical area, the server 400 turns on the remote immobilizer by remotely operating the in-vehicle immobilizer device 20 mounted on the vehicle 100. The in-vehicle immobilizer device 20 is configured to prohibit the execution of the drive system of the vehicle 100 while the remote immobilizer is on.

[0060] According to the above configuration, the same effect as (1-1) can be obtained. (2-2) When the remote immobilizer is turned on, the server 400 is configured to notify the terminal 300 of the authorized user of the vehicle 100 that the remote immobilizer has been turned on.

[0061] According to the above configuration, the same effect as (1-2) can be obtained. (2-3) The server 400 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a preset time period is outside a preset geographical area. The server 400 is configured not to turn on the remote immobilizer during a time period that does not fall within the preset time period, even if the location of the vehicle 100 is outside the preset geographical area.

[0062] According to the above configuration, the same effect as (1-3) can be obtained. (2-4) The server 400 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired on a preset day of the week is outside a preset geographical area. The server 400 is configured not to turn on the remote immobilizer on days that do not correspond to the preset day of the week, even if the location of the vehicle 100 is outside the preset geographical area.

[0063] According to the above configuration, the same effect as (1-4) can be obtained. (2-5) The server 400 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a preset time period on a preset day of the week is outside a preset geographical area. The server 400 is configured not to turn on the remote immobilizer during a time period that does not fall within the preset time period on a preset day of the week, even if the location of the vehicle 100 is outside the preset geographical area.

[0064] According to the above configuration, the same effect as (1-5) can be obtained. (2-6) The predetermined geographical area is set through machine learning based on the past driving history of the vehicle 100.

[0065] According to the above configuration, the same effect as (1-6) can be obtained. (2-7) The in-vehicle immobilizer device 20 is configured to be able to set a plurality of geographical areas as the preset geographical area. The server 400 is configured to turn on the remote immobilizer when the vehicle 100 moves from one of the preset geographical areas to outside the geographical area.

[0066] According to the above configuration, the same effect as (1-7) can be obtained. (2-8) The server 400 is configured to turn on the remote immobilizer if the location of the vehicle 100 cannot be obtained.

[0067] According to the above configuration, the same effect as (1-8) can be obtained. (2-9) When an attempt is made to start the drive system of the vehicle 100 while the remote immobilizer is on, the in-vehicle immobilizer device 20 is configured to display a message on the display 30 of the vehicle 100 prompting the user to enter authentication information. The in-vehicle immobilizer device 20 is configured to transmit a request to the server 400 to turn off the remote immobilizer when preset identification information corresponding to the message is entered. The server 400 is configured to turn off the remote immobilizer in response to the request by remotely operating the in-vehicle immobilizer device 20 mounted on the vehicle 100.

[0068] According to the above configuration, the same effect as (1-9) can be obtained. (2-10) The server 400 is configured to transmit the operation status of the remote immobilizer to the terminal 300 of the authorized user of the vehicle 100 in response to a request from the terminal 300.

[0069] According to the above configuration, the server 400 knows whether the remote immobilizer is on or not, and the user can inquire of the server 400 to check the operation status of the remote immobilizer.

[0070] (2-11) The server 400 is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from the terminal 300 of the authorized user of the vehicle 100 while the remote immobilizer is on.

[0071] According to the above configuration, the same effect as (1-11) can be obtained. (Third embodiment) The third embodiment will be described below with reference to the drawings, and a description of the configuration common to the first and third embodiments will be omitted.

[0072] The first and third embodiments have in common the point that the vehicle 100 determines whether the location of the vehicle 100 is outside a predetermined geographical area. In the first embodiment, the vehicle 100 turns on the remote immobilizer by itself. In contrast, in the third embodiment, as will be described later, the vehicle 100 requests an instruction to turn on the remote immobilizer from the server 400. Then, the server 400 transmits an instruction to turn on the remote immobilizer to the vehicle 100.

[0073] <Summary> An overview of the third embodiment will be described with reference to FIG. 9 . The vehicle control system includes a vehicle 100 and a server 400. The vehicle 100 repeatedly acquires its location. If the acquired location of the vehicle 100 is outside a predetermined geographical area, the vehicle 100 requests the server 400 to send an instruction to turn on the remote immobilizer to the vehicle 100. When the server 400 receives the request, the server 400 transmits an instruction to turn on the remote immobilizer to the vehicle 100, thereby remotely controlling the on-board immobilizer device 20 mounted on the vehicle 100 to turn on the remote immobilizer. The on-board immobilizer device 20 prohibits the operation of the drive system of the vehicle 100 while the remote immobilizer is on. When the server 400 turns on the remote immobilizer, the server 400 is configured to notify the terminal 300 of the authorized user of the vehicle 100 that the remote immobilizer has been turned on.

[0074] <Turning on the remote immobilizer> The operation of turning on the remote immobilizer will be described with reference to Fig. 10. The process shown in Fig. 10 is automatically started after the drive system of the vehicle 100 is started. Furthermore, the process shown in Fig. 10 is also automatically started when the remote immobilizer is switched from on to off while the drive system of the vehicle 100 is operating.

[0075] As described above, the in-vehicle immobilizer device 20 acquires the position of the vehicle 100. However, if a thief removes the in-vehicle navigation device 10 from the vehicle 100, the in-vehicle immobilizer device 20 will not be able to acquire the position of the vehicle 100. In step S1000, the in-vehicle immobilizer device 20 determines whether or not it is possible to acquire the position of the vehicle 100. If the in-vehicle immobilizer device 20 is able to acquire the position of the vehicle 100 (S1000: YES), the in-vehicle immobilizer device 20 proceeds to step S1002. If the in-vehicle immobilizer device 20 is unable to acquire the position of the vehicle 100 (S1000: NO), the in-vehicle immobilizer device 20 proceeds to step S1006.

[0076] In step S1002, the in-vehicle immobilizer device 20 determines whether the location of the vehicle 100 is outside a preset geographical area. If the determination in step S1002 is negative (S1002: NO), the in-vehicle immobilizer device 20 returns to step S1000. If the determination in step S1002 is positive (S1002: YES), the in-vehicle immobilizer device 20 proceeds to step S1004.

[0077] In step S1004, the in-vehicle immobilizer device 20 determines whether the current time falls within a time period of a preset day of the week. If the in-vehicle immobilizer device 20 makes a negative determination in step S1004 (S1004: NO), the process returns to step S1000. If the in-vehicle immobilizer device 20 makes a positive determination in step S1004 (S1004: YES), the process proceeds to step S1006.

[0078] In step S1006, the in-vehicle immobilizer device 20 requests the server 400 to issue an instruction to turn on the remote immobilizer. In step S1008, the server 400 transmits an instruction to turn on the remote immobilizer to the vehicle 100. Next, the server 400 proceeds to step S1010. In step S1010, the server 400 notifies the user's terminal 300 that the remote immobilizer has been turned on.

[0079] <Action when drive system startup is attempted> The operation when an attempt is made to start the drive system in the first embodiment has been described above with reference to FIG. 4. The third embodiment differs from the first embodiment in that the processing in step S406 in FIG. 4 is changed to the processing described below. The vehicle 100 transmits a request to turn off the remote immobilizer to the server 400 via the in-vehicle communication device 40. The server 400 receives the request to turn off the remote immobilizer from the vehicle 100. Next, in response to the request, the server 400 remotely controls the in-vehicle immobilizer device 20 installed in the vehicle 100 to turn off the remote immobilizer.

[0080] <Operations related to querying the remote immobilizer operation status> The operation relating to the inquiry about the operating state of the remote immobilizer according to the third embodiment is the same as the operation according to the first embodiment.

[0081] <Remote immobilizer off operation upon user request> A first example of the operation of turning off the remote immobilizer in accordance with the third embodiment in response to a user request will now be described. In the first example, the server 400 receives a request to turn off the remote immobilizer from the terminal 300, and then remotely turns off the remote immobilizer.

[0082] The first example will be described in detail below with reference to FIG. 6. In step S600, the user's terminal 300 requests the server 400 to turn off the remote immobilizer. In this case, the server 400 that receives the request appropriately authenticates the user. If the authentication is not successful, the request is not accepted. Specifically, the terminal 300 transmits a request to turn off the remote immobilizer to the server 400. The operation for transmitting this request is performed via an application installed on the terminal 300. If the user authentication is successful, the server 400 receives the request transmitted from the terminal 300. Next, in step S602, the remote immobilizer is turned off. Specifically, the process is as follows: The server 400 transmits an instruction to the vehicle 100 to turn off the remote immobilizer. The in-vehicle communication device 40 notifies the in-vehicle immobilizer device 20 that the instruction to turn off the remote immobilizer has been received. Then, the in-vehicle immobilizer device 20 turns off the remote immobilizer, that is, it deactivates the remote immobilizer that is currently on.

[0083] A second example of the operation of turning off the remote immobilizer in accordance with the third embodiment in response to a user request will now be described. In the second example, the vehicle 100 receives a request to turn off the remote immobilizer from the terminal 300, and then turns off the remote immobilizer.

[0084] The second example will be described in detail below with reference to FIG. 6. In step S600, the user's terminal 300 requests the vehicle 100 to turn off the remote immobilizer. In this case, the vehicle 100 that receives the request appropriately authenticates the user. If the authentication is not successful, the request is not accepted. Specifically, the terminal 300 transmits a request to turn off the remote immobilizer to the vehicle 100. The operation for transmitting this request is performed via an application installed on the terminal 300. If the user authentication is successful, the in-vehicle communication device 40 receives the request transmitted from the terminal 300. Next, in step S602, the remote immobilizer is turned off. Specifically, the in-vehicle communication device 40 requests the server 400 to transmit an instruction to turn off the remote immobilizer. Next, the server 400 transmits an instruction to turn off the remote immobilizer to the vehicle 100. As a result, the in-vehicle communication device 40 receives the instruction to turn off the remote immobilizer. The in-vehicle communication device 40 transmits an instruction to turn off the remote immobilizer to the in-vehicle immobilizer device 20. Then, the in-vehicle immobilizer device 20 turns off the remote immobilizer, i.e., cancels the remote immobilizer that is currently on.

[0085] <Operation of the Third Embodiment> If the location of the vehicle 100 is outside the preset geographical area and during the preset time period on the day of the week (S1002: YES and S1004: YES), the remote immobilizer is turned on (S1006, S1008). As described above, if the remote immobilizer is on, the drive system of the vehicle 100 cannot be started even with the genuine immobilizer key 70. If the location of the vehicle 100 cannot be obtained (S1000: NO), the vehicle 100 requests the server 400 to send an instruction to turn on the remote immobilizer to the vehicle 100. Therefore, the remote immobilizer is turned on regardless of whether the location of the vehicle 100 is outside the preset geographical area or not.

[0086] <Effects of the third embodiment> (3-1) The vehicle control system includes a vehicle 100 and a server 400. The vehicle 100 repeatedly acquires the position of the vehicle 100. Based on the fact that the acquired position of the vehicle 100 is outside a predetermined geographical area, the vehicle 100 requests the server 400 to send an instruction to turn on a remote immobilizer to the vehicle 100. When the server 400 receives the request, it sends an instruction to turn on the remote immobilizer to the vehicle 100. In response, the server 400 turns on the remote immobilizer by remotely operating an in-vehicle immobilizer device 20 mounted on the vehicle 100. The in-vehicle immobilizer device 20 is configured to prohibit the execution of the drive system of the vehicle 100 while the remote immobilizer is on.

[0087] According to the above configuration, the same effect as (1-1) can be obtained. (3-2) When the remote immobilizer is turned on, the server 400 is configured to notify the terminal 300 of the authorized user of the vehicle 100 that the remote immobilizer has been turned on.

[0088] According to the above configuration, the same effect as (1-2) can be obtained. (3-3) The server 400 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a preset time period is outside a preset geographical area. The server 400 is configured not to turn on the remote immobilizer during a time period that does not fall within the preset time period, even if the location of the vehicle 100 is outside the preset geographical area.

[0089] According to the above configuration, the same effect as (1-3) can be obtained. (3-4) The server 400 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired on a preset day of the week is outside a preset geographical area. The server 400 is configured not to turn on the remote immobilizer on days that do not correspond to the preset day of the week, even if the location of the vehicle 100 is outside the preset geographical area.

[0090] According to the above configuration, the same effect as (1-4) can be obtained. (3-5) The server 400 is configured to turn on the remote immobilizer based on the fact that the location of the vehicle 100 acquired during a predetermined time period on a predetermined day of the week is outside a predetermined geographical area. The server 400 is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period on a predetermined day of the week, even if the location of the vehicle 100 is outside the predetermined geographical area.

[0091] According to the above configuration, the same effect as (1-5) can be obtained. (3-6) The pre-defined geographical area is set through machine learning based on the past driving history of the vehicle 100.

[0092] According to the above configuration, the same effect as (1-6) can be obtained. (3-7) The in-vehicle immobilizer device 20 is configured to be able to set a plurality of geographical areas as the preset geographical area. The server 400 is configured to turn on the remote immobilizer when the vehicle 100 moves from one of the preset geographical areas to outside the geographical area.

[0093] According to the above configuration, the same effect as (1-7) can be obtained. (3-8) The vehicle 100 is configured to request the server 400 to send an instruction to the vehicle 100 to turn on the remote immobilizer if the vehicle 100 cannot acquire the location of the vehicle 100.

[0094] According to the above configuration, the same effect as (1-8) can be obtained. (3-9) When an attempt is made to start the drive system of the vehicle 100 while the remote immobilizer is on, the in-vehicle immobilizer device 20 is configured to display a message on the display 30 of the vehicle 100 prompting the user to enter authentication information. When preset identification information corresponding to the message is entered, the in-vehicle immobilizer device 20 is configured to transmit a request to the server 400 to turn off the remote immobilizer. In response to the request, the server 400 is configured to turn off the remote immobilizer by remotely operating the in-vehicle immobilizer device 20 mounted on the vehicle 100.

[0095] According to the above configuration, the same effect as (1-9) can be obtained. (3-10) The server 400 is configured to transmit the operation status of the remote immobilizer to the terminal 300 of the authorized user of the vehicle 100 in response to a request from the terminal 300.

[0096] According to the above configuration, the server 400 knows whether the remote immobilizer is on or not, and the user can inquire of the server 400 to check the operation status of the remote immobilizer.

[0097] (3-11) The server 400 is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from the terminal 300 of the authorized user of the vehicle 100 while the remote immobilizer is on.

[0098] According to the above configuration, the same effect as (1-11) can be obtained. <Example of change> The following are common modifiable elements of the first to third embodiments: The following modifications can be implemented in combination with one another within the scope of technical compatibility.

[0099] In the first to third embodiments, a normal immobilizer and a remote immobilizer are combined. However, this is merely an example. The normal immobilizer may be omitted. In other words, implementation using only the remote immobilizer is also possible.

[0100] One or more of steps S200, S204, and S208 in FIG. 2 may be omitted. The configuration shown in FIG. 3 can be modified as appropriate. For example, only a time period may be set. For example, only a day of the week may be set. For example, a date may be set. For example, a period spanning multiple days may be set.

[0101] The process in Figure 5 can be omitted. At least one of the processes in Figure 4 and Figure 6 may be omitted. When the processes in Figure 4 and Figure 6 are omitted, for example, it is possible to configure the remote immobilizer to be turned off by the user calling a call center.

[0102] One or more of steps S800, S804, and S808 in FIG. 8 may be omitted. One or more of steps S1000, S1004, and S1010 in FIG. 10 may be omitted.

[0103] In the first to third embodiments, the in-vehicle immobilizer device 20 displays a message prompting the user to enter authentication information on the display 30 of the vehicle 100 in step S402. However, this is merely an example. In step S402, the in-vehicle immobilizer device 20 may display a message prompting the user to enter authentication information on a display unit other than the display 30 of the vehicle 100. The display unit may be the screen of the terminal 300.

[0104] In the first to third embodiments, the server 400 includes a CPU, RAM, and ROM. The server 400 executes software processing. However, this is merely an example. For example, the server 400 may include a dedicated hardware circuit (e.g., ASIC) that processes at least part of the software processing executed in the above embodiments. That is, the server 400 may have any of the following configurations (a) to (c): (a) The server 400 includes a processing device that executes all processing in accordance with a program, and a program storage device such as a ROM that stores the program. That is, the server 400 includes a software execution device. (b) The server 400 includes a processing device that executes part of the processing in accordance with a program, and a program storage device. Furthermore, the server 400 includes a dedicated hardware circuit that executes the remaining processing. (c) The server 400 includes a dedicated hardware circuit that executes all processing. Here, there may be multiple software execution devices and / or dedicated hardware circuits. That is, the above processing may be executed by processing circuitry that includes at least one of a software execution device and a dedicated hardware circuit. The processing circuit may include multiple software execution devices and dedicated hardware circuits. The program storage device, i.e., computer-readable medium, includes a storage device, which is any available medium accessible by a general-purpose or dedicated computer. The processes performed by each of the control unit 50 and the user terminal 300 may also be performed by a processing circuit. Here, the control unit 50 is composed of the in-vehicle navigation device 10, the in-vehicle immobilizer device 20, the display 30, and the in-vehicle communication device 40.

[0105] <Additional Notes> The technical ideas that can be understood from the above-described embodiment and modified examples will be described. [Appendix 1] A vehicle, an in-vehicle navigation device configured to obtain the location of the vehicle; an in-vehicle immobilizer device; the in-vehicle immobilizer device is configured to turn on a remote immobilizer function that remotely prohibits execution of a drive system of the vehicle, based on the fact that the location of the vehicle acquired from the in-vehicle navigation device is outside a predetermined geographical area; the in-vehicle immobilizer device is configured to prohibit execution of a drive system of the vehicle while the function of the remote immobilizer is on; vehicle.

[0106] [Appendix 2] the vehicle further comprises an on-board communication device configured to communicate with equipment external to the vehicle; the in-vehicle communication device is configured to, when the in-vehicle immobilizer device turns on the remote immobilizer, notify a terminal of an authorized user of the vehicle that the remote immobilizer has been turned on; Vehicles as described in Appendix 1.

[0107] [Appendix 3] the in-vehicle immobilizer device is configured to turn on the remote immobilizer based on the fact that the position of the vehicle acquired during a predetermined time period is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period even if the position of the vehicle is outside the predetermined geographical area. A vehicle as described in Appendix 1 or 2.

[0108] [Appendix 4] the in-vehicle immobilizer device is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired on a predetermined day of the week is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer on days other than the predetermined day of the week even if the location of the vehicle is outside the predetermined geographical area. A vehicle as described in Appendix 1 or 2.

[0109] [Appendix 5] The in-vehicle immobilizer device is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a predetermined time period on a predetermined day of the week is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period on the predetermined day of the week, even if the location of the vehicle is outside the predetermined geographical area. A vehicle as described in Appendix 1 or 2.

[0110] [Appendix 6] The predetermined geographical area is set through machine learning based on the past driving history of the vehicle. A vehicle as set forth in any one of appendices 1 to 5.

[0111] [Appendix 7] When a plurality of geographical areas are set as the predetermined geographical area, the in-vehicle immobilizer device is configured to turn on the remote immobilizer when the vehicle moves from one of the plurality of predetermined geographical areas to outside the geographical area. A vehicle as set forth in any one of appendices 1 to 6.

[0112] [Appendix 8] the in-vehicle immobilizer device is configured to turn on the remote immobilizer when the location of the vehicle cannot be obtained from the in-vehicle navigation device; A vehicle as set forth in any one of appendices 1 to 7.

[0113] [Appendix 9] When an attempt is made to start a drive system of the vehicle while the remote immobilizer is on, the in-vehicle immobilizer device is configured to display a message on a display unit prompting an input for authentication, the in-vehicle immobilizer device is configured to turn off the remote immobilizer when preset identification information corresponding to the display is input; A vehicle as set forth in any one of appendices 1 to 8.

[0114] [Appendix 10] the vehicle further comprises an on-board communication device configured to communicate with equipment external to the vehicle; the in-vehicle communication device is configured to transmit the operation status of the remote immobilizer to a terminal of a legitimate user of the vehicle in response to a request from the terminal. A vehicle as set forth in any one of appendices 1 to 9.

[0115] [Appendix 11] the vehicle further comprises an on-board communication device configured to communicate with equipment external to the vehicle; the in-vehicle communication device is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from a terminal of an authorized user of the vehicle while the remote immobilizer is on. A vehicle as set forth in any one of appendices 1 to 10.

[0116] [Appendix 12] 1. A server comprising: a processing circuit; obtaining a vehicle's location from said vehicle; and turning on a remote immobilizer function by remotely operating an in-vehicle immobilizer device mounted on the vehicle, based on the acquired location of the vehicle being outside a predetermined geographical area; the in-vehicle immobilizer device is configured to prohibit execution of a drive system of the vehicle while the function of the remote immobilizer is on; server.

[0117] [Appendix 13] the processing circuit is configured to, when the remote immobilizer is turned on, notify a terminal of an authorized user of the vehicle that the remote immobilizer has been turned on; 12. The server described in Appendix 12.

[0118] [Appendix 14] The processing circuit is configured to turn on the remote immobilizer based on the location of the vehicle acquired during a predetermined time period being outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period even if the location of the vehicle is outside the predetermined geographical area. 14. The server according to claim 12 or 13.

[0119] [Appendix 15] The processing circuit is configured to turn on the remote immobilizer based on the location of the vehicle acquired on a preset day of the week being outside the preset geographical area, and is configured not to turn on the remote immobilizer on days other than the preset day of the week even if the location of the vehicle is outside the preset geographical area. 14. The server according to claim 12 or 13.

[0120] [Appendix 16] The processing circuit is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a preset time period on a preset day of the week is outside the preset geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the preset time period on the preset day of the week, even if the location of the vehicle is outside the preset geographical area. 14. The server according to claim 12 or 13.

[0121] [Appendix 17] The predetermined geographical area is set through machine learning based on the past driving history of the vehicle. 17. The server according to any one of appendices 12 to 16.

[0122] [Appendix 18] and when a plurality of geographical areas are set as the preset geographical area, the processing circuit is configured to turn on the remote immobilizer when the vehicle moves from one of the plurality of preset geographical areas to outside the geographical area. 18. The server according to any one of appendices 12 to 17.

[0123] [Appendix 19] the processing circuitry is configured to turn on the remote immobilizer if the location of the vehicle cannot be obtained. 19. The server according to any one of appendices 12 to 18.

[0124] [Appendix 20] When an attempt is made to start a drive system of the vehicle while the remote immobilizer is on, the in-vehicle immobilizer device is configured to display a message on a display unit prompting an input for authentication, the in-vehicle immobilizer device is configured to transmit a request to the server to turn off the remote immobilizer when preset identification information corresponding to the display is input; the processing circuit is configured to turn off the remote immobilizer by remotely operating the vehicle immobilizer device mounted on the vehicle in response to the request. 20. The server according to any one of appendices 12 to 19.

[0125] [Appendix 21] the server is configured to transmit the operation status of the remote immobilizer to a terminal of a legitimate user of the vehicle in response to a request from the terminal. 21. The server according to claim 12.

[0126] [Appendix 22] the server is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from a terminal of an authorized user of the vehicle while the remote immobilizer is on; 22. The server according to claim 12, wherein the server is a

[0127] [Appendix 23] A vehicle control system, the vehicle control system includes a vehicle and a server; The vehicle acquires a location of the vehicle; and requesting the server to transmit to the vehicle an instruction to remotely turn on a function of a remote immobilizer that remotely inhibits execution of a drive system of the vehicle, based on the acquired location of the vehicle being outside a predetermined geographical area; the server is configured, when receiving the request, to transmit to the vehicle an instruction to turn on a function of the remote immobilizer, thereby remotely operating an in-vehicle immobilizer device mounted on the vehicle, thereby turning on the function of the remote immobilizer; the in-vehicle immobilizer device is configured to prohibit execution of a drive system of the vehicle while the function of the remote immobilizer is on; Vehicle control system.

[0128] [Appendix 24] the server is configured to, when the remote immobilizer is turned on, notify a terminal of an authorized user of the vehicle that the remote immobilizer has been turned on; 24. The vehicle control system of claim 23.

[0129] [Appendix 25] The server is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a predetermined time period is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period even if the location of the vehicle is outside the predetermined geographical area. 25. A vehicle control system according to claim 23 or 24.

[0130] [Appendix 26] the server is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired on a predetermined day of the week is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer on days other than the predetermined day of the week even if the location of the vehicle is outside the predetermined geographical area. 25. A vehicle control system according to claim 23 or 24.

[0131] [Appendix 27] the server is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a preset time period on a preset day of the week is outside the preset geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the preset time period on the preset day of the week even if the location of the vehicle is outside the preset geographical area. 25. A vehicle control system according to claim 23 or 24.

[0132] [Appendix 28] The predetermined geographical area is set through machine learning based on the past driving history of the vehicle. 28. A vehicle control system according to any one of appendices 23 to 27.

[0133] [Appendix 29] When a plurality of geographical areas are set as the predetermined geographical area, the server is configured to turn on the remote immobilizer when the vehicle moves from one of the plurality of predetermined geographical areas to outside the geographical area. A vehicle control system according to any one of appendices 23 to 28.

[0134] [Appendix 30] the vehicle is configured to request the server to send an instruction to the vehicle to turn on the remote immobilizer if the vehicle's location cannot be obtained; 30. A vehicle control system according to any one of appendices 23 to 29.

[0135] [Appendix 31] When an attempt is made to start a drive system of the vehicle while the remote immobilizer is on, the in-vehicle immobilizer device is configured to display a message on a display unit prompting an input for authentication, the in-vehicle immobilizer device is configured to transmit a request to the server to turn off the remote immobilizer when preset identification information corresponding to the display is input; the server is configured to turn off the remote immobilizer by remotely operating the vehicle immobilizer device mounted on the vehicle in response to the request. A vehicle control system according to any one of appendices 23 to 30.

[0136] [Appendix 32] the server is configured to transmit the operation status of the remote immobilizer to a terminal of a legitimate user of the vehicle in response to a request from the terminal. 32. A vehicle control system according to any one of appendices 23 to 31.

[0137] [Appendix 33] the server is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from a terminal of an authorized user of the vehicle while the remote immobilizer is on; 33. A vehicle control system according to any one of appendices 23 to 32. [Explanation of symbols]

[0138] 10...In-vehicle navigation device, 20...In-vehicle immobilizer device, 30...Display, 40...In-vehicle communication device, 100...Vehicle, 200...Global positioning system, 300...Terminal, 400...Server

Claims

1. A vehicle, an in-vehicle navigation device configured to obtain the location of the vehicle; an in-vehicle immobilizer device; the in-vehicle immobilizer device is configured to turn on a remote immobilizer function that remotely prohibits execution of a drive system of the vehicle, based on the fact that the location of the vehicle acquired from the in-vehicle navigation device is outside a predetermined geographical area; the in-vehicle immobilizer device is configured to prohibit execution of a drive system of the vehicle while the function of the remote immobilizer is on; vehicle.

2. the vehicle further comprises an on-board communication device configured to communicate with equipment external to the vehicle; the in-vehicle communication device is configured to, when the in-vehicle immobilizer device turns on the remote immobilizer, notify a terminal of an authorized user of the vehicle that the remote immobilizer has been turned on; The vehicle of claim 1 .

3. the in-vehicle immobilizer device is configured to turn on the remote immobilizer based on the fact that the position of the vehicle acquired during a predetermined time period is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period even if the position of the vehicle is outside the predetermined geographical area. The vehicle of claim 1 .

4. the in-vehicle immobilizer device is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired on a predetermined day of the week is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer on days other than the predetermined day of the week even if the location of the vehicle is outside the predetermined geographical area. The vehicle of claim 1 .

5. The in-vehicle immobilizer device is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a predetermined time period on a predetermined day of the week is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period on the predetermined day of the week, even if the location of the vehicle is outside the predetermined geographical area. The vehicle of claim 1 .

6. The predetermined geographical area is set through machine learning based on the past driving history of the vehicle. The vehicle of claim 1 .

7. When a plurality of geographical areas are set as the predetermined geographical area, the in-vehicle immobilizer device is configured to turn on the remote immobilizer when the vehicle moves from one of the plurality of predetermined geographical areas to outside the geographical area. The vehicle of claim 1 .

8. the in-vehicle immobilizer device is configured to turn on the remote immobilizer when the location of the vehicle cannot be obtained from the in-vehicle navigation device; The vehicle of claim 1 .

9. When an attempt is made to start a drive system of the vehicle while the remote immobilizer is on, the in-vehicle immobilizer device is configured to display a message on a display unit prompting an input for authentication, the in-vehicle immobilizer device is configured to turn off the remote immobilizer when preset identification information corresponding to the display is input; The vehicle of claim 1 .

10. the vehicle further comprises an on-board communication device configured to communicate with equipment external to the vehicle; the in-vehicle communication device is configured to transmit the operation status of the remote immobilizer to a terminal of a legitimate user of the vehicle in response to a request from the terminal. The vehicle of claim 1 .

11. the vehicle further comprises an on-board communication device configured to communicate with equipment external to the vehicle; the in-vehicle communication device is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from a terminal of an authorized user of the vehicle while the remote immobilizer is on. The vehicle of claim 1 .

12. 1. A server comprising: a processing circuit; obtaining a vehicle's location from said vehicle; and turning on a remote immobilizer function by remotely operating an in-vehicle immobilizer device mounted on the vehicle, based on the acquired location of the vehicle being outside a predetermined geographical area; the in-vehicle immobilizer device is configured to prohibit execution of a drive system of the vehicle while the function of the remote immobilizer is on; server.

13. the processing circuit is configured to, when the remote immobilizer is turned on, notify a terminal of an authorized user of the vehicle that the remote immobilizer has been turned on; The server of claim 12.

14. The processing circuit is configured to turn on the remote immobilizer based on the location of the vehicle acquired during a predetermined time period being outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period even if the location of the vehicle is outside the predetermined geographical area. The server of claim 12.

15. The processing circuit is configured to turn on the remote immobilizer based on the location of the vehicle acquired on a preset day of the week being outside the preset geographical area, and is configured not to turn on the remote immobilizer on days other than the preset day of the week even if the location of the vehicle is outside the preset geographical area. The server of claim 12.

16. The processing circuit is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a preset time period on a preset day of the week is outside the preset geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the preset time period on the preset day of the week, even if the location of the vehicle is outside the preset geographical area. The server of claim 12.

17. The predetermined geographical area is set through machine learning based on the past driving history of the vehicle. The server of claim 12.

18. and when a plurality of geographical areas are set as the preset geographical area, the processing circuit is configured to turn on the remote immobilizer when the vehicle moves from one of the plurality of preset geographical areas to outside the geographical area. The server of claim 12.

19. the processing circuitry is configured to turn on the remote immobilizer if the location of the vehicle cannot be obtained. The server of claim 12.

20. When an attempt is made to start a drive system of the vehicle while the remote immobilizer is on, the in-vehicle immobilizer device is configured to display a message on a display unit prompting an input for authentication, the in-vehicle immobilizer device is configured to transmit a request to the server to turn off the remote immobilizer when preset identification information corresponding to the display is input; the processing circuit is configured to turn off the remote immobilizer by remotely operating the vehicle immobilizer device mounted on the vehicle in response to the request. The server of claim 12.

21. the server is configured to transmit the operation status of the remote immobilizer to a terminal of a legitimate user of the vehicle in response to a request from the terminal. The server of claim 12.

22. the server is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from a terminal of an authorized user of the vehicle while the remote immobilizer is on; The server of claim 12.

23. A vehicle control system, the vehicle control system includes a vehicle and a server; The vehicle acquires a location of the vehicle; and requesting the server to transmit to the vehicle an instruction to remotely turn on a function of a remote immobilizer that remotely inhibits execution of a drive system of the vehicle, based on the acquired location of the vehicle being outside a predetermined geographical area; the server is configured, when receiving the request, to transmit to the vehicle an instruction to turn on a function of the remote immobilizer, thereby remotely operating an in-vehicle immobilizer device mounted on the vehicle, thereby turning on the function of the remote immobilizer; the in-vehicle immobilizer device is configured to prohibit execution of a drive system of the vehicle while the function of the remote immobilizer is on; Vehicle control system.

24. the server is configured to, when the remote immobilizer is turned on, notify a terminal of an authorized user of the vehicle that the remote immobilizer has been turned on; 24. The vehicle control system of claim 23.

25. The server is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a predetermined time period is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the predetermined time period even if the location of the vehicle is outside the predetermined geographical area.

24. The vehicle control system of claim 23.

26. the server is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired on a predetermined day of the week is outside the predetermined geographical area, and is configured not to turn on the remote immobilizer on days other than the predetermined day of the week even if the location of the vehicle is outside the predetermined geographical area.

24. The vehicle control system of claim 23.

27. the server is configured to turn on the remote immobilizer based on the fact that the location of the vehicle acquired during a preset time period on a preset day of the week is outside the preset geographical area, and is configured not to turn on the remote immobilizer during a time period that does not correspond to the preset time period on the preset day of the week even if the location of the vehicle is outside the preset geographical area.

24. The vehicle control system of claim 23.

28. The predetermined geographical area is set through machine learning based on the past driving history of the vehicle.

24. The vehicle control system of claim 23.

29. When a plurality of geographical areas are set as the predetermined geographical area, the server is configured to turn on the remote immobilizer when the vehicle moves from one of the plurality of predetermined geographical areas to outside the geographical area.

24. The vehicle control system of claim 23.

30. the vehicle is configured to request the server to send an instruction to the vehicle to turn on the remote immobilizer if the vehicle's location cannot be obtained; 24. The vehicle control system of claim 23.

31. When an attempt is made to start a drive system of the vehicle while the remote immobilizer is on, the in-vehicle immobilizer device is configured to display a message on a display unit prompting an input for authentication, the in-vehicle immobilizer device is configured to transmit a request to the server to turn off the remote immobilizer when preset identification information corresponding to the display is input; the server is configured to turn off the remote immobilizer by remotely operating the vehicle immobilizer device mounted on the vehicle in response to the request.

24. The vehicle control system of claim 23.

32. the server is configured to transmit the operation status of the remote immobilizer to a terminal of a legitimate user of the vehicle in response to a request from the terminal.

24. The vehicle control system of claim 23.

33. the server is configured to turn off the remote immobilizer when a request to turn off the remote immobilizer is received from a terminal of an authorized user of the vehicle while the remote immobilizer is on; 24. The vehicle control system of claim 23.

Images