KR20170138384A - Electronic ticket management apparatus and electronic ticket management method - Google Patents

Abstract

An electronic ticket management apparatus according to the present disclosure includes: an issuance ticket management table for accumulating electronic ticket information including an upper limit amount of usage, a usage right holder, and a payer; a transfer management unit for acquiring a transfer request from the payer and changing a usage right of the electronic ticket information stored in the issuance ticket management table to a person designated in the transfer request; a transaction management unit for permitting a transaction using the electronic ticket only when the electronic ticket is used within the upper limit amount of the usage of the usage right holder; and a payment processing unit for processing the payment so that a difference between the upper limit amount of the usage of the electronic ticket used for the transaction and an actual usage amount of the transaction is reduced to the payer of the electronic ticket. Accordingly, the present invention can promote the usage of the electronic ticket.

Description

[0001] The present invention relates to an electronic ticket management apparatus and an electronic ticket management method,

The present disclosure relates to an electronic ticket management apparatus and an electronic ticket management method.

Recently, electronic payment service utilizing information communication technology has been spreading. For example, in the system described in Patent Document 1, a taxi ticket is converted into an electronic ticket, and settlement is performed by the electronic ticket. By using the electronic ticket, the settlement process can be simplified.

Patent Document 1: JP-A-2005-135330

Although there are the advantages described above in the settlement processing using an electronic ticket, it is difficult to say at the present time that the use of the electronic ticket is widely and generally penetrated.

Accordingly, the present disclosure aims at providing an electronic ticket management apparatus and an electronic ticket management method which are useful for promoting the utilization of an electronic ticket.

The inventors of the present invention paid attention to the fact that if an electronic ticket can appropriately be transferred from one user (first user) to another user (second user) in consideration of the desire to smoothly transfer electronic tickets between users, And to promote the use of Therefore, the inventors of the present invention have come up with an apparatus for transferring an electronic ticket with a usage upper limit amount to a second user, in accordance with a request from a first user, as an electronic ticket management apparatus. According to the electronic ticket management device, the first user can easily transfer the electronic ticket with the usage upper limit amount to the second user through the electronic ticket management device.

Here, in the step of transferring the electronic ticket, it is often difficult to specify the amount actually used by the second user. Therefore, it is necessary for the first user to set the upper limit of the usage with a high margin. Thereby, there is a fear that the first user who is the payer hesitates to relinquish the electronic ticket, and the promotion of the use of the electronic ticket may not be sufficiently performed.

In this regard, the inventors of the present invention have conducted intensive studies and have come to the conclusion that the aforementioned problems can be solved by the electronic ticket management apparatus having the following configuration.

That is, an electronic ticket management device according to an embodiment of the present disclosure includes: a storage unit for storing electronic ticket information including an upper limit amount of usage of an electronic ticket, a usage right holder, and a payer; A transfer manager for acquiring a transfer request from a payer and changing a usage right of the electronic ticket information stored in the storage unit to a character designated in the transfer request; A transaction management unit that permits transactions using the electronic tickets only when the licensee uses the electronic tickets within the upper limit of usage; And when the transaction management unit permits the transaction using the electronic ticket, the difference between the upper limit of the usage amount of the electronic ticket used in the transaction and the actual usage amount in the transaction is returned to the payer of the electronic ticket And a settlement processing unit for performing the settlement processing.

In this electronic ticket management device, the use right is changed in accordance with the transfer request from the payer. When the electronic ticket is used within the upper limit of the use of the user, the use of the electronic ticket is permitted, and the difference between the upper limit of the usage amount and the usage amount is returned to the payer. For this reason, the higher the amount of use of the right of use and the upper limit of the usage amount of the electronic ticket, the larger the amount is returned to the payer. Therefore, even when the usage upper limit is set high in the setting of the usage upper limit or when the purchase amount of the user is low, the disadvantage of the electronic ticket payer can not be obtained. As a result, the transfer of the electronic ticket can be promoted, and as a result, the utilization of the electronic ticket can be promoted.

Further, in the electronic ticket management device, the electronic ticket information further includes information for specifying the usage of the electronic ticket, and the transaction management section may be configured such that, when the electronic ticket is used within the usage upper limit, , The transaction using the electronic ticket may be permitted. As a result, the use of the electronic ticket is limited and the burden of managing the electronic ticket can be reduced.

The information processing apparatus may further comprise a usage management section for acquiring the usage destination designation from the payer and setting the information specifying the usage of the electronic ticket information stored in the storage section to the content designated by the usage purpose specification. This makes it possible to prevent the payer from using the electronic ticket for unintended use. Therefore, the convenience of the payer can be improved, and the use of electronic tickets can be further promoted.

In the electronic ticket management device, the electronic ticket information may further include an expiration date of the electronic ticket. In the case where the usage right is within the expiration date, More specifically, a transaction using the electronic ticket may be permitted. Thus, the use period of the electronic ticket is limited, thereby reducing the management burden on the electronic ticket. Further, for example, when the expiration date can be set by the payer, it is possible to prevent the electronic ticket from being used in an unintended period by the payer. That is, the payer can urge the electronic ticket to be used during the intended period. Therefore, the convenience of the payer can be improved, and the use of electronic tickets can be further promoted.

In the above electronic ticket management device, the settlement processing unit may perform a pre-settlement by an upper limit amount of use in a previous stage of the settlement process, and may perform a correction process in accordance with an actual use amount in the settlement process. By performing the pre-settlement as much as the upper limit of the usage amount, the purchasing power of the electronic ticket and the settlement completion amount can be interlocked, and further settlement can be performed according to the actual condition.

Further, in the electronic ticket management device, the settlement processing unit may perform post settlement as much as a usage amount in the settlement processing. This makes it possible to simplify settlement since payment can be made only once after the amount of use of the electronic ticket is fixed.

An electronic ticket management method according to an embodiment of the present invention is an electronic ticket management method performed by an electronic ticket management apparatus, comprising: accumulating electronic ticket information including an upper limit amount of use of an electronic ticket, a usage right holder, and a payer; Acquiring the transfer request from the payer and changing the use right of the electronic ticket information from the transfer request to the designated character; Granting a transaction using the electronic ticket only if the licensee uses the electronic ticket within the upper limit of use; And when the transaction using the electronic ticket is permitted at the permission stage, the difference between the upper limit of the electronic ticket used for the transaction and the actual usage amount in the transaction is returned to the payer of the electronic ticket To be performed.

