Vehicle control device

Abstract

The vehicle control device (1) is equipped with a processor. When the processor receives a first signal indicating that payment of debt to the target vehicle (4) has not been properly made, it locks the engine start of the target vehicle (4), obtains information on the purpose of use, and determines whether the target vehicle (4) is being used for the intended purpose. When the processor determines that the target vehicle (4) is being used for the intended purpose, it unlocks the engine start of the target vehicle (4) and obtains information on the usage status. Additionally, based on the information on the usage status and the information on the purpose of use, the processor determines whether the target vehicle (4) is being used for purposes other than the intended purpose, and when it determines that the target vehicle (4) is being used for purposes other than the intended purpose, it locks the engine start of the target vehicle (4).

Description

Technology Field

[0001] The present disclosure relates to a vehicle control device. Background Technology

[0002] Japanese Patent No. 6647509 discloses a technology in which an individual or legal entity other than the user of a vehicle, such as the owner of the vehicle (hereinafter simply referred to as the “creditor”), locks the engine start of a vehicle for reasons of preservation of claims or safety. In this technology, when the creditor has not recovered the claim from the debtor, such as the user, the engine start is locked, and when the claim can be recovered from the debtor, the engine start is unlocked.

[0003] Meanwhile, after the vehicle's engine lock has been activated, if the debtor has no choice but to use the vehicle for daily life purposes, such as commuting to work or visiting a doctor, the creditor may unlock the vehicle's engine lock to permit its use. For example, if the creditor does not allow the minimum use of the vehicle for the creditor's daily life, the performance of the debtor's obligations will be increasingly delayed, which will result in disadvantage. The problem to be solved

[0004] However, if the engine start lock is unconditionally released, it is difficult to secure the claim, and the creditor's objective of recovering the claim cannot be achieved, leaving room for improvement.

[0005] The present disclosure is made in light of the above and provides a vehicle control device capable of securing claims, achieving claims recovery, and providing flexibility in the use of a vehicle. means of solving the problem

[0006] A vehicle control device according to the present disclosure comprises a processor. The processor is configured to receive a first signal indicating that payment of a debt to the target vehicle has not been properly made from a debt management server configured to manage debts of the target vehicle, and in response to receiving the first signal, control the engine start of the target vehicle to be locked, acquire purpose of use information regarding the purpose of use of the target vehicle, determine whether the target vehicle is being used for the purpose based on the purpose of use information, and if it is determined that the target vehicle is being used for the purpose, control the engine start of the target vehicle to be unlocked, acquire usage status information regarding the usage status of the target vehicle, determine whether the target vehicle is being used for a non-purpose based on the usage status information and the purpose of use information, and if it is determined that the target vehicle is being used for a non-purpose, control the engine start of the target vehicle to be re-locked.

[0007] A vehicle control device according to the present disclosure comprises a processor. When the processor receives a first signal indicating that payment of a debt to a target vehicle has not been properly made, it locks the engine start of the target vehicle, obtains usage purpose information regarding the purpose of use of the target vehicle, determines whether the target vehicle is being used for the purpose based on the usage purpose information, and when it is determined that the target vehicle is being used for the purpose, it unlocks the engine start of the target vehicle, obtains usage status information regarding the usage status of the target vehicle, determines whether the target vehicle is being used for a non-purpose based on the usage status information and the usage purpose information, and when it is determined that the target vehicle is being used for a non-purpose, it locks the engine start of the target vehicle again. Effects of the invention

[0008] According to the present disclosure, while preserving the claim, the creditor's objective can be achieved and the use of the vehicle can be permitted. Brief explanation of the drawing

[0009] The features, advantages, and technical and industrial significance of exemplary embodiments of the present invention are described below with reference to the accompanying drawings, in which similar reference numerals indicate similar elements. FIG. 1 is a block diagram showing the schematic configuration of a vehicle control system according to Embodiment 1 of the present disclosure. FIG. 2 is a sequence diagram showing an example of the exchange of information between each of the debt collection server, vehicle information server, and vehicle, which are provided in a vehicle control system according to Embodiment 1 of the present disclosure. FIG. 3 is a flowchart showing an overview of the processing performed by a debt collection server according to Embodiment 1 of the present disclosure. FIG. 4 is a flowchart showing an overview of the process of unlocking the engine start lock after locking the engine start of a vehicle executed by a vehicle information server according to Embodiment 1 of the present disclosure. FIG. 5 is a flowchart showing an overview of the processing when a vehicle information server according to Embodiment 1 of the present disclosure performs the activation of the engine start lock of a vehicle. FIG. 6 is a flowchart showing an overview of the process when releasing the engine start lock after the engine start performed by the vehicle according to Embodiment 1 of the present disclosure. FIG. 7 is a flowchart showing an overview of the process for re-locking the engine start after releasing the engine start lock performed by a vehicle according to Embodiment 1 of the present disclosure. FIG. 8 is a flowchart showing an overview of the processing performed by a vehicle according to Embodiment 2 of the present disclosure. Specific details for implementing the invention

[0010] Hereinafter, a vehicle control device according to an embodiment of the present disclosure will be described with reference to the drawings. In addition, the components in the following embodiments include those that are easily replaceable by those skilled in the art or are substantially identical.

[0011] Embodiment 1

[0012] Vehicle control system

[0013] FIG. 1 is a block diagram showing the schematic configuration of a vehicle control system according to Embodiment 1. The vehicle control system (100) shown in FIG. 1 comprises a debt collection server (1), a debt management server (2), a vehicle information server (3), a vehicle (4), and a terminal device (5). The debt collection server (1), the debt management server (2), the vehicle information server (3), the vehicle (4), and the terminal device (5) are all equipped with communication functions and are configured to communicate with each other through a network N to exchange various information. This network N is configured by a public network such as an internet network or a mobile phone network. In addition, among the vehicle control systems according to Embodiment 1, the debt collection server (1) functions as a vehicle control device that remotely controls the operation of the vehicle (4) (in particular, engine start lock and engine start lock release by an immobilizer).

[0014] In addition, in embodiment 1, "claims" may include, for example, claims related to an installment contract for the purchase of a vehicle, claims related to a lease contract for a vehicle (4), claims related to a subscription contract for a vehicle (4), claims related to a rental car contract for a vehicle (4), etc.

[0015] In addition, the creditor in Embodiment 1 is, for example, the holder (owner) of the vehicle (4). Specifically, the creditor may be, for example, a dealer who sold the vehicle (4), a credit sales company, and a bank. In addition, the debtor in Embodiment 1 is, for example, the user of the vehicle (4). Specifically, the debtor may be, for example, the purchaser of the vehicle (4), a contracting party such as a lease agreement, or a business company.

[0016] [Functional Configuration of the Debt Collection Server]

[0017] First, the functional configuration of the debt collection server (1) will be explained. The debt collection server (1) remotely controls the operation of the vehicle (4) to collect debts related to the vehicle (4). As shown in FIG. 1, the debt collection server (1) is equipped with a control unit (11), a vehicle history DB (DataBase) (12), a display device (13), an input device (14), and a communication unit (15).

[0018] The control unit (11) is realized by a processor, such as a CPU (Central Processing Unit), and a memory (main memory) such as RAM (Random Access Memory) or ROM (Read Only Memory). When the vehicle (4) satisfies the requirements for an engine start lock that have been predetermined (hereinafter referred to as "engine start lock requirements"), the control unit (11) obtains specific information from the vehicle history DB (12) and the vehicle information server (3), and determines whether to activate the engine start lock based on this information. When the control unit (11) determines that the engine start lock should be activated, it locks the engine start of the vehicle (4) (controls that the engine does not start).

[0019] "Engine start lock condition" can be, for example, when the debtor of the vehicle (4) is in default (e.g., delayed payment). The determination of whether this engine start lock condition is satisfied is, for example, made by the debt collection server (1). And, if there is a vehicle (4) (target vehicle) that satisfies the engine start lock condition, information for identifying the vehicle (4) (e.g., vehicle identification number (VIN number), etc.) is transmitted from the debt management server (2) to the debt collection server (1). Also, the target vehicle refers, for example, to the vehicle (4) subject to the debt.

[0020] Additionally, regarding a vehicle (4) with its engine locked, the control unit (11) acquires (receives) information regarding the purpose of use of the vehicle (4) from a predetermined terminal device, for example, the debtor's terminal device (5), and determines whether the vehicle (4) is being used for its intended purpose based on the information regarding the purpose of use. Then, if the control unit (11) determines that the vehicle (4) is being used for its intended purpose, it unlocks the engine of the vehicle (4) by remote control. After unlocking the engine of the vehicle (4), the control unit (11) acquires information regarding the usage status of the vehicle (4), and determines whether the vehicle (4) is being used for purposes other than its intended purpose based on the acquired information regarding the usage status and the information regarding the purpose of use requested from the debtor's terminal device (5). And, when the control unit (11) determines that the vehicle (4) is being used for purposes other than intended, it outputs a lock signal to the immobilizer (42) of the vehicle (4) to activate the engine start lock of the vehicle (4) and re-locks the engine start of the vehicle (4) by remote control.

