JP2024060293A - Vehicle information management system, vehicle information management method, and program - Google Patents

Abstract

To suitably facilitate the private sale and purchase of vehicles.SOLUTION: A registration number receiving unit 101 receives a user's car number (automobile registration number) from a user terminal 20 that has accepted a friend registration request via a communication application, and an attribute information input unit 102 accepts input of automobile attribute information obtained from an attribute information DB 200 using the car number received by the registration number receiving unit 101, and outputs the information to a storage unit 103. A vehicle price acquisition unit 104 acquires a corresponding vehicle price (market price) from a used vehicle market price DB 250 based on attribute information stored in a management information DB 120 and outputs the vehicle price to a vehicle price storage unit 105. When a desired sale request for a vehicle is input from a desired sale receiving unit 107, a desired sale storage unit 108 generates desired sale vehicle information based on the attribute information corresponding to a seller user who has sent the request and the vehicle price, and stores the generated desired sale vehicle information in a desired sale/purchase DB 121.SELECTED DRAWING: Figure 2

Description

The present invention relates to a vehicle information management system, a vehicle information management method, and a program.

A method for managing car buying and selling information has been proposed that enables cars to be bought and sold efficiently and at the right time (for example, Patent Document 1).

JP 2019-46218 A

In the method described in Patent Literature 1, individuals who wish to sell a car must request the sale of the car from a store, and it is anticipated that vehicle information on the person who wishes to sell the car may not be collected appropriately. Therefore, there is a risk that the method described in Patent Literature 1 will not be able to solve the problem of enabling efficient car buying and selling.

The present invention was made in consideration of the above-mentioned circumstances, and aims to provide a vehicle information management system etc. that can effectively promote the buying and selling of vehicles.

In order to achieve the above object, the vehicle information management system according to the present invention comprises:
a registration number receiving means for receiving a vehicle registration number of a vehicle owned by a user;
an attribute information input means for inputting attribute information corresponding to the vehicle registration number when the vehicle registration number is received from a user;
a storage means for storing in a vehicle information database, in association with the identification information of the user who transmitted the vehicle registration number and the attribute information corresponding to the vehicle registration number;
a vehicle price acquisition means for acquiring a corresponding vehicle price from a used car price database in which market prices of used cars are stored, based on the attribute information stored in the vehicle information database;
a vehicle price storage means for storing the vehicle price acquired by the vehicle price acquisition means in the vehicle information database in association with the user's identification information and the user's attribute information;
an information distribution means capable of distributing to a user information corresponding to the attribute information stored in association with the user;
a vehicle sale request receiving means for receiving a vehicle sale request from a seller user who is a seller of the vehicle;
a sales request storage means for generating sales request vehicle information based on the attribute information and the vehicle price corresponding to the seller user when a sales request is received from the seller user, and storing the generated sales request vehicle information in a sales request database;
a vehicle information transmitting means for transmitting the vehicle information stored in the vehicle sales database to a requester in response to a request to view the vehicle information;
Equipped with.

A purchase condition receiving means for receiving vehicle purchase conditions of a buyer user who will be a buyer of the vehicle;
a desired purchase conditions storage means for storing the desired purchase conditions received by the desired purchase conditions receiving means in the trading desire database;
A search means for searching for the vehicle information stored in the sales and purchase request database that matches the desired purchase conditions;
a notification means for notifying the seller user and the buyer user that a match between a purchase request and a sale request has been established when the search means has searched for the vehicle information to be sold that meets the purchase request conditions;
The above configuration may be adopted.

an attribute information retrieval means for retrieving the attribute information that matches the desired purchase conditions stored in the trader desire database from the vehicle information database;
When the attribute information search means is able to search for the attribute information that matches the desired purchase conditions, the information distribution means may distribute, as the distribution information, information indicating that there is a desire to purchase a vehicle to a user corresponding to the attribute information.

a purchase request receiving means for receiving a request for purchasing a vehicle from a buyer user who is a buyer of the vehicle and who specifies the vehicle sale request information;
a notification means for notifying the seller user corresponding to the vehicle information designated by the purchase request that a purchase request has been received, when the purchase request has been received from the buyer user;
The above configuration may be adopted.

When the selling request storage means receives a selling request from the seller user, it may extract at least one of information related to the vehicle inspection expiration date, information related to the vehicle model, information related to the year, and information related to the mileage from the attribute information corresponding to the seller user, and generate the selling vehicle information.

The information distribution means may be capable of distributing at least one of information regarding vehicle inspections, product information, information regarding vehicle switching, and coupons as the distribution information based on the attribute information.

Further, the vehicle information management method according to the present invention includes:
receiving a vehicle registration number of a vehicle owned by a user;
When receiving the vehicle registration number from the user, input attribute information corresponding to the vehicle registration number;
The identification information of the user who transmitted the vehicle registration number is associated with the attribute information corresponding to the vehicle registration number and stored in a vehicle information database;
Based on the attribute information stored in the vehicle information database, a corresponding vehicle price is obtained from a used car price database in which market prices of used cars are stored;
The acquired vehicle price is added to the vehicle information database in association with the user's identification information and the attribute information;
The information to be distributed to a user corresponds to the attribute information stored in association with the user,
receiving a request to sell a vehicle from a seller user who is a seller of the vehicle;
When a request for sale is received from the seller user, generating vehicle sale information based on the attribute information corresponding to the seller user and the vehicle price, and storing the generated vehicle sale information in a sales request database;
In response to a request to view the vehicle information wanted for sale, the vehicle information wanted for sale stored in the vehicle information wanted for sale database is transmitted to a requester.

In addition, the program according to the present invention is
Computer,
A registration number receiving means for receiving a vehicle registration number of a vehicle owned by a user;
an attribute information input means for inputting attribute information corresponding to the vehicle registration number when the vehicle registration number is received from the user;
a storage means for storing in a vehicle information database, in association with the identification information of the user who transmitted the vehicle registration number and the attribute information corresponding to the vehicle registration number;
a vehicle price acquisition means for acquiring a corresponding vehicle price from a used car price database in which market prices of used cars are stored, based on the attribute information stored in the vehicle information database;
a vehicle price storage means for adding the vehicle price acquired by the vehicle price acquisition means to the vehicle information database in association with the user's identification information and the user's attribute information;
an information distribution means capable of distributing to a user information corresponding to the attribute information stored in association with the user;
a vehicle sale request receiving means for receiving a vehicle sale request from a seller user who is a seller of the vehicle;
a sales request storage means for generating sales request vehicle information based on the attribute information corresponding to the seller user and the vehicle price when a sales request is received from the seller user, and storing the generated sales request vehicle information in a sales request database;
a vehicle information transmission means for transmitting the vehicle information stored in the vehicle sales database to a requester in response to a request to view the vehicle information;
Function as.

The above-described system, method, and program can effectively promote vehicle buying and selling. In particular, it can effectively promote private vehicle buying and selling.

1 is a configuration diagram of a vehicle information management system according to an embodiment of the present invention. FIG. 2 is a functional configuration diagram of a server. FIG. 2 is a hardware configuration diagram of a computer constituting a server. 10 is a diagram illustrating an example of attribute information stored in an attribute information DB. 13 is a flowchart showing operations of a member registration process. FIG. 2A is a diagram showing an example of store information, and FIG. 2B is a diagram showing an example of member information. 13 is a flowchart showing the operation of a buy/sell request acceptance and matching process. 1A is a diagram showing an example of vehicle-for-sale information, and FIG. 1B is a diagram showing an example of desired purchase condition information. 13 is a flowchart showing an operation of a distribution information determination process. (A) to (D) are examples of displays on a user terminal. (A) to (D) are examples of displays on a user terminal.

Below, a vehicle information management system and a vehicle information management method according to an embodiment of the present invention will be described in detail with reference to the drawings. In the embodiments, the same components are given the same reference numerals.

The vehicle information management system 1 according to this embodiment is a system that manages vehicle information registered by users, and is a system that can match users' desire to sell and purchase (matching of private sales).

In order to effectively match users' desire to sell and purchase, it is necessary to secure a sufficient number of users and the number of desires to sell and purchase vehicles. To this end, in this embodiment of the vehicle information management system 1, in order to attract vehicle owners who could potentially become sellers as users, users are accepted to register as members through stores that provide automobile-related services, such as gas stations used by the vehicle owners, regardless of whether they wish to sell or purchase.

However, it is difficult for a store to attract users unconditionally. Therefore, the vehicle information management system 1 of this embodiment is capable of delivering useful information such as information about the car and coupons that can be used at the store, as well as information related to the car owned by the user, to a store that provides services related to cars, such as a gas station, and that has registered as a member at the store that has the vehicle information management system 1 installed.

