Vehicle control device

Abstract

The invention relates to a vehicle control apparatus. A vehicle control device includes a processor. The processor is configured to acquire vehicle state information indicating a plurality of states of a target vehicle for which engine locking is to be enabled, and is configured to determine a state of the target vehicle based on the vehicle state information by comparing the state of the target vehicle one by one with respective corresponding conditions in a predetermined sequence, and configured to enable engine lock-up in the target vehicle when the states satisfy the corresponding conditions in a predetermined order, respectively.

Description

TECHNICAL FIELD

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

[0002] Japanese Patent No. 6647509 (JP 6647509 B) discloses a technology in which a person or a company staff other than a user of a vehicle (e.g., a vehicle holder, etc.) performs engine immobilization for the reason of protecting accounts receivable or safety. In order to ensure the safety of the user, the engine immobilization is such that the condition for enabling the engine immobilization is also, for example, that the current position of the vehicle is at a certain location, the vehicle is not traveling, etc. SUMMARY

[0003] However, for example, with the technology disclosed in JP 6647509 B, it is difficult to accurately determine whether or not the vehicle is not being used and then perform engine immobilization, and there is room for improvement in ensuring the safety of the user.

[0004] The present disclosure has been made in view of the foregoing, and provides a vehicle control device that can enable engine immobilization while ensuring the safety of a user of a vehicle.

[0005] The vehicle control device according to the first aspect of the present disclosure includes a processor, and the processor is configured to: acquire vehicle state information indicating a plurality of states of a target vehicle to be enabled with engine immobilization; determine a state of the target vehicle based on the vehicle state information by comparing the plurality of states of the target vehicle with respective corresponding conditions one after another in a predetermined order; and enable the engine immobilization in the target vehicle when the plurality of states satisfy the plurality of conditions, respectively, in the predetermined order.

[0006] In the vehicle control device according to the first aspect of the present disclosure, the plurality of states can be at least two of a state of the target vehicle in which an ignition is off, a state in which a time elapsed since the ignition of the target vehicle entered an off state is a predetermined period of time or more, a state of illumination of a light included in the target vehicle, a state of charging of the target vehicle, and a state in which a smart key configured to lock and unlock the target vehicle is inside or outside the target vehicle.

[0007] In the vehicle control device according to the first aspect of the present disclosure, the determining of the state of the target vehicle by comparing the state of the target vehicle with the respective corresponding conditions one after another in the predetermined order can include a process of comparing the state of the target vehicle with at least two conditions of a plurality of conditions corresponding to the state one after another in the predetermined order, the plurality of conditions including a condition of whether an ignition of the target vehicle is in an off state, a condition of whether a state of elapsed time since the ignition of the target vehicle entered the off state is a predetermined time period or more, a condition of whether an illumination state of a light included in the target vehicle is an off state, a condition of whether a charging state of the target vehicle is a state of being charged, and a condition of whether a smart key configured to lock and unlock the target vehicle is in a state of being outside the target vehicle.

[0008] In the vehicle control device according to the first aspect of the present disclosure, the corresponding conditions can include a first condition, a second condition, a third condition, and a fourth condition, the determining of the state of the target vehicle by comparing the state of the target vehicle with the respective corresponding conditions one after another in the predetermined order can include a process of comparing the state of the target vehicle with the corresponding conditions in an order of the first condition to the fourth condition as long as a preceding condition of the corresponding conditions is satisfied, the first condition can be a condition of whether the ignition of the target vehicle is in the off state, the second condition can be a condition of whether the state of the elapsed time since the ignition of the target vehicle entered the off state is the predetermined time period or more, the third condition can be a condition of whether the illumination state of the light included in the target vehicle is the off state, and the fourth condition can be a condition of whether the smart key configured to lock and unlock the target vehicle is in the state of being outside the target vehicle.

[0009] In the vehicle control device according to the first aspect of the present disclosure, the target vehicle can be any one of a BEV and a PHEV. The corresponding conditions can include a first condition, a second condition, a third condition, a fourth condition, and a fifth condition, the determining of the state of the target vehicle by comparing the state of the target vehicle with the respective corresponding conditions one after another in the predetermined order can include a process of comparing the state of the target vehicle with the corresponding conditions in an order of the first condition to the fifth condition as long as a preceding condition of the corresponding conditions is satisfied, the first condition can be a condition of whether the ignition of the target vehicle is in the off state, the second condition can be a condition of whether the state of the elapsed time since the ignition of the target vehicle entered the off state is the predetermined time period or more, the third condition can be a condition of whether the illumination state of the light included in the target vehicle is the off state, the fourth condition can be a condition of whether the charging state of the target vehicle is the state of being charged, and the fifth condition can be a condition of whether the smart key configured to lock and unlock the target vehicle is in the state of being outside the target vehicle.

