JP7459432B2 - Individual car sharing support system, method, and program - Google Patents

Description

Article 30, Paragraph 2 of the Patent Act applies Website publication date: April 15, 2019, Website address: https://221616. com/idom/news/press/20190415-23880. html, Publisher: IDOM Co., Ltd., Contents of the disclosed invention: A personal car invented by Ryo Niimori on the website of IDOM Co., Ltd. published at the website address above. The share support system and application program have been released. Website publication date: May 16, 2020, Website address: https://221616. com/idom/news/press/20190516-24022. html, Publisher: IDOM Co., Ltd., Contents of the disclosed invention: A personal car invented by Ryo Niimori on the website of IDOM Co., Ltd. published at the website address above. The share support system and application program have been released.

The present invention relates to a service platform that allows other people to share/share an individual's private automobile. In particular, the present invention relates to a server system, application program, etc. that mediates and supports so-called "car sharing," which is the shared use of vehicles.

In the past, in order to make effective use of owners' cars, it was proposed to accept registrations from car owners via a network when offering their cars as rental cars, accept applications from rental car users, select a provider and user based on the conditions for the offer and the conditions for the application, and mediate the rental of the car between the selected two parties (Patent Publication 2002-099762: Patent Document 1).

In the personal car rental support system, the support server consists of a terminal operated by a user who wishes to rent a car, a terminal operated by the individual owner of the rented car, and a terminal operated by the individual owner who owns the rented car, and a terminal operated by the individual owner who owns the rented car. Provides an inspection necessity input page that communicates with the terminal operated by the person in charge of the car service place providing the service, and inputs the necessity of inspection and maintenance of the rented car to the owner terminal. It has been proposed to implement an inspection requirement notification program that notifies a car service terminal when an inspection requirement is input (Japanese Unexamined Patent Publication No. 2018-028850: Patent Document 2).

In order to encourage the owner of a shared object to reuse the object by a user who is favorable to the owner, it has been proposed that the system be configured to accept a third evaluation of the owner by the user, and to grant a specific benefit to a target user identified by the specific owner from among users whose third evaluation of the specific owner is within a third range, so as to promote the granting of a benefit to a user whose evaluation of the owner in a mutual review is above a certain threshold (Patent No. 6481076: Patent Document 3)

"Personal car sharing services" are generally provided in the form of applications for smartphones, etc. In this case, "owners" who want to share their own cars and "drivers" who want to use the cars when necessary register as members in advance and use the Internet. Matching can be done via. The driver searches for the car he or she wants to ride based on location, date and time, requests a reservation, and if the owner approves the reservation, the reservation is confirmed and auto insurance can be automatically added. Drivers and owners can use the app's chat function to exchange details such as delivery methods.

Japanese Patent Application Publication No. 2002-099762 Japanese Patent Application Publication No. 2018-028850 JP 2019-102079 A

With the spread of the sharing economy, car sharing between individuals is also becoming more widespread. However, personal car sharing, which is completed on smartphones, is not necessarily widely used because there are concerns about trouble because it is a transaction between individuals. Further, services that are always mediated by a car service place are likely to have limited use because there are often no car service places nearby.

For this reason, it would be desirable to have a mechanism that can eliminate the concerns about car sharing between individuals, that is easy to use, and that can meet the diverse needs of individuals regarding the shared use of cars. A system, method, and program that realizes such a mechanism would be desirable. An application program that allows easy transactions between individuals using a smartphone, etc., and allows users to appropriately use the high-quality services of businesses, etc., would be desirable.

The present invention aims to provide a car sharing support server system that supports easy and safe use of car sharing between individuals. It also aims to provide an application program with an improved user interface for easily conducting transactions on a smartphone. It also aims to provide a car sharing method that provides high user satisfaction by linking with services at physical stores.

One aspect of the present invention for solving the above-mentioned problems is to provide a personal vehicle equipped with a server for supporting car sharing in which a driver uses a vehicle owned by an owner, which is performed between an owner terminal and a driver terminal. In the sharing system, the server executes a process for managing the car sharing, the process for managing the car sharing includes a process for registering information regarding the car sharing, and the process for registering the information regarding the car sharing includes: In response to the category selection input on the owner terminal, the landmark associated with the category is displayed on the owner terminal in a selectable manner in association with location information as a candidate for the delivery location of the vehicle, and the selection is determined by the selection input on the owner terminal. This includes registering designated landmarks as delivery locations.

The above categories are preferably categories of landmarks that have been pre-selected as vehicle pick-up and drop-off locations, making it easier to set pick-up and drop-off locations for each vehicle. By making it easier for owners to set multiple appropriate pick-up and drop-off locations for each vehicle, the possibility of matching with a driver can be increased, making it easier to use car sharing.

