KR20230169734A - Server for managing rental car - Google Patents

Abstract

The present invention relates to a car rental management server to efficiently manage various costs incurred by a customer in processes of from renting and using a vehicle from a car rental company to returning the vehicle. According to the present invention, the car rental management server is connected to a customer terminal to exchange data. The car rental management server comprises: a communication unit receiving customer information, rental information, contract information, cost information, and approval information; a storage unit storing the customer information, rental information, contract information, cost information, and approval information provided through the communication unit; and a control unit providing a car rental service program for receiving the customer information, rental information, contract information, cost information, and approval information stored in the storage unit. The control unit outputs at least one or more pieces of car information, which allows a car to be selected through the car rental service program, on a screen of the customer terminal, outputs the rental date for the selected car on the screen of the customer terminal when one car information is selected, stores the car information and the rental date in the storage unit and calculates the car rental fee information according to the car information and the rental date when the rental date is selected; and generates the contract information when the approval information is provided from the communication unit.

Description

Vehicle rental management server {SERVER FOR MANAGING RENTAL CAR}

The present invention relates to a car rental management system, and more specifically, to a car rental management server that allows a car rental company to charge a customer for costs incurred while the customer uses the car rental company's vehicle.

Customers can use vehicles through vehicle rental companies. Customers can select the appropriate vehicle from among the vehicle rental company's vehicles, taking into account their circumstances and budget. Customers can make reservations to use the vehicle of their choice. Customers may enter into a rental contract with a vehicle rental company to use the vehicle. The customer must pay for the use of the vehicle for the rental contract.

The car rental company must rent the car when it is reserved according to the rental contract. A car rental company completes the contract when the customer completes use and returns the car. When a customer completes use of the vehicle and returns it, the vehicle rental company can check for damage to the vehicle through basic inspection, including visual inspection. Additionally, if there is any damage, the car rental company may charge additional costs to repair the damage.

A customer may incur a fine by violating traffic laws while driving, or a customer may cause an accident while driving and require insurance coverage. In this way, additional processing is required for costs incurred during operation, and processing this is difficult.

The present invention is intended to solve the above-described problem. The purpose of the present invention is to enable a customer to rent and use a vehicle from a car rental company, and for the car rental company to automatically bill the customer for costs depending on situations that occur during use. The purpose is to provide a vehicle rental management server that allows

A vehicle rental management server that is connected to a customer terminal and exchanges data according to an embodiment of the present invention includes a communication unit that receives customer information, rental information, contract information, cost information, and approval information; a storage unit that stores customer information, rental information, contract information, cost information, and approval information provided through the communication unit; and a control unit providing a vehicle rental service program to receive customer information, rental information, contract information, cost information, and approval information stored in the storage unit.

In one embodiment, the control unit may output at least one vehicle information that allows selecting a vehicle through the vehicle rental service program to the screen of the customer terminal.

In one embodiment, when any vehicle information is selected, the control unit outputs the rental date for the selected vehicle on the screen of the customer terminal, and when the rental available date is selected, the vehicle information and rental available date are displayed. is stored in the storage unit, vehicle rental fee information is calculated according to vehicle information and rental available dates, and contract information can be generated when approval information is received from the communication unit.

In one embodiment, the control unit collects vehicle information, contractor information, rental period information, and return information, checks the return information, and proceeds with settlement processing if the rental vehicle is returned within the rental period. Rental cost information can be displayed on the screen of the customer terminal.

The control unit checks the return information and, if the rental vehicle is returned beyond the rental period, registers the customer of the returned vehicle in the delinquent list and registers the returned vehicle in the delinquent list. After one month has passed, the returned vehicle The first non-deposit notification can be sent to the customer and displayed on the screen of the customer terminal, and the first non-deposit notification can be sent. When another month has passed, the second non-deposit notification can be sent to the customer terminal. It is displayed on the screen, and after sending the second non-deposit notification, collection processing can be performed.

In one embodiment, the control unit collects fine management information from the outside through the communication unit, compares the vehicle information of the fine management information with the vehicle number stored in the storage unit, and if the vehicle number as a result of the comparison matches, the penalty grant date and the rental period of the contract information, and if the penalty grant date is included in the rental period as a result of the comparison, the customer stored in the contract information is designated as the target of penalty notification, and penalty management information is transmitted through the communication unit, and the customer terminal Fine management information can be displayed on the screen.

In one embodiment, the control unit collects insurance loan information from the outside through the communication unit, first checks whether there is a vehicle dispatched according to the insurance loan information, and if there is a vehicle dispatched after first checking, proceeds with dispatch. And if no vehicle has been dispatched through the first check, check whether the repair of the accident vehicle has been completed, and if the repair of the accident vehicle has been completed, check secondarily whether there is a vehicle dispatched, and if there is a vehicle dispatched through the second check, check whether the vehicle has been dispatched. , and if there is no vehicle dispatched by second confirmation, you can proceed with the rental completion process.

According to the car rental management server according to the present invention, it is possible to efficiently manage various costs incurred in the process of a customer renting and using a car from a car rental company, and using and returning the car.

1 is a configuration diagram illustrating a vehicle rental management system according to an embodiment of the present invention.
FIG. 2 is a block diagram illustrating the vehicle rental management system shown in FIG. 1 by way of example.
FIG. 3 is a block diagram illustrating the first customer terminal shown in FIG. 2.
FIG. 4 is a block diagram exemplarily showing the vehicle rental management server shown in FIG. 2.
FIG. 5 is a flowchart exemplarily illustrating member registration and authentication methods among the operations of the customer information management unit shown in FIG. 4.
FIG. 6 is a flowchart illustrating an exemplary method of operating the application management unit shown in FIG. 4.
FIG. 7 is a flowchart illustrating an exemplary operation method of the vehicle rental management server shown in FIG. 2.
FIG. 8 is a diagram exemplarily showing the relationship between the additional information DB and the additional information management unit shown in FIG. 4.
FIG. 9 is a flowchart showing a method of processing settlement information of the settlement information management unit shown in FIG. 8.
FIG. 10 is a flowchart showing a method of processing penalty information of the penalty information management unit shown in FIG. 8.
FIG. 11 is a flowchart showing a method of processing insurance loan information of the insurance loan information management unit shown in FIG. 8.
Figure 12 is a screen showing an example of a user interface for logging in that appears on the screen of the first customer terminal.
Figure 13 is a screen showing the manager interface displayed on the customer terminal in Figure 12.
Figure 14 is a screen illustrating a collection management interface according to an embodiment of the present invention.
Figure 15 is a screen exemplarily showing a fine management interface according to an embodiment of the present invention.
FIG. 16 is a screen exemplarily showing the insurance loan management interface that appears when the insurance loan management unit is selected in FIG. 13.

