JP2024019759A - System for supporting car sharing between individual, method, and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it possible to consecutively perform car rental on fixed days of the week or on a monthly basis to a same user not by spot lending of single shot or incidental lending.

SOLUTION: A system: stores owner registration information being input from an owner terminal 30 and user registration information being input from a user terminal 40; searches for the owner registration information on the basis of search information transmitted from the user terminal 40; extracts corresponding vehicle information and transmits the vehicle information to the user terminal 40; transmits usage application information, when receiving vehicle usage application information from the user terminal 40, to the owner terminal 30; generates usage contract information, when receiving lending permission information from the owner terminal 30, on the basis of the usage application information and the lending permission information, and transmits them to the owner terminal 30 and the user terminal 40; and sets, as the usage contract information, a vehicle lending period as a period in which at least one day of the week is fixed on a weekly basis and the day of the week is set as a period in which the vehicle is repeatedly rented.

SELECTED DRAWING: Figure 2

COPYRIGHT: (C)2024,JPO&INPIT

Description

The present invention relates to a technology for supporting car sharing between individuals between an owner who wishes to rent a vehicle and a user who wishes to use the vehicle.

2. Description of the Related Art In recent years, car sharing (car sharing), in which a plurality of users share a car, such as user members who have registered as members, has become commonplace.
Particularly in recent years, with the spread and expansion of the Internet, smartphones, SNS, etc., car enthusiasts and other car owners are now allowing car owners and car users to directly lend and borrow cars (shared use). ) There is a growing need for interpersonal car sharing.

For example, we focus on the needs of wanting to drive or rent a luxury car, and by acting as an intermediary between luxury vehicle owners and users who like luxury cars, we offer individual spot rentals and generous car insurance for luxury cars. An individual car sharing service has been proposed that provides such contracts.
As a technology to support this type of personal car sharing, for example, Patent Document 1 describes a "share support device and share support device" that allows drivers and owners to confirm information regarding automobile insurance in personal car sharing. method is proposed.

JP2020-201648A

However, car sharing between individuals to date, including the method disclosed in Patent Document 1, has been aimed at spot rental in which the user pinpoints a specific date and time when he or she wishes to use the vehicle. Applications and contracts had to be made individually each time.
For this reason, not only are procedures for applying and signing a contract, including signing up for automobile insurance, complicated, but usage fees and insurance premiums are also relatively high, and it cannot be said to be user-friendly.

In addition, with pinpoint spot lending based on user applications, vehicle owners cannot expect stable sales due to continuous rental, and it is impossible to predict the occurrence of applications and rental dates and timings. There were also concerns about renting out on a spot basis to users, and it was not easy to use.

The present invention was proposed to solve the above-mentioned problems, and instead of one-off or accidental spot rental, the present invention allows the same user to use the vehicle continuously on a fixed day of the week on a monthly basis. By making this possible, owners can eliminate the hassle of renting and borrowing each time, the anxiety of renting to an unspecified number of people, and the high cost of usage fees and car insurance premiums, which have been associated with personal car sharing to date. The purpose of the present invention is to provide a personal car sharing support system, method, and program that realize personal car sharing that is easy to use for both users and users.

In order to achieve the above object, the personal car sharing support system of the present invention is a system for supporting personal car sharing between an owner who wishes to rent a vehicle and a user who wishes to use the vehicle. and an individual car sharing device communicably connected to an owner terminal used by the owner and a user terminal used by the user, and the individual car sharing device receives input from the owner terminal. , storage means for storing predetermined owner registration information regarding the owner including predetermined vehicle information of the vehicle and predetermined user registration information regarding the user input from the user terminal; a search extraction means for searching the owner registration information based on the search information and extracting the corresponding vehicle information; and transmitting the extracted vehicle information to the user terminal, and transmitting the vehicle information from the user terminal. When receiving predetermined usage application information, a transmitting/receiving means transmits the usage application information to the owner terminal, and when receiving predetermined lending permission information regarding the usage application information from the owner terminal, the usage application information and the rental contract information generation means for generating predetermined usage contract information based on permission information; the transmitting/receiving means transmits the usage contract information to the owner terminal and the user terminal; As the usage contract information, the rental period of the vehicle is set to be a fixed period of at least one day of the week on a weekly basis, and the day of the week is set as a period during which the vehicle is repeatedly rented.

Further, the present invention can be configured as an individual car sharing support method executed by the individual car sharing support system according to the present invention as described above.
Furthermore, the present invention can also be configured as a personal car sharing support program for executing the personal car sharing support system and method according to the present invention as described above.

According to the present invention, instead of one-off or accidental spot lending, it becomes possible to continuously use and lend to the same user on a fixed day of the week on a monthly basis.
This will eliminate the hassle of car sharing between individuals, the anxiety of renting to an unspecified number of people, and the high cost of usage fees and car insurance premiums. It becomes possible to realize interpersonal car sharing that is convenient for both parties.

BRIEF DESCRIPTION OF THE DRAWINGS FIG. 1 is an explanatory diagram schematically showing the overall configuration of an interpersonal car sharing support system (this system) according to an embodiment of the present invention. FIG. 2 is a functional block diagram showing the configuration of each part in this system. FIG. 2 is an explanatory diagram showing an example of data stored in a database (storage unit) in the present system. FIG. 2 is a sequence diagram showing the flow of processing by the interpersonal car sharing support system in this system. FIG. 5 is a sequence diagram continuing from FIG. 4 and showing the flow of processing by the interpersonal car sharing support system in the present system. FIG. 2 is an explanatory diagram showing the transition of display screens displayed on the owner terminal/user terminal in this system. FIG. 7 is an explanatory diagram continuing from FIG. 6 and showing the transition of display screens displayed on the owner terminal in the present system. FIG. 7 is an explanatory diagram continuing from FIG. 6 and showing the transition of display screens displayed on the user terminal in the present system. FIG. 9 is an explanatory diagram continuing from FIG. 8 and showing the transition of display screens displayed on the user terminal in the present system. 7 is an explanatory diagram showing the transition of display screens displayed on the owner terminal in the present system, continuing from FIG. 7. FIG. 10 is an explanatory diagram showing the transition of display screens displayed on the owner terminal in this system, continuing from FIG. 10. FIG. FIG. 2 is a block diagram showing the hardware configuration of a server, an owner terminal, and a user terminal in this system.

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, embodiments of an interpersonal car sharing support system, method, and program according to the present invention will be described with reference to the drawings.
Here, each device constituting the personal car sharing support system (this system) for implementing the personal car sharing support method according to the present invention described below is executed by a computer according to instructions of a program (software). Realized by processes, means, and functions.
The program can send commands to each component of the computer to cause it to perform the following processes and functions according to the present invention. That is, each process, means, and function in the present invention is realized by specific means in which a program and a computer cooperate.

