JP2021071983A - Server device, program, user terminal device, and system - Google Patents

Abstract

To provide a server device with which it is possible to realize cashless payment of a charge by simple means, without specifically requiring additional communication means to a vehicle side as transport means.SOLUTION: A server device includes a structure below. A user function unit receives use record data from a user's terminal device that includes transport operator identification information for identifying a transport operator which does a transport service and information pertaining to an amount of a transport charge. A data storage unit accumulates the received use record data. A determinant function unit executes a process of approving the use of the transport service by the user at least before or after the transport service is carried out, and adds information to the approved use record data indicating as having been approved. A transport company function unit provides the terminal device of a transport operator with the use record data sorted for each transport operator, on the basis of the approved use record data.SELECTED DRAWING: Figure 2

Description

The present invention relates to server devices, programs, user terminal devices, and systems.

It is desirable for organizations such as companies to efficiently collect and aggregate taxi fare information used for business purposes. For example, when a paper taxi ticket is used, it takes a lot of time and effort (manpower) to manage the distribution of the taxi ticket and to convert the amount of the taxi fare written on the paper into data and aggregate it. Therefore, it is conceivable to improve the efficiency of these data processes by using information devices and communication.

For example, in paragraph 0002 (column of background technology) of Patent Document 1, "a taxi ticket information such as taxi ticket identification information is transmitted from a management system that manages taxi tickets to a portable device such as a mobile phone or an IC card. The taxi ticket processing method that memorizes and reads the taxi ticket information stored in the portable device carried by the taxi user and the taxi device installed in the taxi setstles the taxi usage fee, and the taxi ticket settlement. "System" is described.

Further, the taxi ticket processing system is described in the column of the embodiment of Patent Document 1.

Specifically, in paragraph 0030, the ticket generation system receives the ticket application information from the ticket application server and accepts the taxi ticket generation request (S210), and the taxi company selection unit stores it in the taxi company information DB. Select a taxi company (S230) based on the taxi company information and ticket application information provided, and the mobile phone receives this e-mail (S310) and connects to the URL included in the e-mail (S310). S320), it is described that the authentication information is transmitted and the taxi ticket application is requested to be downloaded (S330).

Further, in paragraph 0031, the user who downloaded the taxi ticket application to the mobile phone starts this application and displays the ticket data and the taxi company information on the display, and the user displays the taxi ticket based on the service content and the like. Select one of the taxi companies to be used, the mobile phone will call the phone number, the user will request a vehicle dispatch, and short-range wireless communication (infrared) between the mobile phone and the taxi device when the user gets on board. Etc.), and the ticket data is transmitted to the taxi device (S410), and the taxi device receives the ticket data (S510) and determines whether or not it is available (S520). ing. In other words, the taxi device can use the ticket data when the validity of the ticket data can be confirmed based on the electronic signature and the current position, time, etc. can be confirmed to meet the restrictions of the usage restriction information. It is stated that it is determined to be present.

Further, in paragraph 0025, the taxi device is a device mounted on the taxi that calculates and setstles the taxi usage fee, and includes a mobile phone, a data management server of a taxi company, a ticket payment server of a payment agency, and the like. It is possible to communicate, and the taxi device installed in each taxi is a communication device that controls communication with a data management server and a ticket settlement server, and a short-distance that controls short-range wireless communication with a mobile phone. It is stated that it is equipped with a communication device and the like.

Further, in paragraph 0027, the data management server is capable of communicating with a taxi device, a ticket settlement server, etc. via a communication line, and is a server that manages data processing in a taxi company. The management server receives usage record information from the taxi device, stores and manages each taxi ID, and the data management server charges the usage fee for which payment processing was performed based on the ticket data in the stored usage record information. It is stated that it will be aggregated on a regular basis and the aggregated result will be sent to the ticket settlement server of the settlement agency to request payment of this fee.

JP-A-2007-018304

However, various problems remain in the technique described in Patent Document 1.

For example, in the method of "the taxi ticket information stored in the portable device carried by the taxi user is read by the taxi device installed in the taxi and the taxi usage fee is settled", the taxi usage fee is settled. Communication with the taxi device is required, and the cost of the device itself and the cost of increasing the scale of the software become excessive.

Further, the method in which the taxi company selection unit 33 (on the server side) selects a taxi company based on the taxi company information and the ticket application information stored in the taxi company information DB 36 is a method for the user to select a taxi company. It is inconvenient in that the degree of freedom of taxi is narrowed, and there is an inconvenience that the processing load such as selection of a taxi company is applied to the server side before boarding a taxi.

Further, the method in which the mobile phone 40 requests the download of the taxi ticket application based on the received e-mail is inconvenient because the user is required to download (and install) the application more than necessary. is there.

Further, the process of transferring ticket data between the mobile phone 40 and the taxi device 50 by communication such as short-range wireless communication (infrared ray or the like) is complicated in procedure, and it is desirable to avoid it if possible.

Further, in the system described in Patent Document 1, it is difficult to incorporate an approval process regarding taxi use on the side of an organization such as a company.

The present invention has been made based on the above-mentioned problem recognition, does not require an additional communication means on the taxi side (vehicle side for transportation means), uses a low-cost device, and is a simple means. It is intended to provide a server device, a program, a user terminal device, and a system capable of realizing cashless payment of taxi charges and the like.

[1] In order to solve the above problems, the server device according to one aspect of the present invention uses the transportation company identification information for identifying the transportation company that provides the transportation service and the amount of the transportation fee from the terminal device of the user. The user function unit that receives the usage record data including the information of the above, the data storage unit that stores the received usage record data, and the use of the transportation service by the user are the implementation of the transportation service. For the decision-maker function unit that executes the process of approving at least either before or after and adds information indicating that it is approved to the approved usage record data, and the terminal device of the transportation company. , A transportation company functional unit that provides the usage record data sorted by transportation company.

[2] Further, in one aspect of the present invention, in the above server device, the transportation company identification information is optically applied to the transportation means possessed by the transportation company and used for the transportation service. The code information provided in a readable form is acquired by the terminal device of the user.

[3] Further, in one aspect of the present invention, in the server device, the user's terminal device reads the code information at the start of the transportation service, and the user function unit reads the code information. The carrier identification information based on the code information is received from the user's terminal device as a part of the service start record.

[4] Further, in one aspect of the present invention, in the above server device, the terminal device of the user is the transportation fee after the amount of the transportation fee for the transportation service is determined at the end of the transportation service. The user function unit receives the information on the amount of the transportation fee from the terminal device of the user as a part of the service termination record.

[5] Further, in one aspect of the present invention, in the above server device, the terminal device of the user acquires information on the amount of the transportation fee by manual input of the user.

[6] Further, in one aspect of the present invention, in the above server device, when the transportation company functional unit provides the usage record data for the transportation company to the terminal device of the transportation company. , In the unit of implementation of the transportation service, the usage record data is also transmitted together with information indicating whether or not the transportation company has confirmed, and it is instructed that the usage record data has been confirmed from the terminal device of the transportation company. Information indicating that the usage record data has been confirmed is added to the usage record data.

[7] Further, in one aspect of the present invention, in the above server device, when the transportation company functional unit provides the usage record data for the transportation company to the terminal device of the transportation company. , In the unit of implementation of the transportation service, information indicating whether or not the transportation company has been charged for the usage record data is also transmitted, and the charge has been charged from the terminal device of the transportation company. With respect to the usage record data instructed to be, information indicating that the charge has been charged is added.

[8] Further, one aspect of the present invention further includes a usage record confirmation unit for confirming the contents of the usage record data in the server device, and the user function unit is provided at the start of the transportation service. , The information of the time at the start of the transportation service and the information of the position at the start of the transportation service are received from the terminal device of the user, and at the end of the transportation service, the time at the end of the transportation service. And the information of the position at the end of the transportation service are received from the terminal device of the user, and the data storage unit receives the information of the time at the start of the transportation service as a part of the usage record data. And, the information of the position at the start of the transportation service, the information of the time at the end of the transportation service, and the information of the position at the end of the transportation service are stored. By referring to the attendance data representing the attendance status of the user, the attendance data, the information of the time at the start of the transportation service, the information of the position at the start of the transportation service, and the information of the position at the start of the transportation service, and the end of the transportation service It is determined whether or not the time information and the position information at the end of the transportation service meet a predetermined alert condition, and if the alert condition is met, the usage record. It raises an alert about the data.

[9] Further, one aspect of the present invention is usage record data including transportation company identification information for identifying a transportation company that provides transportation services and information on the amount of transportation charges from a user's terminal device. Approve the use of the transportation service by the user, the user function unit that receives the data, the data storage unit that stores the received usage record data, and at least before or after the implementation of the transportation service. The decision-maker function unit that executes the processing to add information indicating that the usage record data has been approved and the terminal device of the transportation company are sorted by the transportation company. It is a program for operating a computer as a server device equipped with a transportation company functional unit that provides usage record data.

[10] Further, one aspect of the present invention is to identify a transportation company that provides a transportation service by reading code information provided in an optically readable form in the transportation means used for the transportation service. Acquires the transportation company identification information, acquires the information on the amount of the transportation fee, and transmits the usage record data including the information on the identification information of the transportation company and the information on the amount of the transportation fee to the server device. It is a user terminal device.

[11] Further, in one aspect of the present invention, in the user terminal device, the user terminal device includes the transportation company identification information by reading the code information at the start of the transportation service. After transmitting the usage record data to the server device and determining the amount of the transportation fee, the user manually inputs the information of the amount of the transportation fee and obtains the information of the amount of the transportation fee, and the usage including the information of the amount of the transportation fee. The actual data is transmitted to the server device, a confirmation screen including information on the amount of the transportation fee is displayed, and the usage actual data is confirmed when the "register" button included in the confirmation screen is operated. The confirmation notification, which is the notification of the above, is transmitted to the server device.