Hereinafter, embodiments of the present invention will be described clearly and in detail so that a person skilled in the art can easily practice the present invention.

1 is a configuration diagram illustrating a vehicle rental management system according to an embodiment of the present invention. Referring to FIG. 1, the vehicle rental management system 1000 may include customer terminals 1100, 1101, 1200, and 1201, a vehicle rental management server 2000, and an information management server 3000.

Customers can access the car rental management server 2000 using several customer terminals 1100, 1101, 1200, and 1201. Here, the customer terminals 1100, 1101, 1200, and 1201 may be electronic devices such as smart phones, tablet PCs, laptop PCs, and desktop PCs. Customer terminals 1100, 1101, 1200, and 1201 may communicate with the vehicle rental management server 2000 by wire or wirelessly. A customer can access the car rental management server 2000 using the first or second customer terminal 1100 or 1200 and obtain car rental information provided by the operator of the car rental management server 2000.

The vehicle rental management server 2000 may receive and store data input from customer terminals 1100, 1101, 1200, and 1201. Additionally, the vehicle rental management server 2000 may provide stored data to customer terminals 1100, 1101, 1200, and 1201. The vehicle rental management server 2000 can perform vehicle management, contract management, cost management, and additional management tasks. The vehicle rental management server 2000 may provide information related to performed management tasks to the outside.

The information management server 3000 may provide specific information required for vehicle rental management. The information management server 3000 is a bank server that can provide bank deposit information, a fine server of a local government or police agency that issues fine-related information, a server of an insurance company that applies for insurance rental due to a vehicle accident, or a car rental company and collection services. It may be one of the servers of a solicitor's office that issues payment orders for gold bullion.

FIG. 2 is a block diagram illustrating the vehicle rental management system shown in FIG. 1 by way of example. Referring to FIG. 2 , the vehicle rental management system 1000 may include a first customer terminal 1100, a second customer terminal 1200, and a vehicle rental management server 2000.

The first customer terminal 1100 may be a smart phone, and the second customer terminal 1200 may be a desktop PC. As an example, the first customer terminal 1100 may be an app-based terminal, and the second customer terminal 1200 may be a web-based terminal. Additionally, the first or second customer terminals 1100 and 1200 may be terminals in which both app-based and web-based car rental service programs can be installed and run.

The first or second customer terminals 1100 and 1200 may be connected to each other through a communication network. Additionally, each of the first or second customer terminals 1100 and 1200 may be connected to the vehicle rental management server 2000 through a communication network. Additionally, the first or second customer terminal 1100 or 1200 may transmit data for vehicle rental information to the vehicle rental management server 2000 or receive data from the vehicle rental management server 2000. The first and second customer terminals 1100 and 1200 may receive information provided by the customer through a vehicle rental service program and provide vehicle rental information required by the customer.

The first or second customer terminal (1100, 1200) may include a screen unit (1110, 1210) and a driving unit (1120, 1220). The driving unit 1120 of the first customer terminal 1100 may execute a car rental application. The driving unit 1220 of the second customer terminal 1200 may provide vehicle rental information on the screen using a web service such as a homepage. The driving units 1120 and 1220 may include hardware or software for running a car rental application or web service. The internal configuration and operating principles of the driving units 1120 and 1220 will be described in more detail below.

The vehicle rental management server 2000 may include a communication unit 2100, a storage unit 2200, and a control unit 2300. The vehicle rental management server 2000 may store data input from the first or second customer terminal (1100, 1200) and transmit the stored data to the first or second customer terminal (1100, 1200).

The communication unit 2100 may receive customer information, rental information, contract information, cost information, or vehicle rental information from the first or second customer terminal (1100, 1200). For this purpose, the communication unit 2100 provides a long-distance network interface, such as a G module, LTE module, LTE-A module, Wi-Fi module, WiGig module, UWB (Ultra Wide Band) module, or LAN card. may include. In addition, the communication unit 2100 includes a short-distance network interface such as a Magnetic Secure Transmission (MST) module, Bluetooth module, NFC module, RFID module, ZigBee module, Z-Wave module, or infrared module. can do.

The communication unit 2100 may approve or block membership registration according to the control of the control unit 2300. Additionally, the communication unit 2100 may approve, block, or restrict service use according to customer information when logging in. The communication unit 2100 may provide customer information to the storage unit 2200.

The storage unit 2200 can store customer information such as personal information of customers using the service or whether they sign up for membership or whether the service is blocked, and can store customer information, rental information, contract information, or cost information provided through the communication unit 2100. You can save it. To this end, the storage unit 2200 may include a non-volatile memory that does not lose data even when the power is turned off. The storage unit 2200 may be, for example, flash memory, ROM, RAM, EEROM, EPROM, EEPROM, HDD, or SSD. The storage unit 2200 may include, for example, a file system, a database, or an embedded database.

The control unit 2300 may control each component included in the vehicle rental management server 2000 and the operation of the vehicle rental management server 2000. The control unit 2300 may perform an operation to provide various vehicle rental information to customers. The control unit 2300 may control the operation of the vehicle rental management server 2000 using customer information and vehicle rental information received from the first or second customer terminals 1100 and 1200.

The control unit 2300 may provide a car rental service program to the customer terminal 1100 to receive customer information, rental information, contract information, or cost information stored in the storage unit 2200. Additionally, the control unit 2300 may perform operations to manage and update customer information and vehicle rental information. To this end, the control unit 2300 may include a central processing unit (CPU), a graphics processing unit (GPU), a micro controller unit (MCU), or a microprocessor. You can.

The control unit 2300 may cause at least one vehicle information to be displayed on the screen units 1110 and 1210 of the first or second customer terminals 1100 and 1200. The control unit 2300 can receive information by clicking or touching the output vehicle information.

When one vehicle information is selected, the control unit 2300 may display information on dates available for rental for the selected vehicle on the screen units 1110 and 1210. When a available rental date is selected, the control unit 2300 may store vehicle information and available rental dates in the storage unit 2200. The control unit 2300 can calculate vehicle rental fee information according to vehicle information and rental available dates and display it on the screen units 1110 and 1210. Additionally, the control unit 2300 can generate contract information when approval information is provided through the communication unit 2100.