Because a user needs to register as a member to receive coupons and information distribution from a store, the user can be encouraged to register as a member. Also, because a user needs to register vehicle information he or she owns in order to receive information related to the vehicle he or she owns, the user can be encouraged to register vehicle information. In particular, with the vehicle information management system 1 of this embodiment, vehicle information (attribute information) can be registered simply by inputting the car navigation system, so vehicle information can be registered with simple operations.

The vehicle information management system 1 can be introduced by stores, companies, and manufacturers, and is a system that can be used across stores, companies, and manufacturers. Therefore, the vehicle information management system 1 can be said to be a service, tool, or platform that can be used by each store that introduces it. Since the vehicle information management system 1 can be used across stores, companies, and manufacturers, it can collect a variety of vehicle information.

In this way, according to the vehicle information management system 1, it is possible to acquire members of the vehicle information management system 1 through multiple stores used by users who are owners of automobiles, so that it is possible to ensure a large number of users who are potential buyers and sellers, and a large number of pieces of vehicle information, and it is possible to effectively match users' desire to sell and purchase, and to effectively promote private sales (personal sales) of vehicles. Note that, although the vehicle information management system 1 of this embodiment assumes that the users are individuals, the users may also be businesses or companies. For example, a vehicle sales intermediary may be the buyer user who purchases the vehicle.

In the vehicle information management system 1, the registration of members and information distribution for each specific store is performed via a communication application having a function for exchanging messages (messenger, chat function) that is installed in the user terminal 20 held by the user. The communication application allows the exchange (sending and receiving) of messages, images, videos, files, etc. between the user terminals 20 on which it is installed. In addition, the communication application allows the user to receive information distributed by a store, company, manufacturer, etc. by registering the account of the store, company, manufacturer, etc. (registering as a friend). In this way, the communication application may be one that is widely distributed in general, or may use a dedicated application or a message function of a social networking service (SNS). Note that the communication application and the dedicated application are not limited to those that allow two-way message exchange, and may be one that allows the server 10 to notify the user terminal 20 of a message.

In this embodiment of the vehicle information management system 1, when registration (friend registration) for information distribution to a store that has introduced the vehicle information management system 1 is performed via a communication application, the user is prompted to enter the car number (vehicle registration number) of the user's vehicle. In stores that use the vehicle information management system 1, it is preferable to encourage users to register as friends and enter their car numbers by displaying POPs (point of purchase advertising), posters, stickers, panels, cards, etc. that contain two-dimensional codes and IDs for friend registration, or by having store staff make appeals.

When the car number is input, the vehicle information management system 1 obtains the vehicle's attribute information (vehicle inspection certificate information such as vehicle type, engine displacement, mileage, year, remaining period of vehicle inspection, etc.) from the vehicle number. In this embodiment, the vehicle type includes at least the vehicle name, and may also include the model, grade, and engine displacement. As a result, the vehicle information management system 1 determines the information to be distributed to the user according to the vehicle's attribute information, and distributes information according to the determined vehicle's attribute information to the user, so that useful information according to the vehicle owned by the user can be distributed. In addition, since membership registration and acquisition of the car number are performed via a commonly used communication application, it is easy for users to register as members, and it is expected that new customers will be acquired and customers will be retained. The type of information that can be distributed, the type of coupon, and the distribution time of the coupon are set in advance by the store in the vehicle information management system 1. The vehicle information management system 1 determines the information to be distributed to the user within that setting.

In addition, the vehicle information management system 1 acquires vehicle attribute information based on the vehicle number when a member registers for information distribution, so that it can collect attribute information on vehicles owned by users who are potentially the subject of private transactions, and can conveniently build a database of vehicle information.

Note that registration as a member of the vehicle information management system 1 is not limited to being done through a store, but may also be done by registering as a friend to the account of the vehicle information management system 1 using a communication application, or may be done through a dedicated application. Also, it may be possible to register as a member from a specified website.

As shown in FIG. 1, the vehicle information management system 1 is composed of a server 10, a user terminal 20, and a store terminal 30, which are interconnected via a communication network 90. In addition, an attribute information database (database; DB) 200 and a used car market price database (DB) 250 are connected to the communication network 90 as external devices. Although three user terminals 20 and one store terminal 30 are shown in FIG. 1, the number of user terminals 20 and store terminals 30 is merely an example, and in reality, the number will depend on the number of users and stores that use the vehicle information management system 1.

The server 10 accepts friend registrations from the user terminal 20 in a communication application, and receives information on the vehicle number owned by the user via the communication application. Then, based on the vehicle number, the server 10 obtains the vehicle's attribute information (vehicle inspection certificate information such as vehicle type, engine displacement, mileage, year, remaining vehicle inspection period, etc.) from the attribute information DB 200. The server 10 also obtains the used car market price of the vehicle from the used car market price DB 250 based on the vehicle's attribute information. The server 10 then stores the user's communication application identification information (user ID), the vehicle number, the attribute information, the vehicle price (used car market price), etc. in association with each other.

The server 10 also determines the information to be distributed based on the stored attribute information of the user's vehicle, and distributes the determined information to the user via the communication application.

The server 10 receives requests to sell or purchase automobiles from the user terminal 20, matches the requests to sell with the requests to purchase, and notifies the user terminal 20 of the matching result when a match is made. The server 10 also matches the desired purchase conditions with the vehicle information (attribute information) of the users (members) of the vehicle information management system 1, and when there is a vehicle that matches the desired purchase conditions, it is possible to distribute information to the user who owns the vehicle indicating that there is a purchase request. This allows members to be approached about selling their vehicles, which is expected to increase the number of requests to sell.

FIG. 2 is a functional configuration diagram showing the functional configuration of the server 10. As shown in FIG. 2, the server 10 has, as its functional configuration, a registration number receiving unit 101, an attribute information input unit 102, a memory unit 103, a vehicle price acquisition unit 104, a vehicle price memory unit 105, an information distribution unit 106, a sale request receiving unit 107, a sale request memory unit 108, a vehicle information transmission unit 109, a purchase request condition receiving unit 110, a purchase request condition memory unit 111, a search unit 112, a notification unit 113, an attribute information search unit 114, a purchase request receiving unit 115, a management information DB 120, and a purchase request DB 121.

The registration number receiving unit 101 receives the user's car number (automobile registration number) from the user terminal 20 that has accepted a friend registration request via a communication application, and outputs the user's communication application identification information (user ID) and the car number to the storage unit 103. The registration number receiving unit 101 also outputs the car number to the attribute information input unit 102.

The attribute information input unit 102 inputs the automobile attribute information obtained from the attribute information DB 200 using the car number received by the registration number receiving unit 101, and outputs it to the memory unit 103.

The storage unit 103 associates the user's identification information with the vehicle number of the vehicle owned by the user and the attribute information of the vehicle, and stores the information in the management information DB 120.

The vehicle price acquisition unit 104 acquires the corresponding used car market price (vehicle price) from the used car market price DB 250 based on the attribute information stored in the management information DB 120, and outputs it to the vehicle price storage unit 105.

The vehicle price storage unit 105 adds the vehicle price acquired by the vehicle price acquisition unit 104 to the management information DB 120 in association with the user's identification information, the vehicle number of the vehicle owned by the user, and the attribute information of the vehicle.

The information distribution unit 106 determines the distribution information to be distributed to the user based on the attribute information (vehicle type, engine displacement, mileage, model year, remaining period of vehicle inspection, etc.) stored in the management information DB 120, and distributes the determined distribution information to the corresponding user (user terminal 20) via a communication application. In addition, when the attribute information search unit 114 is able to search for attribute information that matches the desired purchase conditions, the information distribution unit 106 distributes information indicating that there is a desire to purchase a vehicle to the user corresponding to the attribute information.

The sale request receiving unit 107 receives a request to sell a vehicle from the user terminal 20 of the seller user who is the seller of the vehicle or from another communication terminal, and outputs the request to the sale request storage unit 108. Note that the server 10 communicates with the user via the user terminal 20 owned by the user, but communication via other communication terminals is also possible.

When a request to sell a vehicle is input from the sale request receiving unit 107, the sale request storage unit 108 generates sale request vehicle information based on the attribute information corresponding to the seller user who sent the request and the vehicle price, and stores the generated sale request vehicle information in the sale request DB 121.

The vehicle information transmission unit 109 transmits the vehicle information for sale stored in the purchase and sale request DB 121 to the requester in response to a request to view the vehicle information for sale from the user terminal 20 of the buyer user who will be the buyer of the vehicle or from another communication terminal.

The desired purchase conditions receiving unit 110 receives the desired purchase conditions for a vehicle from the user terminal 20 of the buyer user who will be the buyer of the vehicle or from another communication terminal, and inputs the received desired purchase conditions into the desired purchase conditions storage unit 111.

When the desired purchase conditions are input from the desired purchase conditions receiving unit 110, the desired purchase conditions storage unit 111 associates the desired purchase conditions with the buyer user's information and stores them in the desired purchase DB 121 as desired purchase conditions information.

