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 made correctly 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 payment information related to loan payment status. Summary of the Invention

[0003] However, creditors of car rentals and car loans are more interested in repayment than restricting the use of vehicles, and therefore try to get debtors to repay their money smoothly.

[0004] However, in the technology disclosed in Japanese Patent No. 7050844, simply issuing notices related to the repayment status of the loan, the delay in the loan, or urging payment is insufficient to urge the debtor to repay, and there is 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 disclosed herein includes a processor that, upon receiving a first signal from a debt management server that manages debts of a vehicle capable of autonomous driving, indicating that debt repayment for the vehicle has not been properly made, controls the vehicle to stop or park at a predetermined distance from a destination designated for the vehicle, depending on the condition of receiving the first signal.

[0007] Furthermore, the vehicle control device involved in this disclosure includes a processor that, upon receiving a first signal indicating that the repayment of a debt to an autonomous vehicle has not been performed correctly, restricts a portion of the functions of the vehicle based on the condition of receiving the first signal.

[0008] According to this disclosure, it can serve to urge debtors to repay their debts. Attached Figure Description

[0009] 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 showing the outline structure of the vehicle control system according to Embodiment 1 of this disclosure; Figure 2 This 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. Figure 3 This is a flowchart illustrating a summary of the processes performed by the debt collection server according to Embodiment 1 of this disclosure; Figure 4 This is a flowchart illustrating a summary of the processing performed by the vehicle information server according to Embodiment 1 of this disclosure; Figure 5 This is a flowchart illustrating a summary of the processing performed by the vehicle according to Embodiment 1 of this disclosure; and Figure 6 This is a flowchart illustrating a summary of the processes performed by the debt recovery server according to Embodiment 2 of this disclosure. Detailed Implementation

[0010] Hereinafter, a 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.

[0011] Implementation Method 1 Vehicle control system Figure 1 This is a block diagram showing the general structure of the vehicle control system involved in Implementation 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 via a network N. This network N may be, for example, a public line network such as the Internet or a mobile phone line network.

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

[0013] 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.

[0014] 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.

[0015] 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).

[0016] 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.

[0017] 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.

[0018] The input device 14 is implemented, for example, through a touch panel, keyboard, indicator device, etc. The input device 14 accepts various operations input from the user and outputs signals corresponding to the accepted operations to the control unit 11.

[0019] 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.

[0020] 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.

[0021] When the debt management system 21 finds a vehicle 4 (object vehicle) among the multiple vehicles 4 managed by the debt management DB22 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 (object vehicle) that meets the engine start-lock requirement includes vehicles 4 (object vehicles) where payment for debts has been delayed, vehicles 4 (object vehicles) where debt payments have not been made correctly, and vehicles 4 where debts have been defaulted on or where debt payments have been delayed.

[0022] 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 payment status of loan and lease receivables.

[0023] 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.

[0024] 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 then 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.

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

[0026] 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. Upon request from the debt collection server 1, the vehicle information DB32, under the control of the control unit 31, sends the utilization status information to the debt collection server 1.

[0027] 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.

[0028] [Vehicle Functional Structure] Next, the functional structure of vehicle 4 will be explained. Vehicle 4 can be, for example, a conventional vehicle (CONV), a hybrid electric vehicle (HEV), or a plug-in hybrid electric vehicle (PHEV). Alternatively, vehicle 4 could also be a fuel cell electric vehicle (FCEV) or a battery electric vehicle (BEV). Furthermore, vehicle 4 is envisioned to be capable of autonomous driving and configured to move autonomously to the destination or pick-up / drop-off location input from the debt collection server 1 or terminal device 5.

[0029] Vehicle 4 includes a memory 40, an ECU 41, a car navigation system 42, a drive unit 43, a dimming glass 44, a detection unit 45, a voice output unit 46, a display device 47, an input unit 48, and a communication unit 49.

[0030] 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.

[0031] 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, for example, a situation where the debtor of vehicle 4 is in default on debts (e.g., payment delay). For example, debt management server 2 determines whether the function lock-up requirements are met. Furthermore, if 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, for example, refers to the vehicle 4 that is the object of the debt.

[0032] Furthermore, when ECU41 receives a second signal indicating predetermined conditions, such as the debt of vehicle 4 having been fulfilled, for vehicle 4 that has been functionally locked, ECU41 releases the functional restriction on vehicle 4.

