JP2021009745A - Information creation method, and computer program - Google Patents

Abstract

To provide an information creation method of transaction information capable of allowing a payer, etc. to determine the information required for payment after service completion, and a computer program.SOLUTION: An information creation method is an information creation method of creating a piece of transaction information required for settlement of consideration for services or products. The information creation method includes the steps of: receiving content of a selection of services or products; transmitting a request for drafting transaction information on the condition that the selected services or products will be provided; and displaying a search screen that includes a list of a piece of provider identification information of a provider of the services or goods according to the condition and a piece of payer identification information of a payer who will pay the consideration, and receives a selection of provider identification information and payer identification information, and a selection of whether to pay for the services or products as expense processing by the payer or personal expense of the user.SELECTED DRAWING: Figure 15

Description

The present invention relates to an information creation method for creating transaction information necessary for settlement of charges for services or goods, and a computer program.

Electronic money using a non-contact IC chip that communicates identification information by short-range wireless communication and enables payment of service or product charges has become widespread. In addition, a payment service that completes payment with a user's bank account or credit card by simply taking a picture of a two-dimensional bar code with a camera is also widespread (Patent Document 1 and the like). Cashless society is progressing due to such electronic money and payment services.

JP-A-2007-328549

Cashless payment still assumes that the payer of the cost is the individual user who enjoys the service or product, and the payment is made based on the link with the bank account or credit card.

However, the use of services or goods is not limited to personal purposes. Business use accounts for a large proportion of transportation using public transportation. In this case, if the popular cash payment as described above is used, it is complicated because the settlement process with the accounting department of the organization to which the user belongs is required, so that the user ends up using cash. Subsequent settlement processing will be performed using receipts that serve as proof of payment and use.

An object of the present invention is to provide an information creation method, an information creation system, an information creation device, and a computer program regarding transaction information that allows information necessary for payment by a payer or the like to be fixed after the service is completed.

The information creation method of the embodiment of the present disclosure is an information creation method for creating transaction information necessary for settlement of consideration for a service or product, and accepts selection of the content of the service or product and selects the service or product. A request for drafting transaction information is sent on condition that the product is provided, and a list of the provider identification information of the service or product provider corresponding to the condition and the payer identification information of the payer who pays the consideration. , A screen that accepts the selection of the provider identification information and the payer identification information, and the selection of whether the payment of the consideration for the service or the product is to be expensed by the payer or paid by the user. Display the search screen that includes.

The computer program of the embodiment of the present disclosure is a computer program for causing a computer provided with a display unit to display information on transaction information necessary for payment of consideration for a service or a product, and the computer is displayed with the service or the product. Accepts the selection of contents, sends a request for drafting transaction information on condition that the selected service or product is provided, and provides the provider identification information of the provider of the service or product and the consideration according to the condition. A list of payer identification information of the payer, selection of the provider identification information and the payer identification information, and payment of consideration for the service or goods shall be expense processing by the payer or the individual user. The process of displaying the search screen including the screen for accepting the selection of whether to bear the burden is executed.

In the information creation method of the present disclosure and the computer program, the transaction information that is the basis of settlement and expense processing is the content-specific information, consideration information, provider identification information, user identification information, and payment included in this transaction information. If any one of the person identification information is determined, it is drafted and the use of the service or the product can be started. The content-specific information, consideration information, provider identification information, user identification information, and payer identification information that should be included in the transaction information are sequentially added and created, and payment and expense processing become possible.

It is now possible to search for transaction information that has been decided and drafted by any one of the content of the service or product, consideration, user, provider, and payer, by attributes such as the content of the service or product. Become. By searching for transaction information by attributes such as male only, female only, food and drink only, and specific area only, users can easily find and use transaction information for which the user has not been decided, and the provider also , You can easily find transaction information for which the provider has not been decided.

A request for drafting transaction information can be sent with conditions including the content of the service or product, whether it is a provider, user or payer, and whether to choose between expense processing and personal expense.

Not only the form of the transaction that starts the transaction after the user decides the content of the service or product, the provider and the payer, but also the transaction that recruits the user and the provider after the payer is confirmed, the provider It is possible to realize a new form of transaction such as a transaction that recruits users and payers after it is confirmed.

Even if multiple users enjoy the service or product provided by one provider, transaction information is created for each, and when the provision is completed and the fee is fixed, each transaction information is completed and the service is provided. After the facts are confirmed, payment and expense processing will be possible.

In the platform of the present disclosure, it is possible to use a service or a product by creating transaction information that is the basis of payment and expense processing at a stage where two of the user, the provider, and the payer are not determined. Information that is the basis of payment and expense processing is completed by sequentially determining all information of users, providers, and payers according to the progress of use. This allows cashless payments to be used by both individuals and expenses. Information is completed based on the content of the service or product that was actually provided and the fact that it was used, so even if the same service is used by multiple users (carpooling, shared seats, etc.), each user The fee will be fixed and paid based on the services enjoyed by.

It is a figure which shows the outline of the information creation system. It is a block diagram which shows the structure of the user terminal apparatus of an information creation system. It is a block diagram which shows the structure of the provider terminal apparatus of an information creation system. It is a block diagram which shows the structure of the payer terminal apparatus of an information creation system. It is a block diagram which shows the structure of the information creation apparatus. It is a figure which shows the content example of the information stored in a user DB. It is a figure which shows the content example of the information stored in the provider DB. It is a figure which shows the content example of the information stored in the payer DB. It is a figure which shows the content example of the information stored in the form DB. It is a figure which shows the content example of the information stored in the recruitment condition DB. It is a flowchart which shows an example of the processing procedure in an information creation apparatus. An example of the screen displayed on the user terminal device is shown. An example of the screen displayed on the user terminal device is shown. It is a figure which shows the sequence until the digital form is completed based on the request from a user terminal device. It is a schematic diagram showing the process of completing a digital form. An example of the screen displayed on the provider terminal device is shown. An example of the screen displayed on the provider terminal device is shown. It is a figure which shows the content example of the notification screen of application to a user. An example of a digital ticket displayed on a user terminal device is shown. It is a figure which shows the content example of a digital ticket. It is a figure which shows the sequence until the digital form is completed based on the request from the provider terminal device. It is a schematic diagram of the digital form in the second case. An example of the screen displayed on the user terminal device is shown. It is a figure which shows the screen example displayed on the provider terminal apparatus. It is a figure which shows the screen example displayed on the user terminal apparatus. It is a schematic diagram of the digital form in the third case. An example of the contents of the search screen displayed on the user terminal device according to the second embodiment is shown. It is a sequence diagram which shows an example of the processing procedure about the digital form which realizes the carpooling of a taxi. It is a sequence diagram which shows an example of the processing procedure about the digital form which realizes the carpooling of a taxi. It is a sequence diagram which shows an example of the processing procedure about the digital form which realizes the carpooling of a taxi. An example of the contents of the search screen displayed on the provider terminal device in the second embodiment is shown. An example of the screen displayed on the provider terminal device in the third embodiment is shown. An example of the screen displayed on the user terminal device in the third embodiment is shown. An example of the screen displayed on the payer terminal device in the fourth embodiment is shown. An example of the screen displayed on the user terminal device in the fourth embodiment is shown.

The present disclosure will be specifically described with reference to the drawings showing the embodiments thereof. In the following embodiment, an information creation system to which the information creation method of the present disclosure is applied will be described.

(Embodiment 1)
FIG. 1 is a diagram showing an outline of the information creation system 100. The information creation system 100 setstle the charges between the user of the service or product, the provider who provides the service or product, and the payer who pays the charge necessary for using the service or product, and the expenses in the payer. It is a system that creates transaction information required for processing.

The information creation system 100 realizes a mechanism in which the user can actually enjoy the service or product without cash, and when the fee according to the actual use is fixed, the fee is paid from the payer to the provider without any trouble. Provide a platform. In the platform of the present disclosure, digital form DF is used as transaction information that can be used as a basis for settlement or expense processing.

In the platform of the present disclosure, a digital form DF is issued for each transaction, and a digital ticket is issued based on the issued digital form DF and can be used by the user. The platform of the present disclosure allows the content of a service or product to be determined after the digital form DF has been issued, and is not only the user himself as the payer, but also the employer of the user and the sponsor of the user. Allow to be.

The platform of the present disclosure accepts requests from any one of a user, a provider, or a payer, such as wanting to receive a service (product) or recruiting users of the service (product). The platform recruits service providers, payers, users, etc. that match the request, and when the information and fees of the users, providers and payers are confirmed, the payment of the fee from the payer to the provider Is guaranteed to be executed. The payment service may be a separate system, and the platform of the present disclosure creates a digital form DF on which the payment used by the payment service is based. On the platform, when the fee is fixed, the payer can pay the fee to the provider after confirming whether the user has definitely enjoyed the service or the product. The provider can reliably collect the fee from the user himself or the payer who is the employer of the user. Users can enjoy services or products without cash.