[0021] The vehicle history DB (12) is configured using an HDD (Hard Disk Drive) or an SSD (Solid State Drive), and is a database that accumulates various information regarding the vehicle (4). For example, the vehicle history DB (12) acquires usage status information from the vehicle information server (3) and accumulates it by corresponding it to the vehicle identification number (VIN number), etc. Additionally, the vehicle history DB (12) accumulates normal stopping location information, for example, information regarding the location where the vehicle (4) normally or routinely stops or parks, which is created by the control unit (11) based on the usage status information accumulated in the vehicle history DB (12).

[0022] The display device (13) is realized by, for example, a liquid crystal display (LCD), an organic EL display (OLED), etc. The display device (13) displays various information under the control of the control unit (11).

[0023] The input device (14) is realized by, for example, a touch panel, a keyboard, a pointing device, etc. The input device (14) receives input of various operations by a user and outputs a signal corresponding to the received operation to the control unit (11).

[0024] The communication unit (15) is composed of, for example, a LAN (Local Area Network) interface board, a wireless communication circuit for wireless communication, etc. Under the control of the control unit (11), the communication unit (15) performs the exchange of information between the bond management server (2) and the vehicle information server (3) by communication through network N.

[0025] [Functional Configuration of the Debt Management Server]

[0026] Next, the functional configuration of the receivables management server (2) will be described. The receivables management server (2) is intended to manage receivables related to a vehicle (4). The receivables management server (2) is equipped with a receivables management system (21), a receivables management DB (22), and a communication unit (23).

[0027] The debt management system (21) transmits information (e.g., vehicle identification number (VIN number), etc.) to the debt recovery server (1) to identify the vehicle (4) among the multiple vehicles (4) managed by the debt management DB (22) when there is a vehicle (4) (target vehicle) that satisfies the requirements for an engine start lock. Here, the vehicle (4) (target vehicle) that satisfies the requirements for an engine start lock is a vehicle (4) (target vehicle) in which a delay in payment, etc., from the debt by the debtor has occurred, a vehicle (4) (target vehicle) in which payment of the debt has not been properly made, and a vehicle (4) in which a default has occurred.

[0028] The debt management DB (22) manages information for identifying each vehicle (4) and information regarding the debt of said vehicle (4) in correspondence. Here, the information for identifying each vehicle (4) is, for example, a vehicle identification number (VIN number). In addition, the information regarding the debt of said vehicle (4) is repayment information indicating the payment status of, for example, loan debt and lease debt.

[0029] The communication unit (23) is composed of, for example, a LAN interface board, a wireless communication circuit for wireless communication, etc. The communication unit (23) performs the exchange of information with the debt collection server (1) through communication via network N.

[0030] [Functional Configuration of the Vehicle Information Server]

[0031] Next, the functional configuration of the vehicle information server (3) is described. The vehicle information server (3) acquires usage status information from the vehicle (4) in response to a request from the debt collection server (1) and transmits the acquired usage status information to the debt collection server (1). The vehicle information server (3) is equipped with a control unit (31), a vehicle information DB (32), and a communication unit (33).

[0032] The control unit (31) is realized by a processor, such as a CPU, and a memory (main memory) such as RAM or ROM. The control unit (31) acquires usage status information from the vehicle (4) in response to a request from the debt collection server (1) and transmits the acquired usage status information to the debt collection server (1).

[0033] The vehicle information DB (32) accumulates usage status information obtained from the vehicle (4) (target vehicle) and information for identifying the vehicle (4) (e.g., vehicle identification number (VIN number), etc.) in correspondence. The vehicle information DB (32) transmits the usage status information to the debt collection server (1) under the control of the control unit (31) in response to a request from the debt collection server (1).

[0034] The communication unit (33) is composed of, for example, a LAN interface board, a wireless communication circuit for wireless communication, etc. The communication unit (33) performs the exchange of information between the debt collection server (1), the debt management server (2), and the vehicle (4) through communication via network N.

[0035] Vehicle Function Configuration

[0036] Next, the functional configuration of the vehicle (4) will be described. The vehicle (4) is, for example, a conventional engine vehicle (CONV), a hybrid electric vehicle (HEV), a plug-in hybrid electric vehicle (PHEV), etc. Additionally, the vehicle (4) may be, for example, a fuel cell electric vehicle (FCEV), a battery electric vehicle (BEV), etc.

[0037] The vehicle (4) is equipped with a memory (40), an ECU (41), an immobilizer (42), a positioning unit (43), a detection unit (44) (Bluetooth detection device), an imaging device (45), a clock (46), a weight sensor (47), an input unit (48), a communication unit (49), and a display device (50).

[0038] The memory (40) is configured using an HDD or SSD, etc., and records 2D map information or 3D map information used by the positioning unit (43).

[0039] The ECU (41) is an Electronic Control Unit whose main components are a microcomputer, such as a CPU, ROM, RAM, etc. The ECU (41) transmits usage status information to the vehicle information server (3) in response to a request (remote control) from the debt collection server (1) via the vehicle information server (3). In addition, the ECU (41) acquires usage status information of the vehicle (4) detected by each of the positioning unit (43) and the detection unit (44) in response to a request (remote control) from the debt collection server (1), and transmits it to the debt collection server (1) via the vehicle information server (3). Furthermore, the ECU (41) performs the activation of the engine start lock of the vehicle (4) in response to an instruction signal instructing the activation of the engine start lock for remote control transmitted from the debt collection server (1) via the vehicle information server (3). That is, the ECU (41) controls the vehicle (4) so ​​that the engine is not started even when the debtor presses the ignition switch to start the vehicle (4). In this case, the ECU (41) may display information on the display device (50) equipped with the vehicle (4) indicating that the engine has been locked due to the delay in payment of the debt, or may display contact information for the creditor.

[0040] The immobilizer (42) enables or disables the engine start lock based on the control of the ECU (41). Specifically, the immobilizer (42) enables or disables the engine start lock under the control of the ECU (41) in accordance with the remote control of the vehicle information server (3). The immobilizer (42) is realized by a processor consisting of a CPU, etc. and a memory (main memory) consisting of RAM, ROM, etc., and records key information (ID code) for disabling the engine start lock in the memory. The immobilizer (42) determines whether the key information included in the remote control of the vehicle information server (3) matches the key information recorded in the memory, and if the key information matches, enables or disables the engine start lock under the control of the ECU (41) in accordance with the remote control of the vehicle information server (3).

[0041] The positioning unit (43) detects the current position of the vehicle (4) by receiving radio waves from, for example, a GPS (Global Positioning System) satellite. In addition, the method of detecting the current position of the vehicle (4) is not limited to a method using GPS satellites, and may use, for example, a method combining LiDAR (Light Detection and Ranging, Laser Imaging Detection and Ranging) and 2D or 3D map information recorded by the memory (40).

[0042] The detection unit (44) detects a terminal device located within the vehicle (4). Specifically, the detection unit (44) detects the identifier (UUID: Universally Unique Identifier) ​​of a terminal device located within the vehicle (4) that emits Bluetooth (registered trademark), and outputs the detection result to the ECU (41). The detection unit (44) is configured using a Bluetooth receiver or a Bluetooth beacon, etc.

[0043] The imaging device (45) captures the interior or exterior of the vehicle (4) to generate still image data or moving image data, and outputs the still image data or moving image data to the ECU (41). The imaging device (45) is configured using one or more lenses and a CCD (Charge Coupled Device) and CMOS (Complementary Metal Oxide Semiconductor), etc., which capture the image of a subject formed by the lenses.

[0044] The clock (46) is configured using a timer or the like that has a timekeeping function, and displays the time and outputs the result of this display to the ECU (41).

[0045] A weight sensor (47) is provided in each seat, trunk, and suspension of the vehicle (4). The weight sensor (47) measures the weight of a passenger or user seated in each seat and outputs the measurement result to the ECU (41). Additionally, the weight sensor (47) measures the weight of the vehicle (4) and outputs the measurement result to the ECU (41).

[0046] The input unit (48) is realized, for example, by a touch panel, keyboard, pointing device, etc. The input unit (48) receives input of various operations by a user and outputs a signal corresponding to the received operation to the ECU (41).