[0033] Furthermore, upon receiving a first signal (hereinafter referred to as the "first signal") from the vehicle information server 3 indicating that payment for the debt to vehicle 4 (the object vehicle) has not been correctly made, ECU 41 restricts a portion of the functions possessed by vehicle 4. Moreover, ECU 41 maintains the functional restrictions on vehicle 4 until it receives a second signal (hereinafter referred to as the "second signal") from the vehicle information server 3 indicating that the debt to vehicle 4 (the object vehicle) has been fulfilled. Furthermore, in Embodiment 1, ECU 41 functions as a processor of the vehicle control device.

[0034] Furthermore, the ECU41 controls the drive unit 43 and, based on the vehicle 4's location information detected by the car navigation system 42, enables the vehicle 4 to move autonomously toward the destination or pick-up / drop-off location specified via the terminal device 5 or the input unit 48.

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

[0036] The drive unit 43 is constructed using a drive source such as an engine and an electric motor, a braking mechanism, and a steering mechanism to move the vehicle 4. Furthermore, under the control of the ECU 41, the drive unit 43 autonomously drives the vehicle 4 to its destination based on the position information of the vehicle 4 detected by the vehicle navigation system 42.

[0037] The dimming glass 44 is installed on the door window or sunroof of the vehicle 4, and under the control of the ECU 41, it changes the light transmittance according to the on / off state of the power supply. Specifically, the dimming glass 44 switches from a light-blocking state to a transparent state according to the on / off state of the power supply controlled by the ECU 41. Furthermore, while dimming glass 44 is envisioned in Embodiment 1, it could also be a dimming film capable of changing its transmittance according to the on / off state of the power supply, or it could be a liquid crystal film.

[0038] The detection unit 45 is configured using a timer and sensors that detect the driving state of the drive unit 43, etc., to detect the time after the vehicle 4 stops and output the detection result to the ECU 41.

[0039] The voice output unit 46 is composed of a speaker, a DA conversion circuit, and an amplifier, and outputs various information under the control of the ECU 41. For example, the voice output unit 46 converts digital voice data input from the ECU 41 into analog voice data and outputs it to the outside.

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

[0041] The input unit 48 is implemented, for example, through a touch panel, keyboard, indicator device, etc. The input unit 48 accepts various operation inputs from the user and outputs signals corresponding to the accepted operations to the ECU 41.

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

[0043] 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 accepts input from the debtor for various operations.

[0044] 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 illustrated using the case where a debtor's vehicle 4 (the object vehicle) is involved in a delay in payment for a debt among multiple vehicles 4.

[0045] like Figure 2As 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 functions of the vehicle 4 and sends a success message to the vehicle information server 3 regarding the function restriction of the vehicle 4 (S4). The content of the restriction on the portion of the functions of the vehicle 4 implemented by the ECU 41 will be described later. Afterwards, the vehicle information server 3 receives a response from the vehicle 4 and sends a success message regarding the function restriction to the debt collection server 1 (S5). In this case, the debt collection server 1 establishes a correspondence between the success message regarding 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 database DB12.

[0046] 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 releases a portion of the functional restrictions on the vehicle 4 and sends a response of release information to the vehicle information server 3 (S9). In this case, the debtor can utilize the vehicle 4 without functional restrictions. The vehicle information server 3 then sends the response of the release information 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 release 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 database DB12.

[0047] Processing in the debt recovery server Next, the processing performed by debt collection server 1 will be explained. Figure 3 This is a flowchart summarizing the processes performed by debt collection server 1.

[0048] 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).

[0049] 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 release information from the vehicle information server 3 (S106). After S106, the debt recovery server 1 terminates this process.

[0050] Vehicle information server processing Next, a summary of the processing performed by the vehicle information server 3 will be provided. Figure 4 This is a flowchart summarizing the processes performed by the vehicle information server 3.

[0051] 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).

[0052] 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).

[0053] 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).

[0054] 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.

[0055] Vehicle handling Next, a summary of the processes performed by vehicle 4 will be provided. Figure 5 This is a flowchart summarizing the processes performed by vehicle 4.