The process of managing the car sharing may include a process of giving a coupon to the driver, and the process includes a process of giving a coupon to the driver in response to a reservation cancellation from the owner after the car share reservation is established and before the car share starts. The process may include a process of giving a predetermined coupon and/or a process of giving a coupon determined by the owner to the driver after the owner cancels the reservation.

The predetermined coupon may be, for example, a coupon that is automatically given by the system in response to a reservation cancellation input from the owner terminal and that discounts the driver's system usage fee on the next transaction. This makes it easier for drivers who have made reservations to find alternatives to canceled transactions, and can prevent them from leaving the application. In addition, owners who cancel due to unavoidable circumstances can encourage drivers not to give up on future business with them.

Preferably, the server is provided with a store database for supporting car sharing, the store database including service type information for each store, and registering information regarding car sharing includes, when registering one or more stores in association with an owner, registering the stores as delivery locations searchable from a driver's terminal for the owner's vehicle according to the service type of the store being registered, and the delivery locations searchable from the driver's terminal include registered landmarks and stores registered as delivery locations.

The store may be a store of a business related to the car sharing system according to the present invention. The landmark category linked to location information (map information) may not necessarily represent the business entity of the store or the detailed service format, etc., but by doing the above, it supports car sharing according to the present invention. Depending on the details of the store, the driver can register the delivery location as a searchable location.

The server may be configured to support car sharing, in which a driver uses a vehicle owned by an owner, which is carried out between an owner terminal, a driver terminal, and a store terminal, and the process of managing the car sharing may further include generating a store page according to the service type of the store when a car sharing reservation is made.

The service type of the store consists of one or a combination of multiple services provided in relation to car sharing, and when a store with a service type that includes at least the provision of a pick-up and drop-off location is registered in association with an owner, the store can be registered as a pick-up and drop-off location for the owner's vehicle.

Stores come in a wide variety of shapes and sizes, and the services they provide regarding car sharing can vary widely. With a wide range of stores offering various service types supporting car sharing, it becomes easier for individual users (owners/drivers) to obtain the services they desire when using car sharing. For example, if a driver wishes to have a nearby pick-up and drop-off location, they can select a vehicle from a nearby landmark, etc., and transact directly with the owner; alternatively, if a driver wishes to have a service mediated by a store, they can reserve a vehicle registered with a store that provides pick-up and drop-off services, etc., and the owner can transact with either driver.

Registering information related to car sharing means that the acquisition price of the vehicle is automatically calculated using vehicle information and auto auction market price information, and the owner The method may include registering the value input by the terminal as a shared use fee for the vehicle.

By doing so, it is possible to set an appropriate fee as a joint usage fee related to car sharing.

Another aspect of the present invention is an interpersonal car sharing support method for supporting car sharing in which a driver uses a vehicle owned by an owner, which is performed between an owner terminal and a driver terminal, the method of supporting car sharing. Managing car sharing includes registering information regarding car sharing, and registering information regarding car sharing includes registering landmarks associated with categories on the owner terminal. In response to the category selection input, the vehicle delivery location candidate is displayed on the owner terminal in a selectable manner in association with position information, and the landmark determined by the selection input on the owner terminal is registered as the delivery location.

Furthermore, when registering information related to car sharing, when registering one or more stores in association with an owner, the store database containing service type information of each store that supports car sharing is referred to, and the service of the store to be registered is registered. Depending on the format, this includes registering the owner's vehicle as a delivery location that can be searched from the driver terminal, and the delivery locations that can be searched from the driver terminal include registered landmarks and stores that are registered as delivery locations. .

Yet another aspect of the present invention is a program that causes a computer to execute the above method.

According to the present invention, a user-friendly car sharing application with an improved user interface is provided. A high-added-value car sharing system is provided that is linked to services provided by stores of businesses involved in the operation of the car sharing system (e.g., car buying/selling businesses, etc.). A car sharing system is provided that provides a sense of security and high user satisfaction by allowing users to easily complete transactions on the app while also receiving support from a physical store.

FIG. 1 shows an outline of a car sharing support system between individuals according to the present invention. FIG. 2 shows a schematic diagram of a Web/Ap server and a DB server according to the present invention. FIG. 3(a) shows a schematic data structure of an owner DB, FIG. 3(b) shows a driver DB, FIG. 3(c) shows a vehicle DB, FIG. 3(d) shows a landmark category DB, and FIG. 3(e) shows a schematic data structure of an AA market price DB. FIG. 4 schematically shows the data structure of the store DB. FIG. 5 shows a flow of registering a vehicle delivery location based on landmark category selection. FIG. 6 shows (A) a category selection screen request page, (B) a category selection page, and (C) a landmark display and selection page for a selected category, according to one embodiment of the present invention. FIG. 7 shows a flow for registering a store that provides services related to car sharing. FIG. 8 illustrates a store selection page according to one embodiment of the present invention. FIG. 9 shows a joint usage fee registration flow according to the present invention. FIG. 10 shows a car sharing transaction processing flow according to one embodiment of the present invention. FIG. 11 illustrates a driver search page according to one embodiment of the present invention. FIG. 12 schematically shows the first data structure of the car share transaction DB. FIG. 13 schematically shows the second data structure of the car share transaction DB.

