JP2021149847A - Computer program, digital ticket system, user terminal device and information processing method - Google Patents

Abstract

To provide a computer program, a digital ticket system, a user terminal device and an information processing method which can automatically provide digital tickets seamlessly.SOLUTION: A computer program causes a computer to execute processing of: receiving a schedule of an itinerary by an operation part; transmitting to an information processing device a retrieval request of transaction information that is necessary for settlement of a price of a service or product for one or a plurality of journeys included in the itinerary based on the received schedule; displaying a candidate of the transaction information extracted in response to the retrieval request on a display part in association with provider identification information of a provider of the service or product included in the transaction information for each journey; receiving the approval of the displayed candidate of the transaction information by the operation part; and transmitting to the information processing device a notification of deciding user identification information of a user of the service or product for the approved transaction information.SELECTED DRAWING: Figure 19

Description

The present invention relates to a computer program, a digital ticket system, a user terminal device, and an information processing method relating to a cashless payment method.

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 payments are being made by such electronic money and payment services.

JP-A-2007-328549

Various electronic money and cashless payments have been put into practical use and are becoming widespread. However, cashless payment is often a usage pattern for each service. For example, in the case of a taxi, you can call a taxi via an application program for taxis, and cashless payment is possible. It is necessary to purchase a ticket and secure a seat. For concert tickets, you need to log in to the service provided by the concert organizer to purchase. That is, each service is connected to a Web-based service managed by the service provider, and is provided with vehicles, accommodation, eating and drinking services, and entertainment.

The present invention provides a computer program, a digital ticket system, a user terminal device, and information processing that enable seamless and automatic arrangement of digital tickets for services operated on the same platform even if they are different services. The purpose is to provide a method.

The computer program of the embodiment of the present disclosure receives an itinerary schedule at the operation unit on a computer provided with a display unit and an operation unit, and provides a service for one or more itineraries included in the itinerary based on the accepted schedule. Or, transaction information including the provider identification information of the provider of the service or the product, the payer identification information of the payer who pays the consideration, and the consideration information indicating the consideration, which are necessary for the settlement of the consideration of the product. A search request is transmitted to an information processing device that executes processing on the transaction information, and a candidate for the transaction information extracted in response to the search request for each process is selected as the service or product included in the transaction information. Displayed on the display unit in association with the provider identification information of the provider of the above, the operation unit accepts the approval of the displayed transaction information candidate, and the service or product is used for the approved transaction information. A process of transmitting a notification for confirming the user identification information of the person to the information processing apparatus is executed.

The digital ticket system of the embodiment of the present disclosure is a digital ticket that creates transaction information necessary for settlement of the service or product and provides a digital ticket based on the transaction information to a user of the service or product. In the system, the user terminal device used by the user of the service or product provides a means for receiving the schedule of the user's itinerary and services or a plurality of itineraries included in the itinerary based on the received schedule. The means for transmitting a search request for transaction information required for settlement of consideration for a product to an information processing device that executes processing for the transaction information, and the candidate for the transaction information extracted in response to the search request are described above. A means for displaying in association with the provider identification information of the provider of the service or product included in the transaction information, a means for accepting approval of a candidate for the displayed transaction information, and a service for the approved transaction information. Alternatively, the information processing device is provided with a means for transmitting a notification for confirming the user identification information of the user of the product to the information processing device, and the information processing device identifies the provider of the service or product provider based on the search request. Of the information, the payer identification information of the payer who pays the consideration, the user identification information of the user of the service or the product, and the transaction information including the consideration information indicating the consideration, at least the user identification information is not yet available. A means for extracting confirmed transaction information and the extracted transaction information are transmitted to the user terminal device as candidates together with information on the provider of the service or product indicated by the provider identification information included in the transaction information. The means includes means and means for converting the user identification information of the transaction information into the user identification information of the user of the user terminal device based on the notification transmitted from the user terminal device.

The user terminal device of the embodiment of the present disclosure is a user terminal device used by a user of a service or a product, and is included in the itinerary based on the means for accepting the itinerary schedule and the accepted schedule. For a plurality of processes, the provider identification information of the provider of the service or the product required for the settlement of the consideration of the service or the product, the payer identification information of the payer who pays the consideration, and the consideration information indicating the consideration, A means for transmitting a search request for transaction information including the transaction information to an information processing apparatus that executes processing for the transaction information, and a candidate for the transaction information extracted in response to the search request for each process, the transaction information A means for displaying in association with the provider identification information of the provider of the service or product included in the above, a means for accepting approval of a candidate for the displayed transaction information, and a service or product for the approved transaction information. It is provided with a means for transmitting a notification for confirming the user identification information of the user to the information processing apparatus.

The information processing method of the embodiment of the present disclosure is information processing that creates transaction information necessary for settlement of the service or product and provides a digital ticket based on the transaction information to the user of the service or product. In the method, a step in which a terminal device used by a user of the service or product accepts the schedule of the user's itinerary, and one or more itineraries included in the itinerary based on the schedule accepted by the terminal device. A step of transmitting a transaction information search request required for settlement of consideration for a service or product to an information processing device that executes processing on the transaction information, the information processing device is based on the search request, and the service or product Of the transaction information including the provider identification information of the provider, the payer identification information of the payer who pays the consideration, the user identification information of the user of the service or the product, and the consideration information indicating the consideration, at least The step of extracting transaction information in which the user identification information is undetermined, the information processing apparatus indicates the extracted transaction information of the provider of the service or product indicated by the provider identification information included in the transaction information. The step of transmitting to the terminal device as a candidate together with the information, the terminal device identifies the candidate of the transaction information extracted in response to the search request as the provider of the service or product provider included in the transaction information. A step of displaying in association with information, a step of receiving approval of a candidate for the displayed transaction information by the terminal device, a user of a user of a service or a product with respect to the approved transaction information by the terminal device. In the step of transmitting a notification for confirming the identification information to the information processing device, the information processing device transmits the user identification information of the transaction information based on the notification transmitted from the terminal device to the user of the terminal device. Includes a step to use as user identification information.

