KR101824015B1 - Mobile Ticket Trading System - Google Patents

Abstract

The present invention relates to a mobile ticket transaction system, and more particularly, to a mobile ticket transaction system that includes a facility for transferring or returning a physical ticket to a purchaser, or a facility for receiving a ticket without using a business link such as a ticket use place and a computer processing Even if it is a real-time ticket transaction, a refund, and a resale.
The present invention has the following effects.
It is possible to transmit the ticket to the buyer without worrying about the outflow of the ticket by transmitting only the general information of the ticket, not the actual ticket, to the buyer at the time of purchase of the ticket.
In addition, the purchaser can confirm the purchase by exchanging the cipher key with the seller at the time of actually using the ticket and requesting the encrypted ticket, thereby obtaining a favorable refundable period compared with the existing transaction method. Tickets that have not been read during this period can be refunded in real time by confirming whether or not the ticket is read at the time of the request of the buyer's refund. The ticket purchaser does not need to certify that he did not use the ticket.
Finally, the seller can confirm whether or not the ticket is read according to whether or not the encrypted ticket is delivered, so that the seller can resell the ticket without worrying about the ticket of the flea market. The cost for the facility to receive or return the physical ticket to the buyer, There is no need to consider the cost of making business connections such as ticket usage and computation processing to determine whether or not to use the service.

Description

Mobile ticket transaction system {omitted}

The present invention relates to a mobile ticket transaction system, and more particularly, to a mobile ticket transaction system that includes a facility for transferring or returning a physical ticket to a purchaser, or a facility for receiving a ticket without using a business link such as a ticket use place and a computer processing Even if it is a real-time ticket transaction, a refund, and a resale.

The number of travelers to and from home is increasing due to the development of transportation means and the improvement of quality of life.

In addition, due to the activation of the Internet and smart phones, many travelers have pre-booked their travel plans according to their travel plans as well as flight and accommodation reservations.

In order to supply cheaper tickets, the ticket seller (A) purchases a large amount of tickets at a low price from a ticket issuer (B) who uses the ticket, and sells the tickets to the consumer (C) at a reasonable price. In most cases, Since the company (A) takes the method of delivering the physical ticket to the consumer (C) or delivering the ticket and the corresponding electronic document (pdf, etc.) by e-mail, the ticket itself is immediately disclosed.

If the consumer (C) requests a refund of the ticket, the ticket seller (A) must establish a business link with the ticket issuer (B) and computer processing to know whether the ticket is used, Ticket issuer (B) costs to build and manage it all.

This is especially the case when the ticket issuer (B) is a local company in the overseas, because of the various ticket management system, time difference and communication problem in each country and company as well as computer processing problem, It is very difficult to expect.

Also, the ticket vendor (A) tries to provide a convenient way to purchase tickets, but often the refund policy is adversely applied to the consumer (C).

Consumers (C) will incur unacceptable expenses for purchasing tickets that are not used, even if they are inevitably difficult to use due to changes in schedule, weather, or disease.

Therefore, there is a need for inventing a service and a technology capable of supporting convenient and reasonable transactions for ticket seller (A), ticket issuer (B), and consumer (C).

Korean Registered Patent No. 10-1198884 (Nov. 07, 2012)

The problems to be solved in the present invention are as follows.

It is also possible to return unused tickets to the purchaser immediately as a simple procedure even if there are no facilities for receiving or returning the actual ticket to the buyer or for business connection such as ticket use and computer processing in order to judge whether or not the ticket is used , And presents a mobile ticket transaction system to allow sellers to resell tickets without having to worry about the tickets.

In order to solve the above problems,