Various features of the present invention will now be described with reference to the drawings, together with preferred embodiments which are not intended to be limiting of the present invention. The same reference numerals may refer to the same devices, functions, processes, etc.

Figure 1 is a schematic diagram showing the configuration of a network including a person-to-person car sharing support system (car sharing system) 1 according to one embodiment of the present invention. The network configuration includes the car sharing system 1 according to the present invention, a store terminal 40 that communicates with the system 1 via a communication network 7 such as the Internet, an owner terminal 3, a driver terminal 4, and one or more external servers 5, 6, etc.

The car share system 1 includes a web application (Web/Ap) server 10 and a database (DB) server 20 that manages a database (DB) device. Each is equipped with a central processing unit (CPU), RAM, ROM, hard disk, etc., executes a programming language under the control of an appropriate operating system (OS), and provides functional means for executing various processes. The programs stored in the server are constructed using HTML, JavaScript (registered trademark), native programs (object code), and the like. A database management system (DBMS, RDBMS) is running on the DB server 20. The Web/Ap server 10 and the DB server 20 may be composed of public cloud type servers in cloud computing, which is a form of providing or using resources such as storage resources and calculation resources as services on the Internet, and may be configured as a public cloud type server in cloud computing, which is a form of providing or using resources such as storage resources and calculation resources as a service on the Internet. It may also consist of private cloud-type servers for widespread use. The business PC 30 can be used by an operator at the headquarters of the business operator involved in the operation of the system 1 for proper operation of the system 1.

The store terminal 40 used by the person in charge of the store 2, the owner terminal 3 used by the owner, and the driver terminal 4 used by the driver are high-performance terminals such as smartphones or tablet-type high-performance terminals equipped with known camera devices and browser software. It may be a functional terminal or the like. These devices are equipped with platforms including iPhone OS (iOS), Android, etc., which are a set of operating systems (OS) and basic applications such as web browsers. The store terminal 40, owner terminal 3, and driver terminal 4 may be desktop PCs or the like. Although FIG. 1 shows one store terminal 40, one owner terminal 3, and one driver terminal 4, there are generally a plurality of these.

The external servers 5 and 6 are composed of known server devices, and the external server 5 may be a server of a map information provider. The car sharing system 1 according to the present invention can generate information related to car sharing by linking with, for example, Google Maps API. The external server 6 may be a server of an auto auction (AA) information provider, and the system 1 can use AA market prices to calculate appropriate shared use fees for various vehicles offered for car sharing. The system 1 can transmit and receive data as appropriate to servers (not shown) of non-life insurance companies, credit companies, etc. via the network 7.

Figure 2 shows a functional block diagram of the Web/AP server 10 and DB server 20 related to the car sharing system 1.

The Web/Ap server 10 receives various information and requests from the network 7 via the network interface (NIC) 11.

The data processing unit 18 of the server 10 can register and search data in an RDB (relational database), create search results, and perform processes such as adding data to each database, generating search results, deleting data, and updating data. The data acquired and created by each unit of the server 10 is stored in each database via the data processing unit 18 and storage interface 19.

The Web/Ap server 10 includes at least an owner information management section 12, a driver information management section 13, a vehicle information management section 14, a store information management section 15, and a shared use system in order to appropriately acquire/manage data related to car sharing. It includes a fee management section 16 and a transaction information management section 17.

The DB server 20 includes at least an owner DB 21, a driver DB 22, a vehicle DB 23, a landmark category DB 24, a store DB 25, an AA market price DB 26, and a car sharing transaction DB 27.

The owner information management unit 12 includes electronic equipment, electronic circuits, and programs for registering and managing information about owners who use their vehicles for car sharing in the owner DB 21.

Figure 3(a) shows a schematic diagram of the data structure of the owner DB 21. The owner DB 21 includes a vehicle ID and a store ID linked to an owner ID. The owner DB 21 also includes owner information, which may include the owner's name, address, driver's license, credit card, bank account, ratings given by drivers, generated coupon information, and the like. For example, an owner can access a download site from a two-dimensional barcode (Figure 1) on a poster, flyer, or the like placed at a store 2 that the owner visited to purchase or sell a car, download an application program related to car sharing, be assigned an owner ID and a passcode, and register various information by following the application screen.