The search unit 112 searches for vehicle information for sale that matches the desired purchase conditions stored in the purchase and sale request DB 121, and if there is vehicle information for sale that matches the desired purchase conditions, it inputs that fact to the notification unit 113.

When the search unit 112 is able to search for vehicle information for sale that meets the desired purchase conditions, the notification unit 113 notifies the seller user and the buyer user's user terminals 20, etc., that a match between the purchase request and the sale request has been made. In addition, when a request to purchase a vehicle specifying the vehicle information for sale is input from the purchase request receiving unit 115, the notification unit 113 notifies the seller user corresponding to the vehicle information for sale specified by the purchase request that there is a purchase request.

The attribute information search unit 114 searches the management information DB 120 for attribute information that matches the desired purchase conditions stored in the trade request DB 121, and if attribute information that matches the desired purchase conditions is found, it inputs that fact to the information distribution unit 106.

When the purchase request receiving unit 115 receives a request to purchase a vehicle specifying the vehicle to be sold information from the user terminal 20 of the buyer user who will be the buyer of the vehicle or another communication terminal, the purchase request receiving unit 115 inputs the request to the notification unit 113.

The management information DB 120 is a DB that stores store information about stores that use the vehicle information management system 1, member information (vehicle information) for each store, coupon distribution scenarios, etc.

The sales and purchase request DB121 is a DB that stores information on vehicles desired for sale (model, year, color, mileage, equipment, images, vehicle inspection information, desired price, etc.) of seller users who wish to sell, and information on the purchase conditions desired by buyer users who wish to purchase (model, vehicle type, year, color, mileage, equipment, remaining period of vehicle inspection, desired price, etc.).

Although the above description has been given with respect to one server 10 having these mechanical configurations, multiple servers 10 may be provided and the above functional configurations may be realized by the multiple servers 10. For example, functional units related to matching between private buyers and sellers of vehicles, such as the sale request receiving unit 107, sale request storage unit 108, vehicle information transmitting unit 109, purchase request condition receiving unit 110, purchase request condition storage unit 111, search unit 112, notification unit 113, attribute information search unit 114, purchase request receiving unit 115, and purchase request DB 121, may be provided on a separate server.

The server 10 shown in Figs. 1 and 2 is composed of a computer, and in terms of hardware, for example, as shown in Fig. 3, includes a CPU (Central Processing Unit) 151, a ROM (Read Only Memory) 152, a RAM (Random Access Memory) 153, an auxiliary storage device 154, and a communication I/F (interface) 155. These components are electrically connected to each other via a bus BL. The server 10 may be a server device installed by the operator of the vehicle information management system 1, or may be a cloud server provided by a third party that implements the functions of the server 10. The server 10 may include input/output devices such as a display device, a speaker, a mouse, and a keyboard, a connection interface with external devices, and other components.

The CPU 151 controls the entire server 10 by expanding into the RAM 153 and executing the programs stored in the ROM 152 and the auxiliary storage device 154. The CPU 151 functions as the registration number receiving unit 101, the attribute information input unit 102, the storage unit 103, the vehicle price acquisition unit 104, the vehicle price storage unit 105, the information distribution unit 106, the sale request receiving unit 107, the sale request storage unit 108, the vehicle information transmitting unit 109, the purchase request condition receiving unit 110, the purchase request condition storage unit 111, the search unit 112, the notification unit 113, the attribute information search unit 114, and the purchase request receiving unit 115 shown in FIG. 2.

ROM 152 is a non-volatile memory that stores basic programs executed by CPU 151, fixed data, etc. RAM 153 is used as a working area for CPU 151.

The auxiliary storage device 154 is composed of a large-capacity, non-volatile storage device whose contents can be rewritten. The auxiliary storage device 154 stores member information, store information, information on vehicles to be sold, and desired purchase conditions of the vehicle information management system 1. The auxiliary storage device 154 functions as the management information DB 120 and the sales and purchase request DB 121 shown in FIG. 2. The auxiliary storage device 154 also stores programs that allow the CPU 151 to execute each process described below.

The communication I/F 155 is connected to the communication network 90 via a wired or wireless connection, and communicates with the user terminal 20, the store terminal 30, the attribute information DB 200, and the used car market price DB 250 via the communication network 90.

The user terminal 20 is a communication terminal owned by the user, and may be, for example, a smartphone or a tablet terminal. A communication application capable of exchanging messages is installed on the user terminal 20. By registering as a member of the vehicle information management system 1 using the user terminal 20, in other words, by registering a specific store that has installed the vehicle information management system 1 as a friend in the communication application, the user can receive information related to the vehicle owned by the user and coupons for the store that the user has registered as a member from the server 10 via the communication application. The user terminal 20 is only required to be able to process reservations for products and services according to the distribution information received from the server 10, output a screen for using coupons, and register a desire to sell or purchase a vehicle.

In addition, the user terminal 20 can send a request to sell or purchase a vehicle to the server 10, and can receive a notification from the server 10 when the desired conditions are met or when a sale is concluded.

The store terminal 30 is a communication terminal installed in the store or held by the store staff, and is composed of, for example, a personal computer, a smartphone, a tablet terminal, etc. By accessing the server 10 from the store terminal 30 via the communication network 90, it is possible to refer to or change information distribution settings, refer to registered member information, coupon usage records, etc. In addition, the store terminal 30 can register purchase history at the store, application history such as coating, and maintenance history such as oil changes. These pieces of information are stored as attribute information of the server 10. In this way, the attribute information may include information about the vehicle other than the vehicle inspection certificate information (maintenance and application history, etc.). This makes it possible to further enrich the attribute information. In terms of hardware, the user terminal 20 and the store terminal 30 are equipped with a CPU, ROM, RAM, auxiliary storage device, communication I/F, input/output device, etc.

Attribute information DB 200 shown in FIG. 1 stores attribute information (vehicle inspection certificate information) such as chassis number, owner's name or title, owner's address, ..., registration date, vehicle displacement, vehicle model year (first registration year and month), vehicle inspection validity expiration date, vehicle inspection history (vehicle inspection expiration date, vehicle inspection implementation date, mileage at the time of vehicle inspection, vehicle inspection cost ...) in association with multiple vehicle registration numbers (car numbers), as exemplified in FIG. 4. In response to a search request including the vehicle registration number from server 10, attribute information DB 200 searches and reads out the corresponding attribute information and transmits it to attribute information input unit 102. Attribute information DB 200 is installed, for example, by a company, an industry group, etc. Basic data is registered in attribute information DB 200 when a vehicle is registered, and when vehicle inspection is implemented, information related to the vehicle inspection (registration date and vehicle inspection history) and the vehicle inspection validity expiration date are set.

The used car market price DB 250 shown in FIG. 1 is a database that associates vehicle information (such as information included in attribute information) such as the vehicle model, year, remaining period of vehicle inspection, and mileage with the used car market price (price or price range) of the vehicle. The used car market price may be calculated based on the accumulated data by accumulating multiple transaction records, for example. In response to a used car market price inquiry request accompanied by vehicle information from the server 10, the used car market price DB 250 searches for and reads the corresponding used car market price, and transmits it to the vehicle price acquisition unit 104. If the used car market price of the corresponding vehicle is not stored in the used car market price DB 250, it may transmit a message indicating that there is no match, or may transmit the used car market price of a similar vehicle (nearby search result), or may calculate and transmit the used car market price based on the new car price and current vehicle information (year, mileage, etc.). The used car market price DB 250 is installed, for example, by a company, an industry group, etc. The used car market price DB 250 may be constructed as an internal configuration of the vehicle information management system 1.

The communication network 90 shown in FIG. 1 is, for example, the Internet, a mobile phone communication line, a LAN (Local Area Network), a VPN (Virtual Private Network), or a communication cable, or a combination of two or more of these, and connects the components of the vehicle information management system 1 so that data communication can be performed.

Next, the operation of the vehicle information management system 1 having the above configuration will be described. FIG. 5 is a flowchart showing the operation of the member registration process. When a friend registration operation of a communication application, such as reading a two-dimensional code printed on a medium (POP, poster, etc.) installed in a store with the user terminal 20, is detected (Step S11; Yes), the user terminal 20 transmits the user ID of the communication application (friend registration request) to the server 10 (Step S12).

After that, when the operation of registering the car number via the communication application is detected (step S13; Yes), the information of the entered car number is sent to the server 10 (step S14). Note that FIG. 5 shows an example in which the car number is registered consecutively after friend registration, but the user can register the car number via the communication application at any time after friend registration. In this way, the user can register as a member with a simple operation via a commonly used communication application, so that it is possible to encourage users to register as members, and it is expected that new customers will be acquired and customers will be retained, which will contribute to the expansion of the business. In addition, since the attribute information of the car is registered by the user simply by inputting the car number, it is not necessary to input information about the car owned, and the attribute information can be registered with a simple operation, and information based on the attribute information can be distributed. In addition, the server 10 can efficiently collect information about the vehicle owned by the user, and the vehicle information can be used to mediate private sales, which can lead to the promotion of private sales of vehicles.