Users, providers, and payers each install computer programs on their computers and contract with platform operators to take advantage of such platforms that enable cashless and secure payments. Depending on the type of account issued in the contract with the platform operator, the computers of the user, provider and payer who use this computer program are the user terminal device 1, the provider terminal device 2 and the payer, respectively. It becomes the terminal device 3.

Specifically, the functions provided by the platform of the present disclosure are in the information creation device 4 which is a computer in which the user terminal device 1, the provider terminal device 2, and the payer terminal device 3 function as a server to which communication connection is possible. It is realized by processing.

The network N includes a public communication network N1 which is a so-called Internet and a carrier network N2 which realizes wireless communication according to a predetermined mobile communication standard. The public communication network N1 includes an access point AP. The carrier network N2 includes a base station BS. The user terminal device 1, the provider terminal device 2, and the payer terminal device 3 can each be connected to the information creation device 4 via the public communication network N1 or the carrier network N2. The payer terminal device 3 may be able to communicate with the information creation device 4 via a dedicated line.

FIG. 2 is a block diagram showing the configuration of the user terminal device 1 of the information creation system 100. As described above, the user terminal device 1 uses a computer having a communication function such as a smartphone. The user terminal device 1 includes a control unit 10, a storage unit 11, a communication unit 12, a display unit 13, an operation unit 14, a reading unit 15, and a position information acquisition unit 16.

The control unit 10 is a processor using a CPU (Central Processing Unit) or a GPU (Graphics Processing Unit), and uses a built-in memory such as a ROM (Read Only Memory) and a RAM (Random Access Memory) to control each component unit. Control and execute processing. The control unit 10 may be configured as one piece of hardware (SoC: System On a Chip) in which a processor, a memory, a storage unit 11, and a communication unit 12 are integrated. The control unit 10 can communicate with the information creation device 4 based on the terminal application program 1P stored in the storage unit 11, displays information related to service use described later, and accepts operations.

The storage unit 11 uses a flash memory to store programs and data referred to by the control unit 10 including the terminal application program 1P. The storage unit 11 stores account information that serves as a user ID that identifies a user of the service. The control unit 10 displays a graphical interface for the user on the display unit 13 based on the account information corresponding to the user ID and the terminal application program 1P, and transmits / receives information to / from the information creation device 4 as an application for the user. To do.

The communication unit 12 is a wireless communication module that realizes wireless communication with the information creation device 4 via the public communication network N1 or the carrier network N2. The communication unit 12 uses, for example, a wireless communication device compatible with Wi-Fi or a carrier communication module.

The display unit 13 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 14 is an interface that accepts user operations, and uses physical buttons, a touch panel device with a built-in display, a speaker, a microphone, and the like. The operation unit 14 may accept an operation on the screen displayed on the display unit 13 by a physical button or a touch panel, recognizes the operation content from the input voice by the microphone, and interacts with the voice output by the speaker. The operation may be accepted in the form.

The reading unit 15 is a reader that reads a code such as a provider ID. The reading unit 15 is at least one of a barcode reader, a camera, and a wireless tag reader. The reading unit 15 may include any of them and selectively use any of them depending on the mode of presenting the code to read the code. The reading unit 15 notifies the control unit 10 of the read code.

The position information acquisition unit 16 is a device that acquires the position information of the user terminal device 1. The position information acquisition unit 16 may use a GPS (Global Positioning System) receiving device or a device that identifies the position information by Wi-Fi of the communication unit 12.

FIG. 3 is a block diagram showing the configuration of the provider terminal device 2 of the information creation system 100. As described above, the provider terminal device 2 uses a computer having a communication function such as a tablet terminal. The provider terminal device 2 used by the support staff or the administrator, not the staff who actually provides the service, uses a desktop or laptop personal computer.

The provider terminal device 2 includes a control unit 20, a storage unit 21, a communication unit 22, a display unit 23, an operation unit 24, and a reading unit 25.

The control unit 20 is a processor that uses a CPU or GPU, and uses a built-in memory such as a ROM or RAM to control each component and execute processing. The control unit 20 can communicate with the information creation device 4 based on the terminal application program 2P stored in the storage unit 21, displays information related to service provision, and accepts operations.

The storage unit 21 uses a flash memory to store programs and data referred to by the control unit 20 including the terminal application program 2P. The storage unit 21 stores account information corresponding to the provider ID that identifies the service provider. The storage unit 21 may store information that individually identifies individual staff members who operate the provider terminal device 2. The control unit 20 displays a graphical interface for the provider on the display unit 23 based on the account information corresponding to the provider ID and the terminal application program 2P, and exchanges information with the information creation device 4 as an application for the provider. To do.

The communication unit 22 is a wireless communication module that realizes wireless communication with the information creation device 4 via the public communication network N1 or the carrier network N2. The communication unit 22 uses, for example, a wireless communication device compatible with Wi-Fi or a carrier communication module.

The display unit 23 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 24 is an interface that accepts the operation of the service provider, and uses physical buttons, a touch panel device with a built-in display, a speaker, a microphone, and the like. The operation unit 24 may accept an operation on the screen displayed on the display unit 23 by a physical button or a touch panel, recognizes the operation content from the input voice by the microphone, and interacts with the voice output by the speaker. The operation may be accepted in the form.

The reading unit 25 is a reader that reads information from other devices. The reading unit 25 may be a barcode reader or a camera. The reading unit 25 may be an interface connected to another device (cash register terminal, meter) for calculating the service charge. The charge may be input using the operation unit 24.

The reading unit 25 may function as a reader that reads the user ID presented by the user terminal device 1 as described later. In this case, the reading unit 25 is a bar code reader, a camera, or a short-range wireless communication module, and acquires information including a user ID of a user who is a customer of a service or a product. The reading unit 25 notifies the control unit 20 of the read information.

It is desirable that the provider terminal device 2 can also acquire the position information if it is possessed by the taxi driver as described later. The provider terminal device 2 may be provided with a position information acquisition unit, or may be able to acquire position information from a taximeter or a navigation system.

The provider terminal device 2 can be used as a terminal for a general-purpose computer if the service can be obtained from a taximeter if it is a taxi business, a cash register terminal if it is a restaurant, or a check-in check-out system if it is an accommodation business. It is realized by installing the application program 2P and associating the provider ID.

FIG. 4 is a block diagram showing the configuration of the payer terminal device 3 of the information creation system 100. As described above, the payer terminal device 3 is used by the accounting department of the company that is the payer, the manager who is the superior of the user and has the payment right, or the user who can be a sponsor. The payer terminal device 3 may be a personal computer or a server computer, or may be a tablet terminal or a smartphone individually managed by the staff of the accounting department.

The payer terminal device 3 includes a control unit 30, a storage unit 31, a communication unit 32, a display unit 33, and an operation unit 34.

The control unit 30 is a processor that uses a CPU or GPU, and uses a built-in memory such as a ROM or RAM to control each component and execute processing. The control unit 30 can communicate with the information creation device 4 based on the terminal application program 3P stored in the storage unit 31, displays information related to payment approval, which will be described later, and accepts operations.

The storage unit 31 uses a hard disk or an SSD (Solid State Drive). The storage unit 31 stores programs and data referred to by the control unit 30 including the terminal application program 3P. The storage unit 31 stores account information that serves as a payer ID that identifies the payer. As shown in FIG. 4, the storage unit 31 may store the user ID of the user belonging to the payer's company and the payer DB 301 including the user information including the attributes of the user. The payer DB 301 of the payer terminal device 3 used in the accounting department may include expense information for which payment has been completed.

The control unit 30 displays a graphical interface for the payer on the display unit 33 based on the account information corresponding to the payer ID stored in the storage unit 31 and the terminal application program 3P, and serves as an application for the payer. Information is exchanged with the information creation device 4.

The communication unit 32 is a network card that realizes a communication connection with the information creation device 4. The payer terminal device 3 may be connected to the information creation device 4 via the public communication network N3, or may be connected to the information creation device 4 via a dedicated line.

The display unit 33 uses a display device such as a liquid crystal panel or an organic EL display. The operation unit 34 is an interface that receives operations of the staff of the accounting department of the company, and uses a keyboard and a pointing device. The operation unit 34 may use a speaker, a microphone, or the like to recognize the operation content from the input voice by the microphone and accept the operation in an interactive manner with the voice output by the speaker.

The terminal application programs 1P, 2P, and 3P are application programs that differ depending on the type of computer (laptop, desktop, smartphone, or tablet terminal), but have common functions. When not only the account information corresponding to the user ID but also the account information corresponding to the payer ID is stored in the storage unit 11 of the user terminal device 1 under the contract with the platform operator, the user terminal device 1 can also be a payer terminal device 3. That is, the user can also act with the authority of the superior approver, that is, the payer by switching the account. Similarly, the user terminal device 1 can be switched to the provider terminal device 2. Of course, the terminal application programs 1P, 2P, and 3P may be provided as computer programs specialized for users, service providers, and payers, respectively.