The vehicle information management unit 14 includes an electronic device, an electronic circuit, and a program for registering and managing detailed information for each vehicle ID in the vehicle DB 23. FIG. 3(c) schematically shows the data structure of the vehicle DB 23. The detailed information for each vehicle ID may include sharing conditions including vehicle delivery location, shareable date and time, joint usage fee, and the like. As will be described later, the delivery location includes a delivery location registered by pinpoint, a delivery location registered from a landmark category, and/or a delivery location registered by store registration. Further, the vehicle information may include various information regarding the vehicle, including, but not limited to, the contents of the vehicle inspection certificate (vehicle number, vehicle type, model, date of first registration, etc.), mileage, vehicle color, vehicle photo, etc. The vehicle information may be input manually, or may be input by reading a two-dimensional barcode on the vehicle inspection certificate using an owner terminal as appropriate.

The driver information management unit 13 includes an electronic device, an electronic circuit, and a program for registering and managing information regarding the driver who uses the vehicle in the driver DB 22.

Figure 3(b) shows a schematic diagram of the data structure of the driver DB 22. The driver DB 22 may include driver information associated with the driver ID, such as name, address, driver's license, credit card, and rating given by the owner. It may also include coupon information (contents of usable coupons, expiration date, etc.). Drivers can download a car sharing application program to their respective terminals 4 in advance using two-dimensional barcodes (Figure 1) placed on posters, flyers, etc. at stores 2 visited to purchase or sell a car, and after being assigned a driver ID and passcode, can perform the necessary registration.

The store information management unit 15 includes electronic equipment and electronic circuits for registering and managing information regarding the physical stores of business operators (for example, car purchase/sales businesses) that support personal car sharing related to the system 1 in the store DB 25. and a program.

FIG. 4 schematically shows the data structure of the store DB 25. The information regarding the store includes, for each store ID, the store address (latitude and longitude) and the service content (service type) provided for car sharing.

Stores may include directly managed stores and franchise stores of a specific business operator operating System 1, as well as stores of various other businesses related to System 1, and stores may have various concepts, sizes, and personnel arrangements. is possible. Therefore, the services provided regarding car sharing may also vary. Examples of services provided regarding car sharing include, but are not limited to, provision of a delivery location, delivery agency, on-site delivery, and free car washing.

The delivery location may be provided in a space such as a store parking lot for car sharing. In addition to providing a delivery space such as a parking lot, the delivery agency handles the delivery of the vehicle between the owner and the driver by the store's personnel. The vehicle is handed over to the driver after handing over the car and keys and checking for scratches on the car. At the return time, handing over the car and keys to the driver and checking for scratches on the car is done before returning the vehicle to the owner. It can be anything. In on-site delivery, the store may go to the owner's address to pick up the vehicle and then act as a delivery agent. The free car wash may be performed free of charge during a predetermined period such as before car sharing, during car sharing, or after car sharing.

In the example of FIG. 4, store A only provides a delivery location, store B provides a delivery location and also a free car wash, store C provides delivery agency services, which essentially includes providing a delivery location, store D provides on-site delivery, which essentially includes providing a delivery location and delivery agency services, and store E only provides a free car wash. A combination of one or more of such multiple services related to car sharing may be referred to as a service form in this specification.

The vehicle delivery location can be registered at a specific location (owner's parking lot, etc.) by pinpoint address search, pinpoint landmark name search, etc., according to the application screen installed on the owner terminal 3 (not shown). You can also register specific landmarks as delivery locations.

Registering multiple landmarks (e.g., five) as pickup locations using pinpoint search is a time-consuming process for owners. On the other hand, if only a few pickup locations are registered, it is difficult to match them with drivers, which makes it difficult to promote the use of car sharing.

Figure 5 shows the flow of registering a landmark delivery location by category selection according to the present invention. When the system 1 receives a request to register a delivery location from the owner terminal 3 (S101), it acquires the owner's location information (e.g., the owner's registered address, the entered address, or current location information obtained by GPS positioning of the terminal 3, etc.) and accepts a request for a category selection screen (S102). Figure 6 (A) is a map based on the current location of the terminal 3, and the owner can request a category selection screen by tapping the "Landmark Selection" button at the bottom of the screen. When the screen is requested, the landmark category selection screen is transmitted (S103) (see Figure 6 (B)).

