JP2019020942A - Matching device, matching method, and program - Google Patents

Abstract

To solve the problem in which there is conventionally no such mechanism available for integrating a plurality of websites of companies operating reservation sites of a plurality of drivers.SOLUTION: A matching device provided with a driver information storage unit in which at least two pieces of driver information are stored, a partner information storage unit in which at least two pieces of partner information are stored, a reservation information storage unit in which at least one piece of reservation information is stored, a vehicle allocation instruction reception unit for receiving a vehicle allocation instruction from a user terminal, and a reservation information composition unit for composing reservation information in response to receiving the vehicle allocation instruction and storing thereof into the reservation information storage unit, provides a platform enabling seamlessly reservations of a plurality of drivers managed by partners representing a plurality of management organizations.SELECTED DRAWING: Figure 4

Description

  The present invention relates to a matching device that manages a request for pick-up of a driver such as a taxi.

  Conventionally, there has been a taxi dispatch application system in which it is claimed that a taxi dispatch order and a dispatch reservation can be realized quickly only by a simple operation of a customer communication terminal (see Patent Document 1).

  Such a taxi dispatch application system includes a customer communication terminal possessed by a customer and having a network access function and a location information notification function, and a taxi having a taxi dispatch program configured to be communicable with the customer communication terminal via the network. The company's dispatch management server system, a crew terminal including a taxi radio equipped with a taxi equipped with a location information notification function and a usage charge notification function, and a communicable connection to the dispatch management server system, and via a taxi radio A taxi dispatch application system having a wireless center terminal for wireless communication with the crew terminal, wherein the dispatch management server system is connected to a taxi via a network from a customer communication terminal facing the use of a taxi based on a taxi dispatch program. Dispatch / Receives about request, performs taxi dispatch processing or reservation processing, sends order result screen with message input button to open text message input screen to customer communication terminal, and receives order result screen at customer communication terminal Open the text message input screen by the customer and send the information on the text message input screen to the dispatch management server system via the network in response to the input of the text message, between the customer communication terminal and the dispatch management server system. The main feature is that it is possible to communicate with the text message.

JP 2014-29580 A

  However, in the prior art, there is no mechanism for integrating a plurality of websites of a reservation company operating a plurality of drivers.

  The matching device according to the first aspect of the present invention is information relating to a driver, which is information relating to a driver information storage unit storing two or more driver information having a driver identifier for identifying a driver, and a partner that manages the driver. A partner information storage unit for storing two or more partner information having a partner identifier for identifying the driver and one or more driver identifiers, and a user identifier for identifying a user who reserves the driver. Reservation information is stored in the reservation information storage unit in which the reservation information is stored, the dispatch instruction receiving unit that receives the dispatch instruction from the user terminal, and the receipt of the dispatch instruction. And a reservation information configuration unit.

  With this configuration, it is possible to provide a platform capable of seamlessly reserving a plurality of drivers managed by a partner who is a plurality of management organizations.

  The matching device according to the second aspect of the present invention is the same as that of the first aspect, wherein a charging processing unit for charging a user for a driver reservation or a driver usage is charged, and charging is performed by the charging process. The matching apparatus further includes a distribution processing unit that performs a distribution process for distributing the amount of money between the driver, the partner, and the operating company of the matching apparatus.

  With this configuration, the charged amount can be appropriately distributed on the platform.

  Further, in the matching device of the third invention, in contrast to the first or second invention, the partner information includes distribution information relating to distribution between the driver and the partner, and between the partner and the operating company of the matching device. The distribution information relating to distribution includes one or more pieces of distribution information, and the distribution processing unit is a matching device that performs distribution processing using the distribution information included in the partner information.

  With this configuration, the amount can be distributed according to the distribution conditions for each partner.

  Further, in the matching device of the fourth aspect of the present invention, for any one of the first to third aspects, the driver information has distribution information relating to distribution between the driver and the partner. This is a matching device that performs distribution processing using distribution information included in driver information.

  With this configuration, the amount can be distributed according to the distribution conditions for each driver.

  Further, the matching device of the fifth aspect of the invention is a receiving unit that accepts partner registration information having partner information and one or more driver information corresponding to the partner information for any one of the first to fourth aspects of the invention. And a partner registration unit that accumulates partner information included in the partner registration information in the partner information storage unit and stores one or more driver information included in the partner registration information in the driver information storage unit.

  With this configuration, partner information and driver information can be registered together.

  The matching device according to the sixth aspect of the present invention is a user in which one or more pieces of user information having a user identifier for identifying a user is stored in the first to fifth aspects of the invention. An information storage unit, an inquiry transmission unit that sends an inquiry to one or more drivers about the possibility of pick-up in response to receiving a dispatch instruction, and a driver terminal that grants permission from one driver terminal in response to the transmission of the inquiry And at least a part of the driver information of the driver of the driver terminal that transmitted the permission information is transmitted to the user terminal that transmitted the dispatch instruction in response to the reception of the permission information. A reservation information configuration unit that configures reservation information in response to reception of the license information and stores the reservation information in the reservation information storage unit. A matching device for.

  With this configuration, the user can request the driver to be dispatched with confidence.

  Further, the matching device of the seventh aspect of the invention further comprises an attribute value acquisition unit for acquiring attribute values of two or more drivers with respect to the sixth invention, and the inquiry transmission unit includes two or more drivers. The matching device transmits an inquiry to one or more driver terminals at different times according to the attribute value of each of two or more drivers.

  With this configuration, the matching device can appropriately communicate with the driver terminal.

  In addition, the matching device of the eighth aspect of the invention provides the following inquiry to the seventh aspect of the invention, when the inquiry transmission unit satisfies a predetermined condition for receiving permission information for the transmitted inquiry. Is a matching device that performs transmission.

  With this configuration, the matching device can appropriately communicate with the driver terminal.

  In the matching device of the ninth aspect of the invention, in the seventh or eighth aspect of the invention, the attribute value acquisition unit receives priority order information indicating a priority order for two or more drivers, and each of the two or more drivers. The attribute value is a matching device that is a priority for two or more drivers indicated by the priority information.

  With this configuration, the matching device can appropriately communicate with the driver terminal.

  In the matching device of the tenth invention, the attribute value acquisition unit receives the designation information indicating the designation for one or more drivers, and the inquiry transmission unit, for any one of the seventh to ninth inventions Transmits an inquiry to the driver terminal of one or more drivers corresponding to the specified information, and if the reception of permission information for the transmitted inquiry satisfies a predetermined condition, the one or more drivers not corresponding to the specified information A matching device that transmits an inquiry to a driver terminal.

  With this configuration, the matching device can appropriately communicate with the driver terminal.

  Further, according to the eleventh aspect of the present invention, in response to any one of the seventh to tenth aspects of the invention, the dispatch instruction receiving unit also receives user position information indicating the position of the user terminal. The driver position information receiving unit that receives one or more pieces of driver position information indicating the position of the driver terminal from each driver terminal, and the attribute value acquisition unit are based on the user position information and the one or more pieces of driver position information. This is a matching device that acquires relative position information, which is an attribute value indicating the relative positional relationship between the driver and the driver.

  With this configuration, the matching device can appropriately communicate with the driver terminal.

  Further, the matching device of the twelfth aspect of the present invention is directed to any one of the sixth to eleventh aspects of the invention, a reward information storage unit that stores reward information related to rewards in association with a user identifier, and a driver A remuneration information accumulating unit for accumulating remuneration information in association with the user identifier of the user corresponding to the user terminal when the information transmission unit has not been able to transmit the permission information indicating that the information has been matched to the user terminal; Matching device.

  With this configuration, user satisfaction can be improved even when the driver cannot be dispatched.

  According to the matching device of the present invention, it is possible to provide a platform capable of seamlessly requesting a plurality of drivers managed by a partner who is a plurality of management organizations. be able to.