[0047] The communication unit (49) is composed of, for example, a DCM (Data Communication Module), etc. The communication unit (49) performs the exchange of information with the vehicle information server (3) through communication via network N.

[0048] The display device (50) is realized by, for example, a liquid crystal display (LCD), an organic EL display (OLED), etc. The display device (50) displays various information under the control of the ECU (41).

[0049] [Terminal Device]

[0050] Next, the terminal device (5) will be described. The terminal device (5) is an information processing terminal, such as a mobile phone. The terminal device (5) receives inputs of various operations by the debtor. Specifically, when the engine start is locked by the immobilizer (42) of the vehicle (4), the terminal device (5) receives input of purpose of use information regarding the purpose of using the vehicle (4) to unlock the engine start of the vehicle (4) through the debt management server (2) or the debt collection server (1). Additionally, the terminal device (5) transmits the received purpose of use information to the debt collection server (1) or the debt management server (2). Here, the purpose of use information includes the reason for the debtor to use the vehicle (4), the destination, the date and time of use, and the time of use.

[0051] [Exchange of Information Between Each Device of the Vehicle Control System]

[0052] Next, the exchange of information between the debt collection server (1), the debt management server (2), the vehicle information server (3), the vehicle (4), and the terminal device (5) will be described. FIG. 2 is a sequence diagram showing an example of the exchange of information between each of the debt collection server (1), the debt management server (2), the vehicle information server (3), the vehicle (4), and the terminal device (5). In addition, the following processing will be described by giving an example of the processing performed on a vehicle (4) (target vehicle) used by a debtor who has a delay in the payment of debt among a plurality of vehicles (4).

[0053] As shown in FIG. 2, first, when the control unit (11) of the debt collection server (1) receives a first signal (hereinafter simply referred to as the "first signal") from the debt management server (2) indicating that payment of debt to the vehicle (4) (target vehicle) has not been properly made (step S1), the engine start of the vehicle (4) is locked by remote control. Specifically, in order to lock the engine start of the vehicle (4) by remote control, i.e., perform remote lock control, the control unit (11) of the debt collection server (1) transmits the first signal and a lock signal requesting the lock of the engine start of the vehicle (4) to the vehicle information server (3) (step S2). Subsequently, the vehicle information server (3), based on the first signal and lock signal received from the debt collection server (1), transmits a lock signal to the vehicle (4) to request the engine start lock as a lock signal for the debt collection server (1) to remotely control the engine start of the vehicle (4) (Step S3). Accordingly, the vehicle (4) locks the engine start and provides a reply to the vehicle information server (3) with information on the success of the engine start lock activation (Step S4). Specifically, the vehicle (4) provides a reply to the vehicle information server (3) with information on the success of the engine start lock activation by remote control by the vehicle information server (3). After that, the vehicle information server (3) transmits the reply with the success information received from the vehicle (4) to the debt collection server (1) (Step S5). In this case, the debt collection server (1) corresponds the successful information on the activation of the engine start lock of the vehicle (4) by remote control received from the vehicle information server (3) with the vehicle identification number (VIN number) of the vehicle (4) and accumulates it in the vehicle history DB (12).

[0054] Next, when the terminal device (5) receives input of purpose of use information for temporarily using the vehicle (4) with the engine locked according to the debtor's operation input, it transmits the received purpose of use information to the debt collection server (1) (Step S6). Subsequently, the debt collection server (1) searches for the vehicle identification number of the vehicle (4) accumulated in the vehicle history DB (12) from the vehicle identification number associated with the identification information of the terminal device (5) included in the purpose of use information, and transmits a release signal and purpose of use information to the vehicle information server (3) to remotely release the engine lock of the vehicle (4) (Step S7). In this case, the control unit (11) of the debt collection server (1) determines whether the reason for use included in the purpose of use information is a pre-determined reason for use, and if it is a pre-determined reason for use, that is, if it is use within the purpose, it transmits a release signal and purpose of use information to the vehicle information server (3) to release the engine lock of the vehicle (4). In contrast, the control unit (11) of the debt collection server (1) does not transmit a release signal to unlock the engine start of the vehicle (4) if it is determined that the reason for use is not a pre-established reason, that is, if it is not used for the intended purpose. Here, the pre-established reasons for use include, for example, the debtor's use to travel to a hospital, the debtor's family's use to transport to a hospital or school, the use to travel to purchase daily necessities, or the use to travel to carry out evacuation during a disaster such as an earthquake or heavy rain. These pre-established reasons for use are recorded in the vehicle history DB (12) or the memory (40) of the vehicle (4). In addition, the vehicle history DB (12) records the reasons for use in correspondence with the vehicle identification number (VIN number) of the vehicle (4). After that, the vehicle information server (3) transmits the purpose of use information and a release signal to the vehicle (4) for the debt collection server (1) to remotely control and unlock the engine start of the vehicle (4) (Step S8).Accordingly, the vehicle (4) releases the engine start lock in accordance with the remote control of the engine start lock of the vehicle (4) by the debt collection server (1), and sends a reply of lock release information to the vehicle information server (3) indicating that the engine start lock has been released (Step S9). After that, the vehicle information server (3) transmits the reply of lock release information received from the vehicle (4) to the debt collection server (1) (Step S10). In this case, the debt collection server (1) corresponds the lock release information received from the vehicle information server (3) regarding the release of the engine start lock of the vehicle (4) with the vehicle identification number (VIN number) of the vehicle (4) and accumulates it in the vehicle history DB (12). Then, the debt collection server (1) transmits the reply of lock release information received from the vehicle information server (3) to the terminal device (5) (Step S11). By doing so, the debtor can determine that the engine lock of the vehicle (4) has been temporarily released.

[0055] Next, the debt collection server (1) requests the vehicle information server (3) for the usage status information of the vehicle (4) at regular intervals, for example, in order to obtain the usage status information of the vehicle (4) via remote control at regular intervals (Step S12). Subsequently, the vehicle information server (3) requests the vehicle (4) for usage status information based on the request for usage status information received from the debt collection server (1) (Step S13). Accordingly, the vehicle (4) transmits one or more of the following as usage status information to the vehicle information server (3): the location information of the vehicle (4) detected by the positioning unit (43), the identification information of the terminal device (5) emitted by the terminal device (5) present in the vehicle (4) detected by the detection unit (44) (first identification information), still image data or moving image data captured by the imaging device (45), time information displayed by the clock (46), and the weight result detected by the weight sensor (47) (Step S14). Next, the vehicle information server (3) transmits the usage status information received from the vehicle (4) to the debt collection server (1) (step S15). In this case, the debt collection server (1) matches the usage status information of the vehicle (4) received from the vehicle information server (3) with the vehicle identification number (VIN number) of the vehicle (4) and accumulates it in the vehicle history DB (12).

[0056] Next, the control unit (11) of the debt collection server (1) determines whether the vehicle (4) is being used for purposes other than intended based on the usage status information of the vehicle (4) and the usage purpose information received from the terminal device (5) associated with the vehicle (4) (vehicle identification information). If it is determined that the vehicle is being used for purposes other than intended, the control unit (11) transmits a lock signal requesting a re-lock of the engine start to the vehicle information server (3) to perform remote control, i.e., remote locking, for re-locking the engine start (Step S16). Subsequently, the vehicle information server (3) transmits the lock signal requesting a re-lock of the engine start received from the debt collection server (1) to the vehicle (4) (Step S17). Accordingly, the vehicle (4) re-locks the engine start according to the remote control by the debt collection server (1) and sends a reply to the vehicle information server (3) with information on the success of the engine start lock activation (Step S18). After that, the vehicle information server (3) transmits a reply regarding the success of the engine start lock activation received from the vehicle (4) to the debt collection server (1) (step S19). In this case, the debt collection server (1) corresponds the success of the engine start lock activation of the vehicle (4) received from the vehicle information server (3) with the vehicle identification number (VIN number) of the vehicle (4) and accumulates it in the vehicle history DB (12). By doing so, the creditor can preserve the vehicle (4) that is the subject of the debt.

[0057] Processing on the debt collection server

[0058] Next, the processing performed by the debt collection server (1) will be described. FIG. 3 is a flowchart showing an overview of the processing performed by the debt collection server (1).

[0059] As shown in FIG. 3, when the control unit (11) receives a first signal from the debt management server (2) (step S100), it transmits the first signal from the debt management server (2) and a lock signal to the vehicle information server (3) to request the engine start of the vehicle (4) to be locked by remote control (step S101).