The vehicle rental management server 2000 may provide a vehicle rental information service and request membership registration from each customer. The vehicle rental management server 2000 may request the customer to log in if he or she has registered as a member. At this time, the car rental management server 2000 may store customer information for each customer in the storage unit 2200. In addition, the car rental management server 2000 may refer to customer information stored in the storage unit 2200 and approve, prohibit, or restrict membership registration or login of each customer.

FIG. 3 is a block diagram illustrating the first customer terminal shown in FIG. 2. In Figure 3, a smart phone is shown as an example. Referring to FIG. 3, the first customer terminal 1100 includes a screen unit 1110, a wireless communication unit 1111, an input/output interface unit 1112, an operating system 1113, a car rental application 1114, and a memory 1115. ) may include. Hereinafter, the description will focus on the first customer terminal 1100, but the vehicle rental management system can be provided to the second customer terminal 1200 in a similar manner through a web-based vehicle rental service program.

The wireless communication unit 1111 allows the first customer terminal 1100 to wirelessly connect to the car rental management server (see FIG. 2, 2000). Additionally, the first customer terminal 1100 may exchange data with an external device such as the second customer terminal 1200 or the car rental management server 2000 through the wireless communication unit 1111. The wireless communication unit 1111 may include a wireless Internet module such as a 3G module, LTE module, LTE-A module, and Wi-Fi module.

The input/output interface unit 1112 may be used to input letters or numbers into the first customer terminal 1100 or provide content to the customer. The input/output interface unit 1112 may be connected to an internal input device such as an on-screen keyboard or an external input device (eg, a keyboard or electronic pen) using a wire or Bluetooth. Additionally, the input/output interface unit 1112 may be connected to an internal output device such as the screen unit 1110 or an external output device (eg, a monitor or printer, etc.) using a wire or Bluetooth. When registering or logging in through the car rental application 1114, the customer can input customer information such as a customer ID or password using the input/output interface unit 1112. Additionally, the customer can provide or receive vehicle rental information to the vehicle rental management server 2000 using the input/output interface unit 1112.

The operating system 1113 may provide an environment in which the car rental application 1114 can be executed. The car rental application 1114 is an application program that is installed and operates on the operating system 1113.

The car rental application 1114 may provide a customer interface that can set up and manage service use through customer registration or login. Additionally, the car rental application 1114 may provide a customer interface through which the first customer terminal 1100 can connect to the car rental management server 2000 to exchange car rental information. The car rental application 1114 can transmit and receive data through the operating system 1113 and the input/output interface unit 1112.

The memory 1115 may store customer information (eg, customer ID or password, etc.) of customers using the car rental application 1114. The memory 1115 may include volatile memory, which loses data when the power is turned off, and non-volatile memory, which preserves data. In the memory 1115, not only passwords but also programs such as a car rental application 1114 or an operating system 1113 may be stored.

FIG. 4 is a block diagram exemplarily showing the vehicle rental management server shown in FIG. 2. Referring to FIG. 4, the vehicle rental management server 2000 may include a communication unit 2100, a storage unit 2200, and a control unit 2300. The vehicle rental management server 2000 may receive information related to vehicle rental from the first or second customer terminals 1100 and 1200. The vehicle rental management server 2000 can convert the input information into a database and store it. The car rental management server 2000 can calculate data on providing car rental information when there is a request for information from the customer terminals 1100, 1101, 1200, and 1201. The vehicle rental management server 2000 may provide vehicle rental information to customer terminals 1100, 1101, 1200, and 1201 that have requested information.

The communication unit 2100 may communicate with the first or second customer terminals 1100 and 1200. The communication unit 2100 includes code division multiple access (CDMA), global system for mobile communication (GSM), wideband CDMA (WCDMA), CDMA-2000, time division multiple access (TDMA), long term evolution (LTE), and Wimax (worldwide). It can support wired and wireless communications such as interoperability for microwave access, WLAN (wireless LAN), UWB (ultrawide band), Bluetooth, WI-DI (wireless display), Internet, LAN, etc.

The communication unit 2100 may include an input unit 2110 and an output unit 2120. The input unit 2110 may receive vehicle rental information data, including customer information or vehicle rental information, from the first or second customer terminals 1100 and 1200, and transmit it to the storage unit 2200 or the control unit 2300. . When a request for vehicle rental information is received from the first or second customer terminal (1100, 1200), the output unit 2120 obtains the vehicle rental information directly from the storage unit 2200 or rents the vehicle through the control unit 2300. Information can be calculated and provided to customers.

The storage unit 2200 may include a vehicle information DB 2210, a customer information DB 2220, a rental information DB 2230, a contract information DB 2240, and an additional information DB 2250. The storage unit 2200 may store vehicle rental information data received from the input unit 2110.

The vehicle information DB 2210 may store information about vehicles owned by the vehicle rental company and vehicle rental fee information. For example, information about the vehicle may include vehicle number, vehicle type, engine displacement, vehicle class, vehicle price, etc. In particular, a license plate number may be used to identify a specific vehicle.

The customer information DB 2220 may store information about customers who have signed up through the car rental application 1114, including customer name, gender, age, and driver's license number. In this case, the driver's license number may be used to identify a specific customer.

In the rental information DB 2230, the vehicle number stored in the vehicle information DB 2210 may be stored to identify the vehicle being rented, and in relation to the rental period, the rental date and rental time, return date, and return date may be stored in the rental information DB 2230. Time, rental period, etc. may be stored.

To identify the vehicle, the contract information DB 2240 uses the vehicle number stored in the vehicle information DB 2210, the driver's license number stored in the customer information DB 2220, and the rental information stored in the rental information DB 2230. Information related to period and insurance subscription may be stored.

The additional information DB (2250) is information about situations that may additionally occur in relation to vehicle rental, and may store settlement-related information, recovery-related information, collection-related information, fine-related information, and insurance loan-related information, etc., as follows. It will be described in more detail with Figure 8.

The control unit 2300 may include a processor 2310, an application management unit 2320, a customer information management unit 2340, a rental vehicle billing management unit 2340, and a payment information management unit 2350. The control unit 2300 may be implemented as hardware or software. For example, the processor 2310 is implemented in hardware, the application management unit 2320, the customer information management unit 2340, the rental vehicle billing management unit 2340, and the payment information management unit 2350 include algorithms or It can be implemented in software.

