Program and information processing method

Abstract

To provide a calculation server and a communication terminal that communicates with the calculation server, which calculate the shared ride distance and the proportion of the usage fee borne by users based on the distance traveled, without increasing the burden on users and drivers of paid vehicles. [Solution] The processing method of an information processing device that communicates with a first terminal of a first user and a second terminal of a second user riding in a vehicle involves transmitting information regarding the first fare to be borne by the first user to the first terminal and information regarding the second fare to be borne by the second user to the second terminal, based on first boarding location information based on wireless communication between the vehicle's electronic device and the first terminal, first disembarking location information based on the interruption of wireless communication between the electronic device and the first terminal, second boarding location information based on wireless communication between the electronic device and the second terminal, and second disembarking location information based on the interruption of wireless communication between the electronic device and the second terminal.

Description

Technical Field

[0001] The present invention relates to a settlement technology for multiple users who share a ride in a paid vehicle such as a taxi. In particular, the present invention relates to a technology for calculating the burden ratio of the usage fee for each user when the riding distances of multiple users who share a ride in a paid vehicle are different.

Background Art

[0002] Conventionally, as one means of transportation, a transportation means using a paid vehicle such as a taxi or a hire car has been used. Since the transportation means using the paid vehicle can provide a service according to the needs of each user, it is very convenient. However, the operating fee is higher than that of public transportation means such as trains and buses.

[0003] For paid vehicles such as taxis and hire cars, the usage fee per user can be kept low if as many users as possible share the ride. In particular, when multiple users move to the same destination, there is a high demand for sharing the paid vehicle.

[0004] In the method of sharing the above-mentioned paid vehicle, for example, as shown in Patent Document 1, a technology for calculating the fare for each of multiple users according to the boarding position and destination of the user transmitted from multiple users to the taxi driver or the taxi dispatching center has been developed. The boarding position and destination of multiple users are transmitted from multiple users to the taxi driver or the taxi dispatching center verbally or by input characters.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, according to the technology described in Patent Document 1, when a user communicates their pickup location and destination by text input, the user had to go through the trouble of setting the destination in advance and entering it in text. Also, when the pickup location and destination were communicated verbally to the taxi driver, the taxi driver had to communicate the pickup location and destination of each of the multiple users to the taxi dispatch center, which not only increased the burden on the driver but also posed a problem of inducing errors due to the driver's memory lapses. Furthermore, even if the route when sharing a ride was unnecessarily longer than the route when not sharing a ride, the share of the fare was simply determined according to each user's ride distance, resulting in a problem of not being able to split the fare fairly.

[0007] This invention has been made in view of such problems, and aims to provide a calculation server that calculates the shared ride section and the proportion of the usage fee borne by users according to the distance traveled, without increasing the burden on users and drivers of paid vehicles, and a communication terminal that communicates with the calculation server. [Means for solving the problem]

[0008] A server device according to one embodiment of the present invention includes: an identification information acquisition unit that acquires operation identification information that identifies the operation of a vehicle and user identification information that identifies multiple users riding in the operation; a location information identification unit that identifies the boarding location information and alighting location information of each of the multiple users based on the distance between the communication terminals of the multiple users and the vehicle; a storage unit that stores the operation identification information, user identification information, boarding location information, and alighting location information in association with each other; a ratio calculation unit that calculates the proportion of the amount that each of the multiple users should bear for the operation based on the boarding location information and alighting location information of the multiple users; and a fare calculation unit that calculates the amount that each of the multiple users should bear based on the ratio and the operation fare.

[0009] In another embodiment, the ratio calculation unit may calculate the ratio based on the distance traveled by each of the multiple users individually from the boarding location to the alighting location.

[0010] In another embodiment, the ratio calculation unit may calculate the ratio based on the actual distance traveled by each of the multiple users using their respective vehicles, or the actual travel time required for that distance.

[0011] In another embodiment, the location information identification unit may identify boarding location information and disembarking location information by short-range wireless communication between the communication terminal and the vehicle.

[0012] In another embodiment, the system may further include a notification unit that notifies the user terminal of the amount.

[0013] A communication terminal according to one embodiment of the present invention includes: an identification information receiving unit that receives operation identification information that identifies the operation of a vehicle to be operated in response to an operation request; a location information identification unit that identifies the user's boarding location information and alighting location information based on the distance between the communication terminal of the user riding in the vehicle and the vehicle; and a fare information receiving unit that receives the boarding location information, alighting location information, and the amount to be borne by the user calculated based on the operation fare.

[0014] In another embodiment, the location information identification unit may identify boarding location information and alighting location information through short-range wireless communication between the user's communication terminal and the vehicle.

[0015] In another embodiment, the system may further include a fare information receiving unit that receives fare information, including the fare, from a vehicle, and a fare information transmitting unit that transmits the fare information received by the fare information receiving unit to a calculation server. [Effects of the Invention]

[0016] According to the computing server, communication terminal, and program of the communication terminal according to the present invention, it is possible to calculate a carpooling section without increasing the burden on the user and the driver of the paid vehicle, and provide a computing server that calculates a burden ratio of the usage fee according to the riding distance of the user who uses carpooling and a communication terminal that communicates with the computing server.

Brief Description of the Drawings

[0017] [Figure 1] It is a diagram showing an overview of a carpooling fee calculation system according to an embodiment of the present invention. [Figure 2] It is a block diagram showing an overview of a carpooling fee calculation system according to an embodiment of the present invention. [Figure 3] It is a block diagram showing the hardware configuration of a computing server used in a carpooling fee calculation system according to an embodiment of the present invention. [Figure 4] It is a schematic diagram showing the hardware configuration of a communication terminal used in a carpooling fee calculation system according to an embodiment of the present invention. [Figure 5] It is a schematic diagram showing the hardware configuration of a vehicle used in a carpooling fee calculation system according to an embodiment of the present invention. [Figure 6] It is a block diagram showing the functional configuration of a computing server used in a carpooling fee calculation system according to an embodiment of the present invention. [Figure 7] It is a block diagram showing the functional configuration of a communication terminal used in a carpooling fee calculation system according to an embodiment of the present invention. [Figure 8] It is a block diagram showing the functional configuration of a communication terminal used in a carpooling fee calculation system according to an embodiment of the present invention. [Figure 9] It is a diagram showing the operation flow of a carpooling fee calculation system according to an embodiment of the present invention. [Figure 10] In the operation flow of a carpooling fee calculation system according to an embodiment of the present invention, it is a diagram showing an example of an interface displayed on a user terminal when a program of a carpooling support device is started. [Figure 11]In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of an interface displayed on a user terminal when the program of the carpool support device is started. [Figure 12] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of an interface for user registration. [Figure 13] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of an interface for user registration. [Figure 14] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of an interface for inputting the boarding position. [Figure 15] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of an interface for confirming consent to a user information request. [Figure 16] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of a screen display after transmitting a running request signal. [Figure 17] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of a screen display while waiting for a car. [Figure 18] In the operation flow of the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of a screen display when the vehicle arrives at the position of the user terminal. [Figure 19] It is a diagram showing an outline of a calculation method of a calculation server used in the carpool fare calculation system according to an embodiment of the present invention. [Figure 20] In the carpool fare calculation system according to an embodiment of the present invention, it is a diagram showing an example of a method for determining a user's boarding or alighting. [Figure 21] In the carpool fare calculation system according to a modification example of an embodiment of the present invention, it is a diagram showing an example of a method for determining a user's boarding or alighting. [Figure 22]This figure shows an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. [Figure 23] This figure shows an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. [Figure 24] This figure shows an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. [Figure 25] This figure shows an overview of the calculation method of the calculation server used in a ride fare calculation system according to a modified version of one embodiment of the present invention. [Figure 26] This figure shows an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. [Figure 27] This figure shows an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. [Figure 28] This is a block diagram showing the functional configuration of a communication terminal used in a ride fare calculation system according to one embodiment of the present invention. [Figure 29] This is a block diagram showing the functional configuration of a communication terminal used in a ride fare calculation system according to one embodiment of the present invention. [Modes for carrying out the invention]