[12] Further, in one aspect of the present invention, in the user terminal device, after transmitting the application data for using the transportation service to the server device and transmitting the confirmation notification to the server device. , The ticket number given by the server device in association with the application data is displayed on the screen.

[13] Further, one aspect of the present invention is usage record data including transportation company identification information for identifying a transportation company that provides transportation services and information on the amount of transportation charges from a user's terminal device. Approve the use of the transportation service by the user, the user function unit that receives the data, the data storage unit that stores the received usage record data, and at least before or after the implementation of the transportation service. The decision-maker function unit that executes the processing to add information indicating that the usage record data has been approved and the terminal device of the transportation company are sorted by the transportation company. The transportation business by reading code information provided in an optically readable form in a server device including a transportation company functional unit that provides usage record data and a transportation means used for the transportation service. In addition to acquiring the person identification information, the information on the amount of the transportation fee is acquired, and the usage record data including the information on the identification information of the transportation company and the information on the amount of the transportation fee is transmitted to the server device. It is a system including a human terminal device.

According to the present invention, it is possible to realize the settlement of a taxi or the like by a simple means by using a low-cost device without requiring an additional communication means on the vehicle side for the transportation means.

It is a block diagram which shows the structural example of the taxi use support system by 1st Embodiment of this invention. It is a block diagram which showed the configuration (including the schematic configuration of the communication network) of the taxi use support system by the same embodiment in more detail. It is a block diagram which shows the schematic functional structure in the server apparatus by the same embodiment. It is a sequence diagram which shows the typical processing procedure (pre-approval by a deciding person, and the use of a taxi) of the taxi use support system by this embodiment. It is a sequence diagram which shows the typical processing procedure (post-approval by a deciding person) of the taxi use support system by the same embodiment. It is a schematic diagram which shows the example of the code information (two-dimensional code) for identifying the taxi company (business operator) which is the target of use in the same embodiment. It is a schematic diagram which shows the example of the screen displayed on the mobile terminal device for a user at the time of operation of the taxi use support system by the same embodiment (before getting on a taxi). It is a schematic diagram which shows the example of the screen displayed in the mobile terminal device for a user at the time of operation of the taxi use support system by the same embodiment (immediately after the completion of boarding confirmation). It is a schematic diagram which shows the example of the screen displayed in the mobile terminal device for a user at the time of operation of the taxi use support system by the same embodiment (input of the amount of money at the time of getting off). It is a schematic diagram which shows the example of the screen displayed in the mobile terminal device for a user at the time of operation of the taxi use support system by the same embodiment (at the time of getting off confirmation). It is a schematic diagram which shows the example of the screen displayed in the mobile terminal device for a user at the time of operation of the taxi use support system by the same embodiment (when registration is completed in the latter case). In the same embodiment, it is a schematic diagram showing data generated at each stage of getting on a taxi, a waypoint, and getting off, and the flow thereof. It is a part of the data managed by the server device by this embodiment, and is the schematic which shows the structure of the table which holds the information for identifying a taxi company and a car. It is a part of the data managed by the server apparatus by the same embodiment, and is the schematic which shows the structure of the table which holds the information about the user of a system. It is a part of the data managed by the server device according to the same embodiment, and is a schematic diagram showing the structure of a table for accumulating individual taxi usage status. It is a block diagram which shows the schematic function composition in the 1st user function part by the same embodiment. It is a block diagram which shows the schematic function composition in the 2nd user function part by the same embodiment. It is a block diagram which shows the schematic function composition in the decision-maker function part by the same embodiment. It is a block diagram which shows the schematic functional composition in the taxi company functional part by the same embodiment. It is a block diagram which shows the schematic functional structure in the administrator function part by the same embodiment. It is a block diagram which shows the schematic function composition of the 1st user function part in the taxi use support system by 2nd Embodiment.