Figure 3 (d) shows a schematic data structure of the landmark category DB24. In the landmark category DB24, for each landmark ID, the address (latitude and longitude), landmark information, and the category of the landmark may be stored. The landmark information may include one or more of the following information, but is not limited to: the landmark name, business hours, number of parking spaces, and a photo of the exterior. Preferably, the categories in the landmark category DB24 do not include categories that are not envisioned as a car sharing pick-up and drop-off location, and landmarks linked to categories that are not envisioned as a car sharing pick-up and drop-off location are not stored.

The categories included in the landmark category DB24 may be categories such as stores that have parking lots that can be used by an unspecified number of people for a fee or free of charge, and such categories may be, for example, convenience stores, stations, parking lots, department stores, airports, restaurants, gas stations, home improvement stores, parks, stadiums, supermarkets, shopping malls, etc. To simplify the registration operation for owners, the number of categories included in the landmark category DB24 may be limited to around 6 to 10.

In the example of FIG. 6(B), six categories (convenience store, station, parking lot, department store, airport, restaurant, and gas station) are displayed. More categories may be displayed for selection by scrolling. It is preferable that the number of categories is not too large, such as 15 or less, 10 or less, etc., so that the owner can easily search and register the delivery location. When one or more categories are selected by tapping a check field or the like and the OK button is tapped, the landmarks (LM) of the selected categories are extracted in terms of position and marked as markers, as illustrated in FIG. 6(C). is displayed (FIG. 5, S104). In the illustrated example, five landmarks are extracted. The display screen is not limited to this, and a list of extracted landmark names etc. may be displayed. Following the screen in FIG. 6(C), a detailed screen including the name of the landmark may be displayed by, for example, tapping the marker, and by tapping a determination button (not shown) on the landmark detailed screen. Accordingly (S105), the selection of the landmark is accepted (S106), and the landmark is registered as a delivery location linked to the vehicle (S107). Although it is preferable to register a plurality of delivery locations, an upper limit number (for example, 3, 4, 5, 6, 10 locations, etc.) may be provided, and the process may be repeated until the upper limit number is reached (S108). When a request for a category selection screen is received by tapping the landmark selection button on the screen of FIG. 6(C) (S109), landmarks of a new category newly extracted with respect to the position may be displayed for selection. .

FIG. 7 shows a delivery location registration flow associated with store registration. Store registration is to associate the owner with the physical store. Through this registration, the owner can know which physical stores support car sharing and make inquiries as necessary. By understanding this information, it is possible to provide services unique to the store during car sharing transactions or at any time.

When the system 1 receives a request for store registration from the owner terminal 3 (S201), it acquires the owner's location information (e.g., the owner's registered address, the entered address, or current location information by GPS positioning of the terminal 3, etc.) and displays a list of stores extracted in relation to the location in a selectable manner (S202). FIG. 8 is an example of a store list screen, and stores extracted in relation to the owner's location (e.g., within a certain range from the owner's current location) are displayed in a list, for example, in order of proximity. At this time, it is preferable that the service type of the store is displayed in an easy-to-understand manner, and in the illustrated example, services that the store supports are displayed in a dark gray frame, and services that the store does not support are displayed in a light gray frame. In the illustrated example, whether or not four types of services are supported is displayed, but the types of services are not limited to these. For example, free inspections, inspection discount coupons, etc. may be included, and services that are not necessarily related to car sharing may be included. The store list screen may also display an introduction to the store, the distance from the owner's location, etc. The owner can select the nearest store or a store with a preferred service format by tapping a check box (represented by a circle in FIG. 8 ), and can register the store by tapping the confirm button (S203). The owner may be able to select services that the store can provide, and in the example of FIG. 8 , when the owner selects store B, the owner may tap the button for the delivery location to invert it, thereby turning off the delivery location's services. In this way, the owner can register store B as a store that only offers free car wash services, without making it a delivery location. Generally, only one store is registered. Alternatively, the system may be configured to allow multiple stores to be registered.

The store DB25 is then referenced (S204), and if the registered store is able to provide a delivery location, it is registered as the delivery location for the owner's vehicle. In this example, the store registration and delivery location registration are described after the owner registers the vehicle, but the store may be registered before the vehicle is registered. In that case, a store linked to the owner ID may be registered as the delivery location for the vehicle in response to the registration of the vehicle.

As described above, by selecting a landmark from a category, the owner can easily register multiple landmarks as delivery locations for each vehicle, making it easier to match the vehicle with the driver. Additionally, by registering a store, owners can enjoy the store's services and a sense of security. Not only can drivers use car sharing by using familiar landmarks as delivery locations, but when dealing with first-time owners, they can use car sharing without worry, such as by using a store that handles delivery as the delivery location. Can be done.

Referring to FIG. 2, the joint usage fee management unit 16 calculates the upper limit of the joint usage fee for each vehicle, and also registers and manages the shared usage fee determined by the owner in the vehicle DB 23. and a program.

