Vehicle control device

Abstract

A vehicle control device is provided. The vehicle control device includes a processor that, in a case where a first signal indicating that a payment of a debt for a vehicle has not been properly made is received, restricts a portion of a function provided by the vehicle in accordance with the case where the first signal is received.

Description

Technical Field

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

[0002] Japanese Patent No. 7050844 discloses a technique for imposing restrictions related to vehicle operation based on repayment information related to loan repayment status. Summary of the Invention

[0003] However, creditors of long-term car leases and car loans are more interested in being repaid than in having their use of the vehicle restricted, and therefore will try to find ways to get debtors to repay their money smoothly.

[0004] However, the technology disclosed in Japanese Patent No. 7050844 is insufficient in urging debtors to repay their debts by simply issuing notices related to the repayment status of the loan and the delay in the loan, thus leaving room for improvement.

[0005] This disclosure was made in view of the above circumstances, and its purpose is to provide a vehicle control device that can urge a debtor to repay a debt.

[0006] The vehicle control device involved in this disclosure is a vehicle control device equipped with a processor, wherein the processor

[0007] Upon receiving a first signal from a debt management server that manages the debts of the target vehicle indicating that the repayment of the debts for the target vehicle has not been properly implemented, control is performed to reduce the charging speed of the target vehicle to a predetermined speed.

[0008] Furthermore, the vehicle control device involved in this disclosure is a vehicle control device equipped with a processor that, upon receiving a first signal indicating that the repayment of a debt to the target vehicle has not been properly implemented, restricts a portion of the charging function for the target vehicle.

[0009] According to this disclosure, it is possible to achieve the effect of urging debtors to repay their debts. Attached Figure Description

[0010] The features, advantages, and technical and industrial significance of exemplary embodiments of the present invention will now be described with reference to the accompanying drawings, wherein like symbols denote like elements, and wherein: Figure 1 This is a block diagram illustrating the general structure of the vehicle control system according to Embodiment 1 of this disclosure.

[0011] Figure 2This is a sequence diagram illustrating an example of the debt collection server, debt management server, vehicle information server, and information exchange between vehicles involved in Embodiment 1 of this disclosure.

[0012] Figure 3 A flowchart illustrating the outline of the processing performed by the debt collection server according to Embodiment 1 of this disclosure.

[0013] Figure 4 A flowchart illustrating the outline of the processing performed by the vehicle information server according to Embodiment 1 of this disclosure.

[0014] Figure 5 A flowchart illustrating an outline of the processes performed by the vehicle according to Embodiment 1 of this disclosure.

[0015] Figure 6 A flowchart illustrating the outline of the processing performed by the debt collection server according to Embodiment 2 of this disclosure. Detailed Implementation

[0016] Hereinafter, the vehicle control device according to embodiments of the present disclosure will be described with reference to the accompanying drawings. Furthermore, the structural elements in the following embodiments include elements that can be easily replaced by those skilled in the art or elements that are substantially the same.

[0017] Implementation Method 1 Vehicle control system Figure 1 This is a block diagram illustrating the general structure of the vehicle control system according to Embodiment 1. Figure 1 The vehicle control system 100 shown includes 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, debt management server 2, vehicle information server 3, vehicle 4, and terminal device 5 all have communication capabilities and are configured to communicate with each other and exchange various information through a network N. This network N may be, for example, a public line network such as the Internet or a mobile phone line network.

[0018] Furthermore, in Implementation 1, as "claims", for example, claims related to installment payment contracts at the time of vehicle purchase, claims related to long-term lease contracts for vehicle 4, claims related to subscription contracts for vehicle 4, and claims related to short-term rental contracts for vehicle 4 can be listed.

[0019] Furthermore, in Implementation 1, the creditor is, for example, the holder (owner) of vehicle 4. Specifically, creditors could include, for example, the dealer who sold vehicle 4, a credit sales company, and a bank. In addition, the debtor in Implementation 1 is, for example, the user of vehicle 4. Specifically, debtors could include, for example, the purchaser of vehicle 4, the signatory of a long-term lease agreement, or an operating company.