FIG. 5 is a block diagram showing the configuration of the information creation device 4. As described above, the information creation device 4 uses a server computer. In the first embodiment, the information creation device 4 will be described as one server computer below, but the functions or processes may be distributed among a plurality of server computers.

The information creation device 4 includes a control unit 40, a storage unit 41, a communication unit 42, and an input / output unit 44. The control unit 40 is a processor using a CPU or GPU, and controls each component unit using a built-in memory to execute processing. The control unit 40 executes information processing based on the information processing program 4P stored in the storage unit 41.

The storage unit 41 uses a hard disk or SSD. The storage unit 41 stores the information processing program 4P, and also stores other programs and data referred to by the control unit 40.

The communication unit 42 realizes communication in the public communication network N1 or the carrier network N2. The control unit 40 can transmit and receive information to and from the user terminal device 1, the provider terminal device 2, or the payer terminal device 3 via the public communication network N1 or the carrier network N2 by the communication unit 42.

The input / output unit 44 is a connection interface with a service DB (Data Base: database) 401 that stores various information about the platform. The service DB 401 may be built in the storage unit 41.

The service DB 401 includes a user DB 402, a provider DB 403, a payer DB 404, a form DB 405, and a recruitment condition DB 406.

FIG. 6 is a diagram showing an example of the content of the information stored in the user DB 402. The user DB 402 stores attributes such as the user's name in association with the user ID. The attributes may include contact information such as a user's telephone number and e-mail address, a company name to which the user belongs, an employee ID, and the like. The user DB 402 stores a payer ID that identifies a default payer when the expense is recorded by the company to which the user belongs in association with the user ID. The default business number associated with the account when it is recorded as an expense may be stored. The user DB 402 stores information that identifies the user's bank account or payment information that is information on the user's personal credit card.

FIG. 7 is a diagram showing an example of the content of the information stored in the provider DB 403. The provider DB 403 stores attributes such as the name of the provider, the type of the provider, and the like for the provider ID of the provider of the service or product. The provider ID may be identified by a direct service providing staff, for example, a taxi driver, a restaurant store or a restaurant staff ID, etc. when the provider is organized, or for each business operator. It may be identified. The provider DB 403 stores information that identifies a bank account for depositing fees to the provider.

FIG. 8 is a diagram showing an example of the contents of the information stored in the payer DB 404. The payer DB 404 stores attributes such as the name of the company that is the payer in association with the payer ID of the payer. The payer DB 404 stores information that identifies the payer's bank account for withdrawal and payment.

The payer ID is issued by the platform operator in response to an application from the payer company. User IDs are issued to applications from payers only for users who belong to the payer's organization. The user ID may be issued personally, in which case the payer defaults to the user himself. The information stored in the user DB 402 and the payer DB 404 may be remotely registered by the payer from the payer terminal device 3 in association with the issued payer ID or user ID. The information stored in the provider DB 403 may also be registered in association with the provider ID issued by the administrator in response to the membership application from the service or product provider.

FIG. 9 is a diagram showing an example of the contents of the information stored in the form DB 405. The form DB 405 stores the digital form DF. The digital form DF is a transaction ID, issuance date and time, use start date and time, use end date and time, purpose of use, name of service or product used, detailed content, amount of money, user ID of user, provider of service or product. Includes the provider ID and the payer ID of the payer. The digital form DF includes the type of personal burden or expense processing. In the case of expense processing, the business number should be included so that the account item can be identified. When the cost is shared between the payer and the user himself / herself for one use, the user ID or the payer ID of another payer is included as the second payer. The digital form DF is information that can be issued by any one of the user ID of the user, the provider ID of the provider who provides the service or the product, and the payer ID of the payer. The digital form DF will be completed in sequence according to the progress of service provision as described later. The digital form DF allows the information required for payment to be finalized after the service is completed.

FIG. 10 is a diagram showing an example of the content of the information stored in the recruitment condition DB 406. The solicitation condition DB 406 stores the contents of the solicitation condition included in the request from the user terminal device 1, the provider terminal device 2, or the payer terminal device 3 transmitted to the information creation device 4. The solicitation conditions are associated with a solicitation ID for identifying the solicitation, and include the contents of conditions such as charges and places, and the transaction ID of the digital form DF issued by the solicitation. When the recruitment is completed, the recruitment condition is deleted by the information creation device 4.

The information creation device 4 that functions as a platform in the information creation system 100 configured in this way issues a digital form DF when at least one of the user ID, the provider ID, and the payer ID is determined. In the digital form DF, the user ID indicates who the user is in the transaction related to the enjoyment of the service or the product. The provider ID corresponds to what the service or product provided to the user is. The payer ID indicates who pays for the service or goods. The information creation device 4 completes the digital form DF that is the basis of payment when all the information in the issued digital form DF is confirmed. The information creation device 4 can request payment from the payment service based on the completed digital form DF, and when the payment is completed, it is possible to create expense information and send it to the payer terminal device 3. is there.

The procedure for preparing to use the platform will be explained. In preparation for use, the accounting department of the company installs the terminal application program 3P distributed from the information creation device 4 or the distribution server (not shown) on the personal computer. The personal computer, which is a general-purpose computer, functions as the payer terminal device 3 of the information creation system 100 by installing the terminal application program 3P and the account information issued to the company as the payer ID. Based on the terminal application program 3P, the payer terminal device 3 receives registration of attributes such as a payer ID and a name from an operator in the accounting department, and transmits the received payer ID and attribute information to the information creation device 4. .. The payer ID may be issued by the platform operator that manages the information creation device 4 by prior application. The payer terminal device 3 receives the information of the bank account for payment used for payment of the fee to the provider of the service or the product, and transmits the information to the information creation device 4. As a result, as shown in FIG. 6, the payer information is stored in the payer DB 404 in association with the payer ID. Based on the operation of the operator, the payer terminal device 3 requests the information creation device 4 to issue user IDs for the number of users belonging to an organization such as a company that is the payer, and the issued user IDs. Should be received.

In the information creation system 100 of the first embodiment, the user installs the terminal application program 1P distributed from the information creation device 4 or a distribution server (not shown) on the smartphone. The smartphone, which is a general-purpose computer, functions as the user terminal device 1 of the information creation system 100 by installing the application program 1P for the terminal and the account information issued to the user as the user ID. Based on the terminal application program 1P, the user terminal device 1 accepts registration of attributes including contact information such as user ID, name, and e-mail address from the user, and creates information on the received user ID and attribute. It is transmitted to the device 4. The user ID is preferably issued in advance by the information creation device 4 in response to an application from the company to which the payer belongs, as described above, in order to accurately associate the relationship with the default payer. The user terminal device 1 accepts registration of payment information for personal use of the terminal application program 1P and transmits it to the information creation device 4. The payment information for personal use is the user's personal bank account or credit card information. As a result, as shown in FIG. 6, the user information is stored in the user DB 402 in association with the user ID.

At the usage preparation stage, the provider of the service or product installs the terminal application program 2P distributed from the information creation device 4 or the distribution server (not shown) on the tablet terminal of the personal computer or the staff. By installing the application program 2P for the terminal and the account information issued as the provider ID in advance based on the contract with the platform operator, the personal computer or tablet terminal that is a general-purpose computer can be the provider terminal of the information creation system 100. It functions as a device 2. Based on the terminal application program 2P, the provider terminal device 2 accepts registration of attributes such as the provider ID and name from the operator of the service provider, and transmits the received provider ID and attribute information to the information creation device 4. To do. When a plurality of provider terminal devices 2 are used by the same service provider, registration may be accepted by the provider terminal device 2 of the personal computer used by the operator of the accounting department of the provider. The specific provider terminal device 2 receives the information of the bank account for deposit used for depositing the fee related to the service or the product, and transmits it to the information creation device 4. As a result, as shown in FIG. 7, the provider information is stored in the provider DB 403 in association with the provider ID.

As part of the preparation for use, the provider terminal device 2 requests the platform operator to issue a service code that identifies the service. The service code is, for example, an ID that identifies the provider for each event unit and may be the same as the provider ID, or is an ID that individually identifies the staff when the provider is composed of a plurality of staff. It may be present, or it may be an ID that identifies the location of staff. In this case, the specific provider terminal device 2 may request the information creation device 4 to issue a service code corresponding to the number of staff identification information in association with the information identifying each staff member. The provider terminal device 2 other than the specific provider terminal device 2 receives and uses the service code including at least the provider ID issued to the provider. When the service code is attached so as to identify the staff or the location, etc., instead of each provider, the provider terminal device 2 used by each staff is a service code in which the information for identifying the staff is combined with the provider ID. May be used. The provider may present a two-dimensionally coded provider ID or service code at the service provision location. The presentation method may be a method of printing and sticking on a sticker medium, or a method of being displayed on the display unit 23 of the provider terminal device 2.