The figure which shows the conceptual diagram of the information system A in Embodiment 1. FIG. Block diagram of the information system A Block diagram of the user terminal 2 Block diagram of the matching device 1 The figure explaining operation | movement of the matching apparatus 1 The figure explaining operation | movement of the matching apparatus 1 Flow chart explaining the classification process Flow chart explaining the same general driver classification process Flow chart for explaining the operation of the user terminal 2 A flowchart for explaining the operation of the driver terminal 3 A flowchart for explaining the operation of the registration terminal 4 Data structure diagram of driver information in Example 1 Data structure diagram of partner information in Example 1 Figure showing an example of the partner registration information Conceptual diagram of the platform realized using the information system A Data structure diagram of partner information in Example 2 Figure showing the driver information management table Figure showing the same user information management table Figure showing the remuneration information management table Figure showing the relative position condition management table The figure which shows the example of the same screen display The figure which shows the example of the same screen display The figure which shows the example of the same screen display The figure which shows the example of the same screen display The figure which shows the example of the same screen display The figure which shows the example of the same screen display Diagram showing the driver classification information The figure which shows the example of the same screen display Diagram showing the driver classification information The figure which shows the example of the same screen display Overview of the computer system Block diagram of the computer system

  Hereinafter, embodiments of the matching device and the like will be described with reference to the drawings. In addition, since the component which attached | subjected the same code | symbol in embodiment performs the same operation | movement, description may be abbreviate | omitted again.

  (Embodiment 1)

  In the present embodiment, an information system including a matching device that manages reservations for drivers such as taxis by three or more persons (for example, drivers, partners, operating companies, etc.) will be described. A matching device that performs charging and distribution will be described. Further, a matching device that manages the amount distribution condition for each driver will be described. Further, a matching device that manages the amount distribution condition for each driver will be described. A matching device that can register partner information together with driver information will be described.

  Further, in the present embodiment, there is a matching device that transmits an inquiry as to whether or not the vehicle can be picked up by shifting the time to the terminals of two or more drivers in accordance with the attribute value of the driver or the designation of the user. The information system will be described. Also, in the present embodiment, an information system having a matching device that transmits an inquiry to a terminal of a driver not designated by the user when it is detected that the driver designated by the user cannot go to the user will be described. . Also, in the present embodiment, an information system having a matching device that sequentially sends inquiries to a plurality of drivers with priorities assigned according to the relative positions of the driver and the user will be described. In the present embodiment, an information system including a matching device that gives a reward to a user when matching cannot be described will be described. In the present embodiment, an information system including a user terminal that displays driver information such as a photograph of a moving driver on a map will be described. In the present embodiment, an information system including a user terminal that displays driver information such as a photograph of the driver on a map only when the user designates the driver will be described. Further, in the present embodiment, an information system having a user terminal whose screen changes after detecting arrival of a driver will be described. After detecting the arrival of the driver, the user terminal switches to a screen that displays a route to the destination, for example. Further, in this embodiment, an information system having a user terminal whose screen is switched after detecting arrival at the destination will be described. Note that after detecting arrival at the destination, the user terminal switches to a screen on which a message can be input, for example. Furthermore, in the present embodiment, an information system including a user terminal that allows a user to input a driver's evaluation and a driver terminal that allows the driver to input a user's evaluation will be described.

  FIG. 1 is a conceptual diagram of the information system A. The information system A includes a matching device 1, 1 or 2 or more user terminals 2, and 1 or 2 or more driver terminals 3. The matching device 1 is a device that manages information related to user pick-up reservations. The matching device 1 is a device that performs matching between a user and a driver. The matching device 1 is usually a server device, for example, a so-called cloud server, ASP server, or the like, but the type is not limited. The user terminal 2 is a user terminal that requests a driver such as a taxi to pick up a vehicle. The user terminal 2 is, for example, a tablet terminal, a smartphone, a mobile terminal, a notebook computer, or the like, and the type thereof is not limited. The driver terminal 3 is a terminal used by a driver such as a taxi. The driver terminal 3 is, for example, a navigation terminal, a tablet terminal, a smartphone, a mobile terminal, a notebook computer, or the like, and the type thereof is not limited. The driver is, for example, a taxi driver, a so-called white taku driver, a driving agent driver, or the like. However, the driver may be a person who goes to the user and provides a service for traveling with the user. The registration terminal 4 is a terminal for registering partner information and driver information. The registration terminal 4 is, for example, a tablet terminal, a smartphone, a mobile terminal, a notebook computer, or the like, and the type thereof is not limited.

  FIG. 2 is a block diagram of the information system A in the present embodiment. FIG. 3 is a block diagram of the user terminal 2. FIG. 4 is a block diagram of the matching device 1.

  The information system A includes a matching device 1, 1 or 2 or more user terminals 2, 1 or 2 or more driver terminals 3, and 1 or 2 or more registration terminals 4.

  The matching device 1 includes a storage unit 11, a reception unit 12, a reception unit 13, a processing unit 14, and a transmission unit 15.

  The storage unit 11 includes a partner information storage unit 110, a driver information storage unit 111, a user information storage unit 112, a reward information storage unit 113, and a reservation information storage unit 114.

  The receiving unit 12 includes a vehicle allocation instruction receiving unit 121, a permission information receiving unit 122, and a driver position information receiving unit 123.

  The processing unit 14 includes an attribute value acquisition unit 141, a control unit 142, a reward information storage unit 143, a reservation information configuration unit 144, a charging processing unit 145, a distribution processing unit 146, and a partner registration unit 147.

  The transmission unit 15 includes an inquiry transmission unit 151, a driver information transmission unit 152, and a user information transmission unit 153.

  The user terminal 2 includes a user storage unit 21, a user reception unit 22, a user transmission unit 23, a user processing unit 24, a user reception unit 25, and a user output unit 26.

  The user storage unit 21 includes a map information storage unit 211.

  The user reception unit 22 includes a vehicle allocation instruction reception unit 221, a destination reception unit 222, and a driver evaluation reception unit 223.

  The user transmission unit 23 includes a vehicle allocation instruction transmission unit 231 and a driver evaluation transmission unit 232.

  The user processing unit 24 includes a driver arrival detection unit 241, a destination arrival detection unit 242, and a display screen change unit 243.

  The user receiving unit 25 includes a driver information receiving unit 251.

  The user output unit 26 includes a map output unit 261 and a driver attribute value output unit 262.

  The driver terminal 3 includes a driver storage unit 31, a driver reception unit 32, a driver transmission unit 33, a driver processing unit 34, a driver reception unit 35, and a driver output unit 36.

  The driver processing unit 34 includes a driver arrival detection unit 341, a destination arrival detection unit 342, and a display screen change unit 343.

  The registration terminal 4 includes a registration storage unit 41, a registration reception unit 42, a registration transmission unit 43, a registration processing unit 44, a registration reception unit 45, and a registration output unit 46.

  The storage part 11 which comprises the matching apparatus 1 can store various information. The various information includes, for example, partner information described later, driver information described later, user information described later, reward information described later, reservation information described later, and the like. The various information is, for example, one or two or more relative position conditions. The relative position condition is a condition for grouping using the relative position information, and is a condition associated with a group ID for identifying a group. The relative position condition is, for example, “relative position information <= 500 m” associated with the first group, and “500 <relative position information <= 1 km” associated with the second group. The relative position conditions are, for example, “relative position information <= 1 minute” corresponding to the first group, “1 minute <relative position information <= 3 minutes” corresponding to the second group, “3 minutes <relative position information <= 5 minutes” corresponding to the group. The relative position condition is, for example, a condition for relative position information regarding the distance or time between the user and the driver. The various information is, for example, screen information. Screen information is information constituting a screen. The screen here is, for example, a screen for instructing driver dispatch. For example, the screen is preferably a screen on which two or more drivers managed by a partner corresponding to each of two or more partner identifiers are allocated (may be referred to as reservation). The screen information is, for example, HTML, XML, image data and a program. However, the means for realizing the screen information does not matter.

  The partner information storage unit 110 stores two or more partner information. Partner information is information about the partner. A partner is an organization or person who manages one or more drivers. The partner information includes a partner identifier and one or more driver identifiers. The partner identifier is information for identifying a partner. The partner identifier is, for example, an ID for identifying a partner, a partner name, or the like, but may be anything as long as the partner can be identified. The driver identifier is information for identifying the driver. The driver identifier is, for example, an ID for identifying the driver, a driver name, or the like, but may be anything as long as the driver can be identified.

  The partner information includes distribution information relating to distribution between the driver and the partner (referred to as first distribution information as appropriate), distribution information relating to distribution between the partner and the operating company of the matching device 1 (as appropriate, second distribution information). It is preferable to have one or more pieces of distribution information. The partner information usually has second distribution information. The second distribution information includes, for example, a distribution ratio between the partner and the operating company. The ratio of distribution between the partner and the operating company may be, for example, 4: 3, 2: 1, or the like. However, the data structure of the second distribution information does not matter. The first distribution information also includes a distribution ratio between the driver and the partner, for example.

  It is more preferable that the partner information includes, for example, first distribution information and second distribution information. Such partner information indicates the distribution ratio between the driver, the partner and the operating company. The distribution ratio between the driver, the partner, and the operating company may be, for example, 5: 5: 3, 7: 3: 1, or the like.

  The driver information storage unit 111 stores two or more driver information. Driver information is information about the driver. The driver information includes a driver identifier that identifies the driver. The driver information includes, for example, a driver identifier, name, age, driver evaluation, driver photo, and the like. The driver information may include first distribution information. The driver information may have a partner identifier. The driver identifier may be anything as long as it is information for identifying the driver, such as ID, name, e-mail address, telephone number, and the like. The driver evaluation is information related to driver evaluation, and is, for example, a natural number from 1 to 5, an integer from 0 to 100, an evaluation value of any one of “A, B, and C”. The number of identifications for evaluation is not limited, and may be 5 levels or 10 levels. The driver photo is information on a photo in which the driver is photographed, and a face photo is preferable, but an image of a photo of the entire body may be used.

  The user information storage unit 112 stores one or more user information. User information is information about the user. The user information has a user identifier. The user information includes, for example, a user identifier, name, credit card number, user evaluation, and the like. The user identifier is information for identifying the user, and is, for example, an ID, a name, a mail address, a telephone number, or the like. The user evaluation is information related to user evaluation, and is, for example, a natural number from 1 to 5, an integer from 0 to 100, an evaluation value of “A, B, C”, or the like. The number of identifications for evaluation is not limited, and may be 5 levels or 10 levels.

  The reward information storage unit 113 stores reward information related to rewards in association with the user identifier. Note that the reward information may be considered to be included in the user information. The reward information is, for example, points, money, an identifier of a product or service given to the user, or the like. The reward may be anything as long as it gives a profit to the user.

  The reservation information storage unit 114 stores one or more reservation information. The reservation information is information related to the driver's reservation. The reservation information includes a user identifier that identifies a user who reserves the driver. The reservation information may have a driver identifier. The reservation information may include time information indicating a time when the driver goes to pick up and position information indicating a place where the driver goes to pick up.

  The receiving unit 12 receives various information and instructions. The various types of information and instructions include, for example, a vehicle dispatch instruction described later, user position information described later, permission information described later, driver position information described later, and the like.

  The dispatch instruction receiving unit 121 receives a dispatch instruction from the user terminal 2. The dispatch instruction is an instruction for the user to request a driver. It may be said that the vehicle allocation instruction is an instruction that the user requests the driver to pick up the vehicle. The dispatch instruction receiving unit 121 also receives user position information indicating the position of the user terminal 2, for example. The user position information is, for example, (latitude, longitude), but the format is not limited.

  The license information receiving unit 122 receives license information from one driver terminal 3 in response to the transmission of the inquiry. The inquiry is an inquiry as to whether or not the driver terminal 3 can go to the user. The permission information is information indicating permission to go to the user. The permission information includes, for example, driver position information and a driver identifier. However, the license information receiving unit 122 may receive driver position information, a driver identifier, and the like in association with the license information. The driver position information is information indicating the position of the driver terminal 3. The driver position information is, for example, (latitude, longitude), but the format is not limited.

  Note that the license information receiving unit 122 may receive license information from two or more driver terminals 3. In such a case, one driver terminal 3 is selected by some algorithm from the two or more driver terminals 3 that have transmitted the permission information.

  The driver position information receiving unit 123 receives one or more driver position information indicating the position of the driver terminal 3 from one or more driver terminals.

  The reception unit 13 receives various types of information. Examples of the various information include partner registration information and driver registration information. Partner registration information is information regarding partner registration.

  The partner registration information usually includes partner information and one or more driver information corresponding to the partner information. However, the data structure of partner registration information does not matter. It is preferable that the reception unit 13 receives partner information and one or more pieces of driver information at a time. As a result, the previous operation of the partner is taken over as it is and is operated by the matching device 1. The previous management is information on the distribution of revenue and information on contracts between the partner and one or more drivers.

  The driver registration information is information related to driver registration. The driver registration information usually includes driver information. However, the data structure of the driver registration information does not matter.

  The reception here is usually reception of information transmitted via a network or the like, but for example, reception of information input from an input device such as a keyboard or from a recording medium such as an optical disk, a magnetic disk, or a semiconductor memory. It is a concept that includes acceptance of read information. The receiving unit 13 usually receives partner registration information or the like from the registration terminal 4 via a network or the like. For example, it may be received via an input device such as a keyboard or may be read from a recording medium. .

  In addition, the reception part 13 may receive partner information and driver information separately.

  The processing unit 14 performs various processes. The various processes include, for example, a partner registration unit 147, an attribute value acquisition unit 141, a control unit 142, a reward information storage unit 143, a reservation information configuration unit 144, a billing processing unit 145, a distribution processing unit 146, a partner registration unit 147, and the like. Is a process performed. The various types of processing include various types of determination described with reference to flowcharts.

  The attribute value acquisition unit 141 acquires attribute values of two or more drivers. The attribute value acquisition unit 141 acquires attribute values of two or more drivers from the driver information storage unit 111. The acquired attribute value is, for example, driver position information, driver evaluation, priority order, and the like.

  The attribute value acquisition unit 141 receives priority order information indicating the priority order for two or more drivers. The attribute value acquisition unit 141 receives priority order information from the user terminal 2. The priority order information is, for example, two or more driver identifiers having order and two or more sets of order and driver identifiers.

  The attribute value acquisition unit 141 receives designation information indicating designation for one or more drivers. The designation information may be the same as the priority information. One or more driver identifiers may be used.

  The attribute value acquisition unit 141 acquires relative position information based on the user position information and one or more pieces of driver position information. The relative position information is information indicating a relative positional relationship between the user and the driver. The relative position information is, for example, a distance and a movement time. Note that the relative position information may be considered as an example of a driver attribute value.

  The control unit 142 classifies drivers into two or more groups using attribute values of two or more drivers. This classification is a classification for the inquiry transmission unit 151 to transmit an inquiry to the driver terminal 3. This classification is a classification of two or more drivers having priority.

  Here, it is preferable that the attribute value of one or more drivers used for classification of two or more drivers has driver position information. For classification of two or more drivers, it is preferable to use relative position information acquired from user position information and driver position information. The relative position information is information indicating a relative positional relationship between the user and the driver. The relative position information is an example of an attribute value. The relative position information is, for example, the distance between the user and the driver and the moving time of the driver calculated from the distance.

  The control unit 142 preferably classifies two or more drivers into two or more groups according to the received priority order information. For example, according to the priority order information, the control unit 142 stores the driver identifiers of the drivers of each group in association with the first to Nth (N is a natural number of 2 or more) groups. Further, for example, the control unit 142 sets the driver identifiers of the drivers belonging to the groups after the (N + 1) th group according to the relative position information among the drivers not corresponding to the priority information (not specified by the user). You may associate with the group after the N + 1 group.

  The control unit 142 preferably classifies two or more drivers into two or more groups according to the received designation information. For example, the control unit 142 associates the driver identifiers of one or more drivers designated by the designation information with the first group having the highest priority, and determines the second group according to the relative position information among other drivers. Driver identifiers of drivers belonging to subsequent groups may be associated with groups after the second group.

  When the driver information transmission unit 152 cannot transmit the permission information to the user terminal 2, the reward information storage unit 143 stores the reward information in association with the user identifier of the user corresponding to the user terminal 2. The transmission of the permission information indicates that the user and the driver can be matched. The accumulation of reward information may be a new accumulation of reward information or an increase in reward information such as stored points.

  The reservation information configuration unit 144 configures reservation information in response to reception of the dispatch instruction and stores the reservation information in the reservation information storage unit 114. The reservation information configuration unit 144 may configure the reservation information in response to reception of the permission information and store it in the reservation information storage unit 114. The reservation information may be considered to be information related to the driver heading to the user.

  The billing processing unit 145 performs billing processing. The charging process is a process for charging the user for the reservation of the driver or the use of the driver. The charging processing unit 145 performs charging processing when a predetermined condition is satisfied. Predetermined conditions include, for example, detecting that the user has arrived at the destination, detecting that the user has been removed from the car, and detecting that the driver has arrived at the user. is there. The billing process is a process necessary for billing, for example, transmission of information for billing to a billing server (not shown), accumulation of information necessary for billing, billing process using a credit card number Etc. The content of the billing process here does not matter. The charging process can be realized by a known technique, and thus detailed description is omitted.

  The distribution processing unit 146 performs distribution processing. The distribution process is a process for distributing the amount charged by the charging process among the driver, the partner, and the operating company of the matching device 1.

  For example, the distribution processing unit 146 performs distribution processing using distribution information included in the partner information. The distribution information included in the partner information is one or more distribution information of the first distribution information or the second distribution information. Specifically, for example, when the partner information includes the first distribution information, the distribution processing unit 146 performs distribution processing between the driver and the partner using the first distribution information. Alternatively, for example, when the partner information includes the second distribution information, the distribution processing unit 146 performs a distribution process between the partner and the operating company of the matching device 1 using the second distribution information. Alternatively, when the partner information includes the first distribution information and the second distribution information, the distribution processing unit 146 performs a distribution process between the driver and the partner and a distribution process between the partner and the operating company of the matching device 1. I do. The distribution process is a process for determining distribution of profits between the two or three parties (for example, the driver, the partner, and the operating company of the matching device 1). The distribution process is, for example, a process of calculating the profits of two or more entities among drivers, partners, and management companies of the matching device 1. The distribution process is, for example, a process of calculating the profits of two or more entities among the driver, the partner, and the operating company of the matching apparatus 1, and depositing the profits to the bank account or the like. The distribution processing is, for example, notification of distribution amount (for example, automatic notification by e-mail, FAX, or the like) to two or more entities among the driver, the partner, and the operating company of the matching apparatus 1.

  Further, the distribution processing unit 146 may perform distribution processing between the driver and the partner using the first distribution information included in the driver information. For example, when the partner information does not have the first distribution information, the distribution processing unit 146 preferably performs the distribution process between the driver and the partner using the first distribution information included in the driver information. .

  The distribution processing unit 146 normally executes the distribution processing at a predetermined date and time (for example, 12:00 at the end of the month, 17:00 on the 15th of every month), but may be executed in response to the completion of the accounting process. The timing of execution is not questioned.

  The partner registration unit 147 accumulates the partner information included in the partner registration information in the partner information storage unit 110, and accumulates one or more driver information included in the partner registration information in the driver information storage unit 111.

  The partner registration unit 147 accumulates partner information included in the partner registration information received by the reception unit 13 in the partner information storage unit 110. The partner registration unit 147 accumulates one or more pieces of driver information included in the partner registration information received by the receiving unit 13 in the driver information storage unit 111. The partner registration unit 147 preferably stores the partner information included in the partner registration information received by the reception unit 13 and one or more driver information together in the storage unit 11. The partner registration information received by the receiving unit 13, the accumulated partner information, and one or more driver information may have different data structures or different identifiers of various types of information. That is, the partner registration information received by the receiving unit 13, the accumulated partner information, and the one or more driver information may not be completely the same. However, the partner registration information received by the receiving unit 13, the accumulated partner information, and the one or more driver information have the same information entity (for example, the driver's name).

  However, the partner registration unit 147 may accumulate the partner information received by the receiving unit 13 in the partner information storage unit 110. Further, the partner registration unit 147 may accumulate the driver information received by the reception unit 13 in the driver information storage unit 111.

  The transmission unit 15 transmits various information and instructions. Various types of information, instructions, and the like refer to an inquiry, driver information, which will be described later, at least a part of information (sometimes simply referred to as driver information), and at least a part of user information (simply referred to as user information). In some cases).

  The inquiry transmission unit 151 transmits an inquiry to one or two or more driver terminals 3 in response to reception of the dispatch instruction. The inquiry is an inquiry for a driver and a request for a response as to whether or not pick-up is possible. The inquiry may be considered as a response command for requesting whether or not the pick-up is possible. Pick-up means going to the user. The inquiry may also include a user identifier or user location information. The inquiry may include at least a part of user information such as a user name.

  The inquiry transmission unit 151 transmits an inquiry to one or more driver terminals 3 by shifting the time according to one or two or more attribute values of each of two or more drivers to the driver terminals 3 of two or more drivers. It is preferable to do.

  For example, the inquiry transmission unit 151 transmits the next inquiry when reception of permission information for the transmitted inquiry satisfies a predetermined condition. Here, the predetermined condition indicates that the pick-up is “possible” from all the driver terminals 3 that have transmitted the inquiry for a time longer than the predetermined time or more than the predetermined time. This is a case where the license information could not be received. The permission information indicating that the pick-up is “possible” cannot be received when the content of the received permission information is “impossible” or when the permission information cannot be received. The permission information is usually information indicating permission (information indicating that the pick-up is “possible”) or information indicating that the pick-up is “impossible”.

  It is preferable that the inquiry transmission unit 151 transmits the inquiry to the driver terminals 3 belonging to each group at different times for each of the two or more groups classified by the control unit 142. That is, the inquiry transmission unit 151 first transmits an inquiry to one or more driver terminals 3 in the first group using the result of the control unit 142 classifying two or more drivers into two or more groups. If all of the one or more driver terminals 3 of the first group do not transmit permission information indicating permission or do not respond at all for a predetermined time or more than a predetermined time, It is preferable to send an inquiry to one or more driver terminals 3 in the group. When two or more drivers are classified into three or more groups, the inquiry transmission unit 151 may send the one or more drivers of the second group for a predetermined time or more or a time longer than the predetermined time. When all of the terminals 3 do not transmit permission information indicating permission or do not respond at all, it is preferable to transmit an inquiry to one or more driver terminals 3 of the third group. It is preferable that the inquiry transmission unit 151 can execute such processing on one or more driver terminals 3 in an Nth (N is an integer of 2 or more) group.

  The inquiry transmission unit 151 transmits an inquiry to the driver terminal 3 of one or more drivers corresponding to the designation information, and when receiving the permission information indicating permission for the transmitted inquiry satisfies a predetermined condition, The inquiry may be transmitted to the driver terminal 3 of one or more drivers that do not correspond to the designation information.

  Further, the attribute value of one or more drivers used for classification of two or more drivers may be a priority order for two or more drivers indicated by the priority order information. Such priority information is information transmitted from the user terminal.

  In response to receiving the permission information indicating permission, the driver information transmitting unit 152 transmits at least a part of the driver information of the driver of the driver terminal 3 that has transmitted the permission information to the user terminal 2 that has transmitted the dispatch instruction. Send. The driver information transmission unit 152 acquires at least a part of the driver information paired with the driver identifier included in the permission information from the driver information storage unit 111, and transmits the acquired information to the vehicle allocation instruction. To the user terminal 2. Note that the information to be transmitted preferably has a name or a driver photo.

  The user information transmission unit 153 transmits at least part of the user information to one or more driver terminals 3. The user information transmission unit 153 acquires information paired with the user identifier included in the received dispatch instruction from the user information storage unit 112, and transmits the information to one or more driver terminals 3. The information paired with the user identifier is at least a part of the user information, such as the user's name and evaluation. The user information transmission unit 153 may transmit user information to the driver terminal 3 that has transmitted the permission information indicating permission, or may transmit the user information to the driver terminal 3 that transmits an inquiry.

  Various information is stored in the user storage unit 21 constituting the user terminal 2. The various information includes, for example, a user identifier, a map information case, and route information.

  The map information storage unit 211 stores map information. Map information is information about a map. Further, the type of map indicated by the map information, the data format of the map information, etc. are not limited. The types of the maps are, for example, road maps, topographic maps, topographic maps, geological maps, land use maps, housing maps, route maps, guide maps, aerial photographs, satellite photographs, and the like. The data format is, for example, raster data, vector data, KIWI format, or the like.

  The user reception unit 22 receives various information and instructions. The various information, instructions, and the like are, for example, a vehicle dispatch instruction, a destination, and driver evaluation described later.

  Here, reception means reception of information input from an input device such as a keyboard, mouse, touch panel, reception of information transmitted via a wired or wireless communication line, recording on an optical disk, magnetic disk, semiconductor memory, or the like. It is a concept including reception of information read from a medium.

  The input means for various information and instructions may be anything such as a touch panel, a keyboard, a mouse, or a menu screen.

  The dispatch instruction receiving unit 221 receives a dispatch instruction. The dispatch instruction is an instruction for dispatch. The dispatch instruction is an instruction to arrange by the driver. The dispatch instruction usually includes a user identifier. The dispatch instruction may include user position information.

  The destination reception unit 222 receives a destination. The reception of the destination includes reception of (latitude, longitude) indicating the destination, reception of a name specifying the destination, and the like. There is no limitation on how to accept the destination.

  The driver evaluation reception unit 223 receives a driver evaluation.

  The user transmission unit 23 transmits various information and instructions. Various types of information, instructions, and the like are, for example, vehicle dispatch instructions, driver evaluation, and route information.

  The dispatch instruction transmitting unit 231 transmits the dispatch instruction received by the dispatch instruction receiving unit 221 to the matching device 1. Needless to say, the structure of the instruction of the dispatch instruction received by the dispatch instruction receiving unit 221 and the instruction of the dispatching instruction to be transmitted may be different.

  The driver evaluation transmission unit 232 transmits the driver identifier and the driver evaluation to the matching device 1.

  The user processing unit 24 performs various processes. Various processes are processes which acquire user position information, for example. The user processing unit 24 acquires user position information using, for example, a GPS receiver. Further, the user processing unit 24 may acquire the user position information using, for example, signal strengths from three or more mobile phone base stations. There are various processes for acquiring the user position information, and since it is a known technique, a detailed description is omitted.

  The driver arrival detection unit 241 detects the arrival of the driver. For example, when the driver arrival detection unit 241 determines that the position indicated by the received driver position information and the position indicated by the user position information are close enough to satisfy a predetermined condition, the driver arrival detection unit 241 detects that the driver has arrived.

  Further, the driver arrival detection unit 241 detects the arrival of the driver when information indicating that the driver has arrived is received from the driver terminal 3 or the matching device 1, for example. In such a case, the driver terminal 3 or the matching device 1 transmits information indicating that it has arrived at the user terminal 2.

  Note that the method for detecting the arrival of the driver by the driver arrival detecting unit 241 is not limited.

  The destination arrival detection unit 242 detects arrival at the destination. For example, when the destination arrival detection unit 242 determines that the position indicated by the stored location information of the destination and the location indicated by the user location information are close enough to satisfy a predetermined condition, the destination arrival detection unit 242 has arrived at the destination Detect that. Since the technique for detecting arrival at the destination is a known technique, detailed description thereof is omitted.

  The display screen change unit 243 switches the display screen when the driver arrival detection unit 241 detects the arrival of the driver.

  The display screen changing unit 243 switches the display screen when the destination arrival detection unit 242 detects arrival at the destination.

  The display screen information switched by the display screen changing unit 243 or the screen information output by the user output unit 26 is stored in the user storage unit 21. Further, the information on the display screen is normally stored in the user storage unit 21 in association with information indicating detection of driver arrival or information indicating detection of arrival at the destination. The information on the display screen is described in, for example, HTML, XML, etc., but the structure or the like is not limited.

  When the driver arrival detection unit 241 detects the arrival of the driver, for example, the display screen change unit 243 acquires a screen on which a route to the destination is displayed and switches to the screen. A technique for obtaining a screen displaying a route to a destination when information indicating the position of the destination is stored in the user storage unit 21 is a known technique, and thus detailed description thereof is omitted. The screen displaying the route to the destination may be a screen displaying the entire route from the current position to the destination indicated by the user position information, or a screen displaying a part of the route. good.

  When the driver arrival detection unit 241 detects the arrival of the driver or when the destination arrival detection unit 242 detects arrival at the destination, for example, the display screen change unit 243 can input a message or driver evaluation. Switch to the correct screen. The message is, for example, a message indicating gratitude to the driver, a complaint to the driver, or the like.

  When the destination arrival detection unit 242 detects arrival at the destination, for example, the display screen change unit 243 switches to a screen that can input provision of a chip to the driver. Such a screen has, for example, a field for inputting the amount of a chip, a button for instructing provision of a chip, a menu item, or the like.

  The user receiving unit 25 receives various types of information. The various information is, for example, at least a part of the driver information.

  The driver information receiving unit 251 receives driver position information of a driver and a driver attribute value that is an attribute value of the driver. The driver attribute value preferably includes a driver photograph that is a photograph of the driver.

  The user output unit 26 outputs various information. The various information includes, for example, a map, a driver attribute value, information received by the user receiving unit 25, information received by the user receiving unit 22, and the like.

  Here, the output is usually a display on a display, but projection using a projector, printing with a printer, sound output, transmission to an external device, accumulation in a recording medium, other processing devices and others It may be considered that the concept includes the delivery of processing results to the program.

  The map output unit 261 uses the map information stored in the map information storage unit 211 to output a map.

  The driver attribute value output unit 262 outputs the driver attribute value to a position specified by the driver position information on the map. That is, when two or more received driver position information indicates the movement of the driver, for example, a driver attribute value (for example, a driver photograph) moves on the map and is output.

  It is preferable that the driver attribute value output unit 262 outputs information including a driver photograph only when the driver corresponding to the driver attribute value is a driver designated by the user.

  Various types of information are stored in the driver storage unit 31 constituting the driver terminal 3. The various information is, for example, a driver identifier.

  The driver reception unit 32 receives various information and instructions. The various information and instructions are, for example, permission information indicating that the pick-up is possible, permission information indicating that the pick-up is impossible, and user evaluation.

  The driver transmission unit 33 transmits various information and instructions. The various types of information, instructions, and the like are various types of information and instructions received by the driver receiving unit 32, driver position information acquired by a driver processing unit 34, which will be described later, and the like. Needless to say, the various types of information and instructions received by the driver reception unit 32 and the various types of information and instructions transmitted by the driver transmission unit 33 may have different structures.

  The driver processing unit 34 performs various processes. The various processes are, for example, a process of acquiring driver position information and a structure of various information and instructions received by the driver receiving unit 32 such as information to be transmitted and instructions. In addition, the various processes include, for example, a structure or screen for outputting information received by the driver receiving unit 35. In addition, the process which acquires driver position information may be implement | achieved by the GPS receiver.

  The driver arrival detection unit 341 detects that the driver has arrived at the user. The driver arrival detection unit 341 performs the same processing as the driver arrival detection unit 241.

  The destination arrival detection unit 342 detects arrival at the destination. The destination arrival detection unit 342 performs the same processing as the destination arrival detection unit 242. The destination information is stored in the driver storage unit 31, for example.

  The display screen changing unit 343 switches the display screen when the driver arrival detection unit 341 detects that the driver has arrived at the user. The display screen switching may be acquisition of screen information of a screen to be displayed next or output of a new screen.

  The display screen change unit 343 switches the display screen when the destination arrival detection unit 342 detects arrival at the destination.

  The display screen information switched by the display screen changing unit 343 or the screen information output by the driver output unit 36 is stored in the driver storage unit 31. The information on the display screen is usually stored in the driver storage unit 31 in association with information indicating detection of arrival of the driver or information indicating detection of arrival at the destination. The information on the display screen is described in, for example, HTML, XML, etc., but the structure or the like is not limited.

  When the driver arrival detection unit 341 detects arrival of a driver, for example, the display screen change unit 343 acquires a screen on which a route to the destination is displayed and switches to the screen. A technique for obtaining a screen displaying a route to a destination when information indicating the position of the destination is stored in the driver storage unit 31 is a known technique, and thus detailed description thereof is omitted. The screen displaying the route to the destination may be a screen displaying the entire route from the current position to the destination indicated by the user position information, or a screen displaying a part of the route. good.

  When the driver arrival detection unit 341 detects that the driver has arrived at the user or when the destination arrival detection unit 342 detects arrival at the destination, for example, the display screen changing unit 343 Switch to a screen where user evaluation can be entered.

  When the destination arrival detection unit 342 detects arrival at the destination, for example, the display screen change unit 343 switches to a screen on which user evaluation can be input.

  The driver receiving unit 35 receives various information and instructions. The various information, instructions, and the like are, for example, the above-described inquiry, at least a part of user information, and the like.

  The driver output unit 36 outputs various information. The various information includes, for example, a screen corresponding to the received inquiry, information on at least a part of user information, and the like.

  The registration storage unit 41 constituting the registration terminal 4 stores various types of information. The various information is, for example, partner registration information.

  The registration receiving unit 42 receives various types of information. The various information is, for example, partner registration information. The registration accepting unit 42 usually accepts partner registration information via an input device such as a keyboard.

  The registration transmission unit 43 transmits various types of information. The various information is, for example, partner registration information. For example, the registration transmission unit 43 transmits the partner registration information received by the registration reception unit 42 to the matching device 1. For example, the registration transmission unit 43 transmits the partner registration information in the registration storage unit 41 to the matching device 1.

  The registration processing unit 44 performs various processes. The various processes are, for example, processes for accumulating partner registration information and the like in the registration storage unit 41. Since this process can be performed using a known technique, a detailed description is omitted.

  The registration receiving unit 45 receives various types of information. The various information is, for example, information indicating completion of registration of partner registration information.

  The registration output unit 46 outputs various information. The various information includes, for example, information received by the registration receiving unit 45, information received by the registration receiving unit 42, and the like. In general, output means display on a display, sound output from a speaker, printing on a printer, transmission to an external device, storage in a recording medium, delivery of processing results to another processing device or other program, etc. It is a concept that includes

  The storage unit 11, the partner information storage unit 110, the driver information storage unit 111, the user information storage unit 112, the reward information storage unit 113, the reservation information storage unit 114, the user storage unit 21, the driver storage unit 31, and the registration storage unit 41 are A non-volatile recording medium is suitable, but a volatile recording medium can also be realized.

  The process in which information is stored in the storage unit 11 or the like is not limited. For example, information may be stored in the storage unit 11 or the like via a recording medium, information transmitted via a communication line or the like may be stored in the storage unit 11 or the like, Alternatively, information input via the input device may be stored in the storage unit 11 or the like.

  The receiving unit 12, the dispatch instruction receiving unit 121, the permission information receiving unit 122, the driver position information receiving unit 123, the user receiving unit 25, the driver receiving unit 35, and the registration receiving unit 45 are usually realized by wireless or wired communication means. However, it may be realized by means of receiving a broadcast.

  The reception unit 13, the user reception unit 22, the driver reception unit 32, and the registration reception unit 42 may or may not include an input device. The receiving unit 13 and the like can be realized by driver software for the input device or by the input device and its driver software.

  Processing unit 14, attribute value acquisition unit 141, control unit 142, reward information storage unit 143, reservation information configuration unit 144, billing processing unit 145, distribution processing unit 146, partner registration unit 147, user processing unit 24, driver arrival detection unit 241, destination arrival detection unit 242, display screen change unit 243, driver processing unit 34, driver arrival detection unit 341, destination arrival detection unit 342, display screen change unit 343, and registration processing unit 44 are usually MPU or It can be realized from a memory or the like. The processing procedure of the processing unit 14 or the like is usually realized by software, and the software is recorded on a recording medium such as a ROM. However, the processing procedure may be realized by hardware (dedicated circuit).

  The transmission unit 15, inquiry transmission unit 151, driver information transmission unit 152, user information transmission unit 153, user transmission unit 23, dispatch instruction transmission unit 231, driver evaluation transmission unit 232, driver transmission unit 33, and registration transmission unit 43 Usually, it is realized by a wired or wireless communication means, but may be realized by a broadcasting means (for example, a broadcasting module).

  The user output unit 26, the map output unit 261, the driver attribute value output unit 262, the driver output unit 36, and the registration output unit 46 may or may not include an output device such as a display or a speaker. The management output unit 23 and the like can be realized by output device driver software, or by an output device and its driver software.

  Next, the operation of the information system A will be described. First, operation | movement of the matching apparatus 1 is demonstrated using the flowchart of FIG. 5, FIG.

  (Step S501) The dispatch instruction receiving unit 121 determines whether a dispatch instruction or the like has been received from the user terminal 2. If a vehicle dispatch instruction or the like has been received, the process goes to step S502. If no vehicle dispatch instruction or the like has been received, the process goes to step S517. The dispatch instruction or the like has, for example, a user identifier, user position information, and one or more driver identifiers.

  (Step S <b> 502) The control unit 142 classifies two or more drivers in response to reception of a dispatch instruction or the like. Such classification processing will be described with reference to the flowchart of FIG.

  (Step S503) The inquiry transmission unit 151 substitutes 1 for a counter i.

  (Step S504) The inquiry transmission unit 151 determines whether or not the i-th group exists in the classification result in step S502. If the i-th group exists, the process goes to step S505, and if the i-th group does not exist, the process goes to step S515.

  (Step S505) The inquiry transmission unit 151 acquires one or more driver identifiers associated with the i-th group. Then, the inquiry transmission unit 151 transmits an inquiry to one or more driver terminals 3 identified by the one or more driver identifiers. The inquiry preferably includes at least a part of user information. That is, the inquiry transmission unit 151 obtains at least a part of the user information paired with the user identifier included in the vehicle allocation instruction received in step S501 from the user information storage unit 112, and obtains the obtained information. It is preferred to send a query containing information.

  (Step S506) Inquiry transmission part 151 judges whether it is time-out. If the time has expired, the process goes to step S509. If the time has not expired, the process goes to step S507. The term “time out” means, for example, that a time longer than a predetermined time or more than a predetermined time has elapsed since the inquiry was transmitted.

  (Step S507) The permission information receiving unit 122 determines whether information has been received from one or more driver terminals. If the information is received, the process goes to step S508. If not, the process returns to step S506. The information usually corresponds to the driver identifier. The information is, for example, permission information.

  (Step S508) The processing unit 14 temporarily stores the information received in Step S507 in the storage unit 11 in association with the driver identifier. The process returns to step S506.

  (Step S509) The processing unit 14 performs processing for determining a driver to go to the user. That is, the processing unit 14 acquires one driver identifier among one or more driver identifiers corresponding to the license information indicating the license stored in the storage unit 11. When there is one driver identifier corresponding to the license information stored in the storage unit 11, the processing unit 14 acquires the one driver identifier. Further, when the driver identifier corresponding to the license information stored in the storage unit 11 is 2 or more, the processing unit 14 may select the one driver identifier at random, or correspond to the smallest relative distance information. One driver identifier may be selected. When one driver identifier corresponding to the smallest relative distance information is selected, it is assumed that relative distance information is calculated for each driver using user position information and driver position information. In addition, when there is no driver identifier corresponding to the license information stored in the storage unit 11, the processing unit 14 cannot acquire the driver identifier. The fact that the driver identifier cannot be acquired means that the driver to go to the user cannot be determined.

  (Step S510) The processing unit 14 determines whether or not a driver has been determined in step S509. If the driver can be determined, the process proceeds to step S511. If the driver cannot be determined, the process proceeds to step S512.

  (Step S511) The inquiry transmission unit 151 increments the counter i by one. The process returns to step S504.

  (Step S512) The processing unit 14 acquires at least a part of the driver information among the driver information paired with the one driver identifier acquired in Step S509.

  (Step S513) The driver information transmission unit 152 transmits the driver information acquired in Step S512 to the user terminal 2 that has transmitted the dispatch instruction.

  (Step S514) The processing unit 14 performs post-processing. The process returns to step S501. The post-processing is, for example, processing for acquiring at least a part of user information of a user who has transmitted a dispatch instruction and transmitting the information to the driver terminal 3.

  (Step S515) The reward information storage unit 143 acquires reward information to be given to the user who has transmitted the dispatch instruction. The reward information may be determined in advance or may change dynamically. For example, the reward information changes dynamically such that the higher the user evaluation, the larger the reward information.

  (Step S516) The reward information storage unit 143 stores the reward information acquired in step S515 in the reward information storage unit 113 in association with the user identifier that identifies the user who has transmitted the dispatch instruction. The process returns to step S501.

  (Step S517) The driver position information receiving unit 123 determines whether or not driver position information has been received. If the driver position information is received, the process goes to step S518. If the driver position information is not received, the process goes to step S519. The driver position information is received in association with the driver identifier.

  (Step S518) The processing unit 14 stores the driver position information received in step S517 in the storage unit 11 in association with the driver identifier. The process returns to step S501.

  (Step S519) The reception unit 13 determines whether partner registration information has been received. If the accepting unit 13 accepts the partner registration information, the process proceeds to step S520. If not accepted, the process proceeds to step 521.

  (Step S520) The partner registration unit 147 accumulates the partner information included in the partner registration information received by the reception unit 13 in the partner information storage unit 110.

  (Step S <b> 521) The partner registration unit 147 accumulates one or more pieces of driver information included in the partner registration information received by the reception unit 13 in the driver information storage unit 111. The process returns to step S501.

  (Step S522) The reception unit 13 determines whether driver registration information has been received. If the accepting unit 13 accepts the driver registration information, the process proceeds to step S523. If not accepted, the process proceeds to step S524.

  (Step S523) The processing unit 14 accumulates the driver information included in the driver registration information received by the receiving unit 13 in the driver information storage unit 111. The process returns to step S501.

  (Step S524) The processing unit 14 determines whether or not to charge. If it is charged, the process proceeds to step S525. Otherwise, the process proceeds to step S526. Note that the processing unit 14 holds a predetermined condition regarding the execution of charging, for example, when information for charging including an amount and a user identifier is received from the driver terminal 3, and the conditions If the condition is satisfied, it is determined to charge.

  (Step S525) The billing processing unit 145 executes billing processing. The billing process is not repeated because it has been described above. Thereafter, the process returns to step S501.

  (Step S526) The processing unit 14 determines whether to distribute. When distributing, it progresses to step S527, and when not distributing, it returns to step S501. Note that the processing unit 14 holds predetermined conditions regarding the execution of distribution such as, for example, that a predetermined date and time has been reached, and that the accounting process has been completed. To do.

  (Step S527) The distribution processing unit 146 executes distribution processing. Since the distribution process has been described above, it will not be repeated. Thereafter, the process returns to step S501.

  In the flowcharts of FIGS. 5 and 6, the processing is ended by powering off or interruption for aborting the processing.

  Further, in the flowcharts of FIGS. 5 and 6, when the receiving unit 12 receives other information or the like, needless to say, the processing unit 14 or the like performs processing according to the other information or the like.

  Next, the classification process of step S502 will be described using the flowchart of FIG.

  (Step S701) The control unit 142 acquires the user position information of the user terminal 2 that has transmitted the dispatch instruction. Note that the user position information is included in, for example, a dispatch instruction.

  (Step S702) The control unit 142 determines whether priority information is included in the received dispatch instruction or the like. If priority information is included, the process goes to step S703, and if priority information is not included, the process goes to step S714. Here, it is assumed that the designation information is an example of priority information. The designation information includes information for identifying only the driver of the group with the highest priority.

  (Step S703) The control unit 142 substitutes 1 for a counter i.

  (Step S704) The control unit 142 determines whether or not there is a driver identifier corresponding to the i-th priority using the priority information. If there is a driver identifier corresponding to the i-th priority, the process goes to step S705, and if not, the process goes to step S713.

  (Step S705) The control unit 142 substitutes 1 for the counter j.

  (Step S706) The control unit 142 determines whether or not the j-th driver identifier exists among the driver identifiers corresponding to the i-th priority. If the j-th driver identifier exists, the process goes to step S707, and if not, the process goes to step S712.

  (Step S707) The control unit 142 acquires driver position information that is paired with the j-th driver identifier.

  (Step S708) The control unit 142 obtains relative position information, which is relative position information between the user and the j-th driver, from the user position information acquired in Step S701 and the driver position information acquired in Step S707. get.

  (Step S709) The control unit 142 determines whether or not the relative position information acquired in step S708 is close enough to satisfy a predetermined condition. If the condition is satisfied, the process goes to step S710. If the condition is not satisfied, the process goes to step S711.

  (Step S710) The control unit 142 temporarily stores the jth driver identifier in the storage unit 11 in association with the group ID (for example, i).

  (Step S711) The control unit 142 increments the counter j by 1. The process returns to step S706.

  (Step S712) The controller 142 increments the counter i by one. The process returns to step S704.

  (Step S713) The control unit 142 determines whether or not a driver not designated by the user can pick up and drop off. If the pick-up is possible, the process goes to step S714. Here, the case of returning to the higher-level processing is a case where a group is not configured, and a case where no driver goes to the user. Further, when going to step S714, the driver is classified based on the relative position information from the drivers not designated by the user. Note that a flag indicating whether or not a driver not designated by the user can pick up and drop off is included in the received dispatch instruction, for example.

  (Step S714) The control unit 142 performs general driver classification processing. Return to upper process. The general driver classification process will be described with reference to the flowchart of FIG. The general driver classification process is a process of grouping candidate drivers for transmitting an inquiry based on relative position information.

  Next, the general driver classification process of step S714 will be described using the flowchart of FIG.

  (Step S801) The control unit 142 substitutes 1 for a counter i.

  (Step S802) The control unit 142 determines whether there is an i-th unevaluated driver. If the i-th unevaluated driver exists, the process goes to step S803, and if it does not exist, the process returns to the upper process.

  (Step S803) The control unit 142 substitutes 1 for a counter j.

  (Step S804) The control unit 142 determines whether or not the j-th relative position condition exists in the storage unit 11. If the j-th relative position condition exists, the process goes to step S805; otherwise, the process goes to step S810.

  (Step S805) The control unit 142 acquires the driver position information of the i-th unevaluated driver.

  (Step S806) The control unit 142 calculates relative position information using the user position information and the driver position information acquired in step S805.

  (Step S807) The control unit 142 determines whether or not the relative position information calculated in step S806 satisfies the jth relative position condition. If the j-th relative position condition is satisfied, the process goes to step S808; otherwise, the process goes to step S809.

  (Step S808) The control unit 142 temporarily stores the driver identifier of the i-th unevaluated driver in the storage unit 11 in association with the group ID corresponding to j.

  (Step S809) The control unit 142 increments the counter j by 1. The process returns to step S804.

  (Step S810) The controller 142 increments the counter i by 1. The process returns to step S802.

  In the flowchart of FIG. 8, the control unit 142 may classify drivers using driver attribute values other than driver position information, such as driver evaluation. For example, the control unit 142 may determine two or more drivers that are close enough for the relative position information to satisfy a predetermined condition, and classify the drivers into two or more groups based on the driver evaluation. For example, the control unit 142 may classify drivers having a high driver evaluation (for example, a threshold value or more) into a first group and drivers having a low driver evaluation (for example, less than a threshold value) to a second group.

  Next, the operation of the user terminal 2 will be described using the flowchart of FIG.

  (Step S901) The dispatch instruction receiving unit 221 determines whether a dispatch instruction has been received. When the dispatch instruction is accepted, the process goes to step S902, and when the dispatch instruction is not accepted, the process goes to step S921.

  (Step S902) The user processing unit 24 constitutes a dispatch instruction to be transmitted. For example, the user processing unit 24 configures a vehicle dispatch instruction having a stored user identifier and the acquired user position information. In addition, the user processing unit 24 configures, for example, a vehicle allocation instruction having priority order information included in the vehicle allocation instruction received in step S901, a stored user identifier, and the acquired user position information. The dispatch instruction may include a flag. Such a flag is, for example, a flag indicating that an undesignated driver may arrive.

  (Step S903) The dispatch instruction transmitting unit 231 transmits the dispatch instruction configured in Step S902 to the matching device 1.

  (Step S904) The driver information receiving unit 251 determines whether or not the driver information has been received in response to the transmission of the dispatch instruction in step S903. If the driver information is received, the process goes to step S905. If the driver information is not received, the process goes to step S917.

  (Step S905) The map output unit 261 outputs a map using the map information in the map information storage unit 211.

  (Step S906) The driver attribute value output unit 262 outputs the driver attribute value (for example, driver photo) included in the driver information received in step S904 to the position specified by the driver position information on the map.

  (Step S907) The driver arrival detection unit 241 determines whether or not the driver has arrived. If it is determined that the driver has arrived, the process goes to step S908. If it is determined that the driver has not arrived, the process returns to step S907. The driver position information is continuously received until the driver arrives, and the driver attribute value output unit 262 uses the driver position information of the moving driver to identify the driver attribute value based on the driver position information on the map. It is preferable to output to the position to be performed.

  (Step S <b> 908) The display screen changing unit 243 obtains, from the user storage unit 21, screen information of a screen that changes after the driver arrives.

  (Step S909) The display screen changing unit 243 outputs a screen using the screen information acquired in step S908.

  (Step S910) The user processing unit 24 determines whether user position information has been acquired. If the user position information has been acquired, the process goes to step S911, and if not, the process returns to step S910.

  (Step S911) The user output unit 26 updates the screen based on the user position information acquired in Step S910.

  (Step S912) The destination arrival detection unit 242 determines whether or not the destination has been reached. If it is determined that it has arrived at the destination, the process goes to step S913. If it is not determined that it has arrived at the destination, the process returns to step S910.

  (Step S <b> 913) The display screen changing unit 243 acquires screen information of a screen that transitions after arrival at the destination from the user storage unit 21.

  (Step S914) The display screen changing unit 243 outputs a screen using the screen information acquired in step S914.

  (Step S915) The user receiving unit 22 determines whether an input has been received from the user. When the input is accepted, the process goes to step S916, and when the input is not accepted, the process returns to step S901.

  (Step S916) The user transmission unit 23 transmits the information received in Step S915 to the matching device 1. The process returns to step S901. Such information includes, for example, driver evaluation, a chip, a message, and the like.

  (Step S917) The user reception unit 25 determines whether or not information indicating that the vehicle cannot be allocated has been received. If the information indicating that the vehicle cannot be dispatched is received, the process goes to step S918; otherwise, the process goes to step S919. It is preferable that the information indicating that the vehicle cannot be dispatched includes reward information.

  (Step S918) The user output unit 26 outputs the information (for example, reward information) received in Step S917. The process returns to step S901.

  (Step S919) The user processing unit 24 determines whether or not user position information has been acquired. If the user position information has been acquired, the process goes to step S920, and if not, the process returns to step S904.

  (Step S920) The user transmission unit 23 transmits the user position information acquired in Step S919 to the matching device 1. The process returns to step S904.

  (Step S921) The destination receiving unit 222 determines whether or not a destination has been received. If the destination is accepted, the process goes to step S922. If the destination is not accepted, the process goes to step S923.

  (Step S922) The user processing unit 24 accumulates the destination accepted in Step S921. The process returns to step S901. The accepted destination and the accumulated destination may have different data structures.

  (Step S923) The user receiving unit 22 determines whether information, an instruction, or the like has been received. When information, an instruction, or the like is received, the process goes to step S924, and when information, an instruction, or the like is not received, the process returns to step S901.

  (Step S924) The user processing unit 24 performs processing according to the information, instructions, etc. received in Step S923. The process returns to step S901.

  In the flowchart of FIG. 9, the process is terminated by power-off or a process termination interrupt.

  Next, the operation of the driver terminal 3 will be described using the flowchart of FIG.

  (Step S1001) The driver receiving unit 35 determines whether or not an inquiry has been received from the matching device 1. If an inquiry has been received, the process goes to step S1002, and if no inquiry has been received, the process goes to step S1006.

  (Step S1002) The driver output unit 36 outputs a screen corresponding to the inquiry. In addition, this screen is a screen for inputting permission information etc., for example.

  (Step S1003) The driver reception unit 32 determines whether or not an input has been received. When the input is accepted, the process goes to step S1004, and when the input is not accepted, the process goes to step S1005.

  (Step S1004) The driver transmission unit 33 transmits the information input in Step S1003 to the matching device 1. The process returns to step S1001. Note that the input information is, for example, permission information.

  (Step S1005) The driver processing unit 34 determines whether or not a timeout has occurred. If timed out, the process returns to step S1001, and if not timed out, the process returns to step S1003.

  (Step S1006) The driver arrival detection unit 341 determines whether the driver has arrived at the user. If it has arrived, go to step S1007, and if it has not arrived, go to step S1011.

  (Step S <b> 1007) The display screen changing unit 343 acquires screen information of a screen to be output after the driver arrives at the user from the driver storage unit 31.

  (Step S1008) The driver output unit 36 outputs a screen using the screen information acquired in step S1007.

  (Step S1009) The driver receiving unit 32 determines whether or not an input has been received for the output screen. If an input is accepted, the process goes to step S1010. If no input is accepted, the process returns to step S1001.

  (Step S1010) The driver transmission unit 33 transmits the information received in step S1009 to the matching device 1. The process returns to step S1001.

  (Step S1011) The destination arrival detection unit 342 determines whether or not the destination has been reached. If it has arrived at the destination, it goes to step S1012. If it has not arrived, it goes to step S1016.

  (Step S <b> 1012) The display screen changing unit 343 acquires screen information of a screen to be output after arrival at the destination from the driver storage unit 31.

  (Step S1013) The driver output unit 36 outputs a screen using the screen information acquired in step S1012.

  (Step S1014) The driver receiving unit 32 determines whether or not an input has been received for the output screen. If the input is accepted, the process goes to step S1015. If the input is not accepted, the process returns to step S1001.

  (Step S1015) The driver transmission unit 33 transmits the information received in step S1009 to the matching device 1. The process returns to step S1001.

  (Step S1016) The driver processing unit 34 determines whether or not the driver position information has been acquired. If the driver position information is acquired, the process goes to step S1017. If the driver position information is not acquired, the process goes to step S1018.