[0018] The computing server, communication terminal, and communication terminal program according to the present invention will be described below with reference to the drawings. However, the computing server, communication terminal, and communication terminal program of the present invention can be implemented in many different forms and should not be interpreted as being limited to the embodiments described below. In the drawings referenced in this embodiment, the same parts or parts having similar functions are denoted by the same reference numerals, and repeated descriptions thereof are omitted.

[0019] Furthermore, in the following explanation, while it is the user who utilizes the paid vehicle, the user travels with their communication terminal (user terminal), so the two are not clearly distinguished. For example, when a user utilizes a paid vehicle, they possess a user terminal and use the vehicle, so it may be expressed as "the user terminal utilizes the paid vehicle." This has the same meaning as "the user who possesses the user terminal utilizes the paid vehicle." Similarly, when a user uses a vehicle arrangement service, it may be expressed as "the user terminal uses the service."

[0020] Furthermore, while embodiments of the present invention illustrate a ride-sharing fare calculation system using vehicles such as taxis and hired cars, where the fare varies depending on either the distance traveled, the duration of travel, or both, as an example of a vehicle, the invention is not limited to this. For example, it can also be applied to other operating vehicles such as ships, airplanes, and helicopters.

[0021] <Embodiment 1> A ride-sharing fare calculation system and a ride-sharing fare calculation system including a program for calculating ride-sharing fares according to Embodiment 1 of the present invention will be described in detail with reference to Figures 1 to 20.

[0022] [System Overview] Figure 1 is a diagram illustrating the overview of a ride-sharing fare calculation system according to one embodiment of the present invention. Figure 2 is a block diagram illustrating the overview of a ride-sharing fare calculation system according to one embodiment of the present invention. As shown in Figures 1 and 2, the ride-sharing fare calculation system 10 according to Embodiment 1 includes a calculation server 110, a booking server 120, and a social networking service (SNS) server 130 (hereinafter simply referred to as "SNS server 130"). As shown in Figure 1, the calculation server 110 and the SNS server 130 communicate with a plurality of user terminals 200A and 200B, and the booking server 120 communicates with a vehicle 300. Here, the vehicle 300 is the vehicle that received a ride request from user terminal 200A, and first boards user terminal 200A, then boards user terminal 200B, and proceeds to the destination with user terminals 200A and 200B riding together.

[0023] Here, unless specifically distinguished, user terminals 200A and 200B are simply referred to as user terminal 200. Furthermore, any multiple user terminals 200 can be communication terminals capable of connecting to the first network 101 shown in Figure 2, and each user terminal 200 may have different functions. User terminals 200 can include mobile phones, smartphones, tablet PCs, PDAs, personal computers, PHS phones, and the like.

[0024] The calculation server 110 is a server that calculates the proportion and amount of the fare that each of the multiple user terminals 200 should bear for the ride on the vehicle 300. Here, the calculation server 110 acquires operation identification information that identifies the operation of the vehicle 300 and user identification information that identifies the multiple users riding on the operation. Based on the distance between the user terminals 200, which are the communication terminals of the multiple users, and the vehicle 300, it identifies the boarding location information and alighting location information of each of the multiple users. The calculation server 110 stores the above operation identification information, user identification information, boarding location information, and alighting location information in association with each other. Based on the boarding location information and alighting location information of the multiple users, it calculates the proportion that each of the multiple users should bear for the operation, and calculates the amount that each of the multiple users should bear based on that proportion and the fare for the operation.

[0025] Here, operation identification information refers to identification information assigned to each of the multiple vehicles 300 for each fare run. Specific examples of operation identification information include order sheets issued for each fare run or operation logs for each fare run. User identification information refers to information that identifies user terminal 200A and user terminal 200B. Specific examples of user identification information include device-specific information possessed by each user terminal 200, and user IDs (IDentifiers) for services unique to user terminals 200A and 200B managed by the SNS server 130.

[0026] The dispatch server 120 is a server owned by the dispatch center that receives dispatch requests and issues dispatch instructions to the vehicle 300, and manages the location information and dispatch information of the vehicle 300. Here, dispatch information includes the dispatch identification information and dispatch charges mentioned above. User identification information may also be included in the dispatch information. The dispatch server 120 may manage the above dispatch information in an analog manner or in a digital manner. Analog management is a management method in which the driver of the vehicle 300 brings back an order sheet created for each dispatch of the vehicle 300 and a receipt for the dispatch charges recorded on the fare meter to the dispatch center, and a worker at the dispatch center stores the order sheet and receipt in the database of the dispatch server 120. On the other hand, digital management is a management method in which the dispatch identification information of the vehicle 300 corresponding to the order sheet and the dispatch charges corresponding to the receipt, or both, are transmitted wirelessly from the vehicle 300 to the dispatch server 120, and the information is stored in the database sequentially.

[0027] The SNS server 130 is a server that provides SNS services to user terminals 200 and manages personal information of users who own multiple user terminals 200 that subscribe to the SNS service (device-specific information of the user terminal, name, telephone number, credit card information, email address, address, age, gender, user ID, etc.).

[0028] Here, one or both of the multiple user terminals 200 and the vehicle 300 have location identification means. For example, the location identification means may be GPS (Global Positioning). The following can be used: In the shared ride fare calculation system 10, location information from multiple user terminals 200 is transmitted to the calculation server 110, and location information from the vehicle 300 is transmitted to the arrangement server 120. In addition, location information from the destination 400 is input by multiple user terminals 200, and location information from the user terminal 200 that input the location information is transmitted to the calculation server 110. In addition to GPS, another example of a location identification means is the use of short-range wireless communication. Details of short-range wireless communication will be explained in detail later.

[0029] In this embodiment, a configuration in which the computing server 110, the procurement server 120, and the SNS server 130 are separate servers is illustrated, but the configuration is not limited to this. For example, the computing server 110 may have functions that are possessed by one or both of the procurement server 120 and the SNS server 130. In other words, a single server may implement the functions of the computing server 110, the procurement server 120, and the SNS server 130.

[0030] Here, each user of the multiple user terminals 200 may be a user with whom a contactable interaction relationship, such as "following" or "friending," has been established in the SNS service managed by the SNS server 130. In other words, the multiple user terminals 200 have formed a contactable interaction relationship registered by at least one user in a predetermined service registered by the multiple user terminals 200. Here, a configuration in which multiple user terminals 200 have formed an interaction relationship has been illustrated, but the configuration is not limited to this. That is, the multiple user terminals 200 do not have to form such an interaction relationship. In that case, the SNS server 130 can be omitted in Figure 1.

[0031] Furthermore, each user of the multiple user terminals 200 may be a user with whom a "friend" relationship has been established in the SNS service managed by the SNS server 130. In other words, the multiple user terminals 200 have formed mutually approved communication relationships in a predetermined service registered by the multiple user terminals 200. A mutually approved communication relationship refers not merely to recognizing each other's existence, but to a relationship established, for example, when one user sends a request to establish a friendship relationship and the other user approves it. Here, a configuration in which multiple user terminals 200 have formed mutually approved communication relationships has been illustrated, but the system is not limited to this configuration. That is, in the ride-sharing fare calculation system 10, the multiple user terminals 200 do not have to form such communication relationships. In that case, the SNS server 130 can be omitted in Figure 1.