The shared use fee for car sharing between individuals should be set at a range that does not exceed the actual cost of acquiring and maintaining a vehicle, based on the idea that multiple people share the actual cost of maintaining a personal car. If the owner sets the shared use fee on his or her own, it will not necessarily be set appropriately, which will ultimately make car sharing difficult to use, and is therefore not desirable.

With reference to FIG. 9, the calculation flow of the joint usage fee will be explained. In response to a fee setting request from an owner terminal (S301), the joint usage fee management unit 16 transmits a page for inputting a joint usage fee (S302). The annual maintenance fee inputted by the owner terminal on this page may be, for example, the total amount of automobile tax, parking lot fee, vehicle inspection fee, and maintenance fee (regular inspection fee, consumables replacement fee, car wash fee, etc.). The shared usage fee management unit 16 further acquires vehicle data (car type, model, first registration date, car color, mileage, specifications, etc.) from the vehicle DB 23 as input data, and records the auto auction (AA) transaction results (transactions). Reference is made to the AA market price DB 26 having the price) (S303). FIG. 3(e) schematically shows the data structure of the AA market price DB 26. Based on the input data, the calculation model is updated from the transaction history of the applicable car model, model, etc. over a predetermined period (for example, the last few weeks to several months), and the AA market price (predicted value of transaction price in AA) is calculated. (S304).

The machine learning model used to construct the calculation model may be a random forest with a discriminator (decision tree) inside. Generally, the value (price) of a used car such as a personal car is determined by an expert's appraisal. The vehicle data transmitted from the owner terminal 3 does not include expert visual appraisal data (e.g., "evaluation points" etc.) used in general appraisals, but the inventor of the present invention has found a calculation model that accurately represents the AA market price (wholesale price) based on data accumulated in the sale/purchase of used cars. In other words, it has been confirmed that when a price is calculated for a certain vehicle using the calculation model, it is actually traded at an auto auction at a price very close to that price. Therefore, the retail price obtained by multiplying the predicted value (assessment price) output by the calculation model by a coefficient set according to the price range may correspond to the acquisition price of the vehicle. The acquisition cost per day can be determined by dividing the determined retail price by the number of days corresponding to the useful life of the vehicle. The useful life may be calculated by a simple method, or may be fixed to "1 year" etc. depending on the price of the vehicle etc. In addition, the maintenance cost per day can be calculated from the annual maintenance cost entered by the owner. These can be added together to determine the upper limit of the shared use fee per day (S305). The determined upper limit is displayed on the owner terminal 3, and the owner can input a shared use fee up to this upper limit (S306). The input shared use fee is stored in the vehicle DB 23 (S307). Using this as the standard shared use fee, a shared use fee per hour, per week, etc. may be automatically determined.

The transaction information management unit 17 consists of electronic devices, electronic circuits, and programs for managing information related to car sharing transactions and registering and managing the information in the car sharing transaction DB 27.

The car share transaction process flow is described with reference to FIG. 10. Vehicles of registered owners are searchable by registered drivers via the network 7, and a car share transaction is generally initiated by a reservation request from the driver (S401).

FIG. 11 is an example of a search screen sent to the driver terminal 4 in response to a driver's vehicle search request. In this example, registered delivery locations are displayed as markers based on the desired sharing date and time and the driver's current location P, and the number of vehicles registered at each delivery location (1 and 3 in the illustrated example) is displayed. The joint usage fee per unit (950 to 2000 yen in the illustrated example) is displayed. For example, when a driver taps a delivery location, a list of registered vehicles is displayed, and when a driver taps a reservation request button (not shown), a reservation request is sent. A transaction ID is assigned to the reservation request and stored in the transaction DB 27, and the reservation request is sent to the owner of the vehicle (S402).

After that, approval or non-approval is accepted from the owner for a specified period of time. If the owner does not enter non-approval or does not respond during the period, the reservation is not established, but if the reservation is established with the owner's approval, the process proceeds to the next step (S403). According to the present invention, processing at the actual store occurs according to the pick-up location of the established reservation and the service type of the store associated with the owner (S404). As described below, when processing at the store occurs, a store page is generated for viewing and input by the store (S405). If the reservation is not canceled (S406), sharing begins at the reserved time, and a check at the time of pick-up by the user and/or the store is accepted (S407). If the reservation is canceled due to cancellation by the owner, a specified coupon or an owner-generated coupon may be given to the driver (S413).

During sharing, an extension request from the driver and an approval/non-approval of extension from the owner are accepted as appropriate, and driving logs can be collected based on the driver's consent (S408). The driving log may acquire, for example, vehicle speed, engine speed, throttle opening, etc. from onboard equipment data. Alternatively, data such as location information, sudden acceleration, sudden stopping, travel distance, maximum speed, average speed, etc. may be obtained from the GPS of the smartphone. Based on the driving log, the driver's driving characteristics (such as rough driving) may be determined, and the results may be transmitted to the owner terminal and recorded in the transaction DB 27.