The processor 2310 may control the overall operation of the vehicle rental management server 2200. For example, the processor 2310 accesses the customer information DB 2220, settlement information DB 2220, and payment information DB 2230 of the storage unit 2200, and the customer information management unit 2340. , the control unit 2300 can be driven by executing algorithms or program commands constituting the rental vehicle billing management unit 2340 and the payment information management unit 2350. Additionally, the processor 2310 may include controllers, interfaces, graphics engines, etc. that control various components of the car rental management server 2000. The processor 2310 may be provided in the form of a system-on-chip (SoC), application specific integrated circuit (ASIC), or field programmable gate array (FPGA).

The application management unit 2320 may provide a car rental application to the first customer terminal 1100 or support installation of a car rental service program. Alternatively, the application management unit 2320 may execute a car rental service program through the second customer terminal 1200. The application management unit 2320 may receive vehicle rental information from the vehicle rental management server 2000 or provide vehicle rental information through the first or second customer terminals 1100 and 1200.

The vehicle information management unit 2330 may manage vehicle information by accessing the vehicle information DB 2210 of the storage unit 2200. When a new vehicle is received at a car rental company, the vehicle information management unit 2330 may assign an ID to the new vehicle and store the new vehicle ID in the vehicle information DB 2210. The vehicle information management unit 2330 may delete vehicle information stored in the vehicle information DB 2210 when the use of an existing vehicle is terminated.

The customer information management unit 2340 can manage customer information by accessing the customer information DB 2220 of the storage unit 2200. When a new customer is registered through the first customer terminal 1100, the customer information management unit 2340 may assign an ID to the new customer and store the new customer ID and name in the customer information DB 2220. The customer information management unit 2340 may update customer information stored in the customer information DB 2220 when information about an existing customer changes. The customer information management unit 2340 may provide a means for making comments or online consultations for smooth communication with customers accessing the car rental management server 2000.

The rental information management unit 2350 may manage rental information by accessing the rental information DB 2230 of the storage unit 2200. When vehicle type and rental period information is input through the first customer terminal 1100, the rental information management unit 2350 grants a new rental ID and records the new rental ID and rental vehicle information and information in the rental information DB 2230. Rental period information, etc. can be saved. The rental information management unit 2350 may update the rental information stored in the rental information DB 2230 when the type of vehicle to be rented is changed or the rental period is changed.

The contract information management unit 2360 may manage contract information by accessing the contract information DB 2240 of the storage unit 2200. When contract details are entered through the first customer terminal 1100, the contract information management unit 2360 grants a new contract ID and records the new contract ID, customer information, vehicle information, and rental period in the contract information DB 2240. Information, rental fee information, and insurance-related information can be stored. The contract information management unit 2360 may update the contract information stored in the contract information DB 2240 when the contract details such as vehicle type, rental period, rental fee, and insurance-related content are changed.

The additional information management unit 2370 may manage additional information by accessing the additional information DB 2250 of the storage unit 2200. Additional information may include settlement-related information, recovery-related information, collection-related information, fine-related information, and insurance loan-related information, and the additional information management unit 2370 may include settlement-related information, recovery-related information, collection-related information, and fines. Additional information such as related information and insurance loan-related information can be stored, and additional information such as settlement-related information, recovery-related information, collection-related information, penalty-related information, and insurance loan-related information can be stored in the additional information DB (2250 ) You can update additional information stored in .

FIG. 5 is a flowchart exemplarily illustrating member registration and authentication methods among the operations of the customer information management unit shown in FIG. 4. Referring to FIG. 5, the customer information management unit 2340 can manage membership registration through an identity authentication process.

In step S110, the customer can register as a member using the first customer terminal 1100. Customers can access the car rental management server 2000 or sign up for membership through the car rental application 1114. The customer information management unit 2340 may request personal information such as the customer's name, date of birth, resident registration number, phone number, email, address, etc. when registering as a member. Additionally, the customer information management unit 2340 may request information on whether the customer has acquired a driver's license, driver's license number, and insurance subscription status in addition to personal information. A customer may register as a member by responding to a request provided by the customer information management unit 2340.

In step S120, the customer may perform an identity authentication process using the customer terminal 1100. Identity authentication can be performed through a mechanical method, such as simply entering personal information such as the customer's name, resident registration number, and phone number, or through a public authentication method used in banks, etc. Additionally, identity authentication can be performed through biometric authentication such as iris or fingerprint, or electronic authentication such as mobile phone authentication.

In step S130, success or failure of authentication can be determined based on the authentication information entered by the customer. The customer information management unit 2340 may determine whether authentication is successful by comparing the authentication information input by the customer with authentication information (eg, public authentication) stored in the customer information DB 2220. If identity authentication is successful, step S140 may be performed, and if it fails, step S132 may be performed.

In step S132, if authentication is not successful in step S130 (NO), the number of authentication failures can be determined. The customer information management unit 2340 may determine whether the number of customer authentication failures has been repeated N times. If the number of authentication failures has not been repeated N times, step S120 is performed. That is, the customer information management unit 2340 may guide the customer to perform the identity authentication process again. However, if the number of authentication failures is repeated N times, step S134 is performed.

In step S134, the customer information management unit 2340 may inform of authentication failure. If the customer fails to authenticate himself N times repeatedly, the customer information management unit 2340 may inform the customer that authentication has failed and terminate the identity authentication process. At this time, the customer can request the operator of the car rental management server 2000 to perform identity authentication again. Depending on the embodiment, steps (S130, S132, and S134) for determining whether authentication is successful may be omitted.

In step S140, the customer information management unit 2340 may provide a customer ID to the customer through the first customer terminal 1100. Customer ID may be used when using a car rental service program. Customer ID can be issued in the following order. Referring to the example of FIG. 5, in step S141, the customer can access the car rental management server 2000 using the first customer terminal 1100. In step S142, the customer information management unit 2340 may request customer information. The customer may input customer information (eg, email address, etc.) using the first customer terminal 1100. In step S143, the customer can enter the password. Here, the customer information and password may be the same information as the information entered in the customer registration step (S110).

FIG. 6 is a flowchart illustrating an exemplary method of operating the application management unit shown in FIG. 4. Referring to FIG. 6, the application management unit 2320 may provide a car rental application 1114 to the first customer terminal 1100 or support installation and execution of a car rental service program through the second customer terminal 1200. there is.

In step S210, the application management unit 2320 may install or execute a car rental service program on the first customer terminal 1100. The car rental service program can be stored and installed in the memory unit 1115 of the first customer terminal 1100 through a removable storage medium (for example, USB or memory card, etc.) or downloaded from the car rental management server 2000. there is. The car rental service program may include authentication data for identity verification as described in FIG. 5.