[0032] As shown in Figure 2, the computing server 110, the dispatch server 120, the SNS server 130, and the multiple user terminals 200 are connected to each other via the first network 101. The dispatch server 120 and the vehicles 300 are also connected to each other via the second network 102. Here, the computing server 110, the dispatch server 120, and the SNS server 130 each have databases (DBs) 115, 125, and 135, respectively. The first network 101 can be a general IP network. The second network 102 can be a taxi radio or a local network.

[0033] Here, the database 115 of the computing server 110 stores operation identification information, user identification information, and boarding and alighting location information for each of the multiple users. Furthermore, the operation identification information, user identification information, and boarding and alighting location information for each of the multiple users stored in the database 115 are all related to one another.

[0034] Furthermore, while Figure 2 illustrates a configuration in which the dispatch server 120 and the vehicle 300 are connected via the second network 102, the configuration is not limited to this, and for example, the vehicle 300 may be connected to the dispatch server 120 via the first network 101. Also, while Figure 2 illustrates a configuration in which the computing server 110, the dispatch server 120, and the SNS server 130 are directly connected to the databases 115, 125, and 135, the configuration is not limited to this, and for example, the databases 115, 125, and 135 may be connected to the first network 101. In other words, cloud computing, which stores data via the network, can be used instead of the databases 115, 125, and 135.

[0035] The database 115 connected to the computing server 110 or the database 135 connected to the SNS server 130 stores personal information of the user who owns each user terminal 200 (device-specific information, name, telephone number, credit card information, email address, address, age, gender, user ID), evaluation information of the user and vehicle 300 that owns the user terminal 200, road map information, and traffic congestion information. Here, each item included in the personal information of the user of the user terminal 200 is stored in relation to one another.

[0036] The database 125 connected to the dispatch server 120 stores information such as the vehicle type, vehicle number, driver information (name, mobile phone number, age, gender), actual vehicle status (vacant, out of service, picking up, departing, etc.), and location information of the vehicle 300.

[0037] The database 135 connected to the SNS server 130 stores user IDs of users who use the SNS service provided by the SNS server 130, device-specific information of the user's terminal, and a list of other users with whom the user has a relationship (friend list). Furthermore, if the SNS server 130 has a payment system within the SNS service, the database 135 may also store information registered in the payment system, such as credit card information.

[0038] [Hardware configuration of the computing server] Figure 3 is a block diagram showing the hardware configuration of a calculation server used in a ride fare calculation system according to one embodiment of the present invention. According to Figure 3, the calculation server 110 includes a control unit 111, a hard disk 112, and a communication unit 113.

[0039] The control unit 111 includes a central processing unit (CPU), registers, and memory. The control unit 111 executes programs stored in memory using the CPU and performs arithmetic processing in response to instruction signals from the user terminal 200.

[0040] The hard disk 112 is a storage device capable of storing large amounts of data, and it stores programs necessary for arithmetic processing, as well as temporarily saves information transmitted from the user terminal 200.

[0041] The communications unit 113 controls the transmission and reception of data via the first network 101 with the ordering server 120, the SNS server 130, and the user terminal 200.

[0042] Here, the storage device of the control unit 111 reads and stores the program necessary for arithmetic processing from the hard disk 112 as needed.

[0043] [User terminal hardware configuration] Figure 4 is a schematic diagram showing the hardware configuration of a communication terminal used in a ride-sharing fare calculation system according to one embodiment of the present invention. According to Figure 4, the user terminal 200, which is a communication terminal used in the ride-sharing fare calculation system 10, has a memory 205, a control unit 210, a short-range wireless communication unit 215, and a communication module 220 inside its main body. In addition, a display 230, operation buttons 240, a speaker 250, and a microphone 260 are provided on one side of the user terminal 200. Here, the display 230 may have a touch sensor, and the operation buttons 240 may not be provided. Also, if the user terminal 200 does not have a call function, the speaker 250 and microphone 260 may not be provided.

[0044] Memory 205 stores data such as programs for causing the user terminal 200 to perform specific functions, unique information of the user terminal 200, and personal information of the user held by the user terminal 200.

[0045] The control unit 210 includes an arithmetic unit such as a CPU and a memory device such as registers. The control unit 210 executes the program stored in the memory 205 using the CPU and implements various functions of the user terminal 200 in response to the instruction signals input by the user.

[0046] The short-range wireless communication unit 215 is a functional unit that performs short-range wireless communication using high-frequency radio waves ranging from megahertz to gigahertz, and can communicate within a range of several meters to tens of meters. Short-range wireless communication is a type of communication that receives radio waves emitted from a radio source and transmits various information such as the unique information of the communication device and the distance between the radio source and the communication device. Examples of short-range wireless communication include RFID (Radio Frequency Identifier) ​​and BLE (Bluetooth® Low Energy). In this short-range wireless communication, the short-range wireless communication unit 215 has an antenna that receives radio waves emitted from the radio source and a logic circuit that analyzes the received radio waves. Furthermore, the short-range wireless communication unit 215 may have a logic circuit that modulates the radio waves emitted from the radio source in order to transmit the unique information of the user terminal 200.

[0047] The communication module 220 includes an antenna, high-frequency circuits, and demodulation circuits for wirelessly transmitting and receiving signals. The communication module 220 is controlled by the control unit 210 to connect to the network and access the computing server 110.

[0048] The display 230 can use liquid crystal displays, organic EL displays, etc. The touch sensor can also be a resistive, capacitive, or optical sensor. The user operates the user terminal 200 according to the display instructions to perform various functions.

[0049] [Vehicle Hardware Configuration] Figure 5 is a schematic diagram showing the hardware configuration of a vehicle used in a ride-sharing fare calculation system according to one embodiment of the present invention. According to Figure 5, the vehicle 300 is equipped with a short-range wireless communication unit 320 inside the vehicle body 310. The short-range wireless communication unit 320 includes a radio wave source that emits radio waves used for short-range wireless communication. The short-range wireless communication unit 320 may also include a receiving unit that receives radio waves modulated by the short-range wireless communication unit 215 of the user terminal 200, and an analysis unit that analyzes unique information of the user terminal 200 from the modulated radio waves.

[0050] [Functional Configuration of the Computing Server] Figure 6 is a block diagram showing the functional configuration of a calculation server used in a ride-sharing fare calculation system according to one embodiment of the present invention. Figure 6 describes each functional block of the calculation server 110 in Figure 2 in more detail. According to Figure 6, the calculation server 110 has an identification information acquisition unit 170, a location information identification unit 172, a storage unit 174, a percentage calculation unit 176, a fare calculation unit 178, and a notification unit 180.

[0051] The identification information acquisition unit 170 acquires operation identification information and operation fees from the dispatch server 120. Here, as described above, the operation identification information is information that identifies the operation of vehicle 300, and may be transmitted wirelessly from vehicle 300, or it may be information based on an order sheet stored by a worker, or a combination of these. The identification information acquisition unit 170 also acquires user identification information from the user terminal 200. The user identification information is information that identifies multiple users who ride in the operation of vehicle 300. In the case of Figure 6, the identification information acquisition unit 170 acquires a user ID from the user terminal 200 as user identification information. Here, the identification information acquisition unit 170 may also acquire a user ID in the SNS service managed by the SNS server 130 as user identification information by communicating with the SNS server 130.

[0052] The location information identification unit 172 identifies the boarding location information and alighting location information for each of the user terminals 200 based on the distance between the user terminals 200 and the vehicle 300. The boarding location information and alighting location information may be identified by short-range wireless communication between the user terminals 200 and the vehicle 300, or based on information obtained by GPS.

[0053] The memory unit 174 stores operation identification information, user identification information, boarding location information, and alighting location information in association with each other. The above information is read from the database 115 connected to the computing server 110 and temporarily stored on the hard disk 112 of the computing server 110. However, the above information does not necessarily have to be stored on the hard disk 112. In other words, the above information is stored in association with each other in the database 115 connected to the computing server 110, and the computing server 110 may perform subsequent calculations by referring to the above information stored in the database 115.