The sharing ends at the reservation (extension) end date and time, and a check is received from the user and/or the store at the time of return (S409). After that, an evaluation is received (S410), the evaluation is stored (S411), and a coupon generated by the owner is received and issued to the driver (S412).

Figure 12 shows a schematic data structure of the car sharing transaction DB27. Depending on the content of the car sharing transaction, the data structure may include all of the items described, or may include only some of the items. Furthermore, the items are not limited to these, and may include any items related to the car sharing transaction, such as the period of coverage of the driver's one-day automobile insurance, photos of scratches on the vehicle body, whether or not an extension request has been made and whether or not it has been approved, chat records between users, etc. (In the figure, OW stands for owner, DR stands for driver, and LM stands for landmark).

For example, in the case of a car sharing transaction that does not involve a store and involves a delivery point at a landmark, the owner and driver can input the results of checking the vehicle for scratches, etc. into the app when the sharing starts, and "Confirmed" can be stored in the "Start Damage Check" field. Similarly, when the sharing ends, the owner and driver mutually check and "Confirmed" can be stored in the "End Damage Check" field (S407, S409 in FIG. 10).

In the case of a transaction in which a store acts as a delivery agent, the system 1 accepts input from the store terminal 40 regarding the transaction. At the start of car sharing, the store checks the owner's and driver's licenses, and by inputting them on the app on the terminal 40, "confirmation" is stored in "OW/DR license check", and further information on scratches at the start/end. By obtaining confirmation from the owner and driver, "confirmation" can be entered in "start/end flaw check" (S407, S409 in FIG. 10).

To facilitate processing by the store, the car sharing transaction DB27 may further include transaction data for each store. FIG. 13 shows a schematic diagram of the data structure for each store. The store page for each store to view and/or enter data may include items such as those shown in FIG. 13(a), (b), (c), (d), and (e) depending on the type of service provided by the store, etc.

For example, if the delivery location for the vehicle reserved by the driver is a store that basically provides only a location, such as Store A registered by the owner, (see Figure 4), then A store page can be generated that includes such items. Stores can view the page and free up parking spaces for sharing according to the sharing start date and time and vehicle return date and time.

If the delivery location of the vehicle reserved by the driver is a store that performs delivery agency, such as Store C, which is registered by the owner of the vehicle, for example, the store page as shown in Figure 13(d) will be displayed. can be generated. The store uses the store terminal 40 to view the page and makes necessary inputs such as the sharing start date and time, return date and time, checking the owner's and driver's licenses, checking for scratches at the time of delivery and return, and taking photos. be able to.

If the delivery location for the vehicle reserved by the driver is a store that provides on-site delivery services, such as store D, registered by the vehicle owner, a store page like that shown in FIG. 13(e) can be generated. The store can view the page using the store terminal 40 and go to the delivery location, such as the owner's address, at a date and time that is automatically set prior to the sharing start date and time (e.g., 30 minutes or 1 hour before the sharing start date and time), or at a date and time that is set manually as appropriate, perform the necessary checks, pick up the vehicle from the owner, and then perform the necessary checks at the store and hand over the vehicle to the driver.

If the pick-up location for the vehicle reserved by the driver is a landmark or other location that is not a store that supports car sharing, and the store registered by the owner of the vehicle is a service-type store such as Store A, Store C, or Store D, no service will be provided by the store related to the transaction, and a store page does not need to be generated. For example, users who have traded with each other several times can easily share at a familiar landmark or other location without going through a store.

Even if the delivery location of the vehicle reserved by the driver is a landmark that is not a store that supports car sharing, the store registered by the owner of the vehicle will be the place to deliver the vehicle related to car sharing, such as stores B and E. In the case of a store that provides services not directly related to (for example, free car wash), a store page including items as shown in FIG. 13(b) may be generated. Along with the car share transaction, the owner is given a free car wash coupon that is valid for a predetermined period (for example, one week before and after the car share), and the store provides the service by checking the coupon on the store page or the owner's terminal screen. be able to. The addition of such services makes it easier for owners to proactively offer their vehicles for car sharing.

Alternatively, a store that provides a delivery location and services not directly related to delivery (for example, free car wash), such as Store B, where the delivery location for the vehicle reserved by the driver is registered by the vehicle owner. In this case, a store page as shown in FIG. 12(c) may be generated.

The service format of the store is not limited to the above, and the items and patterns of store data included in the transaction DB 27 may not be limited to the above.

