JP2017208041A - Information processor and information processing method - Google Patents

Abstract

PROBLEM TO BE SOLVED: To enhance convenience fo a rental car user.SOLUTION: A travel support server 16 displays a user screen which contains elements for allowing a user to select a driver to whom, drive of a rental car is requested, out of plural drivers who have been registered in advance, on a user terminal 12. The travel support server 16 displays a driver screen which contains elements for allowing an input of whether or not to approve request of drive of the rental car, on a driver terminal 14 of a driver selected on the user screen. The user screen contains an area which allows the user to input attribute information of the rental car which the user has reserved, to a rental car company, and the travel support server 16 displays the attribute information of the rental car input to the user screen, on the driver screen. When the request is approved on the driver screen, the travel support server 16 displays information indicating a fact that, the request is approved, on the user screen.SELECTED DRAWING: Figure 1

Description

  The present invention relates to a data processing technique, and more particularly to an information processing apparatus and an information processing method.

  Prior to travel, accommodation and transportation may be reserved on the website. In the following Patent Document 1, a travel plan providing device is proposed in which a user inputs a departure date and a return date, a budget, a purpose, and the like, and a travel plan is generated based on the input information.

JP 2014-142784 A

  A traveler may use a rental car at a travel destination, but may get lost due to unfamiliarity with the geography of the travel destination. In addition, although there are travelers who want to visit places that are popular among local residents but are not converted into tourist spots, it is not easy for travelers to collect information about such places in advance.

  This inventor was made in view of the said subject, and the main objective is to provide the technique which raises the convenience of a rental car user.

  In order to solve the above problems, an information processing apparatus according to an aspect of the present invention includes an element for causing a user to select a driver who requests driving of a rental car from a plurality of drivers registered in advance. Driving that includes a user screen providing unit that displays the user screen on the user's terminal and an element that allows the driver's terminal selected on the user screen to input whether to approve the request for driving the rental car. A driver screen providing unit for displaying a driver screen. The user screen includes an area that allows the user to input the rental car attribute information reserved by the user to the rental car company. The driver screen provider displays the rental car attribute information entered on the user screen on the driver screen, and the user screen provider displays information indicating that the request is approved on the driver screen. Is displayed on the user screen.

  Another embodiment of the present invention is also an information processing apparatus. This device includes a user screen display unit for displaying a user screen including an element for allowing a user to select a driver who requests driving a rental car from a plurality of registered drivers, and a user screen. Notifying the server when the driver is selected, so that the driver's terminal selected on the user screen via the server can input whether to approve the driving request for the rental car And a notification unit for displaying a driver screen including the elements. The user screen includes an area for allowing the user to input the rental car attribute information reserved by the user to the rental car company. The notification unit notifies the server of the rental car attribute information so that the rental car attribute information is displayed on the driver screen, and the user screen display unit indicates that if the request is approved on the driver screen. The information to be displayed is displayed on the user screen.

  Yet another embodiment of the present invention is an information processing method. In this method, a user screen including an element for causing a user to select a driver who requests driving of a rental car from a plurality of drivers registered in advance is displayed on the user's terminal; The computer executes a step of causing the driver's terminal selected on the screen to display a driver screen including an element for inputting whether to approve a request for driving a rental car. It includes an area where the user inputs the rental car attribute information reserved by the car rental company. The step of displaying the driver screen displays the rental car attribute information entered on the user screen on the driver screen, and if the request is approved on the driver screen, the computer uses information indicating that The step of displaying on the person's screen is further executed.

  It should be noted that any combination of the above-described constituent elements, the present invention expressed by a system, a computer program, a recording medium storing the computer program, etc. are also effective as an aspect of the present invention.

  According to the present invention, convenience for rental car users can be enhanced.

It is a figure which shows the structure of the information system of 1st Example. It is a block diagram which shows the function structure of the travel assistance server of FIG. It is a block diagram which shows the function structure of the user terminal of FIG. It is a block diagram which shows the function structure of the driver | operator terminal of FIG. It is a flowchart which shows operation | movement of a travel assistance server. It is a figure which shows the example of an application page. It is a figure which shows the example of a matching confirmation page. It is a figure which shows the example of a matching confirmation page. It is a flowchart which shows operation | movement of a travel assistance server. It is a figure which shows the example of a matching confirmation page. It is a figure which shows the example of a matching confirmation page. It is a block diagram which shows the function structure of the travel assistance server of 2nd Example. It is a flowchart which shows operation | movement of the travel assistance server of 3rd Example.

  The travel support server according to the embodiment provides a service that supports sightseeing using a rental car at a travel destination. Specifically, the travel support server provides information on driver candidates that can be entrusted with driving a rental car, and supports CtoC (Consumer-to-Consumer) that supports selection of drivers according to the user's preference and purpose of travel. ) Matching service. The user selects a driver who entrusts driving a rental car from among drivers registered on a website (hereinafter referred to as “travel support site”) provided by the travel support server.

  The travel support site provides a matching service between the user and the driver, and it is the user to rent a car from a rental car company and to entrust the driver who matched with the travel support site to drive the car. Do it yourself. In addition, the user and driver will negotiate directly and contract for specific rewards and destinations.

  The “user” in the embodiment is a person who plans to rent a rental car at a travel destination, and is a person who selects a driver who entrusts driving a rental car using a travel support site. It can be said that it is a traveler. In addition, the “driver” in the embodiment is a person registered as a driver on the travel support site, and can be said to be a driver candidate who can be entrusted with driving a rental car from the user. Typically, the driver is a person who lives in the travel destination of the user and is familiar with the circumstances and geography of the travel destination. The matching service of the embodiment can be said to be a pairing service between the user and the driver.