Note that all or part of the program is provided by, for example, a magnetic disk, optical disk, semiconductor memory, or any other computer-readable recording medium, and the program read from the recording medium is installed on the computer and executed. Ru. Further, the program can also be directly loaded and executed on a computer through a communication line without using a recording medium.
In addition, the system is composed of a device group consisting of a plurality of information processing devices, and the system includes a computer that becomes a "server" (individual car sharing support device), which will be described later, an "owner terminal" and a "user terminal". Smartphones, tablet terminals, PCs, etc. that can be However, any information processing device in the device group constituting the “system” may be a single device or a common device.

In addition, as shown in FIG. 12, each information processing device included in the device group constituting this system has hardware including a CPU 301, RAM 302, ROM 303, HDD 304, input device 305, display device (display) 306, communication IF 307, etc. Consists of wear. These components are connected by a system bus, and data is exchanged via the system bus. A CPU (Central Processing Unit) 301, also called a central processing unit, is a part that performs central processing of a computer, and controls each device and calculates and processes data. RAM (Random Access Memory) 302 is a type of memory device, and data can be erased and rewritten. A ROM (Read Only Memory) 303 is a type of memory device using a semiconductor or the like, and data can be written only once during manufacture, and recorded data can only be read when used. The HDD (Hard Disk Drive) 304 is an auxiliary storage device that records and reads information using the properties of magnetic material. The input device 305 is used by the user to issue operating instructions to the computer or to input characters, etc., and specifically includes a keyboard, a mouse, and the like. The display device 306 is composed of, for example, a liquid crystal display. Each device in this system may include a device having a touch panel function in which an input device 305 and a display device 306 are integrated. Further, it can also be provided with a communication function (communication IF 307) that enables communication with other terminals, information processing devices, and the like. A communication IF (Interface) is a device for communicating with other devices according to a predetermined communication standard, and includes, for example, a NIC (Network Interface Card).

[System configuration]
As shown in FIG. 1, a personal car sharing support system 1 (hereinafter referred to as "this system 1") according to an embodiment of the present invention includes a server 10 serving as a personal car sharing support device, and one or more It includes an owner terminal 30 (30-1 to 30-n) and one or more user terminals 40 (40-1 to 40-n).
The server 10, the owner terminal 30, and the user terminal 40 are connected to each other via the Internet 100, which includes networks such as a LAN (Local Area Network) and a WAN (Wide Area Network), and are capable of data communication with each other.

Here, in this system 1, the targets of personal car sharing support are the owner of the vehicle (automobile) and the user who wishes to use the vehicle (automobile). A member owner/member user who has registered predetermined owner information/user information with .
That is, the present system 1 mediates between an owner who wishes to rent a vehicle and a user who wishes to use the vehicle via an owner terminal 30 owned by the owner and a user terminal 40 owned by the user. It provides technology and services to support the use of car sharing and the conclusion of contracts between individuals.

In this system 1, the server 10, the owner terminal 30, and the user terminal 40 are realized by information processing devices installed and operated by different organizations/companies, communication terminals used by individuals, and the like.
For example, the server 10 is an information processing device operated by a company that provides this system 1 as a service to customers (owners/users), and the owner terminal 30/user terminal 40 is an information processing device operated by a company that provides this system 1 as a service to customers (owners/users). It consists of smartphones, mobile phone terminals, tablet terminals, etc. owned by the individual owner/user receiving the provision.

[server]
The server 10 is an information processing device that is the core of the system 1 and provides support services for personal car sharing to owners who wish to rent a vehicle and users who wish to use a vehicle.
Although the server 10 will be described as one information processing device in this embodiment, it may be configured with two or more information processing devices. For example, the server 10 may be realized by a server computer, a personal computer, a server system consisting of one or more virtual servers built on a cloud computing service, or the like.

Predetermined programs (referred to as server programs) such as an OS (Operating System), a DBMS (Data Base Management System), and application programs are installed in the server 10 .
The server 10 publishes and provides available applications, for example in the form of API (Application Programming Interface), to one or more owner terminals 30 and user terminals 40 via a network such as the Internet 100.
Further, the server 10 can be communicably connected to an insurance company system 50 and a payment company system 60 outside the present system, which will be described later, via a network such as the Internet 100 (see FIG. 1).

Specifically, as shown in FIG. 2, the server 10 according to the present embodiment includes a transmitting/receiving section 11, a search extraction section 12, a contract information generation section 13, a key delivery information generation section 14, a billing information generation section 15, and A storage section 20 is provided.
These units are an example of the search extraction unit 12, the contract information generation unit 13, the key delivery information generation unit 14, and the billing information generation unit 15 when the CPU 301 is executing the server program shown in FIG. , the CPU 301 and the communication IF 307 are examples of the transmitting/receiving section 11, and at least one of the RAM 302 and the HDD 304 is an example of the storage section 20.
Each part of the server 10 will be specifically explained below.

[Transmission/reception section]
The transmitting/receiving unit 11 is a receiving unit that receives various information transmitted from the owner terminal 30 operated by the owner and various information transmitted from the user terminal 40 operated by the user.
Further, the transmitting/receiving unit 11 is a transmitting means that transmits various information generated by the server 10 to the corresponding owner terminal 30/user terminal 40.
This transmitting/receiving section 11 functions as a transmitting/receiving means according to the present invention.
Specifically, the transmitting/receiving unit 11 receives predetermined owner registration information transmitted from the owner terminal 30 and predetermined user registration information transmitted from the user terminal 40. The received owner/user registration information is generated and registered as predetermined database information in the storage unit 20 as described later (see FIG. 3).

The transmitting/receiving unit 11 also receives predetermined search information, which will be described later, transmitted from the user terminal 40, and extracts predetermined vehicle information extracted by the search extraction unit 12, which will be described later, based on the received search information. The information is sent to the user terminal 40 that sent the information.
The transmitting/receiving unit 11 also receives predetermined usage application information, which will be described later, transmitted from the user terminal 40, and transmits the usage application information to the owner terminal 30 of the owner of the corresponding vehicle.
The transmitting/receiving unit 11 also receives predetermined rental permission information regarding usage application information from the owner terminal 30, and transfers predetermined usage contract information generated based on the usage application information/lending permission information to the corresponding owner terminal. 30/Send to user terminal 40.