[0020] Functional structure of debt recovery server First, the functional structure of the debt collection server 1 will be explained. To collect debts related to vehicle 4, the debt collection server 1 remotely controls the actions of vehicle 4. For example... Figure 1 As shown, the debt collection server 1 includes a control unit 11, a vehicle history database (DB) 12, a display device 13, an input device 14, and a communication unit 15.

[0021] The control unit 11 is implemented, for example, by a processor consisting of a CPU (Central Processing Unit) and a memory (main storage unit) consisting of RAM (Random Access Memory) and ROM (Read Only Memory).

[0022] The vehicle history database DB12 is constructed using HDDs (Hard Disk Drives), SSDs (Solid State Drives), and other similar devices, and stores various information related to vehicle 4. For example, vehicle history DB12 obtains usage status information from vehicle information server 3, establishes a correspondence with the vehicle identification number (VIN), and stores it. Furthermore, vehicle history DB12 stores stable parking location information, generated based on location information periodically sent from vehicle 4, such as information related to the stable or daily parking or stationary positions of vehicle 4.

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

[0024] The input device 14 is implemented, for example, by a touch panel, keyboard, indicator device, etc. The input device 14 receives input from various operations performed by the user and outputs a signal corresponding to the received operation to the control unit 11.

[0025] The communication unit 15 is composed, for example, of a LAN (Local Area Network) interface board and a wireless communication circuit for wireless communication. Under the control of the control unit 11, the communication unit 15 exchanges information with the debt management server 2 and the vehicle information server 3 via communication through the network N.

[0026] Functional Structure of Debt Management Server Next, the functional structure of the debt management server 2 will be described. The debt management server 2 is used to manage the debts related to vehicle 4. The debt management server 2 includes a debt management system 21, a debt management database 22, and a communication unit 23.

[0027] When the debt management system 21 finds a vehicle 4 (the target vehicle) among the multiple vehicles 4 managed by the debt management DB 22 that meets the requirement of engine start-lock, it sends information used to identify that vehicle 4 (such as the vehicle identification number (VIN)) to the debt collection server 1. Here, the vehicle 4 (the target vehicle) that meets the engine start-lock requirement is a vehicle 4 (the target vehicle) that has experienced delays in repayment of a debtor's claim, a vehicle 4 (the target vehicle) that has not properly repaid its debt, or a vehicle 4 that has experienced non-performance of its debt or delays in performance of its debt.

[0028] The debt management DB22 establishes and manages a correspondence between information used to identify each vehicle 4 and information related to the debts owed to that vehicle 4. Here, the information used to identify each vehicle 4 includes, for example, the Vehicle Identification Number (VIN). Furthermore, the information related to the debts owed to that vehicle 4 includes, for example, repayment information indicating the repayment status of loan claims and lease claims.

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

[0030] Functional structure of vehicle information server Next, the functional structure of the vehicle information server 3 will be described. The vehicle information server 3 obtains usage status information from the vehicle 4 according to a request from the debt collection server 1, and sends the obtained usage status information to the debt collection server 1. The vehicle information server 3 includes a control unit 31, a vehicle information database 32, and a communication unit 33.

[0031] The control unit 31 is implemented, for example, by a processor consisting of a CPU or the like, and a memory (main storage unit) consisting of RAM, ROM or the like. The control unit 31 obtains usage status information from the vehicle 4 according to a request from the debt collection server 1, and sends the obtained usage status information to the debt collection server 1.

[0032] The vehicle information DB32 establishes a correspondence between the utilization status information obtained from vehicle 4 (the target vehicle) and the information used to identify vehicle 4 (such as the vehicle identification number (VIN)) and stores it. The vehicle information DB32 sends the utilization status information to the debt collection server 1 according to a request from the debt collection server 1 and under the control of the control unit 31.

[0033] The communication unit 33 is composed of, for example, a LAN interface board and a wireless communication circuit for wireless communication. The communication unit 33 exchanges information with the debt collection server 1, the debt management server 2, and the vehicle 4 via communication through the network N.

[0034] Vehicle functional structure Next, the functional structure of vehicle 4 will be explained. Vehicle 4 can be, for example, a conventional engine vehicle (CONV), a hybrid electric vehicle (HEV), or a plug-in hybrid electric vehicle (PHEV). Alternatively, vehicle 4 can also be, for example, a fuel cell electric vehicle (FCEV) or a battery electric vehicle (BEV).