A ticket transaction app (100) receives a ticket purchase request from a buyer (C) and receives a ticket from the ticket transaction app (100) A ticket purchase interface 110 for transmitting a ticket purchase request to the transaction module 200, a purchase ticket browsing interface 130 for receiving a ticket reading request from the purchaser C and transmitting an encryption request to the electronic signature module 140, A purchase ticket refund interface 170 for receiving a ticket refund request from the seller C and delivering an encryption request to the electronic signature module 140, a ticket decryption module 160 for receiving and decrypting the encrypted ticket from the seller server 20, A purchase ticket inquiry interface 120 for providing the buyer C with ticket general information transmitted from the seller server 20, ticket detail information received from the ticket decryption module 160, and ticket refund information received from the seller server 20, ), The ticket browsing interface 130 encrypts the ticket browsing request at the time of encryption request and transmits the ticket browsing request to the ticket transaction module 200. The purchase ticket refund interface 170 encrypts the ticket refund request at the time of encryption request and transmits the ticket refund request to the ticket transaction module 200 And a ticket transaction module 200 for interfacing with the ticket transaction app 100 to transmit and receive ticket related requests and ticket related information and a ticket transaction module 200 The ticket transaction module 200 receives the ticket purchase request from the ticket purchase interface 110 and issues a ticket to the ticket information transmission module 220. [ Transmits the request, stores the transaction information in the encryption DB 300, decrypts the encrypted ticket reading request received from the request encryption module 140 to check the ticket owner information, and transmits the ticket owner information to the seller ticket encryption / decryption module 240 And transmits a ticket refund request decrypted to the seller ticket encryption / decryption module 240. The ticket refund module 240 decrypts the encrypted ticket refund request received from the request encryption module 140, Receives the ticket issuance request from the user management module 210 and the user management module 210, fetches the ticket general information from the encryption DB 300 and transmits the ticket general information to the purchase ticket inquiry interface 120, The ticket information transmission module 220 for storing information, the encrypted ticket detail information from the encryption DB 300, and stores the ticket reading completion information in the encryption DB 300, encrypts the decrypted ticket detailed information, Receives the ticket refund request from the seller ticket decryption module 240 and the user management module 210 that transmit the ticket general information to the ticket decryption module 160, And a ticket refund module 250 for storing ticket refund completion information in the encryption DB 300 and transmitting the refund information together with ticket general information to the purchase ticket inquiry interface 120. The encryption DB 300 is a transaction A ticket information DB 320 for storing ticket general information, an encrypted ticket DB (not shown) for encrypting and storing the ticket detailed information, a transaction information DB 310 for storing ticket information, ticket reading completion information and ticket refund completion information, The ticket information is general information including an amount of a ticket, and the ticket detailed information is information of a specific ticket necessary for use of the ticket , The purchaser C can inquire only the general information of the ticket until the ticket reading request, and when the buyer C requests the ticket detail information And the ticket reading completion information is stored in the transaction information DB 310 so that the sale of the ticket is confirmed and the ticket refund request is made only when the purchaser C does not request the ticket browsing. We present a ticket transaction system.

delete

The present invention has the following effects.

It is possible to transmit the ticket to the buyer without worrying about the outflow of the ticket by transmitting only the general information of the ticket, not the actual ticket, to the buyer at the time of purchase of the ticket.

In addition, the purchaser can confirm the purchase by exchanging the cipher key with the seller at the time of actually using the ticket and requesting the encrypted ticket, thereby obtaining a favorable refundable period compared with the existing transaction method. Tickets that have not been read during this period can be refunded in real time by confirming whether or not the ticket is read at the time of the request of the buyer's refund. The ticket purchaser does not need to certify that he did not use the ticket.

Finally, the seller can confirm whether or not the ticket is read according to whether or not the encrypted ticket is delivered, so that the seller can resell the ticket without worrying about the ticket of the flea market. The cost for the facility to receive or return the physical ticket to the buyer, There is no need to consider the cost of making business connections such as ticket usage and computation processing to determine whether or not to use the service.

1 is a block diagram of a mechanical part in which the present invention operates;
2 is a block diagram of a ticket purchase process;
3 is a block diagram of a ticket browsing process.
4 is a block diagram of a ticket refund process;
5 is a diagram illustrating a process of purchasing and browsing a ticket at a purchaser terminal;

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, preferred embodiments of the present invention will be described with reference to the accompanying drawings. However, the scope of the present invention should be understood from the description of the claims. Further, the description of known technology which obscures the gist of the present invention is omitted.

The present invention is summarized as follows.

That is, in the system in which the buyer terminal 10 on which the ticket transaction app 100 is loaded and the ticket transaction app 100 are interlocked with the seller server 20, the ticket transaction app 100 receives a ticket purchase request from the buyer C A purchase ticket retrieval interface 130 for receiving a ticket reading request from the purchaser C, a purchase ticket refund interface 170 for receiving a ticket refund request from the purchaser C, A ticket decryption module 160 for receiving and decrypting the encrypted ticket, ticket general information transmitted from the seller server 20, ticket detailed information transmitted from the ticket decryption module 160, ticket refund received from the seller server 20, And a purchase ticket inquiry interface (120) for providing the buyer (C) with any one or more of the information,

The ticket purchase interface 110 receives a ticket purchase request from the buyer C and transmits a ticket purchase request to the ticket transaction module 200. The purchase ticket browsing interface 130 receives a ticket read request from the buyer C The purchase ticket refund interface 170 receives the ticket refund request from the buyer C and transmits an encryption request to the electronic signature module 140. The ticket transaction refund application 170 receives the ticket refund request from the electronic signature module 140, The ticket authentication module 100 encrypts the request for ticket browsing at the request of encryption at the purchase ticket browsing interface 130 and transfers the ticket request to the ticket transaction module 200 or encrypts the ticket refund request at the request of the purchase at the purchase ticket refund interface 170, A request encryption module 140 for delivering the ticket to the transaction module 200, and a buyer ticket decryption module 160 for receiving and decrypting the encrypted ticket from the ticket transaction module 200,

The seller server (20) includes a ticket transaction module (200) for interfacing with the ticket transaction app (100) and transmitting / receiving a ticket related request or ticket related information; The ticket transaction module 200 receives the ticket purchase request from the ticket purchase interface 110 and transmits the ticket information to the ticket transaction module 200. The ticket transaction module 200 receives the ticket purchase request from the ticket purchase interface 110, Transmits the ticket issuance request to the module 220, stores the transaction information in the encryption DB 300, or decrypts the encrypted ticket reading request received from the request encryption module 140 to check the ticket owner information, Module 240, or decrypts the encrypted ticket refund request received from the request encrypting module 140 to check whether the ticket can be refunded. The ticket refund module 240 decrypts the ticket, A purchasing user management module 210 for transferring a request, a ticket issuance request from the user management module 210, a ticket general information from the encryption DB 300, A ticket information transmission module 220 for transmitting the ticket information to the encryption DB 300 and storing the ticket owner information in the encryption DB 300, a decryption module for decrypting and decoding the encrypted ticket detail information from the encryption DB 300, A vendor ticket decryption module 240 for storing the read completion information and encrypting the decrypted ticket detailed information and transmitting the decrypted ticket detailed information to the buyer ticket decryption module 160, a ticket refund request receiving module for receiving the ticket refund request from the user management module 210, And a ticket refund module 250 for storing ticket refund completion information in the encryption DB 300 and transmitting the refund information together with the ticket general information to the purchase ticket inquiry interface 120 The encryption DB 300 includes a transaction information DB 310 for storing transaction information, ticket owner information, ticket reading completion information and ticket refund completion information, a ticket information DB 320 for storing ticket general information, Encrypt Participating stores will be encrypted on the mobile ticket trading systems that feature configured to include a ticket DB (330).

The ticket transaction system of the present invention includes a ticket transaction app 100, a ticket transaction module 200, and an encryption DB 300. (See FIG. 1)

The ticket transaction application 100 is an application installed in the purchaser terminal 10 and is a client corresponding to the seller server 20 and receives a request for ticket purchase, browsing and refund from the ticket purchaser C, The result can be inquired.

The purchaser terminal is not limited to a smart device that can be loaded with an application such as a smart phone or a tablet PC.

The ticket in the present invention is preferably a short-term validity period and a long-term unlimited use period or a long-term use period rather than a ticket which can not be used or resold when a specific date has elapsed.

The communication between the ticket transaction app 100 and the ticket transaction module 200 is preferably transmitted through a network encrypted with SSL (Secure Sockets Layer), which is an Internet communication protocol protocol.

The ticket transaction application 100 includes a ticket purchase interface 110, a purchase ticket inquiry interface 120, a purchase ticket browsing interface 130, a request encryption module 140, a buyer ticket decryption module 160, (170).

The ticket purchase interface 110 receives a ticket purchase request from the buyer C and transmits a ticket purchase request to the ticket transaction module 200. The ticket purchase request may include transaction information such as information of the buyer (C), information of the ticket to be purchased, date and time of the purchase request, purchase price, use place, option,

The purchase ticket browsing interface 130 receives a ticket browse request from the buyer C and encrypts the ticket browse request in the request encrypting module 140. Specifically, the purchase ticket browsing interface 130 transmits an electronic signature request to the electronic signature module 141. [ The ticket reading request is a request to view detailed information (ticket number, bar code, etc.) of a ticket in order to use the ticket purchased by the purchaser (C). That is, the buyer C can inquire only the general information of the ticket until the ticket reading request, and can confirm the detailed information of the ticket without requesting the ticket reading, which is usually performed at the stage just before the ticket use. Also, the actual sale between the ticket seller (A) and the buyer (C) is completed only when the buyer's ticket is requested to be viewed.

The purchase ticket refund interface 170 receives a ticket refund request from the purchaser C and encrypts it in the request encrypting module 140. Specifically, the purchase ticket refunding interface 170 transmits an electronic signature request to the electronic signature module 141. [ A ticket refund request is a request made by the buyer (C) when he / she does not use the purchased ticket and wants to refund the ticket. That is, if the buyer (C) does not request the ticket inspection and the detailed information of the ticket is not retrieved, the ticket is not used yet (or is not actually sold).

The request encryption module 140 encrypts the request from the buyer and transmits the encrypted request to the ticket transaction module 200, which may be an electronic signature module 141. [

The electronic signature module 141 generates a public key / secret key pair when requesting an electronic signature at the purchase ticket browsing interface 130, digitally signs the request to read the ticket with a private key, and then transmits the electronic signature to the ticket transaction module 200 together with the public key . In addition, the purchase ticket refund interface 170 generates a public key / secret key pair when requesting an electronic signature, digitally signs the ticket refund request with a secret key, and transmits the digital signature together with the public key to the ticket transaction module 200. The electronic signature is for authenticating that the user of the ticket transaction app 100 requesting ticket reading or ticket refund is a purchaser C and generates a ticket reading request or a ticket refund request by encrypting it with a secret key in the digital signature module 141. [ Which is decrypted in the user management module 210 by a public key which is transmitted to the ticket transaction module 200 together.

The identity check of the purchaser C in the ticket transaction app 100 can be confirmed through a password preset by the purchaser or a user fingerprint of the smart phone.

The buyer ticket decryption module 160 receives and decrypts the encrypted ticket from the ticket transaction module 200 and includes a buyer symmetric key exchange module 161 and a buyer symmetric key decryption module 162.

The buyer symmetric key exchange module 161 exchanges the symmetric key with the ticket transaction module 200 and delivers the symmetric key to the shopper symmetric key decryption module 162. That is, a module for sharing a symmetric key between a buyer terminal 10 and a seller server 20 by using a symmetric key exchange technique such as Diffie-Hellman, and the symmetric key is used for encrypting and decrypting detailed information of a ticket do. The buyer's symmetric key exchange module 161 transfers the symmetric key shared with the ticket transaction module 200 to the buyer's symmetric key decryption module 162.

The purchaser symmetric key decryption module 162 receives the ticket encrypted with the symmetric key from the ticket transaction module 200 and decrypts the ticket using the symmetric key received from the purchaser symmetric key exchange module 161. That is, since the ticket received from the ticket transaction module 200 includes detailed information but is encrypted with the symmetric key, it is decrypted using the symmetric key received from the purchaser's symmetric key exchange module 161 to obtain detailed information of the ticket . Symmetric key decryption methods include, but are not limited to, DES, AES, and LEA.

The purchase ticket inquiry interface 120 receives the ticket general information transmitted from the ticket transaction module 200, the ticket detailed information received from the buyer symmetric key decryption module 162, and the ticket refund information received from the ticket transaction module 200 And provides one or more pieces of information to the buyer (C).

Therefore, if the buyer C makes a purchase request, the buyer C confirms the general information about the purchase ticket, confirms the detailed information about the purchase ticket when requesting the ticket reading, or confirms that the purchase ticket is refunded Information can be confirmed.

In this case, the "general information" of the ticket refers to general information of the ticket, not about the specific ticket, such as the type of ticket, the place of use, amount, benefit, other general information, period of use, etc., I can not.

The "detailed information" of the ticket includes information necessary for use of a specific ticket such as a ticket number and a barcode. Therefore, in order to use a ticket, detailed information of the ticket must be read.

The ticket transaction module 200 is a module that transmits and receives ticket related requests and ticket related information in cooperation with the ticket transaction apps 100 in the seller server 20. [

The ticket-related request means purchase, inquiry, browsing, refund request, etc. made by the buyer (C) through the ticket transaction app 100. Ticket related information includes ticket general information, encrypted ticket detail information, electronic signature, , A symmetric key, refund information, and the like.

A ticket management module 210, a ticket information transmission module 220, a seller ticket encryption / decryption module 240, and a ticket refund module 250.

The user management module 210 performs the following functions according to the order of purchase, browse, and refund requests of the buyer C through the ticket transaction app 100 as follows.

Upon receipt of a ticket purchase request: a ticket purchase request is received from the ticket purchase interface 110. Accordingly, the ticket issuance request is transmitted to the ticket information transmission module 220 and the transaction information is stored in the transaction information DB 310 of the encryption DB 300. The ticket purchase request may include transaction information such as information of the buyer (C), information of a ticket to be purchased, date and time of purchase request, and purchase price. The ticket for requesting ticket issuance is a ticket for requesting a ticket purchase.

Upon receipt of the ticket request: the digital signature module 141 receives the digital signature request and the public key. At this time, the ticket owner information is confirmed from the transaction information DB 310. When the ticket owner information is confirmed, the ticket viewing request is transmitted to the seller symmetric key exchange module 241. The method of confirming the ticket owner information is to decrypt the transmitted digital signature read request with the public key received together, and if the digitally signed request is correct, the corresponding ticket owner information is retrieved from the transaction information DB 310. [

Upon request for a ticket refund: the electronic signature module 141 receives the digitally signed refund request and the public key. At this time, it is confirmed whether the refund is possible through the transaction information DB 310 and the ticket refund request is transmitted to the seller symmetric key exchange module 241. In the method of confirming the refund possibility, it is checked whether or not the ticket is read according to the ticket reading completion information, and it is confirmed that the refund is possible only when the ticket is not browsed, that is, when there is no ticket reading completion information.

The ticket information transmission module 220 receives the ticket issuance request from the user management module 210 (that is, when the buyer makes a ticket purchase request), the ticket information transmission module 220 receives a ticket from the ticket information DB 320 of the encryption DB 300 And transmits the information to the purchase ticket inquiry interface 120 so that the purchaser C can confirm the information. Also, the information of the purchaser who made the ticket purchase request is stored in the transaction information DB 310 as the ticket owner information.

The symmetric key exchange module 230 exchanges the symmetric key with the symmetric key decryption module 162 and transmits the ticket to the seller ticket 210. In the case where the ticket browsing request is received from the user management module 210 And transmits the symmetric key to the encryption / decryption module 240.

The seller ticket encryption / decryption module 240 includes a seller symmetric key exchange module 241, a symmetric key encryption module 242, and a server key decryption module 243. The server key decryption module 243 decrypts the ticket detail information encrypted with the server key from the encryption ticket DB 330. The ticket reading completion information is stored in the transaction information DB 310, whereby the seller A confirms that the buyer C has viewed the ticket and confirms the sale. And transmits the ticket detailed information encrypted by the symmetric key encrypting module 242 to the buyer symmetric key decrypting module 162 using the symmetric key received from the seller symmetric key exchange module 241. [ Symmetric key encryption / decryption schemes include, but are not limited to, DES, AES, and LEA.

The ticket refund module 250 receives the ticket refund request from the user management module 210, retrieves the ticket general information from the transaction information DB 310, and stores the ticket refund completion information in the transaction information DB 310. In addition, the buyer C transmits the refund information together with the ticket general information to the purchase ticket inquiry interface 120 so that the buyer C can confirm the refunded information. The refund information includes a message indicating that the refund has been completed. In addition, the refund target ticket general information may be deleted in the ticket transaction app 100 receiving the refund information.

The encryption DB 300 is a heterogeneous database that stores ticket related information in cooperation with the ticket transaction module 200 in the seller server 20 and includes a transaction information DB 310, a ticket information DB 320, And a DB 330.

The transaction information DB 310 stores ticket transaction information, ticket owner information, ticket reading completion information, and ticket refund completion information.

Ticket information DB 320 stores ticket general information.

In the encrypted ticket DB 330, the ticket detailed information is encrypted and stored. At this time, the encryption is performed using the server key.

Preferably, the information of each database is encrypted and stored to protect all data and transmission / reception paths.

The process 1100 of the purchaser C purchasing the ticket of the seller server 20 through the purchaser terminal 10 is as follows. (See FIG. 2)

(1101) transmitting a ticket purchase request received from the buyer (C) to the ticket transaction module (200) of the seller server (20) through the ticket transaction app (100) mounted on the buyer terminal (10);

(1102) storing transaction information according to a ticket purchase request transmitted to the ticket transaction module (200) in the transaction information DB (310) of the seller server (20);

(1103) requesting ticket issuance in the ticket transaction module (200) according to a ticket purchase request transmitted to the ticket transaction module (200);

(1104) from the ticket information DB (320) to the ticket transaction module (200) the general information of the ticket for which the ticket issuance is requested;

(1105) transmitting ticket general information from the ticket information DB 320 to the ticket transaction app 100 from the ticket transaction module 200;

And storing the owner information of the ticket request ticket in the transaction information DB 310 (1106).

The process 1200 of browsing the ticket purchased by the purchaser C through the purchaser terminal 10 at the step 1100 is as follows. (See FIG. 3)

That is, a step 1201 of requesting a digital signature of a buyer C who made a ticket browsing request through the ticket transaction app 100;

Transmitting (1202) an electronically signed ticket read request of the buyer (C) and a buyer ' s public key to the ticket transaction module (200);

A step 1203 of reading the ticket owner information from the transaction information DB 310 and decrypting the digitally signed ticket reading request with the public key to identify the ticket owner;

(1204) requesting ticket reading within the ticket transaction module (200) according to a decrypted ticket reading request when it is confirmed as a ticket owner;

A step 1205 of generating a symmetric key and exchanging a symmetric key with the ticket transaction app 100 when requesting ticket reading in the ticket transaction module 200;

A step 1206 of reading and decoding the ticket detailed information encrypted with the server key from the encryption ticket DB 330 to the ticket transaction module 200;

Encrypting the decrypted ticket detailed information using the symmetric key exchanged in step 1205 and stored in the ticket transaction module 200 (step 1207);

Transmitting the ticket detailed information encrypted in step 1207 to the ticket transaction app 100 (1208);

Storing ticket reading completion information in the transaction information DB 310 in the ticket transaction module 200 (1209);

Decrypting the encrypted ticket detailed information using the symmetric key exchanged in step 1205 and stored in the ticket transaction app 100 (step 1210);

And displaying the decoded browsing target ticket detailed information on the buyer terminal 10 (step 1211).

The process 1300 of refunding the ticket purchased by the purchaser C through the purchaser terminal 10 in step 1100 is as follows. (See FIG. 4)

That is, a step (1301) of requesting a digital signature of a buyer (C) who made a ticket refund request through the ticket transaction app (100);

Transmitting (1302) the electronically signed ticket refund request of the buyer (C) and the buyer ' s public key to the ticket transaction module (200);

Confirming whether or not the ticket reading completion information is stored in the transaction information DB 310 (1303);

(1304) requesting a ticket refund within the ticket transaction module (200) according to a ticket refund request transmitted to the ticket transaction module (200) when it is confirmed that refund is possible;

(1305) from the transaction information DB (310) to the ticket transaction module (200) the ticket general information of the ticket refund request target;

Storing the ticket refund completion information in the transaction information DB 310 in the ticket transaction module 200 (1306);

And transmitting the general information of the ticket to be refunded and the refund information from the ticket transaction module 200 to the ticket transaction app 100 (1307).

While the present invention has been described in connection with what is presently considered to be practical exemplary embodiments, it is to be understood that the invention is not limited to the disclosed embodiments, but, on the contrary, It will be clear to those who have knowledge.

100: Ticket trading app
110: Ticket purchase interface
120: Purchase Ticket Query Interface
130: Purchase ticket browsing interface
140: Request encryption module
141: Electronic signature module
160: Buyer ticket decryption module
161: Buyer symmetric key exchange module
162: Symmetric key decryption module
170: Purchase Ticket Refund Interface
200: Ticket transaction module
210: user management module
220: Ticket information transmission module
240: Seller Ticket Encryption Module
241: Merchant symmetric key exchange module
242: Symmetric key encryption module
243: Server key decryption module
250: Ticket Refund Module
300: Encryption DB
310: Transaction information DB
320: Ticket information DB
330: Encryption Ticket DB
10: Buyer terminal
20: Merchant Server
A: Ticket seller (seller)
B: Ticket issuer
C: Buyer

Claims (3)

A system in which a buyer terminal (10) on which a ticket transaction app (100) is mounted interacts with a seller server (20)

The ticket transaction app 100
A ticket purchase interface 110 for receiving a ticket purchase request from the buyer C and transmitting a ticket purchase request to the ticket transaction module 200,
A purchase ticket browsing interface 130 for receiving a ticket reading request from the purchaser C and transmitting an encryption request to the electronic signature module 140,
A purchase ticket refund interface 170 for receiving a ticket refund request from the buyer C and delivering an encryption request to the electronic signature module 140,
A ticket decryption module 160 for receiving and decrypting the encrypted ticket from the seller server 20,
A purchase ticket inquiry interface 120 for providing the buyer C with ticket general information transmitted from the seller server 20, ticket detail information received from the ticket decryption module 160, and ticket refund information received from the seller server 20, ),
The purchase ticket browsing interface 130 encrypts the ticket browsing request at the time of encryption request and transmits the ticket browsing request to the ticket transaction module 200. The purchase ticket refund interface 170 encrypts the ticket refund request at the time of encryption request, And a request encryption module (140)

The seller server (20)
A ticket transaction module 200 interlocked with the ticket transaction app 100 to transmit and receive ticket related requests and ticket related information,
And an encryption DB (300) interlocked with the ticket transaction module (200) and storing the ticket related information,

The ticket transaction module 200
Receives the ticket purchase request from the ticket purchasing interface 110, delivers the ticket issuance request to the ticket information transmission module 220, stores the transaction information in the encryption DB 300, Decrypts the ticket inquiry request, confirms the ticket owner information, delivers the decoded ticket reading request to the seller ticket encryption / decryption module 240, decrypts the encrypted ticket refund request received from the request encryption module 140, A purchasing user management module 210 for confirming a ticket and transmitting a decoded ticket refund request to the seller ticket encryption / decryption module 240,
Receives the ticket issuance request from the user management module 210, fetches the ticket general information from the encryption DB 300, transmits the ticket general information to the purchase ticket inquiry interface 120, and transmits the ticket information for storing the ticket owner information to the encryption DB 300 The modules 220,
A seller ticket arm that decrypts and decrypts the encrypted ticket detailed information from the encryption DB 300 and stores the ticket reading completion information in the encryption DB 300, encrypts the decrypted ticket detailed information, and transmits the encrypted ticket detailed information to the buyer ticket decryption module 160 Decryption module 240,
Receives the ticket refund request from the user management module 210, retrieves the ticket general information from the encryption DB 300, stores the ticket refund completion information in the encryption DB 300, and transmits the ticket general information and the ticket refund information to the purchase ticket inquiry interface 120 And a ticket refund module 250 for transmitting refund information together,

The encryption DB (300)
Transaction information DB 310 for storing transaction information, ticket owner information, ticket reading completion information and ticket refund completion information,
A ticket information DB 320 for storing ticket general information,
And an encrypted ticket DB 330 for encrypting and storing the ticket detailed information,

The ticket has no restriction on the validity period of use or is a long term,

The ticket general information is general information including the amount of the ticket,
The ticket detail information is information of a specific ticket necessary for use of the ticket,

When the use of a ticket is regarded as a prerequisite for viewing the ticket detailed information,

The buyer (C) can inquire only the general information of the ticket until the ticket reading request,
The purchaser C confirms the ticket detailed information at the time of ticket reading request, and at the same time, the ticket reading completion information is stored in the transaction information DB 310,
The ticket refund request is made possible only when the buyer (C) does not request the ticket reading
Mobile ticket transaction system.
delete delete

Images