Further, the transmitting/receiving section 11 transmits predetermined key handing over information generated by a key handing over information generating section 14, which will be described later, to the corresponding owner terminal 30 or user terminal 40.
Further, the transmitting/receiving unit 11 transmits predetermined billing information generated by a billing information generating unit 15, which will be described later, to the corresponding user terminal 40.
The transmitter/receiver 11 provides useful personal car sharing information between an owner who wishes to rent a vehicle and a user who wishes to use the vehicle.

[Search extraction part]
The search extraction unit 12 is a means for searching owner registration information stored in the storage unit 20 based on search information transmitted from the user terminal 40 and extracting corresponding vehicle information. This search and extraction section 12 functions as a search and extraction means according to the present invention.
Specifically, when predetermined search information transmitted from the user terminal 40 is received in the above-mentioned transmitting/receiving unit 11, the search extraction unit 12 stores the search information in the storage unit 20 based on the received search information. Search data and extract predetermined vehicle information.

Here, the predetermined search information processed by the search extraction unit 12 is information input and transmitted via the user terminal 40 by a user who wishes to use the vehicle, such as the location where the vehicle is to be used, the desired location, etc. There is information such as vehicle type and day of use.
Further, the predetermined vehicle information that is searched and extracted based on the search information includes, for example, information such as vehicle types, storage locations, available dates and times that match the search information.
The vehicle information searched and extracted by the search extraction unit 12 is transmitted to the corresponding user terminal 40 via the transmission/reception unit 11, and is provided as car sharing information for users who wish to use the vehicle.

[Contract information generation department]
The contract information generation unit 13 generates predetermined usage contract information based on the predetermined usage application information transmitted from the user terminal 40 and the predetermined lending permission information for the usage application information transmitted from the owner terminal 30. It is a means. This contract information generation unit 13 functions as contract information generation means according to the present invention.
Specifically, when the rental permission/disapproval information transmitted from the owner terminal 30 is received, the contract information generation unit 13 “permits/disallows” the rental of the corresponding vehicle to the user related to the usage application information. The matching judgment process is executed as follows.
If the result of this matching determination is "Rental not permitted (matching not established)", the contract information generation unit 13 generates predetermined information indicating the "Rental not permitted", and sends the information to the corresponding user via the transmitter/receiver 11. It is transmitted to the terminal 40.
On the other hand, if the matching determination result is "rental permission (matching established)", the contract information generation unit 13 generates predetermined shared usage contract information.

The usage contract information generated and output by the contract information generation unit 13 is a contract specifying predetermined items and contents in accordance with a "shared usage contract" concluded between the owner who lends the vehicle and the user who rents the vehicle. It is information.
The usage contract information generated and output by the contract information generation section 13 is transmitted to both the corresponding owner terminal 30/user terminal 40 via the transmitting/receiving section 11, so that the information regarding the corresponding vehicle can be exchanged between the owner/user. A joint usage agreement will be concluded and established.

Here, the predetermined usage application information is information that a user who applies for the use of a vehicle inputs and transmits via the user terminal 40, such as the user's name, address, telephone number, identification information of the vehicle to be used, There is information such as the period of use and days of the week.
Further, the predetermined rental permission information is information that is input and transmitted via the owner terminal 30 by the owner who has approved and permitted the rental of the vehicle, such as identification information indicating the corresponding usage application information, and information indicating permission to rent the vehicle. There is information such as vehicle identification information, permit period, and permit days.
Further, the predetermined usage contract information is information indicating the contents of the vehicle joint usage contract concluded between the owner/user, such as the name, address, and telephone number of the owner/user, and identification information of the vehicle to be used. , usage period, usage days, and other information.

In this system 1, as usage contract information generated by the contract information generation unit 13, the vehicle rental period is set to be a fixed period of at least one day of the week on a weekly basis, and that day of the week is repeatedly used as the period during which the vehicle is rented. It is now set as .
For example, the rental period (shared use period) of the vehicle may be "6 months/every Saturday and Sunday" or "12 months/every Monday to Friday", or the rental period may be "monthly/fixed days of the week". It is now set with .
By setting a monthly/fixed day of the week rental period, you can eliminate the complexity of contracting each time you rent a spot by pinpointing a specific date and time, and create an easy-to-use car rental system. It will be possible to conclude a fair ring contract.

By being able to make such a "monthly/fixed day of the week" contract, users can rent out the vehicle they want to use continuously and only on the days of the week they want and on the days they need it.
In addition, for the owner, stable sales can be expected as the rental can be continued to the same user on a monthly or day-of-week basis, and the anxiety of renting to an unspecified number of users is eliminated. Owners can also use the vehicle on certain days of the week.
This makes it possible to realize interpersonal car sharing that is easy to use and has excellent convenience and benefits for both the owner who wishes to rent a vehicle and the user who wishes to use the vehicle.

Further, in this system 1, the contract information generation unit 13 is configured to set an automobile insurance premium calculated on a monthly basis, which is the rental period of the vehicle, as usage contract information.
In other words, with this system 1, you can take out car insurance for a fixed period of time on a monthly basis, rather than a one-off car insurance contract that you had to take out each time you rent a spot. It becomes possible to receive discounts, set usage fees including insurance premiums at reasonable prices, and provide a car sharing service that is particularly beneficial to users.

Note that this monthly automobile insurance premium is calculated by an insurance company system 50 (for example, a non-life insurance company) outside this system, which will be described later, and which is connected to this system 1 (server 10) via a network such as the Internet 100. The necessary information and data are provided to the system 1 from the above (see FIG. 1).

[Key delivery information generation section]
The key delivery information generation unit 14 is a means for generating predetermined key delivery information based on the owner registration information stored in the storage unit 20. This key delivery information generation unit 14 functions as an inspection key delivery information generation means according to the present invention.
Specifically, the key delivery information generation unit 14 is configured to generate physical key shipping request information to be sent to the owner terminal 30 and electronic key information to be sent to the user terminal 40 as the key delivery information.

Here, the physical key shipping request information, which is the predetermined key delivery information, refers to, for example, the physical key of the vehicle (automobile key) transmitted to the owner terminal 30 of the owner of the vehicle with which the usage agreement has been concluded. There is information for requesting shipping, mailing, etc. to users who use .
As will be described later, in response to this physical key shipping request information, information indicating the shipping destination, shipping date and time, shipping method, etc. for the physical key of the requested vehicle may be generated at the owner terminal 30. The information is sent to the server 10 as physical key delivery information, and then sent to the corresponding user terminal 40 via the server 10. Therefore, the physical key transfer information generated and transmitted by the owner terminal 30 can also be included in the predetermined key transfer information in the present system 1.