(Step S1017) The driver transmission unit 33 transmits the driver position information acquired in step S1016. The transmission destination of the driver position information is usually the matching device 1. However, the transmission destination of the driver position information may be the user terminal 2.
In such a case, it is assumed that the driver terminal 3 receives and stores information (for example, an IP address) for communicating with the user terminal 2 via the matching device 1.

  (Step S1018) The driver reception unit 32 determines whether other information, instructions, and the like have been received. If any other information or instruction is accepted, the process goes to step S1019. If any other information or instruction is not accepted, the process returns to step S1001.

  (Step S1019) The driver processing unit 34 and the like perform processing according to other information, instructions, and the like received in step S1018. The process returns to step S1001.

  In the flowchart of FIG. 10, the process ends when the power is turned off or the process ends.

  Next, the operation of the registration terminal 4 will be described using the flowchart of FIG.

  (Step S1101) The registration receiving unit 42 determines whether partner registration information has been received. If the registration receiving unit 42 has received the partner registration information, the process proceeds to step S1102, and if not received, the process proceeds to step S1103.

  (Step S1102) The registration processing unit 44 configures partner registration information to be transmitted using the information received in Step S1101. Then, the registration transmission unit 43 transmits the configured partner registration information to the matching device 1. Then, it returns to step S301.

  (Step S1103) The registration receiving unit 42 determines whether driver registration information has been received. If the registration receiving unit 42 has received the driver registration information, the process proceeds to step S1104. If not received, the process returns to step S1101.

  (Step S1104) The registration processing unit 44 configures driver registration information to be transmitted using the information received in step S1103. The registration transmission unit 43 transmits the configured driver registration information to the matching device 1. Then, it returns to step S301.

  In the flowchart of FIG. 11, the process starts in response to power-on of the registration terminal 4 or activation of the program, and the process ends by interruption of power-off or process end. However, the trigger for starting or ending the process does not matter.

  Hereinafter, a specific operation of the information system A in the present embodiment will be described. Three specific examples will be described below. In addition, the following description can be variously changed and does not limit the present invention. In addition, explanations regarding the matters already described are omitted or simplified. Moreover, the conceptual diagram of the information system A is FIG.

  In specific example 1 and specific example 2, charging processing and distribution processing when a user uses a driver using partner information and driver information registered in matching device 1 from registration terminal 4 will be described. Specific example 1 is a case where the first distribution information and the second distribution information are managed separately. Specific example 2 is a case where the first distribution information and the second distribution information are managed in pairs.

  In specific example 3 to specific example 5, a process of matching a user and a driver with matching device 1 will be described. Specific example 3 is a case where the user specifies a driver. Specific example 4 is a case where the user does not specify a driver. Specific example 5 is a case where no driver was found.

  (Specific example 1)

  A driver information management table as shown in FIG. 12 is stored in the driver information storage unit 111 of the matching device 1. Here, the driver information management table stores a large amount of driver information. FIG. 12 is a data structure diagram of driver information in the first specific example. The driver information includes a driver identifier, a partner identifier, first distribution information, and the like.

  Each driver information in the driver information management is associated with an ID (1, 2,... In this example). For example, driver information associated with ID “1” (hereinafter sometimes referred to as “driver information 1”) has a driver identifier “AA1”, a partner identifier “P1”, and first distribution information “5: 5”. . Further, for example, the driver information 3 associated with the ID “3” has a driver identifier “BB1”, a partner identifier “P1”, and first distribution information “7: 3”. That is, the first distribution information for the driver “AA1, AA2...” Is “5: 5”, the first distribution information for the driver “BB1...” Is “7: 3”, and the same partner “P1. The distribution ratio may vary depending on the driver. The first distribution information “7: 3” indicates that the obtained profit is distributed between the driver and the partner at 7: 3.

  The partner information storage unit 110 stores a partner information management table as shown in FIG. Here, two or more pieces of partner information are stored in the driver information management table. FIG. 13 is a data structure diagram of partner information in the first specific example. The partner information includes a partner identifier and second distribution information.

  Each partner information in the partner information management table is associated with an ID (1, 2,... In this example). For example, partner information associated with ID “1” (hereinafter may be referred to as partner information 1) includes partner identifier “P1”, second distribution information “4: 3”, and the like. Further, the partner information (partner information 2) associated with the ID “2” includes a partner identifier “P2”, second distribution information “2: 1”, and the like. The second distribution information “4: 3” indicates that the obtained profit is distributed at 4: 3 between the partner and the operating company of the matching device 1.

  Moreover, the information of FIG. 12, FIG. 13 is accumulate | stored as follows, for example. For example, it is assumed that a user of the registration terminal 4 (hereinafter referred to as an administrator) has input partner registration information to the registration terminal 4. Such partner registration information includes partner information to be registered and one or more driver information.

  Then, the driver registration receiving unit 42 receives partner registration information. Next, the registration process part 44 comprises the partner registration information to transmit using the received partner registration information. Then, the registration transmission unit 43 transmits the configured partner registration information to the matching device 1. The transmitted partner registration information is, for example, the partner registration information in FIG.

  Next, the receiving unit 13 of the matching device 1 receives the partner registration information of FIG. And the partner registration part 147 acquires partner information "<partner information ID = P1 2nd distribution information = 4: 3>" from the partner registration information which the reception part 13 received, and uses this information, partner information is obtained. Accumulate in the partner information storage unit 110. Such information is the record of “ID = 1” in FIG.

  In addition, the partner registration unit 147 acquires one or more pieces of driver information included in the partner registration information received by the reception unit 13 and uses the one or more pieces of driver information to store the one or more pieces of driver information in the driver information storage unit 111. accumulate. Such information is the record of “ID = 1, 2, 3, etc.” in FIG.

  As described above, using the received partner registration information, partner information and one or more driver information are collectively stored.

  In this situation, it is assumed that the user has taken the taxi of driver BB1 and arrived at the destination. Then, it is assumed that the destination arrival detection unit 342 of the driver terminal 3 detects arrival at the destination. Next, it is assumed that the driver processing unit 34 of the driver terminal 3 has acquired a fee of 1000 yen displayed on the taxi meter. Next, the driver processing unit 34 configures charging information “<driver identifier> BB1 <charge> 1000 yen” to be transmitted from the driver identifier “BB1” stored in the driver storage unit 31 and the charge “1000 yen”. To do. Next, the driver transmission unit 33 transmits the charging information to the matching device 1.

  Next, the receiving unit 12 of the matching device 1 receives the billing information “<driver identifier> BB1 <charge> 1000 yen”. Then, the distribution processing unit 146 acquires the first distribution information “7: 3” corresponding to <driver identifier> BB1 from the driver information management table of FIG. Then, the distribution processing unit 146 uses the first distribution information “7: 3” to calculate a share of 700 yen for the driver identified by the driver identifier “BB1”. The distribution processing unit 146 calculates “1000 yen × (7 / (7 + 3)) = 700 yen”. Next, the distribution processing unit 146 acquires the partner identifier “P1” corresponding to <driver identifier> BB1 from the driver information management table of FIG. Further, the distribution processing unit 146 calculates “300 yen (1000 yen-700 yen)” for the distribution of the partner identifier “P1”. Next, the distribution processing unit 146 acquires the second distribution information “4: 3” paired with the partner identifier “P1” from the partner information management table of FIG. Next, the distribution processing unit 146 calculates the share of the partner by “300 yen × 4 / (4 + 3)? 171”, and calculates the share of the operating company by “300 yen × 3 / (4 + 3)? 129”. Then, the distribution processing unit 146 accumulates “700 yen” in association with <driver identifier> BB1, accumulates “171 yen” in association with the partner identifier “P1,” and associates it with the identifier of the operating company. Accumulate “129 yen”.

  FIG. 15 is a conceptual diagram of a platform realized using the information system A. The platform is managed by three tiers: a first tier “operating company”, a second tier “partner”, and a third tier “driver”. A company that belongs to the first hierarchy “operating company” is the operating entity of the matching device 1. A plurality of partners such as a partner P1 that supervises the driver AA1, the driver BBn, and a partner P2 that supervises the driver CC1, the driver DDn, and the like belong to the second-tier “partner”.

  Partners P1 and P2 can participate in information system A as partners while operating their own matching devices. In addition, a partner P3 currently operating another matching device independently can also participate in the present system including the matching device 1 later.

  By using the matching device 1, the user can make a reservation seamlessly at any station belonging to any partner. However, since the partner-specific matching device is also functioning, the user has the option of requesting a desired driver to pick up a vehicle through the partner-specific matching device.

  In this example, the driver is under one of the partners, but an independent driver who does not belong to any partner can easily participate in the information system A as an administrator.

  (Specific example 2)

  The difference from Example 1 is only the data structure of partner information and driver information.

  The partner information storage unit 110 stores two or more pieces of partner information as shown in FIG. FIG. 16 is a data structure diagram of partner information in the second specific example. The partner information includes a partner identifier, one or more driver identifiers, first distribution information, and second distribution information.

  Each of the stored two or more partner information is associated with ID (1, 2,...). For example, the partner information (partner information 1) associated with the ID “1” is the partner identifier “P1”, two or more driver identifiers “AA1”, “AA2”,..., “BB1”. First distribution information “5: 5”, “7: 3”, second distribution information “4: 3”, and the like. Of the two first distribution information, the former first distribution information “5: 5” is associated with the driver identifier “AA1”, and the latter first distribution information “7: 3” is the driver identifier “. It corresponds to BB ".

  The partner information (partner information 2) associated with the ID “2” includes the partner identifier “P2”, the two driver identifiers “CC” and “DD”, and the two first distribution information “5: 5” and “5”. : 5 "and second distribution information" 2: 1 ".

  That is, in the above-described specific example 1, the partner information and the driver information are associated with each other via the partner identifier. However, in this specific example 2, both are directly associated with each other.

  In the example 1 platform, a driver who does not belong to any partner can easily participate as an administrator. However, in the example 2 platform, both the first and second distribution information are included in the driver information. As such, such drivers will typically participate through partners.

  Similarly to the first specific example, when the administrator inputs the partner registration information in FIG. 14 to the registration terminal 4, the record of “ID = 1” in FIG. 16 is registered in the matching device 1. .