The processing at the time of actual service use based on the above-mentioned usage preparation will be described with reference to the flowchart. When the information creation device 4 of the platform receives a request from any one of the user, the provider, or the payer, such as wanting to receive the service (product) or recruiting users of the service (product), the user , Match between providers and payers. Specifically, the information creation device 4 executes the following processes. FIG. 11 is a flowchart showing an example of a processing procedure in the information creation device 4.

The user terminal device 1 is a position information acquisition unit while using the terminal application program 1P using the user ID, that is, while displaying a screen for the user based on the terminal application program 1P. The position information that can be acquired in 16 is sequentially transmitted to the information creation device 4.

The control unit 40 of the information creation device 4 sequentially stores the position information transmitted from the user terminal device 1 in the storage unit 41 in association with the user ID corresponding to the user terminal device 1 from which the position information is transmitted. To do. The location information may be stored in the user DB 402 in association with the user ID and updated sequentially.

The control unit 40 of the information creation device 4 receives a request for recruitment of a user, a provider, or a payer from any of the user terminal device 1, the provider terminal device 2, or the payer terminal device 3 (step S101). ). The recruitment request includes an ID for identifying the request source and recruitment conditions.

The control unit 40 assigns a transaction ID in response to the received solicitation request and issues a digital form DF (step S102). The digital form DF is created including the transaction ID and at least one of the request source user ID, provider ID, and payer ID. After being stored in the form DB 405 as a digital form DF, the user, the provider, or the payer can search and browse.

The control unit 40 associates the recruitment conditions included in the received recruitment request with the recruitment ID and stores them in the recruitment condition DB 406 (step S103). In the solicitation condition DB 406, the solicitation ID and the transaction ID of the digital form DF issued in step S102 are stored in association with each other. In the recruitment condition DB 406, the control unit 40 stores information indicating that recruitment is in progress in association with the recruitment ID.

The control unit 40 extracts the user ID of the user or the user ID of the provider corresponding to the solicitation condition of the request received in step S101 according to the latest location information of the user, the service type of the provider, and the like. (Step S104).

The control unit 40 associates the contents of the recruitment received in step S101 with the user of the user ID extracted in step S104 or the provider of the provider ID (step S105). Specifically, in step S105, the control unit 40 stores the user ID or the provider ID extracted in step S104 in association with the recruitment ID of the recruitment conditions stored in step S103.

By associating in step S105, the user terminal device 1 of the extracted user ID or the provider terminal device 2 of the provider ID can display the associated solicitation list. In step S105, the recruitment content may be push-notified to the extracted user ID or provider ID.

The control unit 40 accepts an application for recruitment from the user of the user ID extracted in step S104 or the provider of the provider ID (step S106).

It should be noted that steps S104 and S105 are not indispensable, even from the user terminal device 1, the provider terminal device 2, and the payer terminal device 3 used by a user other than the extracted user ID user and the provider of the provider ID. Search and application may be possible. The digital form DF may be listed in the digital ticket market according to information such as type, time, provider, etc. by the operation of the user, provider, payer, or other administrator, and may be easily searched and browsed. ..

The control unit 40 notifies the request source of the contents of the accepted application (step S107), and accepts the selection from the users or providers who have applied (step S108). The control unit 40 notifies the user terminal device 1 of the selected user or the provider terminal device 2 of the provider of the selection (step S109) and accepts the confirmation (step S110).

When the user and the provider are confirmed by the confirmation in step S110, the digital form DF can be used as a digital ticket for the user to receive the service from the provider.

When the confirmation is accepted, the control unit 40 stores that the recruitment has been completed in the recruitment condition DB406 with respect to the recruitment condition stored in step S103 (step S111), and provides the user ID of the user or the provider. The person ID is added to the digital form DF issued in step 102 (step S112).

The control unit 40 monitors the progress of the provision of the service or product corresponding to the digital form DF (step S113). In the progress monitor of step S113, first, the provider ID indicates whether the user indicated by the user ID of the digital form DF actually started using the digital form DF from the provider terminal device 2 or the user terminal device 1. It is confirmed by the provider whether the service or goods are provided. For example, at the start of use, the user reads the service code presented by the service provider by the reading unit 15 of the user terminal device 1. As described above, the service code includes at least the provider ID, and includes information for identifying the staff, the location, and the like. The control unit 10 associates the read service code with the user ID corresponding to the user terminal device 1 and transmits it to the information creation device 4. Alternatively, the user ID presented by the user at the start of provision may be read by the reading unit 25 of the provider terminal device 2 and transmitted to the information creation device 4 in association with the service code of the provider. This confirms that the user has actually started using it.

The control unit 40 determines whether or not the provision of the service or the product is completed and the charge is fixed based on the monitored progress status (step S114). When it is determined in step S114 that the process is incomplete and undecided (S114: NO), the control unit 40 returns the process to step S113.

Whether or not the provision is completed in step S114 may be determined by, for example, the operation unit 24 of the provider terminal device 2 receiving the completion notification, and the control unit 20 notifying the information creation device 4. Whether or not the service has been completed may be determined by reading the completion notification receipt or the like output from the service provider by the reading unit 15 of the user terminal device 1, and notifying the information creating device 4 of the result read by the control unit 10. If it is a taxi, it may be detected by a toll meter such as a taximeter or the completion of processing at the cash register.

When the provision is completed in step S114 and it is determined that the charge has been fixed (S114: YES), the control unit 40 adds the charge in the digital form DF and the content of the service or product provided (step S115), and processes it. To complete. When all the necessary information in the digital form DF is confirmed, the digital form DF is created as transaction information, and settlement and accounting processing can be executed based on the digital form DF.

The realization of the service based on the processing procedure shown in the flowchart of FIG. 11 will be described with reference to specific examples. In the first embodiment, among the various service providers that are members of the platform, the service of the taxi operator will be described as an example. In the information creation system 100 of the present disclosure, any of the user, the provider, and the payer can make a service request.

In the case of a taxi operator's service, the provider terminal device 2 of the provider is, for example, a personal computer installed in the taxi operator's business office. In one example, a tablet terminal or smartphone owned by each driver installs the terminal application program 2P and uses the provider ID and the ID that identifies the driver (staff who provides the actual service). It functions as a provider terminal device 2. The provider terminal device 2 possessed by each driver or mounted on the vehicle includes a position information acquisition unit, and the control unit 20 sequentially obtains the position information of the provider terminal device 2 in the same manner as the user terminal device 1. Is acquired, and the latest position information or the history of the position information is transmitted at the timing of communication connection with the information creation device 4. The information creation device 4 stores the position information transmitted from the provider terminal device 2 in association with an ID or a vehicle number that identifies the driver. The location information may be stored in the provider DB 403 and updated sequentially.

In order for users to use the services of taxi operators on the platform of this disclosure, the first case of recruiting taxis for users to board and the second case of recruiting users for taxis are provided. There is a third case in which a person issues a taxi ticket to recruit users and providers. The realization of ticketless payment using the platform will be described below for each case. In either case, when the digital form DF is issued in response to the request, it will be put up for sale in the digital ticket market, and the digital form will be displayed from the user terminal device 1, the provider terminal device 2, and the payer terminal device 3. It can be searched and browsed by any information such as user ID, provider ID, payer ID, service content, amount of money, etc. included in the DF.

[1. Issuing a request from the user]
As a first case, a case where a user requests to take a taxi will be described as an example. Hereinafter, the processing based on the digital form DF in the first case will be described with reference to the sequence diagram and the screen example.

12 and 13 show an example of a screen displayed on the user terminal device 1. FIG. 12 shows a main screen 130 displayed when the user starts the terminal application program 1P in association with the user ID. The main screen 130 includes, for example, a list of available menus preset by the user among the services that are members of the platform. In the example of FIG. 12, the main screen 130 includes a menu button 131 for taking a taxi. The aspect of the main screen 130 is not limited to the content shown in FIG.

FIG. 13 shows a search screen 132 when the menu button 131 for taking a taxi is selected on the main screen 130. The search screen 132 includes an input screen for setting items for issuing a digital ticket for using a taxi. The search screen 132 includes an arrow icon 133 for changing the options for each of the plurality of items. When the arrow icon 133 is selected, for example, in the case of "departure place", options including "current location" or "address" can be selected from the pull-down menu. On the search screen 132, it is possible to specify the "departure time", "destination", and "desired arrival time" of the taxi to be used. For the destination, if you enter the place or address in the input field, you may be able to search on the map. The search screen 132 includes a recruitment display button 135 for displaying the recruitment contents of taxis recruiting users. The recruitment display button 135 will be described later. In addition, on the search screen 132, it is possible to set the "purpose of use", "business number", "conditions of use", "payment method", and "taxi type" of the taxi for requesting a taxi. .. The "taxi type" can be set to, for example, a VIP-compatible vehicle, a welfare vehicle, a one-box vehicle, or no designation. The "use conditions" are the upper limit of expense processing agreed between the user and the payer, and the conditions set by default may be automatically applied. As the "payment method", one of "expense processing" paid by the company to which the user belongs and "individual use" paid by the user himself can be selected. In the case of "expense processing", the information associated with the account item can be selected as the "business number".