[First Embodiment]
Next, an embodiment of the present invention will be described with reference to the drawings. In the taxi use support system 1 according to the present embodiment, for example, when a user belonging to an organization (company or the like) uses a taxi, for example, using a mobile terminal device, at least information for identifying the taxi company, taxi fare, etc. It records the amount of money information. Such a record is called a taxi usage record. The user may obtain the approval of the decision-maker (for example, the user's superior) prior to the use of the taxi or after the use of the taxi. The taxi usage record is accumulated in the database on the server device 10 side. The data stored in the database can be used by users, decision makers, taxi use support system 1 managers (including accounting staff), and taxi company staff according to the scope of their access privileges. You can browse and check. Since the information for identifying the taxi company is included in the usage record, the server device 10 can aggregate the charges and the like for each taxi company. In addition, the person in charge of the taxi company can process the charge based on the data of the usage record for the company. By using the taxi use support system 1, in principle, it is possible to accumulate and aggregate usage records without using paper taxi tickets (paper tickets), and reduce the time and effort required for handling paper. be able to. Further, when the taxi use support system 1 includes a function for the approval process, the approval process, the taxi use process, and the ex post facto settlement process can be executed consistently. In addition, the taxi use support system 1 can automatically confirm the relationship between the work status and the taxi usage record by taking in the data of the attendance status of the user.

In the present embodiment, paid transportation services such as taxi, hire, shared taxi, bus, and car service are collectively referred to as "taxi". When the present embodiment is applied to a means of transportation other than a taxi, "taxi" should be appropriately read as appropriate. Further, in the present embodiment, the "taxi company" is a business operator (company, individual, etc.) that provides the above-mentioned transportation service such as a taxi. In other words, the "taxi company" does not necessarily have to be a company. Further, the "organization" that operates the taxi use support system 1 of the present embodiment is a corporation such as a company, a public institution, various business entities, or the like. Further, in the present embodiment, the taxi use support system 1 provides an information processing function for users, decision makers, and managers in the above-mentioned "organization". Here, the "user" is a person who uses a taxi for business purposes. The "decision person" is a person who has the authority to approve the use of a taxi by the above user (usually, the superior of the user's organization). The "manager" is a person who manages the operation of the taxi use support system 1. The manager is typically a general affairs person or a human resources person in a company or the like. Further, in the present embodiment, the manager may include an accounting person in a company or the like.

FIG. 1 is a block diagram showing a configuration example of a taxi use support system according to the present embodiment. As shown in the figure, the taxi use support system 1 includes a server device 10, an in-house terminal device 20, a user mobile terminal device 30, and a taxi company terminal device 40. The server device 10 can communicate with the in-house terminal device 20, the user mobile terminal device 30, and the taxi company terminal device 40 via a communication network. Note that the figure does not show the physical configuration of the communication network in the system. Further, here, one server device 10, an in-organization terminal device 20, a user mobile terminal device 30, and a taxi company terminal device 40 are shown, but the number of these devices is It is optional.

The server device 10 is a device for storing necessary data in this system and processing the data. The server device is realized by using, for example, a server-type computer. Further, the server device 10 may be physically realized by using a plurality of server-type computers.

The in-organization terminal device 20 is a terminal device used inside the organization. The in-house terminal device 20 functions as a client for the server device 10 described above. The organization terminal device 20 is realized by using, for example, a PC (personal computer), a tablet terminal, a smartphone, or the like. In the organization terminal device 20, a web browser and various applications (application programs) can be operated. The in-house terminal device 20 is used by users, decision makers, and administrators.

The user mobile terminal device 30 is a terminal device that can be used by a user of this system (a person who gets on a taxi) while moving. The user mobile terminal device 30 is also simply referred to as a "user terminal device". The user mobile terminal device 30 functions as a client for the server device 10 described above. The user mobile terminal device 30 may have a function of authenticating the user. Specifically, the authentication function of the user mobile terminal device 30 authenticates an individual user by using a password, a passcode, a fingerprint of the individual user, a face, a voiceprint, or the like. By performing such personal authentication, the user mobile terminal device 30 guarantees that the intended user is operating. Further, the user mobile terminal device may perform authentication using the user code issued by the server device 10. The user code is code information issued by the user code issuing function unit 1220 or the like on the server device 10 side, as will be described later. The user mobile terminal device 30 stores the user code issued on the server device 10 side internally. When the user mobile terminal device 30 accesses the server device 10, the user mobile terminal device 30 reads the user code stored inside and transmits the user code to the server device 10. The server device 10 verifies the validity of the user code received from the user mobile terminal device 30 (whether or not it is a legitimately issued user code, etc.), and from the user mobile terminal device 30. Accept only valid access. When the user mobile terminal device 30 transmits, for example, a user code that has already been deleted on the server device 10 side or a user code that has not been properly issued, the server device 10 denies access. To do. Further, even when the user code is updated (reissued) for a certain user, the server device 10 denies the access by the past (pre-update) user code. In this way, by using the user code, the validity of the access from the user mobile terminal device 30 to the server device 10 is verified. The user mobile terminal device 30 is realized by using, for example, a smartphone, a wearable terminal device, a tablet terminal, a PC, or the like. The user mobile terminal device 30 can operate a web browser and various applications.

The taxi company terminal device 40 is a terminal device used by the taxi company. The taxi company terminal device 40 functions as a client for the server device 10 described above. The taxi company terminal device 40 is realized by using, for example, a PC, a tablet terminal, or the like. The taxi company terminal device 40 can operate a web browser and various applications.

The function executed by the in-house terminal device 20, the user mobile terminal device 30, and the taxi company terminal device 40 may be an application running on a web browser, or may be run without using a web browser. It may be an application in the form of a browser.

FIG. 2 is a block diagram showing the configuration of the taxi use support system 1 shown in FIG. 1 in more detail. FIG. 2 also shows a schematic configuration of a communication network. In the configuration shown here, the taxi utilization support system 1 is realized by using a group of devices connected to the external network 61 and a group of devices connected to the internal network 62. As shown in the figure, the taxi use support system 1 includes a server device 10, an in-house terminal device 20, a user mobile terminal device 30, a taxi company terminal device 40, a relay device 50, and an external network 61. , Intra-organizational network 62.

As shown in the figure, in the present embodiment, the server device 10 is composed of the cloud server device 11 and the internal server device 12. That is, the cloud server device 11 and the in-house server device 12 share functions. The cloud server device 11 and the in-house server device 12 are connected to different communication networks, respectively. The cloud server device 11 is connected to the external network 61. Further, the internal server device 12 is connected to the internal network 62. Here, the external network 61 is an open network provided outside the organization. For example, the Internet can be used as the external network 61. Further, the intra-organization network 62 is a closed network within the organization.

The cloud server device 11 can communicate with the user mobile terminal device 30 and the taxi company terminal device 40 via the external network 61.
In addition, the internal server device 12 can communicate with the internal terminal device 20 via the internal network 62. Further, the relay device 50 relays between the external network 61 and the internal network 62. The cloud server device 11 and the internal server device 12 can communicate with each other via the relay device 50. As a result, data updates can be synchronized between the data held by each of the cloud server device 11 and the internal server device 12.

The user mobile terminal device 30 has a GPS (Global Positioning System) function. By receiving the GPS signal from the GPS satellite 71, the user mobile terminal device 30 can acquire information on the position of its own device, for example, in the form of latitude and longitude.

FIG. 3 is a block diagram showing a schematic functional configuration in the server device 10. As already described, the server device 10 can be realized by using the cloud server device 11 and the in-house server device 12. The in-organization server device 12 itself may be realized in a so-called cloud configuration. As shown in the figure, the cloud server device 11 includes a first data storage unit 110, a first user function unit 111, and a taxi company function unit 112. Further, the in-organization server device 12 includes a second data storage unit 120, a second user function unit 121, a determiner function unit 122, an administrator function unit 123, and a usage record confirmation unit 124. Will be done. Each of these functional units can be realized by, for example, a computer and a program. In addition, each functional unit has a storage means, if necessary. The storage means is, for example, a variable on the program or a memory allocated by executing the program. Further, if necessary, a non-volatile storage means such as a magnetic hard disk device or a solid state drive (SSD) may be used. Further, at least a part of the functions of each functional unit may be realized not as a program but as a dedicated electronic circuit. The outline of the function of each part is as described below.

The first data storage unit 110 stores the data used by the cloud server device 11. The data of the first data storage unit 110 can be read and written from within the cloud server device 11. The details of the data stored in the first data storage unit 110 will be described later with reference to another drawing.

The first user function unit 111 provides necessary data to the user mobile terminal device 30, and acquires data from the user mobile terminal device 30 side.

The taxi company function unit 112 provides necessary data to the taxi company terminal device 40, and acquires data from the taxi company terminal device 40 side.

The second data storage unit 120 stores the data used by the server device 12 in the organization. The data of the second data storage unit 120 can be read and written from the server device 12 in the organization. The details of the data stored in the second data storage unit 120 will be described later with reference to another drawing.

A part of the data content may be duplicated between the first data storage unit 110 and the second data storage unit 120. As described above, the cloud server device 11 and the internal server device 12 can communicate with each other, and data is periodically synchronized between the first data storage unit 110 and the second data storage unit 120. .. For example, so-called master data is mainly maintained and updated on the server device 12 side in the organization, but the necessary data is also passed to the cloud server device 11 side. In addition, the data representing the transaction record (taxi usage record) is mainly acquired first on the cloud server device 11 side, and is also passed to the in-organization server device 12 side in a timely manner.

The second user function unit 121 presents data to the user or acquires data from the user side via the terminal device 20 in the organization. In addition, the second user function unit 121 writes data to the second data storage unit 120 as appropriate.

The decision-maker function unit 122 presents data to the decision-maker or acquires data from the decision-maker side via the terminal device 20 in the organization. In addition, the decision-maker function unit 122 writes data to the second data storage unit 120 as appropriate.

The administrator function unit 123 presents data to the administrator or acquires data from the administrator side via the terminal device 20 in the organization. Further, the administrator function unit 123 writes data to the second data storage unit 120 as appropriate.

The usage record confirmation unit 124 confirms the contents of the taxi usage record data stored in the second data storage unit 120. Specifically, the usage record confirmation unit 124 generates an alert (turns on the alert flag) with respect to the data that matches the predetermined alert condition among the data of the individual taxi usage record. In addition, the usage record confirmation unit 124 may take in the attendance data of the user (employee of the organization) from the outside (for example, the attendance management system) and refer to it in order to confirm the usage record. The attendance data includes information on the work status (commuting time, leaving time, holidays, vacation, etc.) of the user on each day. Specific alert conditions will be described later.

The contents of more specific functions included in the cloud server device 11 and the internal server device 12 will be further described later.

FIG. 4 is a sequence diagram showing a typical processing procedure (pre-approval by a decision-maker and use of a taxi) of the taxi use support system 1. Hereinafter, the operation of the taxi use support system 1 when the user uses a taxi will be described with reference to this sequence diagram.

The procedure from steps S1 to S4 is a procedure for the user to apply for use in advance and the decision-maker to approve it. This pre-approval is not mandatory for taxi use. Subsequent approval may be given by the decision-maker as described below.

In step S1, the user's in-house terminal device 20 transmits the usage application data to the in-house server device 12 based on the user's operation. The information regarding this usage application is stored in the server device 10.

In step S2, based on the operation of the deciding person, the in-organization server device 12 transmits the data of the usage application list to the in-organization terminal device 20 for the deciding person. The in-organization terminal device 20 for the decision-maker displays the information of the usage application list on the screen.

In step S3, based on the operation of the deciding person who saw the usage application information, the in-house terminal device 20 for the deciding person transmits the usage application approval data to the in-organization server device 12. In response to this, the in-house server device 12 updates the status of the application to "approved".

In step S4, based on the user's operation, the in-house server device 12 transmits the data of the usage application list to the in-organization terminal device 20 for the user of the application. The in-organization terminal device 20 for the user displays the information of the application list on the screen. As a result, the user can know whether or not the application filed by the user has been approved. The information in the usage application list may be made available to the user by using the user mobile terminal device 30.

The procedure from steps S5 to S7 is a process of the taxi use support system 1 from the time when the user actually gets on the taxi to the time when the user gets off the taxi. It should be noted that the procedures from steps S5 to S7 can be executed regardless of whether or not the usage application has been made in advance and whether or not the usage application has been approved in advance.

In step S5, the user mobile terminal device 30 transmits the boarding registration data to the cloud server device 11 via the Internet or the like. The process of this step is performed by operating the user mobile terminal device 30 when the user gets on a taxi. The boarding registration data transmitted at this time includes a user code for identifying the user, code information for identifying the taxi company (and, in some cases, the taxi car number), and boarding position information ( Latitude and longitude) and date and time. The user code is held in advance by the user mobile terminal device 30. The code information for identifying the taxi company (and, in some cases, the taxi car number) is obtained by the user mobile terminal device 30 optically reading the two-dimensional code information provided in the taxi. .. The boarding position information is acquired based on the GPS signal received from the GPS satellite 71 by the user mobile terminal device 30.

In step S6, the user mobile terminal device 30 transmits the waypoint registration data to the cloud server device 11 via the Internet or the like. The process of this step is performed by the user operating the user mobile terminal device 30 when the taxi stops at the stopover. The boarding registration data sent at this time includes a user code for identifying the user, code information for identifying the taxi company (and, in some cases, the taxi car number), and stopover information (in some cases, the taxi car number). Latitude and longitude) and included.

In step S7, the user mobile terminal device 30 transmits the disembarkation registration data to the cloud server device 11 via the Internet or the like. The processing of this step is performed by operating the mobile terminal device 30 for the user when the user gets off the vehicle. The boarding registration data transmitted at this time includes a user code for identifying the user, code information for identifying the taxi company (and, in some cases, the taxi car number), and information on the disembarkation position (disembarkation position information). Latitude and longitude), tolls (eg, taxi meter tolls and non-meter toll road tolls), and date and time information.

FIG. 5 is a sequence diagram showing a processing procedure (post-approval by the decision-maker) in the taxi use support system 1. The procedure from steps S8 to S11 is a process of the taxi use support system 1 when the deciding person subsequently approves the taxi after the user has used the taxi. If the decision-maker has given approval in advance, this subsequent approval is not essential.

In step S8, based on the operation of the user, the in-house server device 12 transmits the data of the usage record list to the in-house terminal device 20 for the user. The in-organization terminal device 20 for the user displays the information of the usage record list on the screen. As a result, the user can confirm the information of the usage record. In addition, when there is a usage record that requires complementary input, the user can perform complementary input from the in-organization terminal device 20 for the user.

In step S9, based on the user's operation, the user's internal terminal device 20 transmits complementary data to the internal server device 12. The data corresponding to this complement includes the data complemented and input by the user.

In step S10, based on the operation of the deciding person, the in-organization server device 12 transmits the data of the usage record list to the in-organization terminal device 20 for the deciding person. The in-organization terminal device 20 for the decision-maker displays the information of the usage record list on the screen. As a result, the decision-maker can approve the usage record information.

In step S11, based on the operation of the deciding person, the in-house terminal device 20 for the deciding person transmits the data of approval of the usage record to the in-organization server device 12. In response to this, the server device 12 in the organization updates the status of its usage record to "approved".