[0035] Vehicle 4 includes a memory 40, an ECU 41, a car navigation system 42, a battery 43, a charging device 44, a detection device 45, a locking device 46, a display device 47, an input unit 48, and a communication unit 49.

[0036] The memory 40 records various information related to the vehicle 4, programs executed by the ECU 41, and two-dimensional (2D) or three-dimensional (3D) map information used by the vehicle navigation system 42. Furthermore, the memory 40 is constructed using an HDD or SSD, etc.

[0037] ECU41 is, for example, an electronic control unit (ECU) whose main structural component is a microcomputer consisting of a CPU, ROM, RAM, etc. When vehicle 4 meets the requirements for restricting a portion of the functions possessed by vehicle 4 (hereinafter referred to as "function lock-up requirements"), ECU41 receives predetermined information from vehicle information server 3 and restricts a portion of the functions possessed by vehicle 4 based on this information. Here, "function lock-up requirements" can be exemplified by situations such as the debtor of vehicle 4 defaulting on debts (e.g., delayed repayment). The determination of whether the function lock-up requirements are met is performed, for example, by debt management server 2. Furthermore, when there is a vehicle 4 (the object vehicle) that meets the function lock-up requirements, information used to identify vehicle 4 (e.g., vehicle identification number (VIN)) is sent from debt management server 2 to vehicle 4 via debt collection server 1 and vehicle information server 3. The object vehicle refers, for example, to the vehicle 4 that is the object of the debt. That is, when ECU41 receives a first signal (hereinafter referred to as "first signal") from vehicle information server 3 indicating that the repayment of debts to vehicle 4 (the object vehicle) has not been properly implemented, it restricts a portion of the functions of vehicle 4.

[0038] Furthermore, when the ECU41 receives a second signal indicating a predetermined condition, such as the debt of the vehicle 4 having been fulfilled, for the vehicle 4 whose functions have been locked, the restricted functions of the vehicle 4 will be released.

[0039] Furthermore, ECU41 restricts a portion of the functions of vehicle 4 until it receives a second signal (hereinafter referred to as the "second signal") from vehicle information server 3 indicating that the debt for vehicle 4 (the object vehicle) has been fulfilled. Additionally, in Embodiment 1, ECU41 functions as a processor for the vehicle control device.

[0040] The car navigation system 42 detects the current position of the vehicle 4, for example, by receiving radio waves from GPS (Global Positioning System) satellites. However, the method for detecting the current position of the vehicle 4 is not limited to methods utilizing GPS satellites. For example, it can also utilize methods that combine radar (LiDAR: Light Detection and Ranging, Laser Imaging Detection and Ranging) with two-dimensional or three-dimensional map information recorded in the memory 40.

[0041] The storage battery 43 is composed of a rechargeable nickel-metal hydride battery or a lithium-ion battery, etc. The storage battery 43 is a battery pack formed by electrically connecting multiple individual cells (battery cells) such as lithium-ion batteries in series. Furthermore, the storage battery 43 can be either a battery with a liquid electrolyte between the positive and negative terminals or an all-solid-state battery with a solid electrolyte. The storage battery 43 stores the electricity supplied from the charging device 44 and supplies electricity to various components constituting the vehicle 4, such as motors, via the charging device 44.

[0042] The charging device 44 is constructed using a socket into which a charging plug from an external charger (charging station) can be inserted, and an inverter electrically connected to the socket. The charging device 44 is also constructed using a power conversion device electrically connected to the battery 43, which performs power conversion to convert the DC power from the battery 43 into AC power to drive an electric motor or similar device. Under the control of the ECU 41, the charging device 44 supplies power from the external charger to the battery 43.

[0043] The detection device 45 detects the insertion status of the charging plug into the charging device 44 and outputs the detection result to the ECU 41. The detection device 45 is constructed using pressure sensors, electrical sensors, etc.

[0044] Under the control of ECU 41, locking device 46 prevents the charging plug from falling out of the socket by locking the charging plug inserted into the charging device 44. Locking device 46 is constructed using a spring that applies force toward the charging plug and a motor that controls the force applied by the spring.