[0010] In the vehicle control device according to the first aspect of the present disclosure, the processor can be configured to terminate the determination when one of the conditions is not satisfied.

[0011] The present disclosure brings about the advantageous effect that the engine lockup can be enabled while ensuring the safety of the user of the vehicle. BRIEF DESCRIPTION OF DRAWINGS

[0012] Features, advantages, and technical and industrial significance of exemplary embodiments of the present application will be described below with reference to the accompanying drawings, wherein the same reference numerals denote the same elements, and wherein:

[0013] Figure 1 is a block diagram showing a schematic configuration of a vehicle control system according to an embodiment;

[0014] Figure 2 is a sequence diagram showing an example of information exchange between an accounts receivable recovery server, a vehicle information server, and a vehicle included in the vehicle control system according to the embodiment;

[0015] Figure 3 is a flowchart showing an outline of processing performed by the accounts receivable recovery server according to the embodiment;

[0016] Figure 4 is a flowchart showing an outline of processing performed by the vehicle information server according to the embodiment when vehicle state information is transmitted to the accounts receivable recovery server 1;

[0017] Figure 5 is a flowchart showing an outline of processing performed by the vehicle information server according to the embodiment when engine lockup in the vehicle 4 is to be enabled.

[0018] Figure 6 is a flowchart showing an outline of processing performed by the vehicle according to the embodiment when vehicle state information is transmitted to the vehicle information server 3; and

[0019] Figure 7 is a flowchart showing an outline of processing performed by the vehicle according to the embodiment when engine lockup is enabled. DETAILED DESCRIPTION

[0020] Hereinafter, a vehicle control device according to an embodiment of the present disclosure will be described with reference to the accompanying drawings. Note that the constituent elements in the following embodiment include those which a person skilled in the art can easily replace with the constituent elements, or those which are substantially the same as the constituent elements.

[0021] Vehicle control system

[0022] Figure 1 This is a block diagram illustrating a schematic configuration of a vehicle control system according to an implementation scheme. Figure 1 The vehicle control system shown includes an accounts receivable collection server 1, an accounts receivable management server 2, a vehicle information server 3, and a vehicle 4. Each of these servers includes communication capabilities and is configured to communicate with and exchange various information with each other via a network N. For example, network N may include a public line network, such as an internet line network or a mobile phone line network. In the vehicle control system according to the embodiment, the accounts receivable collection server 1 serves as a vehicle control device for controlling actions (particularly engine lock-up) in the vehicle 4.

[0023] Accounts receivable collection server

[0024] First, the functional configuration of accounts receivable collection server 1 is described.

[0025] Accounts receivable collection server 1 remotely controls vehicle 4 to collect accounts receivable related to vehicle 4. In the implementation scheme, examples of "accounts receivable" include accounts receivable related to installment payment contracts signed at the time of purchase of the vehicle, accounts receivable related to long-term lease agreements for vehicle 4, accounts receivable related to subscription agreements for vehicle 4, accounts receivable related to short-term lease agreements for vehicle 4, etc.

[0026] In this implementation plan, the creditor is, for example, the holder (owner) of vehicle 4. Specifically, examples of creditors include dealers, credit companies, banks, etc., that have already sold vehicle 4. The debtor in this implementation plan is, for example, the user of vehicle 4. Specifically, examples of debtors include the purchaser of vehicle 4, individuals or businesses that have entered into lease agreements, etc.

[0027] like Figure 1 As shown, the accounts receivable collection server 1 includes a control unit 11, a vehicle history database 12, a display device 13, an input device 14, and a communication unit 15.

[0028] The control unit 11 is implemented, for example, by a processor including a central processing unit (CPU) and a memory (main storage unit) including random access memory (RAM), read-only memory (ROM), etc. When the vehicle 4 meets the predetermined requirements for engine locking (hereinafter referred to as "engine locking requirements"), the control unit 11 obtains predetermined information from the vehicle history DB 12 or the vehicle information server 3, determines whether to enable engine locking based on the information, and enables engine locking in the vehicle 4 according to the determined result.