[0056] 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 functions of vehicle 4 (S302). Specifically, ECU41 restricts at least one of the following functions of vehicle 4: (1) to (4). (1) ECU 41 controls drive unit 43 to park or stop the vehicle 4 at a predetermined distance from the destination specified by the user (debtor) via car navigation system 42 using input unit 48. Here, the predetermined distance from the destination is, for example, approximately 300 to 500 meters away. Furthermore, ECU 41 can appropriately change the predetermined distance from the destination; for example, it can be set to a position further from the destination as the user's (debtor's) debt amount increases. In this case, ECU 41 displays a message on display device 47 or terminal device 5 indicating that the vehicle 4 will park or stop at the predetermined distance from the destination. This makes it inconvenient for the user (debtor) to be unable to park or stop the vehicle 4 at the desired destination. As a result, the creditor can urge the user (debtor) to repay the debt. (2) Furthermore, ECU 41 controls drive unit 43 to stop or park the vehicle 4 at a predetermined distance from the pick-up / drop-off location specified by the user via terminal device 5. Here, the predetermined distance from the pick-up / drop-off location is, for example, approximately 300 to 500 meters away. Additionally, ECU 41 can appropriately change the predetermined distance from the pick-up / drop-off location; for example, it can be set to a location farther from the pick-up / drop-off location as the user's (debtor's) debt amount increases. In this case, ECU 41 displays a message on display device 47 or terminal device 5 indicating that the vehicle 4 will stop or park at the predetermined distance from the pick-up / drop-off location. As a result, the user (debtor) is inconvenienced because they cannot park the vehicle 4 at the desired pick-up / drop-off location. That is, the user (debtor) will experience inconvenience because the vehicle 4 has not reached its destination or is parked at a location far from the entrance / exit of the destination. Consequently, the creditor can urge the user (debtor) to repay the debt. (3) Furthermore, the ECU 41 controls the on / off state of the power supply to the dimming glass 44 installed in the windows and sunroof of the vehicle 4, thus keeping the dimming glass 44 in either a dark or transparent state. For example, if the user (debtor) specifies the state of the dimming glass 44 as transparent via the input unit 48, the ECU 41 controls it to be in a dark state by turning on the power supply to the dimming glass 44. On the other hand, if the user (debtor) specifies the state of the dimming glass 44 as dark via the input unit 48, the ECU 41 controls it to be in a transparent state by turning off the power supply to the dimming glass 44. Therefore, even if the user (debtor) wants to switch the window state at a desired time, they cannot do so, which is inconvenient. That is, the user (debtor) will feel inconvenienced if the vehicle 4 does not arrive at their designated residence, or if the vehicle 4 does not arrive even if a designated location has been specified for the user to ride in. As a result, the creditor can urge the user (debtor) to repay the debt. (4) Furthermore, the ECU 41 controls the drive unit 43 to move the vehicle 4 to a predetermined location when the vehicle 4 is not in use. Specifically, if the detection unit 45 detects that a predetermined time, such as one hour, has elapsed after the vehicle 4 has been parked at a predetermined location, such as the parking lot of the user's (debtor's) house, the ECU 41 determines that the vehicle 4 is not in use and drives the drive unit 43 to move it to the parking lot managed by the creditor. Additionally, the ECU 41 determines that the vehicle 4 is not in use at night when it is not in use and drives the drive unit 43 to move it to the parking lot managed by the creditor. Furthermore, the ECU 41 can also drive the drive unit 43 to move the vehicle 4 to a location designated by the creditor, other than the parking lot managed by the creditor. In this case, the ECU 41 can also send a message to the terminal device 5 indicating that the vehicle 4 has been moved.

[0061] Thus, ECU41 restricts at least one of the functions described in (1) to (4) above. As a result, it is able to urge the debtor to repay the debt.

[0062] Next, ECU41 restricts part of the function of vehicle 4 by sending a success message (S303) to vehicle information server 3 regarding the function restriction of vehicle 4.

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

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

[0065] According to Embodiment 1 described above, upon receiving a first signal, ECU 41 restricts a portion of the functions of the autonomous vehicle 4, thereby prompting the debtor to repay the debt.

[0066] Furthermore, according to Embodiment 1, the ECU 41 controls the drive unit 43 to park or park at a predetermined distance from the destination specified by the user (debtor) via the car navigation system 42 using the input unit 48. Therefore, the user (debtor) is unable to park or park the vehicle 4 at the desired destination, which is less convenient, thus enabling the debtor to be urged to repay the debt.