FIG. 6 is a schematic diagram showing an example of code information for identifying the taxi company (business operator) used, its branch office, and the like. This code information is printed on a medium such as paper and can be optically read by the user mobile terminal device 30. In the illustrated example, the code information is a two-dimensional code. An example of a two-dimensional code is a QR code (registered trademark). However, the code information may be represented by a method other than the two-dimensional code (for example, a bar code, characters, etc. Also, for example, RFID (radio frequency identifier, wireless identification tag) or the like may be used for user mobile. The terminal device 30 may be able to read the code information by the radio signal (radio wave). This code information is provided or placed in the taxi vehicle, for example.

This code information includes at least information that uniquely identifies the taxi company (business operator). Further, the code information may further include information that identifies a branch office, a branch office, a department, or the like, such as a taxi company. Further, the code information may include information (vehicle number) that identifies an individual vehicle of the taxi. That is, a two-dimensional code is generated based on the information that identifies the taxi company and the information that identifies the vehicle. When the user uses the taxi, the user's mobile terminal device 30 reads this code information, so that the user's mobile terminal device 30 acquires at least information that identifies the taxi company that operates the taxi. In addition, the user mobile terminal device 30 can transmit at least information identifying the taxi company to the server device 10.

As shown in the figure, the taxi company identification information "0001" and the taxi company name "OO taxi" may be printed in characters together with the two-dimensional code.

Next, the user interface displayed on the user mobile terminal device 30 will be described. 7 to 11 are schematic views showing an example of a user interface (screen) displayed on the user's mobile terminal device 30 when the user uses a taxi in the taxi use support system 1.

FIG. 7 is a schematic view showing a screen displayed on the user mobile terminal device 30 before boarding registration. As shown in the figure, this screen includes three buttons, "boarding record", "waypoint record", and "getting off record". The user can execute the function corresponding to each button by selecting one of the buttons (operation such as tapping).

When the user selects "boarding record" on the screen shown in FIG. 7, the user mobile terminal device 30 executes a function for registering the boarding record. Specifically, the user mobile terminal device 30 acquires the current position (boarding position) by GPS and reads the code information (FIG. 6) provided in the taxi. In addition, the user mobile terminal device 30 stores a user code for identifying the user in advance. In addition, the user mobile terminal device 30 acquires the current date and time (boarding date and time) from the internal clock. Then, the user mobile terminal device 30 records the boarding record including the current position (boarding position) information, the code information read from the taxi, the user code, and the current date and time (boarding date and time). The data is transmitted to the cloud server device 11 and registered. The user mobile terminal device 30 may register the boarding record in the form of associating the usage application information (ticket number) previously made by the user.

FIG. 8 is a schematic view showing a screen displayed on the user mobile terminal device 30 after boarding registration. As shown in the figure, this screen includes two buttons, "Record of waypoints" and "Record of getting off". The user can execute the function corresponding to each button by selecting one of the buttons (operation such as tapping).

When the user selects "waypoint record" on the screen shown in FIG. 8, the user mobile terminal device 30 executes a function for registering the waypoint record. Specifically, the user mobile terminal device 30 acquires the current position (via position) by GPS. In addition, the user mobile terminal device 30 stores a user code for identifying the user in advance. In addition, the user mobile terminal device 30 acquires the current date and time (via date and time) from the internal clock. Then, the user mobile terminal device 30 transmits the data of the waypoint record including the current position (via position) information, the user code, and the current date and time (via way date and time) to the cloud server device 11. ,sign up. If there is no waypoint, that is, if the taxi goes straight from the boarding position to the getting-off position, the operation of registering this waypoint is unnecessary.

When the user selects "getting off record" on the screen shown in FIG. 8, the user mobile terminal device 30 executes a function for registering the getting off record. The screens for that purpose are the following FIGS. 9, 10, and 11.

FIG. 9 is a screen for the user to input the amount of money and the like when getting off the taxi. As shown in the figure, this screen is provided with a field for inputting the reason for use, the boarding fee, and the toll road fee. The reason for use is a field for the user to enter the reason for using this taxi. For example, the user interface may be such that the reason for use can be selected from several options. In addition, the reason for use selected by the user at the time of application may be displayed as the default on this screen. In addition, numerical values can be entered in the fare and toll road fare fields. This screen also includes a button called "Get off confirmation". The user can press (for example, tap) this "getting off confirmation" button after inputting information such as the boarding fee. When the "Get off confirmation" button is pressed, the user mobile terminal device 30 transmits the input data to the cloud server device 11. In addition, the mobile terminal device 30 for users also uses a cloud server for the current position (getting off position) acquired by GPS, the user code stored in advance, and the current date and time (getting off date and time) acquired from the internal clock. It is transmitted to the device 11.

FIG. 10 is a disembarkation confirmation screen. This disembarkation confirmation screen is displayed on the user mobile terminal device 30 after the "disembarkation confirmation" button is pressed on the screen shown in FIG. The disembarkation confirmation screen of FIG. 10 is displayed on the mobile terminal device 30 for users by the cloud server device 11, and includes items such as a taxi company, a vehicle number, a boarding fee, a toll road fee, a total, a boarding date and time, and a disembarking date and time. Includes data.

The taxi company and the vehicle number displayed on the screen of FIG. 10 are based on the data transmitted by the user mobile terminal device 30 to the cloud server device 11. The cloud server device 11 obtains taxi company name information from taxi company identification information by referring to master data (described later). The car number may not be specified, in which case it will not be displayed. Further, the boarding fee and the toll road fee are based on the values input on the screen of FIG. Further, the total is the sum of the boarding fee and the toll road fee, and is a value calculated on the cloud server device 11 side based on the value input on the screen of FIG. The boarding date and time and the disembarking date and time are data transmitted from the user mobile terminal device 30 to the cloud server device 11 at the time of boarding and disembarking, respectively.

In addition, the information about the waypoint may be further displayed on the above-mentioned disembarkation confirmation screen.

The disembarkation confirmation screen includes a "decision / boarding information registration" button and a "correction" button. When the user presses the "decision / boarding information registration" button (operation such as tapping), the information to the effect of registration is transmitted to the cloud server device 11 side, and the data displayed on the disembarkation confirmation screen is transferred to the cloud server. The device 11 is confirmed. Further, when the user presses the "correction" button, for example, the user can return to the screen display of FIG. 9 and perform an operation of correcting the data. When confirming the data, the user may show the screen to the taxi service provider (driver, etc.) to confirm each other.

FIG. 11 is a disembarkation record completion screen. After the "decision / boarding information registration" button is pressed on the disembarkation confirmation screen of FIG. 10, the screen shifts to the disembarkation record completion screen of FIG. This disembarkation record completion screen is also displayed on the mobile terminal device 30 for users by the cloud server device 11, and includes a taxi company, a car number, a boarding fee, a toll road fee, a total, and a boarding date and time. , Includes data for each item of disembarkation date and time and ticket number. This disembarkation record completion screen is for confirming the data confirmed on the server side. The user may show the disembarkation record completion screen to a taxi service provider (driver, etc.) and confirm the contents of the screen. In addition, since the ticket number is displayed on the user's mobile terminal device 30 for the first time at the stage of the disembarkation record completion screen, the taxi service provider (driver, etc.) must confirm that the data has been confirmed on the server side. Can be done. In addition, the taxi service provider can easily refer to the usage record data later by making a note of this ticket number in the crew record or other documents.

FIG. 12 is a schematic diagram summarizing the data generated at each stage of getting on a taxi, a waypoint, and getting off, and the flow thereof. As shown in the figure, when boarding a taxi, the user mobile terminal device 30 transmits and registers the boarding record to the server device 10. The boarding record includes data such as a user code, a ticket number, a boarding date and time, a boarding position, and taxi company code information. When the server device 10 receives the boarding record, the data is written in the storage means. Further, when the taxi passes through the waypoint, the user mobile terminal device 30 transmits and registers the waypoint record to the server device 10. The waypoint record includes data such as a user code, a ticket number, a waying date and time, and a waying position. When the server device 10 receives the waypoint record, the data is written in the storage means. The waypoint record enables registration of, for example, 0 times or more and N times or less (N is a non-negative integer, and N = 10 as an example) for each getting on and off of a taxi. As shown in the figure, when the taxi is disembarked, the user mobile terminal device 30 transmits and registers the disembarkation record to the server device 10. The disembarkation record includes data such as a user code, a ticket number, a disembarkation date and time, a disembarkation position, a fare (meter fare), a toll road fare, and a reason for use. When the server device 10 receives the disembarkation record, the data is written in the storage means. The charge information may be manually input by the user on the screen of the terminal device or the like.

FIG. 13 is a schematic diagram showing a configuration of a table (taxi master) that is a part of data managed by the server device 10 and holds information for identifying a taxi company, its branches, and individual vehicles. .. This table is configured as two-dimensional tabular data and has data items such as a taxi company code, a taxi company name, a branch code, a branch name, and a car number. The taxi company code is a code given to each business operator for the taxi use support system 1. In the illustrated example, codes such as 0001 and 0002 are assigned. The taxi company name is the name of the company or the like. In the illustrated example, the name of the company whose taxi company code is 0001 is "OO taxi". The name of the company whose taxi company code is 0002 is "△△ automobile". The branch code is a code for identifying a branch office, branch office, branch office, department, branch office, or the like of a taxi company. Further, the branch code may be a code for identifying another taxi company (or individual) who has a business alliance with the taxi company. For example, when a plurality of taxi companies form a union and a taxi company code is given to the union itself or a taxi company representing the union (also referred to as a "ticket handling company"), the union is given a taxi company code. A branch code may be given to a member taxi company. The "union" mentioned here is a union of businesses for jointly billing charges. The branches, branch offices, branch offices, branch offices, business alliance companies, etc. mentioned here may be referred to as "branches" or "branches, etc." on behalf of them. The branch name is the name of the above-mentioned branch or the like. In the illustrated example, in a company with a taxi company code of 0001, a Yoyogi branch with a branch code of 0321 and a Shinagawa branch with a branch code of 0322 are registered. A branch code is not used in a company with a taxi company code of 0002. The vehicle number is a number assigned to identify each vehicle. In the illustrated example, the car number is not used in the company whose taxi company code is 0001. Further, in a company whose taxi company code is 0002, a vehicle number from 0001 to 0500 is assigned and used. The two-dimensional code illustrated in FIG. 6 is created by a predetermined calculation procedure based on, for example, a combination of a taxi company code and a vehicle number. If you read the two-dimensional code, you will get the taxi company code, branch code, and car number. Further, when the data of FIG. 13 is searched using the taxi company code and the branch code as keys, the information of the taxi company name and the branch name can be obtained, respectively.

FIG. 14 is a schematic diagram showing a configuration of a table (user master) that is a part of data managed by the server device 10 and holds information about users of the system. As shown, this table contains data items such as user code, name, department code, home address, and home latitude / longitude. The data items of the home address and the home latitude / longitude may be held only in the table on the server device 12 side in the organization, and may not be held in the table on the cloud server device 11 side. The user code is given for the taxi use support system 1 and is code information for individually identifying the user. The name is the name of the user. The department code is code information for identifying the department to which the user belongs in the organization. The home address is the home address of the user. Home latitude / longitude is information representing the position of the user's home in latitude and longitude. It is possible to convert an address to latitude and longitude by searching the database. In addition, the taxi use support system 1 may refer to the home address and its latitude / longitude information for the processing of generating the alert described later. In addition, access control is performed so that only a limited number of people (for example, the person himself / herself) can refer to the home address and its latitude / longitude information.

FIG. 15 is a schematic diagram showing a configuration of a table for accumulating individual taxi usage status, which is a part of data managed by the server device 10. Each row in this table corresponds to a single taxi ride. As shown, this table contains data items such as confirmation date and time, ticket number, taxi company code, vehicle number, user code, boarding date and time, disembarking date and time, boarding section, reason for use, boarding fee, toll road fee.

The meaning of the data of each item is as follows. The confirmation date and time is the date and time when the data at the time of getting off is finally confirmed. The ticket number is a number corresponding to one taxi use. The ticket number is issued, for example, when a usage application is made or when a boarding record is registered without a usage application. The taxi company code and the vehicle number are as described with reference to FIG. The user code is as described with reference to FIG. The boarding date and time is the date and time when the process of registering the boarding record is performed. The disembarkation date and time is the date and time when the process of registering the disembarkation record is performed. The boarding section is data composed based on the position information at the time of registration of the boarding record and the position information at the time of registration of the disembarkation record. Each of the boarding position and the disembarking position may be represented by latitude and longitude, or may be represented by a place name or facility name obtained based on latitude and longitude. The reason for use, the boarding fee, and the toll road fee are the data registered at the time of getting off. The above confirmation date / time, boarding date / time, and disembarking date / time are expressed in the format of, for example, "YYYY / MM / DD hh: mm" (year / month / day, hour / minute).

The taxi usage status of all users is accumulated in a single table having the structure shown in FIG.

Next, the internal functional configuration of each functional unit will be described with reference to the respective diagrams of FIGS. 16 to 20.

FIG. 16 is a block diagram showing a schematic functional configuration in the first user function unit 111. As shown in the figure, the first user function unit 111 includes a boarding registration function unit 1111, a waypoint registration function unit 1112, and a disembarkation registration function unit 1113.

The boarding registration function unit 1111 registers in the database that the user has boarded a taxi. The boarding registration function unit 1111 acquires the taxi code information (at least including the information for identifying the taxi company) read by the user mobile terminal device 30. In addition, the boarding registration function unit 1111 acquires other data collected at the time of boarding from the user mobile terminal device 30. The items of data acquired by the boarding registration function unit 1111 at the time of boarding are as described with reference to FIG. 12 and the like.

The waypoint registration function unit 1112 registers in the database that the user has passed through the waypoint. The waypoint registration function unit 1112 acquires and saves the waypoint record data as described with reference to FIG. 12 and the like.

The disembarkation registration function unit 1113 registers in the database that the user has disembarked. The disembarkation registration function unit 1113 acquires and stores the disembarkation record data as described with reference to FIG. 12 and the like.

FIG. 17 is a block diagram showing a schematic functional configuration in the second user function unit 121. As shown in the figure, the second user function unit 121 includes a home registration function unit 1212, a usage application function unit 1213, a usage application list function unit 1214, a usage record list function unit 1215, and an alert response function unit 1216. , Complementary function unit 1217 and the like.

The home registration function unit 1212 has a function of registering a user's home address. The home registration function unit 1212 writes the home address entered by the user in the table shown in FIG. 14, based on, for example, the operation of the user. At the same time, the home registration function unit 1212 obtains the latitude and longitude of the user's home by referring to geographic data (not shown) based on the registered home address, and the table shown in FIG. Write to.

The usage application function unit 1213 processes the taxi usage application by the user. The usage application function unit 1213 attaches the scheduled boarding date, the scheduled boarding section (the place name of the boarding position, the place name of the disembarking position, and the place name of the waypoint if necessary) to the terminal device 20 in the organization for the user. Display a screen for entering information such as the reason for use and the decision-maker who should approve the application (some items are selected from the options). When the user inputs the data of those items (selects some items) and presses the "apply" button, the usage application function unit 1213 registers the application. In addition, the usage application function unit 1213 is in a state where an appropriate decision-maker can approve the usage application. The usage application list function unit 1214, which will be described later, displays information indicating whether or not the application has been approved. In addition, when the user gets on a taxi, the ride can be associated with the application for use (for example, the application can be selected at the time of boarding).

In addition, the usage application function unit 1213 enables the usage application to be registered in the absence of the decision-maker when the decision-maker who should approve the application is absent (for example, temporarily out of the office). You may. Further, the usage application function unit 1213 may accept the application while leaving some items blank among the data items to be input at the time of application. When these applications are made without a decision-maker or some items are left blank, the complementary function unit 1217, which will be described later, provides a function for supplementing these shortages.

Further, the usage application function unit 1213 may provide a user interface that can collectively perform a plurality of usage applications. For example, when a specific boarding section is used repeatedly every day, a function that allows a user to collectively apply for a plurality of usage applications (a plurality of ticket numbers can be collectively applied) is convenient.

The usage application list function unit 1214 causes the in-house terminal device 20 for users to display list information of taxi usage applications of a specific user (logged-in user). As a result, the user can collectively grasp the status of the usage application (for example, whether or not it has already been approved). The usage application list function unit 1214 may accept search conditions for narrowing down the usage applications to be displayed. The search conditions may include, for example, the user name, the status of the usage application (whether or not it has already been approved), the period for narrowing down the application date, and other conditions related to free words.

The usage record list function unit 1215 has a function of displaying information that allows the user to list the usage record on the in-house terminal device 20 for the user. The usage record list function unit 1215 may accept search conditions for narrowing down the usage record to be displayed. Search conditions include, for example, the user name, the period for narrowing down the date of use, the condition indicating whether or not complementary input is required, the reason for use, the presence or absence or type of alert, and other free words ( For example, a condition related to (search term for boarding section, etc.) may be included. When the search condition is specified by the user, the usage record list function unit 1215 displays only the usage record that matches the specified search condition in a list.

The alert response function unit 1216 has a function that enables the user to take an action to respond to the alert when an alert regarding the usage record has occurred. For example, when there is a usage record including an alert, the alert response function unit 1216 displays a supplementary explanation column so that the user can input a supplementary explanation regarding the alert. Supplementary explanations are accepted, for example, as free text. The alert response function unit 1216 stores the supplementary explanation input by the user in a form associated with the usage record. In addition, the alert response function unit 1216 enables the decision-maker to display the supplementary explanation when viewing the usage record of the user. As a result, the decision-maker can determine whether or not to approve the usage record based on the supplementary explanation input by the user.

Complementary support function unit 1217 has a function for the user to perform complementary input with respect to the usage record requiring complementation. Complementary support is required, for example, in the following cases. As described above, when applying for use, the user can make an application in the absence of a decision-maker, or make an application with some items blank. Regarding the application with these shortages and the usage record based on the application, the complement support function unit 1217 displays that it is "complementary input required". Then, the supplementary function unit 1217 displays a supplementary explanation column for the application that is "complementary input required" so that the user can input the supplementary explanation. Supplementary explanations are accepted as text. The supplementary function unit 1217 stores the supplementary explanation input by the user in a form associated with the application. In addition, the complementary function unit 1217 makes it possible to display the supplementary explanation together when the deciding person browses the application (or the usage record based on such an application) that has been complemented and input. As a result, the decision-maker can determine whether or not to approve the usage record based on the content complemented by the user (supplementary explanation, etc.).

In addition to the above cases (partially blank or absent decision-maker), the Complementary Support Function Unit 1217 similarly "complements required" for applications for specific reasons of use according to the class to which the user belongs. It may be treated as "input". As an example, when a user belonging to a specific class uses a reason for use other than "emergency", "nighttime", and "morning drive", the complementary function unit 1217 regards the application as "complementary input required". deal with.

FIG. 18 is a block diagram showing a schematic functional configuration in the determiner function unit 122. As shown in the figure, the decision-maker function unit 122 includes a user code issuing function unit 1220, a usage application approval function unit 1221, a usage application list function unit 1222, a usage record list function unit 1223, and an alert response function unit 1224. And the complementary function unit 1225.

The user code issuing function unit 1220 issues a user code to the user. The user code is code information in the taxi use support system 1. The user code issuing function unit 1220 displays, for example, a list of potential users (employees, etc.) so that the decision-maker can select the person to be issued the user code with a check box or the like. To. The user code issuing function unit 1220 issues a new user code to a user selected based on the operation of such a determiner. The user code is determined so as not to be duplicated with other users by, for example, using a serial number. The user code issuing function unit 1220 writes the issued user code in the user code field of the table shown in FIG.

The user code issuing function unit 1220 sends the issued user code to the user after the issuance of the user code is completed. As an example, the user code issuing function unit 1220 embeds an encrypted user code or a plain text user code in a character string of a URL (uniform resource locator) in the text of an e-mail. The user who receives this accesses the resource represented by the URL from, for example, the user mobile terminal device 30. Then, the application running on the web browser in the mobile terminal device 30 for the user writes the user code in the storage means in the mobile terminal device 30 for the user. Alternatively, the web browser itself writes the user code into a storage means (for example, a storage unit of management information of the browser). As a result, the user mobile terminal device 30 can read the user code of the user from the storage means and use it when executing the function for the user.

The usage application approval function unit 1221 has a function for the decision-maker to approve the usage application. Specifically, the usage application approval function unit 1221 causes the in-house terminal device 20 for the decision-maker to display a list of applications that require approval by the decision-maker. The usage application approval function unit 1221 may accept search conditions for narrowing down the applications to be displayed as a list. In addition, the usage application approval function unit 1221 provides a means for selecting whether or not to approve those applications collectively or individually for each application (for example, a "approval" or "denial" button). It is displayed on the in-house terminal device 20 for the decision-maker. Then, according to the operation of the deciding person, the usage application approval function unit 1221 performs a process of approving or denying those applications. If the application is approved, the approved flag is updated on in the application data. That is, when the application is approved, the usage application approval function unit 1221 adds information indicating that the application has been approved to the approved usage record data (usage application data).

The usage application list function unit 1222 has a function of displaying a list of usage applications on the in-organization terminal device 20 for the decision-maker. The usage application list function unit 1222 may accept search conditions for narrowing down the usage applications to be displayed. The search conditions may be, for example, the same conditions as those already described for the usage application list function unit 1214.

The usage record list function unit 1223 has a function of displaying a list of taxi usage records on the in-house terminal device 20 for the decision-maker. When the usage record has an alert, the usage record list function unit 1223 also displays that there is an alert for the usage record. The usage record list function unit 1223 may accept search conditions for narrowing down the usage record to be displayed. The search condition may be, for example, a user name, a date, a reason for use, and an amount of money (boarding fee, etc.). In addition, the usage record list function unit 1223 has a function of approving the usage record data displayed in a list based on the operation by the determiner.

The alert response function unit 1224 displays a column for the decision-maker to input a supplementary explanation when the taxi usage record data has an alert. In addition, the alert response function unit 1224 accepts a supplementary explanation (text) input by the determiner. The alert response function unit 1224 stores the received supplementary explanation data in association with the usage record data. In addition, the alert response function unit 1224 has a function of approving the usage record data having the alert based on the operation by the determiner.

The supplementary function unit 1225 displays a column for the deciding person to input a supplementary explanation when the taxi usage application or usage record data is in the "complementary input required" state. The conditions for "complementary input required" are as described above. In addition, the complementary function unit 1225 accepts the supplementary explanation input by the determiner. The complementary function unit 1225 saves the received supplementary explanation data in association with the usage record data. In addition, the complement support function unit 1225 has a function of approving the usage record data that was the "complementary input required" based on the operation by the determiner.

FIG. 19 is a block diagram showing a schematic functional configuration in the taxi company functional unit 112. As shown in the figure, the taxi company function unit 112 includes a data confirmation function unit 1121, a data editing function unit 1122, a billing execution function unit 1123, a billing statement output function unit 1125, a billing statement addition function unit 1126, and paper. It is configured to include a ticket detail addition function unit 1127. The taxi company function unit 112 provides the taxi company terminal device 40 with usage record data sorted by taxi company. The taxi company function unit 112 provides only the data related to the taxi company to the taxi company terminal device 40.

The data confirmation function unit 1121 has a function of confirming the usage record data. Specifically, the data determination function unit 1121 causes the taxi company terminal device 40 to display a list of individual data (referred to as "details") of the usage record. At this time, the data confirmation function unit 1121 displays the confirmed data and the unconfirmed data in different display methods (for example, in different display colors). The data confirmation function unit 1121 has a function that the person in charge of the taxi company who sees this list confirms the data by, for example, checking a check box. The data confirmation function unit 1121 updates the confirmation flag of the confirmed data (details) based on the operation of the person in charge of the taxi company.

The data editing function unit 1122 provides a function that allows the person in charge of the taxi company to edit the usage record data. The taxi company personnel need to edit (correct) the data, for example, in the following cases.
a) When the boarding record cannot be acquired on the cloud server device 11 side due to a situation such as poor radio wave propagation condition at the time of boarding (the boarding record and the disembarking record may be registered together at the time of getting off).
b) When the date and time or position of the boarding record, waypoint record, and getting-off record deviate from the actual one due to the timing of the operation by the user being deviated.
c) When the user makes a mistake in entering the fare and the confirmation by the taxi service provider (driver) is also omitted.