In the computer program, digital ticket system, user terminal device, and information processing method of the present disclosure, transaction information required for settlement of services or products related to the execution of the itinerary included in the itinerary is based on the received itinerary schedule. The search is requested to the information processing device. The information processing device includes the provider identification information of the provider of the service or the product, the user identification information of the user of the service or the product, the payer identification information of the payer who pays the consideration, and the consideration indicating the consideration. It is a device that executes processing on transaction information including at least information. The information processing device can determine at least one of the above-mentioned information to create transaction information, and stores the created transaction information in a searchable manner. Digital tickets based on the extracted transaction information will be available.

As a result, digital tickets are automatically arranged based on the itinerary schedule received by the computer.

The computer program of one embodiment of the present disclosure tells the computer for each of the one or more strokes at a predetermined time before the start of the stroke or at a predetermined time before the completion of the previous stroke. The transmission of the search request is executed.

In the computer program of the present disclosure, based on the itinerary schedule, in addition to the schedule acceptance timing, a digital ticket is automatically arranged before the start of the itinerary or the completion of the previous process.

The computer program of the embodiment of the present disclosure causes the computer to acquire the position data at the timing and execute the process of transmitting the search request on condition of the position indicated by the acquired position data.

The computer program of the present disclosure automatically arranges the necessary digital tickets based on the itinerary schedule and the current location data of the user who owns the computer.

The computer program of the embodiment of the present disclosure causes the computer to acquire the time of the timing and execute a process of transmitting the search request on the condition of the acquired time.

The computer program of the present disclosure automatically arranges the necessary digital tickets based on the itinerary schedule and the time data before the itinerary is carried out.

The computer program of the embodiment of the present disclosure, when the computer determines that the one or more processes have been completed, the contents of the one or more processes, the date and time when the process was executed, and the process. To execute the process of creating a report including the charges of the services or products used for each item that distinguishes between.

In the computer program of the present disclosure, the itinerary report is prepared including the provider, the content of the offer, the fee, etc. regarding the service or product for each itinerary included in the itinerary. The report is automatically created, which enhances the convenience of the user.

In the information processing method of the embodiment of the present disclosure, the information processing apparatus obtains transaction identification information for identifying each of the transaction information when the provision of the service or the product is completed based on the transaction information. It is stored in association with the process identification information that identifies the process that involves the use of services or products based on transaction information.

In the information processing method of the present disclosure, the digital ticket data required for one or more processes included in the itinerary is stored in association with the process identification information for identifying the process. This can be used when outputting the itinerary content after the fact.

In the information processing method of the embodiment of the present disclosure, when it is determined that the information processing apparatus has completed one or more steps included in the itinerary, the process identification information of the one or more steps is obtained. It is stored in association with the itinerary identification information that identifies the itinerary.

In the information processing method of the present disclosure, when the itinerary is completed, the itinerary identification information of each itinerary is stored in association with the itinerary identification information for identifying the itinerary. It can be used when the user or payer confirms the series of itineraries included in the itinerary after the fact.

In the computer program, digital ticket system, user terminal device, and information processing method in the present disclosure, a digital ticket that enables the use of a service or a product is automatically arranged for each process based on a schedule entered by the user. As a result, the convenience of cashless payment can be further improved.

It is a schematic diagram of the digital ticket system of this embodiment. It is a block diagram which shows the structure of the user terminal apparatus of a digital ticket system. It is a block diagram which shows the structure of the provider terminal apparatus of a digital ticket system. It is a block diagram which shows the structure of the payer terminal apparatus of a digital ticket system. It is a block diagram which shows the structure of an information processing 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 schematic diagram which shows an example of the process of completing a digital form. It is a flowchart which shows an example of the processing procedure in the user terminal apparatus of the digital ticket system of this embodiment. It is a flowchart which shows an example of the processing procedure in the user terminal apparatus of the digital ticket system of this embodiment. It is a flowchart which shows an example of the processing procedure in the information processing apparatus of the digital ticket system of this embodiment. It is a flowchart which shows an example of the processing procedure in the information processing apparatus of the digital ticket system of this embodiment. It is a figure which shows the content example of the itinerary reception screen. It is a figure which shows the input example to the itinerary reception screen. It is a figure which shows the content example of the initial plan. It is a figure which shows the display example of an initial plan. It is a figure which shows the content example of the digital ticket display screen. It is a figure which shows the content example of another digital ticket display screen. It is a figure which shows the content example of another digital ticket display screen. It is a figure which shows the display example of the digital ticket display screen after the charge is fixed. It is a figure which shows the content example of the plan which a part process was confirmed. It is a figure which shows the content example of the data which is associated with the itinerary ID and is stored. It is a figure which shows the content example of the itinerary plan screen after the itinerary is completed. It is a flowchart which shows an example of the report creation processing procedure. It is a figure which shows the content example of the output report.

The present disclosure will be specifically described with reference to the drawings showing the embodiments thereof. In the following embodiment, a digital ticket system to which the computer program of the present disclosure is applied will be described.

FIG. 1 is a schematic view of the digital ticket system 100 of the present embodiment. The digital ticket system 100 includes a user terminal device 1, a provider terminal device 2, a payer terminal device 3, and an information processing device 4. The digital ticket system 100 is operated on the digital ticket platform provided by the processing of the information processing device 4. The platform is a digital ticket that allows users to actually enjoy services or products cashlessly, and when the charges are fixed according to the actual usage, the charges can be paid from the payer to the provider without any trouble. I will provide a.

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 fee is paid 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 service uses the basis of payment. 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.

The provider and the payer each participate in the service in the digital ticket system 100, and the user installs a computer program called a ticket application on his / her own computer in order to use the platform on which the service can be provided. , Contract with the platform operator. 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 ticket application are the user terminal device 1, the provider terminal device 2 and the payer, respectively. It becomes the terminal device 3.

The user terminal device 1, the provider terminal device 2, and the payer terminal device 3 can communicate with the information processing device 4 via the network N. 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 processing device 4 via a public communication network N1 or a carrier network N2. The payer terminal device 3 may be able to communicate with the information processing device 4 via a dedicated line.