In the matching device 1, the procedure until the driver is picked up is not limited to the procedure of Specific Example 3 to Specific Example 5 below. The matching device 1 may be configured such that the user simply requests a pick-up, one driver is selected, and the driver goes to the user.
(Premise of specific example 3 to specific example 5)

  Now, a driver information management table shown in FIG. 17 is stored in the driver information storage unit 111 of the matching device 1. The driver information management table is a table for managing one or more driver information. The driver information management table includes one or more records having “driver identifier”, “name”, “age”, “driver evaluation”, and “driver photograph”. The driver evaluation is, for example, an average value of driver evaluations transmitted from one or more user terminals 2. Here, the driver evaluation is a value of 1 to 5.

  The user information storage unit 112 stores a user information management table shown in FIG. The user information management table is a table for managing one or more user information. The user information management table includes one or more records having “user identifier”, “name”, “age”, “credit card number”, and “user evaluation”. The user evaluation is an average value of user evaluations transmitted from one or more driver terminals 3, for example. Moreover, user evaluation is a value of 1-5 here.

  Further, the reward information storage unit 113 stores a reward information management table shown in FIG. The reward information management table is a table for managing reward information of one or more users. The reward information management table has one or more records having “user identifier” and “reward information”. The reward information here is a point.

  Further, the storage unit 11 stores a relative position condition management table shown in FIG. The relative position condition management table is a table that manages the relative position conditions when the drivers are classified based on the relative position information. The relative position condition management table includes one or more records having “group ID” and “relative position condition”.