Further, electronic key information, which is predetermined key delivery information, is transmitted to the user terminal 40 using the vehicle with which a usage agreement has been concluded, and is read by a reading device installed in the vehicle, for example, to lock the vehicle. There is information such as barcodes, two-dimensional codes, authentication codes, etc. for unlocking. In this case, the vehicle can be used, driven, etc. using a physical key provided inside the unlocked vehicle (for example, inside the glove box). Furthermore, as the key delivery information of this system 1, for example, the information stored in the IC chip of the user's license, the information of the registered credit card, etc. can be read by the vehicle's reader, etc. to unlock and unlock the vehicle. Information that notifies the user that locking is possible can also be used as electronic key information.
In this way, the key delivery information generated and output by the key delivery information generation unit 14 is transmitted to the corresponding owner terminal 30 and user terminal 40 via the transmission/reception unit 11, so that the vehicle key (key) will be provided to the user, and the user will be able to use the corresponding vehicle according to the contract details.

[Billing information generation section]
The billing information generation unit 15 is a means for calculating the fuel cost of the vehicle used by the user associated with the user terminal 40 based on predetermined mileage information input from the user terminal 40, and generating predetermined billing information. It is. This billing information generating section 15 functions as billing information generating means according to the present invention.
Specifically, the predetermined billing information generated and output by the billing information generation unit 15 indicates the vehicle usage fee, which is aggregated and calculated on a monthly basis, for example, and is transmitted to the user terminal 40 using the vehicle. It is information.

In this system 1, the billing information generation unit 15 determines the vehicle used by the user associated with the user terminal 40 based on predetermined mileage information (mileage information before use/use number) input from the user terminal 40. The fuel cost is calculated and the fuel cost is sent to the user terminal 40 as billing information. The fuel cost for this vehicle is calculated, for example, from average fuel consumption data of the vehicle.
Further, the billing information generated by the billing information generation unit 15 can include, for example, the automobile insurance premium for the vehicle calculated on a monthly basis. As described above, this automobile insurance premium can be obtained from an insurance company system outside of this system as insurance premium data based on the insurance period and target vehicle.
The key delivery information generated and output by the billing information generation unit 15 is transmitted to the corresponding user terminal 40 via the transmission/reception unit 11, so that the user who used the vehicle can, for example, pay the monthly usage fee. Payment processing will be performed, for example, payment/settlement processing using a credit card.