[0045] The display device 47 is implemented, for example, by a liquid crystal display (LCD) or an organic OLED display, and is installed inside the vehicle 4, functioning as an in-vehicle display. The display device 47 displays various information under the control of the ECU 41.

[0046] The input unit 48 is implemented, for example, via a touch panel, keyboard, or indicator device. The input unit 48 receives input from various operations performed by the user and outputs a signal corresponding to the received operation to the ECU 41.

[0047] The communication unit 49 is configured, for example, by a DCM (Data Communication Module). The communication unit 49 exchanges information with the vehicle information server 3 via communication through the network N.

[0048] Terminal device Next, terminal device 5 will be described. Terminal device 5 is, for example, an information processing terminal such as a mobile phone. Terminal device 5 receives input from various operations performed by the debtor.

[0049] Information exchange among the various devices of the vehicle control system Next, the exchange of information between the debt collection server 1, the debt management server 2, the vehicle information server 3, and the vehicle 4 will be explained. Figure 2 This is a sequence diagram illustrating an example of information exchange between the debt collection server 1, the debt management server 2, the vehicle information server 3, and the vehicle 4. Furthermore, the following processing will be described using a case where the processing involves a vehicle 4 (the object vehicle) belonging to a debtor whose debt repayment has been delayed among multiple vehicles 4.

[0050] like Figure 2 As shown, firstly, upon receiving a first signal from the debt management server 2 (S1), the control unit 11 of the debt collection server 1 sends the first signal to the vehicle information server 3 (S2). Next, the vehicle information server 3 sends the first signal received from the debt collection server 1 to the vehicle 4 (S3). In response, the ECU 41 of the vehicle 4 restricts a portion of the charging function of the vehicle 4 and replies to the vehicle information server 3 with a success message indicating the function restriction of the vehicle 4 (S4). The content of the restriction on the portion of the vehicle 4's function implemented by the ECU 41 will be described later. Afterwards, the vehicle information server 3 receives the success message indicating the function restriction from the vehicle 4 and sends it back to the debt collection server 1 (S5). In this case, the debt collection server 1 establishes a correspondence between the success message indicating the function restriction of the vehicle 4 received from the vehicle information server 3 and the vehicle identification number (VIN) of the vehicle 4 and stores it in the vehicle history DB 12.

[0051] Next, upon receiving a second signal from the debt management server 2 (S6), the control unit 11 of the debt collection server 1 sends the second signal to the vehicle information server 3 (S7). The vehicle information server 3 then sends the second signal received from the debt collection server 1 to the vehicle 4 (S8). In response, the ECU 41 of the vehicle 4 removes a portion of the functional restrictions on the vehicle 4 and sends a response to the vehicle information server 3 regarding the removal of functional restrictions (S9). In this case, the debtor can utilize the vehicle 4 without any functional restrictions. The vehicle information server 3 then sends the response to the removal of functional restrictions received from the vehicle 4 to the debt collection server 1 (S10). In this case, the debt collection server 1 establishes a correspondence between the removal information received from the vehicle information server 3 and the vehicle identification number (VIN) of the vehicle 4 and stores it in the vehicle history DB 12.

[0052] Processing in the debt recovery server Next, the processing performed by debt collection server 1 will be explained. Figure 3 A flowchart illustrating the outline of the processes performed by debt collection server 1.

[0053] like Figure 3 As shown, upon receiving the first signal from the debt management server 2 (S101), the control unit 11 sends the first signal from the debt management server 2 to the vehicle information server 3 (S102). The control unit 11 then receives the success information regarding the functional limitation of the vehicle 4 from the vehicle information server 3 (S103).

[0054] Next, upon receiving the second signal from the debt management server 2 (S104), the control unit 11 sends the second signal to the vehicle information server 3 (S105) and receives the function restriction release information from the vehicle information server 3 (S106). After S106, the debt collection server 1 terminates this process.

[0055] Vehicle information server processing Next, a summary of the processing performed by the vehicle information server 3 will be provided. Figure 4 A flowchart illustrating the outline of the processes performed by the vehicle information server 3.

