KR20210015653A - Method and server for servicing online ticket based on blockchain network - Google Patents

Abstract

The present invention relates to a method for providing an online ticket service based on a blockchain network to prevent illegal ticket purchases using macros and the like and a server using the same. According to the present invention, the method comprises the following steps of a service server: (a) when ticket reservation information corresponding to a ticket purchased by a buyer is acquired from a ticket sales server, generating a ticket token corresponding to the ticket with reference to the ticket reservation information and registering generation information for the ticket token in a distributed ledger of a blockchain network, wherein the ticket reservation information includes at least one of usage information, usage condition information, user information, and seller information of a ticket; and (b) transmitting the ticket token to a seller token wallet corresponding to the seller of the ticket to allow the seller token wallet to transmit the ticket token to a user token wallet corresponding to a ticket user and registering movement information of the ticket token from the seller token wallet to the user token wallet in the distributed ledger of the blockchain network.

Description

How to service online tickets using a blockchain network, and a server using it {METHOD AND SERVER FOR SERVICING ONLINE TICKET BASED ON BLOCKCHAIN NETWORK}

The present invention relates to a method for servicing an online ticket using a blockchain network and a server using the same, and more specifically, a ticket token on a blockchain network by converting a ticket purchased by a user into a ticket token based on a blockchain network. It relates to a method of servicing an online ticket using a blockchain network that allows the management of the system and a server using the same.

In the case of ticket sales used for admission to performances, movie screenings, exhibitions, sports stadiums, amusement parks, etc., they are generally sold on-site or through reservation sales through the Internet.

In particular, as the economy and industry develop, people are interested in leisure life, and tickets used in cultural events go to designated reservations to purchase tickets or make reservations over the phone. It is widely used, and when purchasing a ticket through the Internet, there is an advantage in that it is possible to easily purchase a ticket without the inconvenience of visiting or calling.

However, recently, the act of purchasing tickets in large quantities using macro programs online and then reselling them to others at high prices is increasing, but there are insufficient regulations to prevent or prohibit such acts in advance. Accordingly, there is a problem that actual consumers cannot watch the performance or sport or pay excessively high prices for tickets.

In addition, online scalpels are mainly traded through cafes, apps, and ticket trading sites that trade used products, and small businesses sell them through social network services (SNS) such as Twitter.

However, although the act of buying and selling slogans on the spot is punished under the Minor Crime Penalty Act, there is no clear way to sanction online slogans transactions.

Ticket vendors and concert organizers are working in many ways to eradicate online scum.

As an example, there is a performance in which a procedure such as identification card verification is performed to eradicate black marks, but there is a problem that causes inconvenience to the audience.

In addition, a captcha, which is a mixture of English and numbers, is inserted in the middle of payment, so that a person must read and input it to proceed to the next step, thereby preventing mass purchases using macros, but causing inconvenience to actual purchasers.

In addition, in the conventional ticket sales method, the classic ticket issuing method such as on-site issuance and mail transmission is still prevalent, resulting in waste of resources and various disputes due to loss or damage of tickets.

In addition, in terms of use, due to the offline issuing service, there are many inconveniences in transferring, managing, holding, and presenting the right to use tickets.

In addition, in the conventional ticket sales method, the authenticity of the ticket cannot be verified unless the seller validates the ticket, so the purchaser is limited in exercising ownership of the ticket, and management of the authenticity of the ticket is not performed. There is opacity for ticket management.

In particular, in the case of tickets purchased through online ticket brokerage sites or personal transactions, it is not possible to verify the authenticity, and accordingly, damage due to forgery/forgery scams of tickets and delays in ticket delivery are occurring.

KR 10-1707812 B1

An object of the present invention is to solve all the above-described problems.

In addition, another object of the present invention is to prevent illegal ticket purchase using macros or the like.

In addition, another object of the present invention is to prevent user inconvenience due to a procedure such as identification card verification.

In addition, it is another object of the present invention to easily verify ownership and authenticity of a ticket.

In addition, another object of the present invention is to ensure transparency in ticket sales.

In addition, another object of the present invention is to prevent damage due to forgery/forgery fraud and delay in ticket delivery.

According to an embodiment of the present invention for achieving the above object, in a method of servicing an online ticket using a blockchain network, (a) ticket reservation information corresponding to a ticket purchased by a purchaser from a ticket sales server- The ticket reservation information includes at least one of the ticket usage information, the ticket usage condition information, the ticket user's user information, and the ticket seller information-when acquired, the service server stores the ticket reservation information Generating a ticket token corresponding to the ticket with reference, and registering generation information on the ticket token in a distributed ledger of a blockchain network; And (b) the service server transmits the ticket token to a merchant token wallet corresponding to the seller of the ticket, thereby causing the merchant token wallet to transmit the ticket token to a user token wallet corresponding to the ticket user, Registering movement information of the ticket token from the seller token wallet to the user token wallet in the distributed ledger of the blockchain network; A method comprising a is provided.

In the above, the user information is a user DID (decentralized identity) corresponding to the ticket user-the user DID is user identification information used in the blockchain network, the user DID and the ticket user corresponding to the user DID The ticket user's authentication information for personal information of is registered in the distributed ledger of the blockchain network, and the personal information of the ticket user is stored in the user terminal or DID data hub of the ticket user- Including, in the step (a), the service server, in response to the ticket reservation information, using the user DID, the ticket user's specific proof information for confirming the use condition information of the ticket to the user terminal And, when the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's specific proof information is It is possible to check whether the ticket usage condition information is satisfied, and generate the ticket token corresponding to the ticket when the specific proof information of the ticket user satisfies the ticket usage condition information.

In the above, the service server, when the ticket user's specific authentication information is obtained from the user terminal or the ticket user's specific authentication information is obtained from the DID data hub through an interaction with the user terminal, The user DID is used to check the authentication information of the ticket user registered in the distributed ledger of the blockchain network, and when the specific authentication information of the ticket user matches the authentication information of the ticket user, the specific authentication information of the ticket user is It can be confirmed that it is valid, and whether the specific proof information of the ticket user satisfies the use condition information of the ticket.

In the above, (c) a specific user terminal-the specific user terminal may be a user terminal of the ticket user or a third user terminal of a third user who obtained the ticket-corresponding to the request information for use of the ticket token from Thus, when the ticket token is transmitted to the token receiving wallet by the interaction with the ticket confirmation terminal, the service server refers to the movement information of the ticket token registered in the distributed ledger of the blockchain network in correspondence with the ticket token. It checks whether the ticket token is valid, and if it is confirmed that the ticket token is valid, it transmits approval information for the use of the ticket to the ticket confirmation terminal or the specific user terminal, and the ticket to the distributed ledger of the blockchain network. Registering token usage information; It may further include.

In the above, the service server destroys the ticket token stored in the token receipt wallet when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, and destroys the ticket token destruction information. It can be registered in the distributed ledger of the blockchain network.

In the above, the service server, when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, generates a collection token corresponding to the ticket token and transmits it to the specific user terminal, The generation information for the collection token can be registered in the distributed ledger of the blockchain network.

In the above, the ticket token usage request information is a specific user DID (decentralized identity) corresponding to a specific user who is the owner of the specific user terminal-The specific user DID is specific user identification information used in the blockchain network, and the The specific user DID and authentication information of the specific user for the personal information of the specific user corresponding to the specific user DID are registered in the distributed ledger of the blockchain network, and the personal information of the specific user is It is characterized in that it is stored in a user terminal or a DID data hub, and includes, and the service server uses the specific user DID to check the use condition information of the ticket to the specific user terminal. When specific authentication information is requested, and specific authentication information of the specific user is obtained from the specific user terminal or specific authentication information of the specific user is obtained from the DID data hub through an interaction with the specific user terminal, the specific user Check whether the specific proof information of the ticket reservation information satisfies the ticket usage condition information, and when the specific proof information of the specific user satisfies the ticket usage condition information, transmit the approval information for the use of the ticket I can.