[0060] Next, the control unit (11) determines whether it has received a reply from the vehicle information server (3) regarding the success of the activation of the engine start lock of the vehicle (4) (step S102). If the control unit (11) determines that it has received a reply from the vehicle information server (3) regarding the success of the activation of the engine start lock of the vehicle (4) (step S102: "Yes"), the debt collection server (1) proceeds to step S103, which is described later. Conversely, if the control unit (11) determines that it has not received a reply from the vehicle information server (3) regarding the success of the activation of the engine start lock of the vehicle (4) (step S102: "No"), the debt collection server (1) returns to step S101.

[0061] Next, the control unit (11) obtains information regarding the purpose of use for temporarily using the vehicle (4) with the engine locked from the terminal device (5) via the communication unit (15) (step S103). Specifically, the control unit (11) obtains information regarding the purpose of use input by, for example, by operating the terminal device (5) associated with the vehicle (4) from the terminal device (5).

[0062] Next, the control unit (11) determines whether the purpose of use information for temporarily using the vehicle (4) with the engine locked, obtained from the terminal device (5) via the communication unit (15), is within the intended purpose (step S104). In this case, the control unit (11) determines whether the use is within the intended purpose by determining whether the reason for use included in the purpose of use information obtained from the terminal device (5) is a pre-conceived reason for use. Here, the pre-conceived reasons for use are, for example, the debtor's use to travel to a hospital, the debtor's family's use to transport to a hospital or school, the use to travel to purchase daily necessities, or the use to travel to carry out evacuation during a disaster such as an earthquake or heavy rain. That is, the control unit (11) determines whether the use is within the intended purpose by using one or more of these reasons for use. Of course, the pre-conceived reasons for use are merely examples and can be appropriately added or modified. If the information regarding the purpose of use for temporarily using the vehicle (4) whose engine has been locked by the control unit (11) is determined to be within the intended purpose (Step S104: "Yes"), the debt collection server (1) proceeds to Step S105 described later. Conversely, if the information regarding the purpose of use for temporarily using the vehicle (4) whose engine has been locked by the control unit (11) is determined not to be within the intended purpose (Step S104: "No"), the debt collection server (1) terminates the processing.

[0063] Next, the control unit (11) transmits a release signal to the vehicle (4) to remotely release the engine start lock of the vehicle (4), which is a second signal indicating permission for temporary use of the vehicle (4) through the communication unit (15) (step S105).

[0064] Next, the control unit (11) determines whether it has received a reply regarding unlock information for unlocking the engine start lock of the vehicle (4) from the vehicle information server (3) via the communication unit (15) (step S106). If the control unit (11) determines that it has received a reply regarding unlock information for unlocking the engine start lock of the vehicle (4) from the vehicle information server (3) (step S106: "Yes"), the debt collection server (1) proceeds to step S107. Conversely, if the control unit (11) determines that it has not received a reply regarding unlock information for unlocking the engine start lock of the vehicle (4) from the vehicle information server (3) (step S106: "No"), the debt collection server (1) returns to step S105.

[0065] Next, the control unit (11) requests the vehicle information server (3) at regular intervals to obtain the vehicle (4) usage status information through the communication unit (15) in order to obtain the vehicle (4) usage status information via remote control (step S107).

[0066] Next, the control unit (11) obtains information on the usage status of the vehicle (4) from the vehicle information server (3) through the communication unit (15) (step S108).

[0067] After that, the control unit (11) determines whether the vehicle (4) is being used for purposes other than intended based on the usage status information of the vehicle (4) obtained through the vehicle information server (3) and the usage purpose information received from the terminal device (5) associated with the vehicle (4) (vehicle identification information) (step S109). Specifically, the control unit (11) determines whether the vehicle (4) is being used for purposes other than intended by performing one or more of the following (1) to (8).

[0068] (1) The control unit (11) determines whether the identification information (first identification information) for identifying a terminal device that is detected by the detection unit (44) within the vehicle (4) matches the second identification information for identifying a predetermined information processing terminal recorded in the vehicle history DB (12), and if the first identification information and the second identification information do not match, the control unit determines that the vehicle (4) is being used for purposes other than intended. In this case, the control unit (11) determines that the vehicle (4) is being used by a user who is different from any of the following: the debtor who applied for the release of the engine start lock, the family related to the debtor, or the user of the vehicle (4) that was previously registered, and controls the immobilizer (42) to re-lock the engine start of the vehicle (4). In this case, the ECU (41) receives a lock signal from the debt collection server (1) and controls the immobilizer (42). In this case, the immobilizer (42) does not drive the engine of the vehicle (4) even if there is a command to start. At this time, the control unit (11) may display on the display device (50) or transmit to the terminal device (5) that the engine of the vehicle (4) is locked. Additionally, the second identification information does not need to be recorded in the vehicle history DB (12), and may determine whether the second identification information (first identification information) for identifying the terminal device emitted by the terminal device existing in the vehicle (4) detected by the detection unit (44) matches the debtor terminal (information processing terminal) of any of the debtors associated with the vehicle (4), family members related to the debtor, and pre-registered users of the vehicle (4) recorded in the vehicle history DB (12) provided by the debt collection server (1).

[0069] (2) The control unit (11) extracts a first feature quantity representing the facial features of a person included in the still image data or the moving image data captured by the imaging device (45) inside the vehicle (4), for example, and determines whether the degree of agreement between this first feature quantity and a second feature quantity representing the facial features of a predetermined face recorded in the vehicle history DB (12) is less than a predetermined value. Here, the predetermined face is, for example, the face of a debtor associated with the vehicle (4), a relative related to the debtor, or a user of the vehicle (4) that is previously registered. If the degree of agreement between the first feature quantity and the second feature quantity is less than a predetermined value, for example, less than 80%, the control unit (11) determines that the vehicle (4) is being used by a user other than the person who requested the release of the engine start lock, for example, the debtor, i.e., is use for purposes other than intended, and controls the immobilizer (42) to re-lock the engine start of the vehicle (4). Additionally, the control unit (11) may extract features by performing a known feature extraction process, such as Haar-Like features, HOG features, and SIFT features, on a still image corresponding to still image data or a moving image corresponding to moving image data. Of course, the control unit (11) may also extract features by using a learned model that has been trained in advance by machine learning such as deep learning, which inputs still image data and moving image data and outputs features of a person's face.

[0070] (3) The control unit (11) determines whether the difference between the weight result (weight information) of the user (passenger) seated on the seat detected by the weight sensor (47) and the weight information of a specific person recorded in the vehicle history DB (12) is greater than or equal to a predetermined value. Here, the specific person is, for example, a debtor associated with the vehicle (4), a relative associated with the debtor, and a user who has been registered in advance. If the difference between the weight result of the user seated on the seat detected by the weight sensor (47) and the weight information of the debtor associated with the vehicle (4) recorded in the vehicle history DB (12) is greater than or equal to a predetermined value, for example, 5 kg or more, the control unit (11) determines that a separate user different from the user (debtor) who requested the release of the engine start lock is using the vehicle (4), that is, determines that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine start of the vehicle (4).

[0071] (4) The control unit (11) extracts text and buildings included in the still image data or moving image data captured by the imaging device (45) outside the vehicle (4), for example, and determines whether the vehicle (4) is moving to a destination based on the extraction result and at least one of the predetermined destinations included in the purpose of use information. Here, the predetermined destination is, for example, destination information entered by the debtor or relatives related to the debtor, or workplace information of the debtor or relatives related to the debtor. In this case, the control unit (11) uses a learned model that has been trained in advance by machine learning such as deep learning, which inputs the still image data and moving image data and outputs the name of the building or text, to extract text and buildings included in the still image data or moving image data. And, if the control unit (11) determines that the vehicle (4) is not moving toward the destination, it determines that the vehicle is not heading toward the destination requested by the debtor, that is, that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, before re-locking the engine of the vehicle (4), the control unit (11) may give a warning to the display device (50) for a predetermined time, for example, about 5 minutes, and then control the immobilizer (42) to re-lock the engine of the vehicle (4). Of course, the control unit (11) may stop the warning if the vehicle (4) is moving toward the destination after giving a warning to the display device (50). Additionally, the control unit (11) may determine whether the vehicle (4) is moving to a destination based on the extraction result of text and buildings extracted from still image data or moving image data captured by the imaging device (45) outside the vehicle (4), a predetermined destination included in the purpose of use information, and map information including at least the text and building feature quantities recorded in the vehicle history DB (12).