[0029] Examples of the "engine immobilization request" include a case where the user of the vehicle 4 is in a state of debt default (delayed payment) or the like. Determination of whether or not the engine immobilization request is satisfied is performed by, for example, the receivables recovery server 1. When there is a vehicle 4 (target vehicle) that satisfies the engine immobilization request, information for identifying the vehicle 4 (for example, a vehicle identification number (VIN) or the like) is transmitted from the receivables management server 2 to the receivables recovery server 1.

[0030] Specifically, the control unit 11 receives, from the vehicle 4 (target vehicle) via the vehicle information server 3, vehicle state information indicating a plurality of states of the vehicle 4 (target vehicle) in which the engine immobilization can be enabled. Subsequently, based on the vehicle state information about the vehicle 4 (target vehicle), the control unit 11 determines the state of the vehicle 4 by comparing the state of the vehicle 4 with the respective corresponding conditions one after another in a predetermined order. When the plurality of states of the vehicle 4 satisfy the corresponding conditions respectively in the predetermined order, the control unit 11 transmits, to the vehicle 4 via the vehicle information server 3, an engine immobilization enable request for enabling the engine immobilization in the vehicle 4.

[0031] Here, the state is at least two of the following states: a state of the ignition of the vehicle 4, a state in which the time elapsed since the ignition of the vehicle 4 entered an off state (IG-OFF state) is a predetermined period of time or more (for example, five minutes or more), a state of the illumination of a light included in the vehicle 4, a state of the charging of the vehicle 4, and a state of an intelligent key that locks and unlocks the vehicle 4 being inside or outside the vehicle 4.

[0032] For example, when the control unit 11 determines the state of the vehicle 4 by comparing the state of the vehicle 4 with each of the corresponding conditions in the predetermined order one after another, the control unit 11 performs the determination by comparing the state of the vehicle 4 with at least two of the following corresponding conditions in the predetermined order one after another: whether the ignition of the vehicle 4 is in the off state, whether the state in which the time elapsed since the ignition of the vehicle 4 entered the off state is a predetermined time period or more is established, whether the lighting state of the light included in the vehicle 4 is the off state, whether the charging state of the vehicle 4 is the state of being charged, and whether the smart key that locks and unlocks the vehicle 4 is in the state of being outside the vehicle 4. For example, as long as each of the conditions (1), (2), (3), (4), (5) is satisfied, the control unit 11 performs the determination by comparing each of the following conditions in the order of (1), (2), (3), (4), (5) described above: (1) whether the ignition of the vehicle 4 is in the off state, (2) whether the state in which the time elapsed since the ignition of the vehicle 4 entered the off state is a predetermined time period or more is established, (3) whether the lighting state of the light included in the vehicle 4 is the off state, (4) whether the charging state of the vehicle 4 is the state of being charged, and (5) whether the smart key that locks and unlocks the vehicle 4 is in the state of being outside the vehicle 4. In other words, the predetermined order is the order of (1), (2), (3), (4), (5) described above. Note that in this embodiment, not all of the conditions (1), (2), (3), (4), (5) need to be satisfied, and the state in which at least two of the conditions are satisfied can be sufficient.

[0033] As described above, the receivables recovery server 1 acquires predetermined information from the vehicle history DB 12 or the vehicle information server 3, determines whether to enable the engine lock based on the information, and remotely enables the engine lock in the vehicle 4 according to the result of the determination. Thus, it is possible to more securely determine the enablement of the engine lock in the vehicle 4. Note that when the engine lock in the vehicle 4 (target vehicle) is to be enabled, the control unit 11 can display information related to the vehicle 4 (target vehicle) on the display device 13, and in response to an instruction signal according to an operation input to the input device 14 by an operator who operates the receivables recovery server 1, can transmit an engine lock enablement request to the vehicle 4 to enable the engine lock. Thus, seeking a final determination on the enablement of the engine lock from the operator enables the operator to give advance notice of the enablement of the engine lock to the debt person of the vehicle 4.

[0034] The vehicle history DB 12 is a database configured by using a hard disk drive (HDD), a solid state drive (SSD), or the like, and accumulates various information related to the vehicle 4. For example, the vehicle history DB 12 acquires vehicle state information from the vehicle information server 3, and accumulates the vehicle state information associated with a vehicle identification number (VIN) or the like. The vehicle history DB 12 creates frequent parking location information based on the vehicle state information accumulated in the vehicle history DB 12.