In the above, the service server, when the specific authentication information of the specific user is obtained from the specific user terminal or through the interaction with the specific user terminal, the specific user DID of the specific user The authentication information of the specific user registered in the distributed ledger of the blockchain network is checked using, and when the specific authentication information of the specific user matches the authentication information of the specific user, the specific authentication information of the specific user is determined to be valid. After checking, it is possible to check whether the specific authentication information of the specific user satisfies the use condition information of the ticket.

In the above, when a refund request for the ticket token is obtained from (d) a specific user terminal-the specific user terminal may be a user terminal of the ticket user or a third user terminal of a third user who obtained the ticket, The service server checks whether the ticket token is valid by referring to movement information of the ticket token corresponding to the ticket token and registered on the distributed ledger of the blockchain network, and if the ticket token is confirmed to be valid, the ticket Sending a token from the specific user token wallet of the specific user to the token refund wallet, and registering the movement information of the ticket token from the specific user token wallet to the token refund wallet in the distributed ledger of the blockchain network, Transmitting the refund request information of the ticket token to the ticket sales server so that the ticket sales server makes a refund for the ticket corresponding to the ticket token; It may further include.

In addition, according to an embodiment of the present invention, in a method of servicing an online ticket using a blockchain network, (a) when a purchase request for a ticket by a purchaser is obtained, the ticket sales server is Requesting user information of a ticket user for purchasing the ticket; And (b) when the user information of the ticket user is obtained, the ticket sales server provides ticket reservation information corresponding to the ticket purchased by the purchaser.- The ticket reservation information includes the ticket usage information and the ticket use. By transmitting at least one of condition information, user information of the ticket user, and seller information of the ticket-to the service server, the service server generates a ticket token corresponding to the ticket by referring to the ticket reservation information And the process of registering the generation information of the ticket token on the distributed ledger of the blockchain network, and transmitting the ticket token to the seller token wallet corresponding to the seller of the ticket so that the seller token wallet A process for transmitting the ticket token to a user token wallet corresponding to the ticket user, and registering movement information of the ticket token from the seller token wallet to the user token wallet in the distributed ledger of the blockchain network. There is provided a method comprising; allowing to perform.

In the above, the user information of the ticket user is a user DID (decentralized identity) corresponding to the ticket user-The user DID is user identification information used in the blockchain network, and the user DID and the user DID The ticket user's authentication information about the ticket user's personal information is registered in the distributed ledger of the blockchain network, and the ticket user's personal information is stored in the ticket user's user terminal or DID data hub. -Includes, wherein the ticket sales server transmits the ticket reservation information to the service server, thereby causing the service server to use the ticket to the user terminal using the user DID in response to the ticket reservation information Request the ticket user's proof information for checking condition information, and the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof from the DID data hub through an interaction with the user terminal When the information is obtained, it is checked whether the specific proof information of the ticket user satisfies the usage condition information of the ticket, and when the specific proof information of the ticket user satisfies the usage condition information of the ticket, the corresponding to the ticket You can have it generate a ticket token.

In the above, the ticket seller server transmits the ticket reservation information to the service server, thereby causing the service server to obtain specific verification information of the ticket user from the user terminal or the DID data through an interaction with the user terminal. When the ticket user's specific proof information is obtained from the hub, the ticket user's user DID is used to check the ticket user's authentication information registered in the distributed ledger of the blockchain network, and the ticket user's specific proof information When is matched with the authentication information of the ticket user, it is possible to confirm that the specific authentication information of the ticket user is valid, and check whether the specific authentication information of the ticket user satisfies the use condition information of the ticket.

In the above, (c) refund request information for the ticket from the service server-The refund request for the ticket is generated by the service server, and a specific user terminal-the specific user terminal is the user terminal of the ticket user or the May be the third user terminal of the third user who obtained the ticket-In response to the request for refund of the ticket token from, movement information of the ticket token registered in the distributed ledger of the blockchain network in correspondence with the ticket token Check whether the ticket token is valid with reference, and if the ticket token is confirmed to be valid, the ticket token is transferred from the specific user token wallet of the specific user to the token refund wallet, and the token from the specific user token wallet It is generated after registering the movement information of the ticket token to the refund wallet in the distributed ledger of the blockchain network.If is obtained, the ticket sales server provides a refund for the ticket to the ticket user corresponding to the ticket. Giving step; It may further include.

In addition, according to an embodiment of the present invention, there is provided a service server for servicing an online ticket using a blockchain network, comprising: a memory storing instructions for providing an online ticket service for a ticket purchased by a purchaser; And a processor configured to generate a ticket token corresponding to a ticket purchased by a purchaser in response to the instructions stored in the memory to provide an online ticket service. Including, the processor, (i) ticket reservation information corresponding to the ticket purchased by the purchaser from the ticket sales server-The ticket reservation information is the ticket usage information, the ticket usage condition information, the user of the ticket user Including at least one of information and seller information of the ticket-when is obtained, a ticket token corresponding to the ticket is generated by referring to the ticket reservation information, and the generated information on the ticket token is distributed in the blockchain network. The process of registering with the ledger, and (ii) sending the ticket token to the merchant token wallet corresponding to the seller of the ticket, causing the merchant token wallet to transmit the ticket token to the user token wallet corresponding to the ticket user. , A service server performing a process of registering movement information of the ticket token from the seller token wallet to the user token wallet of the ticket token in the distributed ledger of the blockchain network is provided.

In the above, the user information is a user DID (decentralized identity) corresponding to the ticket user-the user DID is user identification information used in the blockchain network, the user DID and the ticket user corresponding to the user DID The ticket user's authentication information for personal information of is registered in the distributed ledger of the blockchain network, and the personal information of the ticket user is stored in the user terminal or DID data hub of the ticket user- Including, wherein the processor, in the (i) process, in response to the ticket reservation information, using the user DID to the user terminal for specific verification information of the ticket user for confirming the use condition information of the ticket Request, and when the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's specific proof information It is possible to check whether the ticket usage condition information is satisfied, and when the specific proof information of the ticket user satisfies the ticket usage condition information, the ticket token corresponding to the ticket may be generated.

In the above, the processor, when the ticket user's specific authentication information is obtained from the user terminal or the ticket user's specific authentication information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's user Check the authentication information of the ticket user registered in the distributed ledger of the blockchain network using DID, and if the specific authentication information of the ticket user matches the authentication information of the ticket user, the specific authentication information of the ticket user is valid. It can be confirmed that the ticket user's specific proof information satisfies the ticket usage condition information.

In the above, the processor, (iii) use of the ticket token from a specific user terminal-the specific user terminal may be the user terminal of the ticket user or a third user terminal of the third user who obtained the ticket- When the ticket token is transmitted to the token receiving wallet by interaction with the ticket confirmation terminal in response to the request information, the ticket token corresponds to the ticket token and refers to the movement information of the ticket token registered in the distributed ledger of the blockchain network. Checks whether the ticket token is valid, and if it is confirmed that the ticket token is valid, it transmits approval information for the use of the ticket to the ticket confirmation terminal or the specific user terminal, and the ticket token to the distributed ledger of the blockchain network. You can further perform the process of registering the usage information.

In the above, the processor destroys the ticket token stored in the token receiving wallet when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, and the ticket token destruction information It can be registered on the distributed ledger of the blockchain network.