In this situation, the following specific examples 3 to 5 will be described.
(Specific example 3)

  Now, it is assumed that the user inputs an instruction for starting a taxi pick-up app installed in the user terminal 2 to the user terminal 2. Then, the user reception unit 22 receives an application activation instruction. Next, the user process part 24 starts an application and acquires user position information. Next, the user output unit 26 transmits user position information to the matching device 1.

  Next, the receiving unit 12 of the matching device 1 receives user position information. Then, the processing unit 14 acquires the driver information identified by the driver identifier paired with the user position indicated by the user position information and the driver position information that is close enough to satisfy a predetermined condition from the driver information management table of FIG. To do. The storage unit 11 stores a driver identifier and driver position information in association with each other. In addition, the driver identifier and the driver position information are always transmitted from the driver terminal 3 to the matching device 1. Next, the driver information transmission unit 152 transmits the acquired driver information to the user terminal 2 that has transmitted the user position information. Here, it is assumed that driver information for 15 people has been transmitted.

  Then, the driver information receiving unit 251 of the user terminal 2 receives driver information. Here, it is assumed that the driver information includes driver position information.

  And the map output part 261 reads the map information according to the position which user position information shows from the map information storage part 211, and displays a map. Next, the driver attribute value output unit 262 displays at least a part of the received driver information at a position on the map indicated by the driver position information of the received driver information. A display example of such a screen is shown in FIG. In FIG. 21, reference numeral 1301 denotes a position indicated by the user position information. Three 1302 are displayed driver information. Then, it is assumed that the user has pressed 1303 in FIG.

  Then, the user terminal 2 outputs the screen of FIG. It is assumed that screen information constituting the screen of FIG. 22 is linked to 1301.

  Next, it is assumed that the user inputs the getting-off position “00 ward △ Δ town □□ 0-0-0” in the “input getting-off position” field 1401 in FIG. Then, the destination reception unit 222 receives the destination “00 ward ΔΔ town □□ 0-0-0”. Next, the user transmission unit 23 transmits the accepted destination to the matching device 1.

  The receiving unit 12 of the matching device 1 receives the destination “00 ward ΔΔ town □□ 0-0-0”. Next, the processing unit 14 determines whether or not the destination “00 ward ΔΔ town □□ 0-0-0” is a place where a taxi is likely to stop. That is, the storage unit 11 stores one or more pieces of position information for specifying a place where the taxi is likely to stop, and the processing unit 14 determines that the destination is not a place where the taxi is likely to stop. And the one or more pieces of position information, the position information indicating the point where the taxi is likely to stop is acquired so as to be a point that satisfies a destination and a predetermined condition. Next, the transmission unit 15 transmits to the user terminal 2 stop inappropriate information that is information including the acquired position information and is information indicating that the destination is not a place where a taxi is likely to stop.

  Next, the user receiving unit 25 of the user terminal 2 receives stop inappropriate information. Then, in response to the reception of the inappropriate stop information, the user processing unit 24 reads screen information for the inappropriate stop information from the user storage unit 21, and the user output unit 26 outputs the screen shown in FIG. In FIG. 23, it is preferable to clearly indicate a place where the taxi is likely to stop using the received position information.

  Next, it is assumed that the user presses the completion button 1501 in FIG. Then, the user processing unit 24 reads screen information linked to the completion button 1501 from the user storage unit 21, and the user output unit 26 outputs the screen of FIG. 24 using the screen information.

  Next, it is assumed that the user presses a button 1601 in FIG. Then, the user reception unit 22 receives an instruction for the button 1601, and the user processing unit 24 reads screen information linked to the button 1601. Then, the user processing unit 24 applies the already received driver information for 15 persons to the read screen information, and configures an output screen. Next, the user output unit 26 displays the screen shown in FIG. Then, the user inputs a check in the menu item of 3 drivers out of 15 drivers (see 1701), and “If the selected driver does not approve the request, the request is also sent to the corresponding nearby driver. It is assumed that a check is also input to the “throw” item (see 1702). It is assumed that the user presses a button 1703.

  Then, the user reception unit 22 receives a check on the menu items of the three drivers, a check on the item “send a request to a nearby driver”, and a press on the button 1703.

  Note that the user output unit 26 may output the screen of FIG. 26 instead of the screen of FIG. In FIG. 26, 1801 represents the position indicated by the user position information on the map. In FIG. 26, the driver information of the driver who is close to the position indicated by the user position information is output in association with the position indicated by the driver position information (see 1802). When the user presses the button 1803, the same processing as when the button 1703 in FIG. 25 is pressed is performed.

  Then, the user processing unit 24 acquires the driver identifiers of the three drivers corresponding to the checked menu item. In addition, the user processing unit 24 acquires a flag “1” corresponding to the item “throw a request to a nearby driver”. And the user process part 24 comprises the dispatch instruction to transmit. The dispatch instruction includes a driver identifier (for example, D001, D002, D003) of each of the three drivers and a flag “1”. In addition, it is preferable that the dispatch instruction includes a user identifier, user position information, and the like.

  Next, the dispatch instruction transmission unit 231 transmits the dispatch instruction to the matching device 1. Here, the user processing unit 24 may acquire priority order information that identifies the order of the checked drivers. In this case, for example, the priority order information is “1: D001, 2: D002, 3: D003”. It is assumed that the user inputs checks in the order of drivers D001, D002, and D003.

  Next, the dispatch instruction receiving unit 121 of the matching device 1 receives the dispatch instruction from the user terminal 2.

  Next, the control unit 142 classifies two or more drivers in response to reception of a dispatch instruction or the like. That is, the control unit 142 sets the three driver identifiers “D001, D002, D003” included in the dispatch instruction as the first group. Next, the control unit 142 sets a driver identifier satisfying “relative position information <= 300 m” of the group ID = “1” illustrated in FIG. 20 as the second group. Further, the control unit 142 sets a driver identifier satisfying “300 m <relative position information <= 600 m” of the group ID = “2” illustrated in FIG. 20 as the third group. Further, the control unit 142 sets a driver identifier satisfying “600 m <relative position information <= 1 km” of the group ID = “2” illustrated in FIG. 20 as the fourth group. That is, the control unit 142 uses the user position information and the driver position information of each driver to acquire relative position information that is a distance between the two points (a linear distance or a distance on the route). Then, the control unit 142 associates the driver identifier paired with the driver position information whose relative position information matches the relative position condition of the group ID “1” with the group ID of the second group, and the relative position information is the group ID. The driver identifier paired with the driver position information that matches the relative position condition of the ID “2” is associated with the group ID of the third group, and the relative position information matches the relative position condition of the group ID “3”. The driver identifier paired with the driver position information is associated with the group ID of the fourth group. The control unit 142 temporarily accumulates the driver classification information illustrated in FIG. 27 in the storage unit 11.

  Next, the inquiry transmission unit 151 acquires three driver identifiers “D001, D002, D003” associated with the first group (G1). Then, the inquiry transmission unit 151 transmits an inquiry to the driver terminal 3 identified by the three driver identifiers. The processing unit 14 obtains user information such as a user identifier included in the dispatch instruction and a name paired with the user identifier from the user information storage unit 112, and forms a query including the user information such as the user identifier and the name. The inquiry transmission unit 151 preferably transmits the inquiry to the driver terminal 3 identified by each driver identifier.

  Next, the driver receivers 35 of the three driver terminals 3 identified by the driver identifiers “D001, D002, D003” receive the inquiry from the matching device 1. Next, the driver output unit 36 outputs a screen corresponding to the inquiry.

  It is assumed that the driver identified by the driver identifier “D001” among the three drivers inputs permission information to the screen. Note that the input of permission information is, for example, pressing of a “permission” button. Then, the driver reception unit 32 receives permission information indicating permission. Then, the driver transmission unit 33 transmits the permission information and the driver identifier “D001” to the matching device 1.

  Next, the license information receiving unit 122 of the matching device 1 receives the license information from the driver terminal 3 identified by the driver identifier “D001”.

  Next, the processing unit 14 displays at least a part of driver information (for example, name and driver photo) of the driver information paired with the driver identifier “D001” received together with the permission information indicating permission. Obtained from 17 driver management tables. Note that it is preferable that the processing unit 14 obtains a driver photo only when it is determined that the driver identifier “D001” transmitted in pair with the permission information is the driver identifier of the driver selected by the user. That is, when the processing unit 14 determines that the driver identifier “D001” transmitted in pair with the license information is not the driver identifier of the driver selected by the user, the processing unit 14 does not acquire the driver photo or acquire the driver information at all. That is preferred.

  Next, the driver information transmission unit 152 transmits the acquired driver information to the user terminal 2 that has transmitted the dispatch instruction.

  Next, the driver information receiving unit 251 of the user terminal 2 receives the driver information in response to the transmission of the dispatch instruction. Next, the map output unit 261 outputs a map using the map information in the map information storage unit 211. Further, the driver attribute value output unit 262 outputs the driver attribute value included in the received driver information to the position specified by the driver position information on the map.

  Until the driver arrives at the user, the driver information receiving unit 251 receives the driver position information of the driver terminal 3 that transmitted the permission information, and the driver attribute value output unit 262 displays the driver attribute value on the map. Is displayed according to the driver position information.

  Next, the driver arrival detection unit 241 detects that the position indicated by the acquired user position information and the position indicated by the received driver position information are close enough to satisfy a predetermined condition, and determines that the driver has arrived. .

  Next, the display screen changing unit 243 obtains screen information of the screen that transitions after the driver arrives from the user storage unit 21. Then, the display screen change unit 243 outputs a screen using the acquired screen information. In addition, this screen is a screen which guides to the destination, for example. That is, the user processing unit 24 searches for a route using the accepted destination and the user position information, and acquires route information from the current location to the destination. And the user process part 24 comprises the map information which specified the path | route which the said path | route information shows. And the display screen change part 243 outputs the map in which the route was specified using this map information.

  In addition, the driver processing unit 34 of the driver terminal 3 detects that the driver has arrived at the user, and acquires corresponding screen information from the driver storage unit 31. Then, the driver output unit 36 outputs a screen using the acquired screen information.

  Next, on the user terminal 2, as the taxi moves, the map display changes so that the current position moves on the map.

  Then, the destination arrival detection unit 242 of the user terminal 2 determines that the user has arrived at the destination using the user position information and the destination information.

  Next, the display screen changing unit 243 acquires screen information of a screen that transitions after arrival at the destination from the user storage unit 21. Then, the display screen change unit 243 outputs a screen using the acquired screen information. It is assumed that this screen is a screen for inputting a driver evaluation and / or a message.

  Next, it is assumed that the user inputs a driver evaluation and a message on the displayed screen. Then, the user reception part 22 receives an input from a user. Next, the user transmission unit 23 transmits the driver identifier and the received driver evaluation and message together with the user identifier to the matching device 1.

  Next, the receiving unit 12 of the matching device 1 receives the driver identifier, driver evaluation, message, and user identifier. Then, the processing unit 14 accumulates the driver evaluation and the message in the storage unit 11 in a pair with the driver identifier. The processing unit 14 may accumulate such information in pairs with the user identifier.

  The driver processing unit 34 of the driver terminal 3 detects arrival at the destination and acquires corresponding screen information from the driver storage unit 31. Then, the driver output unit 36 outputs a screen using the acquired screen information.

  Then, it is assumed that the driver inputs user evaluation for the screen. Then, the driver receiving unit 32 receives a user evaluation for the output screen. Next, the driver transmission unit 33 transmits the received user evaluation, user identifier, and driver identifier to the matching device 1.