When the CPU 151 of the server 10 receives the user ID of the communication application from the user terminal 20, the CPU 151 stores the user ID in the auxiliary storage device 154 (management information DB 120) (step S21).

In addition, when the CPU 151 of the server 10 receives car number information from the user terminal 20 via the communication application, it stores the car number in the management information DB 120 in association with the user ID (step S22).

Then, the CPU 151 of the server 10 obtains attribute information corresponding to the car number from the attribute information DB 200 and inputs it to the server 10 (step S23).

In step S23, for example, the CPU 151 transmits a search request including the car number to the attribute information DB 200 via the communication network 90. In response to the search request from the server 10, the attribute information DB 200 reads out the attribute information stored in association with the received car number and transmits it to the server 10. Note that the attribute information DB 200 is not limited to transmitting all the attribute information stored in association with the received car number, and may restrict the transmission of some information (e.g., personal information such as the owner's name or title, and the owner's address). In this way, attribute information that cannot be obtained from the attribute information DB 200 may be made inputtable at the user terminal 20 and obtained from the user terminal 20.

The operator may search the attribute information DB 200 based on the car number and input attribute information corresponding to the search results to the server 10, or the process of sending a search request including the car number to the attribute information DB 200 and the process of inputting attribute information corresponding to the search results sent from the attribute information DB 200 may be automated. That is, it is sufficient that the attribute information obtained based on the car number is input to the server 10.

When the attribute information is input, the CPU 151 of the server 10 stores the attribute information in association with the user ID (step S24).

Next, the CPU 151 of the server 10 sends a vehicle price acquisition request including the attribute information to the used car market price DB 250, and acquires the corresponding vehicle price from the used car market price DB 250 (step S25). In step S25, for example, the CPU 151 may extract information required for searching the used car market price from the attribute information (such as vehicle type, year, mileage, remaining period of vehicle inspection, etc.) and send the information to the used car market price DB 250. The used car market price DB 250 searches for the used car market price based on the information and returns the search result to the server 10. The used car market price DB 250 may be any that returns the vehicle price or vehicle price range (price range) as the used car market price.

In addition, the operator may search the used car market price DB 250 based on the attribute information and obtain the vehicle price corresponding to the search results.

When the vehicle price is acquired, the CPU 151 of the server 10 adds the vehicle price in association with the user ID and attribute information (step S26). The vehicle price may be a vehicle price range. Thereafter, the member registration process is terminated.

Through the above member registration process, the user ID, car number, attribute information, and vehicle price are associated and stored in the management information DB 120, completing the user's registration as a member of the vehicle information management system 1. In this way, simple operations such as registering friends via a communication application and inputting a car number allow a user to register as a member to receive information from a store that has introduced the vehicle information management system 1, encouraging users to register as members and helping to acquire new customers and retain existing customers, thereby contributing to the expansion of business. It also makes it possible to distribute information based on attribute information corresponding to the input car number, allowing useful information to be distributed to the user.

Furthermore, the server 10 can efficiently collect vehicle information owned by users and automatically link vehicle prices to the collected vehicle information. This makes it possible to propose vehicle sales using the vehicle information and vehicle prices and to mediate private sales, which can lead to the promotion of private sales of vehicles. At a specified time, such as when the vehicle inspection expires as indicated by the attribute information, it is possible to check whether there have been any changes to the car number, and if there have been any changes, to prompt the user to enter a new car number. In this way, the user's latest vehicle information (attribute information) can be stored and managed. The message prompting the user to enter a new car number may include information or a coupon corresponding to the new vehicle that can be received. This can encourage the user to enter a new car number.

Figure 6 shows an example of information stored in the management information DB 120. Figure 6 (A) shows store information. In order for a store to introduce the vehicle information management system 1, it is necessary to register store information in advance in the vehicle information management system 1. The store information is information in which a store ID, a store name, member information, information distribution settings, etc. are associated. The store ID is identification information for uniquely identifying a store, and is automatically assigned, for example, when the store information is registered. The store name is the name of the store corresponding to the store ID. The member information is information of the members belonging to the store (member ID, number of members, etc.). The information distribution setting is information that defines the type of information to be distributed by the store, the type of coupon, and the distribution time. The store information is, for example, input by the operator of the vehicle information management system 1 based on information heard from the store. The information distribution setting may be directly set by the store. Among the information distribution settings, multiple coupon distribution scenarios that define the type of coupon and the distribution time may be prepared and the store may select one. Other information (business type, location, business hours, etc.) may also be associated with the store information.

Figure 6 (B) shows member information (vehicle information). Member information is information in which a member ID, a user ID of a communication application, a car number (automobile registration number), attribute information (vehicle inspection certificate information), vehicle price, maintenance and construction history, coupon distribution and usage history, etc. are associated. Member information is created by the member registration process of Figure 5 when a user registers a friend with a store that has the vehicle information management system 1. The member ID is identification information for uniquely identifying a member of the vehicle information management system 1, and is automatically assigned when a friend registration request (user ID) of the communication application is accepted. The member ID may be made to identify which store the member is a member of by a part of the member ID, etc. The user ID of the communication application, the car number, the attribute information, and the vehicle price are information stored in the member registration process of Figure 5. Member information is information in which the attribute information of a vehicle and the vehicle price are associated, and can also be called vehicle information. Coupon distribution and usage history is information indicating the distribution history and usage history of coupons for that member. Maintenance and construction history is the construction history of coatings and the like at the store, and maintenance history, and is registered arbitrarily from the store terminal 30. The maintenance and construction history may be included in the attribute information. The coupon distribution and usage history may be updated when a coupon is distributed or used. Other information (personal information, contact information, etc.) may be associated with the membership information. For example, purchasing information at the store and information regarding equipment may be stored in association with each other. In addition, the other information may be registered by the user (member) via the user terminal 20, for example.

In this embodiment, a member ID is assigned when registering as a member, but it is also possible to identify a member by the user ID of the communication application without assigning a member ID. Also, it is also possible to create a member ID in a separate process, and then link the previously created member ID to the user ID of the communication application later.

Figure 7 is a flowchart showing the operation of the buy/sell request acceptance and matching process executed by the search unit 112 of the server 10, etc. The buy/sell request acceptance and matching process accepts requests for vehicle sales and purchases in private transactions, and when a sale request and a purchase request match, notifies the member (user) that a match between the sale request and the purchase request has been achieved. The CPU 151 of the server 10 executes the buy/sell request acceptance and matching process at all times or during request acceptance times (business hours), etc., to monitor the receipt of various requests.

In the purchase/sale request acceptance/matching process, the CPU 151 first determines whether or not a request to sell a vehicle has been received from the user terminal 20 of the seller user who will be the seller of the vehicle (step S51).

Figure 10 (A) shows an example of a private sale menu screen displayed on the user terminal 20 of the vehicle information management system 1. The private sale menu screen may be transitioned from, for example, a menu screen of a communication application (member menu of any store). The private sale menu screen can be transitioned by any store member. As shown in Figure 10 (A), the private sale menu screen displays an operation button 201 for sending a request to sell a vehicle, and when the operation button 201 is operated, a request to sell a vehicle is sent to the server 10. At this time, the desired selling price (desired selling price range) may be set. Also, an image of the vehicle may be attached. Note that since the vehicle information (vehicle inspection certificate information + maintenance/construction history, etc.) of the user of the vehicle information management system 1 is stored in advance, the user does not need to register his/her own vehicle information again. When a user sells a vehicle in a private sale, it is necessary to register the vehicle information in detail for the safety and clarity of the transaction. In this system, detailed vehicle information, which is attribute information, is registered without the user being aware of it, so there is no need to register detailed vehicle information again, which improves the convenience when the user registers a vehicle sale request. Furthermore, from the buyer's perspective, detailed vehicle information such as maintenance and construction history can be referenced, which can encourage purchasing. When submitting a request to sell a vehicle, attribute information and maintenance and construction history stored in association with the user's user ID may be displayed, allowing the user to complete vehicle information not included in the attribute information.