In the above, the processor, when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, generates a collection token corresponding to the ticket token and transmits it to the specific user terminal, and the Generation information for the collection token can be registered in the distributed ledger of the blockchain network.

In the above, the ticket token usage request information is a specific user DID (decentralized identity) corresponding to a specific user who is the owner of the specific user terminal-The specific user DID is specific user identification information used in the blockchain network, and the The specific user DID and authentication information of the specific user for the personal information of the specific user corresponding to the specific user DID are registered in the distributed ledger of the blockchain network, and the personal information of the specific user is It is characterized in that it is stored in a user terminal or a DID data hub-includes, and the processor, by using the specific user DID, to identify the specific user to check the usage condition information of the ticket to the specific user terminal When the verification information is requested, and when the specific verification information of the specific user is obtained from the specific user terminal or the specific verification information of the specific user is obtained from the DID data hub through the interaction with the specific user terminal, It is possible to check whether specific proof information satisfies the ticket usage condition information of the ticket reservation information, and transmit approval information for the use of the ticket when the specific proof information of the specific user satisfies the ticket usage condition information. have.

In the above, the processor, when the specific authentication information of the specific user is obtained from the specific user terminal or the specific authentication information of the specific user is obtained from the DID data hub through the interaction with the specific user terminal, the specific user Check the authentication information of the specific user registered on the distributed ledger of the blockchain network using the specific user DID of, and when the specific authentication information of the specific user matches the authentication information of the specific user, the specific authentication of the specific user It is possible to confirm that the information is valid, and check whether the specific authentication information of the specific user satisfies the use condition information of the ticket.

In the above, the processor may request a refund of the ticket token from (iv) a specific user terminal-the specific user terminal may be a user terminal of the ticket user or a third user terminal of a third user who obtained the ticket. When is obtained, it checks whether the ticket token is valid by referring to the movement information of the ticket token registered in the distributed ledger of the blockchain network in correspondence with the ticket token, and if the ticket token is confirmed to be valid, the ticket token To be transmitted from the specific user token wallet of the specific user to the token refund wallet, and register movement information of the ticket token from the specific user token wallet to the token refund wallet in the distributed ledger of the blockchain network, and the By transmitting the refund request information of the ticket token to the ticket sales server, the process of causing the ticket sales server to refund the ticket corresponding to the ticket token may be further performed.

In addition, according to an embodiment of the present invention, there is provided a ticket sales server for servicing an online ticket using a blockchain network, comprising: a memory for storing instructions for ticket sales; And a processor that performs an operation for selling tickets in response to the instructions stored in the memory. Including, the processor, (i) when the purchase request for the ticket by the purchaser is obtained, the process of requesting the user information of the ticket user for the purchase of the ticket to the purchaser terminal of the purchaser, and (ii) ( ii-1) When the user information of the ticket user is obtained, ticket reservation information corresponding to the ticket purchased by the purchaser-The ticket reservation information includes the ticket usage information, the ticket usage condition information, the ticket user Including at least one of user information and seller information of the ticket-is transmitted to the service server to cause the service server to generate a ticket token corresponding to the ticket by referring to the ticket reservation information, and the ticket token Register the generated information on the distributed ledger of the blockchain network, and (ii-2) transmit the ticket token to the seller token wallet corresponding to the seller of the ticket, so that the seller token wallet transfers the ticket token to the ticket user. A ticket that performs a process of transmitting information to the user token wallet corresponding to the user token wallet, and registering movement information of the ticket token from the seller token wallet to the user token wallet in the distributed ledger of the blockchain network A sales server is provided.

In the above, the user information of the ticket user is a user DID (decentralized identity) corresponding to the ticket user-The user DID is user identification information used in the blockchain network, and the user DID and the user DID The ticket user's authentication information about the ticket user's personal information is registered in the distributed ledger of the blockchain network, and the ticket user's personal information is stored in the ticket user's user terminal or DID data hub. -Includes, wherein the processor transmits the ticket reservation information to the service server, thereby causing the service server to send the ticket reservation information to the user terminal using the user DID. The ticket user's proof information is requested to confirm, and the ticket user's specific proof information is obtained from the user terminal, or the ticket user's specific proof information is received from the DID data hub through an interaction with the user terminal. When obtained, it is checked whether the specific proof information of the ticket user satisfies the use condition information of the ticket, and when the specific proof information of the ticket user satisfies the use condition information of the ticket, the ticket token corresponding to the ticket Can be created.

In the above, the processor transmits the ticket reservation information to the service server to cause the service server to obtain specific authentication information of the ticket user from the user terminal or from the DID data hub through an interaction with the user terminal. When the ticket user's specific proof information is obtained, the ticket user's user DID is used to check the ticket user's authentication information registered in the distributed ledger of the blockchain network, and the ticket user's specific proof information If the ticket user's authentication information is matched, it is possible to confirm that the ticket user's specific authentication information is valid, and whether the ticket user's specific authentication information satisfies the ticket usage condition information.

In the above, the processor, (iii) refund request information for the ticket from the service server-the refund request for the ticket is generated by the service server, and the specific user terminal-the specific user terminal May be a user terminal or a third user terminal of the third user who obtained the ticket-In response to a request for a refund of the ticket token from, the ticket token corresponding to the ticket token and registered in the distributed ledger of the blockchain network Check whether the ticket token is valid with reference to the movement information of, and if the ticket token is confirmed to be valid, the ticket token is transferred from the specific user token wallet of the specific user to the token refund wallet, and the specific user token wallet It is generated after registering the movement information of the ticket token from the token refund wallet to the distributed ledger of the blockchain network-When is obtained, a refund for the ticket is given to the ticket user corresponding to the ticket. The process can be performed further.

In addition to this, a computer-readable recording medium for recording a computer program for executing the method of the present invention is further provided.

According to the present invention, the following effects are obtained.

The present invention can prevent illegal ticket purchase using macros or the like by providing a ticket service using a block chain network.

In the present invention, by using a decentralized identity (DID) of a blockchain network to identify a user, it is possible to prevent user inconvenience due to procedures such as identification card verification.

In the present invention, it is possible to easily verify the ownership and authenticity of a ticket by managing a ticket using a blockchain network.

In the present invention, it is possible to secure transparency for ticket sales by managing tickets using a blockchain network.

The present invention can be distributed regardless of region by issuing and distributing tickets using a blockchain network, and it is possible to secure the reliability of the secondary resale market.

In the present invention, by managing the ticket token corresponding to the ticket using a blockchain network, it is possible to prevent damage due to forgery/forgery fraud and delay in ticket delivery.

1 schematically shows a system for servicing an online ticket using a blockchain network according to an embodiment of the present invention,
FIG. 2 schematically illustrates a method of issuing a ticket token in a method of servicing an online ticket using a blockchain network according to an embodiment of the present invention.
3 schematically shows a method of using a ticket token in a method of servicing an online ticket using a blockchain network according to an embodiment of the present invention,
4 schematically shows a method of destroying and refunding ticket tokens in a method of servicing an online ticket using a blockchain network according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION The detailed description of the present invention to be described later refers to the accompanying drawings, which illustrate specific embodiments in which the present invention may be practiced. These embodiments are described in detail sufficient to enable a person skilled in the art to practice the present invention. It is to be understood that the various embodiments of the present invention are different from each other, but need not be mutually exclusive. For example, specific shapes, structures, and characteristics described herein may be implemented in other embodiments without departing from the spirit and scope of the present invention in relation to one embodiment. In addition, it is to be understood that the location or arrangement of individual components within each disclosed embodiment may be changed without departing from the spirit and scope of the present invention. Accordingly, the detailed description to be described below is not intended to be taken in a limiting sense, and the scope of the present invention, if appropriately described, is limited only by the appended claims, along with all ranges equivalent to those claimed by the claims. Like reference numerals in the drawings refer to the same or similar functions over several aspects.

Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings in order to enable those of ordinary skill in the art to easily implement the present invention.

