Program and information processing method
A system using a calculation server and communication terminals to determine fair fares in shared rides by specifying positions and calculating proportional charges based on travel distances or times, addressing the inefficiencies and inaccuracies of manual input methods.
Patent Information
- Application Number
- JP2024160231
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Filing Date
- 2024-09-17
- Publication Date
- 2024-12-05
- Estimated Expiration
- Not applicable · inactive patent
AI Technical Summary
Existing methods for calculating fares in shared rides in paid vehicles, such as taxis, are cumbersome and prone to errors due to manual input of destinations, leading to unfair billing and increased burden on drivers, and do not account for varying ride distances accurately.
A system utilizing a calculation server and communication terminals to determine user-specific fare shares based on actual travel distances or times, using GPS and short-range wireless communication to specify boarding and alighting positions, and calculate proportional charges.
The system efficiently calculates fair usage fees without increasing user or driver burden, ensuring accurate billing based on shared ride distances, reducing errors and misunderstandings.
Smart Images

Figure 2024169522000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a payment technique for multiple users sharing a toll vehicle such as a taxi. In particular, the present invention relates to a technique for calculating the share of the usage fee for each user when the riding distance of each of the multiple users sharing a toll vehicle is different. [Background technology]
[0002] Conventionally, transportation using paid vehicles such as taxis and hire cars has been used as one of the means of transportation. Transportation using paid vehicles is very convenient because it can provide services according to the needs of each individual user. However, the operation fee is higher than public transportation such as trains and buses.
[0003] Paid vehicles such as taxis and hire cars can be shared by as many users as possible, i.e., carpooling, in order to keep the cost per user low. In particular, when multiple users are traveling to the same destination, there is a high demand for carpooling.
[0004] In the above-mentioned method of sharing paid vehicles, a technique has been developed for calculating the fares of each of multiple users according to the boarding positions and destinations of the users transmitted from the multiple users to a taxi driver or a taxi dispatch center, as shown in, for example, Patent Document 1. The boarding positions and destinations of the multiple users are transmitted from the multiple users to the taxi driver or the taxi dispatch center verbally or by inputting characters. [Prior art documents] [Patent documents]
[0005] [Patent Document 1] JP 2003-233656 A Summary of the Invention [Problem to be solved by the invention]
[0006] However, according to the technology described in Patent Document 1, when a user transmits the boarding location and destination by character input, the user has to set the destination in advance and input it in characters, which is time-consuming. In addition, when the boarding location and destination are transmitted to a taxi driver orally, the taxi driver has to transmit the boarding locations and destinations of each of the users to the taxi dispatch center, which not only increases the burden on the driver but also induces mistakes due to the driver's misremembering. In addition, even if the route in the case of carpooling is longer than necessary compared to the route in the case of not carpooling, the fee sharing ratio is simply determined according to the riding distance of each user, so there is a problem that the fare is not divided fairly.
[0007] The present invention has been made in consideration of such problems, and aims to provide a calculation server that calculates shared ride sections without increasing the burden on users and drivers of toll vehicles, and calculates the user's share of the usage fee based on the distance traveled using the shared ride, 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 has 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 boarding position information and disembarking position information of each of the multiple users based on the distance between the communication terminals of the multiple users and the vehicle, a memory unit that associates and stores the operation identification information, user identification information, boarding position information, and disembarking position information, a proportion calculation unit that calculates the proportion of the amount that each of the multiple users must pay for the operation based on the boarding position information and disembarking position information of the multiple users, and a fare calculation unit that calculates the amount that each of the multiple users must pay based on the proportion and the operation fare for the operation.
[0009] In another aspect, the ratio calculation unit may calculate the ratio based on the distance traveled when each of the multiple users independently uses a vehicle from the boarding position information to the disembarking position information.
[0010] In another aspect, the ratio calculation unit may calculate the ratio based on the actual travel distances traveled by each of a plurality of users using a vehicle, or the actual travel time required for the travel distance.
[0011] In another aspect, the position information identifying unit may identify the boarding position information and the disembarking position information by short-range wireless communication between the communication terminal and the vehicle.
[0012] In another aspect, the electronic device 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 has an identification information receiving unit that receives operation identification information that identifies the operation of a vehicle operated in response to an operation request, a location information identifying unit that identifies a user's boarding location information and disembarking 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 and disembarking location information, as well as an amount to be paid by the user calculated based on the operation fare for the operation.
[0014] In another aspect, the position information identifying unit may identify the boarding position information and the disembarking position information by short-range wireless communication between the user's communication terminal and the vehicle.
[0015] In another aspect, the vehicle may further include a fare information receiving unit that receives fare information including a fare from the vehicle, and a fare information transmitting unit that transmits the fare information received by the fare information receiving unit to the calculation server. Effect of the Invention
[0016] According to the calculation server, communication terminal, and communication terminal program of the present invention, it is possible to provide a calculation server that calculates shared ride sections without increasing the burden on users and drivers of toll vehicles, and calculates the user's share of the usage fee based on the distance traveled using the shared ride, and a communication terminal that communicates with the calculation server. [Brief description of the drawings]
[0017] [Figure 1] 1 is a diagram showing an overview of a shared ride fare calculation system according to one embodiment of the present invention. [Diagram 2] 1 is a block diagram showing an overview of a shared ride fare calculation system according to one embodiment of the present invention. [Diagram 3] 1 is a block diagram showing the hardware configuration of a calculation server used in a shared ride fare calculation system according to one embodiment of the present invention. FIG. [Figure 4] 1 is a schematic diagram showing the hardware configuration of a communication terminal used in a shared ride fare calculation system according to one embodiment of the present invention. FIG. [Diagram 5] 1 is a schematic diagram showing the hardware configuration of a vehicle used in a shared ride fare calculation system according to one embodiment of the present invention. FIG. [Figure 6] 2 is a block diagram showing the functional configuration of a calculation server used in the shared ride fare calculation system according to one embodiment of the present invention. FIG. [Figure 7] 2 is a block diagram showing the functional configuration of a communication terminal used in the shared ride fare calculation system according to one embodiment of the present invention. FIG. [Figure 8] 2 is a block diagram showing the functional configuration of a communication terminal used in the shared ride fare calculation system according to one embodiment of the present invention. FIG. [Figure 9] A diagram showing the operational flow of the shared ride fare calculation system according to one embodiment of the present invention. [Figure 10] A figure showing an example of an interface displayed on a user terminal when a program of a ride-sharing support device is started in the operational flow of a ride-sharing fare calculation system according to one embodiment of the present invention. [Figure 11]A figure showing an example of an interface displayed on a user terminal when a program of a ride-sharing support device is started in the operational flow of a ride-sharing fare calculation system according to one embodiment of the present invention. [Figure 12] A figure showing an example of a user registration interface in the operational flow of the shared ride fare calculation system according to one embodiment of the present invention. [Figure 13] A figure showing an example of a user registration interface in the operational flow of the shared ride fare calculation system according to one embodiment of the present invention. [Figure 14] A figure showing an example of an interface for inputting a boarding location in the operational flow of the shared fare calculation system according to one embodiment of the present invention. [Figure 15] FIG. 11 is a diagram showing an example of an interface for confirming consent to a user information request in the operational flow of a shared ride fare calculation system according to one embodiment of the present invention. [Figure 16] A figure showing an example of a screen display after an operation request signal is sent in the operational flow of the shared fare calculation system according to one embodiment of the present invention. [Figure 17] A figure showing an example of a screen display during pick-up in the operational flow of the shared ride fare calculation system according to one embodiment of the present invention. [Figure 18] A figure showing an example of a screen display when a vehicle arrives at the location of a user terminal in the operational flow of a shared ride fare calculation system according to one embodiment of the present invention. [Figure 19] FIG. 1 is a diagram showing an overview of a calculation method of a calculation server used in a shared fare calculation system according to one embodiment of the present invention. [Figure 20] A figure showing an example of a method for determining whether a user is getting on or off in a shared ride fare calculation system according to one embodiment of the present invention. [Figure 21] A figure showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system related to a modified embodiment of the present invention. [Figure 22]A figure showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system related to a modified embodiment of the present invention. [Diagram 23] A figure showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system related to a modified embodiment of the present invention. [Figure 24] A figure showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system related to a modified embodiment of the present invention. [Diagram 25] A diagram showing an overview of the calculation method of a calculation server used in a shared fare calculation system related to a modified example of one embodiment of the present invention. [Figure 26] A figure showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system related to a modified embodiment of the present invention. [Figure 27] A figure showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system related to a modified embodiment of the present invention. [Figure 28] 2 is a block diagram showing the functional configuration of a communication terminal used in the shared ride fare calculation system according to one embodiment of the present invention. FIG. [Figure 29] 2 is a block diagram showing the functional configuration of a communication terminal used in the shared ride fare calculation system according to one embodiment of the present invention. FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0018] The calculation server, communication terminal, and program of the communication terminal according to the present invention will be described below with reference to the drawings. However, the calculation server, communication terminal, and program of the communication terminal according to the present invention can be implemented in many different forms, and should not be interpreted as being limited to the description of the embodiments shown below. In the drawings referred to in this embodiment, the same parts or parts having similar functions are given the same reference numerals, and repeated explanations thereof will be omitted.
[0019] In addition, in the following description, it is the user who uses the toll vehicle, but since the user travels with the communication terminal (user terminal) that the user possesses, there is no clear distinction between the two. For example, when a user uses a toll vehicle, the user possesses a user terminal and uses the toll vehicle, so it may be expressed as "a user terminal uses a toll vehicle." This has the same meaning as "a user who possesses a user terminal uses a toll vehicle." Similarly, when a user uses a vehicle arrangement service, it may be expressed as the user terminal using the service.
[0020] In the embodiment of the present invention, the vehicle fare calculation system is described using a vehicle such as a taxi or hire car, the fare of which varies depending on either or both of the travel distance and the travel time, but is not limited thereto. For example, the present invention can be applied to ships, airplanes, helicopters, and other operating bodies.
[0021] First Embodiment A shared ride fare calculation system according to a first embodiment of the present invention and a shared ride fare calculation system including a program for calculating a shared ride fare will be described in detail with reference to FIGS.
[0022] [System Overview] FIG. 1 is a diagram showing an overview of a shared ride fare calculation system according to an embodiment of the present invention. FIG. 2 is a block diagram showing an overview of a shared ride fare calculation system according to an embodiment of the present invention. As shown in FIGS. 1 and 2, a shared ride fare calculation system 10 according to the first embodiment includes a calculation server 110, a dispatch server 120, and a social networking service (SNS) server 130 (hereinafter simply referred to as the "SNS server 130"). As shown in FIG. 1, the calculation server 110 and the SNS server 130 communicate with a plurality of user terminals 200A and 200B, and the dispatch server 120 communicates with a vehicle 300. Here, the vehicle 300 is a vehicle that has received a driving request from the user terminal 200A, and first the user terminal 200A gets on, then the user terminal 200B gets on, and heads to the destination while the user terminals 200A and 200B are sharing the ride.
[0023] Here, when there is no particular distinction between the user terminal 200A and the user terminal 200B, they are simply referred to as user terminals 200. Furthermore, the multiple user terminals 200 may be communication terminals that can be connected to at least the first network 101 shown in Fig. 2, and each user terminal 200 may have different functions. The user terminals 200 may be mobile phones, smartphones, tablet PCs, PDAs, personal computers, PHSs, etc.
[0024] The calculation server 110 is a server that calculates the share and amount of the operation fee that each of the multiple user terminals 200 who use the vehicle 300 to share the vehicle 300 should bear. 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 who ride in the operation, specifies the boarding position information and the disembarking position information of each of the multiple users based on the distance between the user terminal 200, which is the communication terminal of the multiple users, and the vehicle 300, associates and stores the above operation identification information, user identification information, boarding position information, and disembarking position information, calculates the share that each of the multiple users should bear for the above operation based on the boarding position information and the disembarking position information of the multiple users, and calculates the amount that each of the multiple users should bear based on the share and the operation fee for the operation.
[0025] Here, the operation identification information is, for example, identification information assigned to each of the multiple vehicles 300 for each hire. Specific examples of the operation identification information include an order sheet issued for each hire or an operation log for each hire. Furthermore, the user identification information is, for example, information for identifying the user terminal 200A and the user terminal 200B. Specific examples of the user identification information include device-specific information possessed by each user terminal 200, and user IDs (IDentifiers) in a service specific to each of the user terminals 200A and 200B managed by the SNS server 130.
[0026] The dispatch server 120 is a server owned by a dispatch center that receives a driving request and issues a pick-up instruction to the vehicle 300, and manages the location information and driving information of the vehicle 300. Here, the driving information includes the above driving identification information and driving fare. The driving information may also include user identification information. The dispatch server 120 may manage the above driving information in an analog or digital manner. Analog management is a management method in which the driver of the vehicle 300 brings back to the dispatch center an order sheet created each time the vehicle 300 is driven and a receipt for the driving fare recorded on the fare meter, and a worker at the dispatch center stores the order sheet and the receipt in the database of the dispatch server 120. On the other hand, digital management is a management method in which one or both of the driving identification information of the vehicle 300 corresponding to the order sheet and the driving fare corresponding to the receipt are transmitted from the vehicle 300 to the dispatch server 120 by wireless communication, and the information is successively stored in the database.
[0027] The SNS server 130 is a server that provides SNS services to user terminals 200, and manages personal information (device specific information of the user terminal, name, telephone number, credit card information, email address, address, age, gender, user ID, etc.) of users who own multiple user terminals 200 and subscribe to the SNS service.
[0028] Here, one or both of the multiple user terminals 200 and the vehicle 300 have a location identification means. The location identification means may be, for example, a GPS (Global Positioning System). In the shared ride fare calculation system 10, the location information of the multiple user terminals 200 is transmitted to the calculation server 110, and the location information of the vehicle 300 is transmitted to the dispatch server 120. The location information of the destination 400 is input by the multiple user terminals 200, and the location information of the destination 400 is transmitted to the calculation server 110 from the user terminal 200 that input the location information. As another example of the location identification means, in addition to the above GPS, short-range wireless communication can be used. The details of short-range wireless communication will be described in detail later.
[0029] In the present embodiment, the calculation server 110, the dispatch server 120, and the SNS server 130 are each separate servers, but the present invention is not limited to this configuration. For example, the calculation server 110 may have the functions of one or both of the dispatch server 120 and the SNS server 130. In other words, the functions of the calculation server 110, the dispatch server 120, and the SNS server 130 may be realized by one server.
[0030] Here, each user of the multiple user terminals 200 may be a user with whom a contactable exchange relationship called "follow" or "friend" is established in the SNS service managed by the SNS server 130. In other words, the multiple user terminals 200 form a contactable exchange relationship registered by at least one user in a predetermined service in which the multiple user terminals 200 are registered. Here, a configuration in which the multiple user terminals 200 form an exchange relationship is exemplified, but is not limited to this configuration. In other words, the multiple user terminals 200 do not need to form an exchange relationship as described above. In that case, the SNS server 130 can be omitted in FIG. 1.
[0031] In addition, each user of the multiple user terminals 200 may be a user who has built a "friend" relationship in an SNS service managed by the SNS server 130. In other words, the multiple user terminals 200 form a mutually approved exchange relationship in a predetermined service in which the multiple user terminals 200 are registered. A mutually approved exchange relationship does not simply mean that the users recognize each other's existence, but refers to a relationship that is built by, for example, one user approving a request sent by the other user to build a friend relationship. Here, a configuration in which the multiple user terminals 200 form a mutually approved exchange relationship is exemplified, but is not limited to this configuration. In other words, in the shared ride fare calculation system 10, the multiple user terminals 200 do not need to form the above-mentioned exchange relationship. In that case, the SNS server 130 can be omitted in FIG. 1.
[0032] As shown in Fig. 2, the calculation server 110, the dispatch server 120, the SNS server 130, and the multiple user terminals 200 are connected to each other via a first network 101. The dispatch server 120 and the vehicles 300 are connected to each other via a second network 102. Here, the calculation server 110, the dispatch server 120, and the SNS server 130 have databases (DB) 115, 125, and 135, respectively. A general IP network can be applied as the first network 101. A taxi radio or a local network can be applied as the second network 102.
[0033] Here, the database 115 of the calculation server 110 stores operation identification information, user identification information, and boarding position information and alighting position information of each of the multiple users. In addition, the operation identification information, user identification information, and boarding position information and alighting position information of each of the multiple users stored in the database 115 are associated with each other.
[0034] 2 illustrates a configuration in which the dispatch server 120 and the vehicle 300 are connected via the second network 102, but the present invention is not limited to this configuration, and for example, the vehicle 300 may be connected to the dispatch server 120 via the first network 101. Also, in FIG. 2, a configuration in which the calculation server 110, the dispatch server 120, and the SNS server 130 are directly connected to the databases 115, 125, and 135, respectively, is illustrated, but the present invention is not limited to this configuration, and for example, the databases 115, 125, and 135 may be connected to the first network 101. In other words, instead of the databases 115, 125, and 135, cloud computing in which data is stored via a network can be used.
[0035] The database 115 connected to the calculation server 110 or the database 135 connected to the SNS server 130 stores personal information (device specific information, name, telephone number, credit card information, email address, address, age, sex, user ID) of the user who owns each user terminal 200, evaluation information of the user who owns the user terminal 200 and the vehicle 300, road map information, traffic congestion information, etc. Here, each item included in the personal information of the user of the user terminal 200 is stored in association with each other.
[0036] The database 125 connected to the dispatch server 120 stores the vehicle type, vehicle number, driver information (name, mobile phone number, age, gender), actual vehicle status such as empty, out of service, pick-up, or hire, and location information of the vehicle 300.
[0037] The database 135 connected to the SNS server 130 stores the user ID of a user who uses the SNS service provided by the SNS server 130, device specific information of the user terminal owned by the user, a list of other users who have formed an exchange relationship with the user (friend list), etc. In addition, if the SNS server 130 has a payment system within the SNS service, the database 135 may further store information registered in the payment system, such as credit card information.
[0038] [Hardware configuration of the calculation server] 3 is a block diagram showing the hardware configuration of a calculation server used in a shared ride fare calculation system according to an embodiment of the present invention. According to FIG. 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) and storage devices such as a register and a memory. The control unit 111 executes a program stored in the memory by the CPU, and performs arithmetic processing in response to a command signal from the user terminal 200.
[0040] The hard disk 112 is a storage device capable of storing a large amount of data, and stores programs necessary for arithmetic processing and the like, and temporarily stores information transmitted from the user terminal 200 .
[0041] The communication unit 113 controls the transmission and reception of data between the dispatch server 120 , the SNS server 130 , and the user terminal 200 via the first network 101 .
[0042] Here, the storage device of the control unit 111 reads out and stores a program required for arithmetic processing from the hard disk 112 as necessary.
[0043] [Hardware configuration of user terminal] Fig. 4 is a schematic diagram showing the hardware configuration of a communication terminal used in a shared ride fare calculation system according to an embodiment of the present invention. According to Fig. 4, a memory 205, a control unit 210, a short-range wireless communication unit 215, and a communication module 220 are provided inside the main body of a user terminal 200, which is a communication terminal used in the shared ride fare calculation system 10. In addition, a display 230, an operation button 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 button 240 may not be provided. In addition, if the user terminal 200 does not have a calling function, the speaker 250 and the microphone 260 may not be provided.
[0044] The memory 205 stores data such as programs for causing the user terminal 200 to execute specific functions, information specific to the user terminal 200, and personal information of the user held by the user terminal 200.
[0045] The control unit 210 has an arithmetic unit such as a CPU and a storage device such as a register. The control unit 210 executes a program stored in the memory 205 by the CPU, and realizes various functions of the user terminal 200 in response to a command signal input by the user.
[0046] The short-distance wireless communication unit 215 is a functional unit that performs short-distance wireless communication using high-frequency radio waves from megahertz to gigahertz, and can perform communication within a range of several meters to several tens of meters. The short-distance wireless communication is communication that receives radio waves emitted from a radio wave source and transmits various information such as unique information of a communication device and a distance between the radio wave source and the communication device. Examples of short-distance wireless communication include RFID (Radio Frequency IDentifier) and BLE (BlueTooth (registered trademark) Low Energy). Here, the short-distance wireless communication unit 215 has an antenna that receives radio waves emitted from the radio wave source and a logic circuit that analyzes the received radio waves in the above-mentioned short-distance wireless communication. The short-distance wireless communication unit 215 may also have a logic circuit that modulates the radio waves emitted from the radio wave source in order to transmit unique information of the user terminal 200.
[0047] The communication module 220 includes an antenna for wirelessly transmitting and receiving signals, a high-frequency circuit, a demodulation circuit, etc. The communication module 220 is controlled by the control unit 210 to connect to a network and access the calculation server 110.
[0048] The display 230 may be a liquid crystal display, an organic electroluminescence display, or the like. The touch sensor may be a resistive film type, a capacitive type, an optical type sensor, or the like. The user operates the user terminal 200 according to the display to realize various functions.
[0049] [Vehicle hardware configuration] Fig. 5 is a schematic diagram showing a hardware configuration of a vehicle used in a shared fare calculation system according to an embodiment of the present invention. According to Fig. 5, a short-range wireless communication unit 320 is provided inside a vehicle body 310 of a vehicle 300. 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 analyzing unit that analyzes unique information of the user terminal 200 from the modulated radio waves.
[0050] [Functional configuration of the calculation server] Fig. 6 is a block diagram showing the functional configuration of a calculation server used in a shared ride fare calculation system according to an embodiment of the present invention. In Fig. 6, each functional block of the calculation server 110 in Fig. 2 is explained in more detail. According to Fig. 6, the calculation server 110 has an identification information acquisition unit 170, a location information specification unit 172, a storage unit 174, a ratio calculation unit 176, a fare calculation unit 178, and a notification unit 180.
[0051] The identification information acquisition unit 170 acquires the operation identification information and the operation fare from the dispatch server 120. Here, as described above, the operation identification information is information for identifying the operation of the vehicle 300, and may be information transmitted from the vehicle 300 by wireless communication, or may be information based on an order sheet stored by an operator. Or, it may be a mixture of these. In addition, the identification information acquisition unit 170 acquires user identification information from the user terminal 200. The user identification information is information for identifying multiple users who board the operation of the vehicle 300. In the case of FIG. 6, the identification information acquisition unit 170 acquires a user ID from the user terminal 200 as the user identification information. Here, the identification information acquisition unit 170 may acquire a user ID in the SNS service managed by the SNS server 130 as the user identification information by communicating with the SNS server 130.
[0052] The position information identification unit 172 identifies the boarding position information and the disembarking position information of each of the multiple user terminals 200 based on the distances between the multiple user terminals 200 and the vehicle 300. The boarding position information and the disembarking position information may be identified by short-range wireless communication between the user terminal 200 and the vehicle 300, or may be identified based on information obtained by GPS.
[0053] The storage unit 174 stores the operation identification information, the user identification information, the boarding position information, and the disembarking position information in association with each other. The above information is read from the database 115 connected to the calculation server 110 and temporarily stored in the hard disk 112 of the calculation server 110. However, the above information does not necessarily have to be stored in the hard disk 112. In other words, the above information is stored in association with each other in the database 115 connected to the calculation server 110, and the calculation 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 ratio of the cost to be borne by each of the multiple users who own the multiple user terminals 200 for the operation of the vehicle 300, based on the boarding position information and the alighting position information of each of the multiple user terminals 200. A specific calculation method of the ratio calculation unit 176 will be described later.
[0055] The fee calculation unit 178 calculates the amount to be paid by each of the multiple user terminals 200 based on the ratio calculated by the ratio calculation unit 176 and the travel fare for traveling the vehicle 300.
[0056] The notification unit 180 notifies the user terminals 200 using the shared ride of the charge calculated by the fare calculation unit 178. Here, the notification unit 180 can notify information such as the operation date and time, user information (name, telephone number, address, etc.) using the shared ride, boarding and alighting positions of each user, operation route, and payment status, in addition to the calculated charge. When the notification unit 180 notifies the user of map information such as the operation route, the notification can be performed by displaying it by a web view in which a process of displaying each position information is performed on the user terminal 200. These calculation results and the data notified to the user terminal 200 are stored in the database 115. Here, when the above information is notified to the user terminal 200 by another server or another system, the calculation server 110 does not need to have the notification unit 180.
[0057] Although not shown, the calculation server 110 may have an arrangement management unit in addition to the above-mentioned identification information acquisition unit 170, location information determination unit 172, memory unit 174, ratio calculation unit 176, fee calculation unit 178, and notification unit 180.
[0058] In the shared ride fare calculation system 10, when the user terminal 200 transmits an operation request, the dispatch management unit submits the operation request to the dispatch server 120. Here, the dispatch management unit may have a delay function so as to submit the operation request to the dispatch server 120 a predetermined period after the user terminal 200 transmits the operation request. Furthermore, the dispatch management unit can accept cancellation of the operation request from the user terminal 200 during the delay period. On the other hand, if the dispatch order is not canceled during the delay period, the dispatch management unit submits an operation request to the dispatch server 120.
[0059] The dispatch management unit may also notify the user terminal 200 of the location information of the user terminal 200 while the vehicle 300 is picking up the user, the location information of the vehicle 300, the location information of the destination, and traffic congestion information. The dispatch management unit may also provide the user terminal 200 with a means for making an inquiry (call or message) to the vehicle 300 while the vehicle 300 is picking up the user. The dispatch management unit may also provide the user terminal 200 that has used the vehicle 300 with a means for evaluating the used vehicle 300. Conversely, the dispatch management unit may also provide the vehicle 300 used by the user terminal with a means for evaluating the used user terminal 200. These evaluation results are stored in the database 115. Here, based on the evaluation results, the priority of the vehicle 300 used by the user terminal 200 or the priority of the user terminal 200 that provides the service of the shared ride fare calculation system 10 may be changed.
[0060] [Functional configuration of the communication terminal that requests operation] Fig. 7 is a block diagram showing the functional configuration of a communication terminal used in a shared ride fare calculation system according to an embodiment of the present invention. Fig. 7 provides a more detailed explanation of the functional blocks of the user terminal 200A of user A who makes an operation request, among the user terminals 200 in Fig. 2. According to Fig. 7, the user terminal 200A who makes an operation request has an operation request signal transmission unit 270, an identification information reception unit 272, a position information specification unit 274, and a fare information reception unit 276.
[0061] The operation request signal transmitting unit 270 transmits an operation request signal to the dispatch server 120, requesting operation of the vehicle 300. The identification information receiving unit 272 receives from the dispatch server 120 operation identification information that identifies the operation of the vehicle 300 that operates in response to the operation request transmitted by the operation request signal transmitting unit 270. Here, as described above, the operation identification information may be an operation log for each hire trip transmitted by wireless communication from the vehicle 300 to the dispatch server 120, or may be information on an order sheet stored by an employee in the dispatch server 120 or database 125. Alternatively, it may be a mixture of these.
[0062] The position information identification unit 274 identifies the boarding position information and the disembarking position information of the user terminal 200 based on the distance between the user terminal 200 boarding the vehicle 300 operating in response to the above-mentioned operation request and the vehicle 300. Although details will be described later, the boarding position information and the disembarking position 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 becomes equal to or less than a predetermined distance, or may be information obtained based on the distance between the position information of the user terminal 200 and the position information of the vehicle 300 obtained by GPS or the like.
[0063] The fare information receiving unit 276 receives the amount to be paid by the user, calculated based on the boarding position information and the disembarking position information identified by the position information identifying unit 274, and the operating fare for operating the vehicle 300.
[0064] [Functional configuration of passenger communication devices] Fig. 8 is a block diagram showing the functional configuration of a communication terminal used in a shared ride fare calculation system according to an embodiment of the present invention. Fig. 8 provides a more detailed explanation of the functional blocks of the user terminal 200B, which is a passenger in the vehicle 300 operated by the operation request of the user terminal 200A, among the user terminals 200 in Fig. 2. According to Fig. 8, the passenger user terminal 200B is similar to the functional blocks of the user terminal 200A of the user A who makes the operation request, but differs from the user terminal 200A in that the user terminal 200B does not have an operation request signal transmission unit 270.
[0065] Since the user terminal 200B does not need to make an operation request, it does not have to have the operation request signal transmission unit 270 as described above. However, this does not limit the user terminal 200B to not having the operation request signal transmission unit 270. Of course, the user terminal 200B may have the operation request signal transmission unit 270.
[0066] [Operation flow of the shared ride fare calculation system] Fig. 9 is a diagram showing an operation flow of the shared ride fare calculation system according to one embodiment of the present invention. In Fig. 9, the operation of each block of the shared ride fare calculation system 10 shown in Fig. 2 is explained in detail using a flowchart.
[0067] First, the user terminal 200A starts a program that operates the ride-sharing fare calculation system 10 (step S501). Here, an example of an interface displayed on the user terminal when the program of the ride-sharing fare calculation system 10 is started in step S501 is shown in Figs. 10 and 11. The interface 610 shown in Fig. 10 is a setting screen in the SNS service provided by the SNS server 130. As shown in Fig. 10, the interface 610 has a vehicle icon 611, and the program of the ride-sharing fare calculation system 10 is started by selecting the vehicle icon 611. Here, the interface 610 has multiple tabs at the bottom of the screen, such as a friend list tab 612, a talk tab 613, a timeline tab 614, and a miscellaneous tab 615. A tab for starting the program of the ride-sharing fare calculation system 10 may be arranged in one of these multiple tabs.
[0068] When the vehicle icon 611 of the interface 610 is selected, an interface 620 in Fig. 11 is displayed. The interface 620 is the top screen of the ride-sharing fare calculation system 10. When a request button 621 is selected in the interface 620, the calculation server 110 can be accessed from the user terminal 200.
[0069] Here, when using the shared fare calculation system 10 for the first time, a user registration interface 630 and a credit card information registration interface 631 shown in Figures 12 and 13 may be displayed. The interface 630 displays at least fields for inputting the name and telephone number of the user terminal 200. The interface 631 also displays at least fields for inputting the credit card number, expiration date, and PIN number.
[0070] Next, a request to operate the vehicle 300 is executed by the user terminal 200A (step S502). Here, FIG. 14 shows an example of an interface displayed on the user terminal when making a request to operate in step S502. The interface 640 shown in FIG. 14 is a map displayed by a web view function. The user uses the user terminal 200 to select a boarding position 600 on the map. A boarding position pin 641 is displayed as a landmark at the selected boarding position 600. In addition, a boarding position address 642 is displayed above the boarding position pin 641. When setting the selected boarding position 600, the position information of the boarding position 600 is set as the boarding position of the user terminal 200A by selecting a set button 643.
[0071] 14, the expected time required (15 minutes) from the current location of the user terminal 200 to the boarding position 600 is displayed on the boarding position pin 641. In addition, a plurality of vehicles 644 managed by the dispatch server 120 are displayed on the map. Here, the function of displaying the boarding position address 642, the time required to the boarding position 600, or the vehicle 644 may be omitted, and may be provided as an optional function.
[0072] In addition, in step S502, when the setting button 643 of the interface 640 shown in FIG. 14 is selected, an interface 650 is provided for confirming consent to transmitting the boarding position 600 and the information of the user terminal A to the calculation server 110, as shown in an example in FIG. 15. The interface 650 shown in FIG. 15 is a map displayed by a web view function. In the map shown in FIG. 15, a location information pin 652 is displayed at the boarding position 600 of the user terminal 200A. When the consent button 657 is selected by the user terminal 200A, the boarding position 600 is transmitted from the user terminal 200A to the calculation server 110.
[0073] 15 is provided with a user information confirmation field 653 displaying user information (name, phone number, etc.) of the user terminal 200, a user registered credit card information field 654 displaying credit card information registered in the shared fare calculation system 10, a coupon code field 655 displaying information on coupons owned by the user, a dispatch center information field 656 displaying information to be notified to the user terminal from the dispatch center, such as the pick-up fee, and a shuttle information field 658 displaying the expected pick-up time, etc. Here, it is sufficient for the interface 650 to have at least the function of confirming consent, and other functions can be omitted, or may be provided as optional functions.
[0074] As described above, when the user terminal 200A initiates an action of requesting operation by the shared fare calculation system 10, the user terminal 200A transmits an operation request signal 552 to the calculation server 110. Here, the operations of steps S501 and S502 may be executed by the user terminal 200B.
[0075] When the operation request signal 552 transmitted from the user terminal 200A is received by the calculation server 110, the calculation 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 calculation 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 after the operation request is confirmed in step S502. Also, during the delay period, the calculation server 110 may provide the user terminal 200A with an interface 660 for accepting cancellation of the operation request, for example, as shown in FIG. 16.
[0076] When the dispatch server 120 receives the operation request application signal 554, a pick-up instruction signal 556 is transmitted to the vehicle 300 managed by the dispatch center (step S541). Here, in step S541, the dispatch server 120 acquires information including the location information of the vehicle 300 managed by the dispatch center and the actual vehicle status of the vehicle 300 (empty vehicle, out of service, pick-up, hire, etc.) via the second network 102 of the dispatch center. Then, based on this information, the dispatch server 120 transmits the pick-up instruction signal 556 specifying the vehicle 300. If the vehicle 300 that received the pick-up instruction signal 556 is in an actual vehicle status that is actually available for pick-up, an acceptance signal 558 is returned from the vehicle 300 to the dispatch server 120 (step S521).
[0077] When the dispatch server 120 receives the acceptance signal 558 returned from the vehicle 300, the dispatch server 120 transmits an acceptance notification 560 to the calculation server 110 (step S542). When the calculation server 110 receives the acceptance notification 560, the calculation server 110 transmits a dispatch status notification 562 to the user terminal 200A (step S522). The dispatch status notification 562 includes information on the vehicle being picked up (such as vehicle type, vehicle number, driver information, actual vehicle status, etc.) and the current location of the vehicle 300. The dispatch status notification 562 may further include an estimated time of arrival at the location of the user terminal 200A aboard the vehicle 300, an estimated time of arrival at the location of the destination 400, traffic congestion information, etc.
[0078] The calculation server 110 may provide the user terminal 200A that has received the dispatch status notification 562 transmitted in step S522 with an interface 670 for accepting an inquiry about the vehicle 300 currently being picked up, as shown in Fig. 17. When the user wishes to make an inquiry about the vehicle 300 currently being picked up, the user can talk to the driver of the vehicle 300 using the interface 670 shown in Fig. 17. Then, when the vehicle 300 currently being picked up arrives at the location of the user terminal 200A, an interface 680 may be provided that notifies the user that the vehicle 300 has arrived, as shown in Fig. 18.
[0079] 18 may include an inquiry button 681 for connecting the user terminal 200A and the mobile phone of the driver of the vehicle 300 so that a call can be made when the user who is planning to board the vehicle cannot find the vehicle 300 (taxi). By pressing the inquiry button 681, the user terminal 200A can automatically call the mobile phone of the driver of the vehicle 300. Alternatively, by pressing the inquiry button 681, a call may be automatically made from the mobile phone of the driver of the vehicle 300 to the user terminal 200A. In addition, the interface 680 may include an estimated time of arrival 682 at the destination 400, a confirmation number 683 indicating that the user terminal 200 is the terminal that has requested operation, and a driver evaluation 684.
[0080] As described above, the user terminal 200A gets into the vehicle 300 (step S503). In step S503, when the user terminal 200A gets into the vehicle 300, first riding position information 564 indicating the riding position of the user terminal 200A in the vehicle 300 is generated and transmitted to the calculation server 110 (step S504). Here, the first riding position information 564 may be generated by the user terminal 200A based on the relative positional relationship between the user terminal 200A and the vehicle 300, or may be generated by the calculation server 110 based on the relative positional relationship between the user terminal 200A and the vehicle 300. The calculation server 110 receives the first riding position information 564 generated in step S504, and thereby the calculation server 110 acquires the first riding position information 564 (step S532). Here, the first riding position information 564 includes user identification information for identifying the user terminal 200A and the user terminal 200B. Here, the first riding position information 564 includes the user ID of the user terminal 200A as the user identification information.
[0081] The vehicle 300 with the user terminal 200A in it moves to the boarding position of the user terminal 200B and the user terminal 200B in it (step S511). In step S511, when the user terminal 200B gets in the vehicle 300, second boarding position information 566 indicating the boarding position of the 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 the user terminal 200B based on the relative positional relationship between the user terminal 200B and the vehicle 300 or the relative positional relationship between the user terminal 200B and the user terminal 200A in 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 the user terminal 200B and the vehicle 300 or the relative positional relationship between the user terminal 200B and the user terminal 200A in the vehicle 300. The calculation server 110 receives the second riding position information 566 generated in step S512, and thereby the calculation server 110 acquires the second riding position information 566 (step S533). Here, the second riding position information 566 includes user identification information for identifying the user terminal 200A and the user terminal 200B. Here, the second riding position information 566 includes the user ID of the user terminal 200B as the user identification information.
[0082] When the user terminals 200A and 200B and the vehicle 300 arrive at the destination (step S505), the user terminals 200A and 200B get off the vehicle 300 (steps S506 and S513). In step S506, when the user terminal 200A gets off the vehicle 300, first get-off position information 568 indicating the get-off position of the user terminal 200A from the vehicle 300 is generated and transmitted to the calculation server 110 (step S507). In addition, in step S513, when the user terminal 200B gets off the vehicle 300, second get-off position information 570 indicating the get-off position of the user terminal 200B from the vehicle 300 is generated and transmitted to the calculation server 110 (step S514).
[0083] Here, the first drop-off position information 568 may be generated by the user terminal 200A based on the relative positional relationship between the user terminal 200A and the vehicle 300, or may be generated by the calculation server 110 based on the relative positional relationship between the user terminal 200A and the vehicle 300. In addition, the second drop-off position information 570 may be generated by the user terminal 200B based on the relative positional relationship between the user terminal 200B and the vehicle 300, or may be generated by the calculation server 110 based on the relative positional relationship between the user terminal 200B and the vehicle 300.
[0084] The first drop-off location information 568 and the second drop-off location information 570 transmitted from the user terminals 200A and 200B are received (acquired) by the calculation server 110 (step S534). Here, the first drop-off location information 568 and the second drop-off location information 570 include user identification information for identifying the user terminal 200A and the user terminal 200B. Here, as the user identification information, the user ID held by the user terminal 200A is included in the first drop-off location information 568, and the user ID held by the user terminal 200B is included in the second drop-off location information 570.
[0085] Furthermore, when the vehicle 300 arrives at the destination in step S505, the vehicle 300 generates operation information 572 including the operation identification information and the operation fare, and reports this to the dispatch server 120 (step S523).
[0086] When the operation information 572 reported from the vehicle 300 is received by the dispatch server 120, the dispatch server 120 notifies the calculation server 110 of the operation information 574 including the operation identification information and the operation fare (step S543).
[0087] When the calculation server 110 receives the operation information 574 notified from the dispatch server 120, the calculation server 110 acquires the operation identification information and the operation fare included in the operation information 574 (step S535). Next, based on the operation identification information and the operation fare acquired in step S535, the burden ratio and the burden amount of the operation fare to be borne by each of the user terminal A and the user terminal B are calculated (step S536). Then, the calculation result 576 in step S536 (one or both of the calculated burden ratio and the burden amount) is notified to the user terminals 200A and 200B (step S537).
[0088] When the calculation result 576 notified from the calculation server 110 is received by the user terminals 200A and 200B, confirmation of the calculation result 576 is performed in each of the user terminals 200A and 200B (steps S508 and S515). When a selection to confirm the calculation result is made in steps S508 and S515 ("Yes" in steps S508 and S515), confirmation information 578 is transmitted from the user terminals 200A and 200B to the calculation server 110. On the other hand, when a selection to reject the calculation result is made ("No" in steps S508 and S515), the operation flow is terminated, and the program is terminated or the screen moves to the top screen.
[0089] When the calculation server 110 receives the confirmation information 578 transmitted from the user terminals 200A and 200B, the calculation server 110 performs billing 580 on the user terminals 200A and 200B (step S538). Then, the user terminals 200A and 200B execute payment for the billing in step S538 (steps S509 and S516).
[0090] Here, if the calculation result is rejected in steps S508 and S515, the calculation server 110 may charge the full amount of the travel fare to the user terminal 200A that requested the travel.
[0091] In the manner described above, the shared ride section can be calculated without increasing the burden on the user terminals 200A, 200B and the vehicle 300, and the share of the usage fee that is borne by the user terminals 200A, 200B using the shared ride can be calculated according to the travel distance.
[0092] [Calculation method for percentage calculation part] A calculation method of the ratio calculation unit 176 of the calculation server 110 shown in Fig. 6 will be described in detail with reference to Fig. 19. An example will be described in which the ratio calculation unit 176 in the shared fare calculation system 10 according to the first embodiment calculates the burden ratios of the user terminals 200A and 200B from the boarding ratios of the respective user terminals 200A and 200B on a route to the destination 400, in which the user terminal 200A, which is relatively far from the destination 400, boards first, and then the user terminal 200B boards together.
[0093] The ratio calculation unit 176 acquires the first boarding position information, the second boarding position information, the first disembarking position information, and the second disembarking position information in steps S532 to S534 in the operation flow of the shared fare calculation system 10 shown in Fig. 9. Then, based on the acquired position information, the distance Da between the boarding position of the user terminal 200A and the boarding position of the user terminal 200B, and the distance Db between the boarding position of the user terminal 200B and the destination 400 are calculated. Here, the first travel distance of the first journey in which the user terminal 200A boards the vehicle 300 is Da+Db, and the second travel distance of the second journey in which the user terminal 200B boards together with the user terminal A is Db.
[0094] In the example of FIG. 19, the ratio calculation unit 176 calculates the ratio of the second travel distance (Db) to the first travel distance (Da+Db) as the riding ratio. Here, a method of calculating the riding ratio based on the travel distance in the first and second steps is exemplified, but the method is not limited to this method. For example, the riding ratio may be calculated based on the second travel time required for the travel in the second step relative to the first travel time required for the travel in the first step. In other words, the ratio calculation unit 176 calculates the burden ratio that each of the multiple users should bear for the operation of the vehicle 300 based on the actual travel distance of each of the multiple users using the vehicle 300 or the actual travel time required for the travel distance.
[0095] Here, the distances Da and Db are distances on a road map. For example, the distance Da is the distance of a route on a road map from the boarding position of the user terminal 200A to the boarding position of the user terminal 200B. Note that the distance on the road map is not the straight-line distance between two points, but the distance when moving based on the road map. However, the distances Da and Db are not limited to the distance on the road map, and may be the straight-line distance connecting each piece of position information.
[0096] In addition, in FIG. 19, the ratio calculation unit 176 has exemplified a case in which the user terminals 200A and 200B get on the vehicle 300 at different positions and get off the vehicle 300 at the same destination 400, but the present invention is not limited to this case. For example, the ratio calculation unit 176 may calculate the share of the cost for a route in which the user terminals 200A and 200B get on the vehicle 300 at the same position and get off the vehicle 300 at different destinations. Alternatively, the ratio calculation unit 176 may calculate the share of the cost for a route in which the user terminals 200A and 200B get on the vehicle 300 at different positions and get off the vehicle 300 at different destinations. For example, the user terminal 200B may get on the vehicle 300 in which the user terminal 200A gets on, and the share of the cost may be calculated for a route in which the user terminal 200A gets off the vehicle 300 first.
[0097] [Method of acquiring user boarding and alighting location information] Here, a method for acquiring the user's boarding position information and alighting position information by the position information identification unit 172 will be described in detail with reference to FIG. 20. FIG. 20 is a diagram showing an example of a method for determining whether a user has boarded or alighted in a shared ride fare calculation system according to an embodiment of the present invention. As shown in FIG. 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 becomes equal to or less than a first distance D1. When the vehicle 300 has the short-range wireless communication unit 320, the short-range wireless communication unit 320 may be provided in a Point-Of-Sale terminal (POS terminal) provided in the vehicle 300 or in a communication terminal carried by the driver.
[0098] When the distance between the user terminal 200B and the vehicle 300 becomes equal to or shorter than 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. That is, when the distance between the user terminal 200B and the vehicle 300 becomes equal to or shorter than 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 calculation server 110 that the specific information signal has been received. Then, the position information identification unit 172 of the calculation server 110 determines that the user terminal 200B has boarded the vehicle 300 or that the user terminal 200B has dismounted from the vehicle 300 based on the specific information signal.
[0099] As described above, the position information identification unit 172 acquires the position information when the user terminal 200B boards the vehicle 300, thereby acquiring second boarding position information indicating the boarding position of the user terminal 200B into the vehicle 300. In the example of Fig. 20, since the user terminal 200B boards the vehicle 300 in which the user terminal 200A boarded, the second boarding position information corresponds to the start position of the ride-sharing of the user terminals 200A and 200B.
[0100] As described above, according to the ride-sharing fare calculation system 10 of embodiment 1 of the present invention, it is possible to provide a calculation server that calculates the ride-sharing section without increasing the burden on the user and the vehicle driver, and calculates the usage fare burden rate of the user who uses the ride-sharing based on the travel distance, and a communication terminal that communicates with the calculation server.
[0101] First Modification of First Embodiment A modified example of one embodiment of the present invention will be described with reference to Fig. 21. Fig. 21 is a diagram showing an example of a method for determining whether a user gets on or off in a shared ride fare calculation system according to a modified example of one embodiment of the present invention. A shared ride fare calculation system 11 according to modified example 1 of embodiment 1 differs from the shared ride 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 becomes equal to or shorter than a first distance D1.
[0102] When the distance between the user terminal 200B and the vehicle 300 becomes equal to or shorter than the first distance D1, the short-range wireless communication unit 215 transmits an information signal specific to the short-range wireless communication unit 215 to the vehicle 300. That is, when the distance between the user terminal 200B and the vehicle 300 becomes equal to or shorter than the first distance D1, the vehicle 300 receives an information signal specific to the short-range wireless communication unit 215 from the short-range wireless communication unit 215. When the vehicle 300 receives the information signal specific to the short-range wireless communication unit 215, it transmits to the dispatch server 120 that it has received the unique information signal. Then, the unique information signal is transmitted from the dispatch server 120 to the calculation server 110, and the location information identification unit 172 of the calculation server 110 acquires second boarding position information indicating the boarding position of the user terminal 200B in the vehicle 300 in which the user terminal 200A has boarded, based on the unique information signal. As in FIG. 20, in the example of FIG. 21, the user terminal 200B rides in the vehicle 300 in which the user terminal 200A rides, so the second riding position information corresponds to the starting position of the ride-sharing of the user terminals 200A and 200B.
[0103] Second Modification of First Embodiment A modified example of an embodiment of the present invention will be described with reference to Figs. 22 to 24. Fig. 22 is a diagram showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system according to a modified example of an embodiment of the present invention. As shown in Fig. 22, the position information identification unit 172 of the shared ride fare calculation system 12 according to the modified example 2 of the first embodiment determines that the user terminal 200B has boarded the vehicle 300 when the distance between the position information of the user terminal 200B and the position information of the vehicle 300 is equal to or less than the second distance D2. Then, based on the position information of the user terminal 200B or the vehicle 300 when it is determined that the user terminal 200B has boarded the vehicle 300, second boarding position information indicating the position where the user terminal 200B has boarded the vehicle 300 is acquired.
[0104] On the other hand, when the distance between the position information of the user terminal 200B and the position information of the vehicle 300 becomes greater than the second distance D2, the position information identification unit 172 determines that the user terminal 200B has dismounted from the vehicle 300. Then, based on the position information of the user terminal 200B or the vehicle 300 when it is determined that the user terminal 200B has dismounted from the vehicle 300, it acquires second dismounting position information indicating the position where the user terminal 200B has dismounted from the vehicle 300.
[0105] 22, when the vehicle 300 enters within a radius of the second distance D2 from the user terminal 200B, it is determined that the user terminal 200B has boarded the vehicle 300. Also, when the vehicle 300 goes out of the radius of the second distance D2 from the user terminal 200B, it is determined that the user terminal 200B has disembarked from the vehicle 300, as at a disembarking determination time 720.
[0106] Next, a function for further improving the accuracy of boarding / alighting determination will be described. FIG. 23 is a diagram showing an example of a method for determining whether a user has boarded or alighted in a shared ride fare calculation system according to a modified embodiment of the present invention. As shown in FIG. 23, the position information identification unit 172 may determine that the user terminal 200B is boarding the vehicle 300 when the distance between the position information of the user terminal 200B and the position information of the vehicle 300 is equal to or less than the second distance D2, and further, when the position information of the user terminal 200B and the position information of the vehicle 300 are moving in the same direction. On the other hand, as shown in FIG. 24, the position information identification unit 172 may determine that the user terminal 200A has alighted from the vehicle 300 when the position information of the vehicle 300 is moving in a direction different from that of the position information of the user terminal 200B.
[0107] <Modification 3 of the First Embodiment> A modified example of an embodiment of the present invention will be described with reference to Figures 25 to 27. Figure 25 is a diagram showing an overview of a calculation method of a calculation server used in a shared ride fare calculation system according to a modified example of an embodiment of the present invention.
[0108] [Calculation method for percentage calculation part] As shown in FIG. 25, the ratio calculation unit 176 calculates the share of the burden based on a first estimated distance Ea from the first boarding position 410 of the user terminal 200A (first user) who boarded first to the destination 400 and a second estimated distance Eb from the second boarding position 420 of the user terminal 200B (second user) who boarded with the user terminal 200A after the user terminal 200A to the destination 400. In other words, the first estimated distance Ea is the distance when the user terminal 200A moves from the first boarding position 410 to the destination 400 without carpooling, and the second estimated distance Eb corresponds to the distance when the user terminal 200B moves from the second boarding position 420 to the destination 400 without carpooling. In other words, the ratio calculation unit 176 calculates the share of the burden of each of the multiple user terminals 200A and 200B based on the distance when each of them uses the vehicle 300 independently from the boarding position to the drop-off 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, and may be straight-line distances connecting each piece of position information.
[0109] [Method of acquiring user boarding and alighting location information] Next, a method for acquiring the first boarding position information at the first boarding position 410 and the second boarding position information at the second boarding position 420 will be described with reference to Fig. 26 and Fig. 27. Here, a case will be described in which the vehicle 300 has a short-range wireless communication unit 320. Fig. 26 and Fig. 27 are diagrams showing an example of a method for determining whether a user has boarded or disembarked in a shared ride fare calculation system according to a modified example of one embodiment of the present invention.
[0110] First, as shown in FIG. 26, when the distance between the user terminal 200A and the vehicle 300 becomes equal to or shorter than a predetermined distance, the user terminal 200A receives an information signal unique to the short-range wireless communication unit 320 from the short-range wireless communication unit 320. When the user terminal 200A receives the unique information signal, the user terminal 200A transmits to the calculation server 110 that the unique information signal has been received. Then, the calculation server 110 determines that the user terminal 200A has boarded the vehicle 300 based on the unique information signal. Then, the position information identification unit 172 acquires first boarding position information indicating the boarding position of the user terminal 200A in the vehicle 300.
[0111] Next, as shown in FIG. 27, when the distance between the user terminal 200B and the vehicle 300 becomes equal to or shorter than a predetermined distance, the user terminal 200B receives an information signal unique to the short-range wireless communication unit 320 from the short-range wireless communication unit 320. When the user terminal 200B receives the unique information signal, the user terminal 200B transmits to the calculation server 110 that the unique information signal has been received. Then, the calculation server 110 determines that the user terminal 200B has boarded the vehicle 300 based on the unique information signal. Then, the position information identification unit 172 acquires second boarding position information indicating the boarding position of the user terminal 200B in the vehicle 300.
[0112] Then, when the user terminals 200A, 200B and the vehicle 300 arrive at the destination 400, the user terminals 200A, 200B get off the vehicle 300, and the user terminals 200A, 200B are no longer able to receive an information signal specific to the short-range wireless communication unit 320 from the short-range wireless communication unit 320, it is determined that the user terminals 200A, 200B have got off the vehicle 300. Then, the position information identification unit 172 acquires first alighting position information and second alighting position information indicating the alighting positions of the user terminals 200A, 200B from the vehicle 300.
[0113] When using a shared ride along the route shown in Fig. 25 to Fig. 27, the user terminal 200B travels the same distance whether or not it shares a ride, but the user terminal 200A travels a different distance whether or not it shares a ride. In other words, the user terminal 200A travels a longer distance than necessary to accommodate the user terminal 200B. According to the shared ride fare calculation system 13 according to the third modification of the first embodiment, even in such a case, a fair share of the fare can be calculated.
[0114] As described above, according to the ride-sharing fare calculation system 13 according to the third modification of the first embodiment of the present invention, a calculation server that calculates a ride-sharing section without increasing the burden on the user and the vehicle driver and calculates the burden ratio of the usage fee according to the riding distance of the user who uses the ride-sharing, and a communication terminal that communicates with the calculation server can be provided, as in the first embodiment. Furthermore, even if the travel distance is longer than necessary when traveling to the destination by ride-sharing compared to the case of traveling to the destination without using the ride-sharing, a fair burden ratio can be calculated.
[0115] Second Embodiment A shared ride fare calculation system according to the second embodiment of the present invention will be described in detail with reference to FIG. 28 and FIG. 29. The overview of the shared ride 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 shared ride fare calculation system 10 according to the first embodiment, and therefore will not be described here. In the second embodiment, the user terminal 200 receives the fare from the vehicle 300 by communicating with the fare meter of the vehicle 300. In the second embodiment, the function of the communication terminal is different from that of the first embodiment and its modified example. Therefore, the functional configuration of the communication terminal of the second embodiment will be described here, and the description of the other configurations will be omitted. Here, the user terminal 200 may directly communicate 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 dispatch server 120 and the calculation server 110.
[0116] [Functional configuration of the communication terminal that requests operation] A communication terminal for requesting operation used in the shared fare calculation system 20 according to the second embodiment will be described. The functional configuration of the user terminal 200A used in the shared fare calculation system 20 is similar to that of the user terminal 200A used in the shared fare calculation system 10 according to the first embodiment shown in FIG. 7, but differs from the user terminal 200A used in the shared fare calculation system 10 in that it has a fare information receiving unit 278 that receives fare information including the fare from the fare meter of the vehicle 300, and a fare information transmitting unit 280 that transmits the fare information received by the fare information receiving unit 278 to the calculation server 110. Here, the fare information receiving unit 278 does not need to directly communicate with the vehicle 300 or the fare meter of the vehicle 300, and for example, the fare information receiving unit 278 may communicate with the vehicle 300 or the fare meter of the vehicle 300 via one or both of the dispatch server 120 and the calculation server 110.
[0117] [Functional configuration of passenger communication devices] Fig. 29 is a block diagram showing the functional configuration of a communication terminal used in a shared ride fare calculation system according to an embodiment of the present invention. Fig. 29 provides a more detailed explanation of the functional blocks of the user terminal 200B, which is a passenger in the vehicle 300 operated by the operation request of the user terminal 200A, among the user terminals 200 in Fig. 2. According to Fig. 29, the passenger user terminal 200B is similar to the functional blocks of the user terminal 200A of the user A who makes the operation request, but differs from the user terminal 200A in that the user terminal 200B does not have an operation request signal transmission unit 270.
[0118] Since the user terminal 200B does not need to make an operation request, it does not have to have the operation request signal transmission unit 270 as described above. However, this does not limit the user terminal 200B to not having the operation request signal transmission unit 270. Of course, the user terminal 200B may have the operation request signal transmission unit 270.
[0119] As described above, according to the ride-sharing fare calculation system 20 of the second embodiment of the present invention, as in the first embodiment, it is possible to provide a calculation server that calculates a ride-sharing section without increasing the burden on the user and the vehicle driver, and calculates the share of the usage fee according to the riding distance of the user who uses the ride-sharing, and a communication terminal that communicates with the calculation server. Also, by enabling communication between the fare meter of the vehicle 300 and the user terminal 200, data can be exchanged more efficiently.
[0120] The calculation server and the communication terminal described in the above embodiment can be realized by a program or application that operates the computer included in the calculation server and the communication terminal. The program or application can be downloaded and installed in the calculation server and the communication terminal via Internet communication. Also, the program or application can be installed in the calculation server and the communication terminal via a computer-readable recording medium.
[0121] The present invention is not limited to the above-described embodiment, and can be modified as appropriate without departing from the spirit and scope of the present invention. [Explanation of symbols]
[0122] 10, 11, 12, 20: Shared 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: Dispatch server, 130: SNS server, 170: Identification information acquisition unit, 172: Location information determination 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 button, 250: Speaker, 260: Microphone, 270: Operation request signal transmission unit, 272: Identification information receiving unit, 274: Location information specifying 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 position, 420: Second boarding position, 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 position information, 566: Second boarding position information, 568: First drop-off position information, 570: Second drop-off position information, 572, 574: Operation information, 576: Calculation result, 578: Confirmation information, 580: Request, 600: Boarding position, 610, 620, 630, 640, 650, 660, 670, 680: Interface, 611: Vehicle icon, 612: Friend list tab, 613: Chat tab, 614: Timeline tab, 615: Other tabs, 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 registered credit card information field, 655: Coupon code field, 656: Dispatch center information field, 657: Agree button, 658: Pick-up information field, 681: Inquiry button, 682: Estimated arrival time, 683: Confirmation number, 684: Driver evaluation, 710: When boarding decision, 720: When disembarking decision
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, Based on the fact that a dispatch instruction for the vehicle is accepted by the first terminal among the first terminal and the second terminal, transmitting the dispatch instruction and user information of the first user to an information processing server that communicates with a third terminal of the vehicle; acquiring, by the first terminal, first boarding position information where the first user boards the vehicle and first alighting position information where the first user alights from the vehicle, and transmitting the information to the information processing server; acquiring second boarding position information where the second user associated with the first user boards the vehicle and second disembarking position information where the second user disembarks from the vehicle by the second terminal, and transmitting the second boarding position information to the information processing server; acquiring, by the first terminal, a first fare to be paid by the first user out of the fare for the vehicle; and acquiring, by the second terminal, a second fare to be paid by the second user out of the fare for the vehicle; the first fare borne by the first user is calculated based on a first distance assumed to be traveled by the first user alone on the vehicle from a first boarding position corresponding to the first boarding position information to a first alighting position corresponding to the first alighting position information; the second fee borne by the second user is calculated based on a second distance assumed to be traveled by the second user alone on the vehicle from a second boarding position corresponding to the second boarding position information to a second alighting position corresponding to the second alighting position information; program.
2. The program according to claim 1, acquiring the first riding position information by the first terminal based on the fact that the distance between the first terminal and the vehicle becomes equal to or shorter than a predetermined distance, and transmitting the first riding position information to the information processing server; program.
3. The program according to claim 2, acquiring the second riding position information by the second terminal based on the fact that the distance between the second terminal and the vehicle becomes equal to or shorter than a predetermined distance, and transmitting the second riding position information to the information processing server; program.
4. The program according to claim 2, The determination that the distance between the first terminal and the vehicle is equal to or shorter than a predetermined distance is performed by short-range wireless communication. program.
5. The program according to claim 2, When a distance between the first terminal and the vehicle becomes equal to or greater than a predetermined distance, the first terminal acquires the first drop-off position information and transmits the information to the information processing server. program.
6. The program according to claim 1, displaying an estimated time of arrival at the destination on the first terminal before the first user gets on the vehicle; program.
7. The program according to claim 1, after transmitting the dispatch instruction for the vehicle from the first terminal to the information processing server, displaying an object for canceling the dispatch instruction on the first terminal; program.
8. The program according to claim 1, After transmitting the dispatch instruction of the vehicle from the first terminal to the information processing server, an identification number of the vehicle is displayed on the first terminal. program.
9. The program according to claim 1, After transmitting the dispatch instruction of the vehicle from the first terminal to an information processing server, displaying on the first terminal a confirmation number assigned to the first user and information prompting the first user to convey the confirmation number to a driver of the vehicle. program.
10. The program according to claim 1, The first terminal of the first user and the second terminal of the second user are terminals that do not form an approved exchange relationship with each other other than through the application. program.
11. The program according to claim 1, after the first terminal receives the dispatch instruction, an object for contacting the driver of the vehicle from the first terminal is displayed on the first terminal via the application; program.
12. The program according to claim 1, when the vehicle arrives at the position of the first user, displaying, on the first terminal via the application, an object for communication between the first terminal and the third terminal based on the user information; program.
13. An information processing method 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, comprising: Based on the fact that a dispatch instruction for the vehicle is accepted by the first terminal among the first terminal and the second terminal, transmitting the dispatch instruction and user information of the first user to an information processing server that communicates with a third terminal of the vehicle; acquiring, by the first terminal, first boarding position information where the first user boards the vehicle and first alighting position information where the first user alights from the vehicle, and transmitting the information to the information processing server; acquiring second boarding position information where the second user associated with the first user boards the vehicle and second disembarking position information where the second user disembarks from the vehicle by the second terminal, and transmitting the second boarding position information to the information processing server; acquiring, by the first terminal, a first fare to be paid by the first user out of the fare for the vehicle; and acquiring, by the second terminal, a second fare to be paid by the second user out of the fare for the vehicle; the first fare borne by the first user is calculated based on a first distance assumed to be traveled by the first user alone on the vehicle from a first boarding position corresponding to the first boarding position information to a first alighting position corresponding to the first alighting position information; the second fee borne by the second user is calculated based on a second distance assumed to be traveled by the second user alone on the vehicle from a second boarding position corresponding to the second boarding position information to a second alighting position corresponding to the second alighting position information; Information processing methods.
Citation Information
Patent Citations
Method for signal transmission between communication station
JP1995222126A
Taxi allocation processing system, vehicle terminal, user terminal and allocation center server
JP2003109190A
Carpool reserving system
JP2003167946A
Taxi arrangement system, reservation acceptance server, and method of taxi arrangement
JP2003281422A
Message exchanging system
JP2004318393A
Cited By
System and Program
JP2026173735A
System and Program
JP2026173736A
System and Program
JP2026173737A
System and Program
JP2026173738A
System and Program
JP2026173739A