The search screen 132 includes a button 134 for requesting a digital ticket for taxi use based on the digital form DF. When the operation unit 14 detects that the user has tapped the button 134 on the display unit 13, the control unit 10 of the user terminal device 1 transmits a request for a taxi to carry the user to the information creation device 4. To do.

FIG. 14 is a diagram showing a sequence until the digital form DF is completed based on the request from the user terminal device 1. Among the procedures shown in the sequence diagram of FIG. 14, the procedure shown in the flowchart of FIG. 11 in the processing procedure of the information creation device 4 is given the same step number and detailed description thereof will be omitted.

The control unit 10 of the user terminal device 1 accepts the operation of the button 134 on the search screen 132 of FIG. 13 and transmits a request for a taxi to carry the user from the communication unit 12 (step S201). The request includes "purpose of use", "business number", "conditions of use", "payment method", and "conditions of request" set on the search screen 132.

The control unit 40 of the information creation device 4 receives the request from the user terminal device 1, accepts the request (S101), and issues a digital form DF based on the request (S102). In this case, as the digital form DF created in step S102, as shown in the form DB 405 of FIG. 9, only the user ID is determined among the user ID, the provider ID and the payer ID. ..

FIG. 15 is a schematic diagram showing the process of completing the digital form DF. FIG. 15 shows the process in which each item of the digital form DF is filled in the order of A, B, and C. As shown in FIG. 15A, at the stage of step S102, (1) information for identifying a transaction (transaction ID), (2) information indicating the content of the provided service or product, which are items necessary for payment or expense processing. (Item), (3) Fee, (4) Service or product provider (payee), (5) Service or product user, (6) Fee payer, (5) is determined (1) is in the state of being numbered. Since the "payment method" included in the request received in step S101 is "expense processing", the payer of (6) is tentatively determined by the company to which the user belongs. As described above, in the platform in the present disclosure, a digital form DF which is a source of payment and expense processing is created at a stage when the payer and the provider are not determined.

The description will be continued by returning to the sequence diagram of FIG.
The control unit 40 of the information creation device 4 stores the recruitment conditions from the request received in step S101 (S103), and sequentially receives the provider IDs of the providers that match the recruitment conditions from the provider terminal device 2. Extract based on the position information (S104). In step S104, the control unit 40 provides each provider of the taxi provider terminal device 2 at a position where the taxi provider terminal device 2 can arrive at the departure point included in the request within a predetermined time (for example, 1-5 minutes) from the departure time. Extract based on the position information from the terminal device 2.

The control unit 40 associates the extracted provider ID with the recruitment ID of the recruitment conditions stored in step S103 (S105).

The control unit 40 may send a notification to the provider terminal device 2 extracted in step S105 that there is a taxi recruitment in ascending order of distance to the departure point, or the provider terminal device 2 may be transmitted. The taxi driver used may apply for the recruitment by searching for the recruitment.

The control unit 20 of the provider terminal device 2 receives the notification or acquires the recruitment by searching (step S301), and accepts the application for the recruitment (step S302).

The acceptance of applications will be described with reference to a screen example of the provider terminal device 2. 16 and 17 show an example of a screen displayed on the provider terminal device 2. FIG. 16 shows the main screen 230 displayed when the provider starts the terminal application program 2P in association with the provider ID. The main screen 230 shown in FIG. 16 is displayed based on an application program incorporated in the terminal application program 2P specialized for taxi operators. The main screen 230 includes a taxi vehicle day schedule, a menu button 231 for finding nearby passengers, and a button 232 for requesting passengers. The processing by the button 232 will be described later. In the example of FIG. 16, the schedule shows the current time and the reservation status. The aspect of the main screen 230 is not limited to the content shown in FIG.

FIG. 17 shows a search screen 233 when the menu button 231 for searching for passengers is selected on the main screen 230. On the search screen 233, if there is a recruitment targeting the provider ID corresponding to the provider terminal device 2, a list 234 of the recruitment contents is displayed. In list 234 of FIG. 17, among the recruitment from which the provider ID is extracted, a list of recruitment narrowed down by the departure / arrival time and the departure / arrival point based on the reservation status is displayed as a narrowing condition. List 234 of the search screen 233 includes a button 235 for selecting one for each recruitment. When the button 235 is selected, the application from the provider terminal device 2 is accepted.

The description will be continued by returning to the sequence of FIG. When any button 235 is selected for application on the search screen 233 shown in FIG. 17, the application notification is transmitted from the communication unit 22 to the information creation device 4 by the control unit 20 of the provider terminal device 2. (Step S303).

The control unit 40 of the information creation device 4 accepts the application (S106) and notifies the user terminal device 1 of the requesting user of the content of the accepted application (S107).

The control unit 10 of the user terminal device 1 receives the notification of the application (step S202) and receives the selection of the application (step S203). FIG. 18 is a diagram showing an example of the contents of the application notification screen 136 to the user. The notification screen 136 is displayed after waiting after selecting the request button 134 on the search screen 132 of FIG. The notification screen 136 displays a list of information on taxis that have applied for the request, and includes a selection button 137. The user selects one of the taxis and selects the corresponding selection button 137.

The description will be continued by returning to the sequence of FIG. When the selection button 137 is selected on the notification screen 136 shown in FIG. 18, the selection result is transmitted from the communication unit 12 to the information creation device 4 by the control unit 10 of the user terminal device 1 (step S204).

In the information creation device 4, the control unit 40 accepts the selection by receiving the selection result (S108), and notifies the provider terminal device 2 of the selected provider of the selection (S109).

The control unit 20 of the provider terminal device 2 receives the selection notification (step S304), accepts the confirmation, and transmits it to the information creation device 4 (step S305).

The control unit 40 of the information creation device 4 receives confirmation from the provider terminal device 2 (S110). If there are multiple applications in step S106, it is advisable to notify the unselected providers that they have not been selected. In the provider terminal device 2, after the screen shown in FIG. 17, a notification screen indicating that the application has been selected is displayed, and confirmation is accepted by the confirmation button included in the notification screen.

The control unit 40 of the information creation device 4 adds the provider ID of the selected provider to the digital form DF (S112). As a result, as shown in FIG. 15B, the item of the provider is filled in the digital form DF.

FIG. 19 shows an example of the digital ticket 138 displayed on the user terminal device 1. FIG. 19 shows the contents of the digital ticket 138 for taxi use, which can be used by the user in response to the request when the selection button 137 is selected in FIG. The digital ticket 138 includes information such as a transaction ID of the digital form DF on which the ticket is based, a ticket issuance date, service contents, and charges.

After that, the control unit 40 sequentially determines the progress status such as whether or not the requesting user has boarded the taxi of the provider ID of the selected provider and whether or not the taxi has arrived by the scheduled time. Monitor based on the transmitted position information, information such as confirmation of boarding in a taxi (S113). The control unit 40 determines whether or not the service provision is completed and the charge is fixed, depending on whether or not the taxi provider terminal device 2 has notified the taxi to get off and the charge is fixed (S114).

When the control unit 40 receives a notification of charge confirmation from the provider terminal device 2 (S114: YES), the content and charge of the service provided after being confirmed or approved by the user terminal device 1 and the payer terminal device 3 And the payer is confirmed and added to the digital form DF (S115). FIG. 20 is a diagram showing an example of the contents of the digital ticket 138. In the digital ticket 138 displayed in FIG. 19, after the charge is confirmed, as shown in FIG. 20, the confirmed charge is displayed in the charge column, and a confirmation button 139 confirmed by the user is included. When the confirmation button 139 is selected, the information creation device 4 accepts the confirmation. In the digital ticket 138 of FIG. 20, if the fixed charge is within the upper limit according to the usage conditions between the payer and the user in the case of expense processing, the payer is the affiliated company, and a partial charge exceeding the upper limit. Will be decided at the time of S115, such as personal burden. In addition, a notification may be transmitted to the payer terminal device 3 and approval may be obtained by operating the payer terminal device 3. As a result, as shown in FIG. 15C, all the items are filled in the digital form DF, and settlement and expense processing become possible based on this.

[2. Request issued by the provider]
As a second case, a case where a taxi operator, which is a provider, recruits users will be described as an example. Hereinafter, the processing based on the digital form DF in the second case will be described with reference to the sequence diagram and the screen example.

The control unit 20 of the provider terminal device 2 transmits a request for recruiting taxi passengers to the information creation device 4 by the button 232 for making a passenger request on the main screen 230 of the provider terminal device 2 of FIG.

FIG. 21 is a diagram showing a sequence until the digital form DF is completed based on the request from the provider terminal device 2. Among the procedures shown in the sequence diagram of FIG. 21, the same step number or the corresponding step number is used for the processing procedure starting from the user terminal device 1 of FIG. 14 and the process common to the procedure shown in the flowchart of FIG. A detailed description will be omitted.