[0056] like Figure 4 As shown, firstly, the control unit 31 receives a first signal from the debt collection server 1 (S201) and sends the received first signal to the vehicle 4 (S202).

[0057] Next, the control unit 31 receives the success information of the function restriction of vehicle 4 from vehicle 4 (S203) and sends the received success information of the function restriction of vehicle 4 to the debt collection server 1 (S204).

[0058] Next, the control unit 31 receives a second signal from the debt collection server 1 (S205) and sends the received second signal to the vehicle 4 (S206).

[0059] Next, the control unit 31 receives the release information from the vehicle 4 (S207) and sends the received release information to the debt collection server 1 (S208). After S208, the vehicle information server 3 ends this process.

[0060] Vehicle handling Next, a summary of the processes performed by vehicle 4 will be provided. Figure 5 A flowchart illustrating the outline of the processes performed by vehicle 4.

[0061] like Figure 5 As shown, firstly, upon receiving a first signal from the vehicle information server 3 (S301: Yes), ECU41 restricts a portion of the charging function for vehicle 4 (S302). Specifically, ECU41 restricts at least the charging function of vehicle 4 as described in (1) to (5) below.

[0062] (1) In order to control part of the charging function of vehicle 4, ECU 41 controls the charging location and equipment that are pre-registered in the car navigation system 42. For example, ECU 41 restricts the charging to be performed only at the user's (debtor's) home, the facilities, equipment, workplace of the car dealer who sold vehicle 4, or the charging equipment installed by the creditor. In this case, ECU 41 determines whether the current location information of vehicle 4 detected by car navigation system 42 is the same as at least one of the pre-registered charging locations and equipment (hereinafter referred to as "registered location information"). Based on the determination result, if the current location information of vehicle 4 is different from the registered location information, ECU 41 restricts the user (debtor) from charging by controlling the operation of charging device 44 to be disconnected, for example, by disconnecting the switch connecting the socket to the inverter. In contrast, when the current location information of vehicle 4 matches the registered location information, ECU 41 controls the charging device 44 to be turned on, for example, by turning on the switch connecting the connector to the inverter. As a result, the user (debtor) can only charge at the registered charging locations and equipment, which becomes inconvenient. Consequently, the creditor can urge the user (debtor) to repay the debt.

[0063] (2) Furthermore, the ECU 41 controls the charging device 44 in such a way that the charging speed is reduced to a predetermined speed. Specifically, the ECU 41 controls the charging device 44 so that, for example, if the battery 43 can be fully charged in 14 hours, the charging speed is reduced by switching the switch inside the charging device 44, which is electrically connected to an external charger, on and off simultaneously, so that the battery can be fully charged in 28 hours. Of course, the ECU 41 may also control the charging device 44 in such a way that the charging speed is a predetermined speed, for example, zero.

[0064] (3) Furthermore, the ECU 41 controls the charging device 44 in such a way that the charging limit of the battery 43 is reduced to a predetermined limit. Specifically, the ECU 41 controls the charging device 44 in a manner that allows the battery 43 to be fully charged in 14 hours, for example, to charge for only 4 hours. Of course, in addition to controlling the charging time of the battery 43, the ECU 41 also controls the charging device 44 to reduce the upper limit of the charging rate of the battery 43 to a predetermined limit, for example, 50%.

[0065] (4) Furthermore, the ECU 41 controls the charging device 44 in such a way that charging does not begin when the charger plug is inserted into the vehicle 4's socket. Specifically, the ECU 41 controls the charging device 44, which electrically connects the vehicle 4's socket to the battery 43, to be in an off state, thereby preventing charging from starting when the charger plug is inserted into the vehicle 4's socket.

[0066] (5) Furthermore, the ECU 41 controls the locking device 46 in such a way that the charging plug cannot be unplugged from the charging device 44 until a fixed time has elapsed after the vehicle 4 has finished charging. Here, the fixed time is, for example, 5 minutes to 1 hour. As a result, even if the user (debtor) wants to use the vehicle 4 at the desired time, they must wait again until the charging plug can be unplugged, which becomes inconvenient. As a result, the creditor can urge the debtor to repay the debt.