In the digital ticket system 100 of the present embodiment, the user terminal device 1 requests the issuance of the digital form DF based on the ticket application, or the digital ticket based on the digital form DF issued by the provider terminal device 2 Can be obtained. In the digital ticket system 100 of the present embodiment, in particular, the user terminal device 1 owned by the user can function as a ticket attendant and can be used on the platform provided by the information processing device 4, and is required by the user. Search for digital tickets and present them to users. The user terminal device 1 makes it possible to provide a service using a digital ticket selected by the user from the digital tickets presented to the user, and automatically executes payment by the payer. The user receives and obtains the digital ticket required at each time point from the ticket attendant function by giving the position data indicating the current location and the position data indicating the destination to the user terminal device 1 as needed. Can be done.

Hereinafter, the configuration and specific processing for realizing the function of the ticket attendant in the digital ticket system 100 will be described.

FIG. 2 is a block diagram showing the configuration of the user terminal device 1 of the digital ticket system 100. The user terminal device 1 uses a computer having a wireless 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 processing device 4 based on the ticket application 1P for the terminal 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 ticket application 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 ticket application 1P, and transmits / receives information to / from the information processing device 4 as an application for the user.

The communication unit 12 is a wireless communication module that realizes wireless communication with the information processing 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 digital ticket 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 instead of the staff who actually provides the service may use 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 using 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 processing device 4 based on the ticket application 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 ticket application 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 ticket application 2P, and exchanges information with the information processing device 4.

The communication unit 22 is a wireless communication module that realizes wireless communication with the information processing 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 (registration 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 from 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. The provider terminal device 2 may include a position information acquisition unit.

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

FIG. 4 is a block diagram showing the configuration of the payer terminal device 3 of the digital ticket 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 using 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 processing device 4 based on the ticket application 3P for payers 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 ticket application 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 user's attributes. 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 ticket application 3P for the payer, and causes the information processing device 4 to display the graphical interface for the payer. Exchange information with.

The communication unit 32 is a network card that realizes a communication connection with the information processing device 4. The payer terminal device 3 may be connected to the information processing device 4 via the public communication network N3, or may be connected to the information processing 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 ticket applications 1P, 2P, and 3P are computer 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 as the approver of the superior, that is, the payer authority by switching the account. Similarly, the user terminal device 1 can be switched to the provider terminal device 2. Of course, the ticket applications 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 processing device 4. The information processing device 4 uses a server computer. In the present embodiment, the information processing apparatus 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 processing 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 on the public communication network N1 or the carrier network N2. The control unit 40 can send 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, and a form DB 405.

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 charges to the provider.

FIG. 8 is a diagram showing an example of the content 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 the application from the payer only for the 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, usage start date and time, usage end date and time, purpose of use, name of service or product used, detailed content, amount of money, user ID of user, provider providing 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.

The information processing device 4 that controls the digital ticket 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. The user ID indicates who is the user 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 processing device 4 is a drafting request from the user terminal device 1 that specifies the user ID, a drafting request from the provider terminal device 2 that specifies the provider ID, or a payer terminal that specifies the payer ID. A digital form DF can be created based on any of the issuing requests from the device 3, and a digital ticket based on the digital form DF can be issued so that it can be used. The information processing device 4 is the basis for payment when the provision of the service based on the issued digital ticket is completed, the fee is fixed, who the payer is, and all the information in the issued digital form DF is fixed. Complete the digital form DF that becomes. The information processing 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. be.

The processing when using the digital ticket will be described. The information processing device 4 receives a request 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), and receives a digital form DF. Make a vote.

FIG. 10 is a schematic diagram showing an example of the process of completing the digital form DF. FIG. 10 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. 10A, at the stage of drafting, items necessary for payment or expense processing are (1) information for identifying a transaction (transaction ID), and (2) information indicating the contents of the provided service or product. By determining (5) among (items), (3) charges, (4) service or product providers (payees), (5) service or product users, and (6) charge payers. (1) is in the state of being numbered. If the "payment method" is specified as "expense processing" in the request, the payer of (6) is tentatively determined by the company to which the user belongs. As described above, the platform in the present disclosure makes it possible to issue a digital form DF that is the source of payment and expense processing at a stage where only the user, payer, or provider is determined.

The same applies to the case where the user is determined first, the case where only the provider is determined first, and the case where only the payer is determined first, as shown in FIG.

Based on the drafted digital form DF, digital tickets for which the user, provider, or payer has not been determined are provided searchably by the information processing device 4, the user, the provider, or the payer, and the digital ticket market is opened. It is formed. By the function of the ticket attendant, the information processing device 4 executes matching of undecided users, providers, and payers with the digital form DF on the digital ticket market. When the user and the provider are confirmed and the service (product) is provided and the payer is confirmed, the digital form DF is completed. Settlement is made based on the completed digital form DF.

11 and 12 are flowcharts showing an example of a processing procedure in the user terminal device 1 of the digital ticket system 100 of the present embodiment. In the present embodiment, the digital ticket is requested or searched on the digital market by the function of the ticket attendant of the user terminal device 1. In the following description, the operation of the user terminal device 1 may be executed not by the user who receives the service but also by an operator who is permitted to use the user ID, such as a family member or a secretary.

When the user uses the ticket attendant function, the control unit 10 of the user terminal device 1 accepts the itinerary schedule and the registration of the purpose (step S101). The schedule includes one or more places and the length of stay (start time, end time) at those places. The purpose is divided into business and non-business (private). In the case of business, the payer is the payer indicated by the payer ID stored in the user DB 402 as the default payer.

In step S101, the control unit 10 may accept both the conditions in the schedule (priority conditions, designation of transportation, upper / lower limit of price, etc.). The condition to be prioritized is, for example, whether the criterion to be selected in the search or matching by the information processing apparatus 4 is cost-oriented, travel distance-oriented, or popularity-oriented. As a result, extraction candidates are narrowed down. Details of the registration of the itinerary schedule in step S101 will be described later.

Based on the registered schedule, the control unit 10 creates an initial plan including a process for transportation, accommodation, and eating and drinking necessary for executing the schedule (step S102).