[0072] (5) The control unit (11), for example, based on the location information of the vehicle (4), extracts text and facilities included in still image data or moving image data captured by the imaging device (45) outside the vehicle (4) when the vehicle (4) arrives at a destination, and determines whether the vehicle (4) has entered the facility based on the extraction result and the facility of the destination included in the purpose of use information. In this case, the control unit (11) uses a learned model that has been learned in advance by machine learning such as deep learning, which inputs the still image data and moving image data and outputs the name of the facility or text, to extract the text or facilities included in the still image data or moving image data. Then, if the control unit (11) determines that the vehicle (4) has not entered the facility, it determines that it is not within the facility of the destination applied for by the debtor, that is, that it is used for purposes other than the intended purpose, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). At this time, the control unit (11) may, before re-locking the engine of the vehicle (4), give a warning to the display device (50) for a predetermined time, for example, about 5 minutes, and then control the immobilizer (42) to re-lock the engine of the vehicle (4). Of course, the control unit (11) may stop the warning after giving a warning to the display device (50) if the vehicle (4) is moving toward the facility. In addition, when the vehicle (4) arrives at the destination, the control unit (11) may extract text and facilities included in still image data or moving image data captured by the imaging device (45) outside the vehicle (4), and determine whether the vehicle (4) has entered the facility based on the extraction result, the facilities of the predetermined destination included in the purpose of use information, and map information recorded in the vehicle history DB (12) that includes at least the text and facility feature quantities.

[0073] (6) The control unit (11) determines whether the weight detected by, for example, the weight sensor (47) is above a predetermined threshold, and if the weight is above the predetermined threshold, determines that the vehicle (4) is loaded with a load having a weight other than the intended purpose, i.e., determines that it is being used for purposes other than the intended purpose, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, the control unit (11) controls the immobilizer (42) to re-lock the engine of the vehicle (4) in order to preserve the vehicle (4) which is the claim, as there is a possibility that the user of the vehicle (4) is loading a load having a weight as assumed by the creditor. By doing so, the creditor can preserve the vehicle (4) which is the claim.

[0074] (7) The control unit (11) determines whether the vehicle (4) has been moving away from the destination for a predetermined amount of time based on, for example, the location information of the vehicle (4) and the predetermined destination included in the purpose of use information requested by the debtor. Then, the control unit (11) determines, for example, that the vehicle (4) has been moving away from the destination for a predetermined amount of time, that is, that it is being used for purposes other than the intended purpose, and remotely controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, the control unit (11) can preserve the vehicle (4) that is the claim while preventing false applications by a debtor with bad intentions.

[0075] (8) The control unit (11) determines whether the usage time of the vehicle (4) after unlocking the engine start lock of the vehicle (4) exceeds the predetermined usage time included in the usage purpose information, and if the usage time of the vehicle (4) exceeds the predetermined usage time, i.e., it determines that it is used for purposes other than intended, and remotely controls the immobilizer (42) to re-lock the engine start of the vehicle (4).

[0076] In this way, the control unit (11) determines whether the vehicle (4) is being used for purposes other than intended by performing one or more of (1) to (8) above. If the control unit (11) determines that the vehicle (4) is being used for purposes other than intended (Step S109: "Yes"), the debt collection server (1) proceeds to Step S110. Conversely, if the control unit (11) determines that the vehicle (4) is not being used for purposes other than intended (Step S109: "No"), the debt collection server (1) proceeds to Step S112.

[0077] Next, the control unit (11) transmits a lock signal to the vehicle information server (3) to request the vehicle (4) to lock the engine start by remote control (step S110).

[0078] Next, the control unit (11) determines whether it has received a reply from the vehicle information server (3) regarding the success of the activation of the engine start lock of the vehicle (4) (step S111). If the control unit (11) determines that it has received a reply from the vehicle information server (3) regarding the success of the activation of the engine start lock of the vehicle (4) (step S111: "Yes"), the debt collection server (1) terminates the processing. Conversely, if the control unit (11) determines that it has not received a reply from the vehicle information server (3) regarding the success of the activation of the vehicle (4) (step S111: "No"), the debt collection server (1) returns to step S110.

[0079] Next, the control unit (11) determines whether the elapsed time after releasing the engine start lock has exceeded a predetermined usage time. Here, the predetermined usage time is the usage time of the vehicle (4) requested by the debtor or the usage time determined in advance by the creditor. For example, the predetermined usage time is the time until the day of the usage request from the debtor, the time until 24 hours have elapsed from the time the usage request from the debtor was made, etc. Of course, as the usage time, it may also be the time obtained by multiplying the usage time of the vehicle (4) requested by the debtor by a coefficient. If the control unit (11) determines that the elapsed time after releasing the engine start lock has elapsed to a predetermined time (Step S112: "Yes"), the debt collection server (1) proceeds to Step S110. On the other hand, if it is determined that the time elapsed after the engine start lock is released by the control unit (11) has not elapsed for a predetermined time (step S112: "No"), the debt collection server (1) returns to step S107.

[0080] Vehicle Information Server Processing 1

[0081] Next, an overview of the process for unlocking the engine start lock after the vehicle information server (3) has locked the engine start of the vehicle (4) will be described. FIG. 4 is a flowchart showing an overview of the process for unlocking the engine start lock after the vehicle information server (3) has locked the engine start of the vehicle (4).

[0082] As shown in FIG. 4, first, the control unit (31) receives a first signal from the debt collection server (1) indicating that payment by the debtor to the vehicle information server (3) has not been properly made, and a lock signal to request the engine start of the vehicle (4) to be locked by remote control (step S201).

[0083] Next, the control unit (31) transmits a lock signal to the vehicle (4) to request the engine start of the vehicle (4) received from the debt collection server (1) to be locked by remote control (step S202).

[0084] After that, the control unit (31) receives information on the success of the engine start lock activation from the vehicle (4) (step S203) and transmits the information on the success of the engine start lock activation to the debt collection server (1) (step S204).

[0085] Subsequently, the control unit (31) receives information on the debtor's purpose of use and a release signal to release the engine start lock of the vehicle (4) from the debt collection server (1) (step S205), and transmits information on the debtor's purpose of use and a release signal to release the engine start lock of the vehicle (4) to the vehicle (4) (step S206).

[0086] Subsequently, the control unit (31) receives a reply from the vehicle (4) regarding the release information of the engine start lock of the vehicle (4) received from the vehicle (4) (step S207), and transmits the release information regarding the release of the engine start lock of the vehicle (4) to the debt collection server (1) (step S208). After step S208, the vehicle information server (3) terminates the processing.

[0087] Vehicle Information Server Processing 2

[0088] Next, an overview of the process for re-locking the engine start of a vehicle (4) after the vehicle information server (3) has released the engine start lock will be explained. FIG. 5 is a flowchart showing an overview of the process for re-locking the engine start of a vehicle (4) after the vehicle information server (3) has released the engine start lock.

[0089] As shown in FIG. 5, the control unit (31) receives a request for usage status information of the vehicle (4) based on a request for usage status information received from the debt collection server (1) (step S301), and transmits the request for usage status information to the vehicle (4) (step S302).

[0090] Next, the control unit (31) receives usage status information from the vehicle (4) (step S303) and transmits the usage status information received from the vehicle (4) to the debt collection server (1) (step S304).

[0091] After that, the control unit (31) receives a lock signal from the debt collection server (1) to request the engine start of the vehicle (4) to be locked by remote control (step S305), and transmits the lock signal received from the debt collection server (1) to the vehicle (4) to request the engine start of the vehicle (4) to be locked by remote control (step S306).

[0092] Next, the control unit (31) receives information on the success of the engine start lock activation from the vehicle (4) (step S307) and transmits the information on the success of the engine start lock activation to the debt collection server (1) (step S308). After step S308, the vehicle information server (3) terminates the processing.

[0093] Vehicle Disposal 1

[0094] Next, an overview of the process for unlocking the engine start lock after the vehicle (4) has locked the engine start will be described. FIG. 6 is a flowchart showing an overview of the process for unlocking the engine start lock after the vehicle (4) has locked the engine start.

[0095] As shown in FIG. 6, first, the ECU (41) receives a lock signal from the debt collection server (1) via the vehicle information server (3) to request the engine start of the vehicle (4) to be locked by remote control (step S401), and in accordance with this lock signal, controls the immobilizer (42) to lock the engine start and transmits information on the success of the engine start lock activation to the vehicle information server (3) (step S402).

[0096] Subsequently, the ECU (41) receives information on the debtor's purpose of use and a release signal to release the engine start lock of the vehicle (4) from the debt collection server (1) via the vehicle information server (3) (step S403), controls the immobilizer (42) to release the engine start lock, and transmits release information indicating that the engine start lock has been released to the vehicle information server (3) (step S404). After step S404, the vehicle (4) terminates the processing.

[0097] Vehicle Disposal 2

[0098] Next, an overview of the process for re-locking the engine start after releasing the engine start lock executed by the vehicle (4) will be described. FIG. 7 is a flowchart showing an overview of the process for re-locking the engine start after releasing the engine start lock executed by the vehicle (4).