In the provider terminal device 2, the control unit 20 receives the operation of the button 232 for the passenger request shown in FIG. 16 and transmits a request for recruiting users to take a taxi from the communication unit 22 (step S311). The request includes "request conditions" regarding departure / arrival times and departure / arrival points based on the reservation status.

As a result, the control unit 40 of the information creation device 4 issues a digital form DF in which only the provider ID is determined among the user ID, the provider ID, and the payer ID. FIG. 22 is a schematic diagram of the digital form DF in the second case. FIG. 22 shows the process in which each item of the digital form DF is filled in the order of A, B, and C. As shown in FIG. 22A, at the stage of step S102, (1) is numbered by determining (4) the provider (payee) of the service or product among the items required for settlement or expense processing. It is in a state. As described above, the platform in the present disclosure issues a digital form DF that is the source of payment and expense processing at the stage when the user and the payer are not determined.

The description will be continued by returning to the sequence of FIG. The control unit 40 of the information creation device 4 extracts the user ID of the user who matches the recruitment condition corresponding to the request received in step S101 based on the position information sequentially received from the user terminal device 1. (S104). The extraction in step S104 may be narrowed down to the user terminal device 1 or the like in which the terminal application program 1P is active. In step S104, the control unit 40 uses, for example, the user terminal device 1 of the user who is using the terminal application program 1P at a place near the departure point included in the request based on the position information of the user terminal device 1. To extract. The control unit 40 associates the extracted user ID with the recruitment ID of the recruitment conditions stored in step S103 (S105).

By associating the recruitment ID with the user ID in step S105, when the control unit 10 of the user terminal device 1 selects the recruitment display button 135 on the search screen 132 of FIG. 13, the control unit 10 becomes the user ID. Acquire the associated recruitment (step S211). In step S211 the control unit 10 may acquire a recruitment to which the user ID is not associated and later narrow down the search. The control unit 10 displays the acquired recruitment, that is, a list of recruitment contents of a nearby taxi recruiting users, and accepts the application for the recruitment (step S212).

FIG. 23 shows an example of a screen displayed on the user terminal device 1. The screen shown in FIG. 23 is displayed when the recruitment display button 135 is selected on the search screen 132 of FIG. In this case, as shown in FIG. 23, the search screen 132 displays a recruitment list 140 for which the user ID corresponding to the user terminal device 1 is extracted. In the list 140 of FIG. 23, a list of recruitment narrowed down by "destination" and "desired arrival time" as conditions of use is displayed among the recruitment from which the user ID is extracted. Listing 140 includes a button 141 for selecting one for each recruitment. When the button 141 is selected, the application from the user terminal device 1 is accepted.

The description will be continued by returning to the sequence of FIG. When the selection button 141 is selected in the list 140 shown in FIG. 23, the control unit 10 of the user terminal device 1 transmits an application notification from the communication unit 12 to the information creation device 4 (step S213). ..

The control unit 40 of the information creation device 4 accepts the application (S106), and notifies the provider terminal device 2 of the requesting provider of the content of the accepted application (S107).

The control unit 20 of the provider terminal device 2 receives the notification of the application (step S312) and receives the selection of the application (step S313). In the provider terminal device 2, information on passengers as users who have applied for the request is displayed as a list on the display unit 23 on a screen similar to the search screen 233 shown in FIG. 17, and by selecting the button 235. One of the users is selected. The taxi selects one of the users and goes to the place of the user who applied.

The description will be continued by returning to the sequence of FIG. When the user who has applied as a passenger is selected, the control unit 20 of the provider terminal device 2 transmits the selection result from the communication unit 22 to the information creation device 4 (step S314).

In the information creation device 4, the control unit 40 accepts the selection by receiving the selection result (S108), and notifies the user terminal device 1 of the selected user of the selection (S109).

The control unit 10 of the user terminal device 1 receives the selection notification (step S214), accepts the confirmation, and transmits it to the information creation device 4 (step S215).

The control unit 40 of the information creation device 4 receives confirmation from the user terminal device 1 (S110). If there are multiple applications in step S106, it is advisable to notify the users who have not been selected that they have not been selected. In the user terminal device 1, after the screen shown in FIG. 23, a notification screen indicating that the application has been selected is displayed, and confirmation is accepted by the confirmation button included in the notification screen.

The control unit 40 of the information creation device 4 adds the user ID of the selected user to the digital form DF (S112). As a result, as shown in FIG. 22B, the user's items are filled in the digital form DF.

After that, the control unit 40 proceeds with whether or not the user terminal device 1 of the user ID of the selected user has boarded the taxi of the request source, and whether or not the taxi has arrived by the scheduled time. The situation is monitored based on information such as position information transmitted sequentially and confirmation of boarding in a taxi (S113). Subsequent processing is the same as in the first case. Then, as shown in FIG. 22C, all the items are filled in the digital form DF, and settlement and expense processing become possible based on this.

[3. Request issued by payer]
As a third case, a case where the payer recruits providers and users will be described as an example. Hereinafter, the processing based on the digital form DF in the third case will be described.

In the payer terminal device 3, as in the first case or the second case, the control unit 30 has an undecided user and provider based on the terminal application program 3P associated with the payer ID. You can send a request to issue a digital ticket. For example, as in the first case and the second case, when a user belonging to an organization corresponding to a payer needs to move to a specific place by taxi for business purposes, a request is made from the user terminal device 1. In the same way, the user can receive the service cashlessly even if the is not sent, and the provider can receive the payment from the payer. In the case where a taxi ticket is usually distributed to the payer to pick up and drop off the customer, the digital ticket issued by the request from the payer terminal device 3 is transferred to the user terminal device 1 of the user to be determined later. You can send it to.

The processing procedure in the third case can be described with reference to the flowchart of FIG. 11 and the sequences of FIGS. 13 and 21.

The control unit 30 of the payer terminal device 3 transmits a request for recruiting taxis and passengers from the communication unit 32 based on the terminal application program 3P corresponding to the payer ID. In the request, for example, a type of service called a taxi and a condition for making the user a user belonging to the payer's organization are specified. Further, for example, a user ID of a specific user who belongs to an organization and is in business and needs to be moved may be specified. In the request, the payer ID of the payer and the user ID of the user (customer) who is the owner of the digital ticket based on the issued digital form DF may be specified.

In the third case, the control unit 40 of the information creation device 4 issues a digital form DF determined only by the payer ID based on the request (S102), and extracts both users and providers corresponding to the recruitment conditions. (S104). Here, the provider may be extracted by extracting a taxi existing near the specific user based on the location information of the user terminal device 1 of the specific user ID. The extracted user ID and provider ID are associated with the recruitment ID related to the request (S105).

As a result, when the provider tries to search for passengers on the provider terminal device 2, a list of recruitment contents is displayed on the display unit 23, and the provider is designated by a user belonging to the organization corresponding to the payer or the payer. It will be possible to apply as a taxi with passengers as passengers. FIG. 24 is a diagram showing an example of a screen displayed on the provider terminal device 2. In FIG. 24, the main screen 230 shown in FIG. 16 displays the contents of the taxi recruitment for carrying any employee belonging to DEF Trading as a payer, and the button 236 for applying for the recruitment is displayed. ..

Further, in the third case, a list of recruitment contents may be displayed as a list of "issued digital tickets" displayed on the display unit 13 of the user terminal device 1. FIG. 25 is a diagram showing an example of a screen displayed on the user terminal device 1. In FIG. 25, a button 142 for selecting a digital ticket issued by a request from the payer is added to the search screen 132 shown in FIG. When the button 142 is selected, the user can apply for the use of any of the tickets based on the ticket list including the transaction ID of the digital form DF for taxi that can be used by the user.

When the provider or the user applies for the recruitment, the information creation device 4 accepts the application and matches. For example, the control unit 40 may allow the payer terminal device 3 to select the list of taxis that are the providers who applied in FIG. 24, or display it on the user terminal device 1 of the target user. It may be possible to select. Similarly, the list of users who applied in FIG. 25 may be selected by the payer terminal device 3, or may be displayed and selected by the taxi provider terminal device 2 which is a nearby provider. You may be able to do it. The control unit 40 may automatically match the two according to the position of the taxi and the destination of the user.

A paper medium that prints out the transaction ID of the issued digital form DF (at least the payer ID has been confirmed) is given to the user, and the provider selected by the user gives a digital ticket based on the transaction ID. By searching for and using this, users, providers, and payers may be matched. That is, the application for the recruitment is not limited to the exchange of information between the user terminal device 1, the provider terminal device 2, and the payer terminal device 3, and may be the presentation of the transaction ID when using the service.