According to the present disclosure, it is possible to provide an electronic ticket management apparatus and an electronic ticket management method which are useful for promoting utilization of an electronic ticket.

1 is a diagram schematically showing a schematic configuration of an electronic ticket management system according to the present embodiment.
2 is a block diagram showing a functional configuration of the electronic ticket management apparatus.
3A is a table showing a customer management table.
3B is a table showing an electronic ticket management table.
4A is a table showing an issued ticket management table.
4B is a table showing the purchase management table.
4C is a table showing the settlement settlement table.
5 is a flowchart showing an execution procedure of the electronic ticket management method.
6 is a diagram schematically showing an image of electronic ticket management using an app (app).
7 is a flowchart showing an execution procedure of the electronic ticket management method according to the modification.

Hereinafter, embodiments will be described in detail with reference to the drawings. In the description, the same elements or elements having the same function are denoted by the same reference numerals, and redundant description is omitted.

[Electronic Ticket Management System]

1, the electronic ticket management system 1 includes an electronic ticket management device 2, a communication network 3, portable terminals 4 and 5, a card company terminal 6, (7). The communication network 3 is the Internet and the electronic ticket management device 2, the portable terminals 4 and 5, the card company terminal 6 and the user company terminal 7 are connected to the communication network 3 .

The portable terminals 4 and 5 are, for example, mobile phones such as smart phones or feature phones, and communication terminals such as tablet-type terminals. The portable terminals 4 and 5 are downloaded with software (apps) for using electronic tickets. Communication is performed between the portable terminals 4 and 5 and the electronic ticket management apparatus 2 by using the application so that electronic tickets of the users of the portable terminals 4 and 5 can be used. In addition, the use of the electronic ticket may not necessarily be realized by the above-mentioned application. In the following, it is explained that the electronic ticket is used by using the above-mentioned application.

The portable terminals 4 and 5 execute applications by issuing requests for issuing electronic tickets, viewing electronic tickets issued, changing the use of electronic tickets, transfer and positive numbers of electronic tickets, and transactions using electronic tickets Purchase of service). In the present embodiment, the portable terminal 4 is a terminal used by a first user (a payer and a transfer person) who purchases an electronic ticket and transfers it to another person. The portable terminal 5 is a terminal used by a second user (a transferee) who receives an electronic ticket from a first user and uses the electronic ticket. Since both the first user and the second user are those who can purchase goods or the like using electronic tickets, they may be described as " consumers " together.

For convenience, the portable terminals 4 and 5 are denoted by different reference numerals, but there is no difference in the function for using the electronic tickets in the portable terminals 4 and 5. 1, all of the portable terminals 4 and 5 are shown one by one, but the number of the portable terminals 4 and 5 may be plural, and the number is not limited.

The card company terminal 6 is a terminal of a credit card company that issues a credit card and manages a transaction based on the credit card. The card company terminal 6 communicates with the electronic ticket management device 2 to perform card settlement regarding purchase of an electronic ticket for purchasing a product or service. The user company terminal 7 is a terminal of a customer (a user company) receiving a payment in a transaction using an electronic ticket. Since the customer is the person who sells the product, the customer may be described as "seller". For example, when a user riding in a taxi uses an electronic ticket, the user company terminal 7 is a terminal of a taxi company. The user company terminal 7 communicates with the electronic ticket management device 2 to perform the settlement processing in the transaction using the electronic ticket. The card company terminal 6 and the user company terminal 7 are provided for each company, and one card company terminal 6 and a plurality of company company terminals 7 may be installed in each company.

[Electronic Ticket Management Device]