Next, the receiving unit 12 of the matching device 1 receives the driver identifier, the user evaluation, and the user identifier. Then, the processing unit 14 accumulates such information in the storage unit 11.
(Specific example 4)

  Assume that the user presses the button 1602 in the situation where the screen of FIG. 24 is displayed on the user terminal 2. Then, the user accepting unit 22 of the user terminal 2 accepts pressing of the button 1602.

  Next, the user processing unit 24 reads screen information linked to the button 1602 from the user storage unit 21. Then, the user output unit 26 outputs the screen shown in FIG. 28 using the screen information. Such a screen is a screen requesting approval to throw a request to all nearby drivers.

  Then, it is assumed that the user has pressed the “Yes” button. Then, the dispatch instruction receiving unit 221 of the user terminal 2 receives the dispatch instruction. The dispatch instruction does not have a driver identifier.

  Next, the user processing unit 24 constitutes a dispatch instruction to be transmitted. That is, the user processing unit 24 constitutes a vehicle dispatch instruction having the stored user identifier and the acquired user position information. Then, the vehicle allocation instruction transmission unit 231 transmits the configured vehicle allocation instruction to the matching device 1.

  Next, the dispatch instruction receiving unit 121 of the matching device 1 receives the dispatch instruction from the user terminal 2.

  Next, the control part 142 detects the driver which belongs to three groups using the relative position conditions of FIG. 20, according to reception of a dispatch instruction | indication. This detection method is the same as the processing described in the first specific example. Then, it is assumed that the control unit 142 temporarily accumulates the driver classification information illustrated in FIG. 29 in the storage unit 11.

  Next, the inquiry transmission unit 151 acquires four driver identifiers “D001, D002, D018, D017” associated with the first group (ID = 1). Then, the inquiry transmission unit 151 transmits an inquiry to the driver terminal 3 identified by each of the four driver identifiers.

  Next, the driver receiving units 35 of the four driver terminals 3 identified by the driver identifiers “D001, D002, D018, D017” receive the inquiry from the matching device 1. Next, the driver output unit 36 outputs a screen corresponding to the inquiry.

  However, it is assumed that any of the four drivers is difficult to pick up and does not input any information within a predetermined time, or inputs that the pick-up is “impossible”.

  Then, the inquiry transmission unit 151 of the matching device 1 acquires four driver identifiers “D003, D201, D004, D008” associated with the second group (ID = 2).

  Then, the inquiry transmission unit 151 transmits an inquiry to the driver terminal 3 identified by each of the four driver identifiers.

  Next, the driver receivers 35 of the four driver terminals 3 identified by the driver identifiers “D003, D201, D004, D008” receive the inquiry from the matching device 1. Next, the driver output unit 36 outputs a screen corresponding to the inquiry.

  However, it is assumed that any of the four drivers is difficult to pick up and does not input any information within a predetermined time, or inputs that the pick-up is “impossible”.

  Next, the inquiry transmission unit 151 of the matching device 1 acquires the driver identifier “D105” associated with the third group (ID = 3).

  Then, the inquiry transmission unit 151 transmits an inquiry to the driver terminal 3 identified by the driver identifier “D105”.

  Next, the driver receiving unit 35 of the driver terminal 3 identified by the driver identifier “D105” receives an inquiry from the matching device 1. Next, the driver output unit 36 outputs a screen corresponding to the inquiry.

  It is assumed that the driver identified by the driver identifier “D105” has input permission information indicating permission to the screen. Then, the driver reception unit 32 receives the permission information. Then, the driver transmission unit 33 transmits the permission information and the driver identifier “D105” to the matching device 1.

  Next, the permission information receiving unit 122 of the matching device 1 receives permission information indicating permission from the driver terminal 3 identified by the driver identifier “D105”.

  Next, the processing unit 14 acquires driver position information paired with the driver identifier “D105” received together with the permission information.

  Next, the driver information transmitting unit 152 transmits the acquired driver position information to the user terminal 2 that has transmitted the dispatch instruction.