(First embodiment)
FIG. 1 shows the configuration of the information system 10 of the first embodiment. The information system 10 includes a user terminal 12a, a user terminal 12b, a user terminal 12c, which are collectively referred to as a user terminal 12, and a driver terminal 14a, a driver terminal 14b, and a driver terminal, which are collectively referred to as a driver terminal 14. 14c, a travel support server 16, and a rental car company server 17. These devices are connected via a communication network 18 including a LAN, a WAN, the Internet, and the like.

  The user terminal 12 is an information processing device operated by a user, and the driver terminal 14 is an information processing device operated by a driver. These devices may be PCs, smartphones, and tablet terminals.

  The travel support server 16 is an information processing apparatus that publishes a travel support site on the Internet. The travel support server 16 may be realized by a plurality of servers physically or logically. For example, the travel support server 16 may be realized by cooperation of a web server, an application server, and a database server.

  The rental car company server 17 is an information processing apparatus of a rental car company. The rental car company server 17 holds and manages at least information related to rental car reservations. For example, it holds the rental car attribute information reserved by the user (rental car company and store identification information, car name / car type / class, car smoking status, car driver's license number, license image, etc.). The information system 10 may include a plurality of rental car company servers 17 corresponding to a plurality of rental car companies. The rental car company server 17 may be installed outside the rental car company, and may be a server on the cloud, for example.

  FIG. 2 is a block diagram showing a functional configuration of the travel support server 16 of FIG. The travel support server 16 includes a control unit 20, a storage unit 22, and a communication unit 24. The control unit 20 executes various data processing at the travel support site. The storage unit 22 is a storage area that stores data that is referred to or updated by the control unit 20. The communication unit 24 communicates with an external device according to a predetermined communication protocol. The control unit 20 exchanges data with the user terminal 12 and the driver terminal 14 via the communication unit 24.

  Each block shown in the block diagram of the present specification can be realized in terms of hardware by an element such as a CPU of a computer or a mechanical device, and in terms of software, it can be realized by a computer program or the like. The functional block realized by those cooperation is drawn. Therefore, those skilled in the art will understand that these functional blocks can be realized in various forms by a combination of hardware and software.

  The storage unit 22 includes a driver information holding unit 26, a user information holding unit 28, a matching information holding unit 30, and a message holding unit 32. These functional blocks may be realized by the storage of the travel support server 16 or the main memory storing data corresponding to each functional block.

  The driver information holding unit 26 holds attribute information related to the driver registered by the driver. Specifically, the driver information holding unit 26 holds basic information indicating basic attributes of the driver, driver profile information disclosed to the user, and driver schedule information. The basic information includes a driver ID (identification information for uniquely identifying the driver in the travel support server 16), name, e-mail address, password, license number, license type, license color, license image, Includes driving record certificate.

  The profile information includes a photographic image (thumbnail image published on the travel support site), a nickname (name published on the travel support site), a unit price per hour, a corresponding language, a possession qualification, and a self-PR text. The schedule information includes a vacant date and time and a reserved date and time. The vacant date / time is a date / time or a period in which the user can make a reservation, in other words, a date / time or a period in which the operation commission from the user can be accepted. The reserved date / time is the date / time or period when the user has reserved / restrained, in other words, the date / time or period when the rental car operation is entrusted.

  The user information holding unit 28 holds attribute information related to the user registered by the user. Specifically, the user information holding unit 28 includes a user ID (identification information for uniquely identifying the user in the travel support server 16), a name, an e-mail address, a password, and credit card information.

  The matching information holding unit 30 holds information on matching between the user and the driver (hereinafter referred to as “matching information”). The matching information includes a matching ID (identification information for uniquely identifying a specific matching in the travel support server 16), a user ID, a driver ID, a status, and application information. The application information includes a start date, an end date, outbound flight information, return flight information, the number of people, a rental car company, a store that rents a rental car, the name or model of the rental car, and whether or not to rent a rental car.

  The status is information indicating the matching status, and in this embodiment, the status is one of “approved”, “non-approved”, and “unapproved”. “Approved” indicates a state where a matching application by the user is approved by the driver. “Non-approved” indicates a state in which the user's matching application is unapproved by the driver. Non-approval can also be a rejection, a rejection or a denial. “Unapproved” means that approval or non-approval has not yet been decided, and it can be said that the application is pending.

  The message holding unit 32 holds message data transmitted and received between the user and the driver. Specifically, the message holding unit 32 includes a message ID, a transmission destination ID, a transmission source ID, a matching ID, a subject, and a text.

  The control unit 20 includes a driver registration unit 34, a user registration unit 36, an authentication unit 38, a user screen providing unit 40, a driver search unit 42, a matching information registration unit 44, a driver screen providing unit 46, and a charging unit 48. The message registration unit 50 and the schedule update unit 52 are included. Each function of the control unit 20 may be implemented as a travel support program, stored in a recording medium, and installed in the travel support server 16. And each function of the control part 20 may be implement | achieved when CPU of the travel support server 16 reads a travel support program into the main memory and executes it.

  The driver registration unit 34 receives a driver registration request from the driver terminal 14. The driver registration request includes the attribute information related to the driver described above. The driver registration unit 34 stores attribute information related to the driver indicated by the driver registration request in the driver information holding unit 26. The user registration unit 36 receives a user registration request from the user terminal 12. The user registration request includes the attribute information related to the user described above. The user registration unit 36 stores attribute information about the user indicated by the user registration request in the user information holding unit 28. The authentication unit 38 performs password authentication for the driver and the user who have requested login to the travel support site.

  The user screen providing unit 40 includes a web page (hereinafter referred to as “user page”) including an element for allowing the user to select a driver who requests driving of a rental car from a plurality of drivers registered in advance. ) To the user terminal 12 for display. This element is an object (also referred to as content) set in the user page or displayed / operated on the user page. Examples include text fields, buttons, and forms.

  The user page includes a search page, an application page, a matching confirmation page, and a message confirmation page. The user screen providing unit 40 receives information about an operation input by the user with respect to the user page from the user terminal 12, and according to the operation, a search page, an application page, a matching confirmation page, or a message confirmation page. May be transmitted to the user terminal 12. Further, the user page may include data of a search page, an application page, a matching confirmation page, or a message confirmation page, and the web browser of the user terminal 12 responds to the user's operation on the user page. The contents of these contained pages may be switched from the non-display state to the display state.

  The search page is a web page for searching for a driver. The search page includes an area for inputting a driver attribute (profile or the like) desired by the user as a search condition. The search page may be set so that a start date and time, an end date and time, a unit price for time, a supported language, a qualification, and the like can be input as a search condition.

  When the search request including the search condition input in the search page is received from the user terminal 12, the driver search unit 42 searches the driver information holding unit 26 for a driver that matches the search condition. For example, the driver search unit 42 detects a driver who has an empty schedule in the period from the start date and time specified by the search condition to the end date and time, and searches for a driver having a unit price or less specified by the search condition. To detect. The user screen providing unit 40 transmits the search result by the driver search unit 42 to the user terminal 12 and displays it on the search page. For example, the user screen providing unit 40 transmits detailed information of the driver that matches the search condition to the user terminal 12 and displays it on the search page.

  The application page is a web page for applying for matching to a specific driver. In this embodiment, the application page is displayed when a predetermined operation is input on a search page showing detailed information of a specific driver. The application page includes an area that allows the user to input the rental car attribute information reserved by the user to the rental car company. Specifically, the application page includes an input area for a start date, an end date, outbound flight information, inbound flight information, number of people, rental car company, rental car store, rental car model, and rental car smoking permission.

  The matching confirmation page is a web page that displays a list of one or more matching information requested by the user. The user screen providing unit 40 searches the matching information holding unit 30 for one or more matching information (for example, application information and status) associated with the user ID, and is associated with the user ID. Then, a matching confirmation page showing one or more pieces of matching information is generated, and the data is transmitted to the user terminal 12. In addition, the user screen providing unit 40 sets an element for sending a message from the user to the driver of the matching partner in an area where matching information whose status is approved is displayed.

  The message confirmation page is a web page that displays a list of messages sent from the driver to the user (so-called inbox) and a list of messages sent from the user to the driver (so-called outbox). . The user screen providing unit 40 reads out message data associated with the user (user ID) from the message holding unit 32, and transmits the read message data to the user terminal 12 to display a list. When the user terminal 12 is notified that an operation for selecting a specific message has been input, the user screen providing unit 40 provides detailed information on the selected message (user nickname, driver nickname, (Subject, text) may be transmitted to the user terminal 12 for display.

  When the matching information registration unit 44 receives from the user terminal 12 a matching request including the application information input on the application page, the matching information registration unit 44 assigns a unique matching ID. The matching information registration unit 44 associates the matching ID, the user ID of the application source user, the driver ID of the application destination driver, the status (initial value “unapproved”), and the application information, and the matching information holding unit 30. To store.

  The driver screen providing unit 46 includes an element for allowing a specific driver's terminal (driver terminal 14a or the like) selected on the user page to input whether to approve a request for driving a rental car. A page (hereinafter referred to as “driver page”) is provided and displayed. This element is an object (also referred to as content) that is set on the driver page or displayed / operated on the driver page. Examples include text fields, buttons, and forms.

  The driver page includes a matching confirmation page and a message confirmation page. The driver screen providing unit 46 receives information related to the operation input by the driver with respect to the driver page from the driver terminal 14, and transmits a matching confirmation page or a message confirmation page to the driver terminal 14 according to the operation. May be displayed. Further, the driver page includes the data of the matching confirmation page or the message confirmation page, and the web browser of the driver terminal 14 displays the contents of these included pages according to the driver's operation on the driver page. You may switch from a non-display state to a display state.

  The matching confirmation page is a web page that displays a list of one or more matching information applied to the driver. The matching information displayed on the matching confirmation page includes the rental car attribute information that the user has reserved with the rental car company. The driver screen providing unit 46 searches the matching information holding unit 30 for one or more matching information (for example, application information and status) associated with the driver ID, and is associated with the driver ID. Then, a matching confirmation page showing one or more pieces of matching information is generated, and the data is transmitted to the user terminal 12.

  Further, the driver screen providing unit 46 sets an element for allowing the driver to select approval or non-approval in an area of matching information whose status is not approved on the matching confirmation page. On the other hand, an element for sending a message from the driver to the user of the matching partner is set in the area of the matching information whose status is approved.

  The message confirmation page is a web page that displays a list of messages sent from the user to the driver (so-called inbox) and a list of messages sent from the driver to the user (so-called outbox). . The driver screen providing unit 46 reads out message data associated with the driver (driver ID) from the message holding unit 32, and transmits the read message data to the driver terminal 14 to display a list. When the driver screen providing unit 46 is notified from the driver terminal 14 that an operation for selecting a specific message has been input, the driver screen providing unit 46 provides detailed information on the selected message (user nickname, driver nickname, (Subject, text) may be transmitted to the driver terminal 14 for display.

  When an operation indicating approval or non-approval for a specific matching is input on the driver terminal 14, the matching information registration unit 44 acquires information indicating this (referred to as “approval information”) from the driver terminal 14. To do. The approval information includes a matching ID of a matching that has been approved or not approved. The matching information registration unit 44 updates the status of the matching information identified by the matching ID held in the matching information holding unit 30 to approved if it is approved, and if it is not approved, the status Update to unapproved.

  The charging unit 48 executes a predetermined charging process for at least one of the driver and the user. In the embodiment, the charging unit 48 charges a predetermined amount to a driver newly registered with the travel support site. For example, the billing unit 48 allows the driver to input credit card information necessary for payment of money to the travel support site operator on the driver registration screen for the travel support site, and cooperates with the credit card company device. A credit card settlement for paying a predetermined amount from the driver to the operator may be executed.

  Further, when the matching application from the user is approved on the driver page, the charging unit 48 refers to the approval information to detect that and charges the user a predetermined amount. For example, when the matching application is approved, the charging unit 48 reads the credit card information of the application source user held in the user information holding unit 28 in advance, and cooperates with the credit card company device to provide travel support from the user. You may perform the credit card payment which pays a predetermined amount to the site operator. As a modification, when a matching application from a user is approved on the driver page, a predetermined amount may be charged to the approved driver instead of the user or together with the user.

  The message registration unit 50 receives message data addressed to the driver transmitted from the user terminal 12. The message data of the present embodiment is associated with any matching and includes a specific matching ID. The message registration unit 50 assigns a unique message ID, and stores the message ID, the transmission source user ID, the transmission destination driver ID, the matching ID, the subject, and the text in the message holding unit 32 in association with each other. . Further, when the message registration unit 50 receives the message data addressed to the user transmitted from the driver terminal 14, the message registration unit 50 associates the message ID, the driver ID of the transmission source, the user ID of the transmission destination, the subject, and the text. The message is stored in the message holding unit 32. Note that the user ID and the driver ID may be included in the message data transmitted from the user terminal 12 or the driver terminal 14, or may be identified by the message registration unit 50 based on the matching ID.

  When the schedule update unit 52 receives the schedule update request transmitted from the driver terminal 14, the schedule update unit 52 updates the driver's schedule information held in the driver information holding unit 26 according to the schedule update request. For example, the schedule update unit 52 reflects the driver's vacant date (period) indicated by the schedule update request in the driver's schedule information held in the driver information holding unit 26. In addition, when the schedule update unit 52 receives the approval information indicating that the matching application has been approved, the schedule update unit 52 sets the matching application so that the period from the start date to the end date indicated by the matching application is set to the reserved date (period). Update the approved driver's schedule information.

  FIG. 3 is a block diagram showing a functional configuration of the user terminal 12 of FIG. The user terminal 12 includes a control unit 60, a storage unit 62, a communication unit 64, an operation input unit 66, and a display 68. The control unit 60 executes various data processes in the user terminal 12. The storage unit 62 is a storage area that stores data that is referred to or updated by the control unit 60. The communication unit 64 communicates with an external device according to a predetermined communication protocol. The control unit 60 exchanges data with the travel support server 16 and the rental car company server 17 via the communication unit 64. The operation input unit 66 is a member to which an operation by a user is input, and is, for example, a keyboard. The operation input unit 66 and the display 68 may be integrated like a touch panel.

  The control unit 60 includes a user screen display unit 70, a search request unit 72, a matching application unit 74, a matching information request unit 76, and a message transmission unit 78. The functions indicated by these blocks are based on the data of the user page 12 (for example, HTML document or Javascript (registered trademark)) transmitted from the travel support server 16 by the web browser 79 installed in advance in the user terminal 12. You may implement | achieve by performing a process.

  The user screen display unit 70 causes the display 68 to display a user page, which is a screen including elements for allowing the user to select a driver who requests driving a rental car from a plurality of drivers registered in advance. The search request unit 72 transmits search conditions (such as driver attributes and ranges thereof) designated on the user page (search page) to the travel support server 16. The user screen display unit 70 displays the search result (driver information satisfying the search condition) provided from the travel support server 16 as a response to the search request by the search request unit 72 on the user page.

  When the driver is selected on the user page, the matching application unit 74 notifies the travel support server 16 of that fact, thereby driving the driver selected on the user page via the travel support server 16. A driver page for inputting whether or not to approve a request for driving a rental car is displayed on the driver terminal 14. Specifically, the matching application unit 74, when application information requesting a specific driver to drive a rental car is input, the application user ID, application driver ID, and application information Is sent to the travel support server 16. As described above, the application information is displayed on the driver page of the driver terminal 14 via the travel support server 16. In addition, the application information includes attribute information of a rental car that the user has already arranged with the rental car company.

  The matching information request unit 76 transmits data requesting to provide matching information (application information, status, etc.) associated with the user to the travel support server 16. The user screen display unit 70 causes the display 68 to display a list of one or more pieces of matching information provided from the travel support server 16 as a response to the request from the matching information request unit 76. The user screen display unit 70 displays an element for transmitting a message to the driver in an area where matching information whose status is approved is displayed.

  The message transmitting unit 78 transmits message data addressed to the driver input on the user page to the travel support server 16. The user screen display unit 70 transmits data requesting to provide a message addressed to the user associated with the user to the travel support server 16. The user screen display unit 70 causes the display 68 to display message data (driver nickname, subject, text, etc.) transmitted from the travel support server 16.

  FIG. 4 is a block diagram showing a functional configuration of the driver terminal 14 of FIG. The driver terminal 14 includes a control unit 80, a storage unit 82, a communication unit 84, an operation input unit 86, and a display 88. The control unit 80 executes various data processes in the driver terminal 14. The storage unit 82 is a storage area that stores data that is referred to or updated by the control unit 80. The communication unit 84 communicates with an external device according to a predetermined communication protocol. The control unit 80 exchanges data with the travel support server 16 via the communication unit 84. The operation input unit 86 is a member to which an operation by the driver is input, for example, a keyboard. The operation input unit 86 and the display 88 may be integrated like a touch panel.

  The control unit 80 includes a driver screen display unit 90, a matching information request unit 92, an approval result transmission unit 94, a message transmission unit 96, and a schedule update request unit 98. The functions shown by these blocks are based on the data of a driver page (for example, an HTML document or a Javascript (registered trademark) program) transmitted from the travel support server 16 by the web browser 99 installed in the driver terminal 14 in advance. You may implement | achieve by performing a process.

  The driver screen display unit 90 displays on the display 88 a driver page that is a screen including an element for allowing the driver to input whether or not to approve the request for driving the rental car applied by the user. The matching information request unit 92 transmits data requesting to provide matching information (application information, status, etc.) associated with the driver to the travel support server 16.

  The driver screen display unit 90 displays a list of one or more pieces of matching information provided from the travel support server 16 as a response to the request from the matching information request unit 92. Each of the one or more pieces of matching information includes attribute information of a rental car that the user has already arranged with the rental car company. The driver screen display unit 90 displays an element for inputting approval or non-approval in an area where matching information whose status is not approved is displayed. On the other hand, an element for sending a message to the user is displayed in the area for displaying matching information whose status is approved.

  The approval result transmission unit 94 transmits to the travel support server 16 approval information, which is information indicating whether the driver has approved matching information (application information) whose status is not approved. The message transmission unit 96 transmits data of a message addressed to the user input on the driver page to the travel support server 16. The driver screen display unit 90 transmits data requesting to provide a message addressed to the driver associated with the driver to the travel support server 16. The driver screen display unit 90 displays message data (user nickname, subject, text, etc.) transmitted from the travel support server 16 on the display 88.

  When the driver's schedule information is input to the driver page, the schedule update request unit 98 transmits and registers the input schedule information to the travel support server 16. As described above, the schedule information includes an available date and time (period) that can be reserved by the user and a reserved date and time (period) that cannot be reserved by the user.

  The operation of the information system 10 having the above configuration will be described. Here, it is assumed that the user and the driver have already been registered in the travel support server 16. That is, various user attribute information is held in the user information holding unit 28, and various driver attribute information is held in the driver information holding unit 26. Further, the user accesses the rental car company server 17 via the user terminal 12 and has reserved a rental car. Of course, it is possible to reserve a rental car by another method such as calling a rental car company.

  FIG. 5 is a flowchart showing the operation of the travel support server 16. The figure shows the operation of the travel support server 16 for the user terminal 12 operated by a single user. The travel support server 16 performs similar processing on a plurality of user terminals 12 (for example, the user terminal 12a, the user terminal 12b, and the user terminal 12c) of a plurality of users.

  The user activates the web browser 79 on the user terminal 12, accesses the travel support site (for the user), and tries to log in. When the authentication unit 38 of the travel support server 16 authenticates the user and the authentication is successful (Y in S10), the user screen providing unit 40 of the travel support server 16 provides the user page 12 to the user terminal 12 ( S12). The user screen display unit 70 of the user terminal 12 displays the user page on the display 68. If the user authentication fails (N in S10), S12 is skipped.

  When the user inputs a desired search condition to the user page and presses the search button, the search request unit 72 of the user terminal 12 transmits a search request including the search condition to the travel support server 16. When the driver search unit 42 of the travel support server 16 receives the search request (Y in S14), the driver search unit 42 searches the driver information holding unit 26 to select a driver that matches the search condition from the registered drivers. The detected driver information is provided to the user terminal 12 (S16). The user screen display unit 70 of the user terminal 12 causes the display 68 to display the search result provided from the travel support server 16, that is, the driver information that matches the search condition. If no search request has been received (N in S14), S16 is skipped.

  When the user inputs an operation to instruct display of detailed information of a specific driver on the user page displaying the search result, the user screen display unit 70 provides the driver detailed information to the travel support server. Request to 16. When the driver search unit 42 of the travel support server 16 receives the request for providing the driver detailed information (Y in S18), the driver search unit 42 acquires the profile information of the driver specified in the request from the driver information holding unit 26. This is provided to the user terminal 12 (S20). The user screen display unit 70 of the user terminal 12 displays the driver's profile information on the user page. If the request for providing the detailed driver information has not been received (N in S18), S20 is skipped.

  When the user confirms the driver's profile information and decides to entrust the driver with the rental car, he / she inputs a predetermined operation for displaying the application page (also referred to as an application form) to the user page. . The user page of the embodiment includes application page data, and the user screen display unit 70 of the user terminal 12 displays the user page when a predetermined operation is input to the user page. Display the application page in part. As described above, the user screen providing unit 40 of the travel support server 16 may provide the application page data to the user terminal 12 and display the data separately from the previous user page.

  FIG. 6 shows an example of the application page 100. The application page 100 includes a rental car information input area 102. The rental car information input area 102 is an area where the user inputs various attribute information related to the rental car reserved in advance with the rental car company. In the present embodiment, a company name and a store name of a rental car company, a rental car type or class, and an input field for smoking presence / absence are included. The “Rental vehicle type or class” column in this column is the vehicle type (classification of vehicle structure / size, such as a normal car or medium-sized car), or a class (car type / size, displacement, etc.) determined in advance by the rental car company. , And the like, for example, “S”, “A”, etc.) are text fields to be input. The class may differ for each rental car company, but the meaning can be uniquely specified by the combination of the rental car company and the class. In addition, a car name may be entered in the “rental car type or class” field.

  The application page 100 further includes an input area for a desired meeting place. The user sets a place where he / she wants to meet the driver at the travel destination as the input area. When the input to each item on the application page 100 is completed, the user inputs a pressing operation on the application button 104. In addition, in the application page 100, a user ID as an application source and a driver ID as an application destination on which profile information is displayed are set as hidden information.

  Returning to FIG. 5, when the application button 104 is pressed on the application page 100, the matching application unit 74 of the user terminal 12 includes a user ID, a driver ID, and a matching request including application information input on the application page 100. Is transmitted to the travel support server 16. When the matching request is received (Y in S22), the matching information registration unit 44 of the travel support server 16 adds the matching ID and status (initial value “0”) to the user ID, driver ID, and application information indicated by the matching request. Matching information associated with “unapproved”) is stored in the matching information holding unit 30 (S24). If no matching request has been received (N in S22), S24 is skipped.

  The user inputs a predetermined operation for displaying a matching confirmation page for confirming whether the matching is correct or not to the user page. The matching information request unit 76 of the user terminal 12 requests the travel support server 16 to provide matching information requested by the user. When the request for providing matching information is received (Y in S26), the user screen providing unit 40 of the travel support server 16 searches the matching information holding unit 30 for matching information associated with the requesting user ID. To do. If there is matching information associated with the requesting user ID (Y in S28), the user screen providing unit 40 generates a matching confirmation page including the detected matching information, and at that time, for each matching information Determine the status.

  The user screen providing unit 40 adds an element for message transmission to the matching information whose status is approved (Y in S30) (S32), but the matching information whose status is unapproved or unapproved ( N) in S30, no element for message transmission is added. If status determination for at least a part of the detected matching information is incomplete (N in S34), the process returns to S30. When the status determination of all the detected matching information is completed (Y in S34), a matching confirmation page showing the detected matching information side by side is provided to the user terminal 12 (S36). If no matching information provision request has been received (N in S26), or if there is no matching information associated with the user ID of the requesting user (N in S28), S30 to S36 are skipped. .

  The user screen display unit 70 of the user terminal 12 displays a matching confirmation page on the display 68. 7 and 8 show examples of the matching confirmation page 106. FIG. FIG. 7 shows a matching confirmation page 106 showing matching information whose status is unapproved. On the other hand, FIG. 8 shows a matching confirmation page 106 showing matching information whose status is already approved. The matching confirmation page 106 of FIG. 8 is provided with a message creation button 108. When the user inputs a pressing operation on the message creation button 108, a message creation area 110 is expanded and displayed.

  The message creation area 110 includes a message subject and text input area, and a message transmission button 112. When the user inputs a message addressed to the driver “Jiro” and presses the message transmission button 112, the message transmission unit 78 of the user terminal 12 inputs the user ID, the ID of the driver “Jiro”, and the message. The message data including the ID, subject, and text of the matching information is transmitted to the travel support server 16.

  Although not shown, a matching confirmation page 106 showing matching information whose status is not approved is the same as that shown in FIG. That is, in the matching confirmation page 106 showing matching information whose status is unapproved or unapproved, elements for transmitting a message to the driver are not set and are not displayed.

  Returning to FIG. 5, when the message registration unit 50 of the travel support server 16 receives the message data from the user terminal 12 (Y in S38), the message registration unit 50 stores the received message data in the message holding unit 32 (S40). If no message data has been received (N in S38), S40 is skipped.

  The user inputs a predetermined operation for instructing browsing of the message on the user page. The user screen display unit 70 of the user terminal 12 transmits a message browsing request to the travel support server 16. When the user screen providing unit 40 of the travel support server 16 receives the message browsing request (Y in S42), the message associated with the requesting user ID from among the messages stored in the message holding unit 32. Is read. For example, a message with the requesting user as the transmission destination and a message with the requesting user as the transmission source are read. Then, the read message is transmitted to the user terminal 12 (S44). If no message browsing request has been received (N in S42), S44 is skipped. The user screen display unit 70 of the user terminal 12 displays the message transmitted from the travel support server 16 on the user page.

  FIG. 9 is a flowchart showing the operation of the travel support server 16. The figure shows the operation of the travel support server 16 for the driver terminal 14 operated by a single driver. The travel support server 16 performs similar processing on a plurality of driver terminals 14 (for example, the driver terminal 14a, the driver terminal 14b, and the driver terminal 14c) of a plurality of drivers.

  The driver starts the web browser 99 on the driver terminal 14, accesses the travel support site (for the driver), and tries to log in. When the authentication unit 38 of the travel support server 16 authenticates the driver and the authentication is successful (Y in S50), the driver screen providing unit 46 of the travel support server 16 provides the driver page 14 to the driver terminal 14 ( S52). The driver screen display unit 90 of the driver terminal 14 displays a driver page on the display 88. If the driver authentication fails (N in S50), S52 is skipped.

  When the driver inputs his / her schedule (vacant date / time, vacant period, etc.) on the driver page, the schedule update request unit 98 of the driver terminal 14 transmits a schedule update request indicating the input schedule to the travel support server 16. To do. When a schedule update request is received (Y in S54), the schedule update unit 52 of the travel support server 16 updates the driver's schedule information according to the schedule update request (S56). If a schedule update request has not been received (N in S54), S56 is skipped.

  The driver inputs a predetermined operation for displaying a matching confirmation page for confirming whether there is a matching application addressed to the driver to the driver page. The matching information request unit 92 of the driver terminal 14 requests the travel support server 16 to provide matching information applied to the driver. When the request for providing matching information is received (Y in S58), the driver screen providing unit 46 of the travel support server 16 searches the matching information holding unit 30 for matching information associated with the requesting driver ID. To do. If there is matching information associated with the driver ID of the request source (Y in S60), the driver screen providing unit 46 generates a matching confirmation page including the detected matching information, and at that time, for each matching information Determine the status.

  The driver screen providing unit 46 adds an element for message transmission to the matching information whose status is already approved (Y of S62) (S64), but the matching information whose status is unapproved or unapproved ( N) in S62, no element for message transmission is added. Although not shown, the driver screen providing unit 46 adds an element for allowing the driver to input approval or non-approval to the matching information whose status is not approved, but the matching information whose status is approved or non-approved Does not add this element.

  If the status determination for at least a part of the detected matching information is incomplete (N in S66), the process returns to S62. When the status determination for all the detected matching information is completed (Y in S66), a matching confirmation page showing the detected matching information side by side is provided to the driver terminal 14 (S68). If no matching information provision request has been received (N in S58), or if there is no matching information associated with the requesting driver ID (N in S60), S62 to S68 are skipped.

  The driver screen display unit 90 of the driver terminal 14 displays a matching confirmation page on the display 88. 10 and 11 show examples of the matching confirmation page 120. FIG. FIG. 10 shows a matching confirmation page 120 showing matching information whose status is unapproved. On the other hand, FIG. 11 shows a matching confirmation page 120 showing matching information whose status is already approved. The matching confirmation page 120 includes an area indicating application information from the user, and includes a rental car information area 122 indicating attribute information of a rental car reserved by the user for the rental car company. The matching confirmation page 120 showing matching information whose status is unapproved is the same as that shown in FIG.

  As shown in FIG. 10, an approval button 124 and a non-approval button 126 are provided in an area indicating matching information whose status is unapproved. The driver confirms the application information on the matching confirmation page 120 and presses the approval button 124 when accepting driving of the rental car, and presses the non-approval button 126 when not accepting driving of the rental car. The approval result transmission unit 94 of the driver terminal 14 transmits approval information indicating approval or non-approval for specific matching information (matching ID) to the travel support server 16.

  As shown in FIG. 11, a message creation button 108 is provided in an area indicating matching information whose status is already approved. When the driver inputs a pressing operation on the message creation button 108, the message creation area 110 is expanded and displayed. The message creation area 110 includes a message subject and text input area, and a message transmission button 112. When the user inputs a message addressed to the user “Taro” and presses the message transmission button 112, the message transmission unit 96 of the driver terminal 14 inputs the ID of the user “Taro”, the ID of the driver, and the message. The message data including the ID, subject, and text of the matching information is transmitted to the travel support server 16.

  Returning to FIG. 9, when the approval information is received from the driver terminal 14 (Y in S70) and the approval information indicates the approval of the application (Y in S72), the charging unit 48 of the travel support server 16 Charge processing for the user is executed (S74). Further, the schedule update unit 52 of the travel support server 16 updates the schedule information of the approved driver with the period from the start date to the end date indicated by the approved application information as a reserved period (S76). When the approval information indicates non-approval of the application (N in S72), S74 and S76 are skipped. The matching information registration unit 44 of the travel support server 16 updates the status of the matching information that has been approved or not approved (S78). If the approval result is not received (N in S70), S72 to S78 are skipped.

  When the message registration unit 50 of the travel support server 16 receives message data from the driver terminal 14 (Y in S80), the message registration unit 50 stores the received message data in the message holding unit 32 (S82). If no message data has been received (N in S80), S82 is skipped.

  The driver inputs a predetermined operation for instructing browsing of the message on the driver page. The driver screen display unit 90 of the driver terminal 14 transmits a message browsing request to the travel support server 16. When the driver screen providing unit 46 of the travel support server 16 receives the message browsing request (Y in S84), the message associated with the driver ID of the request source from the messages stored in the message holding unit 32. Is read. For example, a message having the requesting driver as the transmission destination and a message having the requesting driver as the transmission source are read. Then, the read message is transmitted to the driver terminal 14 (S86). If no message browsing request has been received (N in S84), S86 is skipped. The driver screen display unit 90 of the driver terminal 14 displays the message transmitted from the travel support server 16 on the driver page.

  As described above, the travel support server 16 according to the present embodiment provides a matching service for assisting the user in searching for a driver who entrusts driving a rental car at the destination. With this matching service, a driver who is familiar with the geography and road conditions of the user's travel destination and who meets the user's preference and purpose of the travel will guide the user. The degree can be increased. Even a user who does not have a driver's license or a user who is not confident in driving can enjoy a special trip as if he / she has a driver. In addition, users can enjoy interacting with the local residents of the travel destination, and can easily visit places recommended by local residents that have not been converted into tourist spots. In addition, it is possible to provide the driver with an opportunity to earn income by driving on a familiar road or place.

  In addition, in order to improve matching consistency, the matching service of this embodiment includes the rental car attribute information reserved in advance by the user in the application information from the user to the driver. As a result, the driver can check the rental car attribute information and determine whether to approve it. For example, when the car type or class of the rental car is similar to the car type or class that the driver can get on, the driver can approve the user's application. Further, in the matching service of the present embodiment, the desired meeting place is included in the application information from the user to the driver. Thereby, the risk that the user cannot meet the driver on the road can be reduced.

  Moreover, according to the travel support server 16 of the present embodiment, a business model based on the matching service can be realized. Specifically, a driver who can be matched with many users can be urged to positively approve an application by charging at the time of registration on the travel support site. On the other hand, users who are assumed to be using intermittently can be encouraged to use the travel support site easily by charging when matching is established (at the time of approval). Thus, according to the travel support server 16 of the present embodiment, the operator of the travel support site can also increase profits while suppressing an increase in the sense of cost burden on the user and the driver.

  In addition, the travel support server 16 according to the present embodiment provides a mechanism for exchanging messages between the user and the driver, and can make up for information lacking when matching is established by exchanging messages. However, if message exchange is allowed before matching is established (before approval), the business model is impaired because the user and the driver can communicate with each other without matching, that is, before the user is charged. It might be. Therefore, the travel support server 16 according to the present embodiment enables messages to be exchanged between the user and the driver on condition that matching is established. Thereby, the convenience of a user and a driver | operator, and a business model can be reconciled.