For example, for payment of usage fees and settlement processing performed on a monthly basis, a payment company system 60 (for example, (Credit card company) provides the system 1 with necessary information and data indicating the details of processed payments and settlements (see FIG. 1).

[Storage]
The storage unit 20 is a storage unit according to the present invention in which information regarding owners/users to be managed by the system 1 is managed as a database.
The storage unit 20 stores predetermined information necessary for the operation of the system 1.
Specifically, the storage unit 20 stores, as various information resources, registration information for identifying each owner and user to be managed in this system 1, and vehicle joint use contracts concluded between owners and users. contract information regarding the vehicle, mileage information of the vehicle for calculating the usage fee to be paid by the user to the owner, etc. are stored.
The storage unit 20 also stores drawing data necessary for generating and displaying display screens (see FIGS. 6 to 11) displayed on display means such as the display of the owner terminal 30 and user terminal 40, which will be described later. .

Necessary information is read out, added to, or updated from time to time as the system 1 operates.
That is, the storage unit 20 stores various types of information, including predetermined owner registration information regarding the owner including predetermined vehicle information regarding the vehicle inputted from the owner terminal, and predetermined user registration information regarding the user inputted from the user terminal. Information is stored, and data is added and updated at any time depending on the usage status of the vehicle, contract status, etc. of each owner or user.
Furthermore, when information is transmitted from each owner terminal 30 or user terminal 40 to the server 10 via a network such as the Internet 100, data is added and updated as needed in the storage unit 20 according to the information. be done.

Specifically, the information stored in the storage unit 20 is information related to personal car sharing between each owner and user as described above, which is managed by the present system 1. For example, FIGS. 2 and 3 As shown in the figure, there are various types of information stored in the owner information DB 21, user information DB 22, contract information DB 23, and mileage information DB 24.
Note that the information stored in the storage unit 20 shown below is an example of information to be processed in this system 1, and is not limited to the following information, but may be information necessary for this system 1. It goes without saying that you can add, delete, change, etc.

Specifically, the configurations of the owner information DB 21, user information DB 22, contract information DB 23, and mileage information DB 24 are as follows, for example.
[Owner information DB]
The owner information DB 21 generates and stores necessary information based on predetermined owner registration information including predetermined vehicle information input and transmitted from the owner terminal 30.
The owner registration information input and transmitted from the owner terminal 30 includes, for example, the owner's name, date of birth, address, telephone number, email address, password, vehicle model, model year, rental period, rental days, and key. There is information such as delivery conditions.
The information generated and stored in the owner information DB 21 based on such owner registration information includes, for example, information indicating the following items and contents, as shown in FIG. 3(a).
1: Owner ID
2: Vehicle ID
3: Monthly usage fee (insurance fee included)
4: Location information 5: Key handover conditions 6: Vehicle type 7: Rental days 8: Other

[User information DB]
The user information DB 22 generates and stores necessary information based on predetermined user registration information input and transmitted from the user terminal 40.
The user registration information input and transmitted from the user terminal 40 includes, for example, the user's name, date of birth, address, telephone number, e-mail address, and password.
The information generated and stored in the user information DB 22 based on such user registration information includes, for example, information indicating the following items and contents, as shown in FIG. 3(b).
1: User ID
2: User name 3: Email address 4: Password 5: Other

[Contract information DB]
The contract information DB 23 stores information related to usage contracts concluded between owners and users.
As shown in FIG. 3C, the information stored in the contract information DB 23 includes, for example, information indicating the following items and contents.
1: Owner ID
2: User ID
3: Vehicle ID
4: Monthly usage fee 5: Key delivery conditions 6: Contract day 7: Contract start date 8: Insurance status confirmation check date 9: Final payment completion date 10: Joint contract PDF
11: Others

[Mileage distance information DB]
The mileage information DB 24 stores information related to the mileage of the vehicle that is input and transmitted from the user terminal 40.
As shown in FIG. 3(d), the information stored in the mileage information DB 24 includes, for example, information indicating the following items and contents.
1: Owner ID
2: User ID
3: Vehicle ID
4: Distance meter at start 5: Distance meter at end 6: Mileage 7: Others

Based on the data stored in the storage unit 20 as described above, the processing operations shown in FIG. 2 are executed by each unit, and the support service for personal car sharing is provided to the target owner/user.
The specific functions and operations of the server 10 according to the present embodiment will be described later with reference to examples of display screens displayed on the owner terminal 30 and the user terminal 40 (see FIGS. 6 to 11).

[Owner terminal]
The owner terminals 30 (30-1 to 30-n) are connected to the server 10 via a network such as the Internet 100 and are operated by owners who provide or rent vehicles via the system 1, such as smartphones or the like. It can be configured by one or more information processing devices such as a tablet terminal or a notebook PC.

Specifically, the owner terminal 30 includes a reception section 31, a transmission section 32, a display section 33, and a reception section 34. The owner terminal 30 includes the hardware configuration shown in FIG. 12 described above. In a state where the CPU 301 shown in FIG. 12 is executing a program (referred to as an owner program) that operates on the owner terminal 30, the CPU 301 and the communication IF 307 are examples of the transmitter 32 and the receiver 34, and the CPU 301 and the input device 305 are This is an example of the reception section 31, and the CPU 301 and the display 306 are examples of the display section 33.
Through such an owner terminal 30, the owner of the vehicle using the owner terminal 30 accesses the server 10 via the Internet 100, and obtains the above-mentioned predetermined owner information, usage application information, rental permission information, and usage information. Various necessary information such as contract information and key delivery information (physical key shipping request information) can be sent or received, and can be output or displayed.

Each part of the owner terminal 30 will be explained.
The reception unit 31 receives an operation signal indicating an operation by the owner. The reception unit 31 receives, for example, a signal indicating an application startup operation or an input operation for the application.
The transmitter 32 transmits various information to the server 10 based on the operation signal received by the receiver 31. Specifically, predetermined owner information, lending permission information, physical key delivery information, etc. can be transmitted.
The display unit 33 generates and displays a screen based on the operation signal received by the reception unit 31. For example, the display unit 33 can display usage application information, usage contract information, key delivery information (physical key shipping request information), etc. received from the server 10 on the screen in response to the owner's input operation.
The receiving unit 34 receives various pieces of information transmitted from the server 10, such as usage application information, usage contract information, and key delivery information (physical key shipping request information). Further, the receiving unit 34 has, for example, a function of a GPS receiver, and can acquire information indicating a position based on a GPS signal transmitted from a GPS satellite (not shown).

[User terminal]
The user terminals 40 (40-1 to 40-n) are connected to the server 10 via a network such as the Internet 100, and are operated by a user who receives the use or provision of a vehicle via the system 1, such as a smartphone or the like. It can be configured by one or more information processing devices such as a tablet terminal or a notebook PC.

Specifically, the user terminal 40 includes a reception section 41, a transmission section 42, a display section 43, and a reception section 44. The user terminal 40 includes the hardware configuration shown in FIG. 12 described above. In a state where the CPU 301 shown in FIG. 12 is executing a program (referred to as a user program) that operates on the user terminal 40, the CPU 301 and the communication IF 307 are examples of the transmitter 42 and the receiver 44, and the CPU 301 and the input device 305 are This is an example of the reception unit 41, and the CPU 301 and the display 306 are examples of the display unit 43.
Through such a user terminal 40, a user who wishes to use a vehicle that uses the user terminal 40 accesses the server 10 via the Internet 100 and enters the above-mentioned predetermined user information, usage application information, and usage information. Various necessary information such as contract information and key delivery information (electronic key information) can be sent or received, and can be output or displayed.

Each part of the user terminal 40 will be explained.
The receiving unit 41 receives an operation signal indicating an operation by a user. The reception unit 41 receives, for example, a signal indicating an application startup operation or an input operation for the application.
The transmitter 42 transmits various information to the server 10 based on the operation signal received by the receiver 41. Specifically, predetermined user information, search information, usage application information, etc. can be transmitted.
The display unit 43 generates and displays a screen based on the operation signal received by the reception unit 41. For example, the display unit 43 can display vehicle information, usage contract information, key delivery information (electronic key information, physical key delivery information), etc. received from the server 10 on the screen in response to a user's input operation.
The receiving unit 44 receives various information transmitted from the server 10, such as vehicle information, usage contract information, and key delivery information (electronic key information, physical key delivery information). Further, the receiving unit 44 has, for example, a function of a GPS receiver, and can acquire information indicating a position based on a GPS signal transmitted from a GPS satellite (not shown).

[Insurance company system/payment company system]
The insurance company system 50 and the payment company system 60 are devices/systems outside the present system that are communicably connected to the present system 1 (server 10) via a network such as the Internet 100 (see FIG. 1).
The insurance company system 50 is an information processing system operated by, for example, a non-life insurance company that provides and sells automobile insurance. It now provides information and data showing car insurance premiums calculated on a monthly basis based on contract information.

The payment company system 60 is, for example, an information processing system operated by a credit card company that provides online payment services, and is a usage contract concluded between the owner/user for this system 1 (billing information generation unit 15). Based on the information, it provides information and data showing monthly usage fee payments and settlement processing.
Note that the insurance company system 50/settlement company system 60 is an existing system that can be accessed via the Internet 100, etc., and if it can sell and provide automobile insurance and provide online payment services, the system configuration and functions are particularly important. etc., there is no limitation and the configuration is outside the scope of this system, so a detailed explanation will be omitted.

[motion]
Next, specific processing and operation (implementation of the interpersonal car sharing support system) in the present system 1 as described above will be explained with reference to FIGS. 4 to 11.
In this system 1, by executing a series of processing operations in each part described above, the vehicle is connected to the owner who wishes to rent the vehicle via the owner terminal 30 owned by the owner and the user terminal 40 owned by the user. By sending and receiving the information necessary for a vehicle sharing contract with a user who wishes to use the vehicle, individuals can quickly and easily use and conclude a contract for car sharing on a "monthly/fixed day of the week" basis. It will be carried out smoothly.

Specifically, with reference to FIGS. 4 to 5 and FIGS. 6 to 11, the overall flow of data processing in the present system 1 and specific input operations and display contents on the owner terminal 30/user terminal 40 will be explained. do.
4 and 5 are sequence diagrams showing the flow of a series of processes in the personal car sharing support system in the present system 1.
6 to 11 are explanatory diagrams showing the transition of display screens displayed on the owner terminal 30 in the present system 1.

As a premise, the owner/user of this system 1 operates his own owner terminal 30/user terminal 40 to implement and install an application program to be started and executed in this system 1 on the owner terminal 30/user terminal 40. , the system 1 is accessed by starting the application.
At the owner terminal 30/user terminal 40, for example, it is possible to log in to the system 1 by starting an application and inputting a login ID and password registered in the application.
Then, via this system 1, programs stored in each of the server 10, owner terminal 30, and user terminal 40 are started, and the functions provided by this system 1 are executed and utilized as follows. I can do it.

≪Registration flow≫
First, the "registration flow" of the owner/user in this system 1 will be explained.
In the registration flow in this system 1, as shown in FIG. and enters predetermined owner registration information (step S402). As mentioned above, the owner registration information to be entered here includes, for example, the owner's name, date of birth, address, telephone number, email address, password, vehicle model, model year, rental period, rental days, and key. There is information such as delivery conditions.
The input owner registration information is transmitted from the owner terminal 30 to the server 10 of this system 1 (step S403).

Similarly, a user who wishes to use the vehicle operates the user terminal 40 to start the application of this system 1 (step S404), logs in to this system 1, and inputs predetermined user registration information ( Step S405). As described above, the user registration information to be input here includes, for example, the user's name, date of birth, address, telephone number, e-mail address, and password.
The input user registration information is transmitted from the user terminal 40 to the server 10 of the system 1 (step S406).

The server 10 receives the owner/user registration information transmitted from the owner terminal 30/user terminal 40 (step S407), and executes storage/registration processing as database information in the storage unit 20 (step S408).
The owner/user registration information registered in the server 10 in this manner is published as personal car sharing support information published via the Internet 100, for example, in the form of a list of vehicles available for rent/map information, etc. (Step S409).
Therefore, the owner/user who has accessed this system 1 can freely browse and refer to vehicle information that can be car-shared in this system 1.

FIGS. 6(1) to (4) show examples of transition screens in the registration flow displayed on the owner terminal 30/user terminal 40.
As shown in the figure, by operating the owner terminal 30/user terminal 40, the owner/user can (1) log in to the system 1 by clicking on a web link, and (2) e-mail You can enter your address, password, etc., (3) you can also enter predetermined profile information, and (4) you can enter and send the security authentication code notified by this system 1. The inputted predetermined owner registration information/user registration information can be transmitted and registered in the system 1.

FIGS. 7(5) to (9) show examples of transition screens in the registration flow that are displayed on the owner terminal 30 subsequent to FIG. 6(4).
As shown in the figure, the owner operates the owner terminal 30 to enter and send (5) a telephone number and (6) the above-mentioned authentication code as security authentication information for further registration. For example, you can enter information such as (7) personal profile, driver's license, face photo, (8) basic information about the vehicle to be lent, and (9) vehicle inspection certificate image and bank account information. The information can be transmitted and registered in this system 1 as predetermined owner registration information.

FIGS. 8(5) to 8(8) show examples of transition screens in the registration flow that are displayed on the user terminal 40 subsequent to FIG. 6(4).
As shown in the figure, the user operates the user terminal 40 to enter and send (5) a telephone number and (6) the above-mentioned authentication code as security authentication information to further register. As information, for example, (7) driver's license image and credit card information, (8) detailed profile information, etc. can be input, and this input information is sent to this system 1 as predetermined user registration information.・Can be registered.

≪Matching flow≫
Next, the "matching flow" between owners and users in this system 1 will be explained.
In the matching flow in this system 1, as shown in FIG. 4, first, a user who desires to use a vehicle operates the user terminal 40 and inputs predetermined search information (step S410). As described above, the search information input here includes, for example, information such as the location where the user uses the vehicle, the desired vehicle type, and the day of the week of use.
The input search information is transmitted from the user terminal 40 to the server 10 of the system 1 (step S411).

The server 10 receives the search information transmitted from the user terminal 40 (step S412), and the search extraction unit 12 executes a search process based on the database information stored in the storage unit 20 (step S413) to find the corresponding vehicle. Vehicle information about the vehicle is extracted (step S414). As described above, the vehicle information extracted here includes, for example, information such as vehicle types, storage locations, available dates and times that match the search information.
The extracted vehicle information is transmitted to the corresponding user terminal 40 (step S415), and is referenced and utilized as car sharing information for users who wish to use the vehicle.

The vehicle information transmitted from the server 10 is received by the corresponding user terminal 40 (step S416), and the user can consider and decide whether or not to apply for the use of the vehicle.
When applying to use the vehicle, the user terminal 40 is operated to input and generate predetermined joint use application information (step S417). Here, as described above, the predetermined joint usage application information input and generated by the user terminal 40 includes, for example, the user's name, address, telephone number, identification information of the vehicle to be used, period of use, days of the week, etc. There is information.
The input shared use application information is transmitted from the user terminal 40 to the server 10 of this system 1 (step S418).

The server 10 receives the joint usage application information transmitted from the user terminal 40 (step S419), and transmits the joint usage application information 30 days after the owner terminal of the vehicle associated with the received joint usage application information. (Step S420).
The joint use application information transmitted from the server 10 is received by the corresponding owner terminal 30 (step S421), and the owner considers and determines whether to permit the user's application to use the vehicle related to the joint use application information. You will be able to do this.
Then, the owner terminal 30 is operated to input and generate predetermined lending permission/disapproval information regarding the user's usage application related to the joint usage application information (step S422). Here, the predetermined lending permission/non-permission information input and generated by the owner terminal 30 includes "permission or non-permission" for the owner to use/rent the vehicle to the user indicated in the joint usage application information. As described above, for example, there is information such as identification information indicating the corresponding usage application information, identification information of the vehicle whose rental is permitted/disallowed, the period of permission, and the day of the week of permission.
The input lending permission/non-permission information is transmitted from the owner terminal 30 to the server 10 of the system 1 (step S423).

The server 10 receives the rental permission/non-permission information transmitted from the owner terminal 30 (step S424), and performs a matching judgment process for “permission/denial” of renting the vehicle to the user related to the shared use application information. This is executed in the contract information generation unit 13 (step S425).
If the result of the determination in the server 10 is that "matching is not established (lending not permitted)" (step S425: No), predetermined information indicating that "matching is not established" is transmitted (step S426), and is received by the user terminal 40. (Step S427). As a result, the user who has received the failure information recognizes that the usage application has failed, and searches for another vehicle.

On the other hand, if the determination result in the server 10 is "matching established (lending permission)" (step S425: Yes), predetermined shared use contract information is generated in the contract information generation unit 13 (step S428). The shared use contract information generated here is contract information that defines predetermined items and contents in accordance with a "shared use contract" concluded between the owner who lends the vehicle and the user who borrows the vehicle. Specifically, as mentioned above, the joint use contract information includes the details of the vehicle joint use contract concluded between the owner/user, such as the name, address, and telephone number of the owner/user, and the vehicle to be used. There is information such as identification information, period of use, days of use, etc. In particular, in this system 1, the shared use contract information sets the vehicle rental period as a fixed period of at least one day of the week on a weekly basis, and sets that day as the period for repeatedly renting the vehicle. .

The shared use contract information generated by the server 10 is transmitted to the corresponding owner terminal 30 and user terminal 40 (step S429), and is received by both the corresponding owner terminal 30/user terminal 40 (steps S430, 431). ).
By receiving this joint use contract information at the owner terminal 30 and the user terminal 40, a joint use contract regarding the vehicle is concluded and established between the owner/user.