1 schematically illustrates a system for servicing an online ticket using a block chain network according to an embodiment of the present invention. Referring to FIG. 1, the system includes a user terminal 110, a seller terminal 120, and It may include a ticket sales server 200, and a service server 300.

First, the user terminal 110 manages user personal information and uses a ticket, and may include a personal computer (PC), a mobile computer, a PDA/EDA, a mobile phone, a smartphone, a tablet, an IoT device, and the like. Further, the user terminal 110 is not limited thereto, and may include all devices such as a portable game machine, a digital camera, and a personal navigation system having a wired or wireless communication function. In addition, the user terminal 110 may include a memory that stores user personal information and instructions for using a ticket, and a processor that performs an operation for using a ticket in response to the instructions stored in the memory. At this time, the user terminal 110 may be a purchaser terminal of a purchaser who purchases a ticket or a user terminal of a ticket user to use a ticket. That is, the buyer can designate the ticket user as himself or another user.

Meanwhile, the user terminal 110 may store information corresponding to the user's user decentralized identity (DID). At this time, the user DID is user identification information used in the blockchain network 400, and the user's authentication information for the user DID and the user's personal information corresponding to the user DID is registered in the distributed ledger of the blockchain network 400. The user's personal information may be stored in the user's user terminal 110 or a DID data hub. And, the user's personal information may be stored as proof information corresponding to the authentication information. In this case, the DID data hub may store data requested by a user, and allow only the user or a third user authorized by the user to access the data.

In addition, the user terminal 110 may include a user token wallet capable of storing a ticket token related to a ticket.

Next, the seller terminal 120 is a subject for ticket sales, and may include a personal computer (PC), a mobile computer, a PDA/EDA, a mobile phone, a smartphone, a tablet, an IoT device, and a server. Further, the user terminal 110 is not limited thereto, and may include all devices such as a portable game machine, a digital camera, and a personal navigation system having a wired or wireless communication function. In addition, the seller terminal 110 may include a memory for storing personal information of the seller and instructions for selling tickets, and a processor for performing an operation for selling tickets in response to the instructions stored in the memory. In this case, only one seller terminal 120 is shown in FIG. 1, but this is for convenience of explanation, and the seller terminal 120 may be formed of a plurality of units corresponding to each seller.

Meanwhile, the seller terminal 120 may store information corresponding to the user's seller decentralized identity (DID). At this time, the seller DID is the seller identification information used in the blockchain network 400, and the seller's authentication information on the seller's DID and the seller's personal information corresponding to the seller DID is registered in the distributed ledger of the blockchain network 400. And, the seller's personal information may be stored in the seller's seller terminal 120. And, the seller's personal information may be stored as proof information corresponding to the authentication information.

In addition, the seller terminal 110 may include a seller token wallet capable of storing a ticket token related to a ticket. Alternatively, the merchant token wallet may be included in the service server 300.

Next, the ticket sales server 200 performs an operation related to ticket sales, and performs an operation for ticket sales in response to the instructions stored in the memory 210 and the memory 210 storing instructions for ticket sales. It may include a processor 220 to perform.

Specifically, the ticket vending server 200 is typically a computing device (e.g., a device that may include components of a computer processor, memory, storage, input and output devices, and other conventional computing devices; routers, switches, etc.). Electronic communication devices; electronic information storage systems such as network attached storage (NAS) and storage area networks (SAN)) and computer software (i.e., instructions that allow the computing device to function in a specific way). It may be to achieve system performance.

In addition, the processor of the computing device may include a hardware configuration such as a micro processing unit (MPU) or a central processing unit (CPU), a cache memory, and a data bus. In addition, the computing device may further include an operating system and a software configuration of an application that performs a specific purpose.

Next, the service server 300 provides an online ticket service for the ticket purchased by the user, and generates a ticket token corresponding to the ticket purchased by the user, and stores instructions for providing the online ticket service ( 310) and instructions stored in the memory 310 may include a processor 320 that generates a ticket token corresponding to a ticket purchased by the user to provide an online ticket service.

Specifically, the service server 300 is typically a computing device (e.g., a device that may include components of a computer processor, memory, storage, input and output devices, and other existing computing devices; electronic devices such as routers, switches, etc. Communication device; desired system using a combination of electronic information storage systems such as network attached storage (NAS) and storage area networks (SAN)) and computer software (i.e., instructions that make the computing device function in a specific way) It may be to achieve performance.

In addition, the processor of the computing device may include a hardware configuration such as a micro processing unit (MPU) or a central processing unit (CPU), a cache memory, and a data bus. In addition, the computing device may further include an operating system and a software configuration of an application that performs a specific purpose.

In the system for servicing an online ticket using a blockchain network according to an embodiment of the present invention configured as described above, the service server 300 corresponds to a ticket purchased by a purchaser from the ticket sales server 200, When ticket reservation information including at least one of ticket usage information, ticket usage condition information, ticket user user information, and ticket seller information is obtained, a ticket token corresponding to the ticket is generated by referring to the ticket reservation information, and , Registers the generated information on the ticket token in the distributed ledger of the blockchain network 400, and the service server 300 transmits the ticket token to the seller token wallet corresponding to the seller of the ticket, so that the seller ticket the ticket token. Transfer information to the user token wallet corresponding to the user, and register the transfer information of the ticket token from the seller token wallet to the user token wallet on the distributed ledger of the blockchain network.

In addition, the ticket sales server 200, when a purchase request for a ticket by a purchaser is obtained, requests user information of a ticket user for purchasing a ticket as a purchaser of the purchaser, and when the ticket user information is obtained, the purchaser By transmitting ticket reservation information corresponding to the ticket purchased by the service server 300, the service server 300 generates a ticket token corresponding to the ticket by referring to the ticket reservation information, and generation information on the ticket token The process of registering the token on the distributed ledger of the blockchain network 400, and sending the ticket token to the merchant token wallet corresponding to the seller of the ticket, allows the seller to transmit the ticket token to the user token wallet corresponding to the ticket user, It is possible to perform a process of registering movement information of the ticket token from the seller token wallet of the ticket token to the user token wallet in the distributed ledger of the blockchain network 400.

A method of servicing an online ticket using a system for servicing an online ticket using a blockchain network according to an embodiment of the present invention configured as described above will be described as follows.

A method of issuing a ticket token in a method of servicing an online ticket using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 2.

When the seller requests the ticket sales registration for the ticket to be sold through the seller terminal 120 (S1), the ticket sales server 200 registers the ticket to be sold requested by the seller to purchase the ticket desired by the user. Make it possible.

In this case, the ticket may be to provide the authority to use concerts, plays, musicals, sports, leisure, exhibitions/events, amusement parks, seminars, accommodation facilities, and the like. In addition, the ticket is not limited thereto, and may include all documents for verifying the user's authority and ownership, such as gift certificates, participation certificates, tickets, purchase certificates, and certificates that recognize certain qualifications to participate in specific competitions. In addition, tickets include industrial property rights such as patent rights, utility model rights, trademark rights, and design rights, franchise, goodwill, mining rights, which are rights to manufacture or sell products or services exclusively and exclusively within a specific region. All documents to verify the user's rights and ownership of intangible assets such as fishing rights, copyrights and licenses may be included.