(Second embodiment)
The configuration of the information system 10 of the second embodiment is the same as that of the first embodiment (FIG. 1). The travel support server 16 of the second embodiment enhances the convenience for the user by linking information with the rental car company server 17. It is assumed that the rental car company server 17 is provided with an API (Application Programming Interface) for providing information to the travel support server 16 and an API for receiving information transmitted from the travel support server 16.

  FIG. 12 is a block diagram illustrating a functional configuration of the travel support server 16 according to the second embodiment. In the figure, the same or corresponding blocks as those of the first embodiment are denoted by the same reference numerals as those of the first embodiment (FIG. 2). Hereinafter, differences from the first embodiment will be described.

  The travel support server 16 further includes an information cooperation unit 54 that transmits and receives data to and from the rental car company server 17 by calling an API provided in the rental car company server 17. The information linkage unit 54 includes a rental car information acquisition unit 56 and a driver information provision unit 58.

  The rental car information acquisition unit 56 acquires the rental car attribute information reserved by the user, for example, information to be input to the rental car information input area 102 of FIG. For example, when the user screen providing unit 40 provides the application page to the user terminal 12, the rental car information acquiring unit 56 uses the user identification information (name and e-mail address) predetermined with the rental car company. Or the like) as a key, the rental car reservation status may be inquired to the rental car company server 17. As a response to this inquiry, the rental car information acquisition unit 56 may acquire the rental car attribute information associated with the user identification information from the rental car company server 17.

  The user screen providing unit 40 automatically sets the attribute information of the rental car acquired by the rental car information acquisition unit 56 on the user page. For example, the user screen providing unit 40 sets rental car attribute information in each input field of the rental car information input area 102 in FIG. 6, and sets the user page (application page) in which the rental car attribute information has been set as the user terminal. 12 to display. Thereby, the amount of data to be manually input by the user for the matching application can be reduced, and the convenience for the user can be improved.

  A link to the travel support site provided by the travel support server 16 may be provided on the reservation completion screen of the rental car reservation site provided by the rental car company server 17. When the link is selected, the rental car company server 17 may redirect to the travel support site and pass the rental car reservation identification information (reservation ID in the rental car company server 17) by the user to the travel support server 16. The rental car information acquisition unit 56 of the travel support server 16 may store the reservation ID provided from the rental car company server 17 in the user information holding unit 28 as user attribute information. The rental car information acquisition unit 56 may use the reservation ID as a key when accessing the rental car company server 17. Note that the rental car attribute information may be acquired at any timing as long as it is before the matching application.

  The driver information providing unit 58 provides the attribute information of the approved driver to the rental car company server 17 when the matching application is approved on the driver page. Specifically, the driver information providing unit 58 is predetermined with the rental car company for the user who is the application source when the approval information indicating that the application is approved is received from the driver terminal 14. The user identification information (name, e-mail address, or the above reservation ID) may be acquired from the user information holding unit 28. In addition, for the driver who is the application destination, the license information (license number, license image, etc.) held in the driver information holding unit 26 is acquired.

  The driver information providing unit 58 registers the driver's license information in the rental car company server 17 using the user identification information as a key. The rental car company server 17 stores the license information of the driver who actually drives the rental car in association with the user who made the rental car reservation. This can simplify the user's procedure when renting a rental car at a travel destination. That is, by notifying the rental car company of the driver's license information in advance, it is not necessary to copy the license at the destination store. Not only the license information but also the information necessary for borrowing a rental car among the attribute information of the driver held in the driver information holding unit 26 can be provided in advance to the rental car company by the above mechanism.