[0099] As shown in FIG. 7, first, the ECU (41) receives a request for usage status information from the debt collection server (1) through the vehicle information server (3) (step S501), and in accordance with this request for usage status information, the ECU (41) acquires usage status information (step S502). Specifically, the ECU (41) acquires one or more of the following as usage status information: location information of the vehicle (4) detected by the positioning unit (43), identification information of the terminal device (first identification information) emitted by the terminal device existing in the vehicle (4) detected by the detection unit (44), still image data or moving image data captured by the imaging device (45), time information displayed by the clock (46), and weight result detected by the weight sensor (47).

[0100] Next, the ECU (41) transmits usage status information to the vehicle information server (3) (step S503). In this case, the ECU (41) transmits usage status information instructed by remote control from the debt collection server (1) through the vehicle information server (3). For example, if the ECU (41) is instructed by the debt collection server (1) to have the identification information (first identification information) of the terminal device emitted by the terminal device existing in the vehicle (4) detected by the detection unit (44) transmitted to the vehicle information server (3) as usage status information. Of course, the ECU (41) may also transmit a plurality of information, for example, location information of the vehicle (4) detected by the positioning unit (43), still image data or moving image data captured by the imaging device (45), to the vehicle information server (3) as usage status information.

[0101] After that, the ECU (41) receives a lock signal from the vehicle information server (3) to request the engine start of the vehicle (4) to be locked by remote control (step S504), and in accordance with this lock signal, controls the immobilizer (42) to re-lock the engine start and transmits information of the success of the engine start lock activation to the vehicle information server (3) (step S505). After step S505, the vehicle (4) terminates the process.

[0102] According to Embodiment 1 described above, after the control unit (11) remotely releases the lock on the engine start of the vehicle (4), if it is determined that the vehicle (4) is being used for purposes other than intended, the engine start of the vehicle (4) is re-locked, thereby enabling the recovery of the claim while preserving the claim and providing flexibility in the use of the vehicle (4).

[0103] In addition, according to Embodiment 1, when the control unit (11) receives information on the purpose of use of the vehicle (4) from a terminal device (5) (debtor terminal device) associated with the vehicle (4), it determines whether to permit temporary use of the vehicle (4) based on this information on the purpose of use, and when temporary use of the vehicle (4) is permitted, it outputs a release signal, which is a second signal for remotely controlling the engine start lock, to the immobilizer of the vehicle (4) to perform remote release control, thereby enabling the recovery of the debt while preserving the debt and providing flexibility in the use of the vehicle (4).

[0104] In addition, according to embodiment 1, the control unit (11) determines whether the identification information (first identification information) for identifying a terminal device that has been emitted by a terminal device within a vehicle (4) detected by the detection unit (44) matches the second identification information for identifying a predetermined information processing terminal recorded in the vehicle history DB (12), and if the first identification information and the second identification information do not match, the vehicle (4) is determined to be used for purposes other than intended, so that the vehicle (4) can be preserved when used for purposes other than intended.

[0105] In addition, according to embodiment 1, the control unit (11) extracts a first feature quantity representing the facial features of a person included in still image data or moving image data captured inside the vehicle (4) by the imaging device (45), and determines whether the degree of agreement between this first feature quantity and a second feature quantity representing the facial features of a predetermined face recorded in the vehicle history DB (12) is less than a predetermined value, so that the vehicle (4) can be preserved when used for purposes other than intended.

[0106] In addition, according to embodiment 1, since the control unit (11) determines whether the difference between the weight result of a user sitting on a seat detected by the weight sensor (47) and the weight information of a predetermined person recorded in the vehicle history DB (12) is greater than or equal to a predetermined value, the vehicle (4) can be preserved when used for purposes other than intended.

[0107] In addition, according to embodiment 1, the control unit (11) extracts text and buildings included in the still image data of the vehicle (4) or the moving image data captured by the imaging device (45), and determines whether the vehicle (4) is moving to a destination based on the extraction result and at least one of the predetermined destinations included in the purpose of use information, so that the vehicle (4) can be preserved when used for purposes other than intended.

[0108] In addition, according to embodiment 1, when the vehicle (4) arrives at a destination, the imaging device (45) extracts text and facilities included in still image data or moving image data that captures the outside of the vehicle (4), and determines whether the vehicle (4) has entered the facilities based on the extraction result and the facilities of the predetermined destination included in the purpose of use information, so that the vehicle (4) can be preserved when used for purposes other than intended.

[0109] In addition, according to embodiment 1, the control unit (11) determines whether the weight detected by the weight sensor (47) is above a predetermined threshold, and if the weight is above the predetermined threshold, it determines that the vehicle (4) is loaded with a weight other than the intended purpose, i.e., that it is used for purposes other than the intended purpose, and controls the immobilizer (42) to re-lock the engine of the vehicle (4), so that the vehicle (4) can be preserved when used for purposes other than the intended purpose.

[0110] In addition, according to embodiment 1, the control unit (11) determines whether the vehicle (4) has moved away from the destination and has elapsed a predetermined time based on the location information of the vehicle (4) and the predetermined destination included in the purpose of use information applied for by the debtor, so the vehicle (4) can be preserved while preventing false applications by a debtor with malice.

[0111] In addition, according to embodiment 1, the control unit (11) determines whether the usage time of the vehicle (4) after unlocking the engine start of the vehicle (4) exceeds a predetermined usage time included in the usage purpose information, and if the usage time of the vehicle (4) exceeds the predetermined usage time, the immobilizer (42) is controlled to re-lock the engine start of the vehicle (4), so that the vehicle (4) can be preserved when used for purposes other than intended.

[0112] Embodiment 2

[0113] Next, Embodiment 2 will be described. In Embodiment 1, the control unit (11) of the debt collection server (1) remotely determined whether the vehicle (4), for which the debtor applied for use and the engine start lock was released, was being used for purposes other than intended, based on usage status information obtained from the vehicle (4). However, in Embodiment 2, the vehicle (4) determines whether it is being used for purposes other than intended. That is, the vehicle control system for Embodiment 2 has the same configuration as the vehicle control system (100) for Embodiment 1, and the processing performed by the vehicle (4) is different. Therefore, the processing performed by the vehicle (4) for Embodiment 2 will be described. Furthermore, in the following, the same reference numerals are used for configurations identical to those of the vehicle control system (100) for Embodiment 1, and detailed descriptions are omitted.

[0114] Vehicle Disposal 3

[0115] FIG. 8 is a flowchart showing an overview of the processing performed by the vehicle (4) according to embodiment 2.

[0116] As shown in FIG. 8, first, the ECU (41) receives a first signal and a lock signal to request the engine start of the vehicle (4) to be locked by remote control from the debt collection server (1) through the vehicle information server (3) and the communication unit (49) (step S601), and in accordance with the first signal and the lock signal, controls the immobilizer (42) to lock the engine start (step S602). For example, the ECU (41) sets a flag so that the immobilizer (42) does not respond even when the start button of the vehicle (4) is pressed.

[0117] Next, the ECU (41) determines whether the engine start lock is activated based on, for example, the operating status of the immobilizer (42), and if the engine start lock is activated successfully, transmits the information on the success of the engine start lock activation to the debt collection server (1) through the communication unit (49) and the vehicle information server (3) (step S603).

[0118] Next, the ECU (41) obtains information regarding the purpose of use for temporarily using the vehicle (4) with the engine locked from the terminal device (5) via the communication unit (49) (step S604). Specifically, the ECU (41) obtains information regarding the purpose of use entered by, for example, the debtor by operating the terminal device (5).

[0119] Next, the ECU (41) determines whether the purpose of use information for temporarily using the vehicle (4) with the engine locked, which is obtained from the terminal device (5) via the communication unit (49), is within the intended purpose (Step S605). In this case, the ECU (41) determines whether the use is within the intended purpose by determining whether the reason for use included in the purpose of use information obtained from the terminal device (5) is a pre-conceived reason for use. Here, the pre-conceived reasons for use are, for example, the use of the debtor's transportation to a hospital, the use of transportation for the debtor's family to a hospital or school, the use of transportation to purchase daily necessities, and the use of transportation to carry out evacuation during a disaster such as an earthquake or heavy rain. That is, the ECU (41) determines whether the use is within the intended purpose by using one or more of these reasons for use. Of course, the pre-conceived reasons for use are merely examples and can be appropriately added or modified. These pre-conceived reasons for use are recorded in the memory (40) of the vehicle (4). If the information regarding the purpose of use for temporarily using the vehicle (4) with the engine locked by the ECU (41) is determined to be within the intended purpose (Step S605: "Yes"), the vehicle (4) proceeds to Step S606 described below. Conversely, if the information regarding the purpose of use for temporarily using the vehicle (4) with the engine locked by the ECU (41) is determined not to be within the intended purpose (Step S605: "No"), the vehicle (4) terminates this processing.