[0067] Thus, ECU41 restricts at least one of the functions in (1) to (5) above. As a result, it can urge the debtor to repay the debt.

[0068] Next, ECU41 restricts a portion of the functions of vehicle 4 and sends a success message of the function restriction of vehicle 4 to vehicle information server 3 (S303).

[0069] Next, ECU 41 determines whether it has received the second signal from vehicle information server 3 (S304). If ECU 41 determines that the second signal has been received from vehicle information server 3 (S304: Yes), vehicle 4 proceeds to S305. Conversely, if ECU 41 determines that the second signal has not been received from vehicle information server 3 (S304: No), vehicle 4 repeats the determination.

[0070] Next, ECU41 removes the function restrictions on the functions of vehicle 4 (S305) and sends the removal information to vehicle information server 3 (S306). After S306, vehicle 4 ends this process.

[0071] According to the above-described embodiment 1, since the ECU41 restricts a portion of the functions of the vehicle 4 capable of autonomous driving upon receiving the first signal, it can urge the debtor to repay the debt.

[0072] Furthermore, according to Embodiment 1, the ECU 41 controls, in order to control part of the charging function of the vehicle 4, at least one of the charging locations and devices pre-registered in the vehicle navigation system 42. Therefore, it becomes inconvenient for the user (debtor) to charge only at the registered charging locations and devices. As a result, the creditor can urge the user (debtor) to repay the debt.

[0073] Furthermore, according to Embodiment 1, the ECU 41 controls the charging device 44 in such a way that the charging speed is reduced to a predetermined speed. Therefore, the vehicle 4 cannot be charged within the normal time, which inconveniences the user (debtor) and thus prompts the repayment of the debt.

[0074] Furthermore, according to Embodiment 1, the ECU 41 controls the charging device 44 in such a way that the charging limit of the battery 43 is reduced to a predetermined limit. Therefore, the vehicle 4 cannot be driven in a fully charged state, which inconveniences the user (debtor) and thus prompts the repayment of the debt.

[0075] Furthermore, according to Embodiment 1, the ECU 41 controls the charging device 44 so that charging does not begin when the charging plug of the charger is inserted into the socket of the charging device 44. Therefore, by preventing the charging of the vehicle 4 from being carried out, convenience is provided to the user (debtor), thereby urging the repayment of the debt.

[0076] Furthermore, according to Embodiment 1, the ECU 41 controls the locking device 46 in such a way that the charging plug cannot be unplugged from the charging device 44 until a fixed time has elapsed after the vehicle 4 has finished charging. Therefore, even if the user (debtor) wants to use the vehicle 4 at the desired time, they must again wait until the charging plug can be unplugged, which is inconvenient. As a result, the creditor can urge the debtor to repay the debt.

[0077] Implementation Method 2 Next, Embodiment 2 will be described. In Embodiment 1, when the ECU 41 of vehicle 4 receives the first signal, a portion of the functions of vehicle 4 are limited. However, in Embodiment 2, the control unit 11 of the debt collection server 1 performs the same processing via remote control. That is, in Embodiment 2, the control unit 11 functions as a vehicle control device. The processing performed by the debt collection server 1 according to Embodiment 2 will be described below.

[0078] Processing of debt recovery servers Figure 6 This is a flowchart illustrating an outline of the processes performed by the debt collection server 1 according to Embodiment 2. Furthermore, in Embodiment 2, the control unit 11 of the debt collection server 1 functions as a processor for a vehicle control device.

[0079] like Figure 6 As shown, when the control unit 11 receives a first signal from the debt management server 2 (S401), it sends a lock signal, which restricts a portion of the functions of the vehicle 4 via remote control, to the vehicle 4 via the vehicle information server 3 (S402). In this case, the ECU 41 of the vehicle 4 restricts a portion of the functions of the vehicle 4 based on the remote control-based lock signal from the debt collection server 1. Specifically, the ECU 41 of the vehicle 4 restricts at least one of the functions described in (1) to (4) above in Embodiment 1 based on the remote control-based lock signal from the debt collection server 1. That is, in Embodiment 2, the control unit 11 functions as a processor of the vehicle control device.

[0080] Next, the control unit 11 receives the success information of the functional limitation of the vehicle 4 from the vehicle 4 via the vehicle information server 3 (S403).