[0054] The ratio calculation unit 176 calculates the proportion that each of the multiple users who own multiple user terminals 200 should bear for the operation of the vehicle 300, based on the boarding location information and alighting location information of each of the multiple user terminals 200. The specific calculation method of the ratio calculation unit 176 will be described later.

[0055] The fare calculation unit 178 calculates the amount that each of the multiple user terminals 200 should bear, based on the percentage calculated by the percentage calculation unit 176 and the operating fee for the operation of the vehicle 300.

[0056] The notification unit 180 notifies multiple user terminals 200 that used the ride-sharing service of the amount of the charge calculated by the fare calculation unit 178. In addition to the calculated amount of the charge, the notification unit 180 can also notify information such as the date and time of operation, user information (name, telephone number, address, etc.) of the user who used the ride-sharing service, each user's boarding and alighting locations, route, and payment status. When the notification unit 180 notifies users of map information such as the route, it can do so by displaying it on the user terminals 200 using a web view that processes the display of each location information. These calculation results and the data notified to the user terminals 200 are stored in the database 115. If the above information is notified to the user terminals 200 by another server or system, the calculation server 110 does not need to have the notification unit 180.

[0057] Although not shown in the diagram, the calculation server 110 may have a scheduling management unit in addition to the identification information acquisition unit 170, location information identification unit 172, storage unit 174, percentage calculation unit 176, fee calculation unit 178, and notification unit 180 described above.

[0058] The above-mentioned arrangement management unit submits a request for service to the arrangement server 120 when a user terminal 200 sends a service request in the shared fare calculation system 10. Here, the arrangement management unit may have a delay function so that it submits the request for service to the arrangement server 120 after a predetermined period has elapsed since the user terminal 200 sent the service request. The arrangement management unit can also accept cancellations of service requests from the user terminal 200 during the delay period. On the other hand, if the arrangement order is not canceled during the delay period, the arrangement management unit submits the request for service to the arrangement server 120.

[0059] Furthermore, the arrangement management unit may notify the user terminal 200 of its location information, the location information of the vehicle 300, the location information of the destination, and traffic congestion information while the vehicle 300 is being picked up. The arrangement management unit may also provide the user terminal 200 with a means to contact the vehicle 300 (by phone or message) while the vehicle 300 is being picked up. The arrangement management unit may also provide the user terminal 200 with a means to evaluate the vehicle 300 that it has used. Conversely, the arrangement management unit may also provide the vehicle 300 that a user terminal has used with a means to evaluate the user terminal 200 that it has used. These evaluation results are stored in the database 115. Based on these evaluation results, the priority of the vehicle 300 used by the user terminal 200, or the priority of the user terminal 200 providing the ride-sharing fare calculation system 10 service, may be changed.

[0060] [Functional configuration of the communication terminal requested for operation] Figure 7 is a block diagram showing the functional configuration of a communication terminal used in a ride-sharing fare calculation system according to one embodiment of the present invention. In Figure 7, the functional blocks of user terminal 200A of user A, who makes a ride request, are described in more detail. According to Figure 7, user terminal 200A, which makes a ride request, has a ride request signal transmission unit 270, an identification information receiving unit 272, a location information identification unit 274, and a fare information receiving unit 276.

[0061] The operation request signal transmission unit 270 transmits an operation request signal to the dispatch server 120 requesting the operation of vehicle 300. The identification information receiving unit 272 receives operation identification information from the dispatch server 120 that identifies the operation of vehicle 300 to be operated in accordance with the operation request transmitted by the operation request signal transmission unit 270. Here, as described above, the operation identification information may be an operation log for each chartered trip transmitted wirelessly from vehicle 300 to the dispatch server 120, or it may be information from an order sheet stored in the dispatch server 120 or database 125 by a worker. Alternatively, it may be a mixture of these.

[0062] The location information identification unit 274 identifies the boarding location information and alighting location information of the user terminal 200 based on the distance between the user terminal 200, which is riding in the vehicle 300 operated in accordance with the above operation request, and the vehicle 300. As will be described in detail later, the boarding location information and alighting location information may be information generated in response to a signal obtained from a short-range wireless communication unit that generates a signal when the distance between the user terminal 200 and the vehicle 300 falls below a predetermined distance, or it may be information obtained based on the distance between the location information of the user terminal 200 obtained by GPS or the like and the location information of the vehicle 300.

[0063] The fare information receiving unit 276 receives the boarding location information and alighting location information identified by the location information identification unit 274, as well as the amount that the user should pay, calculated based on the operating fare for the operation of the vehicle 300.

[0064] [Functional configuration of the communication terminals used on board] Figure 8 is a block diagram showing the functional configuration of a communication terminal used in a ride-sharing fare calculation system according to one embodiment of the present invention. In Figure 8, the functional blocks of user terminal 200B, which is a passenger in a vehicle 300 operated by user terminal 200A, are explained in more detail. According to Figure 8, the passenger user terminal 200B is similar in functional block to user terminal 200A of user A who makes the operation request, but user terminal 200B differs from user terminal 200A in that it does not have an operation request signal transmission unit 270.

[0065] Since the user terminal 200B does not need to make a request for service, it does not need to have the service request signal transmission unit 270 as described above. However, this does not mean that the user terminal 200B must not have the service request signal transmission unit 270. Of course, the user terminal 200B may have the service request signal transmission unit 270.

[0066] [Operation Flow of the Shared Ride Fare Calculation System] Figure 9 is a diagram showing the operation flow of a ride-sharing fare calculation system according to one embodiment of the present invention. In Figure 9, the operation of each block of the ride-sharing fare calculation system 10 shown in Figure 2 is explained in detail using a flowchart.

[0067] First, the user terminal 200A starts a program to operate the ride-sharing fare calculation system 10 (step S501). Here, an example of the interface displayed on the user terminal when the ride-sharing fare calculation system 10 program is started in step S501 is shown in Figures 10 and 11. The interface 610 shown in Figure 10 is the settings screen for the SNS service provided by the SNS server 130. As shown in Figure 10, the interface 610 has a vehicle icon 611, and the ride-sharing fare calculation system 10 program is started by selecting the vehicle icon 611. Here, the interface 610 has multiple tabs at the bottom of the screen, such as the friend list tab 612, the talk tab 613, the timeline tab 614, and the other tab 615. The tab that starts the ride-sharing fare calculation system 10 program may be placed on one of these multiple tabs.

[0068] Selecting the vehicle icon 611 on interface 610 displays interface 620 as shown in Figure 11. Interface 620 is the top screen of the shared ride fare calculation system 10. On interface 620, selecting the request button 621 allows the user terminal 200 to access the calculation server 110.

[0069] Here, when the shared fare calculation system 10 is used for the first time, the user registration interface 630 and the credit card information registration interface 631 shown in Figures 12 and 13 may be displayed. Interface 630 displays fields for entering the name and telephone number of the user terminal 200. Interface 631 displays fields for entering the credit card number, expiration date, and PIN.

[0070] Next, the user terminal 200A executes a request to operate the vehicle 300 (step S502). Here, an example of the interface displayed on the user terminal when making an operation request in step S502 is shown in Figure 14. The interface 640 shown in Figure 14 is a map displayed by the web view function. The user uses the user terminal 200 to select a boarding location 600 on the map. A boarding location pin 641 is displayed as a landmark at the selected boarding location 600. In addition, the boarding location address 642 is displayed above the boarding location pin 641. To set the selected boarding location 600, the user selects the setting button 643, and the location information of boarding location 600 is set as the boarding location on the user terminal 200A.

[0071] In Figure 14, the estimated travel time (15 mins) from the user terminal 200's current location to the boarding location 600 is displayed on the boarding location pin 641. Multiple vehicles 644 managed by the dispatch server 120 are also displayed on the map. The functions for displaying the boarding location address 642, the travel time to boarding location 600, or the vehicles 644 can be omitted and may be provided as optional functions.