[0035] The display device 13 is implemented by, for example, a liquid crystal display (LCD), an organic electroluminescence display (OLED), or the like. The display device 13 displays various information under the control of the control unit 11.

[0036] The input device 14 is implemented by, for example, a touch panel, a keyboard, a pointing device, or the like. The input device 14 receives input of various operations by a user, and outputs a signal to the control unit 11 in accordance with the received operation.

[0037] The communication unit 15 is configured by using, for example, a local area network (LAN) interface board, a wireless communication circuit for wireless communication, or the like. The communication unit 15 performs information exchange with the receivables management server 2 and the vehicle information server 3 through communication over the network N under the control of the control unit 11.

[0038] Receivables Management Server

[0039] Next, the functional configuration of the receivables management server 2 will be described.

[0040] The receivables management server 2 is a server for managing receivables related to the vehicle 4. The receivables management server 2 includes a receivables management system 21, a receivables management DB 22, and a communication unit 23.

[0041] Among the plurality of vehicles 4 managed in the receivables management DB 22, when there is a vehicle 4 (target vehicle) that satisfies the engine immobilization requirement, the receivables management system 21 transmits information for identifying the vehicle 4 (for example, a vehicle identification number (VIN) or the like) to the receivables recovery server 1.

[0042] The receivables management DB 22 manages information for identifying each vehicle 4 and information related to receivables from the vehicle 4 in association with each other. Here, the information for identifying each vehicle 4 is, for example, a vehicle identification number (VIN) or the like. The information related to receivables from the vehicle 4 includes, for example, loan receivables, lease receivables, and the like.

[0043] The communication unit 23 is constituted by using, for example, a LAN interface board, a wireless communication circuit for wireless communication, or the like. The communication unit 23 performs information exchange with the accounts receivable recovery server 1 through communication via the network N.

[0044] Vehicle information server

[0045] Next, the functional configuration of the vehicle information server 3 will be described.

[0046] The vehicle information server 3 is a server that acquires vehicle state information from the vehicle 4 according to a request from the accounts receivable recovery server 1 and transmits the acquired vehicle state information to the accounts receivable recovery server 1. The vehicle information server 3 includes a control unit 31, a vehicle information DB 32, and a communication unit 33.

[0047] The control unit 31 is realized by, for example, a processor including a CPU or the like and a memory (main storage unit) including a RAM, a ROM, or the like. The control unit 31 acquires vehicle state information from the vehicle 4 according to a request from the accounts receivable recovery server 1 and transmits the acquired vehicle state information to the accounts receivable recovery server 1.

[0048] The vehicle information DB 32 accumulates vehicle state information acquired from the vehicle 4 (target vehicle) and information for identifying the vehicle 4 (for example, a vehicle identification number (VIN), or the like) in association with each other. The vehicle information DB 32 transmits vehicle state information to the accounts receivable recovery server 1 according to a request from the accounts receivable recovery server 1.

[0049] The communication unit 33 is constituted by using, for example, a LAN interface board, a wireless communication circuit for wireless communication, or the like. The communication unit 33 performs information exchange with the accounts receivable recovery server 1, the accounts receivable management server 2, and the vehicle 4 through communication via the network N.

[0050] Vehicle

[0051] Next, the functional configuration of the vehicle 4 will be described.

[0052] For example, the vehicle 4 is a general-purpose engine vehicle (conventional vehicle), a hybrid electric vehicle (HEV), a plug-in hybrid electric vehicle (PHEV), or the like. For example, the vehicle 4 can be a fuel cell electric vehicle (FCEV), a battery electric vehicle (BEV), or the like. The vehicle 4 includes an ECU 41, a lockup system 42, a positioning unit 43, a detection unit 44, and a communication unit 45.

[0053] The ECU 41 is an electronic control unit that includes a microcomputer including, for example, a CPU, a ROM, a RAM, and the like as main components. The ECU 41 transmits vehicle state information to the vehicle information server 3 in accordance with a request from the receivables recovery server 1 via the vehicle information server 3. The ECU 41 acquires vehicle state information about the vehicle 4 that is individually detected by the positioning unit 43 and the detection unit 44, and transmits the vehicle state information to the receivables recovery server 1 via the vehicle information server 3. Further, the ECU 41 enables engine lock in the vehicle 4 in response to an instruction signal indicating the enablement of engine lock that is transmitted from the receivables recovery server 1 via the vehicle information server 3. In other words, even if the debtor presses the ignition switch to start the engine of the vehicle 4, the ECU 41 does not start the engine of the vehicle 4. In this case, the ECU 41 can cause a monitor not depicted to display information indicating that engine lock has been enabled due to delayed payment of the debt, or display contact information about the creditor.