Thereafter, when the user purchases a desired ticket (S11) while accessing the ticket sales server 200 using the user terminal 110, the ticket sales server 200 reserves a ticket corresponding to the ticket purchased by the user. The information is generated and transmitted to the service server 300 (S12).

In this case, the ticket reservation information may include at least one of ticket use information, ticket use condition information, ticket user information, and ticket seller information. In addition, the ticket usage information may include event information, event location and time information, and ticket information about the event corresponding to the ticket, but is not limited thereto, and includes all information on the ticket and the event corresponding to the ticket. can do. In addition, the ticket usage condition information may include paid or free condition information of the ticket, user condition information that can use the ticket, validity period of the ticket, ticket grade information, and the like. In this case, the user condition information may include condition information of a user who can use the ticket, such as the user's gender, age, and region. In addition, the user information of the ticket user may include information related to a user who intends to use the ticket, such as a user DID, a user token wallet address, and a purchase quantity. In addition, the seller information may include information related to the seller, such as a seller token wallet address, a seller token cancellation wallet address, a seller token refund wallet address, a seller token destruction wallet address, and seller event information.

Then, the service server 300 creates a ticket token corresponding to the ticket by referring to the ticket reservation information (S13), and transmits the generated information on the ticket token to the blockchain network 400 (S14) 400) registers the ticket token generation information in the distributed ledger of the blockchain network 400 (S15). At this time, the service server 300 may be a block chain node constituting the block chain network 400, and the service server 300 registers ticket token generation information in its own distributed ledger so that the block chain network 400 Ticket token generation information can be registered on the distributed ledger of

In this case, the service server 300 may check whether the ticket user satisfies the ticket usage condition information by using the user DID.

That is, the user DID is user identification information used in the blockchain network 400, and the authentication information of the ticket user for the user DID and personal information of the ticket user corresponding to the user DID is distributed in the blockchain network 400. Registered in the ledger, and the personal information of the ticket user is stored in the user terminal 110 or the DID data hub of the ticket user, the service server 300 uses the user DID in response to the ticket reservation information. (110) Requests specific proof information of the ticket user to check the ticket usage condition information, and specific proof information of the ticket user is obtained from the user terminal 110 or DID data through an interaction with the user terminal 110 When the ticket user's specific proof information is obtained from the hub, it checks whether the ticket user's specific proof information satisfies the ticket usage condition information, and responds to the ticket when the ticket user's specific proof information satisfies the ticket usage condition Ticket tokens can be generated.

At this time, the service server 300 obtains the ticket user's specific proof information from the user terminal 110 or the ticket user's specific proof information from the DID data hub through the interaction with the user terminal 110, The user DID is used to check the authentication information of the ticket user registered in the distributed ledger of the blockchain network 400, and if the specific authentication information of the ticket user matches the authentication information of the ticket user, the specific authentication information of the ticket user is considered valid. In addition, it is possible to check whether the ticket user's specific proof information satisfies the ticket usage condition information.

For example, if the ticket usage condition information is a condition related to the age of the ticket user, the service server 300 uses the user terminal 110 to provide specific proof information that allows the ticket user to prove the age condition, which is the ticket usage condition information. When requesting, the ticket user uses the user DID to provide specific proof information that can prove age, that is, specific proof information that has been authenticated by a certification authority for the user's age without disclosing other personal information or age of the user. (300), and the service server 300 checks whether the specific authentication information obtained from the user terminal 110 or the DID data hub matches the authentication information registered in the blockchain network, so that the specific authentication information of the user is valid. If the user's specific proof information is valid, it is possible to check whether the user's age information, which is verified by the specific proof information, matches the age condition, which is the usage condition information of the ticket.

And, the service server 300 transmits the generated ticket token to the seller token wallet corresponding to the seller, so that the seller token wallet transmits the ticket token to the user token wallet corresponding to the ticket user, and the seller token of the ticket token The movement information from the wallet to the user token wallet is registered in the distributed ledger of the blockchain network 400.

As an example, the service server 300 transmits the generated ticket token to the seller terminal 120 (S16) so that the ticket token is stored in the seller token wallet generated in the seller terminal 120, and the blockchain network ( 400), the current owner of the ticket token is registered as the seller. In addition, the seller transmits the ticket token to the user terminal 110 of the ticket token user (S17) so that the ticket token is stored in the user token wallet generated in the user terminal 110, and the blockchain network 400 Registers in the distributed ledger that the owner of the ticket token has changed from seller to user.

At this time, unlike the seller token wallet generated in the seller terminal 120, the seller token wallet may be created in the service server 300. In this case, the service server 300 uses the generated ticket token as a seller token. It can be stored in the wallet, and the merchant token wallet can transmit the ticket token to the user token wallet by an algorithm such as a smart contract.

In addition, in the above, the ticket token corresponding to the purchased ticket was received through the user terminal 110, but in contrast, the purchaser may set the ticket user as another user so that the ticket token is transmitted to the user terminal of the ticket user. . That is, the purchaser of the ticket may set the user of the ticket as the purchaser himself or as a third user for a gift or the like.

A method of using a ticket token in a method of servicing an online ticket using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 3.

In order for a specific user who owns the ticket to use the ticket, a specific user terminal 110-1 requests the use of the ticket token to the ticket confirmation terminal 210 (S21).

In this case, the specific user terminal 110-1 may be a purchaser terminal for purchasing a ticket or a user terminal of a ticket user designated as a ticket user by a purchase request from the purchaser. Also, the specific user terminal 110-1 may be a third user terminal of a third user who acquires and owns a ticket token through a transaction with a ticket token holder. At this time, the ownership may be changed through the transaction of the ticket token, and the ownership change information of the ticket token may be registered in the distributed ledger of the blockchain network 400. In addition, when the ownership of the ticket token is changed, the service server or the smart contract of the blockchain network checks whether the third user matches the ticket usage condition information using the third user DID of the third user who has transferred the ownership of the ticket token. By checking, you can allow or prohibit the transfer of ownership. In addition, the ticket confirmation terminal 210 may include any computing device capable of performing an interaction with a user terminal, such as a kiosk or scanner installed at the event location.

In addition, the ticket confirmation terminal 210 displays a token receiving wallet address for receiving a ticket token for use of the ticket token and requests to transmit the ticket token owned by the ticket user to the token receiving wallet (S22). Then, the ticket user transmits the token stored in the user token wallet to the token receiving wallet through the specific user terminal 110-1 (S23) so that the ticket token is transmitted to the seller terminal 120.

At this time, it has been described that the token receiving wallet is generated in the seller terminal 120, but unlike this, the token receiving wallet may be generated in the service server 300, and accordingly, transmitted from a specific user terminal 110-1. The token ticket may be transmitted to the service server 300.

Thereafter, when the ticket token is transmitted from the user token wallet of the specific user terminal 110-1 to the token receiving wallet (S24), the service server 300 corresponds to the ticket token and registers it in the distributed ledger of the blockchain network 400 Checking whether the ticket token is valid by referring to the movement information of the ticket token (S25).

At this time, the service server 300 checks whether the ticket token has been issued normally, that is, has not been forged, by referring to the movement information of the ticket token, or checks whether a specific user has ownership of the ticket token, or It is possible to check whether it has been illegally distributed by a method such as this scalpel.

In addition, the service server 300 may check whether a specific user satisfies the ticket usage condition information by using the specific user DID, which is information included in the ticket token usage request.