(Third embodiment)
The third embodiment proposes a mechanism that enables a matching application without specifying a driver when a driver that satisfies the conditions specified by the user is not found in the search. In other words, instead of designating the driver in advance on the user side, the application contents of the user are presented to a plurality of drivers, and a mechanism in which one of the drivers can take over the rental car is proposed. The configuration of the information system 10 and the travel support server 16 of the third embodiment is the same as that of the first embodiment (FIGS. 1 and 2). Hereinafter, differences from the first embodiment will be described.

  When the search result by the driver search unit 42 is a predetermined result (the number of hits is 0 in the embodiment), the user screen providing unit 40 requests to drive a rental car without designating a specific driver. The user page including the element is transmitted to the user terminal 12 and displayed. When a matching application that indicates a request for driving a rental car and that does not specify a driver (hereinafter referred to as “special application”) is received from the user terminal 12, the driver screen providing unit 46 A driver page including an element for inputting whether or not to approve the application is displayed on a plurality of predetermined terminals of the driver. When the special application is approved on the driver page, the user screen providing unit 40 transmits information on the driver who approved the special application to the user terminal 12 for display.

  In the third embodiment, information as to whether or not to accept a special application is registered in advance as attribute information of the driver, and the travel support server 16 distributes the special application only to the driver for which the attribute for accepting the special application is set. To do. As a modification, the special application may be distributed to all the drivers registered in the travel support server 16.

  FIG. 13 is a flowchart showing the operation of the travel support server 16 of the third embodiment. This figure shows processing relating to special application additionally executed in addition to the processing of the first embodiment (FIGS. 5 and 9). When the search request including the search condition designated by the user is received from the driver terminal 14 (Y in S90), the driver search unit 42 searches the driver information holding unit 26 for a driver that matches the search request. . If the number of search hits is 0 (Y in S92), the user screen providing unit 40 adds a special application form to the data of the user page (search page) indicating the search result (S94). The special application form in the embodiment may be the same as the normal matching application form shown in FIG.

  The user screen providing unit 40 transmits a user page indicating the search result to the user terminal 12 for display (S96). For example, if the number of search hits is 0, the user terminal 12 displays the search result, a message prompting the user to change the search condition, and a user page including a special application form as an alternative means for changing the search condition. If the number of search hits is not 0 (N in S92), S94 is skipped. In this case, the normal process shown in the first embodiment is performed, and the process of S18 in FIG. 5 continues. If no search request has been received (N in S90), S92 to S96 are skipped.

  The user can check the search result and change the search condition, but here, the request contents of the rental car are entered in the special application form. In addition to the contents shown in FIG. 6, the special application form further includes an input area for items (for example, hourly unit price (reward amount), supported language, qualification, etc.) that can be specified as a search condition on the search page. May be. The matching application unit 74 of the user terminal 12 transmits special application data that does not designate a specific driver to the travel support server 16. The data of the special application does not include the driver ID, and includes identification information indicating the special application so that it can be distinguished from the normal matching application.

  When receiving the special application from the user terminal 12 (Y in S98), the matching information registration unit 44 of the travel support server 16 stores the contents of the special application in the matching information holding unit 30 as new matching information (S100). At this point in time, the driver ID is not set, so the driver ID is not set. The driver screen providing unit 46 distributes the special application to the plurality of driver terminals 14 (S102). If the special application has not been received (N in S98), S100 and S102 are skipped.

  In the embodiment, the driver screen providing unit 46 displays the matching information based on the special application only in the driver terminal 14 of the driver in which attributes that can accept the special application among the plurality of driver terminals 14 are registered in advance. Provide a user page. For example, when a request for providing matching information is received from a certain driver terminal 14, if the attribute that allows the driver to accept the special application is set, the matching information and the special application of the normal application (first embodiment) are set. Providing a driver page that includes both matching information. On the other hand, if the attribute that can accept the special application is not set for the driver, the driver page including only the matching information of the normal application (first embodiment) is provided.

  As a modification, when the travel support server 16 receives a special application, the travel support server 16 pushes the matching information itself based on the special application or the URL of the driver page indicating the matching information based on the special application to the plurality of driver terminals 14. You may further provide the special application delivery part which delivers (or mail delivery).