[0072] Furthermore, in step S502, when the setting button 643 of the interface 640 shown in Figure 14 is selected, an interface 650 is provided to confirm consent to transmit the boarding location 600 and user terminal A information to the computing server 110, as shown in Figure 15 as an example. The interface 650 shown in Figure 15 is a map displayed by the web view function. In the map shown in Figure 15, a location information pin 652 is displayed at the boarding location 600 of user terminal 200A. When the consent button 657 is selected by user terminal 200A, the boarding location 600 is transmitted from user terminal 200A to the computing server 110.

[0073] Furthermore, the interface 650 shown in Figure 15 includes a user information confirmation field 653 displaying user information (name, telephone number, etc.) of the user terminal 200, a user registration credit card information field 654 displaying credit card information registered in the ride-sharing fare calculation system 10, a coupon code field 655 displaying information on coupons held by the user, a dispatch center information field 656 displaying information notified from the dispatch center to the user terminal, such as the dispatch fee, and a pick-up / drop-off information field 658 displaying the estimated pick-up time, etc. Here, the interface 650 only needs to have a function to confirm consent, and other functions can be omitted or provided as optional functions.

[0074] As described above, when the user terminal 200A initiates a ride request action using the ride fare calculation system 10, a ride request signal 552 is transmitted from the user terminal 200A to the calculation server 110. Here, steps S501 and S502 may be performed by the user terminal 200B.

[0075] When the operation request signal 552 transmitted from the user terminal 200A is received by the computing server 110, the computing server 110 transmits an operation request application signal 554 to the dispatch server 120 (step S531). Here, the operation request application signal 554 transmitted from the computing server 110 to the dispatch server 120 in step S531 may be transmitted to the dispatch server 120 after a predetermined period (delay period) has elapsed since the operation request was confirmed in step S502. Furthermore, during the above delay period, the computing server 110 may provide the user terminal 200A with an interface 660 that accepts cancellations of operation requests, for example, as shown in Figure 16.

[0076] When the dispatch server 120 receives the dispatch request signal 554, it sends a dispatch instruction signal 556 to the vehicle 300 managed by the dispatch center (step S541). In step S541, the dispatch server 120 obtains information including the location information of the vehicle 300 managed by the dispatch center and the vehicle status of the vehicle 300 (empty, out of service, dispatched, fare-driven, etc.) via the dispatch center's second network 102. Based on this information, the dispatch server 120 specifies the vehicle 300 and sends the dispatch instruction signal 556. If the vehicle 300 that receives the dispatch instruction signal 556 is actually available for dispatch, it sends an acceptance signal 558 back to the dispatch server 120 (step S521).

[0077] When the arranging server 120 receives the acceptance signal 558 returned from the vehicle 300, the arranging server 120 sends an acceptance notification 560 to the computing server 110 (step S542). When the computing server 110 receives the acceptance notification 560, the computing server 110 sends an arrangement status notification 562 to the user terminal 200A (step S522). The arrangement status notification 562 includes information on the vehicle being picked up (vehicle type, vehicle number, driver information, actual vehicle status, etc.) and the current location of the vehicle 300. The arrangement status notification 562 may also further include the estimated time of arrival at the location of the user terminal 200A riding in the vehicle 300, the estimated time of arrival at the destination 400, traffic congestion information, etc.

[0078] The computing server 110 may provide the user terminal 200A, which received the dispatch status notification 562 transmitted in step S522, with an interface 670 that accepts inquiries about the vehicle 300 being dispatched, for example, as shown in Figure 17. If the user wishes to inquire about the vehicle 300 being dispatched, they can use the interface 670 shown in Figure 17 to communicate with the driver of the vehicle 300. When the vehicle 300 being dispatched arrives at the location of the user terminal 200A, the computing server 110 may provide an interface 680 that notifies the user that the vehicle 300 has arrived, as shown in Figure 18.

[0079] In the interface 680 of Figure 18, an inquiry button 681 may be provided to connect the user terminal 200A and the vehicle 300 driver's mobile phone in a call-enabled manner if the user scheduled to ride cannot find the vehicle 300 (taxi). By pressing the inquiry button 681, the user terminal 200A can automatically make a call to the vehicle 300 driver's mobile phone. Alternatively, pressing the inquiry button 681 may automatically make a call from the vehicle 300 driver's mobile phone to the user terminal 200A. The interface 680 may also include an estimated time of arrival at the destination 400 682, a confirmation number 683 indicating that the user terminal 200 is the terminal that requested the service, and a driver evaluation 684.

[0080] As described above, user terminal 200A boards vehicle 300 (step S503). In step S503, when user terminal 200A boards vehicle 300, first boarding position information 564 indicating the boarding position of user terminal 200A on vehicle 300 is generated and transmitted to the computing server 110 (step S504). Here, the first boarding position information 564 may be generated by user terminal 200A based on the relative positional relationship between user terminal 200A and vehicle 300, or it may be generated by the computing server 110 based on the relative positional relationship between user terminal 200A and vehicle 300. In step S504, the computing server 110 receives the generated first boarding position information 564 and acquires the first boarding position information 564 (step S532). Here, the first boarding position information 564 includes user identification information that identifies user terminal 200A and user terminal 200B. Here, the user ID of the user terminal 200A is included in the first boarding location information 564 as user identification information.

[0081] The vehicle 300 carrying user terminal 200A moves to the boarding position of user terminal 200B and allows user terminal 200B to board (step S511). In step S511, when user terminal 200B boards the vehicle 300, second boarding position information 566 indicating the boarding position of user terminal 200B in the vehicle 300 is generated and transmitted to the calculation server 110 (step S512). Here, the second boarding position information 566 may be generated by user terminal 200B based on the relative positional relationship between user terminal 200B and vehicle 300 or the relative positional relationship between user terminal 200B and user terminal 200A boarding the vehicle 300. Alternatively, the second boarding position information 566 may be generated by the calculation server 110 based on the relative positional relationship between user terminal 200B and vehicle 300 or the relative positional relationship between user terminal 200B and user terminal 200A boarding the vehicle 300. In step S512, the second boarding location information 566 is received by the computing server 110, and the computing server 110 acquires the second boarding location information 566 (step S533). Here, the second boarding location information 566 includes user identification information that identifies user terminal 200A and user terminal 200B. In this case, the user ID of user terminal 200B is included in the second boarding location information 566 as user identification information.

[0082] When user terminals 200A and 200B and vehicle 300 arrive at their destination (step S505), user terminals 200A and 200B disembark from vehicle 300 (steps S506, S513). In step S506, when user terminal 200A disembarks from vehicle 300, first disembarkation location information 568 indicating the disembarkation location of user terminal 200A from vehicle 300 is generated and transmitted to the calculation server 110 (step S507). Also, in step S513, when user terminal 200B disembarks from vehicle 300, second disembarkation location information 570 indicating the disembarkation location of user terminal 200B from vehicle 300 is generated and transmitted to the calculation server 110 (step S514).

[0083] Here, the first disembarkation location information 568 may be generated by user terminal 200A based on the relative positional relationship between user terminal 200A and vehicle 300, or it may be generated by the calculation server 110 based on the relative positional relationship between user terminal 200A and vehicle 300. Also, the second disembarkation location information 570 may be generated by user terminal 200B based on the relative positional relationship between user terminal 200B and vehicle 300, or it may be generated by the calculation server 110 based on the relative positional relationship between user terminal 200B and vehicle 300.