The billing execution function unit 1123 has a function for executing a billing of charges from the taxi company side to the side of the organization (company or the like) to which the user belongs. Specifically, the billing execution function unit 1123 searches for and presents confirmed and unbilled data in the taxi usage record, for example, based on the operation of the person in charge of the taxi company. The billing execution function unit 1123 presents an "OK" button on the screen so that the taxi company person in charge can execute the billing after confirming the data for billing. When the "OK" button is pressed, the billing execution function unit 1123 updates the status of the data (details) to "billed" as if the billing was executed. Further, the billing execution function unit 1123 writes the data of the billing date (the day of billing execution) in each of the detailed data.

The billing details output function unit 1125 has a function of outputting billing details data related to the above billing. The billing statement output function unit 1125 accepts the designation of the billing date as a search condition from the taxi company terminal device 40. The billing details output function unit 1125 extracts the data corresponding to the designated billing date by the search. The billing statement output function unit 1125 prints out the data extracted according to the conditions as a form or outputs it as data for a spreadsheet. As a result, the person in charge of the taxi company can send the printed form (set of detailed data) and the spreadsheet data as an attachment to the invoice to the organization to which the user belongs.

The billing detail addition function unit 1126 is a function for additionally creating detailed data for billing with respect to the usage record that has been leaked for some reason. The billing statement addition function unit 1126 creates detail data to be added based on the operation of the person in charge of the taxi company.