In step S220, the application management unit 2320 may determine whether installation of the program was successful. If installation of the program has failed (NO), the application management unit 2320 may inform the user of the program installation failure through the first customer terminal 1100 (S225). If the program installation is successful (YES), the application management unit 2320 may perform step S230.

In step S230, the application management unit 2320 may check whether the communication unit 2100, storage unit 2200, and control unit 2300 of the car rental management server 2000 are operating normally. The application management unit 2320 may check whether the customer can normally use the car rental application or car rental service program provided by the car rental management server 2000 using the first customer terminal 1100.

In step S231, the application management unit 2320 may check the operation of the communication unit 2100 of the car rental management server 2000. First, the application management unit 2320 may check whether the car rental management server 2000 is smoothly connected to the first or second customer terminals 1100 and 1200.

In step S232, the application management unit 2320 may check the operation of the storage unit 2200 of the car rental management server 2000. The application management unit 2320 stores the information that the storage unit 2200 receives from the communication unit 2100 into vehicle information DB 2210, customer information DB 2220, rental information DB 2230, contract information DB 2240, You can also check whether the information is stored properly in the additional information DB (2250). That is, the customer information input from the first customer terminal 1100 is stored in the customer information DB 2220, and the rental information DB 2230 stores the rental vehicle number information, information about the rental period, and information about whether to return the vehicle. It is possible to check whether the customer identification information, rental period, vehicle number, and insurance-related information on the other party to the contract are stored in the contract information DB 2240.

In step S233, the application management unit 2320 may check the operation of the control unit 2300 of the car rental management server 2000. The application management unit 2320 may check whether the processor 2310 of the control unit 2300 operates normally. The application management unit 2320 may check the operations of the customer information management unit 2340, the rental vehicle billing management unit 2350, the contract information management unit 2360, and the additional information management unit 2370. The application management unit 2320 can check whether it operates according to the car rental service program command.

FIG. 7 is a flowchart illustrating an exemplary operation method of the vehicle rental management server shown in FIG. 2. Referring to FIG. 7, the first or second customer terminal (1100, 1200) shown in FIG. 2 downloads the car rental application from the car rental management server 2000 and provides various car rental information using the car rental service program. can be provided or obtained. The car rental management server 2000 provides car rental information, and allows customers to manage a car rental service program through which they can obtain car rental information that suits them.

In step S310, the car rental management server 2000 may cause the car rental service program to be executed in the first customer terminal 1100. The first customer terminal 1100 may download a car rental application from the car rental management 2000 and execute a car rental service program. When executing a car rental service program, the identity authentication procedure described in FIG. 5 may be performed. Additionally, when a car rental service program is executed, car rental information stored in the car rental management server 2000 may be provided to the first customer terminal 1100.

In step S320, the car rental management server 2000 may receive a request for car rental information from the first customer terminal 1100. The vehicle rental management server 2000 may receive a vehicle rental information request through the input unit 2110 of the communication unit (see FIG. 4, 2100) and provide the vehicle rental information request to the storage unit 2200 or the control unit 2300. there is.

In step S330, when there is a request for vehicle rental information from the first customer terminal 1100, the vehicle rental management server 2000 analyzes the vehicle rental information and determines the type of vehicle desired by the customer, the type of vehicle, the year of the vehicle, Information such as transmission, fuel type, vehicle rental fee, rental period, etc. can be extracted.

In step S340, when there is a request for vehicle rental information from the first customer terminal 1100, the vehicle rental management server 2000 stores the vehicle information DB 2220, customer information DB 2230, and rental information in the storage unit 2200. You can search the information DB (2240) and the contract information DB (2360). The vehicle rental management server 2000 can search for vehicle number, vehicle type, fuel type, transmission type, and convenience functions through the vehicle information DB 2220. Through the customer information DB 2220, customer ID, name, resident registration number, customer terminal ID, contact information, etc. can be searched. Additionally, the vehicle rental management server 2000 may search rental status information of a vehicle at specific times in the past, present, and future through the rental information DB 2230. The vehicle rental management server 2000 can search contract information such as contract type and insurance subscription status through the contract information DB 2260.

In step S350, the vehicle rental management server 2000 may analyze vehicle rental information data using vehicle search information. When vehicle rental information is input through the first or second customer terminal (1100, 1200), the vehicle rental management server 2000 provides vehicle information DB 2210, customer information DB 2220, and rental information DB 2230. ) and vehicle rental information stored in the contract information DB 2240 can be used to analyze vehicle rental information data. Additionally, the vehicle rental management server 2000 may update vehicle rental information when existing vehicle rental information is changed.

The vehicle rental management server 2000 may calculate vehicle rental information desired by the customer from the customer information DB 2220 or settlement information DB 2220 of the storage unit 2200 using vehicle rental information analysis data. The vehicle rental management server 2000 may filter vehicle rental information to suit the customer's vehicle rental information purpose or the vehicle rental information rules of the vehicle rental information provider or school. The car rental management server 2000 can recommend car rental information optimized for the customer by analyzing car rental information patterns provided or requested by the customer.

In step S360, the car rental management server 2000 may provide a car rental information service in response to the customer's request for car rental information. The vehicle rental management server 2000 can analyze vehicle rental information and recommend optimized vehicle information to customers. The vehicle rental management server 2000 can utilize artificial intelligence (AI) or machine learning techniques to analyze customer vehicle rental information patterns and build a vehicle rental information recommendation database. The vehicle rental management server 2000 may perform operations such as displaying advertisements using vehicle rental information provided by the customer. The car rental management server 2000 can provide car rental information, such as car rental information provider or car rental information desired by the customer, to the customer through the customer output interface unit 2120.

FIG. 8 is a diagram exemplarily showing the relationship between the additional information DB and the additional information management unit shown in FIG. 4. Referring to FIG. 8, settlement-related tasks, penalty-related tasks, and insurance lending tasks can be performed by the additional information DB 2250 and the additional information management unit 2370.

The additional information DB 2250 may include a settlement information DB 2251, a penalty information DB 2252, and an insurance loan information DB 2253. The additional information DB 2250 can store settlement-related information, penalty-related information, and insurance loan-related information.

It may include a settlement information management unit 2371, a penalty information management unit 2372, and an insurance balance information management unit 2373. The additional information management unit 2370 may perform settlement processing-related tasks, penalty processing-related tasks, and insurance lending-related tasks using settlement-related information, penalty-related information, and insurance lending-related information.