Next, the driver information receiving unit 251 of the user terminal 2 receives the driver position information in response to the transmission of the dispatch instruction. Next, the map output unit 261 outputs the map information stored in the map information storage unit 211 in a manner that clearly indicates the map.
(Specific example 5)

  In the specific example 3 and the specific example 4, the dispatch instruction is transmitted to the driver terminals 3 of all the groups, but the permission information indicating the permission cannot be received from all the driver terminals 3 within a predetermined time. To do. In such a case, the reward information storage unit 143 acquires reward information to be given to the user who has transmitted the dispatch instruction. Here, it is assumed that the reward information is a default value of 100 points. It is assumed that this reward information is stored in the storage unit 11.

  Next, the reward information storage unit 143 of the matching device 1 stores the reward information “100 points” in the reward information storage unit 113 in association with the user identifier that identifies the user who has transmitted the dispatch instruction.

  And the transmission part 15 transmits that the reward information "100 points" was provided to the user terminal 2 which has transmitted the dispatch instruction.

  Next, the user receiving unit 25 of the user terminal 2 receives information indicating that reward information “100 points” has been given. Then, the user output unit 26 displays a screen including such information. An example of such a screen is shown in FIG.

  As described above, according to the present embodiment, it is possible to provide a platform capable of seamlessly requesting a plurality of drivers managed and controlled by a plurality of partners.

  In addition, the matching device 1 performs a charging process for charging the user for the use of the driver, and distributes the amount charged by the charging process among the driver, the partner, and the operating company of the matching device 1. By performing the distribution process for the above, the charged amount can be appropriately distributed in the platform.

  In addition, the matching device 1 can appropriately charge the platform by performing a charging process when a predetermined condition is satisfied.

  The partner information includes one or more pieces of distribution information among distribution information regarding distribution between the driver and the partner and distribution information regarding distribution between the partner and the management company of the matching device 1. By performing the distribution process using the distribution information included in the partner information, the amount can be distributed according to the distribution conditions for each partner.

  The driver information includes distribution information related to distribution between the driver and the partner, and the matching device 1 performs distribution processing using the distribution information included in the driver information, thereby complying with the distribution condition for each driver. In addition, the amount can be distributed.

  Further, the matching device 1 accepts partner registration information including partner information and one or more driver information corresponding to the partner information, accumulates the partner information included in the partner registration information in the partner information storage unit 110, and stores the partner registration information. The partner information and the like can be registered by storing one or more pieces of driver information included in the driver information storage unit 111.

  Further, according to the present embodiment, the driver information that comes to the user is output to the user's terminal, so that the user can request the driver to dispatch safely.

  In addition, according to the present embodiment, the transmission from the matching device 1 to the driver terminal 3 can be appropriately performed by the transmission control of the inquiry to the driver terminal 3.

  Moreover, according to this Embodiment, even when a driver cannot be dispatched, a user's satisfaction can be improved by giving a reward to a user.

  According to the present embodiment, after the driver arrives at the user, the user terminal 2 or the driver terminal 3 can switch to an appropriate screen.

  Moreover, according to this Embodiment, after arriving at the destination, the user terminal 2 or the driver terminal 3 can switch to an appropriate screen.

  Further, according to the present embodiment, the user can input the evaluation of the driver.

  Further, according to the present embodiment, the driver can input the user's evaluation.

  Moreover, according to this Embodiment, the route information which the user terminal 2 moved can be accumulate | stored in the user terminal 2, and the said route information can be reused.

  Furthermore, the processing in the present embodiment may be realized by software. Then, this software may be distributed by software download or the like. Further, this software may be recorded and distributed on a recording medium such as a CD-ROM. This also applies to other embodiments in this specification. Note that the software that implements the information processing apparatus according to the present embodiment is the following program. That is, this program is, for example, information on a driver, a driver information storage unit that stores two or more driver information having a driver identifier that identifies the driver, and information on a partner that manages the driver. A partner information storage unit storing two or more partner information having a partner identifier to be identified and one or more driver identifiers, and one or more having a user identifier for identifying a user who reserves a driver, which is information related to driver reservation. A computer accessible to a reservation information storage unit storing reservation information of the vehicle, a dispatch instruction receiving unit that receives a dispatch instruction from a user terminal, and configuring the reservation information in response to receiving the dispatch instruction, As a reservation information component that accumulates in the reservation information storage Is a program of the order to.

  Further, in the above program, a charge processing unit for performing charge processing for charging the user for driver reservation or use of the driver, an amount charged by the charge processing, the driver and the It is preferable that the program is to further function as a distribution processing unit that performs distribution processing for distribution between the partner and the operating company of the matching device.

  FIG. 31 shows the external appearance of a computer that executes the program described in this specification and realizes the matching device and the like of the various embodiments described above. The above-described embodiments can be realized by computer hardware and a computer program executed thereon. FIG. 31 is an overview diagram of the computer system 300, and FIG. 32 is a block diagram of the system 300.

  In FIG. 31, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

  32, in addition to the CD-ROM drive 3012, the computer 301 includes an MPU 3013, a bus 3014 connected to the MPU 3013 and the CD-ROM drive 3012, a ROM 3015 for storing programs such as a boot-up program, and an MPU 3013. And a RAM 3016 for temporarily storing instructions of the application program and providing a temporary storage space, and a hard disk 3017 for storing the application program, the system program, and data. Although not shown here, the computer 301 may further include a network card that provides connection to a LAN.

  A program that causes the computer system 300 to execute the functions of the matching device or the like of the above-described embodiment may be stored in the CD-ROM 3101, inserted into the CD-ROM drive 3012, and further transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored in the hard disk 3017. The program is loaded into the RAM 3016 at the time of execution. The program may be loaded directly from the CD-ROM 3101 or the network.

  The program does not necessarily include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the matching device according to the above-described embodiment. The program only needs to include an instruction portion that calls an appropriate function (module) in a controlled manner and obtains a desired result. How the computer system 300 operates is well known and will not be described in detail.

  In the above program, in the step of transmitting information, the step of receiving information, etc., processing performed by hardware, for example, processing performed by a modem or an interface card in the transmission step (only performed by hardware) Processing) is not included.

  Further, the computer that executes the program may be singular or plural. That is, centralized processing may be performed, or distributed processing may be performed.

  Further, in each of the above embodiments, it goes without saying that two or more communication units existing in one apparatus may be physically realized by one medium.

  In each of the above embodiments, each process may be realized by centralized processing by a single device, or may be realized by distributed processing by a plurality of devices.

  The present invention is not limited to the above-described embodiments, and various modifications are possible, and it goes without saying that these are also included in the scope of the present invention.

  As described above, the matching device according to the present invention has an effect of providing a platform capable of seamlessly reserving a plurality of drivers managed by partners who are a plurality of management organizations, and is useful as a matching device or the like.