[0120] In step S605, if it is determined that the vehicle is being used for its intended purpose (step S605: "Yes"), the ECU (41) controls the immobilizer (42) to release the engine start lock (step S606). For example, when the start button of the vehicle (4) is pressed, the ECU (41) releases the engine start lock by knocking down a flag so that the immobilizer (42) responds.

[0121] Next, the ECU (41) acquires usage situation information (step S607). Specifically, the ECU (41) acquires one or more of the following as usage situation information:, for example, location information of the vehicle (4) detected by the positioning unit (43), identification information of the terminal device (first identification information) emitted by the terminal device present in the vehicle (4) detected by the detection unit (44), still image data or moving image data captured by the imaging device (45), time information displayed by the clock (46), and weight result detected by the weight sensor (47).

[0122] Next, the ECU (41) determines whether the vehicle (4) is being used for purposes other than intended based on usage status information and usage purpose information obtained in step S604 (step S608). Specifically, the ECU (41) determines whether the vehicle (4) is being used for purposes other than intended by performing, for example, one or more of the following (1) to (8).

[0123] (1)

[0124] The ECU (41) determines whether the identification information (first identification information) for identifying a terminal device that has been emitted by a terminal device within the vehicle (4) detected by, for example, the detection unit (44) matches the second identification information for identifying a debtor terminal associated with the vehicle (4) recorded in the memory (40), and if the first identification information and the second identification information do not match, it determines that the vehicle (4) is being used for purposes other than intended. In this case, the ECU (41) determines that the vehicle (4) is being used by a user who is different from any of the debtor who applied for the release of the engine start lock, the family related to the debtor, and the user of the vehicle (4) previously registered in the memory (40), and controls the immobilizer (42) to re-lock the engine start of the vehicle (4). At this time, the ECU (41) may display a message indicating that the engine start of the vehicle (4) is being re-locked on the display device (50) or transmit it to the terminal device (5). Additionally, the second identification information does not need to be recorded in the memory (40), and it may be determined whether the second identification information, which identifies the debtor terminal associated with the vehicle (4) recorded in the vehicle history DB (12) provided by the debt collection server (1), matches the identification information (first identification information) for identifying the terminal device emitted by the terminal device existing within the vehicle (4) detected by the detection unit (44).

[0125] (2)

[0126] The ECU (41) extracts a first feature quantity representing the facial features of a person included in still image data or moving image data captured by, for example, an imaging device (45) inside the vehicle (4), and determines whether the degree of agreement between this first feature quantity and a second feature quantity representing the facial features of a predetermined face associated with the vehicle (4) recorded in memory (40) is less than a predetermined value. Here, the predetermined face is the face of any of the debtor, a family member related to the debtor, or a user of the vehicle (4) that is previously registered. In this case, if the degree of agreement between the first feature quantity and the second feature quantity is less than a predetermined value, for example, less than 80%, the ECU (41) determines that a user other than the debtor who applied for the release of the engine start lock is using the vehicle (4), that is, determines that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine start of the vehicle (4). Additionally, the ECU (41) may extract features by performing a known feature extraction process, such as Haar-Like features, HOG features, and SIFT features, on a still image corresponding to still image data or a moving image corresponding to moving image data. Of course, the ECU (41) may also extract features by using a learned model that has been trained in advance by machine learning such as deep learning, inputting still image data and moving image data, and outputting features of a person's face.

[0127] (3)

[0128] The ECU (41) determines whether the difference between the weight result (weight information) of the user sitting on the seat detected by the weight sensor (47) and the weight information of a specific person recorded in the memory (40) is greater than or equal to a predetermined value. Here, the specific person is a debtor associated with the vehicle (4), a family member associated with the debtor, and a pre-registered user, etc. If the difference between the weight result of the user sitting on the seat detected by the weight sensor (47) and the weight information of the debtor associated with the vehicle (4) recorded in the memory (40) is 5 kg or more, the ECU (41) determines that a user other than the debtor who requested the release of the engine start lock is using the vehicle (4), that is, determines that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine start of the vehicle (4).

[0129] (4)

[0130] The ECU (41) extracts text and buildings included in still image data or moving image data captured by, for example, an imaging device (45) outside the vehicle (4), and determines whether the vehicle (4) is moving to a destination based on the extraction result and at least one of the predetermined destinations included in the purpose of use information. Here, the predetermined destination is destination information entered by the debtor or information about the debtor's workplace, etc. In this case, the ECU (41) uses a learned model that has been trained in advance by machine learning such as deep learning, which inputs still image data and moving image data and outputs the name of a building or text, to extract text or buildings included in the still image data or moving image data. Then, if the ECU (41) determines that the vehicle (4) is not moving to a destination, it determines that the vehicle is not heading toward the destination requested by the debtor, that is, determines that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, the ECU (41) may, before re-locking the engine of the vehicle (4), give a warning to the display device (50) for a predetermined time, for example, about 5 minutes, and then control the immobilizer (42) to re-lock the engine of the vehicle (4). Of course, the ECU (41) may stop the warning after giving a warning to the display device (50) if the vehicle (4) is moving toward a destination. In addition, the ECU (41) may determine whether the vehicle (4) is moving toward a destination based on still image data captured by the imaging device (45) outside the vehicle (4) or the extraction result of extracting text and buildings from the moving image data, a predetermined destination included in the purpose of use information, and map information recorded in the memory (40) that includes at least the text and building feature quantity.

[0131] (5)

[0132] The ECU (41), for example, when the vehicle (4) arrives at a destination, extracts text or facilities included in the still image data captured by the imaging device (45) outside the vehicle (4) or the moving image data, and determines whether the vehicle (4) has entered the facility based on the extraction result and the facility of the destination included in the purpose of use information. In this case, the ECU (41) extracts text or facilities included in the still image data or moving image data using a learned model that has been learned in advance by machine learning such as deep learning, which inputs the still image data or moving image data and outputs the name or text of the facility. Then, if the ECU (41) determines that the vehicle (4) is not inside the facility, it determines that it is not inside the facility applied for by the debtor, that is, that it is used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, the ECU (41) may, before re-locking the engine of the vehicle (4), give a warning to the display device (50) for a predetermined time, for example, about 5 minutes, and then control the immobilizer (42) to re-lock the engine of the vehicle (4). Of course, the ECU (41) may stop the warning after giving a warning to the display device (50) if the vehicle (4) is moving toward the facility. In addition, the ECU (41) may, for example, when the vehicle (4) arrives at a destination, extract text and facilities included in still image data or moving image data captured by the imaging device (45) outside the vehicle (4), and determine whether the vehicle (4) has entered the facility based on the extraction result, the facilities of a predetermined destination included in the purpose of use information, and map information including at least the text and facility features recorded in the memory (40).

[0133] (6)

[0134] The ECU (41) determines whether the weight detected by, for example, the weight sensor (47) is above a predetermined threshold, and if the weight is above the predetermined threshold, determines that the vehicle (4) is loaded with a load having a weight other than the intended purpose of use, i.e., determines that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, the ECU (41) controls the immobilizer (42) to re-lock the engine of the vehicle (4) in order to preserve the vehicle (4) which is the claim, as there is a possibility that the user of the vehicle (4) is loading a load having a weight assumed by the creditor. By doing so, the creditor can preserve the vehicle (4) which is the claim.

[0135] (7)

[0136] The ECU (41) determines whether a predetermined amount of time has elapsed while the vehicle (4) is moving away from the destination, for example, based on the location information of the vehicle (4) and the predetermined destination included in the purpose of use information applied for by the debtor. Then, the ECU (41) determines, for example, that a predetermined amount of time has elapsed while the vehicle (4) is moving away from the destination, i.e., that it is being used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine of the vehicle (4). In this case, the ECU (41) can preserve the vehicle (4), which is the claim, while preventing false applications by a debtor with bad intentions.

[0137] (8)

[0138] The ECU (41) determines whether the usage time of the vehicle (4) after unlocking the engine start lock of the vehicle (4) exceeds the predetermined usage time included in the usage purpose information, and if the usage time of the vehicle (4) exceeds the predetermined usage time, i.e., it determines that it is used for purposes other than intended, and controls the immobilizer (42) to re-lock the engine start of the vehicle (4).