The settlement information DB 2251 may store information related to vehicle rental and vehicle return. The settlement information DB (2251) stores rental classification information, vehicle number information, rental date information, expected return date information, receivables information, customer name information, number of text messages, progress status information, execution number information, and last modification date information. You can. The settlement information management unit 2371 using the settlement information DB 2251 will be described in more detail below with reference to FIG. 9.

The fine information DB 2252 may store information related to fines incurred by the customer while using the vehicle. The settlement information DB 2251 may include status classification information according to the progress of fine processing, vehicle number information that generated the fine, information on the contractor of the vehicle, information on violation of the fine, etc. In addition, the settlement information DB 2251 may include information on the jurisdiction for reporting and payment, subject name information for fine violation details, payment deadline information, and violation date and time information for when the fine was incurred. The fine information management unit 2372 using the fine information DB 2252 will be described in more detail below with reference to FIG. 10.

The insurance loan information DB 2253 may store insurance loan application information according to the insurance company's insurance loan application. Insurance rental information DB (2253) contract status information, model name information of the dispatched vehicle, vehicle number information of the dispatched vehicle, contractor information of the vehicle, rental date information, rental end date information, rental cost information, and insurance company that applied for insurance rental Information may be included. The insurance loan information management unit 2373 using the insurance loan information DB 2253 will be described in more detail below with reference to FIG. 11.

FIG. 9 is a flowchart showing a method of processing settlement information of the settlement information management unit shown in FIG. 8. Referring to FIG. 9, the settlement information management unit 2371 can manage the settlement process, vehicle recovery process, and collection process of rental costs incurred due to vehicle rental and return.

The control unit 2300 can collect vehicle information, contractor information, rental period information, and return information, and store the collected vehicle information, contractor information, rental period information, and return information in the storage unit 2200. The control unit 2300 can check return information and proceed with settlement processing if the rental vehicle is returned within the rental period. The control unit 2300 may provide rental cost information to the first or second customer terminals 1100 and 1200 for settlement processing and display the rental cost information on the screen units 1110 and 1210.

If the rental vehicle is returned beyond the rental period, the control unit 2300 may register the customer of the returned vehicle in the delinquent list. The control unit 2300 may send a first non-deposit notification to the customer of the returned vehicle when the customer is registered in the delinquent list and one month has passed. The control unit 2300 may output the first non-deposit notification to the screen units 1110 and 1210 of the first or second customer terminals 1100 and 1200.

The control unit 2300 may transmit the first non-deposit notification and, when one month has elapsed, transmit the second non-deposit notification to the customer. The control unit 2300 may output a second non-deposit notification to the screen units 1110 and 1210 of the first or second customer terminals 1100 and 1200.

The control unit 2300 may transmit a second non-deposit notification and perform collection processing. Additionally, the control unit 2300 may provide contract information to the communication unit 2100. The control unit 2300 can collect vehicle information, contractor information, rental period information, and return information. The control unit 2300 may store the collected vehicle information, contractor information, rental period information, and return information in the storage unit 2200.

In step S410, the settlement information management unit 2371 may designate a vehicle for which a settlement fee remains in relation to the rental of the vehicle as a subject of settlement management. The settlement information management unit 2371 can collect information and return information related to vehicles designated as subject to settlement management and manage them as a rental list.

In step S420, the settlement information management unit 2371 may compare the rental period of the vehicle using information on the vehicle in the rental list. If the rental is returned within the rental date (YES), the settlement information management unit 2371 can perform a process for cost settlement (S430). If the rental has been returned beyond the rental date (NO), the settlement information management unit 2371 can perform a process for cost collection (S440).

In step S430, the settlement information management unit 2371 may determine the rental cost according to the rental period and proceed with settlement processing. The settlement information management unit 2371 may receive rental fee deposit details and depositor information from the bank's information management server 3000. When payment of the rental fee is confirmed, the settlement information management unit 2371 may determine that the contract has been completed and terminate the settlement process.

In step S440, the settlement information management unit 2371 may perform a collection process for the customer in case the rental exceeds the rental date.

In step S441, the settlement information management unit 2371 may register vehicle information, information on customers who returned excess amounts, rental costs accordingly, and penalty information for excess amounts in the delinquency list for the collection process.

In step S442, the settlement information management unit 2371 may register in the delinquent list and maintain the status of the delinquent list until one month has elapsed (NO). The settlement information management unit 2371 can register in the delinquent list and check whether or not the payment has been made after one month (S443).

If the payment is confirmed (YES) in step S443, the settlement information management unit 2371 can proceed with the settlement process described above (S430). If the settlement information management unit 2371 does not confirm the deposit (NO), it can check the customer information and proceed with notification of non-deposit (S445). At this time, notification of non-deposit can be made through SMS, e-mail, vehicle rental application, vehicle rental service program, etc.

In step S446, if the non-deposit notification is the first time (NO), the settlement information management unit 2371 can proceed with steps S441 to S445 again. The settlement information management unit 2371 can proceed with collection processing if there are two or more non-deposit notifications (YES) (S447).

In step S447, the settlement information management unit 2371 may register the customer in the collection list for collection processing. The settlement information management unit 2371 can connect to and transmit the collection application form and related files to the information management server 3000 of the legal office. The settlement information management unit 2371 can connect to the bank's information management server 3000 and deposit the application fee. Additionally, the settlement information management unit 2371 may notify the fact that the transmission and reception fees for the related files have been deposited.

FIG. 10 is a flowchart showing a method of processing penalty information of the penalty information management unit shown in FIG. 8. Referring to FIG. 10, the fine information management unit 2372 can manage fines incurred by customers while using the vehicle. Here, the fine may include fines or fines.

The communication unit 2100 can collect fine management information from the outside, and store the collected fine management information in the storage unit 2200.

The control unit 2300 may compare the vehicle information of the fine management information stored in the storage unit 2200 with the vehicle number stored in the storage unit 2200. If the vehicle numbers match as a result of the comparison, the control unit 2300 can compare the penalty grant date and the rental period of the contract information. If the penalty grant date is included in the rental period of the contract information, the control unit 2300 may designate the customer stored in the contract information as the target of penalty notification. The control unit 2300 may transmit a penalty notice to the first or second customer terminal (1100, 1200) and display the penalty information on the screen units (1110, 1210).

In step S510, the fine information management unit 2372 may connect to the fine server, which is the information management server 3000, and collect fine management information. Here, the fine management information may include information on the vehicle number and the date on which the fine will occur.

In step S520, the fine information management unit 2372 may compare the vehicle number of the collected fine management information with the vehicle number of the rental information DB 2350. The fine information management unit 2372 may continue to collect fine management information (S510) if the numbers of the rental vehicle and the vehicle subject to the fine do not match (NO). If the vehicle number matches (YES), the fine information management unit 2372 can check whether the fine grant date is included in the rental period (S530).