DESCRIPTION OF SYMBOLS 1 Matching apparatus 2 User terminal 3 Driver terminal 4 Registration terminal 11 Storage part 12 Receiving part 13 Reception part 14 Processing part 15 Transmission part 21 User storage part 22 User reception part 23 Management output part 23 User transmission part 24 User processing part 25 User reception Unit 26 User output unit 31 Driver storage unit 32 Driver reception unit 33 Driver transmission unit 34 Driver processing unit 35 Driver reception unit 36 Driver output unit 41 Registration storage unit 42 Registration reception unit 42 Driver registration reception unit 43 Registration transmission unit 44 Registration processing unit 45 registration reception unit 46 registration output unit 110 partner information storage unit 111 driver information storage unit 112 user information storage unit 113 reward information storage unit 114 reservation information storage unit 121 dispatch instruction reception unit 122 license information reception unit 123 driver position information Information receiving unit 141 Attribute value acquiring unit 142 Control unit 143 Remuneration information storage unit 144 Reservation information configuration unit 145 Charging processing unit 146 Distribution processing unit 147 Partner registration unit 151 Inquiry transmission unit 152 Driver information transmission unit 153 User information transmission unit 211 Map Information storage unit 221 Vehicle allocation instruction reception unit 222 Destination reception unit 223 Driver evaluation reception unit 231 Vehicle allocation instruction transmission unit 232 Driver evaluation transmission unit 241, 341 Driver arrival detection unit 242, 342 Destination arrival detection unit 243, 343 Display screen change unit 251 Driver information receiving unit 261 Map output unit 262 Driver attribute value output unit

Claims (14)

A driver information storage unit for storing two or more pieces of driver information having information on the driver and having a driver identifier for identifying the driver;
A partner information storage unit that stores information on a partner that manages the driver, and stores two or more partner information having a partner identifier for identifying the partner and one or more driver identifiers;
A reservation information storage unit for storing one or more reservation information, which is information related to a driver reservation and includes a user identifier for identifying a user who reserves the driver;
A dispatch instruction receiving unit for receiving a dispatch instruction from the user terminal;
A matching apparatus comprising: a reservation information forming unit configured to store reservation information in the reservation information storage unit in response to receiving the dispatch instruction. A charging processing unit for performing a charging process for charging the user for driver reservation or use of the driver;
The matching apparatus according to claim 1, further comprising a distribution processing unit that performs a distribution process for distributing the amount charged by the charging process among the driver, the partner, and a management company of the matching apparatus. The partner information
1 or more distribution information among distribution information regarding distribution between the driver and the partner and distribution information regarding distribution between the partner and the matching device operating company,
The distribution processing unit includes:
The matching device according to claim 2, wherein distribution processing is performed using distribution information included in the partner information. The driver information is
Has distribution information on distribution between driver and partner,
The distribution processing unit includes:
4. The matching device according to claim 2, wherein distribution processing is performed using distribution information included in the driver information. A reception unit that receives partner registration information including partner information and one or more driver information corresponding to the partner information;
The partner registration part which accumulate | stores the partner information which the said partner registration information has in the said partner information storage part, and further accumulate | stores one or more driver information which the said partner registration information has in the said driver information storage part. The matching device according to claim 4. A user information storage unit for storing one or more pieces of user information, which is information related to a user and has a user identifier for identifying the user;
In response to receiving the dispatch instruction, an inquiry transmission unit that transmits to the driver terminal an inquiry for inquiring about one or more drivers about the possibility of pick-up;
A permission information receiving unit that receives permission information indicating permission from one driver terminal in response to transmission of the inquiry;
A driver information transmitting unit that transmits at least part of the driver information of the driver of the driver terminal that transmitted the permission information to the user terminal that transmitted the dispatch instruction in response to reception of the permission information; ,
The reservation information component is
6. The matching device according to claim 1, wherein reservation information is configured and stored in the reservation information storage unit in response to reception of the permission information. An attribute value acquisition unit for acquiring attribute values of two or more drivers;
The inquiry transmission unit
The matching apparatus according to claim 6, wherein the inquiry is transmitted to the driver terminals of the two or more drivers at different times according to the attribute values of the two or more drivers. The inquiry transmission unit
8. The matching apparatus according to claim 7, wherein when the reception of permission information for the transmitted inquiry satisfies a predetermined condition, the next inquiry is transmitted. The attribute value acquisition unit
Receives priority information indicating priority for two or more drivers,
The attribute value of each of the two or more drivers is
9. The matching apparatus according to claim 7, wherein the priority order is priority for two or more drivers indicated by the priority order information. The attribute value acquisition unit
Receives designation information indicating designation for one or more drivers,
The inquiry transmission unit
One or more drivers that do not correspond to the designation information when an inquiry is sent to a driver terminal of one or more drivers corresponding to the designation information, and reception of permission information for the sent inquiry satisfies a predetermined condition The matching device according to claim 7, wherein an inquiry is transmitted to the driver terminal. The dispatch instruction receiving unit
Also receiving user location information indicating the location of the user terminal,
A driver position information receiving unit for receiving one or more driver position information indicating the position of the driver terminal from one or more driver terminals;
The attribute value acquisition unit
11. The relative position information, which is an attribute value indicating a relative positional relationship between the user and the driver, is acquired based on the user position information and the one or more pieces of driver position information. The matching device according to item. Remuneration information storage unit in which remuneration information related to remuneration is stored in association with the user identifier;
A remuneration information accumulating unit that accumulates remuneration information in association with a user identifier of a user corresponding to the user terminal when the driver information transmission unit is unable to transmit permission information indicating that the driver information has been matched to the user terminal; The matching apparatus according to claim 6, further comprising: A driver information storage unit for storing two or more pieces of driver information having information on the driver and having a driver identifier for identifying the driver;
A partner information storage unit that stores information on a partner that manages the driver, and stores two or more partner information having a partner identifier for identifying the partner and one or more driver identifiers;
Information relating to driver reservation, which is realized by a reservation information storage unit in which one or more reservation information having a user identifier for identifying a user who reserves a driver is stored, a dispatch instruction receiving unit, and a reservation information configuration unit A matching method,
The dispatch instruction receiving unit receives a dispatch instruction from a user terminal, and a dispatch instruction receiving step;
A reservation method comprising: a reservation information forming step in which the reservation information forming unit forms reservation information in response to receiving the dispatch instruction and stores the reservation information in the reservation information storage unit. A driver information storage unit for storing two or more pieces of driver information having information on the driver and having a driver identifier for identifying the driver;
A partner information storage unit that stores information on a partner that manages the driver, and stores two or more partner information having a partner identifier for identifying the partner and one or more driver identifiers;
A computer accessible to a reservation information storage unit storing one or more reservation information having information about a driver reservation and having a user identifier for identifying a user who reserves the driver;
A dispatch instruction receiving unit for receiving a dispatch instruction from the user terminal;
A program for configuring reservation information in response to reception of the dispatch instruction and causing it to function as a reservation information configuration unit that accumulates in the reservation information storage unit.