FIG. 26 is a schematic diagram of the digital form DF in the third case. FIG. 26 shows the process in which each item of the digital form DF is filled in the order of A, B, and C. As shown in FIG. 26A, at the stage where the information creation device 4 issues the digital form DF based on the request from the payer terminal device 3, among the items necessary for settlement or expense processing, (6) payment of charges It is a state in which (1) is numbered by determining the person. As described above, the platform in the present disclosure issues a digital form DF that is the source of settlement and expense processing at the stage when the user and the provider are not determined. For example, when a provider applies for recruitment, the provider selected by the payer is determined, and as shown in FIG. 25B, the information of the provider in the digital form DF is determined. In the subsequent processing, as in the second case, the user who applied is selected by the payer or the provider, and the progress status such as whether or not the selected user has boarded the taxi of the provider is checked. When the charge is monitored and the charge is fixed, all the information is fixed and the digital form DF is completed as shown in FIG. 26C, and payment and expense processing become possible.

As described above, the platform in the present disclosure issues a digital form DF that is the basis of payment and expense processing at the stage when two of the user, the provider, and the payer are not determined. That is, any of the user, the provider, and the payer can make a service request. In the information creation system 100, the information creation device 4 solicits service providers, payers, users, etc. that match the request, and obtains a digital form DF in which the information and charges of the users, providers, and payers are fixed. When completed, payment and expense processing based on the digital form DF will be possible.

In the description of the first embodiment, only the taxi is described as the cost of transportation, but it can be applied to other public transportation such as buses, trains, and airplanes. For example, in the information creation device 4, instead of accepting applications for recruitment, the provider terminal device 2 provides search results of buses, trains, airplanes, etc. that can be used to the destination (in the case of limited express trains and airplanes, flights with vacancy, etc.). We accept each from, accept selection from the search results, and notify the provider of the selected provider of the user ID of the user to use. If the user ID can be confirmed (authenticated) from the user terminal device 1 at the time of use by the user, then the usage status is monitored and the digital form DF is confirmed when the charge is confirmed. be able to. If the user ID is associated with the transportation IC card, it is possible to confirm the use of the user by the card information on the transportation IC card.

The user searches for vacant transportation on the search screen 132 displayed on the user terminal device 1 while connecting to a plurality of transportations, and makes a request to each of them or makes an existing digital form DF. You may select the matching transportation system from the recruitment based on.

(Embodiment 2)
In the second embodiment, the service provided by the taxi operator will be described among the various service providers using the platform. The taxi operator, which is the service provider in the second embodiment, realizes a shared taxi service by using the platform.

As shown in the first embodiment, by using the platform of the present disclosure, even if there is no payment by cash or credit card at the time when the fee is fixed, the service content, that is, the service provider based on the content of the service, that is, the service provider. You can pay to. When using the platform of the present disclosure, even if one user is using a taxi as a passenger and another user with a different departure point or end point gets on as a passenger, the service content of each user ( If the distance) can be determined, it is possible to settle the discount after the fact depending on the time of sharing. Since the configuration and the processing procedure to be executed in the second embodiment are the same as those in the first embodiment, the realization of the carpooling service will be described below using the same reference numerals.

In order to realize the shared taxi service according to the second embodiment, the recruitment conditions include whether or not shared riding is possible, the number of passengers in one request, the number of passengers in a taxi, and the attributes of passengers or drivers (for example, gender, etc.). Information on the type of taxi, etc. is required.

FIG. 27 shows an example of the contents of the search screen 132 displayed on the user terminal device 1 according to the second embodiment. In the second embodiment, in addition to the "purpose of use", "business number", "condition of use", "payment method", and "taxi type" as the condition of the request, the "condition" set on the search screen 132 is shared. The availability, the number of passengers, and the desired passenger or driver attributes are set. Carpooling may be a condition that can be selected only when "Vehicle type: One box" or "Welfare vehicle" is selected in "Taxi type".

FIG. 28-30 is a sequence diagram showing an example of a processing procedure relating to a digital form DF that realizes carpooling of taxis. Among the processing procedures shown in FIGS. 28 to 30, the sequence in FIG. 14 of the first embodiment and the procedure common to the processing procedure of the information creating apparatus 4 in FIG. 11 are given the same step numbers and detailed explanations will be given. Omit.

When the request button 134 is selected on the search screen 132 shown in FIG. 27, a request for recruiting taxis from the user terminal device 1 under the condition that the user can ride together is transmitted to the information creation device 4. (S201).

The control unit 40 of the information creation device 4 executes the processes S101-S105 for the request from the user terminal device 1 of the first user. The control unit 40 notifies the user terminal device 1 of the application from the provider terminal device 2 transmitted from step S303, including the condition that carpooling is possible (S107).

In the provider terminal device 2, when the own device is associated with the solicitation from a nearby user, the control unit 20 acquires the solicitation (S301) and accepts the application (S302).

The application of step S302 may be accepted by the provider terminal device 2 by voice. On the search screen 233 of FIG. 17, information on whether or not carpooling is possible is added to each of the displayed recruitment content list 234, and the carpooling possible recruitment content can be selected. In step S302, the taxi provider terminal device 2 on which the passengers are already on may be notified by voice that a recruitment for carpooling is coming, and whether or not to apply may be accepted by voice recognition ( S302). In the taxi provider terminal device 2 on which passengers are already on board, another digital form DF is issued. That is, it is possible to have a digital form DF having a common provider ID, in which services are executed at the same time.

In accepting applications in step S302, it is essential to select whether or not to apply in a carpooling state from the taxi provider terminal device 2 that already has passengers, and whether or not to recruit more shared passengers. Good.

The control unit 40 of the information creation device 4 sends an application from the provider terminal device 2 to the user terminal device 1 of the request source of S101 together with the conditions (whether the carpooling state or whether to recruit more shared passengers). Notify (S107) and accept selection (S108). In the step of selecting step S108, it is preferable to select whether or not to recruit more shared passengers.

The control unit 40 notifies the selected provider terminal device 2 of the selection (S109), accepts the confirmation (S110), and executes the process of the following step S121 before, after, or simultaneously with these processes. (Implemented after S110 in FIGS. 28-30).

In step S121, the control unit 40 has selected to further recruit shared passengers for the application received from the selected provider terminal device 2 in step S106, or in the step of accepting the selection in step S108. It is determined whether or not it is selected as possible to recruit more shared passengers (step S121).

When it is determined that recruitment of shared passengers is not selected (S121: NO), the control unit 40 advances the process to step S111 and executes the subsequent processes. In this case, the passenger starts using the taxi selected by one person, or starts using the taxi that already has passengers.

When it is determined that it is selected to recruit more shared passengers (S121: YES), the control unit 40 specifies only the provider ID corresponding to the selected provider terminal device 2 in the digital form DF. Is issued (step S122). The control unit 40 extracts the user ID of the user who matches the recruitment condition for carpooling based on the position information sequentially received from the user terminal device 1 (step S123). The control unit 40 associates the extracted user ID with the recruitment ID of the recruitment condition stored in step S103 (step S124). Before step S122, the control unit 40 may assign a recruitment ID, store the new recruitment content, and associate it in step S124. Steps S122-124 and subsequent processes may be performed in parallel with the start of boarding the taxi of the requesting user.

After that, the control unit 40 accepts an application from a new passenger user by the process (step S126) corresponding to step S106 in the sequence diagram of FIG. 21, and the user of the provider terminal device 2 or the original request sender. Notify the user terminal device 1 (step S127) and accept the selection (step S128).

During this time, the user terminal device 1 and / or the provider terminal device 2 accepts the application notification (step S222, step S322), accepts the selection (step S223, step S323), and transmits the selection (step S224, step). S324).

The control unit 40 notifies the user terminal device 1 of the selected user of the selection (step S129) and accepts the confirmation (step S130).

In the other user terminal device 1, the recruitment associated in step S124 is acquired (step S231), the application is accepted (step S232), and the application is transmitted (step S233). When the selection is notified, the control unit 10 of the user terminal device 1 accepts the selection notification (step S234), receives the confirmation from the user, and transmits it (step S235).

The control unit 40 of the information creation device 4 subsequently executes step S111, adds the provider to the digital form DF in step S102, and adds the user to the digital form DF in step S122 if there are more passengers. (Step S131), and monitor the progress of the digital form DF (step S132).

When the control unit 40 detects that one of the shared riders has disembarked and the service provision has ended (step S133), the control unit 40 calculates the distance used by the disembarked user and the charge considering the discount due to the shared ride. (Step S134), and add the calculated charge (step S135). In step S134, the control unit 40 may apply a discount according to the distance in the shared riding section, or may apply a discount to all the used sections for using the shared riding.

The control unit 40 determines whether or not the service provision of all the shared users has been completed (step S136), and if it is determined that the service provision has not been completed (S136: NO), the process proceeds to step S132. return.

When it is determined in step S136 that the service provision is completed (S136: YES), the control unit 40 ends the process.