In step S530, the penalty information management unit 2372 may continue to collect penalty management information (S510) if the penalty grant date is not included in the rental period (NO). is performed, and if the penalty grant date is included in the rental period (YES), the customer can be registered as a penalty management target (S540).

In step S550, the penalty information management unit 2372 may perform penalty processing on customers registered as subject to penalty management. The fine information management unit 2372 can remit the fine to related organizations such as local governments or police agencies. Additionally, the fine information management unit 2372 may notify the relevant customer of the fact that a fine has been issued using text, etc.

FIG. 11 is a flowchart showing a method of processing insurance loan information of the insurance loan information management unit shown in FIG. 8. Referring to FIG. 11, the insurance loan information management unit 2373 can manage vehicle rental according to the insurance company's insurance loan application. Here, insurance loan refers to a service that provides rental of the same type of vehicle during the repair period when the insured vehicle cannot be used due to an accident.

The control unit 2300 can collect insurance loan information from the outside through the communication unit 2100 and store the collected insurance loan information in the storage unit 2200.

The control unit 2300 can first check whether a vehicle has been dispatched according to the insurance rental information. If there is a dispatched vehicle as a result of the initial confirmation, the control unit 2300 can proceed with dispatching the vehicle. If no vehicle has been dispatched as a result of the first check, the control unit 2300 can check whether repairs to the accident vehicle have been completed.

If the repair of the accident vehicle has been completed, the control unit 2300 can secondarily check whether there is a dispatched vehicle. The control unit 2300 can proceed with dispatch if a vehicle has been dispatched as a result of the secondary confirmation. If no vehicle has been dispatched as a result of the secondary confirmation, the control unit 2300 may proceed with the rental completion process.

In step S610, the insurance loan information management unit 2373 may collect the insurance loan application information received from the insurance company server, which is the information management server 3000.

In step S620, when the insurance loan application is collected, the insurance loan information management unit 2373 may extract engine displacement information from the vehicle information in the insurance loan application details.

The insurance rental information management unit 2373 may check the vehicle information DB 2210 to create a list of vehicles available for rental. The insurance rental information management unit 2373 can select domestic cars with similar engine displacement from the vehicle list and designate them as rental vehicles. The insurance rental information management unit 2373 may register information about the designated rental vehicle in the rental information DB 2230.

In step S630, the insurance loan information management unit 2373 can check whether the vehicle has been dispatched. If the vehicle has been dispatched (YES), the insurance loan information management unit 2373 can proceed with dispatch (S640). The insurance rental information management unit 2373 can check whether repairs to the accident vehicle have been completed if the vehicle has not been dispatched (NO) (S660).

In step S640, when the insurance loan information management unit 2373 confirms the progress of car dispatch, it can notify the insurance company of the car dispatch so that the customer can use the car.

In step S650, the insurance rental information management unit 2373 can confirm the return of the vehicle when the vehicle rented according to the insurance rental application is returned. When the return of the vehicle is confirmed, the insurance rental information management unit 2373 may proceed with rental completion processing (S680) to finalize the contractual relationship.

In step S660, the insurance loan information management unit 2373 may check whether repairs to the accident vehicle have been completed. If the repair of the vehicle has not been completed (NO), the insurance rental information management unit 2373 can continue to check whether the vehicle has been dispatched (S630). If the repair of the vehicle has been completed (YES), the insurance rental information management unit 2373 can check again whether the vehicle has been dispatched (S670).

In step S670, the insurance loan information management unit 2373 can check once again whether the vehicle has been dispatched. If the insurance loan information management unit 2373 confirms that the vehicle has been dispatched (YES), it can proceed with dispatch (S640). If it is confirmed that the vehicle has not been distributed (NO), the insurance rental information management unit 2373 may proceed with rental completion processing (S680). The reason the rental is considered complete is because the customer can use the car that has had repairs completed.

In step S680, the insurance loan information management unit 2373 may proceed with loan completion processing. The insurance loan information management unit 2373 may transmit related data, such as a rental contract, to the information management server 3000 of the insurance company.

Figure 12 is a screen showing an example of a user interface for logging in that appears on the screen of the first customer terminal. Referring to FIG. 12, the customer terminal 1100 may provide a user interface 1300 for membership registration and login through a screen unit.

The customer terminal 1100 can receive the customer's ID into the ID input unit 1310, and the customer terminal 1100 can receive its password into the password input unit 1330. When the login selection unit 1340 is selected through the screen unit, the customer terminal 1100 can access the car rental management server 2000. The customer terminal 1100 may output a vehicle search screen or period selection screen required for vehicle rental from the vehicle rental management server 2000. The customer terminal 1100 may provide separate interfaces when the user is a general customer and when the user is a rental company manager. When the membership registration unit 1340 is selected by a user without an account, the customer terminal 1100 may provide an interface for membership registration.

Figure 13 is a screen showing the manager interface displayed on the customer terminal in Figure 12. Referring to FIG. 13, the customer terminal 1100 may provide an administrator interface 1400 when the rental company manager logs in. When the rental car company information management menu 1411 of the operation information management unit 1410 is selected, the customer terminal 1100 may provide a management menu for operation. The customer terminal 1100 may display a vehicle status management unit 1420, an insurance loan management unit 1430, a rental management unit 1440, and a detailed status management unit 1440 as management menus for operation.

When the vehicle status management unit 1420 is selected, the customer terminal 1100 can provide vehicle status information. Vehicle status information may include the number of vehicles on standby, number of vehicles under repair, number of vehicles used by employees, number of registered vehicles, and vehicle turnover rate.

When the insurance loan management unit 1430 is selected, the customer terminal 1100 may provide an insurance loan management interface. The insurance loan management interface will be explained with reference to FIG. 16.

When the rental management unit 1440 is selected, the customer terminal 1100 can provide general rental status information. General rental status information may include number of vehicles on standby, number of vehicles in repair, number of vehicles used by employees, number of registered vehicles, and statistical data.

Figure 14 is a screen illustrating a collection management interface according to an embodiment of the present invention. Referring to FIG. 14, the settlement information management unit 2371 may provide a collection management interface 1500 through the customer terminal 1100 of the car rental company manager. The customer terminal 1100 may display a collection search unit 1510 and a collection search result unit 1520 through the collection management interface 1500.