The paper ticket detail addition function unit 1127 has a function of additionally creating detailed data for billing based on a paper taxi ticket (paper ticket). The paper ticket can be used when it is not possible to create a boarding record or a disembarking record by the taxi use support system 1 due to circumstances.

FIG. 20 is a block diagram showing a schematic functional configuration in the administrator function unit 123. As shown in the figure, the administrator function unit 123 includes a user registration function unit 1231, a user change function unit 1232, a user deletion function unit 1233, an approved application disposal function unit 1234, and a user code issuing function. It is composed of a unit 1235, a user code update function unit 1236, and an accounting-related function unit 1239.

The user registration function unit 1231 has a function of registering a user who uses the taxi use support system 1. The user registration function unit 1231 imports, for example, data of users (employees, etc.) managed by another database management system (DBMS), data of spreadsheets created by spreadsheet software for PCs, and the like. By doing so, the user is registered. The imported data has at least a portion of the data items that the table shown in FIG. 14 has. The user registration function unit 1231 writes the imported data in the table shown in FIG. In addition, the administrator may register the user by manually inputting the user information.

The user change function unit 1232 changes the user information. The user change function unit 1232 can change the user's name, department code, and other attribute information based on, for example, the operation of the administrator.

The user deletion function unit 1233 deletes the user registered in the taxi use support system 1. For example, when a user who is an employee retires, the user deletion function unit 1233 deletes the user's registration, for example, by an operation of an administrator. The user deletion function unit 1233 deletes the user from the table shown in FIG. 14, or updates the equivalent data (for example, turns on the invalid flag). The deleted user will not be able to use the taxi use support system 1.

The approved application disposal function unit 1234 has a function for discarding approved usage applications (applications for which taxis have not actually been used) that meet predetermined conditions and the like. The approved application disposal function unit 1234 causes the in-house terminal device 20 for the administrator to display a field for inputting a condition for searching a usage application. This allows the administrator to set search conditions. As a specific example, the administrator inputs the name of the user (for example, an employee whose department has changed due to a personnel change or the like after the application for use has been approved) as a search condition. The approved application disposal function unit 1234 searches for usage applications according to the designated search conditions, and displays the usage applications that match the conditions on the screen. The administrator confirms the display, performs an operation such as selecting a usage application to be discarded as necessary, and presses the "discard" button. Based on this operation, the approved application disposal function unit 1234 can discard the approved usage application.

The user code issuing function unit 1235 issues a user code to the user. The user code is code information in the taxi use support system 1. The user code issuing function unit 1235 issues a new user code to a user selected based on, for example, an operation of an administrator. The user code issuing function unit 1235 writes the issued user code in the user code field of the table shown in FIG.

The user code update function unit 1236 has a function of updating (changing) the user code. The user code update function unit 1236 issues a user code different from the conventional one to a user selected based on, for example, an operation of an administrator. The user code update function unit 1236 updates the user code field of the table shown in FIG. 14 by using the changed user code.

The accounting-related function unit 1239 provides necessary functions from the viewpoint of accounting regarding the use of taxis. For example, the accounting-related function unit 1239 enables an administrator (particularly, an accounting person) to view usage record data and total charge data for each taxi company for a specified period. In addition, the accounting-related function unit 1239 has a function of confirming whether or not the decision-maker has approved the usage record data. Further, the accounting-related function unit 1239 may have a function of confirming whether or not the administrator has approved the usage record data. In addition, the accounting-related function unit 1239 has a function of updating a flag indicating whether or not the charge has been charged by the taxi company on the usage record data. In addition, the accounting-related function unit 1239 displays the usage record for which the taxi company has not been billed prominently (for example, by changing the color) on the screen. In addition, the accounting-related function unit 1239 has a function of outputting data for settlement (data for billing charges from taxi companies and clearing accounts payable by payment) for each taxi company. In addition, the accounting-related function unit 1239 has a function of additionally creating usage record data when there is no usage record data for some reason even though the taxi is actually used. In addition, if a taxi is used without using the mechanism of the taxi use support system 1 (in this case, for example, a taxi ticket (paper ticket) printed on paper is used), the charge will be charged. The accounting-related function department 1239 has a function to reflect it in the settlement data with the taxi company.