In step S102, the control unit 10 is a process for arriving at a predetermined location in the schedule based on an external service that provides map information, an external service that provides transportation timetable information, and the like. , And search for some possible transportation options required for the journey. The control unit 10 also searches for some restaurant candidates other than the predetermined time in the schedule for meals, and extracts some candidates for the route to the searched restaurant. The control unit 10 searches for some candidates for accommodation based on the information of the distance from the predetermined location and the staying time of the predetermined location. The information processing device 4 may execute the search and creation of candidates related to the initial plan.

The control unit 10 sends a search request for a ticket candidate in the digital ticket market to the information processing device 4 regarding the means of transportation related to the first process, eating and drinking at the first destination, or accommodation in the initial plan created in step S102. Transmit (step S103).

As will be described later, the information processing device 4 extracts digital ticket candidates in response to a search request and responds with the extraction result.

The user terminal device 1 receives the digital ticket candidate of the first process from the communication unit 12 (step S104), the control unit 10 displays the digital ticket candidate on the display unit 13 (step S105), and the user. Approved by (step S106). The control unit 10 notifies the information processing device 4 of the approved digital ticket data (data for identifying the digital ticket, transaction ID) (step S107). As a result, the user of the digital form DF, which is the source of the digital ticket, is determined. If the approval is not received in step S106, the control unit 10 may re-execute the search request in step S103 or request another matching candidate digital ticket.

The control unit 10 predicts the process completion date and time and the location of the approved digital ticket of the first process (step S108).

The control unit 10 determines the presence or absence of the next process (step S109), monitors the progress of the current process before completion (step S110), and determines whether or not the process is completed (step S111).

In step S111, when the process involves the provision of a service or product, the control unit receives that the charge for the service or product has been determined from the provider terminal device 2 via the information processing device 4. 10 determines that the process has been completed. In step S111, when the process is not accompanied by the provision of services or goods, the control unit 10 displays on the display unit 13 whether or not the process is completed at the timing of predicting the process completion date and time, and the operation unit 14 completes the process. You may accept whether or not you did. In this case, the control unit 10 may determine that the process is completed at the timing when the predicted process completion date and time has elapsed.

When it is determined in step S111 that the process is not completed and it is determined in step S109 that there is a next process (S111: NO, S109: YES), the control unit 10 predicts in step S108. It is determined whether or not the process has reached a predetermined time before the process completion date and time (step S112).

Even if it is determined that the process has not been completed, if it is determined that there is no next process (S111: NO, S109: NO), the control unit 10 returns the process to step S110.

When it is determined in step S112 that the time has arrived before the predetermined time (S112: YES), the control unit 10 acquires the data of the current time and the current location (step S113), and the next step is subject to the data of the current time and the current location. A search request for a ticket candidate in the digital ticket market is transmitted to the information processing device 4 regarding the means of transportation, eating and drinking, or accommodation (step S114).

The control unit 10 receives the digital ticket candidate for the next process from the communication unit 12 (step S115), the control unit 10 displays the digital ticket candidate on the display unit 13 (step S116), and the user approves. Receive (step S117). The control unit 10 notifies the information processing apparatus 4 of the approved digital ticket data (data for identifying the digital ticket, transaction ID) (step S118), and returns the process to step S110. As a result, the user of the digital form DF, which is the source of the digital ticket used in the next process, is determined by the information processing device 4.

The control unit 10 sends a search request in step S114 to watch the digital ticket at any time, for example, periodically in the case where it is determined that there is a next process even if the predetermined time has not arrived, and the extraction result is obtained. It may be preferentially extracted as. In this case, it does not have to be approved.

If it is determined in step S112 that the predetermined time has not been reached (S112: NO), the process returns to step S110.

When it is determined that the process is completed (S111: YES), the control unit 10 receives the fixed charge from the provider terminal device 2 or the information processing device 4 (step S119), and the display unit 13 receives confirmation. It is displayed together with the screen (step S120). When the control unit 10 receives confirmation from the user regarding the displayed charge (step S121), the control unit 10 notifies the information processing apparatus 4 of the charge confirmation (step S122).

When the process determined to be completed does not involve the provision of services or goods and does not use the digital ticket, the control unit 10 omits the process of steps S119-S122. In step S111, the control unit 10 determines that the process has been completed when the predicted process completion date and time has elapsed, and then substitutes for steps S119-S122 to display on the display unit 13 whether or not the process has been completed. Then, the operation unit 14 may accept whether or not it is actually completed.

After step S122, if it is determined that there is no next step (S109: NO), the control unit 10 advances the process to step S124.

In the case where it is determined that there is a next process after step S122 (S109: YES), the control unit 10 predicts the process completion date and time and the location based on the digital ticket of the approved next process (step). S123). The control unit 10 returns the process to step S110 and repeats the process until the final process is completed. If it is not approved, the control unit 10 receives approval from the search result of the digital ticket candidate.

In step S124, the control unit 10 stores the transaction ID of the digital ticket (digital form DF) of the entire process and the event contents in association with the itinerary ID and the user ID indicating that the itinerary is a series (step S124). ), End the process. The control unit 10 may transmit the itinerary ID, the user ID, the transaction ID of all the itineraries included in the itinerary, and the correspondence of the event contents to the information processing device 4 or the payer terminal device 3 of the payer. ..

The processing procedure on the information processing apparatus 4 side will be described. 13 and 14 are flowcharts showing an example of the processing procedure in the information processing apparatus 4 of the digital ticket system 100 of the present embodiment.

In the information processing device 4, the control unit 40 receives a search request (step S401), and in response to the received search request, a user who matches the search conditions from the user terminal device 1 searches for an undecided digital form DF. (Step S402).

The control unit 40 determines whether or not the digital form DF that matches the search condition can be extracted (step S403). When it is determined that the data can be extracted (S403: YES), the control unit 40 provisionally determines the user ID of the user terminal device 1 of the search request source as the user of the first candidate digital form DF (step S404). ), Data such as the provider and conditions of the extracted digital form DF are transmitted to the user terminal device 1 as digital ticket data (step S405).