FIGS. 9 (9) to (11) show examples of transition screens in the matching flow that are displayed on the user terminal 40 subsequent to FIG. 8 (8).
As shown in the figure, by operating the user terminal 40, the user inputs information such as (9) the location and model of the vehicle he or she wishes to use as predetermined search information, and sends it to the system 1. As the vehicle information extracted and transmitted by this system 1 in response to the transmitted search information, (10) a desired vehicle is displayed so as to be selectable from one or more vehicle information, and (11) ) Information such as detailed information of the selected vehicle, owner's profile, and other users' reviews will be displayed for viewing and reference.

FIGS. 10 (10) to (13) show examples of transition screens in the matching flow that are displayed on the owner terminal 30 subsequent to FIG. 7 (9).
As shown in the figure, by operating the owner terminal 30, the owner receives predetermined usage application information transmitted and presented from the user terminal 40, for example (10) after first going through the business card issuance procedure. (11) It is possible to approve a reservation request, (12) complete a contract, and (13) it is possible to send and receive necessary information such as vehicle details to and from the user via chat or the like.

≪Key delivery flow≫
Next, the "key delivery flow" for the owner/user in this system 1 will be explained.
In the key delivery flow in this system 1, as shown in FIG. A key delivery condition extraction process based on the stored database information is executed (step S501), and information indicating the key delivery condition for the corresponding vehicle is extracted. The information extracted here is information indicating the key delivery conditions, and as described above, for example, information specifying either "shipment of physical key/transmission of electronic key".