As described above, the taxi use support system 1 can seamlessly exchange data with an accounting system of a company or the like.

The alert conditions used by the usage record confirmation unit 124 for confirming the data are as follows, for example. However, the alert conditions are not limited to those listed here. Alert conditions may be added or changed as appropriate. Attendance data such as attendance time and leaving time can be referred to as described above.

(1) Exceeding time after leaving work: The taxi boarding time is more than a predetermined time separated from the leaving time of the user.
(2) Exceeding time after getting off: The time when the user goes to work exceeds the predetermined time when the taxi gets off.
(3) Daily fixed amount or more: The total daily taxi fare for the same user is equal to or higher than the predetermined fixed amount.
(4) Tonight / Midnight / Early Morning: The user is using a taxi for the reason of midnight / early morning on the day when the attendance data shows the all-night work category.
(5) Midnight / Early Morning / Prescribed Distance or More: If you are using a taxi for the reason of using midnight / early morning, the boarding place or getting off place (either home side) is at least the specified distance from your home position (latitude / longitude). is seperated.
(6) Midnight and early morning boarding: If you are using a taxi for late night or early morning use, use a taxi other than the available time zone set for each work location (or department). There is.
(7) Riding near home: When using a taxi other than the reason for use in the middle of the night and early morning, there is a boarding position near the home (within a predetermined distance).
(8) Get off near your home: When using a taxi other than the reason for using it in the middle of the night or early in the morning, there is a drop-off position near your home (within a predetermined distance).
(9) Holiday use: There is a taxi use on holidays or vacation days on the attendance data.
(10) Getting on and off outside working hours: When using a taxi other than the reason for using it in the middle of the night and early morning, the boarding time or getting off time is not within the working hours.

The usage record confirmation unit 124 confirms the taxi usage record based on, for example, the above alert conditions. That is, the usage record confirmation unit 124 determines whether or not the user meets a predetermined alert condition, and if the alert condition is met, an alert for the usage record data is generated. Therefore, when there is a possibility of using an inappropriate taxi, it is possible to ask the user to input a supplementary explanation.

It should be noted that at least a part of the functions in the taxi use support system 1 in the above-described embodiment can be realized by a computer. In that case, the program for realizing this function may be recorded on a computer-readable recording medium, and the program recorded on the recording medium may be read by the computer system and executed. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. The "computer-readable recording medium" is a portable medium such as a flexible disk, a magneto-optical disk, a ROM, a CD-ROM, a DVD-ROM, or a USB memory, or a storage device such as a hard disk built in a computer system. Say that. Furthermore, a "computer-readable recording medium" is a device that temporarily and dynamically holds a program, such as a communication line when a program is transmitted via a network such as the Internet or a communication line such as a telephone line. , In that case, a program that holds a program for a certain period of time, such as a volatile memory inside a computer system that serves as a server or a client, may be included. Further, the above-mentioned program may be a program for realizing a part of the above-mentioned functions, and may be a program for realizing the above-mentioned functions in combination with a program already recorded in the computer system.

The present embodiment is summarized as follows.

The server device includes at least a user function unit, a data storage unit, a decision-maker function unit, and a transportation company function unit. The cloud server device 11 and the in-house server device 12 are server devices. The first user function unit 111 and the second user function unit 121 are user function units. The first data storage unit 110 and the second data storage unit 120 are data storage units. The taxi company functional unit 112 is a transportation company functional unit.
The user function unit receives from the user's terminal device usage record data including the transportation company identification information for identifying the transportation company that provides the transportation service and the information on the amount of the transportation fee. The service that taxis carry people is a transportation service. A taxi company is a freight operator. The information that identifies the taxi company is the transportation company identification information.
The data storage unit stores and stores the received usage record data.
The decision-maker function unit executes a process (pre-approval or post-approval) to approve the use of the transportation service by the user at least before or after the implementation of the transportation service, and the approved use. Information indicating that the data has been approved is added to the actual data.
The transportation company function department provides the terminal device of the transportation company with the usage record data sorted by the transportation company based on the approved usage record data.

The transportation company identification information (taxi company identification information) is optically readable by the transportation means (taxi vehicle, etc.) possessed by the transportation company (taxi company) and used for the transportation service. The code information provided in various forms is acquired by the user's terminal device reading it.

The user's terminal device reads the code information at the start of the transportation service (when boarding a taxi).
The user function unit receives the transportation company identification information based on the code information from the user's terminal device as a part of the service start record (boarding record).

The user's terminal device determines (determines) the amount of the transportation charge (meter charge, toll road charge, and the total) for the transportation service at the end of the transportation service (when getting off the taxi). Information on the amount of the transportation fee is obtained.
The user function unit receives information on the amount of the transportation fee from the user's terminal device as a part of the service end record (disembarkation record).

The user's terminal device acquires information on the amount of the transportation charge manually by the user. That is, it is not necessary to provide a means for receiving fare data from a taxi meter or the like.

When the transportation company functional department provides the usage record data for the transportation company to the terminal device of the transportation company, the transportation company functioning unit uses the usage record data as a unit of implementation of the transportation service. Information indicating whether or not the data has been confirmed is also transmitted, and information indicating that the data has been confirmed is added to the usage record data instructed by the terminal device of the transportation company to be confirmed. (Update confirmed flag).

When the transportation company functional department provides the usage record data for the transportation company to the terminal device of the transportation company, the transportation business is a unit for implementing the transportation service. Information indicating whether or not the person has been charged is also transmitted, and the usage record data instructed by the terminal device of the transportation company to be charged is that the charge has been charged. Add the information to be represented (update billing flag).

The server device further includes a usage record confirmation unit for confirming the contents of the usage record data.
At the start of the transportation service (at the time of boarding), the user function unit obtains information on the time at the start of the transportation service (boarding time) and information on the position at the start of the transportation service (boarding position). In addition to receiving from the user's terminal device, at the end of the transportation service (at the time of getting off), information on the time at the end of the transportation service (getting off time) and the position at the end of the transportation service (getting off position). Information is received from the user's terminal device.
As a part of the usage record data, the data storage unit includes information on the time at the start of the transportation service, information on the position at the start of the transportation service, and information on the time at the end of the transportation service. The position information at the end of the transportation service and the information are stored.
By referring to the attendance data representing the attendance status of the user, the usage record confirmation unit can obtain the attendance data, the information of the time at the start of the transportation service, and the information of the position at the start of the transportation service. , It is determined whether or not the information on the time at the end of the transportation service and the information on the position at the end of the transportation service match a predetermined alert condition, and the information matches the alert condition. In that case, an alert is generated for the usage record data.

The user mobile terminal device 30 (user terminal device) provides a transportation service operator by reading code information provided in an optically readable form in the transportation means used for the transportation service. In addition to acquiring the carrier identification information for identification, the information on the amount of the transportation fee is acquired, and the usage record data including the information on the identification of the carrier and the information on the amount of the transportation fee is sent to the server device. Send to. Further, the user mobile terminal device 30 (user terminal device) transmits the usage record data including the transportation company identification information to the server device by reading the code information at the start of the transportation service. Then, after the amount of the transportation fee is determined, the information on the amount of the transportation fee is acquired manually by the user, and the usage record data including the information on the amount of the transportation fee is transmitted to the server device. A confirmation screen including information on the amount of the transportation fee is displayed, and when the "registration" button included in the confirmation screen is operated, a confirmation notification, which is a notification to confirm the usage record data, is sent to the server device. Send to. Further, the user mobile terminal device 30 (user terminal device) displays the ticket number given by the server device on the screen after transmitting the confirmation notification to the server device.

As described above, according to the present embodiment, it is possible to settle the charge without requiring an excessive device or the like (particularly, without providing an additional communication means on the vehicle side such as a taxi). Further, according to the present embodiment, the user can use a taxi, not limited to a taxi company determined in advance on the server side. Further, according to the present embodiment, it is not necessary for the user's terminal device to bother to download and install the application when using a taxi. Further, according to the present embodiment, the approval process within the user's organization, the taxi use process, and the billing process from the taxi company can be seamlessly connected.

[Second Embodiment]
Next, the second embodiment will be described with reference to the drawings. The matters already described in the previous embodiment may be omitted below. Here, the matters peculiar to the present embodiment will be mainly described. The feature of this embodiment is the configuration of the functions of the cloud server device 11. The cloud server device 11 is configured to have the first user function unit 211 in the present embodiment instead of the first user function unit 111 in the first embodiment.

FIG. 21 is a block diagram showing a schematic functional configuration of the first user function unit 211 in the present embodiment. As shown in the figure, the first user function unit 211 includes a boarding registration function unit 2111, a waypoint registration function unit 2112, a disembarkation registration function unit 2113, a usage application function unit 2118, and a usage application list function unit 2119. Consists of including. Of these, the boarding registration function unit 2111, the waypoint registration function unit 2112, and the disembarkation registration function unit 2113 are the boarding registration function unit 1111, the waypoint registration function unit 1112, and the disembarkation, respectively, according to the first embodiment. It has the same function as the registration function unit 1113. That is, also in this embodiment, the user can execute processes such as boarding registration, waypoint registration, and disembarkation registration by operating the user mobile terminal device 30. The feature of this embodiment is that the first user function unit 211 also includes the usage application function unit 2118 and the usage application list function unit 2119.

The usage application function unit 2118 has the same function as the usage application function unit 1213 in the second user function unit 121 in the first embodiment. Thereby, in the present embodiment, the user can process the taxi use application not only from the in-house terminal device 20 but also from the user mobile terminal device 30. Specifically, the usage application function unit 2118 is a screen for inputting necessary items related to the application (selecting some items from the options) similar to the usage application function unit 1213 to the user mobile terminal device 30. Is displayed. Further, when the user inputs the data and operates (tap or the like) the "application" button, the usage application function unit 1213 registers the application. The data of this application is also transferred from the cloud server device 11 side to the internal server device 12 side at an appropriate timing. That is, the application processed by the usage application function unit 2118 is treated in the same manner as the application processed by the usage application function unit 1213 on the server device 12 side in the organization. In other words, an appropriate decision-maker can approve the usage application.