[0054] The lock system 42 performs enablement of engine lock or release of the enabled engine lock based on control by the vehicle information server 3.

[0055] The positioning unit 43 detects the current position of the vehicle 4, for example, by receiving radio waves from Global Positioning System (GPS) satellites. Note that the method for detecting the current position of the vehicle 4 is not limited to the method using GPS satellites, and, for example, a method that combines a Light Detection and Ranging system or a Light Imaging Detection and Ranging system (LiDAR) and a 3D map, or the like can be used.

[0056] The detection unit 44 detects the state of the ignition switch included in the vehicle 4, detects the time elapsed since the ignition entered an off state, detects the lighting state of the lights included in the vehicle 4, detects the charge state of the vehicle 4, detects the smart key that locks and unlocks the vehicle 4, and detects whether the smart key is outside or inside the vehicle 4. The detection unit 44 is constituted by using a timer, a voltage sensor, a current sensor, an on-off switch detection sensor, a wireless receiver, and the like.

[0057] The communication unit 45 is constituted by using, for example, a Data Communication Module (DCM) or the like. The communication unit 45 performs information exchange with the vehicle information server 3 through communication via the network N.

[0058] Information exchange between receivables recovery server, vehicle information server, and vehicle

[0059] Next, information exchange between the receivables recovery server 1, the vehicle information server 3, and the vehicle 4 is described. Figure 2is a sequence diagram showing an example of information exchange between the receivables recovery server 1, the vehicle information server 3, and the vehicle 4. Note that, in the following processing, a description is given, as an example, regarding processing performed by the vehicle 4 used by a debtor who is in arrears, among a plurality of vehicles 4.

[0060] As shown in Figure 2 , first, the control unit 11 of the receivables recovery server 1 requests the vehicle information server 3 for vehicle state information, for example, at regular intervals (step S1). Subsequently, based on the request for vehicle state information received from the receivables recovery server 1, the vehicle information server 3 requests the vehicle 4 for vehicle state information (step S2). In response thereto, the vehicle 4 transmits vehicle state information detected by the positioning unit 43 and the detection unit 44 to the vehicle information server 3 (step S3). Subsequently, the vehicle information server 3 transmits the vehicle state information received from the vehicle 4 to the receivables recovery server 1 (step S4). In this case, the receivables recovery server 1 accumulates, in the vehicle history DB 12, vehicle state information regarding the vehicle 4 received from the vehicle information server 3 in association with the vehicle identification number (VIN) of the vehicle 4.

[0061] Further, when a plurality of states included in the vehicle state information regarding the target vehicle 4 satisfy respective corresponding conditions (to be described later) one after another in a predetermined order, the control unit 11 of the receivables recovery server 1 triggered by the fact that the engine lock request is satisfied issues a request for execution of engine lock to the vehicle information server 3 (step S5). Subsequently, based on the request for execution of engine lock received from the receivables recovery server 1, the vehicle information server 3 issues a request for execution of engine lock to the vehicle 4 (step S6). In response thereto, the vehicle 4 executes engine lock, and gives a response indicating a success state of engine lock to the vehicle information server 3 (step S7). Thereafter, the vehicle information server 3 transmits the response indicating the success state of lock received from the vehicle 4 to the receivables recovery server 1 (step S8). In this case, the receivables recovery server 1 accumulates, in the vehicle history DB 12, the success state of lock of the vehicle 4 received from the vehicle information server 3 in association with the vehicle identification number (VIN) of the vehicle 4.

[0062] Processing by the receivables recovery server

[0063] Next, the processing performed by the receivables recovery server 1 is described. Figure 3 is a flowchart showing an outline of the processing performed by the receivables recovery server 1.

[0064] As shown in Figure 3As shown, the control unit 11 requests vehicle state information about the vehicle 4 via the vehicle information server 3 (step S101), and acquires the vehicle state information transmitted from the vehicle 4 (step S102).