Then, if the registered key delivery condition is not "shipment of physical key", that is, "transmission of electronic key" (step S502: No), the key delivery information generation unit 14 issues the electronic key. The electronic key is transmitted (step S503), and the electronic key is received at the user terminal 40 (step S504). Thereby, the user who has received the electronic key can use the electronic key to unlock and lock the corresponding vehicle and use the vehicle.
As mentioned above, electronic keys that serve as key delivery information issued and transmitted in this system 1 are, for example, barcodes or double keys that are identified and recognized by an on-vehicle reader, etc. to unlock the vehicle. This information includes dimensional codes, authentication codes, etc., and by unlocking the door using such an electronic key, the user can use the vehicle using the physical key provided inside the vehicle (for example, in the glove box). Be able to drive etc.

On the other hand, if the registered key delivery condition is "physical key shipping" (step S502: Yes), physical key shipping request information is generated in the key delivery information generation unit 14, and the owner terminal 30 of the corresponding owner (step S505).
Here, the physical key delivery request information, which is the key delivery information generated and transmitted by the key delivery information generation unit 14, is transmitted, for example, to the owner terminal 30 of the owner of the vehicle with which the usage agreement has been concluded, as described above. There is information for requesting the physical vehicle key (automobile key) to be shipped/mailed to the user using the vehicle.

Upon receiving the physical key shipping request information, the owner terminal 30 generates predetermined physical key delivery information (step S506), and transmits it from the owner terminal 30 to the server 10 of the system 1 (step S507).
Here, the physical key delivery information generated and transmitted by the owner terminal 30 includes information corresponding to the above-mentioned physical key shipping request information, such as shipping destination, shipping date and time, shipping date and time for the physical key of the requested vehicle. There is information showing methods etc.
The physical key delivery information received by the server 10 (step S508) is transmitted to the user terminal 40 (step S509), and is received by the corresponding user terminal 40 (step S510).
This allows the user to know that the physical key for the vehicle related to the joint usage agreement has been shipped and the expected arrival date and time, and by actually receiving the physical key, the user can use the physical key to use the vehicle. It becomes like this.

≪Liquidation flow≫
Furthermore, the "payment flow" between owners and users in this system 1 will be explained.
In the payment flow in this system 1, as shown in FIG. 5, first, the user using the vehicle operates the user terminal 40 to input mileage information before/after use of the vehicle (step S511). , transmits the mileage information before/after use to the server 10 (step S512). This mileage information before/after use is obtained by visually checking the odometer display of the vehicle and inputting the data into the user terminal 40, or by taking a picture using the camera function of the user terminal 40, etc. The data can be sent to server 10.

When the server 10 receives the mileage information before/after use transmitted from the user terminal 40 (step S513), the billing information generation unit 15 calculates the mileage used (step S514). The fuel cost for the vehicle used by the user is calculated based on the used mileage information (step S515), and predetermined billing information including the fuel cost is generated (step S516) and sent to the user terminal 40. (Step S517).
The billing information transmitted from the server 10 is received at the corresponding user terminal 40 (step S518), and the user processes the monthly usage fee for the vehicle indicated in the billing information by, for example, bank transfer or credit card payment. (Step S519).

Payment information indicating payment processing performed by the user is transmitted, for example, from the user terminal 40 or from the payment company system 60 outside this system, and is received by the server 10 (step S520).
The server 10 that has received the payment information transmits the payment information to the owner terminal 30 of the owner of the vehicle (step S521), and the payment information is received by the owner terminal 30 (step S522).
This allows the vehicle owner to understand that the user has completed the payment process for the vehicle usage fee.
By repeating the processes shown in FIGS. 4 and 5 above, personal car sharing between owners and users via the present system 1 can be smoothly performed.

FIGS. 11 (14) to (17) show examples of transition screens in the settlement flow that are displayed on the owner terminal 30 following FIG. 10 (13).
As shown in the figure, by operating the owner terminal 30, the owner receives information transmitted and presented from the user terminal 40 at the time of returning the vehicle, such as (14) confirmed information on mileage and fuel cost, 15) It is possible to display and check evaluation information of users who have used the vehicle.
Furthermore, when a user's payment processing is performed, it is possible to receive and display information from the system 1 as predetermined payment information, such as (16) the amount of money to be deposited into the registered bank account, and (17) By performing the "amount confirmation (approval)" operation on the owner terminal 30, the payment process can be confirmed and completed.