The usage application function unit 2118 has the same functions as the usage application function unit 1213 even for the functions omitted here.

Also in this embodiment, the second user function unit 121 has the same function of the usage application function unit 1213 as that of the first embodiment. That is, the user can similarly perform the processing related to the application for the use of the taxi regardless of whether the terminal device 20 in the organization is used or the mobile terminal device 30 for the user is used.

When a user applies for the use of a taxi by either the function of the usage application function unit 1213 or the usage application function unit 2118, the decision-maker who should make a decision on the application is notified by e-mail. May be sent. As an example, a daemon that monitors new applications should be kept running within the organization's server unit 12 so that the daemon sends an email to the decision-maker associated with the new application. To do.

The usage application list function unit 2119 has the same function as the usage application list function unit 1214 in the second user function unit 121 in the first embodiment. Thereby, in the present embodiment, the user can view the list of taxi use applications not only from the in-house terminal device 20 but also from the user mobile terminal device 30.

The usage application list function unit 2119 causes the user mobile terminal device 30 to display list information of taxi usage applications of a specific user (logged-in user). As a result, the user can collectively grasp the status of the usage application (for example, whether or not it has already been approved). As for other functions, the usage application list function unit 2119 has the same function as the usage application list function unit 1214.

The user mobile terminal device 30 according to the present embodiment transmits application data for using the transportation service (taxi service) to the server device as described above. Further, as described in the first embodiment, the user mobile terminal device 30 displays the disembarkation record completion screen when the disembarkation confirmation is performed (after the confirmation notification is transmitted to the server device). The ticket number is also displayed on this disembarkation confirmation completion screen. This ticket number is a number assigned by the server device in association with the above application data.

Although the first embodiment and the second embodiment have been described above, the present invention can be further implemented in the following modifications.
Modification 1: In the above embodiment, the function of the server device 10 is divided into a cloud server device 11 and an in-organization server device 12, and a system is configured. As a modification 1, the system may be configured as one server device without separating the two. Further, the function of the server device 10 may be divided into three or more devices to configure the system.
Modification 2: In the above embodiment, at the time of boarding, the user mobile terminal device 30 reads the two-dimensional code information (code information that at least identifies the taxi company) and transmits the information to the server side as a boarding record. I made it. As a modification 2, the user mobile terminal device 30 may read the two-dimensional code information at any time between the time of getting on the taxi and the time of getting off the taxi (while the transportation service is being performed). .. Further, the user mobile terminal device 30 may transmit the information identifying the taxi company to the server side at any time between the time of getting on the taxi and the time of getting off the taxi.
Further, a plurality of modified examples may be combined and carried out.

Although the plurality of embodiments of the present invention have been described in detail with reference to the drawings, the specific configuration is not limited to this embodiment, and includes designs and the like within a range that does not deviate from the gist of the present invention. ..

The present invention can be used, for example, for the purpose of managing the use of transportation means by employees or related parties in an organization such as a company. However, the scope of use of the present invention is not limited to those exemplified here.

1 Taxi usage support system 10 Server device 11 Cloud server device 12 In-house server device 20 In-house terminal device 30 Mobile terminal device for users (user terminal device)
40 Terminal device for taxi company 50 Relay device 61 External network 62 In-house network 110 First data storage unit 111 First user function unit 112 Taxi company function unit 120 Second data storage unit 121 Second user function unit 122 Determiner Function unit 123 Administrator function unit 124 Usage record confirmation unit 211 First user function unit 1111 Boarding registration function unit 1112 Route registration function unit 1113 Disembarkation registration function unit 1212 Home registration function unit 1213 Usage application function unit 1214 Usage application list function Part 1215 Usage record list function section 1216 Alert response function section 1217 Complementary response function section 1220 User code issuance function section 1221 Usage application approval function section 1222 Usage application list function section 1223 Usage record list function section 1224 Alert response function section 1225 Complementary support Function unit 1121 Data confirmation function unit 1122 Data editing function unit 1123 Billing execution function unit 1125 Billing statement output function unit 1126 Billing statement addition function unit 1127 Paper ticket detail addition function unit 1231 User registration function unit 1232 User change function unit 1233 Person deletion function unit 1234 Approved application discard function unit 1235 User code issuance function unit 1236 User code update function unit 1239 Accounting-related function unit 2111 Boarding registration function unit 2112 Waypoint registration function unit 2113 Disembarkation registration function unit 2118 Usage application function Department 2119 Usage application list Function department

Claims (13)

A user function unit that receives usage record data including transportation company identification information for identifying a transportation company that provides transportation services and information on the amount of transportation charges from the user's terminal device.
A data storage unit that stores the received usage record data,
The process of approving the use of the transportation service by the user at least before or after the implementation of the transportation service is executed, and the approved usage record data contains information indicating that the approval has been granted. The decision-maker function part to be added and
The transportation company function department that provides the usage record data sorted by transportation company to the terminal equipment of the transportation company, and
A server device equipped with. The transportation company identification information is code information provided in an optically readable form in the transportation means possessed by the transportation company and used for the transportation service, and is provided by the user. It is acquired by reading by the terminal device,
The server device according to claim 1. The user's terminal device reads the code information at the start of the transportation service.
The user function unit receives the carrier identification information based on the code information from the user's terminal device as a part of the service start record.
The server device according to claim 2. The user's terminal device acquires information on the amount of the transportation fee after determining the amount of the transportation fee for the transportation service at the end of the transportation service.
The user function unit receives information on the amount of the transportation fee from the terminal device of the user as a part of the service end record.
The server device according to any one of claims 1 to 3. The user's terminal device acquires information on the amount of the transportation charge manually by the user.
The server device according to claim 4. When the transportation company functional department provides the usage record data for the transportation company to the terminal device of the transportation company, the transportation company functioning unit uses the usage record data as a unit of implementation of the transportation service. Information indicating whether or not the person has been confirmed is also transmitted, and the usage record data instructed by the terminal device of the transportation company to be confirmed is provided with information indicating that the person has been confirmed. Add,
The server device according to any one of claims 1 to 5. When the transportation company functional department provides the usage record data for the transportation company to the terminal device of the transportation company, the transportation business is a unit for implementing the transportation service. Information indicating whether or not the person has been charged is also transmitted, and the usage record data instructed by the terminal device of the transportation company to be charged is that the charge has been charged. Add information to represent,
The server device according to claim 6. Usage record confirmation department that confirms the contents of the usage record data,
Further equipped,
At the start of the transportation service, the user function unit receives information on the time at the start of the transportation service and information on the position at the start of the transportation service from the terminal device of the user, and also receives the transportation. At the end of the service, the information on the time at the end of the transportation service and the information on the position at the end of the transportation service are received from the terminal device of the user.
As a part of the usage record data, the data storage unit includes information on the time at the start of the transportation service, information on the position at the start of the transportation service, and information on the time at the end of the transportation service. , Memorize the location information at the end of the transportation service,
By referring to the attendance data representing the attendance status of the user, the usage record confirmation unit may refer to the attendance data, information on the time when the transportation service is started, and information on the position when the transportation service is started. It is determined whether or not the information on the time at the end of the transportation service and the information on the position at the end of the transportation service match a predetermined alert condition, and the alert condition is met. If so, generate an alert about the usage record data.
The server device according to any one of claims 1 to 7. A user function unit that receives usage record data including transportation company identification information for identifying a transportation company that provides transportation services and information on the amount of transportation charges from the user's terminal device.
A data storage unit that stores the received usage record data,
The process of approving the use of the transportation service by the user at least before or after the implementation of the transportation service is executed, and the approved usage record data contains information indicating that the approval has been granted. The decision-maker function part to be added and
The transportation company function department that provides the usage record data sorted by transportation company to the terminal equipment of the transportation company, and
A program for operating a computer as a server device, which is equipped with. By reading the code information provided in an optically readable form in the transportation means used for the transportation service, the transportation company identification information for identifying the transportation company that performs the transportation service is acquired, and the above-mentioned The information on the amount of the transportation fee is acquired, and the usage record data including the information on the identification information of the transportation company and the information on the amount of the transportation fee is transmitted to the server device.
User terminal device. The user terminal device is
At the start of the transportation service, the usage record data including the transportation company identification information is transmitted to the server device by reading the code information.
After the amount of the transportation charge is determined, the information on the amount of the transportation charge is manually input by the user, and the usage record data including the information on the amount of the transportation charge is transmitted to the server device.
A confirmation screen including information on the amount of the transportation fee is displayed, and when the "registration" button included in the confirmation screen is operated, a confirmation notification, which is a notification to confirm the usage record data, is sent to the server device. Send to,
The user terminal device according to claim 10. The user terminal device is
After transmitting the application data for using the transportation service to the server device and transmitting the confirmation notification to the server device, the ticket number given by the server device in association with the application data is displayed on the screen. To do
The user terminal device according to claim 11. A user function unit that receives usage record data including transportation company identification information for identifying a transportation company that provides transportation services and information on the amount of transportation charges from the user's terminal device.
A data storage unit that stores the received usage record data,
The process of approving the use of the transportation service by the user at least before or after the implementation of the transportation service is executed, and the approved usage record data contains information indicating that the approval has been granted. The decision-maker function part to be added and
The transportation company function department that provides the usage record data sorted by transportation company to the terminal equipment of the transportation company, and
A server device equipped with
The transportation company identification information is acquired by reading the code information provided in an optically readable form in the transportation means used for the transportation service, and the information on the amount of the transportation fee is acquired. A user terminal device that transmits usage record data including the transportation company identification information and the information on the amount of the transportation fee to the server device, and
System including.

Images