When a request for selling a vehicle is received (step S51; Yes), the CPU 151 generates vehicle information for sale based on the member information (attribute information, vehicle price, etc.) corresponding to the seller user (user ID) who sent the request, and stores the generated vehicle information for sale in the sales request DB 121 (step S52). As shown in FIG. 8 (A), the vehicle information for sale may include a sales information ID that is identification information for the vehicle information for sale, vehicle information included in the attribute information and the request for sale, the desired selling price, and notification information when a match is made. The sales information ID may be automatically assigned when the vehicle information for sale is generated. The vehicle information may be extracted from the attribute information and the request for sale stored in the management information DB 120. For example, the vehicle information may be, as shown in FIG. 8 (A), a vehicle model, year, color, mileage, equipment, vehicle inspection information, maintenance and construction history, images, etc. In addition to these, the manufacturer, vehicle type, etc. may be included. The manufacturer and vehicle type may be classified on the server 10 side based on the vehicle model. If any information is missing, the user may supplement it. The more detailed the vehicle information, the more useful information can be provided to the buyer, facilitating sales. The desired selling price may reflect the vehicle price stored in the management information DB 120, or may reflect the user's desired price. The desired selling price may be a price range. The notification information may be the user ID of the communication application, an optional email address, or a telephone number. The vehicle information desired for sale may also include other information (sale deadline or timing, sale method, etc.).

If a request to sell a vehicle has not been received (step S51; No), or after executing the processing of step S52, the CPU 151 determines whether or not a request to view the vehicle information to be sold has been received from the user terminal 20 of the buyer user who will be the buyer of the vehicle (step S53).

As shown in FIG. 10(A), the private sale menu screen displays an operation button 202 for sending a request to view information on vehicles to be sold, and when the operation button 202 is operated, a request to view is sent to the server 10. At this time, the vehicle search conditions, desired price, and desired price range may be set.

When a request to view vehicle information for sale is received (step S53; Yes), the CPU 151 transmits the vehicle information for sale stored in the sales and purchases DB 121 to the sender of the request to view (step S54). If the request to view vehicle information for sale includes search conditions and a desired price, the vehicle information for sale corresponding to the search conditions and the desired price may be transmitted. In addition, a list screen of vehicle information for sale that allows the user to narrow down vehicle information or search for specific vehicle information may be transmitted.

If a request to view the vehicle information to be sold has not been received (step S53; No), or after executing the process of step S54, the CPU 151 determines whether a request for a purchase specifying the vehicle information to be sold has been received from the user terminal 20 of the buyer user (step S55). A request for a purchase specifying the vehicle information to be sold may be sent, for example, by specifying the vehicle information from a viewing screen for the vehicle information to be sold.

When a purchase request specifying the vehicle information to be sold is received (step S55; Yes), the CPU 151 notifies the notification destination of the seller user specified by the notification destination information of the vehicle information to be sold that there is a purchase request (step S56). For example, as shown in FIG. 10(B), the notification destination of the seller user may be notified so that a message 211 such as "Your request to purchase your car has been received" is displayed on the display screen of the user terminal 20, along with a link 212 for viewing detailed information (purchase price, timing, etc.) and an operation button 213 for proceeding to the sales procedure.

In addition, a vehicle buyer user may be able to bookmark, favorite, watchlist, follow, like, etc., the vehicle information to be sold as a preliminary step to sending a specific purchase request. The seller user may be notified of the registration status and browsing history. In addition, messages may be sent between the buyer user and seller user to request information or images, negotiate prices, etc. In this way, private buying and selling of vehicles can be promoted.

If a purchase request has not been received (step S55; No), or after executing the process of step S56, the CPU 151 determines whether a request to register desired vehicle purchase conditions has been received from the buyer user's user terminal 20 (step S57). The desired vehicle purchase conditions may be information that specifies at least one of the vehicle model, vehicle type (light car, sedan, minivan, etc.), and desired purchase price, for example.

As shown in FIG. 10(A), the P2P sales menu screen displays an operation button 203 for sending a request to register the desired selling conditions for a P2P sale, and when the operation button 203 is operated, the screen transitions to one for specifying the desired selling conditions, such as the vehicle conditions and the desired purchase price, and sending a request to register the desired selling conditions. The user terminal 20 can then send to the server 20 a request to register the desired selling conditions according to the operation content on the screen.

When a registration request for the desired purchase conditions of a vehicle is received (step S57; Yes), the CPU 151 generates desired purchase conditions information based on the request and stores the generated desired purchase conditions information in the purchase and sale request DB 121 (step S58). The desired purchase conditions information may include a desired condition ID that is identification information of the desired purchase conditions information, the vehicle conditions included in the registration request for the desired purchase conditions, the desired purchase price, and notification information when a match is established, as shown in FIG. 8 (B). The desired condition ID may be automatically assigned when the desired purchase conditions information is generated. The vehicle conditions and the desired purchase price may be extracted from the registration request for the desired purchase conditions. The vehicle conditions may be, for example, as shown in FIG. 8 (B), one or more conditions such as the vehicle model, vehicle type, year, color, mileage, equipment, and remaining period of vehicle inspection. The desired purchase price does not necessarily have to be specified. In this case, all price ranges are searched. The notification information may be a user ID of the communication application from which the desired purchase conditions are sent, an optional email address, or a phone number. The desired purchase conditions information may also include other information (purchase deadline, time, purchase method, etc.).

If a request to register the desired purchase conditions has not been received (step S57; No), after executing the process of step S58, the CPU 151 executes a process of matching the sale request with the purchase request (step S59).

In step S59, the vehicle conditions and the desired purchase price (purchase request) of the desired purchase condition information stored in the desired purchase DB 121 are compared with the vehicle information and the desired sale price (sale request) of the vehicle information desired for sale stored in the desired purchase DB 121 to determine whether there is a match. If there is a match, it is determined that the desired purchase and the desired sale are matched, and the desired purchase condition information and the desired vehicle for sale information are stored. This matching process is performed for each desired purchase condition information stored in the desired purchase DB 121. In step S59, the matching process may be performed for all desired purchase conditions stored in the desired purchase DB 121, or for specified desired purchase conditions (for example, desired purchase conditions that have been registered recently, or desired purchase conditions that have been registered a while ago since the last search).

A perfect match between the purchase offer and the sale offer may be determined to be a match, or a partial match between the purchase offer and the sale offer (for example, the vehicle conditions match but the desired price differs, or only some conditions do not match) may be saved as partial matching information. The degree of match may also be quantified, and a match may be determined to be a match if the degree of match is equal to or greater than a predetermined value.

After executing the matching process in step S59, it is determined whether a match has been made between the sale request and the purchase request (step S60). If a match has been made (step S60; Yes), the CPU 151 notifies the user terminals 20 of the buyer user and seller user, which are the recipients of the matching desired purchase condition information and the desired vehicle for sale information, of matching information indicating that a match has been made between the sale request and the purchase request (step S61).

As shown in FIG. 10(C), the matching information may include, for example, a message 221 indicating that a match has been made on the display screen of the user terminal 20, a link 222 for viewing detailed information (vehicle information, price information), and an operation button 223 for transitioning to a transaction procedure screen. The transaction procedure screen may be a screen for sending a message to the transaction partner and selecting a transaction method (payment method, delivery method, etc.). In this embodiment of the vehicle information management system 1, private transactions are assumed, but the vehicle information management system 1 may also act as an intermediary for payment processing and delivery. In addition, it may be possible to request and reserve vehicle inspection, maintenance, and part replacement via the vehicle information management system 1 before delivery of the vehicle.

In this embodiment, an example is shown in which the buyer and seller are notified of the same matching information, but different matching information may be notified to the buyer and seller. Furthermore, when multiple sales requests match the buyer's desired purchase condition information, the number of matches may be displayed, the information on each vehicle requested for sale may be made available, and the buyer may be able to select which transaction to complete. The matching information may be notified to the seller after the buyer selects to complete the transaction.

If there is partial matching information in which the purchase offer and sale offer partially match, the buyer and seller may be notified of the partial matching information including the non-matching information. The partial matching information may include information inquiring of the buyer and/or seller as to whether or not they wish to revise the conditions (such as the desired price or desired equipment).

If there is no information matching the selling request and the buying request (step S60; No), or after executing the process of step S61, the buying/selling request acceptance and matching process is terminated.

In this embodiment of the buy/sell request acceptance and matching process, it is assumed that the server 10 communicates with the user (receives requests and notifies information) via the user terminal 20 and a communication application, but it may also communicate with the user via other communication terminals or other software such as a web browser or email.

This type of buying and selling request acceptance and matching process allows for the registration of buying and selling requests, and the matching process between buying and selling requests. When a match is made, the seller user and the buyer user are notified of this, which effectively promotes buying and selling between individuals.

Figure 9 is a flowchart showing the operation of the distribution information determination process executed by the information distribution unit 106 of the server 10. The distribution information determination process is a process related to the information distribution function, which is another function of the vehicle information management system 1. The CPU 151 (information distribution unit 106) of the server 10 executes the distribution information determination process at a predetermined cycle (e.g., once a day, etc.), determines whether or not to distribute information to members (users) and what information to distribute, and transmits information according to the determination result to the user terminal 20 via a communication application. In the distribution information determination process, the CPU 151 first refers to all member information stored in the management information DB 120, and determines whether the period until the expiration date of the vehicle inspection validity period (vehicle inspection expiration date) of the attribute information included in the member information is 90 days (step S31).