That is, the service server 300 requests specific authentication information of a specific user to check the ticket usage condition information to the specific user terminal 110-1 using the specific user DID, and the specific user terminal 100-1 When specific authentication information of a specific user is obtained from the DID data hub or through an interaction with a specific user terminal 100-1, specific authentication information of a specific user is obtained from the ticket reservation information. It is possible to check whether the usage condition information is satisfied, and when the specific proof information of a specific user satisfies the usage condition information of the ticket, approval information for the use of the ticket can be transmitted.

At this time, the service server 300 obtains specific authentication information of a specific user from a specific user terminal 100-1 or obtains specific authentication information of a specific user from the DID data hub through interaction with the specific user terminal 100-1. When obtained, the authentication information of a specific user registered in the distributed ledger of the blockchain network 400 is checked using the specific user DID of a specific user, and when the specific authentication information of a specific user matches the authentication information of a specific user, a specific user It is possible to confirm that the specific authentication information of a specific user is valid, and whether the specific authentication information of a specific user satisfies the usage condition information of the ticket.

And, if the service server 300 checks whether the ticket token is valid and it is confirmed that it is valid, the service server 300 transmits (S26) approval information for the use of the ticket to the ticket confirmation terminal 210 or a specific user terminal 110-1. Allows users to perform events, and registers ticket token usage information on the distributed ledger of the blockchain network 400 to prevent duplicate use of ticket tokens, or prevent illegal distribution of used ticket tokens. To prevent it.

In addition, the service server 300 generates a collection token corresponding to the ticket token when the confirmation information on the approval information from the ticket confirmation terminal 210 or the specific user terminal 110-1 is obtained, and the specific user terminal 110 -1), and the generation information for the collection token can be registered in the distributed ledger of the blockchain network. That is, the service server 300 may provide the ticket user with a collection token of inverse benefit according to the use of the ticket token. For example, when an event corresponding to a ticket token is an artist's performance, a collection token related to the artist may be provided to users participating in the performance.

In addition, the service server 300 destroys the ticket token stored in the token receiving wallet when the confirmation information on the approval information from the ticket confirmation terminal 210 or a specific user terminal 110-1 is obtained, and destroys the ticket token. Information can be registered in the distributed ledger of the blockchain network 400. The destruction of ticket tokens will be described in more detail below.

A method of destroying and refunding a ticket token in a method of servicing an online ticket using a blockchain network according to an embodiment of the present invention will be described with reference to FIG. 4.

When the ticket token is used in the same manner as in FIG. 3 and the ticket token is transmitted to the ticket receiving wallet to satisfy the conditions for destroying the ticket token, or a ticket token destruction request (S31) from the seller terminal 120 is obtained, the service The server 300 may destroy the ticket token and register the ticket token destruction information in the distributed ledger of the blockchain network 400 (S32) (S33).

In addition, the conditions for destroying the ticket token can be set in various ways, even when the service server 300 monitors the movement information of the ticket token so that the ticket token is illegally circulated or the validity period of the ticket token expires. Ticket tokens can be destroyed by the above method.

At this time, the service server 300 checks the history information on the ticket token requested for destruction on the distributed ledger of the blockchain network 400 to check whether the ticket token requested for destruction is valid, and uses the entity DID of the entity requesting destruction. It is possible to check whether the entity requesting destruction has legitimate ownership of the ticket token requested for destruction.

In addition, in response to a ticket token refund request from a specific user terminal 100-1 owning the ticket token, the service server 300 may perform a refund for the ticket token.

That is, when a ticket token refund request (S41) is obtained from a specific user terminal 110-1 or a ticket token refund request is obtained from the seller terminal 120, the service server 300 corresponds to the ticket token and Check whether the ticket token is valid by referring to the movement information of the ticket token registered in the distributed ledger of (400). And, if the ticket token is verified to be valid, the ticket token is transferred from the specific user token wallet of the specific user to the token refund wallet, and the transfer information of the ticket token from the specific user token wallet to the token refund wallet is transferred to the blockchain network ( 400) is registered in the distributed ledger (S42) (S43).

At this time, the service server 300 checks the history information on the ticket token requested for the refund on the distributed ledger of the blockchain network 400 to check whether the ticket token requested for the refund is valid, and uses the entity DID of the entity requesting the refund. It is possible to check whether the entity requesting the refund has legitimate ownership of the ticket token for which the refund was requested.

And, the service server 300 transmits (S44) the refund request information of the ticket token to the ticket sale server 200, so that the ticket sale server 200 makes a refund (S45) for the ticket corresponding to the ticket token. Can be lost.

On the other hand, in the above, the issuance, use, destruction, refund, etc. of ticket tokens have been described through the interaction between the service server and the seller terminal, but unlike this, the service server may create and own token wallets related to the seller, and the ticket token It is also possible to implement interactions according to issuance, use, destruction, refund, etc. of a smart contract.

Further, the embodiments according to the present invention described above may be implemented in the form of program instructions that can be executed through various computer components and recorded in a computer-readable recording medium. The computer-readable recording medium may include program instructions, data files, data structures, etc. alone or in combination. The program instructions recorded on the computer-readable recording medium may be specially designed and configured for the present invention, or may be known and usable to those skilled in the computer software field. Examples of computer-readable recording media include magnetic media such as hard disks, floppy disks, and magnetic tapes, optical recording media such as CD-ROMs and DVDs, magnetic-optical media such as floptical disks. media), and a hardware device specially configured to store and execute program instructions such as ROM, RAM, flash memory, and the like. Examples of the program instructions include not only machine language codes such as those produced by a compiler, but also high-level language codes that can be executed by a computer using an interpreter or the like. The hardware device may be configured to operate as one or more software modules to perform processing according to the present invention, and vice versa.

In the above, the present invention has been described by specific matters such as specific elements and limited embodiments and drawings, but this is provided only to help a more general understanding of the present invention, and the present invention is not limited to the above embodiments. , Anyone with ordinary knowledge in the technical field to which the present invention pertains can make various modifications and variations from these descriptions.

Therefore, the spirit of the present invention is limited to the above-described embodiments and should not be defined, and all modifications that are equally or equivalent to the claims as well as the claims to be described later fall within the scope of the spirit of the present invention. I would say.

110: user terminal,
110-1: specific user terminal
120: seller terminal,
200: ticket sales server,
300: service server,
400: Blockchain network

Claims (26)