[0081] Next, the control unit 11 determines whether a second signal has been received from the debt management server 2 (S404). If the control unit 11 determines that a second signal has been received from the debt management server 2 (S404: Yes), the debt collection server 1 proceeds to S405. Conversely, if the control unit 11 determines that a second signal has not been received from the debt management server 2 (S404: No), the debt collection server 1 repeats the determination.

[0082] Next, the control unit 11 sends a release signal, indicating that the functional restrictions on vehicle 4 have been lifted via remote control, to vehicle 4 via vehicle information server 3 (S405). In this case, the ECU 41 of vehicle 4 lifts the functional restrictions on the functions possessed by vehicle 4 based on the remote control release signal from debt collection server 1. In this case, the control unit 11 can either display the information indicating that the functional restrictions on vehicle 4 have been lifted via remote control on display device 47 of vehicle 4 via vehicle information server 3, or send and display it to terminal device 5.

[0083] Next, the control unit 11 receives the information to remove the function restriction from the vehicle 4 via the debt management server 2 (S406). After S406, the debt collection server 1 ends this process.

[0084] According to Embodiment 2 described above, since, similar to Embodiment 1, upon receiving the first signal, the control unit 11 remotely restricts a portion of the functions of the vehicle 4, thereby urging the debtor to repay the debt.

[0085] Other implementation methods Those skilled in the art can readily derive further effects and variations. Therefore, the broader aspects of the invention are not limited to the specific details and representative embodiments shown and described above. Thus, various modifications can be made without departing from the spirit or scope of the overall concept of the invention as defined by the technical solutions and their equivalents.

[0086] For example, although Embodiments 1 and 2 are described with the debt collection server 1 or vehicle 4 as the premise, the debt management server 2 or vehicle information server 3 may also have the functions of the control unit 11 or ECU 41. In this case, the debt management server 2 or vehicle information server 3 may also have the functions of the control unit 11 and vehicle history DB 12 of the debt collection server 1. Furthermore, in the vehicle control device involved in Embodiments 1 and 2, the vehicle 4 may also undertake part of the processing of the debt collection server 1 and vehicle information server 3.

[0087] Furthermore, in the embodiments disclosed herein, the debt collection server 1, the debt management server 2, and the vehicle information server 3 are described as different devices. However, the debt collection server 1, the debt management server 2, and the vehicle information server 3 may also be composed of one, two, or more devices.

Claims

1. A vehicle control device, comprising a processor, wherein, Upon receiving a first signal from a debt management server that manages the debts of the target vehicle, indicating that the repayment of the debts for the target vehicle has not been properly implemented, the processor controls the charging speed of the target vehicle to be reduced to a predetermined speed.

2. A vehicle control device, comprising a processor, wherein, Upon receiving a first signal indicating that the repayment of a debt to the target vehicle has not been properly implemented, the processor restricts a portion of the charging function for the target vehicle.

3. The vehicle control device as described in claim 2, wherein, The following are examples of situations where a portion of the charging function is restricted: Control is exercised in a manner that limits at least one of the locations and devices where charging is possible.

4. The vehicle control device as claimed in claim 2, wherein, The following are examples of situations where a portion of the charging function is restricted: It is controlled by reducing the charging speed to a predetermined speed.

5. The vehicle control device as claimed in claim 2, wherein, The following are examples of situations where a portion of the charging function is restricted: It is controlled by reducing the charging limit to a predetermined limit.

6. The vehicle control device as claimed in claim 2, wherein, The following are examples of situations where a portion of the charging function is restricted: The system is controlled to prevent charging from starting when the charging plug is inserted into the vehicle's charging port.

7. The vehicle control device as claimed in claim 2, wherein, The following are examples of situations where a portion of the charging function is restricted: The locking mechanism is controlled in such a way that the charging plug cannot be pulled out of the charging device until a fixed time has elapsed after the vehicle has finished charging.

8. The vehicle control device as claimed in claim 2, wherein, Based on the receipt of the first signal, the processor outputs a locking signal to the target vehicle to lock a portion of the vehicle's functions via remote control, thereby implementing remote locking control.

Images