[0084] The first disembarkation location information 568 and the second disembarkation location information 570 transmitted from user terminals 200A and 200B are received (acquired) by the computing server 110 (step S534). Here, the first disembarkation location information 568 and the second disembarkation location information 570 include user identification information that identifies user terminal 200A and user terminal 200B. In this case, the user ID of user terminal 200A is included in the first disembarkation location information 568, and the user ID of user terminal 200B is included in the second disembarkation location information 570.

[0085] Furthermore, when the vehicle 300 arrives at its destination in step S505, the vehicle 300 generates operation information 572, including operation identification information and operation fare, and reports it to the arrangement server 120 (step S523).

[0086] When the dispatch server 120 receives the operation information 572 reported from the vehicle 300, the dispatch server 120 notifies the calculation server 110 of the operation information 574, which includes operation identification information and operation charges (step S543).

[0087] When the operation information 574 notified by the dispatch server 120 is received by the calculation server 110, the calculation server 110 obtains the operation identification information and operation charges contained in the operation information 574 (step S535). Next, based on the operation identification information and operation charges obtained in step S535, the proportion and amount of the operation charges that user terminal A and user terminal B should each bear are calculated (step S536). Then, the calculation result 576 from step S536 (either the calculated proportion and / or the amount of the burden) is notified to user terminals 200A and 200B (step S537).

[0088] When the calculation result 576 notified from the calculation server 110 is received by user terminals 200A and 200B, each user terminal 200A and 200B confirms the acceptance of the calculation result 576 (steps S508 and S515). If the user terminals select to accept the calculation result ("Yes" in steps S508 and S515), acceptance information 578 is sent from user terminals 200A and 200B to the calculation server 110. On the other hand, if the user terminals select to reject the calculation result ("No" in steps S508 and S515), the operation flow is terminated, the program is terminated, or the user is moved to the top screen.

[0089] When the calculation server 110 receives the confirmed information 578 transmitted from user terminals 200A and 200B, the calculation server 110 issues an invoice 580 to user terminals 200A and 200B (step S538). Then, user terminals 200A and 200B make a payment for the invoice in step S538 (steps S509, S516).

[0090] In steps S508 and S515, if the user selects to reject the calculation result, the calculation server 110 may bill the user terminal 200A that requested the service for the full amount of the service fee.

[0091] As described above, the shared ride section can be calculated without increasing the burden on user terminals 200A and 200B and vehicle 300, and the proportion of the usage fee to be borne by user terminals 200A and 200B according to the distance traveled using the shared ride can be calculated.

[0092] [Calculation method for the percentage calculation section] The calculation method of the ratio calculation unit 176 of the calculation server 110 shown in Figure 6 will be explained in detail with reference to Figure 19. In the shared fare calculation system 10 according to Embodiment 1, the ratio calculation unit 176 calculates the burden ratio of user terminals 200A and 200B based on the respective boarding ratios of user terminals 200A and 200B in a route where user terminal 200A, which is relatively farther from the destination 400, is allowed to board first, and then user terminal 200B is allowed to board together to reach the destination 400.

[0093] In steps S532 to S534 of the operation flow of the ride-sharing fare calculation system 10 shown in Figure 9, the ratio calculation unit 176 acquires first boarding location information, second boarding location information, first alighting location information, and second alighting location information. Based on the acquired location information, it calculates the distance Da between the boarding location of user terminal 200A and the boarding location of user terminal 200B, and the distance Db between the boarding location of user terminal 200B and the destination 400. Here, the first travel distance for the first leg of the journey in which user terminal 200A boarded the vehicle 300 is Da + Db, and the second travel distance for the second leg of the journey in which user terminal 200B boarded together with user terminal A is Db.

[0094] In the example shown in Figure 19, the ratio calculation unit 176 calculates the ratio of the second travel distance (Db) to the first travel distance (Da + Db) as the ride ratio. Here, a method of calculating the ride ratio based on the travel distances in the first and second journeys is illustrated, but the method is not limited to this. For example, the ride ratio may be calculated based on the second travel time required for the second journey relative to the first travel time required for the first journey. In other words, the ratio calculation unit 176 calculates the share of the burden that each of the multiple users should bear for the operation of the vehicle 300, based on the actual travel distances or travel times required for each of the multiple users using the vehicle 300.

[0095] Here, distances Da and Db are distances on a road map. For example, distance Da is the distance of the route on the road map from the boarding position of user terminal 200A to the boarding position of user terminal 200B. Note that the distance on the road map is not the straight-line distance between two points, but the distance traveled based on the road map. However, distances Da and Db are not limited to distances on a road map, and may also be the straight-line distance connecting their respective location information.

[0096] Furthermore, while Figure 19 illustrates a case where the ratio calculation unit 176 calculates the burden ratio for a route in which user terminals 200A and 200B board vehicle 300 at different locations and alight from vehicle 300 at the same destination 400, the unit is not limited to this case. For example, the ratio calculation unit 176 may calculate the burden ratio for a route in which user terminals 200A and 200B board vehicle 300 at the same location and alight from vehicle 300 at different destinations. Alternatively, the ratio calculation unit 176 may calculate the burden ratio for a route in which user terminals 200A and 200B board vehicle 300 at different locations and alight from vehicle 300 at different destinations. For example, the unit may calculate the burden ratio for a route in which user terminal 200B is aboard vehicle 300 with user terminal 200A, and user terminal 200A alights from vehicle 300 first.

[0097] [Method for obtaining user boarding and alighting location information] Here, the method for acquiring the user's boarding location information and alighting location information using the location information identification unit 172 will be explained in detail with reference to Figure 20. Figure 20 is a diagram showing an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to one embodiment of the present invention. As shown in Figure 20, the vehicle 300 has a short-range wireless communication unit 320 that generates a signal when the distance between the user terminal 200B and the vehicle 300 is less than or equal to a first distance D1. If the vehicle 300 has a short-range wireless communication unit 320, the short-range wireless communication unit 320 may be installed in a POS terminal (Point-Of-Sale terminal) installed in the vehicle 300 or in a communication terminal held by the driver.

[0098] When the distance between the user terminal 200B and the vehicle 300 becomes less than or equal to the first distance D1, the short-range wireless communication unit 320 transmits an information signal specific to the short-range wireless communication unit 320 to the user terminal 200B. In other words, when the distance between the user terminal 200B and the vehicle 300 becomes less than or equal to the first distance D1, the user terminal 200B receives an information signal specific to the short-range wireless communication unit 320 from the short-range wireless communication unit 320. When the user terminal 200B receives the information signal specific to the short-range wireless communication unit 320, the user terminal 200B transmits to the computing server 110 that it has received the specific information signal. The location information identification unit 172 of the computing server 110 then determines, based on the specific information signal, that the user terminal 200B has boarded the vehicle 300 or that the user terminal 200B has disembarked from the vehicle 300.

[0099] As described above, the location information identification unit 172 acquires location information when user terminal 200B boards vehicle 300, thereby acquiring second boarding location information indicating the boarding position of user terminal 200B into vehicle 300. In the example shown in Figure 20, user terminal 200B boards vehicle 300 with user terminal 200A, so the second boarding location information corresponds to the starting position of the shared ride for user terminals 200A and 200B.

[0100] As described above, the ride-sharing fare calculation system 10 according to Embodiment 1 of the present invention provides a calculation server that calculates the ride-sharing section without increasing the burden on users and vehicle drivers, and calculates the proportion of the usage fee borne by users according to the distance traveled by users who use the ride-sharing service, as well as a communication terminal that communicates with the calculation server.

[0101] <Variation 1 of Embodiment 1> A modified example of one embodiment of the present invention will be described using Figure 21. Figure 21 is a diagram showing an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. The ride-sharing fare calculation system 11 according to Modification 1 of Embodiment 1 differs from the ride-sharing fare calculation system 10 in that the user terminal 200B has a short-range wireless communication unit 215 that generates a signal when the distance between the user terminal 200B and the vehicle 300 is less than or equal to a first distance D1.