If there are 90 days until the expiration date of the vehicle inspection (step S31; Yes), the CPU 151 decides to distribute vehicle inspection information to the member (step S32). The vehicle inspection information may include the number of days until the expiration date of the vehicle inspection, the estimated cost of the vehicle inspection, coupons that can be used at the time of the vehicle inspection, information for accepting reservations, etc. The estimated cost of the vehicle inspection may be calculated based on attribute information (vehicle type, year, mileage, etc.). Note that here, it is determined whether there are 90 days until the expiration date of the vehicle inspection, and the vehicle inspection information is distributed to the user 90 days before the expiration date of the vehicle inspection, but the timing of the determination and distribution may be any time before the expiration date of the vehicle inspection, as long as the vehicle inspection information can be distributed appropriately.

If there are less than 90 days until the expiration date of the vehicle inspection (step S31; No), or after executing the process of step S32, it is determined whether it is time to distribute product information (step S33). The timing of distributing product information may be determined in advance based on the date, time, or day of the week, or may be determined by the store's information distribution settings.

If it is time to distribute product information (step S33; Yes), the product information to be distributed is determined based on the vehicle model and year included in the attribute information of the member information and the store's information distribution settings (step S34). In step S34, for example, if the store is performing car coating work and the store's information distribution settings are set to distribute car coating information, the car coating product information to be distributed is determined based on the vehicle model and year. For example, if the vehicle is an imported car or a car purchased within one year, it may be determined that high-added-value car coating product information will be distributed, if the vehicle is older than a certain age, it may be determined that low-cost car coating product information will be distributed, and if the vehicle is other than that, it may be determined that regular car coating product information will be distributed. In this way, the product information to be distributed may be determined based on at least one of the vehicle model and year included in the attribute information.