[0065] Next, the control unit 11 compares a plurality of states included in the vehicle state information about the vehicle 4 with respective corresponding conditions in a predetermined order one after another (step S103). Specifically, the control unit 11 determines (1) whether the ignition of the vehicle 4 is in an off state (first condition), (2) whether a state in which a time elapsed since the ignition of the vehicle 4 entered the off state is a predetermined time period or more is maintained (second condition), (3) whether an illumination state of a light included in the vehicle 4 is an off state (third condition), and (4) whether a smart key that locks and unlocks the vehicle 4 is in a state of being outside the vehicle 4 (fourth condition), by comparing the states of the target vehicle with the corresponding conditions in the order of (1), (2), (3), and (4) above, as long as each preceding condition is satisfied. In other words, the corresponding conditions can include the first condition to the fourth condition. The determination of the states of the target vehicle by comparing the states of the target vehicle with the corresponding conditions in a predetermined order one after another can include a process of comparing the states of the target vehicle with the corresponding conditions in the order of the first condition to the fourth condition, as long as the preceding corresponding condition is satisfied. Note that, when the vehicle 4 is a BEV or a PHEV, the control unit 11 determines (1) whether the ignition of the vehicle 4 is in an off state (first condition), (2) whether a state in which a time elapsed since the ignition of the vehicle 4 entered the off state is a predetermined time period or more is maintained (second condition), (3) whether an illumination state of a light included in the vehicle 4 is an off state (third condition), (4) whether a charging state of the vehicle 4 is a state of being charged (fourth condition), and (5) whether a smart key that locks and unlocks the vehicle 4 is in a state of being outside the vehicle 4 (fifth condition), by comparing the states of the target vehicle with the corresponding conditions in the order of (1), (2), (3), (4), and (5) above, as long as each preceding condition is satisfied. In other words, the corresponding conditions can include the first condition to the fifth condition. The determination of the states of the target vehicle by comparing the states of the target vehicle with the corresponding conditions in a predetermined order one after another can include a process of comparing the states of the target vehicle with the corresponding conditions in the order of the first condition to the fifth condition, as long as the preceding corresponding condition is satisfied.

[0066] Thereafter, the control unit 11 determines whether the states included in the vehicle state information of the vehicle 4 satisfy all the corresponding conditions in the predetermined order, respectively (step S104). When the states included in the vehicle state information of the vehicle 4 satisfy all the corresponding conditions in the predetermined order, respectively (step S104: YES), the control unit 11 permits the activation of the engine lockup in the vehicle 4 (step S105), and requests the activation of the engine lockup in the vehicle 4 to the vehicle 4 via the vehicle information server 3 (step S107). Thus, the engine lockup activation request is transmitted from the vehicle information server 3 to the lockup system 42 of the vehicle 4.

[0067] Subsequently, the control unit 11 determines whether a response indicating the engine lockup success state is received from the vehicle 4 via the vehicle information server 3 (step S108). When the response indicating the engine lockup success state is received from the vehicle 4 via the vehicle information server 3 (step S108: YES), the control unit 11 terminates the current processing. In contrast, when the response indicating the engine lockup success state is not received from the vehicle 4 via the vehicle information server 3 (step S108: NO), the control unit 11 returns to step S101. Note that examples of the case where the activation of the engine lockup fails include a case where the engine lockup activation request cannot be transmitted from the vehicle information server 3 to the lockup system 42 of the vehicle 4 due to poor communication or the like, a case where a failure occurs in the lockup system 42 of the vehicle 4, a case where the vehicle state information regarding the vehicle 4 changes immediately after the engine lockup activation request is made, and the like.

[0068] In step S104, if the states included in the vehicle state information regarding the vehicle 4 do not satisfy the respective corresponding conditions in the predetermined order, one after another (step S104: NO), the control unit 11 prohibits the activation of the engine lockup in the vehicle 4 (step S106). Thus, at the time when the states included in the vehicle state information of the vehicle 4 do not satisfy the corresponding conditions in the predetermined order, respectively, the control unit 11 ends the determination, whereby it is possible to reduce the processing throughput and the communication load. Further, the control unit 11 can more securely perform the determination of the activation of the engine lockup in the vehicle 4. After step S106, the control unit 11 returns to step S101.

[0069] Processing 1 of vehicle information server

[0070] Next, a description is given of an outline of the processing performed by the vehicle information server 3 when the vehicle state information is transmitted to the receivables recovery server 1. Figure 4 is a flowchart illustrating an outline of the processing performed by the vehicle information server 3 when the vehicle state information is transmitted to the receivables recovery server 1.