If it is determined in step S403 that extraction is not possible (S403: NO), the control unit 40 issues a digital form DF determined only by the user based on the request (step S406). The control unit 40 extracts the provider ID of the provider having the condition matching the request based on the recorded digital form DF (step S407), and directs the extracted provider ID to the provider terminal device 2. Notify the recruitment (step S408). The control unit 40 accepts the application in response to the notification of recruitment (step S409), and tentatively determines the provider ID of the provider that best matches the search conditions as the provider of the digital form DF created in step S406 (step S406). Step S410). The control unit 40 transmits the digital form DF data including the provisionally determined provider information to the user terminal device 1 as digital ticket data (step S411).

When the control unit 40 receives the approval for the transmitted digital ticket from the user terminal device 1 of the user (step S412), the control unit 40 confirms the provisional determination of the user ID and the provider ID (step S413). When it is clearly stated in step S413 that the control unit 40 is not approved (when the request is sent again), or when a predetermined time has elapsed from the tentative decision, the control unit 40 releases the tentative decision and extracts it in step S403. The user ID in the digital form DF created is deleted, or the provider ID of the digital form DF created in step S406 is deleted.

The control unit 40 determines the payer ID of the payer associated with the user ID according to the selected purpose (step S414). The control unit 40 may acquire the purpose of use of the digital ticket at the time of the search request in step S401 or the approval in step S412.

The control unit 40 monitors the progress of the service (product) (step S415). In step S415, the control unit 40 determines whether or not the charge confirmation notification has been received from the service provider's provider terminal device 2 and the user's user terminal device 1 (step S416).

If it is determined in step S416 that the charge confirmation notification has not been received (S416: NO), the control unit 40 returns the process to step S415.

When it is determined in step S416 that the charge confirmation notification has been received (S416: YES), the control unit 40 adds the charge to the digital form DF in association with the transaction ID (step S417), and ends the process. As a result, the digital form DF corresponding to the request is completed.

When the digital form DF is completed in step S417, if the payer ID is an expense usage different from the user ID, the information processing device 4 processes the expense when the payment process is completed by an external payment service based on the digital form DF. Data is created and transmitted to the payer terminal device 3.

As for the processing procedure regarding the recruitment of users or providers in the information processing apparatus 4 shown in the flowcharts of FIGS. 13 and 14, the contents described in Japanese Patent Application No. 2019-100590 are incorporated.

The procedure shown in the flowchart of FIGS. 11 to 14 will be described with reference to specific examples. FIG. 15 is a diagram showing an example of the contents of the itinerary reception screen 131. The screen example of FIG. 15 shows a screen example of accepting the registration of the itinerary schedule and its purpose in step S101 shown in the flowchart of FIG.

The itinerary reception screen 131 includes an input field 132 that accepts a schedule title, items for each itinerary, content, date and time, time, and classification selection. The input field 132 includes a selection unit 133 for selecting a category of whether it is an expense processing target or a self-pay target.

FIG. 16 is a diagram showing an example of input to the itinerary reception screen 131. On the itinerary reception screen 131 of FIG. 16, "movement (outward route)", "business", "accommodation", etc. are selected as the items of each itinerary in the input field 132. In the input field 132, "date and time" and "classification" are selected for the process of each item. The item of the input field 132 is a selection menu control. When "Move" is selected in the selection menu, it is preferable that "departure place" and "arrival place" can be input to the input control of "content" respectively. In the "date and time" of the input field 132, the date of the process and the fixed time can be input. In the example of FIG. 16, in the first stroke, only the arrival time is input. In this case, the control unit 10 of the user terminal device 1 searches for the means of transportation arriving from the "departure place" to the "arrival place" by the arrival time as a ticket attendant. In the first step in the example of FIG. 16, "expense" is selected by the selection unit 133 for business use.

Specifically, in the example of FIG. 16, the first fixed schedule is a schedule in which the "item" is the "movement" of the outbound route and the "content" is the movement from Shinagawa to Umeda (Osaka). , It is registered with the "date and time" scheduled to arrive by 12:00 on December 5, 2019. In addition, the first schedule is selected to be business content and expense utilization. Next, as the second fixed schedule, the schedule in which the "item" is "business" and the "content" is the meeting in the XYZ building is from 13:00 to 16:30 on December 5, 2019. It is registered by the "date and time" of the schedule. Similarly, as the third finalized schedule, the schedule in which the "item" is "business" and the "content" is a social gathering around Umeda is from 18:30-21 on December 5, 2019. It is registered with the scheduled "date and time" of 00.

FIG. 17 is a diagram showing an example of the contents of the initial plan. FIG. 17 is a plan that is received on the itinerary reception screen 131 of FIG. 16 and is created by the control unit 10 of the user terminal device 1 based on the ticket application 1P based on the registered schedule. As shown in FIG. 17, the control unit 10 creates a plan as a list of "items" such as "movement", "meal", "business", and "accommodation", "date and time", and "contents". As shown in FIG. 17, the control unit 10 may create an initial plan by incorporating a schedule such as "meal" between the registered schedules "movement" and "business". The initial plan shown in FIG. 17 is created so as to include the first step to the thirteenth step. The initial plan shown in FIG. 17 is "planned" because none of the steps have been implemented. An itinerary ID is given to the plan to indicate that it is included in a series of itineraries. The itinerary ID may be assigned by the user terminal device 1 based on the user ID and the date of the user terminal device 1, or may be assigned by the information processing device 4. The content of each itinerary included in the plan is stored in the user terminal device 1 in association with the itinerary ID.

FIG. 18 is a diagram showing a display example of the initial plan. The control unit 10 of the user terminal device 1 displays the itinerary plan screen 134 based on the initial plan including the contents of the itinerary associated with the itinerary ID of the series of itineraries shown in FIG. The itinerary plan screen 134 displays the itinerary shown in FIG. 17 in chronological order together with an interface 136 that accepts changes or deletions for each itinerary and an interface 135 that requests a digital ticket for each itinerary. The request interface 135 is selected when it is desired to determine a digital ticket individually for each process, for example, when it is desired to determine a round-trip ticket, a cheap ticket, or the like. When the interface 135 of the search request is selected, the control unit 10 may display the search condition input screen and allow the user to specify the charge range, the provider, and the like.