When any driver approves the special application at the driver terminal 14, the approval result transmission unit 94 of the driver terminal 14 transmits approval information indicating approval of the special application to the travel support server 16.
When the approval information indicating the approval of the special application is received (Y in S104), the matching information registration unit 44 of the travel support server 16 updates the matching information based on the special application stored in the matching information holding unit 30 ( S106). Specifically, the status of the matching information is updated to “approved”, and the ID of the driver who approved the special application is set in the matching information. Thereafter, special applications can be handled in the same way as normal applications.

  In the present embodiment, the driver screen providing unit 46 of the travel support server 16 uses a user page including information on the driver who has approved the special application (for example, various profiles held in the driver information holding unit 26). It is provided to the terminal 12 and displayed. In this user page, a message that prompts the user to make a normal matching application for the driver who has approved the special application is set. The user executes a matching application that explicitly specifies the driver who approved the special application, and thereafter the flow of the first embodiment (the flow after S22 in FIG. 5) is executed. In addition, the user may be allowed to provide the user terminal 12 with the status of the special application and the driver information from the travel support server 16 by voluntarily displaying the matching confirmation page. If approval information indicating approval of the special application has not been received (N in S104), S106 and S108 are skipped.

  The driver may want to accept a driving request for a rental car even if conditions such as rewards are lowered. According to the configuration of the third embodiment, even when the search condition specified by the user does not match the predetermined driver attribute, it becomes easy to find the driver who approves the condition specified by the user. And the probability of the driver's matching being established. The user can be provided with the merit of being able to request driving a rental car under the conditions specified by the user. In addition, the driver can be provided with the advantage that opportunities for obtaining rewards are expanded. In the above embodiment, the process related to the special application is executed when the number of hits for the driver search is 0. However, when the hit number for the driver search is equal to or less than a predetermined threshold (for example, 1 or less). You may perform the process regarding a special application.

  The present invention has been described based on the first to third embodiments. These embodiments are exemplifications, and it is understood by those skilled in the art that various modifications can be made to the combination of each component and each processing process, and such modifications are within the scope of the present invention. is there.

  A modification will be described. The travel support server 16 may further include a management screen providing unit. The management screen providing unit provides and displays a management page, which is a web page including information for managing the usage status of the matching service, on the terminal of the administrator of the travel support server 16 (in other words, the operator of the travel support site). Let

  Specifically, the management screen providing unit may set a list of matching information held in the matching information holding unit 30 and detailed contents in the management page. The matching information set in the management page includes any matching information whose status is “unapproved”, “approved”, or “non-approved”. The management screen providing unit may provide an input area for filtering conditions on the management page. When a specific status is specified by the administrator as a filtering condition, the management screen providing unit may set only matching information that matches the specific status in the management page.

  In addition, the management screen providing unit, when an operation for selecting specific matching information with respect to the management page is input on the administrator terminal, includes one or more associated with the selected matching information (matching ID) In other words, one or more messages exchanged between the user who is the target of the selected matching and the driver may be read from the message holding unit 32. Then, a management page in which one or more read messages are arranged in time series may be provided to the administrator terminal for display. According to this modification, management of the usage status of the matching service can be supported, and for example, support for troubles occurring between the user and the driver can be supported.

  Another modification will be described. The accounting unit 48 of the travel support server 16 may execute a process of charging a predetermined amount to the rental car company when information linkage occurs between the travel support server 16 and the rental car company server 17. For example, the billing unit 48 may redirect the rental car information acquisition unit 56 or the driver information providing unit 58 described in the second embodiment to the rental car company server 17 or redirect the rental car company site to the travel support site. If this occurs, billing processing for the rental car company may be executed. The matching service of the travel support server 16 is based on the premise that the user reserves a rental car and contributes to sales of the rental car company. According to this modification, it is possible to realize a business model that returns a part of sales of the rental car company to the operator of the travel support site.

  Still another modification will be described. The travel support server 16 causes the driver to register the information on the area where the rental car can be undertaken (information specifying the region, prefecture, municipality, etc.) as the driver attribute information, and the driver information holding unit 26 holds the information. May be. The user screen providing unit 40 of the travel support server 16 may set an input area of a region (typically a travel destination) entrusted with driving a rental car in the user page, and allow the user to input the region. . When the area where the rental car driving is entrusted is specified, the user screen providing unit 40 may display the driver information corresponding to the area specified by the user on the user page as a selectable driver. . In addition, the driver search unit 42 of the travel support server 16 may set the driver corresponding to the area specified by the user as a search population, in other words, the area specified by the user as the search condition. It may be added.

  Any combination of the above-described examples and modifications is also useful as an embodiment of the present invention. The new embodiment produced by the combination has the effects of the combined example and modification. Further, it should be understood by those skilled in the art that the functions to be fulfilled by the constituent elements described in the claims can be realized by the individual constituent elements shown in the embodiments and the modified examples or by their cooperation.

  10 information system, 12 user terminal, 14 driver terminal, 16 travel support server, 17 rental car company server, 40 user screen providing part, 46 driver screen providing part, 48 billing part, 56 rental car information obtaining part, 58 driving Person information providing part, 70 User screen display part.