[0102] When the distance between the user terminal 200B and the vehicle 300 becomes less than or equal to the first distance D1, the short-range wireless communication unit 215 transmits an information signal unique to the short-range wireless communication unit 215 to the vehicle 300. In other words, when the distance between the user terminal 200B and the vehicle 300 becomes less than or equal to the first distance D1, the vehicle 300 receives the information signal unique to the short-range wireless communication unit 215 from the vehicle 300. When the vehicle 300 receives the information signal unique to the short-range wireless communication unit 215, it transmits to the dispatch server 120 that it has received the unique information signal. Then, when the dispatch server 120 transmits the unique information signal to the calculation server 110, the location information identification unit 172 of the calculation server 110 obtains second boarding position information indicating the boarding position of the user terminal 200B in the vehicle 300 on which the user terminal 200A is boarding, based on the unique information signal. Similar to Figure 20, in the example in Figure 21, user terminal 200B boards the vehicle 300 that user terminal 200A is riding in, so the second boarding location information corresponds to the starting position of the shared ride for user terminals 200A and 200B.

[0103] <Modification 2 of Embodiment 1> A modified example of one embodiment of the present invention will be described using Figures 22 to 24. Figure 22 is a diagram showing an example of a method for determining whether a user has boarded or alighted in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. As shown in Figure 22, the location information identification unit 172 of the ride-sharing fare calculation system 12 according to modified example 2 of Embodiment 1 determines that the user terminal 200B has boarded the vehicle 300 when the distance between the location information of the user terminal 200B and the location information of the vehicle 300 is less than or equal to the second distance D2. Then, based on the location information of the user terminal 200B or the vehicle 300 at the time it is determined that the user terminal 200B has boarded the vehicle 300, a second boarding location information indicating the location where the user terminal 200B boarded the vehicle 300 is acquired.

[0104] On the other hand, the location information identification unit 172 determines that the user terminal 200B has disembarked from the vehicle 300 when the distance between the location information of the user terminal 200B and the location information of the vehicle 300 becomes greater than the second distance D2. Then, based on the location information of the user terminal 200B or the vehicle 300 at the time it is determined that the user terminal 200B has disembarked from the vehicle 300, it acquires second disembarkation location information indicating the location where the user terminal 200B disembarked from the vehicle 300.

[0105] Specifically, as shown in Figure 22, during boarding determination 710, it is determined that user terminal 200B has boarded vehicle 300 when vehicle 300 enters a radius of the second distance D2 from user terminal 200B. Also, as shown in disembarking determination 720, it is determined that user terminal 200B has disembarked from vehicle 300 when vehicle 300 leaves the radius of the second distance D2 from user terminal 200B.

[0106] Next, we will describe a function to further improve the accuracy of boarding and alighting determination. Figure 23 is a diagram showing an example of a method for determining whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention. As shown in Figure 23, the location information identification unit 172 may determine that user terminal 200B is on board vehicle 300 if the distance between the location information of user terminal 200B and the location information of vehicle 300 is less than or equal to the second distance D2, and furthermore, the location information of user terminal 200B and the location information of vehicle 300 are moving in the same direction. On the other hand, as shown in Figure 24, the location information identification unit 172 may determine that user terminal 200A has alighted from vehicle 300 if the location information of vehicle 300 is moving in a different direction from the location information of user terminal 200B.

[0107] <Modification 3 of Embodiment 1> A modified example of one embodiment of the present invention will be described with reference to Figures 25 to 27. Figure 25 is a diagram showing an overview of the calculation method of the calculation server used in the ride fare calculation system according to a modified example of one embodiment of the present invention.

[0108] [Calculation method for the percentage calculation section] As shown in Figure 25, the ratio calculation unit 176 calculates the burden ratio based on the first estimated distance Ea from the first boarding position 410 of user terminal 200A (first user), who boarded first, to the destination 400, and the second estimated distance Eb from the second boarding position 420 of user terminal 200B (second user), who boarded with user terminal 200A after user terminal 200A, to the destination 400. In other words, the first estimated distance Ea is the distance assuming that user terminal 200A traveled from the first boarding position 410 to the destination 400 without sharing a ride, and the second estimated distance Eb is the distance assuming that user terminal 200B traveled from the second boarding position 420 to the destination 400 without sharing a ride. In other words, the ratio calculation unit 176 calculates the burden ratio for each of the multiple user terminals 200A and 200B based on the distance each would travel if they used the vehicle 300 independently from the boarding position to the disembarking position. Here, the first estimated distance Ea and the second estimated distance Eb are distances on a road map. However, the first estimated distance Ea and the second estimated distance Eb are not limited to distances on a road map, but may also be the straight-line distance connecting their respective location information points.

[0109] [Method for obtaining user boarding and alighting location information] Next, using Figures 26 and 27, we will explain how to acquire the first boarding position information at the first boarding position 410 and the second boarding position information at the second boarding position 420. Here, we will explain the case where the vehicle 300 has a short-range wireless communication unit 320. Figures 26 and 27 are diagrams showing an example of how to determine whether a user is boarding or alighting in a ride-sharing fare calculation system according to a modified example of one embodiment of the present invention.

[0110] First, as shown in Figure 26, when the distance between the user terminal 200A and the vehicle 300 falls below a predetermined distance, the user terminal 200A receives an information signal specific to the short-range wireless communication unit 320 from the short-range wireless communication unit 320. Upon receiving this specific information signal, the user terminal 200A transmits to the computing server 110 that it has received the specific information signal. The computing server 110 then determines, based on this specific information signal, that the user terminal 200A has boarded the vehicle 300. The location information identification unit 172 then acquires first boarding location information indicating the boarding location of the user terminal 200A in the vehicle 300.

[0111] Next, as shown in Figure 27, when the distance between the user terminal 200B and the vehicle 300 falls below a predetermined distance, the user terminal 200B receives an information signal specific to the short-range wireless communication unit 320 from the short-range wireless communication unit 320. Upon receiving this specific information signal, the user terminal 200B transmits to the computing server 110 that it has received the specific information signal. The computing server 110 then determines, based on this specific information signal, that the user terminal 200B has boarded the vehicle 300. The location information identification unit 172 then acquires second boarding location information indicating the boarding location of the user terminal 200B in the vehicle 300.

[0112] Then, when user terminals 200A and 200B and vehicle 300 arrive at destination 400, user terminals 200A and 200B disembark from vehicle 300, and user terminals 200A and 200B can no longer receive information signals specific to the short-range wireless communication unit 320, it is determined that user terminals 200A and 200B have disembarked from vehicle 300. The location information identification unit 172 then acquires first disembarkation location information and second disembarkation location information indicating the disembarkation locations of user terminals 200A and 200B from vehicle 300.

[0113] When using a shared ride along a route as shown in Figures 25 to 27, there is no difference in the travel distance for user terminal 200B whether or not it shares a ride, but there is a difference in the travel distance for user terminal 200A. In other words, user terminal 200A's travel distance becomes unnecessarily long in order to pick up user terminal 200B. According to the shared ride fare calculation system 13 of the modified example 3 of Embodiment 1, a fair burden ratio can be calculated even in such a case.

[0114] As described above, according to the ride-sharing fare calculation system 13 of the modified embodiment 1 of the present invention, similar to embodiment 1, it is possible to provide a calculation server and a communication terminal that communicates with the calculation server that calculate the ride-sharing section without increasing the burden on the user and the vehicle driver, and calculate the proportion of the usage fee borne by the user according to the distance traveled by the user using the ride-sharing service. Furthermore, even when the distance traveled by using the ride-sharing service to reach a destination is unnecessarily longer than if it were assumed that the user would travel to the destination without using the ride-sharing service, a fair proportion of the burden can be calculated.