A store that can provide a delivery location may be registered as a delivery location by pinpointing the location, even if the owner does not register it as the owner's store. In that case, regardless of the type of service provided by the store, a store page may be generated as shown in FIG. 13(a).

Stores may be registered not only as owners, but also as drivers. Depending on the services the store provides to drivers for car-sharing transactions (e.g., cleaning the interior of the car before and after sharing), a store page may be generated to appropriately support the car-sharing transaction.

According to the system for personal car sharing according to the present invention, a user accesses a download site using a two-dimensional barcode or the like at a vehicle sales/purchasing store, obtains an application, and uses car sharing when purchasing a car. You can choose a vehicle with consideration to reducing your financial burden, or even if you sell your vehicle, you can continue to use your car as a means of transportation through car sharing.

Further, according to the application program according to the present invention, multiple delivery locations can be easily registered using the improved GUI, making it easier to perform matching, which is highly convenient for both owners and drivers. Since the services provided by physical stores that support the car sharing system are incorporated into car sharing transactions, it is possible to create a personal car sharing system that has high added value and can be used with peace of mind.

It will be apparent to those skilled in the art that many different modifications are possible without departing from the spirit and scope of the present invention. Therefore, it should be understood that the embodiments of the present invention are merely illustrative and do not limit the scope of the present invention.

10 Car share support web application server 20 Car share support database server

Claims (10)

An individual car sharing system comprising a server for supporting car sharing between an owner terminal and a driver terminal in which a driver uses a vehicle owned by an owner, the system comprising:
The server executes processing for managing the car sharing,
The process of managing car sharing includes a process of registering information related to car sharing, and the process of registering information related to car sharing includes:
A landmark associated with a category is displayed on the owner terminal in a selectable manner in association with location information as a candidate for a vehicle delivery location in response to a category selection input on the owner terminal, and the owner terminal selects the landmark. An interpersonal car sharing system that includes registering a landmark determined by input as a delivery location. The process of managing the car sharing includes a process of granting a coupon to the driver,
The process of granting a coupon to the driver includes:
A process of granting a predetermined coupon to the driver when a reservation cancellation is received from the owner after a car share reservation is established but before the car share starts, and/or a process of granting a coupon determined by the owner terminal to the driver after a reservation cancellation is received from the owner;
The person-to-person car sharing system according to claim 1 . The server includes a store database for supporting the car sharing,
The store database includes service type information of each store,
Registering the information regarding the car sharing,
When registering one or more stores in association with the owner, the method includes registering the owner's vehicle as a searchable delivery location from the driver terminal according to the service type of the registered store;
2. The personal car sharing system according to claim 1 , wherein the delivery locations searchable from the driver terminal include registered landmarks and stores registered as delivery locations. The server supports car sharing, which is carried out between an owner terminal, a driver terminal, and a store terminal, in which a driver uses a vehicle owned by an owner;
The person-to-person car sharing system according to claim 3 , wherein the process of managing the car sharing further includes generating a store page according to the service format of the store when a car sharing reservation is made. A person-to-person car sharing system as described in claim 3, wherein the service form consists of one or a combination of a plurality of services provided in relation to car sharing, and when a store associated with providing a delivery location is associated with an owner and registered, the store is registered as a delivery location for the owner's vehicle. 2. The personal car sharing system according to claim 1, wherein the categories do not include categories of landmarks that are not expected as vehicle delivery locations. Registering information regarding the car sharing,
The acquisition price of the vehicle is automatically calculated using the vehicle information and the auto auction market price information, and the value input by the owner terminal is used within the set upper limit using the calculated acquisition price. including registering it as a usage fee;
The personal car sharing system according to claim 1 . An interpersonal car sharing support method for supporting car sharing in which a driver uses a vehicle owned by an owner, which is performed between an owner terminal and a driver terminal, the method comprising:
comprising managing the car sharing;
Managing the car sharing includes registering information regarding the car sharing, and registering the information regarding the car sharing,
A landmark associated with a category is displayed on the owner terminal in a selectable manner in association with location information as a candidate for a vehicle delivery location in response to a category selection input on the owner terminal, and the owner terminal selects the landmark. An interpersonal car sharing support method including registering a landmark determined by input as a delivery location. Registering the information regarding the car sharing further includes:
When registering one or more stores in association with the owner, a store database including service type information of each store that supports the car sharing is referred to, and the owner's information is registered according to the service type of the store to be registered. including registering the vehicle as a searchable delivery location from the driver terminal;
9. The personal car sharing support method according to claim 8 , wherein the delivery locations searchable from the driver terminal include registered landmarks and stores registered as delivery locations. A program that causes a computer to execute the method according to claim 8 or 9.

Images