[0071] As Figure 4As shown, firstly, the control unit 31 receives a request for vehicle status information from the accounts receivable collection server 1 (step S201), and sends the received request for vehicle status information to the vehicle 4 (step S202).

[0072] Subsequently, the control unit 31 obtains vehicle status information from the vehicle 4 (step S203), sends the vehicle status information obtained from the vehicle 4 to the accounts receivable collection server 1 (step S204), and completes the current processing.

[0073] Vehicle Information Server Processing 2

[0074] Next, a summary description of the processes performed by the vehicle information server 3 when engine lock-up in vehicle 4 is to be enabled is given. Figure 5 This is a flowchart illustrating a summary of the processes performed by the vehicle information server 3 when engine lock-up in vehicle 4 is to be enabled.

[0075] like Figure 5 As shown, firstly, the control unit 31 receives a request to enable engine lock from the accounts receivable collection server 1 (step S301), and sends the request to enable engine lock received from the accounts receivable collection server 1 to the vehicle 4 (step S302).

[0076] Next, the control unit 31 receives information from the vehicle 4 regarding whether the engine lock-up was successfully or unsuccessfully activated (step S303), sends the information received from the vehicle 4 regarding whether the engine lock-up was successfully or unsuccessfully activated to the accounts receivable collection server 1 (step S304), and ends the process.

[0077] Vehicle handling 1

[0078] Next, a description of the processing performed by vehicle 4 when vehicle status information is sent to vehicle information server 3 is given. Figure 6 This is a flowchart illustrating the outline of the processes performed by vehicle 4 when vehicle status information is sent to vehicle information server 3.

[0079] like Figure 6 As shown, firstly, ECU 41 receives a request for vehicle status information from vehicle information server 3 (step S401), and obtains vehicle status information about vehicle 4 from positioning unit 43 and detection unit 44 (step S402). Subsequently, ECU 41 sends the vehicle status information about vehicle 4 to vehicle information server 3 (step S403) and completes the current processing.

[0080] Vehicle handling 2

[0081] Next, a summary description of the processes performed by vehicle 4 when engine lock is engaged is given. Figure 7is a flowchart showing an outline of processing performed by the vehicle 4 when the engine lock is enabled.

[0082] As shown in Figure 7 first, the ECU 41 receives a request to enable the engine lock from the vehicle information server 3 (step S501). The engine lock is enabled by control of the lock system 42 (step S502). Subsequently, the ECU 41 determines whether or not the enablement of the engine lock is successful, for example, on the basis of the action state of the lock system 42, transmits information on success or failure of the enablement of the engine lock to the vehicle information server 3 (step S503), and completes the current processing.

[0083] According to the above-described embodiment, the accounts receivable recovery server 1 acquires predetermined information from the vehicle history DB 12 or the vehicle information server 3, determines whether or not to enable the engine lock on the basis of the information, and remotely enables the engine lock in the vehicle 4 in accordance with the result of the determination. Thus, the engine lock in the vehicle 4 can be safely enabled.

[0084] Further, according to the embodiment, the accounts receivable recovery server 1 determines a plurality of states in a predetermined order when determining the state of the vehicle 4, and the determination is terminated when the condition is not satisfied. Thus, the processing and communication load can be reduced. In other words, the processor is configured to terminate the determination when one of the conditions is not satisfied.

[0085] More advantageous effects and modification examples can be easily derived by those skilled in the art. Therefore, the boundary aspects of the present disclosure are not limited to the specific details and typical embodiments as presented and described above. Thus, various changes can be made without departing from the spirit or scope of the overall concept of the present disclosure as defined by the appended claims and their equivalents.

[0086] For example, although the premise described in the embodiment is the accounts receivable recovery server 1, the vehicle 4 can be configured to have the function itself. In this case, the vehicle 4 can include the functions of the control unit 11 and the vehicle history DB 12 of the accounts receivable recovery server 1. In the vehicle control device according to the embodiment, the vehicle 4 can be configured to perform a part of the processing of the accounts receivable recovery server 1 or the vehicle information server 3.