[0115] <Embodiment 2> A ride-sharing fare calculation system according to Embodiment 2 of the present invention will be described in detail with reference to Figures 28 and 29. Note that the overview of the ride-sharing fare calculation system, the hardware configuration of the calculation server, the hardware configuration of the user terminal, and the hardware configuration of the vehicle are the same as those of the ride-sharing fare calculation system 10 according to Embodiment 1, and therefore will not be described here. In Embodiment 2, the user terminal 200 communicates with the fare meter of the vehicle 300 to receive the fare from the vehicle 300. Embodiment 2 differs from Embodiment 1 and its modified versions in the functionality of the communication terminal. Therefore, the functional configuration of the communication terminal in Embodiment 2 will be described here, and the other configurations will not be described. Here, the user terminal 200 may communicate directly with the fare meter of the vehicle 300, or the user terminal 200 may communicate with the fare meter of the vehicle 300 via one or both of the arrangement server 120 and the calculation server 110.

[0116] [Functional configuration of the communication terminal requested for operation] The communication terminal used to request rides in the ride-sharing fare calculation system 20 according to Embodiment 2 will now be described. The functional configuration of the user terminal 200A used in the ride-sharing fare calculation system 20 is similar to that of the user terminal 200A used in the ride-sharing fare calculation system 10 according to Embodiment 1 shown in Figure 7. However, it differs from the user terminal 200A used in the ride-sharing fare calculation system 10 in that it has a ride-sharing fare information receiving unit 278 that receives ride-sharing fare information including ride charges from the fare meter of the vehicle 300, and a ride-sharing fare information transmitting unit 280 that transmits the ride-sharing fare information received by the ride-sharing fare information receiving unit 278 to the calculation server 110. Here, the ride-sharing fare information receiving unit 278 does not need to communicate directly with the vehicle 300 or the fare meter of the vehicle 300. For example, the ride-sharing fare information receiving unit 278 can communicate with the vehicle 300 or the fare meter of the vehicle 300 via either or both of the arrangement server 120 and the calculation server 110.

[0117] [Functional configuration of the communication terminals used on board] Figure 29 is a block diagram showing the functional configuration of a communication terminal used in a ride-sharing fare calculation system according to one embodiment of the present invention. In Figure 29, the functional blocks of user terminal 200B, which is a passenger in a vehicle 300 operated by user terminal 200A, are explained in more detail. According to Figure 29, the passenger user terminal 200B is similar in functional block to user terminal 200A of user A who makes the operation request, but user terminal 200B differs from user terminal 200A in that it does not have an operation request signal transmission unit 270.

[0118] Since the user terminal 200B does not need to make a request for service, it does not need to have the service request signal transmission unit 270 as described above. However, this does not mean that the user terminal 200B must not have the service request signal transmission unit 270. Of course, the user terminal 200B may have the service request signal transmission unit 270.

[0119] As described above, the ride-sharing fare calculation system 20 according to Embodiment 2 of the present invention provides a calculation server and a communication terminal that communicates with the calculation server, which calculate the ride-sharing section and the proportion of the usage fee borne by the user according to the distance traveled, without increasing the burden on the user and the vehicle driver, similar to Embodiment 1. Furthermore, by enabling communication between the fare meter of the vehicle 300 and the user terminal 200, data can be exchanged more efficiently.

[0120] The computing server and communication terminal described in the above embodiment can be realized by a program or application that operates the computer contained within the computing server and communication terminal. This program or application can be downloaded and installed to the computing server and communication terminal via internet communication. Alternatively, this program or application can be installed to the computing server and communication terminal via a computer-readable recording medium.

[0121] It should be noted that the present invention is not limited to the embodiments described above, and can be modified as appropriate without departing from the spirit of the invention. [Explanation of Symbols]

[0122] 10, 11, 12, 20: Shared ride fare calculation system, 101: First network, 102: Second network, 110: Calculation server, 111: Control unit, 112: Hard disk, 113: Communication unit, 115, 125, 135: Database, 120: Arrangement server, 130: SNS server, 170: Identification information acquisition unit, 172: Location information identification unit, 174: Storage unit, 176: Percentage calculation unit, 178: Fare calculation unit, 180: Notification unit, 200: User terminal, 205: Memory, 210: Control unit, 215, 320: Short-range wireless communication unit, 220: Communication module, 230: Display, 240: Operation buttons, 250: Speaker, 260: Microphone, 270: Operation request signal transmission unit 272: Identification information receiving unit, 274: Location information identification unit, 276: Fare information receiving unit, 278: Operation fare information receiving unit, 280: Operation fare information transmitting unit, 300: Vehicle, 310: Vehicle body, 400: Destination, 410: First boarding location, 420: Second boarding location, 552: Operation request signal, 554: Operation request application signal, 556: Pick-up instruction signal, 558: Acceptance signal, 560: Acceptance notification, 562: Arrangement status notification, 564: First boarding location information, 566: Second boarding location information, 568: First alighting location information, 570: Second alighting location information, 572, 574: Operation information, 576: Calculation result, 578: Confirmation information, 580: Billing, 600: Boarding location, 610, 620, 630, 640, 650, 660, 670, 680: Interface, 611: Vehicle icon, 612: Friend list tab, 613: Talk tab, 614: Timeline tab, 615: Other tab, 621: Request button, 641: Destination pin, 642: Destination address, 643: Settings button, 651: First location information, 652: First location information pin, 653: User information confirmation field, 654: User registration credit card information field, 655: Coupon code field, 656: Arrangement center information field, 657: Agree button, 658: Pick-up / drop-off information field, 681: Inquiry button, 682: Estimated arrival time, 683: Confirmation number, 684: Driver rating, 710: When deciding to board, 720: When deciding to drop off

Claims

1. A program executed by a first terminal of a first user riding in a vehicle and a second terminal of a second user riding in the vehicle, The dispatch instructions for the vehicle are received by the first terminal via a service interface that enables communication between the first user and the second user, The dispatch instruction is transmitted by the first terminal to a server that communicates with the communication unit of the vehicle, and the following actions are performed: program.

2. The program according to claim 1, The first user and the second user have a mutually recognized relationship in the service. program.

3. A program according to claim 1 or claim 2, The location information of the first terminal is transmitted to the server by the first terminal, The second terminal transmits its location information to the server, and the server is made to perform this action. program.

4. The program according to claim 3, The first terminal transmits to the server the first boarding location information of the first user boarding the vehicle, The second terminal transmits the second boarding location information of the second user boarding the vehicle to the server, and the second terminal performs the following actions: program.

5. The program according to claim 4, The first terminal transmits to the server the first disembarkation location information of the first user disembarking from the vehicle, The second terminal transmits to the server the second disembarkation location information of the second user disembarking from the vehicle, and the following is performed: program.

6. A program according to any one of claims 1 to 5, The interface includes an object for the first user and the second user to communicate. program.

7. A program according to any one of claims 1 to 5, The interface includes an object for calculating the fare for a shared ride between the first user and the second user. program.

8. A program according to any one of claims 1 to 5, After the dispatch instruction is received by the server, the first terminal is provided with an interface for accepting cancellation of the dispatch instruction. program.

9. An information processing method performed by a first terminal of a first user riding in a vehicle and a second terminal of a second user riding in the vehicle, The dispatch instructions for the vehicle are received by the first terminal via a service interface that enables communication between the first user and the second user, The first terminal transmits the dispatch instruction to a server that communicates with the communication unit of the vehicle, Information processing methods.

10. A system comprising a first terminal of a first user riding in a vehicle, a second terminal of a second user riding in the vehicle, and a server capable of communicating with the first terminal and the second terminal, The dispatch instructions for the vehicle are received by the first terminal via a service interface that enables communication between the first user and the second user, The first terminal transmits the dispatch instruction to a server that communicates with the communication unit of the vehicle, and performs the following actions: system.

Images