As explained above, according to the present system 1, an owner who wishes to rent a vehicle and a user who wishes to use the vehicle do not have one-off or accidental spot rentals, but monthly rentals by the same user. It will be possible to make a contract for continuous rental of Nori on a fixed day of the week.
Such a "monthly/fixed day of the week" usage contract allows users to rent out the vehicle they want to use continuously, on the days they want, and only on the days they need.For example, it is useful for families. We will be able to meet the diverse needs of people such as ``I want to rent a car only on Saturdays and Sundays every week.''

In addition, for the owner, stable sales can be expected as the rental can be continued to the same user on a monthly or day-of-week basis, and the anxiety of renting to an unspecified number of users is alleviated. Owners can also use the vehicles themselves, making it possible to rent and operate vehicles in a planned manner.
Furthermore, instead of a one-time car insurance contract like in a conventional spot rental contract, you can take out long-term car insurance on a monthly basis, and you can also receive discounts on insurance premiums with long-term contracts, including insurance premiums. User fees can be set at reasonable prices.

As a result, it will be possible to eliminate the problems that have existed in personal car sharing to date, such as the hassle of renting and borrowing each time, the anxiety of renting to an unspecified number of people, and the high cost of usage fees and car insurance premiums. .
Therefore, it is possible to support and realize personal car sharing that is easy to use, convenient, and attractive for both owners who wish to rent a vehicle and users who wish to use a vehicle.

Although the present invention has been described above with reference to preferred embodiments, it goes without saying that the present invention is not limited to the above-described embodiments, and that various changes can be made within the scope of the present invention.
For example, in the above-described embodiment, the explanation is made assuming that the owner and the user who rent/rent/share the vehicle are on a one-to-one (one-to-one) relationship, but the owner of the vehicle and the user who The present invention can be applied even when there are multiple users.

In addition, in the above-described embodiment, the vehicle to be rented/borrowed/shared is assumed to be a relatively small/medium-sized vehicle (ordinary vehicle) such as a passenger car including a light vehicle. Targeted vehicles include not only ordinary cars such as passenger cars and light cars, but also large vehicles such as commercial trucks, work vehicles such as excavators and crane trucks, special vehicles, and motorcycles such as large motorcycles. The present invention can be applied to any type of automobile, vehicle, etc., as long as there is a need for car sharing between individuals.

Furthermore, in the above-described embodiment, the present system 1 has been described as being configured with a plurality of information processing devices, but it may also be configured with a single information processing device (for example, one personal computer, etc.). You can also do it.

1. Personal car sharing support system 10. Server (personal car sharing support device)
11 Transmission/reception section 12 Search extraction section 13 Contract information generation section 14 Key delivery information generation section 15 Billing information generation section 20 Storage section 21 Owner information DB
22 User information DB
23 Contract information DB
24 Mileage information DB
30 Owner terminal 40 User terminal

Claims (5)

A system for supporting personal car sharing between an owner who wishes to rent a vehicle and a user who wishes to use the vehicle, the system comprising:
an individual car sharing device communicatively connected to an owner terminal used by the owner and a user terminal used by the user;
The personal car sharing device includes:
a storage means for storing predetermined owner registration information regarding the owner, including predetermined vehicle information of the vehicle, input from the owner terminal, and predetermined user registration information regarding the user, input from the user terminal;
a search extraction means for searching the owner registration information and extracting the corresponding vehicle information based on the search information transmitted from the user terminal;
transmitting/receiving means for transmitting the extracted vehicle information to the user terminal and, upon receiving predetermined usage application information regarding the vehicle information from the user terminal, transmitting the usage application information to the owner terminal;
contract information generating means for generating predetermined usage contract information based on the usage application information and rental permission information when receiving predetermined rental permission information regarding the usage application information from the owner terminal;
The transmitting/receiving means includes:
transmitting the usage contract information to the owner terminal and user terminal;
The contract information generating means includes:
The personal car sharing support system is characterized in that, as the usage contract information, the rental period of the vehicle is set as a fixed period of at least one day of the week on a weekly basis, and the day of the week is set as a period for repeatedly renting the vehicle. . The contract information generating means includes:
The personal car sharing support system according to claim 1, wherein the usage contract information is a car insurance premium calculated on a monthly basis, which is a rental period of the vehicle. comprising billing information generation means for calculating fuel costs for a vehicle used by a user associated with the user terminal and generating predetermined billing information based on predetermined mileage information input from the user terminal;
The transmitting/receiving means includes:
The personal car sharing support system according to claim 1 or 2, wherein the billing information is transmitted to the user terminal. A method for supporting personal car sharing between an owner who desires to lend a vehicle and a user who desires to use the vehicle, the method comprising:
An individual car sharing device communicably connected to an owner terminal used by the owner and a user terminal used by the user,
storing predetermined owner registration information regarding the owner, including predetermined vehicle information of the vehicle, input from the owner terminal, and predetermined user registration information regarding the user, input from the user terminal;
Searching the owner registration information based on search information transmitted from the user terminal and extracting the corresponding vehicle information,
When transmitting the extracted vehicle information to the user terminal and receiving predetermined usage application information regarding the vehicle information from the user terminal, transmitting the usage application information to the owner terminal;
Upon receiving predetermined lending permission information regarding the usage application information from the owner terminal, generating predetermined usage contract information based on the usage application information and rental permission information;
transmitting the usage contract information to the owner terminal and user terminal;
The personal car sharing support method is characterized in that, as the usage contract information, the rental period of the vehicle is set as a fixed period of at least one day of the week on a weekly basis, and the day of the week is set as a period for repeatedly renting the vehicle. . In a system for supporting personal car sharing between an owner who wishes to rent a vehicle and a user who wishes to use the vehicle,
A computer constituting an individual car sharing device that is communicably connected to an owner terminal used by the owner and a user terminal used by the user,
storage means for storing predetermined owner registration information regarding the owner, including predetermined vehicle information of the vehicle, input from the owner terminal, and predetermined user registration information regarding the user, input from the user terminal;
a search extraction means for searching the owner registration information and extracting the corresponding vehicle information based on the search information transmitted from the user terminal;
transmitting/receiving means that transmits the extracted vehicle information to the user terminal and, upon receiving predetermined usage application information regarding the vehicle information from the user terminal, transmits the usage application information to the owner terminal;
Upon receiving predetermined rental permission information regarding the usage application information from the owner terminal, it functions as a contract information generation means that generates predetermined usage contract information based on the usage application information and rental permission information;
The transmitting/receiving means,
transmitting the usage contract information to the owner terminal and user terminal;
The contract information generating means includes:
The personal car sharing support program is characterized in that, as the usage contract information, the rental period of the vehicle is a fixed period of at least one day of the week on a weekly basis, and the day of the week is set as a period for repeatedly renting the vehicle. .

Images