The product information to be distributed may be determined based on other attribute information (engine displacement, mileage) or other member information (member's birthday, model information of car navigation system or car audio system, etc.). Also, there may be product information (such as new product information) that is sent based on the store's information distribution settings, regardless of the member's attribute information.

If it is not the time to distribute product information (step S33; No), or after executing the process of step S34, it is determined whether it is the time to distribute transfer information (step S35). The timing to distribute transfer information may be determined in advance on a date, time, or day of the week, or may be determined by the store's information distribution settings.

If it is time to distribute vehicle switching information (step S35; Yes), the CPU 151 determines the member's degree of intention to switch vehicles (purchase a new car) based on the vehicle model, year, and mileage included in the attribute information of the member information (step S36).

Generally, if the model year is newer, breakdowns and other problems are less likely to occur and the likelihood of changing cars (buying a new car) is low; as the model year increases, problems become more likely and the likelihood of changing cars increases. Also, if the mileage of a car is short, breakdowns and other problems are less likely to occur and the likelihood of changing cars is low, but as the mileage increases, the number of cases where breakdowns and other problems occur increases and the likelihood of changing cars increases. Also, the tendency to change cars differs depending on the model of the car.

In this embodiment, the degree of intention to switch vehicles is ranked according to vehicle model, year, and mileage into a predetermined number of stages, and the degree of intention to switch vehicles is determined based on the combination of the ranks. For example, the degree of intention to switch vehicles may be quantified for each combination of ranks.

A database that classifies the ranks of switching intentions is created, for example, by collecting and analyzing questionnaires of users who indicated their intentions, interests, and concerns about purchasing a new vehicle, changing their vehicle, or switching vehicles. For example, the correlation between the vehicle model, year, and mileage entered in the questionnaire and whether or not they actually switched vehicles, and their intentions, interests, and concerns about switching vehicles can be analyzed, and vehicle models, years, and mileage with high correlations can be classified as high ranks. Note that other attribute information, such as the remaining period of vehicle inspection, whether the vehicle is a personal or commercial vehicle, and the owner's age, may also be used to determine the degree of intention to switch vehicles.

Next, the CPU 151 determines whether the degree of intention to switch, determined based on the vehicle model, year, and mileage, is greater than a predetermined threshold (step S37). This threshold may be any value that determines that the degree of intention to switch is high, and may be a value determined in advance based on experience or statistics, or may be determined by the store's information distribution settings.

If the degree of intention to switch is greater than a predetermined threshold (step S37; Yes), it is decided to distribute switching information to the member (step S38). The switching information may include, for example, the going rate in case of a private sale (vehicle price stored as member information), the approximate trade-in price in case of dealer purchase, the approximate price of a new car or lease, coupons that can be used when switching, and other campaign information that is applied when switching. The going rate in case of a private sale may be the price stored in association with member information as the vehicle price. Furthermore, the approximate trade-in price may be calculated based on attribute information (vehicle type, year, mileage, etc.).

If it is not the time to distribute transfer information (step S35; No), if the degree of transfer intention is equal to or lower than a predetermined threshold (step S37; No), or after the processing of step S38 has been executed, it is determined whether it is the time to distribute a coupon (step S39). The timing of coupon distribution may be determined in advance as a date, time, or day of the week, or may be determined by the store's information distribution settings.

If it is time to send a coupon (step S39; Yes), the CPU 151 determines which coupon to distribute based on the store's information distribution settings (step S40). In step S40, for example, it may be determined to distribute a coupon of the type set in the information distribution settings (e.g., coupons for refueling, car washes, repairs, oil changes, etc.). The coupon to distribute may also be determined based on a coupon distribution scenario that predetermines the coupon type, distribution time, distribution order, etc.

If it is not the timing for coupon distribution (step S39; No) or after executing the process of step S40, the CPU 151 refers to the desired purchase conditions stored in the trader desire DB 121 and searches for vehicle information stored in the management information DB 120 to determine whether vehicle information having attribute information corresponding to the desired purchase conditions is stored in the management information DB 120 (step S41). In step S41, a search may be performed for all desired purchase conditions stored in the trader desire DB 121, or a search may be performed for specific desired purchase conditions (for example, desired purchase conditions that have been registered recently, or desired purchase conditions that have been registered a while ago since the previous search).

If there is vehicle information with attribute information that meets the desired purchase conditions (step S41; Yes), the CPU 151 decides to distribute purchase request information indicating the existence of a buyer and the desired purchase price to the member who is the owner of the vehicle with that attribute information (step S42). Note that the purchase request information may be information that at least indicates that there is a buyer for the vehicle owned by the member. For example, as shown in FIG. 10(D), the purchase request information displayed on the user terminal 20 may include a message 401 such as "Someone wants to buy your car!", a link 402 for viewing detailed purchase request information (desired price, timing, purchase conditions, etc.), an operation button 403 for registering a sale request, etc.

By distributing such purchase request information to members, it is possible to make users who did not initially plan to sell a vehicle interested in selling a vehicle, and to encourage private vehicle buying and selling. Note that the purchase request information does not need to be distributed to all members, but may be distributed only to members who are determined in step S37 to have a switching intention degree greater than a predetermined threshold. In this way, it is possible to prevent unnecessary transmission of purchase request information while distributing purchase request information to users who are highly interested in switching, thereby effectively encouraging the sale of vehicles and ensuring the number of vehicle information items to be sold.

If there is no vehicle information having attribute information that meets the desired purchase conditions (step S41; No), or after executing the process of step S42, the CPU 151 transmits the information that has been decided to be distributed to the corresponding user terminal 20 via a communication application (step S43). Thereafter, the distribution information determination process ends.

By executing this type of distribution information determination process, it is possible to distribute information according to the store's settings and the attribute information of each member's vehicle. In particular, since the information to be distributed is determined according to the attribute information of the member's vehicle, it becomes possible to distribute useful information that is appropriate for the member.

Next, a display example on the display screen of the user terminal 20 when using the vehicle information management system 1 will be described. FIG. 11(A) shows an example of a friend registration screen for a store in a communication application. At a gas station A, which is a store that has introduced the vehicle information management system 1, when a user performs a friend registration operation in a communication application, such as reading a two-dimensional code printed on a medium (POP, poster, etc.) installed at the gas station A with the camera of the user terminal 20, the name and icon of the gas station A and a friend registration button 21 are displayed on the display screen of the user terminal 20, as shown in FIG. 11(A). The user can register gas station A as a friend by touching the friend registration button 21, and thereby register as a member of the vehicle information management system 1 (register for information distribution from gas station A).

When gas station A is registered as a friend, a friend registration message is displayed from server 10 via the communication application, and the message is displayed on the display screen of user terminal 20, as shown in FIG. 11 (B). The friend registration message includes a message encouraging the user to register a car number. The message display screen includes a menu button 22, and in this embodiment, the car number registration screen can be called up by touching menu button 22.

When the user touches the menu button 22 and calls up the car number registration screen from the menu item, the car number registration screen is displayed on the display screen of the user terminal 20 as shown in FIG. 11 (C). The car number (car registration number) includes character information such as "Shinagawa" indicating the transport bureau that has jurisdiction over the car, character information such as "sa" indicating whether it is a private car or a rental car, numeric information such as "500" indicating whether it is a regular car or a compact car, and serial number information such as "23-4X". The user inputs this information using the input means (touch panel, etc.) of the user terminal 20 and touches the "Register" button, whereby the car number is transmitted to the server 10. The transmitted car number is stored in the management information DB 120 of the server 10 in association with the user ID of the communication application. As a result, the car number is registered in the user's membership information for gas station A. In this way, simple operations such as registering friends via a communication application and entering the vehicle number allow users to register as members to receive information from a store that has installed the vehicle information management system 1 (in this case, gas station A), which encourages users to register as members and is expected to help acquire new customers and retain existing customers, thereby contributing to the expansion of business operations.

As shown in FIG. 11(C), a "photograph" button and an "image load" button may be provided, and when entering the car number, the number plate may be photographed with the camera of the user terminal 20, and the car number may be captured by character recognition from the captured image, or an image that has already been photographed may be loaded and the car number may be captured from that image. This improves user convenience and encourages the user to register a car number. The car number registration screen shown in FIG. 11(C) may be displayed following the message displayed when registering a friend, as shown in FIG. 11(B).

Figure 11 (D) is an example of the display of a coupon sent from the server 10 via a communication application on the display screen of the user terminal 20. When the coupon type is a fuel coupon, as shown in Figure 11 (D), a coupon image 24 indicating that it is a fuel coupon, the discount amount, the expiration date, etc. is displayed on the message screen of the communication application.

When using a coupon, for example, the user touches the coupon image 24 on the message screen or selects an acquired coupon, which transitions to a coupon usage screen. The coupon can then be used by presenting the usage screen at the time of payment at the target store (in this case, gas station A). When the store performs a usage process on the usage screen (for example, by touching a button to mark the coupon as used), the coupon is marked as used, and coupon usage information is sent to server 10 via the communication application. This allows server 10 to manage the coupon usage history and manage whether the coupon is valid or invalid (such as deducting the number of times it has been used and deleting used coupons).

The coupon usage screen is not limited to one that becomes available when the store processes the coupon, but may display a coupon image that can be used simply by presenting the coupon, a coupon number that is processed by the store's payment device, a barcode, etc. In this case, the server 10 may obtain the coupon usage status from the store (a POS (Point of Sale) terminal, a fuel pump, etc.) and use it to analyze the coupon usage history.

In addition, according to the vehicle information management system 1 of the above embodiment, a user can register as a member for information distribution by simple operations such as registering friends via a communication application and inputting a car number. Since registration can be performed through such simple operations and vehicle information (attribute information) can be obtained based on the car number, a large amount of vehicle information can be collected and a database with a large amount of vehicle information can be constructed.

Based on the vehicle information collected in this way, seller users can register their desire to sell through peer-to-peer transactions, and as there is no need to input detailed vehicle information again, they can easily register their desire to sell, which can promote the sale of users' vehicles. Furthermore, the registered vehicle information for sale is matched with separately registered desires to buy, which can effectively promote peer-to-peer transactions.

In addition, the information to be distributed is determined based on attribute information corresponding to the registered car number, and the determined information is distributed to the user, making it possible to distribute information suitable for the vehicle owned by the user, which is expected to lead to the acquisition of new customers and retention of existing customers, contributing to an increase in the number of customers and the expansion of business operations.

(Modification)
The present invention is not limited to the above-mentioned embodiment, and various modifications and applications are possible, and further features may be added. For example, the configurations and processing contents shown in the above-mentioned embodiment are merely examples, and any configuration may be used as long as it can achieve the same functions and effects as the above-mentioned embodiment. Furthermore, not all of the configurations described in the above-mentioned embodiment are essential configurations, and some of them may be missing.

The buyer user may be a user other than a member of the vehicle information management system 1. For example, the contents corresponding to the sales request information stored in the sales request DB 121 may be uploaded so that they can be viewed on a portal site for vehicle sales and purchases, and a request to register a purchase request or desired purchase conditions may be sent from the portal site.

When seller users register their desired purchasing conditions, they may be able to set the priority of the conditions, and register second and third preference conditions, etc. In other words, the range of conditions may be expanded as desired. This can improve the frequency of matching.

After a vehicle is traded through the vehicle information management system 1, the management information DB 120 and the trade request DB 121 may be updated according to the results of the trade. For example, when a trade is concluded, the corresponding vehicle information to be sold and the desired purchase conditions information may be deleted. When a trade is concluded, the vehicle information (car number, attribute information, vehicle price, maintenance and construction history) in the member information of the seller user may be deleted, and the vehicle information in the member information of the buyer user may be updated based on the vehicle information. In this way, the vehicle information of the buyer user can be registered as vehicle information of a potential seller user. When a trade is concluded, the seller user may be provided with the vehicle information to be sold to encourage the purchase of a new vehicle. In this way, further private vehicle trade can be promoted.

In the above embodiment, the member registration for information distribution to the store that has the vehicle information management system 1 installed has been described as being done by registering as a friend in a communication application, but the user may register with the store at their own will, and may also be done by registering as a bookmark, favorite, watchlist, follow, like, etc.

The type of information to be distributed is not limited to that described in the above embodiment, and may be any information useful to members, such as information about automobiles or information about members. For example, it may be traffic information, tourist information, travel information, weather forecasts, information about the area where the member lives, information about hobbies, news, etc.

In the above embodiment, the user registers the car number, but store staff may register the car number with the user's permission, or the number may be automatically read and registered by a license plate reader (camera) installed in the store. This configuration makes it easier for users to register as members.

In addition, since it is conceivable that one member may own multiple vehicles, it may be possible to register the license plate numbers of multiple vehicles for one member's information. In this case, the information to be distributed may be determined based on the attribute information of the multiple vehicles. Furthermore, when the license plate numbers of multiple vehicles are registered, it may be possible to register a wish to sell a specific vehicle.

In the above embodiment, an example in which the attribute information DB 200 is constructed in advance has been described, but the vehicle information management system 1 of the present invention can be realized even if the attribute information DB 200 is not constructed in advance. For example, in a shop used by an automobile owner (a shop not limited to a user of the vehicle information management system 1, such as a repair shop or a gas station), when a maintenance person maintains a vehicle, with the consent of the vehicle owner, the maintenance person reads the QR code printed on the vehicle inspection certificate using a maintenance terminal device capable of reading QR codes (registered trademark). This QR code contains attribute information of the vehicle, such as the engine displacement, model year, and vehicle inspection expiration date. Then, this attribute information and the car number may be directly transmitted to the server 10 via the communication network 90, or the attribute information DB 200 may be constructed based on this attribute information. This makes it possible for the server 10 to acquire attribute information. With this configuration, the vehicle information management system 1 can be realized even in a situation in which the attribute information DB 200 does not exist, and useful information can be provided to the user.

Similarly, the used car market price DB 250 is not limited to being constructed externally, but may be constructed based on sales history in the vehicle information management system 1, or the vehicle price may be calculated by combining an externally constructed database with a database constructed in the vehicle information management system 1.

In addition, a coupon distribution scenario that specifies the type of coupon and distribution time at any timing may be generated or updated. The management information DB 120 stores the coupon usage history of members of all stores that have introduced the vehicle information management system 1. For example, if 100 stores have introduced the vehicle information management system 1, the coupon usage history of members of all 100 stores will be accumulated. The server 10 may use this big data to generate and update an optimal coupon distribution scenario.

For example, the CPU 151 of the server 10 collects coupon distribution and usage history contained in the membership information of all members stored in the management information DB 120, analyzes the collected coupon distribution and usage history, and generates or updates a coupon distribution scenario including the type of coupon, distribution time, distribution conditions, etc. based on the analysis results.

For example, the CPU 151 uses machine learning to learn correlations between the type of coupon distributed and frequency of use, correlations between distribution time and use time, type of coupon used, correlations between distribution time and attribute information of the member's automobile (model, year) and member information (age, gender, etc.), etc., to determine optimal coupon types, distribution times, and distribution conditions, and reflect these in the coupon distribution scenario. For example, the correlation between the usage interval of a refueling coupon and attribute information can be analyzed, and a distribution scenario for a refueling coupon based on the attribute information can be generated. Analysis can also be performed taking into account regionality and season. Various algorithms such as decision trees, correlation rules, neural networks, and support vector machines can be used as machine learning algorithms.

The generated or updated coupon distribution scenario may be stored in the management information DB 120 and may be made available for reference from, for example, the server 10 or the store terminal 30. Also, for example, the newly generated coupon distribution scenario may be automatically notified to the store terminal 30 together with a message indicating the contents of the scenario. The generated coupon distribution scenario may be applied to the information distribution settings of each store, or a generated coupon distribution scenario may be proposed when the store introduces the vehicle information management system 1. In steps S39 and S40 of FIG. 9, when determining whether or not to distribute a coupon to be distributed and the type of coupon, the generated coupon distribution scenario may be referred to. By periodically executing scenario generation and update, a coupon distribution scenario suited to the member's coupon usage status can be used, and the scenario can be updated at any time according to the member's coupon usage status, so that information and coupons suitable for the user can be distributed. In addition, the store can expect to attract customers and expand its business.

In the above embodiment, the survey for analyzing the degree of intention to switch vehicles can be targeted at people who have actually switched vehicles or who show a strong will or interest in purchasing or switching vehicles, such as visitors to car dealerships, used car dealerships, used car auction participants, and car leasing users, which is expected to improve the analysis accuracy of the degree of intention to switch vehicles. Note that, in order to broaden the scope of the analysis, the survey may be targeted at people who show a certain degree of interest in switching vehicles, such as car sharing users, driving club members, and users of price comparison sites for vehicle switching.

In the above embodiment, the member's degree of intention to switch is determined based on the vehicle model, year, and mileage, but the degree of intention to switch may be determined based on at least one of the vehicle model, year, and mileage. For example, the degree of intention to switch may be determined simply based on the rank of the year only. Also, if any of the information on the vehicle model, year, and mileage is missing, the missing information may be excluded and the degree of intention to switch may be determined based on only the available information. Alternatively, the missing information may be supplemented or estimated to determine the degree of intention to switch.

For example, the mileage that can be obtained as attribute information is the mileage at the time of the last vehicle inspection, so the mileage cannot be obtained for vehicles that have been registered for less than three years. In this case, the degree of intention to switch vehicles may be determined based on the vehicle model and year.

The mileage when determining the degree of intention to switch may be estimated based on, for example, the period (model year) from the first year of registration to the last vehicle inspection, the mileage at the last vehicle inspection, the period of time since the last vehicle inspection, etc. In addition, if the member's mileage is input from the store terminal 30, the information on that mileage may be applied.

The member's intention to switch vehicles may also be determined based on other attribute information (engine displacement, etc.) or other member information (member age, etc.).

The server 10 can be realized using a normal computer, not a dedicated device. For example, the server 10 of the vehicle price management system 1 that executes the above-mentioned processes may be configured by installing a program for executing any of the above-mentioned processes on a computer from a recording medium that stores the program. Also, a single accident analysis system 1 may be configured by multiple computers operating in cooperation with each other.

The method for supplying the program to the computer is arbitrary. For example, the program may be supplied via a communication line, a communication network, a communication system, etc.

The above-described embodiments are intended to facilitate understanding of the present invention, and are not intended to limit the present invention. The flowcharts, sequences, display examples, data structures, elements of the embodiments, and their arrangements, materials, conditions, shapes, sizes, etc., described in the embodiments are not limited to those shown as examples, and may be modified as appropriate. Furthermore, configurations shown in different embodiments may be partially substituted or combined.

1 Vehicle information management system 10 Server 101 Registration number receiving unit 102 Attribute information input unit 103 Memory unit 104 Vehicle price acquisition unit 105 Vehicle price memory unit 106 Information distribution unit 107 Sale request receiving unit 108 Sale request memory unit 109 Vehicle information transmission unit 110 Purchase request condition receiving unit 111 Purchase request condition memory unit 112 Search unit 113 Notification unit 114 Attribute information search unit 115 Purchase request receiving unit 120 Management information database 121 Purchase request database 20 User terminal 30 Store terminal 90 Communication network 200 Attribute information database 250 Used car market price database

Claims (8)

a registration number receiving means for receiving a vehicle registration number of a vehicle owned by a user;
an attribute information input means for inputting attribute information corresponding to the vehicle registration number when the vehicle registration number is received from a user;
a storage means for storing in a vehicle information database, in association with the identification information of the user who transmitted the vehicle registration number and the attribute information corresponding to the vehicle registration number;
a vehicle price acquisition means for acquiring a corresponding vehicle price from a used car price database in which market prices of used cars are stored, based on the attribute information stored in the vehicle information database;
a vehicle price storage means for storing the vehicle price acquired by the vehicle price acquisition means in the vehicle information database in association with the user's identification information and the user's attribute information;
an information distribution means capable of distributing to a user information corresponding to the attribute information stored in association with the user;
a vehicle sale request receiving means for receiving a vehicle sale request from a seller user who is a seller of the vehicle;
a sales request storage means for generating sales request vehicle information based on the attribute information and the vehicle price corresponding to the seller user when a sales request is received from the seller user, and storing the generated sales request vehicle information in a sales request database;
a vehicle information transmitting means for transmitting the vehicle information stored in the vehicle sales database to a requester in response to a request to view the vehicle information;
A vehicle information management system comprising: A purchase condition receiving means for receiving vehicle purchase conditions of a buyer user who will be a buyer of the vehicle;
a desired purchase conditions storage means for storing the desired purchase conditions received by the desired purchase conditions receiving means in the trading desire database;
A search means for searching for the vehicle information stored in the sales and purchase request database that matches the desired purchase conditions;
a notification means for notifying the seller user and the buyer user that a match between a purchase request and a sale request has been established when the search means has searched for the vehicle information to be sold that meets the purchase request conditions;
The vehicle information management system according to claim 1 , an attribute information retrieval means for retrieving the attribute information that matches the desired purchase conditions stored in the trader desire database from the vehicle information database;
3. The vehicle information management system according to claim 2, wherein when the attribute information search means is able to search for the attribute information that matches the desired purchase conditions, the information distribution means distributes, as the distribution information, information indicating that the user wishes to purchase a vehicle to the user corresponding to the attribute information. a purchase request receiving means for receiving a request for purchasing a vehicle from a buyer user who is a buyer of the vehicle and who specifies the vehicle sale request information;
a notification means for notifying the seller user corresponding to the vehicle information designated by the purchase request that a purchase request has been received, when the purchase request has been received from the buyer user;
The vehicle information management system according to claim 1 , A vehicle information management system as described in any one of claims 1 to 4, wherein when the sale request storage means receives a sale request from the seller user, it extracts at least one of information regarding the vehicle inspection expiration date, information regarding the vehicle model, information regarding the year, and information regarding the mileage from the attribute information corresponding to the seller user, and generates the vehicle information regarding the vehicle to be sold. The vehicle information management system according to any one of claims 1 to 4, wherein the information distribution means is capable of distributing at least one of information regarding vehicle inspections, product information, information regarding vehicle changes, and coupons as the distribution information based on the attribute information. receiving a vehicle registration number of a vehicle owned by a user;
When receiving the vehicle registration number from the user, input attribute information corresponding to the vehicle registration number;
The identification information of the user who transmitted the vehicle registration number is associated with the attribute information corresponding to the vehicle registration number and stored in a vehicle information database;
Based on the attribute information stored in the vehicle information database, a corresponding vehicle price is obtained from a used car price database in which market prices of used cars are stored;
The acquired vehicle price is added to the vehicle information database in association with the user's identification information and the attribute information;
The information to be distributed to a user corresponds to the attribute information stored in association with the user,
receiving a request to sell a vehicle from a seller user who is a seller of the vehicle;
When a request for sale is received from the seller user, generating vehicle sale information based on the attribute information corresponding to the seller user and the vehicle price, and storing the generated vehicle sale information in a sales request database;
the vehicle information management method further comprising the steps of: in response to a request to view the vehicle information for sale, transmitting the vehicle information for sale stored in the vehicle sales desire database to a requester; Computer,
A registration number receiving means for receiving a vehicle registration number of a vehicle owned by a user;
an attribute information input means for inputting attribute information corresponding to the vehicle registration number when the vehicle registration number is received from the user;
a storage means for storing in a vehicle information database, in association with the identification information of the user who transmitted the vehicle registration number and the attribute information corresponding to the vehicle registration number;
a vehicle price acquisition means for acquiring a corresponding vehicle price from a used car price database in which market prices of used cars are stored, based on the attribute information stored in the vehicle information database;
a vehicle price storage means for adding the vehicle price acquired by the vehicle price acquisition means to the vehicle information database in association with the user's identification information and the user's attribute information;
an information distribution means capable of distributing to a user information corresponding to the attribute information stored in association with the user;
a vehicle sale request receiving means for receiving a vehicle sale request from a seller user who is a seller of the vehicle;
a sales request storage means for generating sales request vehicle information based on the attribute information corresponding to the seller user and the vehicle price when a sales request is received from the seller user, and storing the generated sales request vehicle information in a sales request database;
a vehicle information transmission means for transmitting the vehicle information stored in the vehicle sales database to a requester in response to a request to view the vehicle information;
A program that functions as a

Images