[0087] For example, the premise described is assumed that the accounts receivable recovery server 1 is used as the vehicle control device in the embodiment, however, the vehicle 4 itself can be used as the vehicle control device. In this case, the vehicle 4 can include the functions of the control unit 11 and the vehicle history DB 12 of the accounts receivable recovery server 1. In the vehicle control device according to the embodiment, the vehicle 4 can be configured to perform a part of the processing of the accounts receivable recovery server 1 or the vehicle information server 3.

[0088] For example, all of the following (1) to (5) can be executed by the accounts receivable recovery server 1, or can be executed by the vehicle 4, or alternatively, (1) to (4) can be executed by the vehicle 4, and (5) can be executed by the accounts receivable recovery server 1.

[0089] (1) determining whether the ignition of the vehicle 4 is in an off state;

[0090] (2) determining whether a state in which the time elapsed since the ignition of the vehicle 4 entered the off state is a predetermined period of time or more remains;

[0091] (3) determining whether the lighting state of a light included in the vehicle 4 is an off state;

[0092] (4) determining whether the charging state of the vehicle 4 is a state of being charged;

[0093] (5) determining whether a smart key that locks and unlocks the vehicle 4 is in a state of being outside the vehicle 4.

[0094] Further, although the accounts receivable recovery server 1, the accounts receivable management server 2, and the vehicle information server 3 are described as each separate device in the embodiments, the accounts receivable recovery server 1, the accounts receivable management server 2, and the vehicle information server 3 can be configured as one device, or two or four or more devices.

Claims

1. A vehicle control device, characterized in that... Including processors, among which The processor is configured to: Obtain vehicle status information, which indicates multiple states of the target vehicle to be locked out. Based on the vehicle status information, the status of the target vehicle is determined by comparing the status of the target vehicle with its corresponding conditions one by one in a predetermined order. as well as When the states satisfy the conditions in the predetermined order, the engine lock in the target vehicle is activated.

2. The vehicle control device according to claim 1, characterized in that, The state is at least two of the following states: the ignition state of the target vehicle; a state in which time has elapsed since the ignition of the target vehicle entered the off state for a predetermined period of time or longer; the illumination state of the lights in the target vehicle; the charging state of the target vehicle; and the state of the smart key configured to lock and unlock the target vehicle inside or outside the target vehicle.

3. The vehicle control device according to claim 1, characterized in that, Determining the state of a target vehicle by comparing its state with its corresponding conditions one after another in the predetermined order includes a process of comparing the state of the target vehicle with at least two of a plurality of conditions corresponding to the state, the plurality of conditions including: Is the ignition of the target vehicle in the off state? Whether the time elapsed since the target vehicle's ignition entered the off state has remained a predetermined time period or a longer time period. Whether the lights in the target vehicle are in an off state. Whether the target vehicle is in a charging state, and Whether the smart key configured to lock and unlock the target vehicle is located outside the target vehicle.

4. The vehicle control device according to claim 1, characterized in that: The corresponding conditions include a first condition, a second condition, a third condition, and a fourth condition; Determining the state of a target vehicle by comparing its state with its corresponding conditions one after another in a predetermined order includes a process of comparing the state of the target vehicle with the corresponding conditions in the order of the first condition to the fourth condition, provided that the preceding corresponding condition is met. The first condition is whether the ignition of the target vehicle is in the off state; The second condition is whether the time elapsed since the ignition of the target vehicle entered the off state is a predetermined time period or a longer time period. The third condition includes whether the lights in the target vehicle are in an off state; and The fourth condition is whether the smart key configured to lock and unlock the target vehicle is located outside the target vehicle.

5. The vehicle control device according to claim 1, characterized in that: The target vehicle is either a BEV or a PHEV; The corresponding conditions include the first condition, the second condition, the third condition, the fourth condition, and the fifth condition; Determining the state of a target vehicle by comparing its state with its corresponding conditions one after another in a predetermined order includes a process of comparing the state of the target vehicle with the corresponding conditions in the order of the first condition to the fifth condition, provided that the preceding corresponding condition is met. The first condition is whether the ignition of the target vehicle is in the off state; The second condition is whether the time elapsed since the ignition of the target vehicle entered the off state is a predetermined time period or a longer time period. The third condition is whether the lighting status of the lights in the target vehicle is off. The fourth condition is whether the target vehicle is in a state of being charged. and The fifth condition is whether the smart key configured to lock and unlock the target vehicle is located outside the target vehicle.

6. The vehicle control device according to claim 1, characterized in that, The processor is configured to terminate the determination if one of the conditions is not met.

Images