[0067] Furthermore, according to Embodiment 1, ECU 41 controls drive unit 43 to stop or park at a predetermined distance from the pick-up / drop-off location designated by the user to vehicle 4 via terminal device 5. Therefore, the user (debtor) is unable to stop or park vehicle 4 at the desired pick-up / drop-off location, which is inconvenient, thus enabling the debtor to be urged to repay the debt.

[0068] Furthermore, according to Embodiment 1, the ECU 41 controls the on / off state of the power supply to the dimming glass 44 installed in the windows and sunroof of the vehicle 4, thus keeping the dimming glass 44 in either a light-blocking or transparent state. Therefore, even if the user wants to switch the window state at a desired time, it cannot be switched, which is inconvenient and thus prompts the repayment of debts.

[0069] Furthermore, according to Embodiment 1, the ECU 41 controls the drive unit 43 to move the vehicle 4 to a predetermined location when the vehicle 4 is not in use. Therefore, even if the user wants to use the vehicle 4 at the desired time, they must again designate the vehicle 4 to the pick-up and drop-off location, which is inconvenient and thus prompts the user to repay the debt.

[0070] 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. Hereinafter, the processing performed by the debt collection server 1 according to Embodiment 2 will be described.

[0071] Processing of debt recovery servers Figure 6 This is a flowchart outlining 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.

[0072] 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 possessed by 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. In addition, in Embodiment 2, the control unit 11 functions as a processor of the vehicle control device.

[0073] 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 (S402).

[0074] Next, the control unit 11 determines whether a second signal has been received from the debt management server 2 (S403). 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.

[0075] Next, the control unit 11 sends a release signal to vehicle 4 via vehicle information server 3 to remove the functional restrictions on vehicle 4 through remote control (S405). In this case, the ECU 41 of vehicle 4 removes 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 removal of the functional restrictions on vehicle 4 on the display device 47 of vehicle 4 via vehicle information server 3 through remote control, or send and display it to terminal device 5.

[0076] 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.

[0077] 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.

[0078] Other implementation methods Those skilled in the art can readily derive further effects and modifications. Therefore, the invention is 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.

[0079] For example, in Embodiments 1 and 2, the description is based on the premise of debt collection server 1 or vehicle 4, but debt management server 2 or vehicle information server 3 may also have the functions of control unit 11 or ECU 41. In this case, debt management server 2 or vehicle information server 3 may also have the functions of control unit 11 and vehicle history database 12 of debt collection server 1. Furthermore, in the vehicle control device involved in Embodiments 1 and 2, vehicle 4 may also perform part of the processing of debt collection server 1 and vehicle information server 3.

[0080] 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, wherein, Equipped with a processor If the processor receives a first signal from a debt management server that manages the debts of an autonomous vehicle indicating that the debts for the vehicle have not been properly repaid, it controls the vehicle to stop or park at a predetermined distance from the destination specified for the vehicle, depending on the situation after receiving the first signal.

2. A vehicle control device, wherein, Equipped with a processor Upon receiving a first signal indicating that debt repayment for a vehicle capable of autonomous driving has not been properly carried out, the processor restricts a portion of the vehicle's functionality based on the circumstances surrounding the receipt of the first signal.

3. The vehicle control device as described in claim 2, wherein, The limitation of some of the functions includes the following situations, namely, Control is performed to stop or park the vehicle at a predetermined distance from the destination specified for the vehicle.

4. The vehicle control device as claimed in claim 2, wherein, The limitation of some of the functions includes the following situations, namely, Control is performed to stop or park the vehicle at a predetermined distance from the designated pick-up / drop-off location.

5. The vehicle control device as claimed in claim 2, wherein, The limitation of some of the functions includes the following situations, namely, The dimming film or dimming glass is controlled in a way that keeps it in a light-blocking or transparent state. The dimming film or dimming glass is installed on the window or sunroof of the target vehicle and changes the light transmittance according to the power supply status.

6. The vehicle control device as claimed in claim 2, wherein, The limitation of some of the functions includes the following situations, namely, When the vehicle is not being used by a user, it is controlled to move to a predetermined location.

7. 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 restrict a portion of the vehicle's functions, thereby performing remote control.

Images