Claims (8)

A user screen providing unit that displays on the user's terminal a user screen including an element for causing the user to select a driver who requests driving of the rental car from a plurality of drivers registered in advance;
A driver screen providing unit for displaying a driver screen including an element for inputting whether or not to approve a request for driving a rental car on the driver's terminal selected on the user screen;
With
The user screen includes an area that allows the user to input the rental car attribute information reserved by the user with respect to the rental car company,
The driver screen providing unit displays the rental car attribute information input on the user screen on the driver screen,
When the request is approved on the driver screen, the user screen providing unit displays information indicating the request on the user screen.   The information processing apparatus according to claim 1, wherein the rental car attribute information input to the user screen includes information indicating a rental car type or a rental car class predetermined by a rental car company. A charging unit that executes a charging process for at least one of the user and the driver when the request is approved on the driver screen;
When the request is approved on the driver screen, the user screen providing unit displays an element for sending a message from the user to the driver on the user screen,
The said driver screen provision part displays the element for sending a message from a driver to a user on the said driver screen, when a request is approved on the said driver screen. Information processing device. It further includes a rental car information acquisition unit that acquires attribute information of a rental car reserved by the user from an external device that holds information related to the rental car reservation,
The information processing apparatus according to claim 1, wherein the user screen providing unit automatically sets the attribute information of the rental car acquired by the rental car information acquisition unit on the user screen.   2. A driver information providing unit that provides driver attribute information to an external device that holds information related to a rental car reservation when a request is approved on the driver screen. 5. The information processing apparatus according to any one of 4. It further includes a search unit that searches for a driver that meets the conditions specified by the user,
When the search result by the search unit is a predetermined result, the user screen providing unit displays a user screen including an element for requesting a rental car without specifying a driver. Display it on your device,
When a request for driving a rental car is received from the terminal of the user by the driver, the driver screen providing unit determines whether to approve the special request. Display driver screens containing elements for input on multiple driver terminals,
The user screen providing unit displays information of a driver who has approved the special request on the terminal of the user when the special request is approved on the driver screen. To 5. The information processing apparatus according to any one of 5. A user screen display unit that displays a user screen including an element for allowing a user to select a driver who requests driving of a rental car from a plurality of drivers registered in advance;
When a driver is selected on the user screen, the driver's terminal selected on the user screen is approved via the server to notify the server of the fact that the driver has been selected. A notification unit for displaying a driver screen including an element for inputting whether or not,
With
The user screen includes an area for allowing the user to input attribute information of the rental car reserved by the user with respect to the rental car company,
The notification unit displays the rental car attribute information on the driver screen by notifying the server of the rental car attribute information,
When the request is approved on the driver screen, the user screen display unit displays information indicating that on the user screen. Displaying on the user's terminal a user screen including an element for allowing the user to select a driver who requests driving of the rental car from among a plurality of drivers registered in advance;
Displaying a driver screen including an element for allowing the driver's terminal selected on the user screen to input whether or not to approve a request for driving a rental car;
The computer runs,
The user screen includes an area that allows the user to input the rental car attribute information reserved by the user with respect to the rental car company,
The step of displaying the driver screen displays the rental car attribute information input on the user screen on the driver screen,
When a request is approved on the driver screen, the computer further executes a step of displaying information indicating the fact on the user screen.

Images