The electronic ticket management device 2 is a server that issues electronic tickets and manages transactions using electronic tickets. The electronic ticket managing apparatus 2 has a processor 201, a memory 202, a storage 203, a network adapter 204, and a bus 205 connecting them. The processor 201 performs data input / output through the network adapter 204 by executing a program in cooperation with at least one of the memory 202 and the storage 203. [ Thus, various functions of the electronic ticket managing apparatus 2 are realized. The configuration of the electronic ticket managing apparatus 2 shown here is an example. The electronic ticket managing apparatus 2 may be configured in hardware as long as it can realize the functions described below.

2 is a diagram showing each function of the electronic ticket managing apparatus 2 as a virtual component (hereinafter referred to as a " function block "). This function block is merely a function of the electronic ticket management device 2 divided into a plurality of blocks for convenience, and does not mean that the hardware is divided into such blocks.

2, the electronic ticket managing apparatus 2 includes a communication section 21, a customer information updating section 22, a issuing section 23, a use management section 24, a ticket information output section 25 A transaction management unit 27, a payment processing unit 28, a customer management table TBL 211, an electronic ticket management table TBL 212, an issued ticket management table TBL 213 (storage unit), a purchase management table (TBL 214), and a fixed settlement table (TBL 215).

The communication unit 21 is connected to the portable terminals 4 and 5, the card company terminal 6 and the user company terminal 7 (hereinafter referred to as portable terminals 4 and 5, card company terminal 6, 7) may be described as " portable terminal 4, 5 " or the like ") to perform transmission and reception of information. That is, the communication unit 21 receives a predetermined request or the like from the portable terminal 4, 5 or the like, and outputs the request or the like to another functional block in the electronic ticket management device 2. [ The communication unit 21 receives an input of a predetermined request or the like from another function block in the electronic ticket management device 2 and transmits the request or the like to the portable terminals 4 and 5 or the like.

The customer information updating unit 22 receives the customer information update request from the portable terminal 4 or 5 or the user company terminal 7 via the communication unit 21 and updates the customer management table TBL211. 3A is a table showing the customer management table (TBL 211). As shown in Fig. 3A, the customer management table TBL211 stores customer information associated with each customer's user ID, name, type of user, notification destination, and card number.

The customer is a person who performs transactions using an electronic ticket by communicating with the electronic ticket management device 2. [ That is, the customer is a customer who purchases a product or service using an electronic ticket (i.e., a user who uses the portable terminals 4 and 5), and a seller who receives a fee for goods or services by an electronic ticket A company that uses the terminal 7). The user ID is an identifier that uniquely identifies the user. The name is the name of the user. The type of the user is the type of the user, for example, either "1" or "2". The user type "1" indicates that the user is a seller, and "2" indicates that the user is a consumer. The notification destination is a contact of the user of interest and is a contact used when performing communication with the electronic ticket management apparatus. As a notification destination, for example, a mail address and a telephone number are registered. The card number is the credit card number of the user. The card number is used in payment processing. In the customer management table TBL211, the name and the card number do not have to be necessarily set.

The customer information updating unit 22 performs addition, deletion, and editing of customer information as update processing of the customer management table (TBL 211). That is, when the customer information update unit 22 receives the customer information update request from the portable terminal 4, 5 or the like that does not store the customer information, the customer information updating unit 22 adds the customer information on the terminal to the customer management table TBL211. In this case, the customer information update request includes information indicating the name, the user classification, the notification destination, and the card number. The customer information update unit 22 creates customer information by associating each piece of information included in the customer information update request with a randomly determined user ID and adds the customer information to the customer management table TBL211.

The customer information update unit 22 deletes the customer information related to the portable terminals 4 and 5 when receiving the customer information update request including the request to delete the customer information from the portable terminals 4 and 5 or the like. The customer information update unit 22 edits the customer information related to the portable terminals 4 and 5 when receiving the customer information update request including the editing request of the customer information from the portable terminals 4 and 5 or the like. Editing of customer information means, for example, changing the name, notification destination, card number, and the like. When the update processing is completed, the customer information updating unit 22 may transmit the completion notification to the portable terminals 4 and 5 through the communication unit 21. [

The issuing unit 23 receives the electronic ticket issuance request from the portable terminal 4 via the communication unit 21 and issues an electronic ticket. More specifically, when the issuer 23 receives the electronic ticket issuance request and receives a completion report (to be described in detail later) from the payment processing section 28, the issuance section 23 issues an electronic ticket. The electronic ticket issuing request includes information (ticket ID) specifying an electronic ticket to be issued, an upper limit amount of use of the electronic ticket, an expiration date of the electronic ticket, and a user ID. The issuing unit 23 refers to the electronic ticket management table (TBL212) and issues an electronic ticket based on the information included in the electronic ticket issuing request. Specifically, the issuing unit 23 stores (adds) the electronic ticket corresponding to the predetermined information in the issuance ticket management table TBL213.

3B is a table showing the electronic ticket management table (TBL 212). As shown in Fig. 3B, the electronic ticket management table (TBL212) stores the ticket ID, usage, company ID, and settable amount of all the electronic tickets in association with each other. The ticket ID is an identifier that uniquely identifies the type of electronic ticket. The predetermined ticket ID (e.g., " 99999 ") may be an identifier of an electronic ticket whose usage, company ID, and settable amount are " free ".Quot; free of charge " means that the user can freely designate the usage and the like (the details will be described later). The purpose is the use of the electronic ticket. The usage company ID is an identifier that uniquely identifies a usage company (seller) that can be used by the electronic ticket. A plurality of IDs may be set in the use company ID. The settable amount is the range of the amount of money that can be set as the usage upper limit of the electronic ticket. In addition, the settable amount in the electronic ticket management table (TBL212) does not necessarily have to be set.

4A is a table showing the issued ticket management table (TBL 213). 4A, the issue ticket management table (TBL 213) includes an issuance ticket ID, a ticket ID, an upper limit amount of use, an expiration date, a payer ID, a license holder ID, and an issuance ticket ID of an electronic ticket issued by the issuing unit 23 (Accumulates) the electronic ticket information associated with the use completion flag.

The issued ticket ID is an identifier that uniquely identifies the issued electronic ticket. The ticket ID is an identifier that uniquely identifies the type of the electronic ticket. The usage upper limit is the usage upper limit set in the electronic ticket. The validity period is the expiration date of the electronic ticket (the period of availability of the corresponding electronic ticket). In Fig. 4A, the valid period is set to the date, but it may be set to the time. The payer ID is an identifier that uniquely identifies a person who makes a payment on the purchase of the electronic ticket. The licensee ID is an identifier that uniquely identifies a person who can purchase a product or the like using the electronic ticket. The use completion flag is a flag indicating whether or not the electronic ticket has been used. "1" is set when the electronic ticket is used, and "0" is set when the electronic ticket is not used.

Further, as apparent from the electronic ticket management table TBL212 shown in Fig. 3B, the usage ID and usage company ID (hereinafter, " use " have. That is, the electronic ticket information of the issued ticket management table (TBL 213) includes a ticket ID which is information for specifying the use of the electronic ticket.

Based on the information in the electronic ticket management table (TBL212) and the information included in the electronic ticket issuance request, the issuing unit 23 issues a ticket ID, an upper limit amount of use, a valid period, a payer ID, Identify the user ID. In other words, when the ticket ID included in the electronic ticket issuance request exists in the electronic ticket management table (TBL 212), the issuing unit 23 specifies the ticket ID as the ticket ID of the electronic ticket to be issued. When the usage upper limit included in the electronic ticket issuance request is within the settable amount range in the electronic ticket management table (TBL212), the issuing unit 23 stores the usage upper limit as the usage upper limit of the electronic ticket to be issued Specify.

The issuing unit 23 also specifies the valid period included in the electronic ticket issuance request as the valid period of the electronic ticket to be issued. The issuing unit 23 also specifies the user ID included in the electronic ticket issuance request as the payer ID and the use-right user ID of the electronic ticket to be issued. At issuance of the electronic ticket, the issuing section 23 specifies that the utilization completion flag of the issued electronic ticket is " 0 ". Then, the issuing unit 23 stores (adds) the electronic ticket to which the specific issuing ticket ID and the specific information are associated in the issuance ticket management table TBL213. When the issuing process is completed, the issuing unit 23 may transmit a completion notification to the portable terminal 4 via the communication unit 21. [

The usage management unit 24 sets information specifying the purpose of the electronic ticket stored in the issued ticket management table (TBL 213), that is, a ticket ID, in accordance with the use destination designation from the first user who is the payer of the issued electronic ticket Change). Specifically, the usage management unit 24 receives a usage purpose designation from the portable terminal 4 of the first user, which is a payer, through the communication unit 21. The use destination designation includes an issue ticket ID for specifying an electronic ticket for changing the ticket ID and a ticket ID after the change. In addition, the utilization purpose designation may include a usage upper limit and / or an expiration date after changing the ticket ID. The usage management unit 24 refers to the issued ticket management table (TBL 213) and changes the ticket ID of the electronic ticket specified by the issued ticket ID included in the usage target designation to the ticket ID included in the usage target designation. In addition, in the case where the use upper limit amount is included in the use purpose designation, the usage upper limit amount and the like may be changed together with the ticket ID.

The use management unit 24 may change the ticket ID only when the ticket ID of the electronic ticket of interest is a predetermined ID. Specifically, the usage management unit 24 may perform the above-described change of the ticket ID only in the electronic ticket with the ticket ID " 99999 " whose usage is " free ". When the change of the ticket ID is completed, the usage management unit 24 may transmit a completion notification to the portable terminal 4 via the communication unit 21. [

The ticket information output unit 25 outputs information about an electronic ticket whose user is at least one of the payer and the user in accordance with a reading request from the user. More specifically, the ticket information output unit 25 receives a request for viewing from the portable terminal 4 or the portable terminal 5 via the communication unit 21. [ The browse request includes an issue ticket ID for specifying an electronic ticket desired to be browsed. The ticket information output unit 25 refers to the issued ticket management table (TBL 213), and specifies electronic ticket information according to the issued ticket ID included in the viewing request. The ticket information output unit 25 refers to the electronic ticket management table (TBL212), and identifies the usage and company ID corresponding to the ticket ID of the specific electronic ticket information. The ticket information output unit 25 transmits the information about the specific electronic ticket to the portable terminal 4 or the portable terminal 5 through the communication unit 21 as the transmission source of the viewing request.

The transfer management unit 26 acquires the transfer request from the first user who is the settlement of the issued electronic ticket and changes the use ticket of the electronic ticket to the designated character in the transfer request. Specifically, the transfer management unit 26 receives a transfer request from the portable terminal 4 of the first user, which is a payer, through the communication unit 21. [ The transfer request includes an issue ticket ID for specifying an electronic ticket for changing a usage right holder, and a user ID for specifying a second user who is a usage right holder after the change (that is, a transferor). Then, the transfer management unit 26 refers to the issued ticket management table (TBL 213) and changes the usage right ID of the electronic ticket specified by the issued ticket ID included in the transfer request to the user ID of the second user included in the transfer request . The transfer management unit 26 transmits a notification to the portable terminal 4 of the first user and the portable terminal 5 of the second user via the communication unit 21 that the modification (rewriting) of the user is completed It is possible.

The transaction management unit 27 manages transactions using electronic tickets by the user. The transaction management unit 27 permits the transaction using the electronic ticket only when the user uses the electronic ticket within the upper limit of usage. When the usage right is within the range of the use of the electronic ticket (that is, the use and the company ID), and the usage date and time is the validity of the electronic ticket Period, and permits the transaction using the electronic ticket.

Specifically, the transaction management unit 27 receives a settlement request from the user company terminal 7 through the communication unit 21. [ The settlement request is output by the user company terminal 7 in response to the settlement request from the second user who performs the transaction using the electronic ticket as the seller, the seller associated with the user company terminal 7. The settlement request includes the usage amount of the electronic ticket and the goods and service name to be traded. The settlement request includes a user ID specifying a seller associated with the user company terminal 7, a usage amount included in the settlement request, a product / service name, and a use date and time when a transaction is made using the electronic ticket. In addition, the use date and time of the transaction is, for example, regarded as the date and time when the use company terminal 7 receives the settlement request from the second user.

The transaction management unit 27 having received the settlement request performs authentication of the user company terminal 7 that has transmitted the settlement request. More specifically, the transaction management unit 27 refers to the customer management table TBL 211, and the user ID included in the settlement request exists in the customer management table TBL 211 and corresponds to the user ID in the customer management table TBL 211 And confirms that a user type is " 1 " (the corresponding user is a seller). When the authentication is completed, the transaction management unit 27 correlates the information included in the settlement request and stores it in the purchase management table (TBL 214).

4B is a table showing the purchase management table (TBL 214). 4B, the purchase management table (TBL 214) stores purchase information associated with a company ID, a usage amount, a product / service name, a usage date and time, and a payment code for each transaction using an electronic ticket . The use company ID is an identifier that uniquely identifies the company (seller) used in the transaction using the electronic ticket. The amount of usage is the amount paid by the electronic ticket in the transaction concerned. The name of a product or service is the name of a product or service related to the transaction. The use date and time is the date and time of the transaction. The payment code is an identifier that uniquely identifies the transaction.

The transaction management unit 27 specifies a user ID, a usage amount, a product / service name, and a use date and time included in the settlement request, and also identifies purchase information (a payout) corresponding to the specific information and a arbitrarily set payment code Code purchase information) is stored in the purchase management table TBL214. After storing, the transaction management unit 27 transmits a code issue notification indicating that the payment code has been issued to the use company terminal 7 through the communication unit 21. [ The code issuance notification includes the issued payment code.

The user company terminal 7 that has received the code issue notification transmits the code issue notification to the portable terminal 5 of the second user. The transmission of the code issuance notification to the portable terminal 5 by the user company terminal 7 may be realized by displaying the payment code on the app and presenting it to the second user or may be realized by using a QR code, Or the like and presenting it to the second user, or may be realized using local communication. Alternatively, the transmission of the code issue notification may be performed by orally transmitting a payment code from the user of the user company terminal 7 to the second user. Then, the payment code is inputted from the portable terminal 5 by the second user who has confirmed the payment code. The payment code input by the second user may be realized by manual input to the code input field of the app or may be realized by reading a figure such as QR code by the camera function of the portable terminal 5 . The transaction management unit 27 acquires the payment code inputted from the portable terminal 5 via the communication unit 21 and a user ID specifying the second user who has input the payment code.

The transaction management unit 27 that has acquired the payment code or the like from the portable terminal 5 performs transaction validity determination processing. In the validity determination process, the transaction management unit 27 performs each process of code identification, user identification, and amount confirmation. The transaction management unit 27 judges that the transaction using the electronic ticket is valid when all conditions are satisfied for all of the above processes.

In the code checking process, the transaction management unit 27 determines whether or not the payment code acquired from the portable terminal 5 is a correct payment code for making a payment request. Specifically, the transaction management unit 27 determines whether or not the acquired payment code is a payment code stored in the purchase management table (TBL214). The transaction management unit 27 regards that the predetermined condition in the code checking process is satisfied only when it is determined that the payment code is the correct payment code for making the payment request.

In the user identification process, the transaction management section 27 determines whether or not the second user can become the user. Specifically, the transaction management unit 27 determines whether or not the acquired electronic ticket with the user ID of the second user is stored in the issued ticket management table (TBL 213). The transaction management unit 27 regards that the predetermined condition in the user identification process is satisfied only when the second user determines that the user can be the user. In this case, the transaction management unit 27 specifies an electronic ticket in which the user ID of the second user is the user ID.

The transaction management unit 27 determines whether the usage amount in the transaction is within the upper limit of the usage amount of the electronic ticket, whether the purpose of use of the transaction is within the usage range of the electronic ticket, And determines whether or not the electronic ticket is within the validity period. Specifically, the transaction management unit 27 refers to the purchase management table (TBL 214), identifies the use company ID, usage amount, goods / service name, and use date / time corresponding to the payment code acquired from the portable terminal 5. And the purpose of use is specified by the company ID and the product / service name.

Then, the transaction management unit 27 refers to the issued ticket management table (TBL213), and determines that the usage upper limit of the electronic ticket specified in the user identification process is larger than the usage amount, the usage agrees with the purpose of use, It is determined whether or not there is an electronic ticket including the use date and time. Here, as described above, the ticket ID is stored as the information specifying the use of the electronic ticket in the issued ticket management table (TBL 213). In the electronic ticket management table (TBL212), the use of the electronic ticket And a user company ID are stored. Therefore, the transaction management unit 27 compares the use and company ID, which is the usage of the specific electronic ticket, with the product, service name and use company ID, which are the purpose of use corresponding to the payment code, It is determined whether or not there is a matching electronic ticket.

The transaction management section 27 regards that the predetermined condition in the confirmation processing of the amount of money is satisfied only when it is determined that the electronic ticket is present. In this case, the transaction management unit 27 specifies one electronic ticket that satisfies the conditions of the confirmation processing such as the amount of money. When there are a plurality of electronic tickets satisfying the condition, the transaction management unit 27 may preferentially specify, for example, an electronic ticket with a small upper limit of usage. It is also possible to receive an input of information designating an electronic ticket to be used from the second user, and specify one electronic ticket according to the input.

If the transaction management section 27 considers that the predetermined condition is satisfied in all of the code checking process, the user identification process, the amount confirmation process, etc., it is determined that the transaction is valid by the use of the specific electronic ticket in the confirmation process And permits the transaction. In this case, the transaction management unit 27 refers to the issued ticket management table (TBL213), and changes the use completion flag of the specific electronic ticket to "1" in the confirmation process of the amount of money. After the use completion flag is changed, the transaction management unit 27 outputs a modification payment request to the payment processing unit 28. [ The corrected payment request includes an issued ticket ID specifying an electronic ticket in which the use completion flag is changed, and a payment code corresponding to the transaction.

When the transaction management section 27 permits the transaction using the electronic ticket, the payment processing section 28 determines whether the difference between the upper limit of the usage amount of the electronic ticket used in the transaction and the actual usage amount in the transaction is greater than the difference The payment processing is performed so as to be returned to the payer. Specifically, the settlement processing unit 28 performs pre-settlement by the upper limit amount in the pre-payment step (more precisely, before the electronic ticket is issued), and in the payment processing, And performs correction processing according to the amount.

In the prepayment processing, the payment processing unit 28 first receives an electronic ticket issuance request from the portable terminal 4 via the communication unit 21. [ The electronic ticket issuance request includes information indicative of a usage upper limit of the electronic ticket to be issued and a user ID of the first user. The payment processing unit 28 specifies the card number of the first user by referring to the customer management table TBL 211 and then communicates with the card company terminal 6 through the communication unit 21 and uses the credit card of the user (Pre-settlement) by the maximum amount of use of the electronic ticket scheduled to be issued. The payment processing unit 28 outputs a pre-payment processing completion report to the issuing unit 23 when the pre-payment processing is completed.

In the modification processing (payment processing), the payment processing unit 28 receives the modification payment request from the preference transaction management unit 27, and acquires the issue ticket ID and the payment code included in the modification payment request. The payment processing section 28 refers to the issued ticket management table (TBL 213), specifies the usage upper limit value of the electronic ticket indicated by the acquired issued ticket ID, and refers to the purchase management table (TBL 214) We specify amount of use in transaction. Then, the settlement processing unit 28 specifies the amount obtained by subtracting the usage amount from the specific usage upper limit as a return amount to the first user who is the settlement person. The payment processing unit 28 specifies the card number of the first user by referring to the customer management table TBL 211 and then communicates with the card company terminal 6 through the communication unit 21 and uses the credit card of the user And performs the refund payment as much as the return amount. Alternatively, the payment processing unit 28 may perform a process of correcting the pre-payment amount to the usage amount. By this correction processing, finally, the settlement amount based on the transaction becomes equal to the transaction amount at the time of transaction.

When the correction processing (settlement processing) is completed, the settlement processing unit 28 notifies the settlement completion notification (second user) and the payer (first user) of the electronic ticket displayed by the issued ticket ID included in the correction payment request And transmits the settlement completion notification to the utilization company (seller) of the transaction represented by the payment code. Finally, the settlement processing unit 28 updates the settlement settlement table (TBL 215).

4C is a table showing the fixed settlement table (TBL 215). As shown in Fig. 4C, the fixed settlement table (TBL 215) stores fixed settlement information associated with settlement ID, payment code, and settlement amount in accordance with the settlement processing performed by the settlement processing unit 28. [ The payer ID is an identifier that uniquely identifies the payer of the electronic ticket according to the payment. The payment code is an identifier that uniquely identifies the transaction. The payment amount is the final payment amount at the time of the transaction. The settlement processing unit 28 stores the settlement person ID, the payment code, and the settlement amount (that is, the amount of use at the time of transaction) in the fixed settlement table (TBL 215) as fixed settlement information.

[Electronic Ticket Management Order]

Next, as an example of the electronic ticket management method, the electronic ticket management procedure by the electronic ticket management device 2 will be described with reference to FIG. 5, an electronic ticket is issued according to a request of a first user (steps S101 to S107), and the usage right of the electronic ticket is changed to a second user (steps S109 to 115) And the payment processing is performed according to the use of the electronic ticket by the second user (steps S117 to S139). Steps S117 and S125 of the respective steps to be described are not the processes in the electronic ticket management device 2, but are processes necessary for explaining the electronic ticket management.

First, an electronic ticket issuance request transmitted from the portable terminal 4 of the first user is received by the issuing section 23 and the settlement processing section 28 via the communication section 21 (step S101). The electronic ticket issuing request includes a ticket ID of an electronic ticket to be issued, an upper limit amount of use of the electronic ticket, an expiration date of the electronic ticket, and a user ID.

Then, the settlement processing unit 28 performs the prepayment processing (step S103). That is, the payment processing unit 28 specifies the card number of the first user with reference to the customer management table TBL 211, communicates with the card company terminal 6 via the communication unit 21, (Pre-settlement) by the maximum amount of usage of the electronic ticket scheduled to be issued. The payment processing unit 28 outputs a completion report of the prepayment processing to the issuing unit 23 when the prepayment processing is completed.

Subsequently, an electronic ticket is issued by the issuing unit 23 which has received the electronic ticket issuance request from the portable terminal 4 and the completion report of the prepayment processing from the payment processing unit 28, and the electronic ticket is issued (Stored) in the table TBL 213 (step S105: accumulating step). That is, the issuing unit 23 issues a ticket ID, an upper limit amount of use, an expiration date, a payer ID, an amount of money, and the like of the electronic ticket to be issued based on the information in the electronic ticket management table (TBL212) And the use-right user ID, and stores the electronic ticket in which the specific information is associated with the arbitrarily set issuance ticket ID in the issuance-ticket management table TBL213. After the issuance of the electronic ticket, the issuing unit 23 transmits the issuing completion notification to the portable terminal 4 (step S107).

An administrative image of an electronic ticket using an app in the electronic ticket issuing process shown in the above-described steps S101 to S107 is shown in Fig. 6A. FIG. 6A shows an example in which a customer (company) at the time of transaction using an electronic ticket is a taxi company (FIGS. 6B and 6C described later are also the same). In the example shown in Figs. 6A, 6B and 6C, the portable terminal 4 of the first user, the portable terminal 5 of the second user, and the user company terminal 7 of the taxi company, A special app for using an electronic ticket as a business partner is downloaded.

FIG. 6A shows an electronic ticket management image using an app when a first user who is a payer purchases an electronic ticket. The first user inputs information specifying the electronic ticket to be purchased and the usage upper limit and the like and activates the dedicated app of the taxi company from the portable terminal 4 to perform an input for instructing purchase (FIG. 6A) See app display image before purchase "). And the electronic ticket issuing request is transmitted to the electronic ticket managing apparatus 2 based on the input. After the pre-payment and issuance processing of the electronic ticket is completed, the first user can confirm the information about the issued electronic ticket in the dedicated app (see "after-purchase" app display image in FIG. 6A).

Returning to Fig. 5, a process for changing the usage right holder will be described. After the issuance of the electronic ticket, the transfer request of the electronic ticket is transmitted from the portable terminal 4 of the first user who has made the pre-settlement, and the transfer request is received by the transfer management unit 26 via the communication unit 21 (Step S109). The transfer request includes an issue ticket ID for specifying an electronic ticket for changing a usage right holder and a user ID for specifying a second user who is a usage right holder after the change (that is, a transferor).

Subsequently, the transfer manager 26 changes the usage right of the electronic ticket according to the transfer request (step S111, changing step). In other words, the transfer manager 26 refers to the issued ticket management table (TBL 213), changes the usage-right user ID of the electronic ticket specified by the issued-ticket ID included in the transfer request to the user ID of the second user included in the transfer request do. After the use right holder is changed, a notification that the change (rewrite) of the right holder is completed is transmitted to the portable terminal 4 of the first user and the portable terminal 5 of the second user by the transfer management part 26 (step S113 , S115).

After the notification that the change of the usage right person shown in the above-mentioned steps S113 and S115 is completed (or when it is done), the first user and the second user can transmit and receive the electronic ticket using the app. 6B shows an electronic ticket management image using an app when the electronic ticket is transferred from the portable terminal 4 of the first user to the portable terminal 5 of the second user.

When the first user and the second user are close to each other, information indicating the transferred electronic ticket (rewritten with the user) is transmitted from the portable terminal 4 of the first user to the portable terminal 5 of the second user (See the app display image of " when the second user is nearby " in Fig. 6B). In this case, information indicating the electronic ticket transmitted and received by the short distance communication is transmitted from both the portable terminal 4 and the portable terminal 5 to the electronic ticket managing apparatus 2. [

If the first user and the second user are distant from each other, the information indicating the transferred electronic ticket (rewritten with the user) is transmitted from the portable terminal 4 to the electronic ticket management apparatus (for example, 2), and the information may also be transmitted from the electronic ticket managing apparatus 2 to the portable terminal 5 (see the app display image of "when the second user is far away" in FIG. 6B).

Returning to Fig. 5, the settlement processing will be described. When the transaction using the electronic ticket is performed by the second user who is the recipient after transfer of the electronic ticket, the settlement request is transmitted from the portable terminal 5 of the second user to the customer company terminal 7 of the customer (step S117) . In the settlement request, the amount of use of electronic ticket and the goods and service name to be traded are included. In addition, the transmission of the settlement request may be realized by the short-range communication, or may be realized by causing the company terminal 7 to read the figure such as the QR code and the bar code. Alternatively, the settlement request may be made orally for the user of the user company terminal 7 from the second user. Then, the settlement request is transmitted to the electronic ticket managing apparatus 2 from the user company terminal 7 that received the settlement request, and the settlement request is received by the transaction managing unit 27 via the communication unit 21 (step S119). The settlement request includes a user ID specifying a seller of the user company terminal 7, a usage amount and a product / service name included in the settlement request, and a use date and time when a transaction is made using the electronic ticket.

Then, the transaction managing unit 27 authenticates the user company terminal 7 according to the settlement request (step S121). That is, the transaction management unit 27 refers to the customer management table (TBL 211), and determines whether the user ID included in the settlement request exists in the customer management table (TBL 211) And confirms that the user type is " 1 " (the user is the seller). When the authentication is completed, the transaction management unit 27 stores the purchase information associated with the information included in the settlement request and the arbitrarily set payment code in the purchase management table (TBL 214). After storing, a code issuing notice indicating that the payment code has been issued by the transaction managing unit 27 is transmitted to the user company terminal 7 (step S123), and the code issuing notice is transmitted from the user company terminal 7 to the portable terminal (Step S125). The transmission of the code issuance notification to the portable terminal 5 by the user company terminal 7 may be realized by displaying the payment code on the app and presenting it to the second user or may be realized by using the QR code, And presenting it to the second user, or may be realized using local communication. Alternatively, the transmission of the code issue notification may be performed by orally transmitting a payment code from the user of the user company terminal 7 to the second user.

The payment code is input from the portable terminal 5 by the second user who has confirmed the payment code. A user ID for specifying the second user who has input the payment code and the payment code is transmitted to the transaction management unit 27) (step S127).

Then, the transaction management unit 27 that has obtained the payment code or the like from the portable terminal 5 determines the validity of the transaction, and permits the transaction using the electronic ticket only when the condition such as the upper limit of the usage is satisfied ( Step S129, permission step). In other words, the transaction management unit 27 performs each process of code identification, user identification, and amount confirmation, and when the predetermined condition is satisfied for all the processes, it is determined that the transaction using the electronic ticket is valid, Allows the trading of tickets.

When the transaction using the electronic ticket is permitted, the transaction management unit 27 updates the electronic ticket to use completion (step S131). That is, the transaction management unit 27 refers to the issued ticket management table (TBL 213) and changes the use completion flag of the electronic ticket specified as the electronic ticket used for the transaction to "1". After the use completion flag is changed, the transaction management unit 27 outputs a modification payment request to the payment processing unit 28. [ The modified payment request includes an issued ticket ID specifying an electronic ticket in which the use completion flag is changed, and a payment code corresponding to the transaction.

Subsequently, the settlement processing unit 28 performs the settlement processing so that the difference between the upper limit of the usage amount of the electronic ticket used for the transaction and the actual usage amount in the transaction is reduced to the payer of the electronic ticket S133, a step of performing payment processing). In other words, the payment processing unit 28 specifies the usage upper limit value of the electronic ticket indicated by the acquired issued ticket ID with reference to the issued ticket management table (TBL 213), and also refers to the purchase management table (TBL214) We specify amount of use in transaction. Then, the settlement processing unit 28 specifies the amount of the amount of use deducted from the specific amount of use upper limit as a return amount for the first user who is the settlement person. The payment processing unit 28 specifies the card number of the first user by referring to the customer management table TBL 211 and then communicates with the card company terminal 6 through the communication unit 21 and uses the credit card of the user (Or a process of correcting the advance payment amount to the usage amount) by the return amount.

After the settlement processing, the settlement processing unit 28 causes the portable terminal 5 and the payer (first user) of the user of the electronic ticket (the second user) displayed by the issued ticket ID included in the correction payment request, (Step S135, S136). In addition, the settlement processing unit 28 transmits a settlement completion notification to the use company terminal 7 of the seller of the transaction represented by the payment code (step S137). Finally, the settlement processing unit 28 updates the settlement settlement table TBL 215 (step S139). In other words, the payment processing unit 28 stores the payer ID, the payment code, and the payment amount (that is, the usage amount at the time of transaction) in the fixed payment table (TBL 215) as the fixed payment information.

In addition, the method of payment of the charge from the credit card company to the user company (payment timing) is not limited. For example, at the time of the advance payment, a fee according to the amount of the advance payment is paid from the credit company to the user company, and at the time of correction payment, the amount due to the correction payment (refund, etc.) may be made between the credit company and the user company. The " advance payment time " may be a time at which the advance payment is made, or may be a credit date of the user's credit card, for example. Further, at the time of the advance payment, the payment from the credit card company to the user company may be paid at the time of the amendment payment without paying from the credit card company to the user company.

FIG. 6C shows an electronic ticket management image using an app when a second user performs a transaction using the electronic ticket to which the second user has transferred. The second user inputs an amount corresponding to the riding fare of the taxi from the portable terminal 5 and inputs an instruction to make a payment. According to the input, the settlement request is transmitted to the use company terminal 7 of the taxi company, and the user company terminal 7 inputs an instruction for settlement. The settlement request is transmitted to the electronic ticket managing apparatus 2 in accordance with the input. In addition, the settlement request may be made verbally to the user of the user company terminal 7 from the second user. A payment code is issued after the authentication of the taxi company as the user company in the electronic ticket management device 2 and the payment processing is performed in the electronic ticket management device 2 when the second user inputs the payment code from the app .

[Operation and effect of the present embodiment]

Next, the operation and effect of the above-described electronic ticket managing apparatus 2 will be described.

In this electronic ticket management device 2, the use right of the electronic ticket is changed in accordance with the transfer request from the first user who is the payer. When the second user, who is the use right holder, uses the electronic ticket in the usage upper limit, the use of the electronic ticket is permitted, and the difference between the usage upper limit and the usage amount is returned to the first user. Therefore, the higher the amount of use of the second user and the upper limit of the usage amount of the electronic ticket, the larger the amount is returned to the first user. Therefore, even if the first user sets the upper limit of usage in the setting of the usage upper limit or the purchase amount of the second user is low, the disadvantage of the first user does not occur. As a result, the transfer of the electronic ticket can be promoted, and as a result, the utilization of the electronic ticket can be promoted.

Also, in the electronic ticket management device 2, the electronic ticket information includes information specifying the usage of the electronic ticket. When the second user, who is the user of the transaction, uses the electronic ticket within the usage upper limit To the case where the purpose of use is within the range of use, and permits the transaction using the electronic ticket. As a result, the use of the electronic ticket is limited, and the burden of managing the electronic ticket can be reduced.

In addition, information for specifying (changing) the information specifying the usage of the electronic ticket stored in the issued ticket management table (TBL 213), that is, the ticket ID, in accordance with the usage designation from the first user who is the payer of the issued electronic ticket And a management unit. This makes it possible to prevent the electronic ticket from being used by the first user who is the payer for an unintended use. Therefore, the convenience of the payer can be improved, and the use of electronic tickets can be further promoted.

In addition, in the electronic ticket management device 2, the electronic ticket information further includes an expiration date of the electronic ticket, and when the transaction management section 27 uses the electronic ticket within the usage upper limit, , And the use date and time is within the validity period, and permits the transaction using the electronic ticket. Accordingly, the use period of the electronic ticket is limited, and the burden of managing the electronic ticket can be reduced. In addition, since the expiration date can be set by the payer, it is possible to promote the use of the electronic ticket in the payer's intended period. Therefore, the convenience of the payer can be improved, and the use of electronic tickets can be further promoted.

In the electronic ticket management device 2, the settlement processing unit 28 performs the pre-settlement by the upper limit of the usage amount at the previous stage of the settlement process, and performs the correction process according to the actual usage amount in the settlement process You may. By performing the advance settlement as much as the usage upper limit amount, the purchasing power of the electronic ticket can be linked to the settlement completion amount, and further settlement can be performed according to actual conditions. In other words, when an electronic ticket with an upper limit of usage is issued, the use of the electronic ticket makes it possible to purchase a product or the like as much as the maximum amount of usage. Therefore, by making a pre-settlement as much as the upper limit of the usage amount, the purchasing power of the electronic ticket (the maximum purchase amount) and the amount of settlement can be matched.

The embodiment has been described above, but the present disclosure is not limited to the above embodiment. For example, the payment processing section 28 has been described in the pre-payment processing step to perform the pre-settlement by the upper limit amount of use, and to perform the correction processing in accordance with the actual amount of money in the settlement processing, however, the present invention is not limited thereto. That is, the settlement processing unit 28 may perform post settlement for the settlement processing by the amount of use, without performing the pre-settlement. As a result, payment can be made only once after the amount of use of the electronic ticket is fixed, so that settlement can be simplified. In addition, even in the case of performing settlement (post settlement) only once in the settlement process, settlement is made by the amount of use, so that the right corresponding to the difference between the amount of use upper limit and the amount of use is left to the first user ) do. That is, the difference between the usage upper limit and the usage amount of the right to use the electronic ticket is returned to the first user.

FIG. 7 is a flowchart showing an execution procedure of the electronic ticket management method according to the modification example, in which post-settlement is performed by the usage amount. 7 are basically the same as those in the case of performing the pre-payment shown in Fig. 5, and the steps S101, S105 to S131, and S135 to 139 in Fig. 5 correspond to the respective processes in the step S201 , S205 to S231, and S235 to 239, respectively. On the other hand, in the process of Fig. 5, the prepayment process (step S103) is performed in response to the electronic ticket issue request, while the prepayment process is not performed in the process of Fig. Instead of the correct payment processing (step S133) performed in Fig. 5, the settlement processing for performing post settlement (step S234) is performed in Fig. As described above, in the processing according to the modification shown in Fig. 7, settlement (post settlement) is performed only once in the settlement processing.

2 Electronic ticket management device
23 Issuing Department
24 Application management department
26 Transfer Manager
27 Transaction Management Department
28 Payment Processing Department
TBL213 Issued Ticket Management Table

Claims (7)

A storage unit for storing electronic ticket information including an upper limit amount of usage of the electronic ticket, a usage right holder and a payer;
A transfer manager for acquiring a transfer request from the first user who is the payer and changing the usage right holder of the electronic ticket information stored in the storage section to a second user specified in the transfer request;
A transaction management unit for limiting the use of the electronic ticket within the upper limit of the usage by the second user as the usage right user and permitting the transaction using the electronic ticket; And
When the electronic ticket is used by the second user when the transaction management unit permits the transaction using the electronic ticket, the usage maximum amount of the electronic ticket used in the transaction and the usage amount of the electronic ticket used in the transaction A settlement processing unit for making a settlement process so that the difference between the actual amount of use and the actual amount of use is reduced to the first user who is the settlement person of the electronic ticket;
The electronic ticket management apparatus comprising: The method according to claim 1,
Wherein the electronic ticket information further includes information specifying a usage of the electronic ticket,
Wherein the transaction management unit further restricts the case where the use purpose is within the range of the usage when the use right holder uses the electronic ticket within the usage upper limit and permits the transaction using the electronic ticket, . The method of claim 2,
A usage management section for acquiring a usage designation from the payer and setting information specifying the usage of the electronic ticket information stored in the storage section to a content designated by the usage purpose specification;
The electronic ticket management apparatus comprising: The method according to claim 1,
Wherein the electronic ticket information further includes an expiration date of the electronic ticket,
Wherein the transaction management unit further restricts the case where the use date and time are within the valid period when the use right holder uses the electronic ticket within the usage upper limit and permits the transaction using the electronic ticket, . 5. The method according to any one of claims 1 to 4,
Wherein the settlement processing unit performs the advance payment by the amount of the upper limit of usage in the previous step of the settlement processing and performs the correction processing in accordance with the actual usage amount in the settlement processing. 5. The method according to any one of claims 1 to 4,
Wherein the settlement processing unit performs post settlement by the amount of use in the settlement processing. An electronic ticket management method performed by an electronic ticket management device,
Accumulating electronic ticket information including an upper limit amount of use of an electronic ticket, a user of use, and a payer;
Acquiring a transfer request from the first user who is the payer and changing the user of the electronic ticket information from the transfer request to the second user specified in the transfer request;
Permitting a transaction using the electronic ticket by limiting the case where the second user as the usage right user uses the electronic ticket within the usage upper limit; And
When the electronic ticket is used by the second user, the usage limit of the electronic ticket used for the transaction and the usage amount of the electronic ticket used in the transaction are compared with each other, Performing a settlement process so that the difference between the amount of money actually used and the actual amount of use is reduced to the first user who is the payee of the electronic ticket;
The electronic ticket management method comprising the steps of:

Images