The itinerary plan screen 134 includes an "automatic progress" interface 137 for automatically arranging all the itineraries according to the progress by the ticket attendant function. When the "automatic progress" interface 137 is selected, the plan displayed on the itinerary plan screen 134 is determined, and the control unit 10 of the user terminal device 1 determines, as shown in the flowcharts of FIGS. 11 and 12. A search request for a digital ticket for the next process is transmitted to the information processing device 4 before a predetermined time of the completion date and time of the process in progress.

When the interface 137 is not selected, the control unit 10 receives a ticket request for each process from the user, sends the request to the information processing device 4, receives matching, and accepts the user's selection from the extracted ticket candidates. It is good.

FIG. 19 is a diagram showing an example of the contents of the digital ticket display screen 138. FIG. 19 shows a digital ticket arranged for the first journey. The digital ticket display screen 138 of FIG. 19 shows ticket candidates extracted in the market based on the digital form DF with the transaction ID (S115). The digital ticket display screen 138 includes a ticket display screen 142 showing the extracted digital ticket of the railway (JJ passenger railway in FIG. 19). The ticket display screen 142 shows the contents of the digital ticket (service provider: JJ passenger railroad, service content: reserved seat information, standard fare: 14300 yen).

The digital ticket display screen 138 includes an interface 139 for "approval" and a "change" interface 140 for each ticket. The digital ticket display screen 138 may include an interface 141 for canceling the arrangement rather than changing the ticket. When the "approval" interface 139 is selected, the control unit 10 executes approval of step S106 and notification of step S107 in the flowcharts of FIGS. 11 and 12. When the "change" interface 140 is selected, the control unit 10 re-executes the process from step S103 because it has been canceled, for example. The control unit 10 may acquire from the information processing device 4 the candidates extracted in response to the request, which are preferentially extracted next to the changed digital ticket.

The digital ticket display screen 138 may include an interface 143 that accepts a transition to a screen indicating a ticket for another process. When the interface 143 is selected, the control unit 10 displays the digital ticket display screen 138 displaying the contents of the digital ticket for the selected process on the display unit 13.

FIG. 20 is a diagram showing an example of the contents of another digital ticket display screen 138. FIG. 20 is an example displayed when the interface 143 that accepts the transition to the screen showing the ticket for another process in FIG. 19 is selected. In the example of FIG. 20, the ticket information regarding the second process in the initial plan shown in FIG. 17 is shown as not yet arranged (search request).

When the "automatic progress" interface 137 is selected on the itinerary plan screen 134 of FIG. 18, the control unit 10 of the user terminal device 1 determines the progress of the process as shown in the flowcharts of FIGS. 11 and 12. A search request for a digital ticket for the next process is transmitted to the information processing device 4 before a predetermined time of the completion date and time. FIG. 21 is a diagram showing an example of the contents of another digital ticket display screen 138. FIG. 21 shows FIG. 20 a digital ticket arranged by sending a search request for the second process to the information processing device 4 one hour before the completion of the first process. The digital ticket display screen 138 of FIG. 21 includes a ticket display screen 142 showing a digital ticket for lunch around Umeda extracted by matching. The ticket display screen 142 shows the contents of the digital ticket (service provider: Umeda S-tei, service contents: time and seats, standard charge: 1000 yen).

The method of using the digital ticket shown in FIGS. 19 and 21 will be described. When the "approval" interface 139 is selected on the digital ticket display screen 138 of FIG. 19, the digital ticket related to the use of the railway shown on the ticket display screen 142 becomes available. At the start of use, the railway company, which is the service provider, needs to acquire the user ID. Therefore, for example, an image of the two-dimensional code of the user ID is displayed on the display unit 13 and the entrance of the railway company. It is advisable to read this at the gate and acquire it at the provider terminal device 2 of the railway company. As a result, the progress start of the service can be monitored by the information processing device 4 thereafter. In addition, a paper ticket that can be used by the railway company is handed to the user by reading the image of the two-dimensional code of the user ID at the reading unit 25 of the provider terminal device 2 installed at the ticket office of the railway company. As a result, it may be possible to use it. In addition, the ID number of the transportation IC card that enables the use of the railway company and the user ID are linked in the user DB 402, and the user ID is given in advance to the ID number of the transportation IC card. A digital ticket based on the confirmed digital form DF may be associated with the digital ticket.

When the user exits the exit gate of the railway, the gate reads the user ID again, and when the service ordered by the service provider (railway use) is completed, the fare is fixed and the fare is fixed from the provider terminal device 2. The charge information is received by the user terminal device 1 via the information processing device 4 (S119). When the confirmation of the charge is received by the user terminal device 1 (S121), a notification is transmitted to the information processing device 4 (S122), whereby the use of one digital ticket is completed. When a transportation IC card is used, the charge is fixed at the timing when the section used at the exit gate is fixed. Therefore, the user terminal device 1 provides that the associated digital ticket has been used. It is possible to complete the digital form DF by recognizing it by the personal terminal device 2 and the information processing device 4 (S417). In the case of self-pay, the charge fixed by the digital form DF may be deducted from the balance of the transportation IC card, or it may be settled from the self-pay credit card linked to the user ID. You may.

When the "approval" interface 139 is selected on the digital ticket display screen 138 of FIG. 21, the digital ticket for eating and drinking shown on the ticket display screen 142 becomes available. At the time of use, the restaurant that is the service provider needs to acquire the user ID. For example, an image of the two-dimensional code of the user ID is displayed on the display unit 13, read by the reading unit 25 of the cashier terminal of the restaurant or the provider terminal device 2 installed at the store, and read again at the time of payment. It may be read by the part 25.