The process for realizing carpooling is not limited to this, and for example, not only the providers who meet the recruitment conditions at the time of step S104 but also the users who meet the recruitment conditions may be extracted. In the extraction in step S104, the control unit 40 of the information creation device 4 is used not only by the provider terminal device 2 but also by the user in step S105 around the departure point and the routeable point of the taxi use route included in the request. The person terminal device 1 is also associated. Then, in step S106, applications may be accepted from both the user terminal device 1 and the provider terminal device 2.

Although the provider terminal device 2 has been described as being used for each taxi vehicle and each crew member, it may be a terminal installed at a taxi business establishment. In this case, the operator may operate the provider terminal device 2 while arranging the taxi and passengers wirelessly with each taxi driver to match the passengers in the carpool.

Similar to the first embodiment, the shared ride may be realized by recruiting users who are allowed to share the ride as passengers, starting from the request from the provider terminal device 2. FIG. 31 shows an example of the contents of the search screen 233 displayed on the provider terminal device 2 in the second embodiment. On the search screen 233 of the provider terminal device 2 of the second embodiment, the position of the passenger, the departure time, the maximum number of passengers, the possibility of carpooling, and the attribute of the user can be set as the "condition" of the request. A button 237 for displaying a drop-down menu is included next to each item of the request condition, and the condition can be set. Gender can be specified as a user attribute. As a result, a shared taxi exclusively for women can be realized. It is possible to set whether or not to share a carpool by selecting in the drop-down menu displayed when the button 237 is selected. Further, when sending a request from the provider terminal device 2 or when applying for the request, it is possible to select a setting such as a discount from the drop-down menu.

When the type of taxi is a welfare vehicle and a vehicle that can be used by a plurality of users, it is possible to recruit passengers who need to move in a wheelchair.

As shown in the second embodiment, the use of the platform of the present disclosure enables payment settlement in a shared taxi. For the user, it is possible to settle later by the amount of the actual distance traveled after receiving a discount due to the possibility of carpooling. Not only expense processing but also personal use is possible. Even if a user who has selected expense processing and a user who has selected personal use are on board, settlement and expense processing are possible based on their respective digital form DFs. By using the platform of the present disclosure in this way, it becomes easy to realize a shared taxi business.

(Embodiment 3)
In the first and second embodiments, the application to a taxi or other transportation means has been described as an example, but the application is also applicable to the provision of other services. In the third embodiment, a case where it is applied to the services of accommodation facilities and restaurants will be described. Specifically, the accommodation facility that is the provider will be described as an example of recruiting users who exist near the facility as guests. The process of recruiting users described below can also be applied to the process of recruiting customers at restaurants.

FIG. 32 shows an example of the screen displayed on the provider terminal device 2 in the third embodiment. The provider terminal device 2 is used by installing the terminal application program 2P on a personal computer installed in each accommodation facility and using it based on the account information corresponding to the provider ID, and is operated by the facility administrator. .. On the main screen 230 shown in FIG. 32, a list of accommodations on the day and a button 232 for requesting to recruit guests are displayed based on the terminal application program 2P incorporated in the accommodation management application specialized for accommodation facilities. including. As shown in FIG. 32, the number of guests staying at the accommodation on the day, discount settings, and the like can be set in the request by the button 237 for the drop-down menu.

When the request button 232 shown in FIG. 32 is selected, the control unit 20 of the provider terminal device 2 informs the communication unit 22 of a request for recruiting guests in step S311 shown in the sequence diagram of FIG. The process of transmitting to the creation device 4 is executed.

Since the processing procedure starting from the request transmitted from the accommodation facility provider terminal device 2 is the same as the sequence after step S311 shown in the sequence diagram of FIG. 21 of the first embodiment, detailed description thereof will be omitted. .. The processing related to the taxi operator in the sequence diagram of FIG. 21 is replaced with the processing at the accommodation facility.

FIG. 33 shows an example of the screen displayed on the user terminal device 1 in the third embodiment. The screen example shown in FIG. 33 is the main screen 130. The main screen 130 includes a notification field 143 in addition to the list of services used. In the notification column 143, a recruitment list 144 for which the user ID corresponding to the user terminal device 1 is extracted is displayed. In list 144 of FIG. 33, for example, a list of recruitment is displayed in which users existing within 1000 m of Shinagawa station are extracted from the provider "E Hotel Shinagawa" shown in FIG. Users with a history of use in the past and users belonging to the organization of payers with a history of payment in the past may be preferentially extracted. Listing 144 includes a button 145 for selecting one for each recruitment. When button 145 is selected, a screen for accepting applications is displayed along with details of the recruitment details.

At the time of application, the user can select whether to handle the expenses or to pay the individual expenses. In the case of expense processing, the digital form DF is completed with the organization to which the user belongs as the payer. With the approval of the payer, payment and expense processing will be possible based on this. In this way, the same processing procedure can be expected to increase sales opportunities for vacant rooms from accommodation facilities, facilitate expense processing, and is extremely convenient for users.

(Embodiment 4)
In the fourth embodiment, medical services will be described among various service providers who use the platform. The medical service provider, which is the service provider in the fourth embodiment, realizes a medical examination service that is publicly subsidized by using the platform. Specifically, the example will be described in which the local government (or country), which is the payer, recruits users under specific conditions as examiners to medical institutions.

FIG. 34 shows an example of the screen displayed on the payer terminal device 3 in the fourth embodiment. The payer terminal device 3 is a personal computer installed in a local government in which a terminal application program 3P corresponding to a payer ID is installed, and is operated by an administrator related to a service in which the local government is the payer. The main screen 330 shown in FIG. 34 includes a button 332 for a request for recruiting examinees for examination on a screen for local governments. As shown in FIG. 34, the request can be set with a drop-down button 331 as a setting item for narrowing down the users to be examined. As shown in FIG. 34, age, gender, and subsidy content can be set as recruitment conditions.

When the request button 332 shown in FIG. 34 is selected, the control unit 30 of the payer terminal device 3 transmits a request for recruiting examinees from the communication unit 32 to the information creation device 4.

Since the processing procedure starting from the request transmitted from the payer terminal device 3 of the local government is the same as the processing procedure described in the third case of the first embodiment, detailed description thereof will be omitted.

FIG. 35 shows an example of the screen displayed on the user terminal device 1 in the fourth embodiment. The screen example shown in FIG. 35 is the main screen 130 displayed based on the terminal application program 1P. In the notification field 143 included in the main screen 130, a recruitment list 144 for which the user ID corresponding to the user terminal device 1 is extracted is displayed. In the list 144 of FIG. 35, a list of recruitment in which the payer “T city” shown in FIG. 35 extracts the users who are the target of the examination coupon is displayed. Listing 144 includes a button 145 for selecting one for each recruitment. When button 145 is selected, a screen for accepting applications is displayed along with details of the recruitment details.

The platform of the present disclosure can be applied not only to the medical examination coupon as described above, but also to subsidize expenses at medical institutions by local governments such as infant medical care, elderly medical care, and vaccination. In this way, in the platform of the present disclosure, the digital form DF can be completed, settled, and expense processed by the completion of the provision of the service from the provider by the user. Therefore, it is possible to inspect whether the user actually received medical treatment. Expenses can be processed after the payer confirms whether or not the payment has been received. Therefore, it is possible for a payer other than the user to pay the actual cost with the evidence that the user actually received vaccination and regular medical examination at a medical institution, that is, the cost can be paid with the medical examination as evidence.

The embodiments disclosed as described above are exemplary in all respects and are not restrictive. The scope of the present invention is indicated by the scope of claims and includes all modifications within the meaning and scope equivalent to the scope of claims.

1 User terminal device 10 Control unit 11 Storage unit 12 Communication unit 13 Display unit 138 Digital ticket 1P, 2P, 3P Terminal application program 2 Provider terminal device 20 Control unit 22 Communication unit 3 Payer terminal device 30 Control unit 32 Communication Unit 4 Information creation device 40 Control unit 41 Storage unit 42 Communication unit 401 Service DB
4P information processing program

Claims (2)

It is an information creation method that creates transaction information required for settlement of consideration for services or products.
Accepting the selection of service or product content,
Send a request for drafting transaction information, subject to the provision of the selected service or product,
A list of provider identification information of the provider of the service or product according to the conditions, payer identification information of the payer who pays the consideration, selection of the provider identification information and the payer identification information, and the service. Alternatively, an information creation method for displaying a search screen including a screen for accepting the selection of whether the payment of the consideration for the product is to be expensed by the payer or to be borne by the user. A computer program that causes a computer equipped with a display unit to display transaction information information required for settlement of consideration for a service or product.
On the computer
Accepting the selection of service or product content,
Send a request for drafting transaction information, subject to the provision of the selected service or product,
A list of provider identification information of the provider of the service or product according to the conditions, payer identification information of the payer who pays the consideration, selection of the provider identification information and the payer identification information, and the service. Alternatively, a computer program that executes a process of displaying a search screen including a screen that accepts the selection of whether the payment of the consideration for the product is the expense processing of the payer or the personal burden of the user.