The collection information management unit 2371 can receive related information through the rent classification, period search, and search term input menus of the collection search unit 1510. The collection information management unit 2371 can search the settlement information DB 2251 using the input information. The collection information management unit 2371 may display search results on the collection search result unit 1520 of the customer terminal 1100.

The customer terminal 1100 displays rental classification information, vehicle number information, rental date and time information, expected return date information, return date and time information, uncollected amount information, customer name information, text message frequency information, progress status information, and Execution number information and last modification date information can be displayed. The customer terminal 1100 may display information that can distinguish between general rental and insurance rental in rental classification information. The customer terminal 1100 may display the number of times non-deposit notification has been made in step S445 of FIG. 9 in the text message transmission information. The customer terminal 1100 may display the progress status information as a collection progress status, one of waiting, receiving, and payment order.

Figure 15 is a screen exemplarily showing a fine management interface according to an embodiment of the present invention. Referring to FIG. 15, the fine information management unit 2372 may provide a fine management interface 1600 through the manager's customer terminal 1100. The customer terminal 1100 may display a penalty search unit 1610 and a penalty search result unit 1620 through the penalty management interface 1600.

The fine information management unit 2372 can receive related information through the status classification, period search, and search term input menus of the fine search unit 1610.

The fine information management unit 2372 may search the fine information DB 2252 using the input information. The fine information management unit 2372 may display search results in the fine search result section 1620 of the customer terminal 1100.

The customer terminal 1100 displays status classification information, vehicle number information, contractor name information, report and payment jurisdiction information, subject name, payment deadline information, payment amount information, violation date and time information, and detailed view information in the fine search result section 1620. can be displayed. The status classification information can display one of the following values: sending an official document, awaiting processing, and burdening the head office. The jurisdiction for reporting and payment indicates the administrative district that has jurisdiction over the place where the fine occurred, and the subject name indicates the reason why the fine occurred, and payment is made. The due date information indicates the end date by which the fine must be paid. Payment amount information is the amount incurred depending on the subject of the penalty, and information on the date of violation can display information about when the penalty occurred.

FIG. 16 is a screen exemplarily showing the insurance loan management interface that appears when the insurance loan management unit is selected in FIG. 13. Referring to FIG. 16, the insurance loan information management unit 2373 may provide the insurance loan management interface 1700 through the manager's customer terminal 1100. The customer terminal 1100 displays an insurance loan search unit 1710, an insurance loan search result unit 1720, an insurance loan contract display unit 1730, and an insurance loan information summary unit 1740 through the insurance loan management interface 1700. You can.

The insurance loan information management unit 2373 can receive related information through the litigation progress status classification, status classification, period search, and search word input menus of the insurance loan search unit 1710. The insurance loan information management unit 2373 can search the insurance loan information DB 2253 using the input information. The insurance loan information management unit 2373 may display search results in the insurance loan search result section 1720 of the customer terminal 1100.

The customer terminal 1100 may display contract status information, model name information, vehicle number information, policyholder information, rental date information, rental fee information, and insurance company information in the insurance loan search result section 1720. The customer terminal 1100 can receive input of any one selection information from the list displayed in the insurance loan search result unit 1720. The customer terminal 1100 can search the insurance loan information DB 2253 according to the input selection information. The customer terminal 1100 may display quotation and billing information as a search result on the insurance rental contract display unit 1730.

The customer terminal 1100 can display information on the number of waiting, receiving, and payment orders and the total number of cases in the insurance loan information summary unit 1740. Here, the number of cases information represents the results of the insurance loan information management unit 2373 searching the insurance loan information DB 2253 and collecting them.

The insurance loan information management unit 2373 may determine the information to be waiting, receiving, or payment order based on information input from the information management server 3000 of the insurance company. Here, waiting refers to a case where insurance loan application information is input. Receiving means that the vehicle management company has started processing. A payment order means that the processing has been completed and the amount to be paid from the insurance company has been confirmed. Here, collection can be carried out even in the case of a general rental rather than an insurance loan. When collection proceeds from a regular rental, it may be in any of the following statuses: waiting, receiving, or payment ordered.

The above-described details are specific embodiments for carrying out the present invention. In addition to the above-described embodiments, the present invention will also include embodiments that can be simply changed or easily changed in design. In addition, the present invention will also include technologies that can be easily modified and implemented using the embodiments. Therefore, the scope of the present invention should not be limited to the above-described embodiments, but should be determined by the claims and equivalents of this invention as well as the claims described later.

1000: Vehicle rental management system
2000: Vehicle rental management server
3000: Information management server

Claims (3)

In the vehicle rental management server that is connected to the customer terminal and exchanges data,
a communications department that receives customer information, rental information, contract information, cost information and authorization information;
a storage unit that stores customer information, rental information, contract information, cost information, and approval information provided through the communication unit; and
It includes a control unit that provides a vehicle rental service program to receive customer information, rental information, contract information, cost information, and approval information stored in the storage unit,
The control unit,
At least one vehicle information that allows the vehicle to be selected through the vehicle rental service program is displayed on the screen of the customer terminal,
When any vehicle information is selected, the available rental date for the selected vehicle is displayed on the screen of the customer terminal,
When a rental available date is selected, vehicle information and rental available dates are stored in the storage unit,
Calculate vehicle rental fee information based on vehicle information and available rental dates,
A vehicle rental management server that generates contract information when approval information is provided from the communication department. According to claim 1,
The control unit,
Collects vehicle information, contractor information, rental period information, and return information,
We will check the return information and process the settlement if the rental vehicle is returned within the rental period.
For settlement processing, rental cost information is displayed on the screen of the customer terminal,
After checking the return information, if the rental vehicle is returned beyond the rental period, the customer of the returned vehicle is registered in the delinquent list.
After registering in the delinquent list and one month has elapsed, a first non-payment notification is sent to the customer of the returned vehicle and displayed on the screen of the customer terminal,
After sending the first non-deposit notification, and when another month has elapsed, send the second non-deposit notification and display it on the screen of the customer terminal,
A vehicle rental management server that performs collection processing after sending a second non-deposit notification. According to claim 1,
The control unit,
Collects fine management information from outside through the communication department,
Compare the vehicle information in the fine management information with the vehicle number stored in the storage,
If the vehicle number matches as a result of the comparison, the penalty grant date and the rental period in the contract information are compared,
As a result of the comparison, if the penalty grant date is included in the rental period, the customer stored in the contract information is designated as the target of penalty notification,
A vehicle rental management server that transmits fine management information through the communication unit and outputs fine management information on the screen of the customer terminal.