FIG. 22 is a diagram showing a display example of the digital ticket display screen 138 after the charge is fixed. When an order is placed at a restaurant, the service content, that is, the order content can be obtained from the user terminal device 1 via the information processing device 4. When the service ordered by the service provider (providing food and drink) is completed, the charge is fixed, and the charge information is received from the provider terminal device 2 by the user terminal device 1 via the information processing device 4 (S119). ). Then, as shown in FIG. 22, the charge is displayed (S120), and the "confirmation" interface 143 is displayed. When the "confirmation" interface 143 is selected, the control unit 10 accepts the confirmation of the charge (S121) and transmits the confirmation notification to the information processing device 4 (S122). This completes the use of one digital ticket.

FIG. 23 is a diagram showing an example of the contents of a plan in which a partial process is confirmed. The control unit 10 approves the digital tickets in order on the screens shown in FIGS. 18 to 22, and sends a confirmation notification to the information processing device 4 each time the charge is fixed. As a result, the information processing device 4 completes the digital form DF for each process. FIG. 23 shows the contents of the finalized plan based on the digital form DF of each process included in the same itinerary. Some changes have been made compared to the initial plan shown in FIG. Expense processing is selected except that self-pay is selected for meals in the second and thirteenth processes, and expense processing is executed based on the digital form DF completed by the information processing device 4. NS.

FIG. 24 is a diagram showing an example of the contents of data associated with and stored in the itinerary ID. Itinerary data stored by the control unit 10 of the user terminal device 1 in step S124 shown in the flowcharts of FIGS. 11 and 12. The itinerary data may be sharablely stored in the information processing device 4 from the provider terminal device 2 and the payer terminal device 3. The itinerary data includes the itinerary content in association with the itinerary ID. The itinerary data includes the itinerary ID of the itinerary included in the itinerary, the items for each itinerary, and the transaction ID of the digital form DF that is the source of the digital ticket used in the itinerary. When the itinerary data is stored in the information processing device 4, it is preferable that the itinerary data is associated with the user ID as shown in FIG.

FIG. 24 shows an example of itinerary data for the finalized plan shown in FIG. The itinerary ID with the title "Osaka Business Trip" is given an ID based on the date and time. In association with the itinerary ID, the items and contents of each itinerary with the itinerary ID plus, for example, a four-digit number, and the transaction ID of the digital form DF of the digital ticket used are stored. The transaction ID is blank because the digital ticket is not used in the business, which is the third process of the "Osaka business trip" itinerary. Based on the transaction ID, the provider ID, the service usage start date and time, the usage completion date and time, and the service content can be acquired from the form DB 405 of the information processing device 4. The itinerary data may include the data itself such as the contents of these services.

FIG. 25 is a diagram showing an example of the contents of the itinerary plan screen 134 after the itinerary is completed. The itinerary plan screen 134 includes the contents of the itinerary associated with the itinerary ID of the series of itineraries shown in FIGS. 23 and 24 by the control unit 10 of the user terminal device 1. The itinerary plan screen 134 of FIG. 25 shows that all the itineraries associated with the same itinerary ID have been completed. Before the completion of all itineraries, it may be displayed together with interface 136, which accepts changes or deletions for each itinerary, and interface 135, which requests a digital ticket for each itinerary, as shown in FIG. The completed process may include an interface that accepts editing of the content for each process. When accepting editing, it is preferable that the event content in the itinerary data of FIG. 24 can be edited. When permitted by the information processing device 4, the provider terminal device 2, and the payer terminal device 3, the digital form DF of the corresponding transaction ID may be editable.

On the itinerary plan screen 134 of FIG. 25, since the itinerary is completed, the interface 144 for executing the "report creation" is displayed. The control unit 10 of the user terminal device 1 displays this interface 144 when displaying the itinerary plan screen 134 in a state where the itinerary is completely completed by the function of the ticket attendant. On the itinerary plan screen 134, an interface 145 for selecting whether the report is a business report for expense use or a travel report for private use is displayed together with the interface 144 for "report creation". There is. The selection interface 145 is not limited to this, and may be made selectable after the interface 144 is selected.

The procedure for creating a report based on the itinerary data shown in FIG. 23-25 will be described. FIG. 26 is a flowchart showing an example of the report creation processing procedure. The control unit 10 of the user terminal device 1 starts the following processing when the interface 144 is selected.

The control unit 10 acquires the itinerary ID of the itinerary displayed on the itinerary plan screen 134 when the interface 144 is selected (step S301).

The control unit 10 reads the itinerary data associated with the itinerary ID from the storage unit 11 or the information processing device 4 (step S302).

The control unit 10 reads out the digital form DF for each process stored in the form DB 405 from the information processing device 4 based on the transaction ID of the process included in the itinerary data (step S303). In step S303, the control unit 10 may read out the data necessary for creating the report, such as the provider ID, the charge, and the expense classification specified from the provider ID of the service (product).

The control unit 10 classifies the read itinerary data for each itinerary by item (step S304), and calculates the subtotal and the total for each item from the charge of the digital form DF for the itinerary for which the expense utilization is selected. (Step S305).

The control unit 10 determines the type of report selected by the selection interface 145 (step S306).

The control unit 10 reports the title of the itinerary, the itinerary contents of the business items included in the itinerary, the date and time, the subtotal calculated in step S305, and the total in a template stored in association with the type selected in step S306. Is output as (step S307). The control unit 10 displays the image of the report on the display unit 13 (step S308), and ends the process.

The processing procedure shown in the flowchart of FIG. 26 may be automatically executed when the itinerary is completed by the ticket attendant function even if the interface 144 is not selected. The output report (document data) may be stored in the storage unit 11 or may be transmitted to the payer terminal device 3 via the information processing device 4.

FIG. 27 is a diagram showing an example of the contents of the output report. FIG. 27 shows a report display screen 146. The report of FIG. 27 is an example output when it is selected to be an expense utilization, that is, a business report. In the report, the title, purpose, date and time, breakdown and subtotal of expenses for expense utilization, and total by item are automatically posted from the itinerary data and digital form DF.

When private use is selected at the time of output of the report, the control unit 10 creates a report with the title "Travel Report" in the travel record template.