In the method of servicing online tickets using a blockchain network,
(a) Ticket reservation information corresponding to the ticket purchased by the purchaser from the ticket sales server-The ticket reservation information includes the ticket usage information, the ticket usage condition information, the ticket user's user information, and the ticket seller information Including at least one of-When is obtained, the service server generates a ticket token corresponding to the ticket by referring to the ticket reservation information, and registers the generation information on the ticket token in the distributed ledger of the blockchain network. step; And
(b) the service server transmits the ticket token to a merchant token wallet corresponding to the seller of the ticket, causing the merchant token wallet to transmit the ticket token to a user token wallet corresponding to the ticket user, and the Registering movement information of the ticket token from the merchant token wallet to the user token wallet in a distributed ledger of the blockchain network;
How to include. The method of claim 1,
The user information is a user DID (decentralized identity) corresponding to the ticket user-The user DID is user identification information used in the blockchain network, and the user DID and personal information of the ticket user corresponding to the user DID The ticket user's authentication information is registered in the distributed ledger of the blockchain network, and the personal information of the ticket user is stored in the user terminal or DID data hub of the ticket user. ,
In the step (a), the service server requests specific verification information of the ticket user to check the usage condition information of the ticket from the user terminal using the user DID in response to the ticket reservation information, When the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's specific proof information is used for the ticket. A method of checking whether condition information is satisfied, and generating the ticket token corresponding to the ticket when the specific proof information of the ticket user satisfies the use condition information of the ticket. The method of claim 2,
The service server, when the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's user DID The ticket user's authentication information registered in the distributed ledger of the blockchain network is checked using, and if the ticket user's specific authentication information matches the ticket user's authentication information, it is confirmed that the ticket user's specific authentication information is valid. And confirming whether the specific proof information of the ticket user satisfies the use condition information of the ticket. The method of claim 1,
(c) Specific user terminal-The specific user terminal may be the user terminal of the ticket user or the third user terminal of the third user who obtained the ticket-Check the ticket in response to the request information for use of the ticket token from When the ticket token is transmitted to the token receiving wallet by interaction with the terminal, the service server refers to the movement information of the ticket token registered in the distributed ledger of the blockchain network in correspondence with the ticket token, and the ticket token Is valid, and if the ticket token is confirmed to be valid, it transmits approval information for the use of the ticket to the ticket confirmation terminal or the specific user terminal, and the use of the ticket token on the distributed ledger of the blockchain network Registering information;
How to further include. The method of claim 4,
The service server destroys the ticket token stored in the token receipt wallet when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, and the ticket token destruction information is stored in the blockchain. How to register on the network's distributed ledger. The method of claim 4,
The service server generates a collection token corresponding to the ticket token and transmits it to the specific user terminal when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, and the collection token How to register the generated information for the blockchain network in the distributed ledger. The method of claim 4,
The ticket token usage request information is a specific user DID (decentralized identity) corresponding to a specific user who is the owner of the specific user terminal-The specific user DID is specific user identification information used in the blockchain network, and the specific user DID And authentication information of the specific user for the personal information of the specific user corresponding to the specific user DID is registered in the distributed ledger of the blockchain network, and the personal information of the specific user is a specific user terminal of the specific user or It is characterized in that it is stored in the DID data hub-includes,
The service server uses the specific user DID to request specific authentication information of the specific user to check the usage condition information of the ticket from the specific user terminal, and specific authentication information of the specific user from the specific user terminal When is obtained or the specific proof information of the specific user is obtained from the DID data hub through the interaction with the specific user terminal, it is determined whether the specific proof information of the specific user satisfies the ticket usage condition information of the ticket reservation information. A method of confirming and transmitting approval information for use of the ticket when the specific proof information of the specific user satisfies the use condition information of the ticket. The method of claim 7,
When the specific authentication information of the specific user is obtained from the specific user terminal or the specific authentication information of the specific user is obtained from the DID data hub through the interaction with the specific user terminal, the service server The user DID is used to check the authentication information of the specific user registered in the distributed ledger of the blockchain network, and when the specific authentication information of the specific user matches the authentication information of the specific user, the specific authentication information of the specific user is A method of confirming that it is valid, and confirming whether the specific proof information of the specific user satisfies the use condition information of the ticket. The method of claim 1,
(d) a specific user terminal-the specific user terminal may be a user terminal of the ticket user or a third user terminal of a third user who obtained the ticket-when a refund request for the ticket token is obtained from the service server A, check whether the ticket token is valid by referring to the movement information of the ticket token corresponding to the ticket token and registered in the distributed ledger of the blockchain network, and if the ticket token is confirmed to be valid, the ticket token is Transfer information from a specific user token wallet to a token refund wallet of a specific user, and register the transfer information of the ticket token from the specific user token wallet to the token refund wallet in the distributed ledger of the blockchain network, and sell the ticket Transmitting the refund request information of the ticket token to a server so that the ticket sales server makes a refund for the ticket corresponding to the ticket token;
How to further include. In the method of servicing online tickets using a blockchain network,
(a) when a purchase request for a ticket is obtained by a purchaser, the ticket sales server requests user information of a ticket user for purchase of the ticket to a purchaser terminal of the purchaser; And
(b) When the user information of the ticket user is obtained, the ticket sales server provides ticket reservation information corresponding to the ticket purchased by the purchaser-The ticket reservation information is the ticket use information, the ticket use condition Including at least one of information, user information of the ticket user, and seller information of the ticket-to the service server to generate a ticket token corresponding to the ticket by referring to the ticket reservation information And, the process of registering the generation information of the ticket token on the distributed ledger of the blockchain network, and by transmitting the ticket token to the merchant token wallet corresponding to the seller of the ticket, the seller token wallet sends the ticket token to the Performs a process to transmit information on the movement of the ticket token from the seller token wallet to the user token wallet in the distributed ledger of the blockchain network to transmit the ticket token to the user token wallet corresponding to the ticket user A step to do;
How to include. The method of claim 10,
The user information of the ticket user is a user DID (decentralized identity) corresponding to the ticket user-The user DID is user identification information used in the blockchain network, the user DID and the ticket user corresponding to the user DID The ticket user's authentication information for personal information of is registered in the distributed ledger of the blockchain network, and the personal information of the ticket user is stored in the user terminal or DID data hub of the ticket user- Including,
The ticket sales server transmits the ticket reservation information to the service server, thereby causing the service server to check the use condition information of the ticket with the user terminal using the user DID in response to the ticket reservation information. When the ticket user's proof information is requested, and if the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket A method of checking whether a user's specific proof information satisfies the ticket usage condition information, and generating the ticket token corresponding to the ticket when the ticket user's specific proof information satisfies the ticket usage condition information . The method of claim 11,
The ticket seller server, by transmitting the ticket reservation information to the service server, causes the service server to obtain specific verification information of the ticket user from the user terminal or from the DID data hub through an interaction with the user terminal. When the ticket user's specific proof information is obtained, the ticket user's user DID is used to check the ticket user's authentication information registered in the distributed ledger of the blockchain network, and the ticket user's specific proof information is the ticket When matching with the user's authentication information, it is confirmed that the specific authentication information of the ticket user is valid, and the method of checking whether the specific authentication information of the ticket user satisfies the use condition information of the ticket. The method of claim 10,
(c) Refund request information for the ticket from the service server-The refund request for the ticket is generated by the service server, and a specific user terminal-The specific user terminal obtains the ticket user's user terminal or the ticket It may be a third user terminal of a third user-In response to a request for a refund of the ticket token from, referring to the movement information of the ticket token registered in the distributed ledger of the blockchain network in response to the ticket token Checks whether the ticket token is valid, and if the ticket token is verified to be valid, the ticket token is transferred from the specific user token wallet of the specific user to the token refund wallet, and from the specific user token wallet to the token refund wallet It is generated after registering the movement information of the ticket token in the distributed ledger of the blockchain network-if is obtained, the ticket sales server refunding the ticket to the ticket user corresponding to the ticket ;
How to further include. In a service server that serves online tickets using a blockchain network,
A memory for storing instructions for providing an online ticket service for a ticket purchased by a buyer; And
A processor for generating a ticket token corresponding to a ticket purchased by a purchaser in response to the instructions stored in the memory to provide an online ticket service; Including,
The processor,
(i) Ticket reservation information corresponding to the ticket purchased by the purchaser from the ticket sales server-The ticket reservation information includes the ticket usage information, the ticket usage condition information, the ticket user's user information, and the ticket seller information Including at least one of-is obtained, the process of generating a ticket token corresponding to the ticket by referring to the ticket reservation information, and registering the generation information on the ticket token in the distributed ledger of the blockchain network, and ( ii) by transmitting the ticket token to the merchant token wallet corresponding to the seller of the ticket, causing the merchant token wallet to transmit the ticket token to the user token wallet corresponding to the ticket user, and the merchant token of the ticket token A service server that performs a process of registering movement information of the ticket token from the wallet to the user token wallet in the distributed ledger of the blockchain network. The method of claim 14,
The user information is a user DID (decentralized identity) corresponding to the ticket user-The user DID is user identification information used in the blockchain network, and the user DID and personal information of the ticket user corresponding to the user DID The ticket user's authentication information is registered in the distributed ledger of the blockchain network, and the personal information of the ticket user is stored in the user terminal or DID data hub of the ticket user. ,
The processor, in the (i) process, requests specific verification information of the ticket user to check the usage condition information of the ticket from the user terminal using the user DID in response to the ticket reservation information, and the When the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's specific proof information is the ticket usage condition A service server that checks whether the information is satisfied, and generates the ticket token corresponding to the ticket when the specific authentication information of the ticket user satisfies the use condition information of the ticket. The method of claim 15,
The processor uses the ticket user's user DID when the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal. The ticket user's authentication information registered in the distributed ledger of the blockchain network is checked, and if the ticket user's specific authentication information matches the ticket user's authentication information, the ticket user's specific authentication information is confirmed to be valid. And a service server that checks whether the specific proof information of the ticket user satisfies the use condition information of the ticket. The method of claim 14,
The processor,
(iii) Specific user terminal-The specific user terminal may be the user terminal of the ticket user or the third user terminal of the third user who obtained the ticket-Check the ticket in response to the request information for use of the ticket token from When the ticket token is transmitted to the token-receiving wallet by interaction with the terminal, the ticket token corresponds to the ticket token and checks whether the ticket token is valid by referring to movement information of the ticket token registered in the distributed ledger of the blockchain network. , If the ticket token is confirmed to be valid, the process of transmitting approval information for the use of the ticket to the ticket confirmation terminal or the specific user terminal, and registering the use information of the ticket token in the distributed ledger of the blockchain network The service server to perform more. The method of claim 17,
The processor destroys the ticket token stored in the token receipt wallet when the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, and sends the ticket token destruction information to the blockchain network. A service server that registers with the distributed ledger of The method of claim 17,
When the confirmation information on the authorization information from the ticket confirmation terminal or the specific user terminal is obtained, the processor generates a collection token corresponding to the ticket token and transmits it to the specific user terminal, and the collection token A service server that registers the generated information on the blockchain network in the distributed ledger. The method of claim 17,
The ticket token usage request information is a specific user DID (decentralized identity) corresponding to a specific user who is the owner of the specific user terminal-The specific user DID is specific user identification information used in the blockchain network, and the specific user DID And authentication information of the specific user for the personal information of the specific user corresponding to the specific user DID is registered in the distributed ledger of the blockchain network, and the personal information of the specific user is a specific user terminal of the specific user or It is characterized in that it is stored in the DID data hub-includes,
The processor uses the specific user DID to request specific authentication information of the specific user to check the usage condition information of the ticket from the specific user terminal, and specific authentication information of the specific user is received from the specific user terminal. When the specific authentication information of the specific user is obtained or obtained from the DID data hub through the interaction with the specific user terminal, it is checked whether the specific authentication information of the specific user satisfies the ticket usage condition information of the ticket reservation information And, when the specific authentication information of the specific user satisfies the use condition information of the ticket, the service server transmitting approval information for the use of the ticket. The method of claim 20,
When the specific authentication information of the specific user is obtained from the specific user terminal or the specific authentication information of the specific user is obtained from the DID data hub through the interaction with the specific user terminal, the specific user of the specific user The authentication information of the specific user registered in the distributed ledger of the blockchain network is checked using DID, and when the specific authentication information of the specific user matches the authentication information of the specific user, the specific authentication information of the specific user is valid. The service server confirms that it is, and checks whether the specific authentication information of the specific user satisfies the use condition information of the ticket. The method of claim 14,
The processor,
(iv) a specific user terminal-the specific user terminal may be a user terminal of the ticket user or a third user terminal of a third user who obtained the ticket-when a refund request for the ticket token is obtained from the ticket token Corresponding to and referring to the movement information of the ticket token registered in the distributed ledger of the blockchain network, it checks whether the ticket token is valid. Transfer information from the token wallet to the token refund wallet, and register the movement information of the ticket token from the specific user token wallet to the token refund wallet in the distributed ledger of the blockchain network, and the ticket token to the ticket sales server The service server further performs a process of causing the ticket sales server to refund the ticket corresponding to the ticket token by transmitting the refund request information of the ticket. In a ticket sales server that provides online tickets using a blockchain network,
A memory for storing instructions for selling tickets; And
A processor that performs an operation for selling tickets in response to the instructions stored in the memory; Including,
The processor,
(i) When a purchase request for a ticket by a purchaser is obtained, a process of requesting user information of a ticket user for purchasing the ticket to the purchaser terminal of the purchaser, and (ii) (ii-1) the ticket user When user information is obtained, ticket reservation information corresponding to the ticket purchased by the purchaser-The ticket reservation information includes the ticket usage information, the ticket usage condition information, the ticket user's user information, and the ticket. By transmitting at least one of the seller information-to the service server, the service server refers to the ticket reservation information to generate a ticket token corresponding to the ticket, and the generation information on the ticket token is transmitted to the blockchain network. And (ii-2) the seller token wallet transmits the ticket token to the user token wallet corresponding to the ticket user by sending the ticket token to the seller token wallet corresponding to the seller of the ticket. And registering the movement information of the ticket token from the merchant token wallet to the user token wallet in the distributed ledger of the blockchain network. The method of claim 23,
The user information of the ticket user is a user DID (decentralized identity) corresponding to the ticket user-The user DID is user identification information used in the blockchain network, the user DID and the ticket user corresponding to the user DID The ticket user's authentication information for personal information of is registered in the distributed ledger of the blockchain network, and the personal information of the ticket user is stored in the user terminal or DID data hub of the ticket user- Including,
The processor, by transmitting the ticket reservation information to the service server, causes the service server to check the ticket usage condition information with the user terminal using the user DID in response to the ticket reservation information. When the ticket user's specific proof information is obtained from the user terminal or the ticket user's specific proof information is obtained from the DID data hub through an interaction with the user terminal, the ticket user's Ticket sales server that checks whether specific proof information satisfies the use condition information of the ticket, and generates the ticket token corresponding to the ticket when the specific proof information of the ticket user satisfies the use condition information of the ticket . The method of claim 24,
The processor, by transmitting the ticket reservation information to the service server, causes the service server to obtain specific authentication information of the ticket user from the user terminal, or the ticket user from the DID data hub through an interaction with the user terminal. When specific proof information of is obtained, the ticket user's user DID is used to check the ticket user's authentication information registered in the distributed ledger of the blockchain network, and the ticket user's specific proof information is If the authentication information is matched, the ticket sales server confirms that the specific authentication information of the ticket user is valid, and checks whether the specific authentication information of the ticket user satisfies the use condition information of the ticket. The method of claim 23,
The processor,
(iii) Refund request information for the ticket from the service server-The refund request for the ticket is generated by the service server, and a specific user terminal-The specific user terminal obtains the ticket user's user terminal or the ticket It may be a third user terminal of a third user-In response to a request for a refund of the ticket token from, referring to the movement information of the ticket token registered in the distributed ledger of the blockchain network in response to the ticket token Checks whether the ticket token is valid, and if the ticket token is verified to be valid, the ticket token is transferred from the specific user token wallet of the specific user to the token refund wallet, and from the specific user token wallet to the token refund wallet It is generated after registering the movement information of the ticket token in the distributed ledger of the blockchain network-When is obtained, ticket sales that further performs a process of refunding the ticket to the ticket user corresponding to the ticket server.

Images