[0139] In this way, the ECU (41) determines whether the vehicle (4) is being used for purposes other than intended by performing one or more of steps (1) through (8) above. If the ECU (41) determines that it is being used for purposes other than intended (Step S608: "Yes"), the vehicle (4) proceeds to Step S609. Conversely, if the ECU (41) determines that it is not being used for purposes other than intended (Step S608: "No"), the vehicle (4) proceeds to Step S610.

[0140] Next, the ECU (41) controls the immobilizer (42) to lock the engine start (step S609). The ECU (41) relocks the engine start by setting a flag so that the immobilizer (42) does not respond even when the start button of the vehicle (4) is pressed. After step S609, the vehicle (4) terminates this process.

[0141] In step S610, the ECU (41) determines whether a predetermined time has elapsed since the engine start lock was released. Here, the predetermined time is, for example, the usage time of the vehicle (4) requested by the debtor in the usage purpose information. Of course, as the predetermined time, it may also be the time obtained by multiplying the usage time of the vehicle (4) requested by the debtor in the usage purpose information by a coefficient. If the ECU (41) determines that the predetermined time has elapsed since the engine start lock was released (Step S610: "Yes"), the vehicle (4) proceeds to step S609. Conversely, if the ECU (41) determines that the predetermined time has not elapsed since the engine start lock was released (Step S610: "No"), the debt collection server (1) returns to step S606.

[0142] According to Embodiment 2 described above, just like Embodiment 1 described above, it is possible to achieve recovery of claims while preserving claims and to provide flexibility in the use of the vehicle.

[0143] Other embodiments

[0144] Additional effects or variations can be easily derived by those skilled in the art. Accordingly, broader aspects of the present invention are not limited to the specific details and representative embodiments shown and described above. Accordingly, various modifications are possible without departing from the spirit or scope of the overall concept of the invention as defined by the appended claims and their equivalents.

[0145] For example, in embodiments 1 and 2, the description was made based on the premise of a debt collection server (1) or a vehicle (4), but the debt management server (2) or the vehicle information server (3) itself may have the function of a control unit (11) or an ECU (41). In this case, the debt management server (2) or the vehicle information server (3) may have the function of a control unit (11) of the debt collection server (1) or a vehicle history DB (12). In addition, in the vehicle control device according to embodiments 1 and 2, the vehicle (4) may be responsible for a part of the processing of the debt collection server (1) or the vehicle information server (3).

[0146] In addition, in the embodiments of the present disclosure, the debt collection server (1), the debt management server (2), and the vehicle information server (3) are described as separate devices, but the debt collection server (1), the debt management server (2), and the vehicle information server (3) may be composed of one, two, or four or more devices.

Claims

Claim 1 A vehicle control device (1) comprising a processor, wherein the processor controls the engine start of the target vehicle (4) to lock in response to receiving a first signal indicating that payment of a debt to the target vehicle (4) has not been properly made from a debt management server (2) configured to manage debts of the target vehicle (4); acquires purpose of use information regarding the purpose of use of the target vehicle (4); determines whether the target vehicle (4) is being used for the purpose based on the purpose of use information, and if the target vehicle (4) is determined to be being used for the purpose, controls the engine start of the target vehicle (4) to unlock; acquires usage status information regarding the usage status of the target vehicle (4); determines whether the target vehicle (4) is being used for a purpose based on the usage status information and the purpose of use information; and if the target vehicle (4) is determined to be being used for a purpose other than the purpose, controls the engine start of the target vehicle (4) to lock again. Claim 2 A vehicle control device (1) comprising a processor, wherein the processor is configured to lock the engine start of the target vehicle (4) when it receives a first signal indicating that payment of a debt to the target vehicle (4) has not been properly made; to acquire usage purpose information regarding the purpose of use of the target vehicle (4); to determine whether the target vehicle (4) is being used for the purpose based on the usage purpose information; to unlock the engine start of the target vehicle (4) when it is determined that the target vehicle (4) is being used for the purpose; to acquire usage status information regarding the usage status of the target vehicle (4); to determine whether the target vehicle (4) is being used for a purpose other than the purpose based on the usage status information and the usage purpose information; and to re-lock the engine start of the target vehicle (4) when it is determined that the target vehicle (4) is being used for a purpose other than the purpose. Claim 3 In paragraph 2, the processor is configured to lock the engine start of the target vehicle (4) by outputting a lock signal to the immobilizer (42) equipped with the target vehicle (4) when it receives the first signal, the lock signal being a signal for remotely controlling the engine start of the target vehicle (4), and when it is determined that the target vehicle (4) is being used for its intended purpose, it is configured to unlock the engine start of the target vehicle (4) by outputting a release signal to the immobilizer (42), the release signal being a signal for remotely controlling the engine start of the target vehicle (4), and when it is determined that the target vehicle (4) is being used for purposes other than its intended purpose, it is configured to re-lock the engine start of the target vehicle (4) by outputting the lock signal to the immobilizer (42). Claim 4 In paragraph 2, the vehicle control device (1) is configured to release the engine start lock when the processor receives a second signal indicating permission for temporary use of the target vehicle (4) based on the purpose of use information. Claim 5 In claim 3 or 4, the processor acquires first identification information for identifying the terminal device (5) that is emitted by the terminal device (5) present in the target vehicle (4) as usage status information - the first identification information is detected by a detection unit (44) provided by the target vehicle (4) -; acquires second identification information for identifying a predetermined information processing terminal from a memory (40) provided by the target vehicle (4); and if the first identification information and the second identification information do not match, the vehicle control device (1) is configured to determine that the target vehicle (4) is being used for purposes other than the intended purpose. Claim 6 A vehicle control device (1) configured such that, in claim 3 or 4, the processor acquires still image data or moving image data captured by an imaging device (45) equipped with the target vehicle (4) as usage situation information, extracts a first feature quantity representing the facial features of a person included in the still image data or the moving image data, acquires a second feature quantity representing a predetermined facial feature from a memory (40) equipped with the target vehicle (4), and determines that the target vehicle (4) is being used for purposes other than the intended purpose when the degree of agreement between the first feature quantity and the second feature quantity is less than a predetermined value. Claim 7 A vehicle control device (1) configured such that, in paragraph 3 or 4, the processor acquires the weight of a passenger inside the target vehicle (4) measured by a weight sensor (47) provided by the target vehicle (4) as usage situation information, acquires weight information of a predetermined person from a memory (40) provided by the target vehicle (4), and if the difference between the acquired weight and the weight information is greater than or equal to a predetermined value, the target vehicle (4) is determined to be used for purposes other than the intended purpose. Claim 8 A vehicle control device (1), wherein, in paragraph 3 or 4, the purpose of use information includes a predetermined destination, and the processor acquires still image data or moving image data captured by an imaging device (45) equipped with the target vehicle (4) as the purpose of use information, extracts either text or buildings included in the still image corresponding to the still image data or the moving image corresponding to the moving image data as an extraction result, determines whether the target vehicle (4) is moving to the destination based on the extraction result and at least one of the destinations included in the purpose of use information, and if it is determined that the target vehicle (4) is not moving to the destination, determines that the target vehicle (4) is being used for purposes other than the purpose of use. Claim 9 A vehicle control device (1) configured such that, in paragraph 3 or 4, the purpose of use information includes a facility at a predetermined destination, the processor acquires still image data or moving image data captured by an imaging device (45) equipped with the target vehicle (4) as the purpose of use information, extracts either a facility or text included in a still image corresponding to the still image data or a moving image corresponding to the moving image data as an extraction result, and when the target vehicle (4) arrives at the destination, determines whether the target vehicle (4) has entered the facility based on the extraction result and the facility at the destination, and when it is determined that the target vehicle (4) has not entered the facility, determines that the target vehicle (4) is being used for purposes other than the purpose. Claim 10 A vehicle control device (1) configured such that, in paragraph 3 or 4, the processor acquires the weight measured by the weight sensor (47) provided by the target vehicle (4) as the usage situation information, and if the weight is greater than or equal to a predetermined threshold, the target vehicle (4) is determined to be used for purposes other than the intended purpose. Claim 11 A vehicle control device (1) configured such that, in paragraph 3 or 4, the purpose of use information includes a predetermined destination, and the processor acquires location information of the target vehicle (4) positioned by a positioning sensor equipped with the target vehicle (4) as the usage situation information, and based on the location information and the destination included in the purpose of use information, if the target vehicle (4) moves away from the destination and a predetermined time elapses, the target vehicle (4) is determined to be used for purposes other than the said purpose. Claim 12 A vehicle control device (1) wherein, in paragraph 3 or 4, the above usage purpose information includes a predetermined usage time, and the processor is configured to determine that the target vehicle (4) is being used for purposes other than intended when the usage time of the target vehicle (4) exceeds the predetermined usage time.

Images