In this way, since it is stored as itinerary data, it is easy to output a report depending on whether it is for private use or for expense use, depending on the selection of the template. The user can automatically create a report to the payer when using the expenses. Since the expense data is created by the information processing device 4 and transmitted to the payer terminal device 3, both the user and the payer can reduce the administrative procedures related to the expense utilization.

In this way, by using the platform that provides the digital ticket market based on the digital form DF, the user can make cashless payment for each service for both the expense use itinerary and the private use itinerary. You don't have to receive it, you can use the digital tickets provided by the platform with one ticket app. Moreover, the user can use the ticket attendant function that automatically arranges a digital ticket according to the progress of the process.

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 12 Communication unit 13 Display unit 14 Operation unit 16 Location information acquisition unit 1P Ticket application (computer program)
4 Information processing device 40 Control unit 42 Communication unit 401 Service DB
402 User DB
405 Form DB

Claims (10)

For computers equipped with a display unit and an operation unit
The itinerary schedule is accepted by the operation unit
For one or more itineraries included in the itinerary based on the accepted schedule, the provider identification information of the provider of the service or product, payment of the payer who pays the consideration, which is necessary for the settlement of the consideration for the service or product. A search request for transaction information including person identification information and consideration information indicating the consideration is transmitted to an information processing device that executes processing on the transaction information.
For each process, candidates for the transaction information extracted in response to the search request are displayed on the display unit in association with the provider identification information of the provider of the service or product included in the transaction information.
The operation unit accepts the approval of the displayed transaction information candidate,
A computer program that executes a process of transmitting a notification for confirming user identification information of a user of a service or product to the information processing device with respect to the approved transaction information. On the computer
The first aspect of claim 1, wherein the search request for the process is transmitted at a predetermined time before the start of the process or a predetermined time before the completion of the previous process for each of the one or a plurality of processes. Computer program. On the computer
Acquire the position data at the above timing and
The computer program according to claim 2, wherein the process of transmitting the search request is executed on the condition of the position indicated by the acquired position data. On the computer
Get the time of the above timing and
The computer program according to claim 2 or 3, wherein the process of transmitting the search request is executed on the condition of the acquired time. On the computer
When it is determined that the one or more processes have been completed, the content of the one or more processes, the date and time when the process was executed, and the charge of the service or product used for each item that distinguishes the process are calculated. The computer program according to any one of claims 1 to 4, which executes a process of creating a report including the above. In a digital ticket system that creates transaction information necessary for payment of the service or product and provides a digital ticket to the user of the service or product based on the transaction information.
The user terminal device used by the user of the service or product is
Means for accepting the user's itinerary schedule and
A means for transmitting a transaction information search request required for settlement of consideration for a service or product to an information processing device that executes processing on the transaction information for one or more itineraries included in the itinerary based on the received schedule. When,
A means for displaying a candidate for the transaction information extracted in response to the search request in association with the provider identification information of the provider of the service or product included in the transaction information.
A means of accepting the approval of the displayed transaction information candidate,
For the approved transaction information, a means for transmitting a notification for confirming the user identification information of the user of the service or product to the information processing device is provided.
The information processing device
Based on the search request, the provider identification information of the provider of the service or the product, the payer identification information of the payer who pays the consideration, the user identification information of the user of the service or the product, and the consideration are shown. A means for extracting at least transaction information in which the user identification information is undetermined from transaction information including consideration information, and
A means for transmitting the extracted transaction information to the user terminal device as a candidate together with the information of the provider of the service or product indicated by the provider identification information included in the transaction information.
A digital ticket system including means for using the user identification information of the transaction information as the user identification information of the user of the user terminal device based on the notification transmitted from the user terminal device. A user terminal device used by a user of a service or product.
Means of accepting itinerary schedules
For one or more itineraries included in the itinerary based on the accepted schedule, the provider identification information of the provider of the service or product required for settlement of the consideration for the service or product, and the payer of the payer who pays the consideration. A means for transmitting a search request for transaction information including identification information and consideration information indicating the consideration to an information processing device that executes processing on the transaction information.
A means for displaying a candidate for the transaction information extracted in response to the search request for each process in association with the provider identification information of the provider of the service or product included in the transaction information.
A means of accepting the approval of the displayed transaction information candidate,
A user terminal device including a means for transmitting a notification for confirming user identification information of a user of a service or product to the information processing device with respect to the approved transaction information. In an information processing method that creates transaction information necessary for payment of the service or product and provides a digital ticket to the user of the service or product based on the transaction information.
A step in which a terminal device used by a user of the service or product accepts the itinerary schedule of the user.
Information processing in which the terminal device executes processing for the transaction information for a search request for transaction information required for settlement of consideration for a service or a product for one or a plurality of itineraries included in the itinerary based on a received schedule. Steps to send to the device,
Based on the search request, the information processing device provides provider identification information of the provider of the service or product, payer identification information of the payer who pays the consideration, user identification information of the user of the service or product, And, from the transaction information including the consideration information indicating the consideration, at least the step of extracting the transaction information in which the user identification information is undetermined.
A step in which the information processing device transmits the extracted transaction information to the terminal device as a candidate together with the information of the provider of the service or product indicated by the provider identification information included in the transaction information.
A step in which the terminal device displays a candidate for the transaction information extracted in response to the search request in association with the provider identification information of the provider of the service or product included in the transaction information.
A step in which the terminal device accepts approval of a candidate for the displayed transaction information.
A step in which the terminal device transmits a notification for confirming the user identification information of a user of a service or a product to the information processing device with respect to the approved transaction information.
An information processing method including a step in which the information processing device uses the user identification information of the transaction information as the user identification information of the user of the terminal device based on the notification transmitted from the terminal device. When the provision of the service or product based on the transaction information is completed, the information processing device provides transaction identification information for identifying each of the transaction information in a process involving the use of the service or product based on the transaction information. The information processing method according to claim 8, wherein the information processing method is stored in association with the process identification information for identifying the information processing. The information processing device
The ninth aspect of claim 9 is that when it is determined that one or more itineraries included in the itinerary are completed, the itinerary identification information of the one or more itineraries is stored in association with the itinerary identification information for identifying the itinerary. Information processing method.

Images