Method for checking electronic ticket authenticated by user terminal and system using same

Abstract

The present invention provides a method for checking an electronic ticket by comparing user terminal information at a ticket issuing time and a ticket checking time, and a system using the same. A ticket checking method of an electronic ticket according to an embodiment of the present invention comprises the steps of: receiving first terminal information and a ticket issuing request signal from a user terminal; generating ticket information corresponding to the ticket issuing request signal, and sending an electronic ticket corresponding to the ticket information to the user terminal; receiving ticket information and second terminal information from a ticket checking device; identifying first terminal information corresponding to the received ticket information; and authenticating the electronic ticket based on the identity of the identified first terminal information and second terminal information received from the ticket checking device.

Description

Technical Field

[0001] The present invention relates to a method for checking electronic tickets by comparing user terminal information at ticket issuing time and ticket checking time and a system using the method. Background Art

[0002] Paper tickets used to enter facilities such as museums, galleries, performance venues and stadiums are being converted to electronic tickets for the convenience of users. However, as physical tickets are converted to digital tickets, problems such as counterfeit tickets, stolen tickets, and illegal transfer of tickets have also emerged.

[0003] In order to prevent this situation, a method of personal authentication by checking the customer's ID card or face at the ticket inspection point of the electronic ticket has recently begun to be used. However, this method has the limitation that additional manpower is required for personal identity authentication, and there is a problem that the accuracy of personal authentication cannot be guaranteed by visual inspection of the ID card and face.

[0004] Therefore, there is a need for a ticket checking method that selectively allows only customers who actually purchased electronic tickets to enter a facility.

[0005] Prior art literature

[0006] Patent Literature

[0007] (Patent Document 0001) Korean Patent Publication No. 10-2020-0141891 (December 21, 2020) Summary of the invention

[0008] Technical problem to be solved by the invention

[0009] The object of the present invention is to check the electronic ticket by comparing the user terminal information at the time of ticket issuance and the time of ticket checking.

[0010] The purpose of the present invention is not limited to the above purpose, and other purposes and advantages of the present invention not mentioned can be understood through the following description, and will be more clearly understood through the embodiments of the present invention. And, it is obvious that the purposes and advantages of the present invention can be achieved by the means and combinations thereof defined in the claims.

[0011] Technical solutions to solve problems

[0012] To achieve the above-mentioned purpose, a method for checking electronic tickets according to an embodiment of the present invention includes the following steps: receiving first terminal information and a ticket issuance request signal from a user terminal; generating ticket information corresponding to the ticket issuance request signal, and sending an electronic ticket corresponding to the ticket information to the user terminal; receiving ticket information and second terminal information from a ticket checking device; identifying the first terminal information corresponding to the received ticket information; and authenticating the electronic ticket based on the sameness of the identified first terminal information and the second terminal information received from the ticket checking device.

[0013] In one embodiment, the electronic ticket is a barcode, a QR code, a near-field communication (NFC) ticket, or a non-fungible token (NFT) ticket.

[0014] In one embodiment, the step of receiving the first terminal information and the ticket issuance request signal comprises the following steps: receiving the ticket issuance request signal from the user terminal; sending a terminal information request signal to the user terminal; and receiving the first terminal information from the user terminal.

[0015] In one embodiment, the step of sending the electronic ticket to the user terminal includes the following steps: generating ticket information corresponding to the ticket request signal; storing the generated ticket information and the received first terminal information in a database in a one-to-one correspondence; and generating an electronic ticket including the generated ticket information and sending it to the user terminal.

[0016] In one embodiment, the step of receiving the ticket information and the second terminal information comprises the following steps: receiving the ticket information of the electronic ticket tagged with the ticket checking device and the second terminal information of the user terminal tagged with the ticket checking device.

[0017] In one embodiment, the first terminal information and the second terminal information include a unique ID that is set differently for each user terminal.

[0018] In one embodiment, the first terminal information and the second terminal information include at least one of a MAC address, an International Mobile Equipment Identity (IMEI), a Unique Device Identifier (UDID), a Universally Unique Identifier (UUID), and an Advertising Identifier (ADID).

[0019] In one embodiment, the step of authenticating the electronic ticket includes the following steps: if the first terminal information is the same as the second terminal information, it is determined that the authentication of the electronic ticket is successful.

[0020] In one embodiment, the step of authenticating the electronic ticket includes the following steps: when the first terminal information is the same as the second terminal information, receiving the terminal location from the user terminal that touches the ticket checking device; and if the distance between the terminal location and the location of the ticket checking device is within a preset distance, determining that the authentication of the electronic ticket is successful.

[0021] In one embodiment, the step of authenticating the electronic ticket includes the following steps: when the first terminal information is the same as the second terminal information, receiving the terminal location from the user terminal that touches the ticket checking device; and if the distance between the terminal location and the location of the viewing facility corresponding to the electronic ticket is within a preset distance, determining that the authentication of the electronic ticket is successful.

[0022] In one embodiment, the following steps are also included: receiving a re-issue request signal for the electronic ticket from a user terminal; in response to the re-issue request signal, deleting the first terminal information stored corresponding to the ticket information of the electronic ticket from a database; re-receiving the first terminal information from the user terminal; storing the ticket information of the electronic ticket and the re-received first terminal information in a one-to-one correspondence in the database; and sending the electronic ticket to the user terminal.

[0023] To achieve the above-mentioned purpose, an electronic ticket checking system according to an embodiment of the present invention includes: a server; a ticket checking device, used to send touch information to the server; a ticket issuing target terminal, used to receive the electronic ticket from the server; and the ticket checking target terminal, used to touch the electronic ticket with the ticket checking device, the server authenticates the electronic ticket based on the sameness of the first terminal information received from the ticket issuing target terminal and the second terminal information collected by touching with the ticket checking device.

[0024] In one embodiment, the ticket issuing target terminal sends the first terminal information and the ticket issuing request signal to the server, the server generates ticket information in response to the ticket issuing request signal, and sends the electronic ticket corresponding to the ticket information to the ticket issuing target terminal, the ticket checking device sends the ticket information and the second terminal information collected by touching the ticket checking target terminal to the server, the server identifies the first terminal information corresponding to the ticket information received from the ticket checking device, and authenticates the electronic ticket based on the sameness of the identified first terminal information and the second terminal information received from the ticket checking device.

[0025] Effects of the Invention

[0026] The present invention checks the electronic ticket by comparing the user terminal information at the time of ticket issuance and the time of ticket checking, and only customers who actually purchased the electronic ticket can be selectively allowed to enter the facility without the need for additional personnel to authenticate whether they are users who meet the regulations.

[0027] In addition to the above-mentioned effects, specific effects of the present invention will be described below in the detailed description. BRIEF DESCRIPTION OF THE DRAWINGS

[0028] Figure 1 FIG. 1 is a diagram showing an electronic ticket checking system according to an embodiment of the present invention.

[0029] Figure 2 FIG. 4 is a flow chart of a method for checking an electronic ticket according to an embodiment of the present invention.

[0030] Figure 3 A flow chart of a process for determining successful authentication of an electronic ticket for a compliant user.

[0031] Figure 4 A flow chart of a process for determining authentication failure of an electronic ticket for a non-compliant user.

[0032] Figure 5 Flow chart of a process for determining successful authentication of an electronic ticket when changing a user terminal. DETAILED DESCRIPTION

[0033] The above objects, features and advantages will be described in detail later with reference to the accompanying drawings so that those skilled in the art can easily implement the technical ideas of the present invention. When describing the present invention, if it is determined that a detailed description of the known technology related to the present invention may be unnecessary and obscure the main purpose of the present invention, the detailed description will be omitted. Below, the preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. In the accompanying drawings, the same reference numerals are used to represent the same or similar components.

[0034] In this specification, "first", "second", etc. are used to describe various components, but of course, these components are not limited to these terms. These terms are only used to distinguish one component from another component, and unless explicitly stated otherwise, the first component can also be the second component.

[0035] Furthermore, in this specification, any component being "on (or below)" or "above (or below)" a component means that any component can be in contact with the upper (or lower) portion of the component, and other components can be inserted between the component and the component disposed above (or below) the component.

[0036] Also, in this specification, when a component is described as being “connected,” “coupled,” or “combined” to another component, the components can be directly connected or combined, or other components can be “inserted” between the components, or the components can be “connected,” “coupled,” or “combined” through other components.

[0037] Furthermore, singular expressions used herein include plural expressions unless the context clearly indicates otherwise. In the present invention, terms such as "consisting of" or "comprising" should not be interpreted as necessarily including all the various components or steps described in the specification, and some components or steps may or may not be included, or may include additional components or steps.

[0038] Also, in this specification, when "A and / or B" is mentioned, unless otherwise specified, it means A, B, or A and B, and when "C to D" is mentioned, unless otherwise specified, it means the reference, indicating C or more and D or less.

[0039] The present invention relates to a method for checking electronic tickets by comparing user terminal information at the time of ticket issuance and the time of ticket checking, and a system using the same. Figures 1 to 5 A method and system for checking an electronic ticket according to an embodiment of the present invention will be described in detail.

[0040] Figure 1 1 is a diagram showing a ticket checking system for an electronic ticket according to an embodiment of the present invention. Figure 2 4 is a flow chart of a method for checking an electronic ticket according to an embodiment of the present invention.

[0041] Figure 3 A flowchart of a process for determining successful authentication of an electronic ticket for a qualified user, Figure 4 A flow chart of a process for determining authentication failure of an electronic ticket for a non-compliant user.

[0042] on the other hand, Figure 5 Flow chart of a process for determining successful authentication of an electronic ticket when changing a user terminal.

[0043] refer to Figure 1 According to an embodiment of the present invention, the electronic ticket checking system 1 can include a server 10, a user terminal 20 and a ticket checking device 30. However, Figure 1 The electronic ticket checking system 1 shown is according to one embodiment, and the multiple components constituting the electronic ticket checking system 1 are not limited to Figure 1 The embodiments shown are described below, and some components can be added, changed or deleted as needed.

[0044] The server 10 can provide a reservation / ticketing service for tickets for entering musicals, plays, museums, art galleries, performance venues, stadiums, and other facilities. Such a server 10 can be implemented as an online platform and can be accessed through a website via a wireless network. The server 10 can run a dedicated application for providing a reservation / ticketing service for tickets, and when the dedicated application is run on the user terminal 20, the touch information based on the electronic ticket is collected from the user terminal 20 and sent to the ticket checking device 30. In the operations described below, the operations performed by the server 10 and the user terminal 20 can refer to operations performed by the dedicated application.

[0045] The user terminal 20 is any device that can receive an electronic ticket by communicating with the server 10. The user terminal 20 can be equipped with a tagging function so as to wirelessly send the ticket information of the electronic ticket to the ticket checking device 30 described later.

[0046] On the other hand, the user terminal 20 described in this specification does not mean a specific terminal, but includes a ticket issuing target terminal 20 that issues an electronic ticket as needed and a ticket checking target terminal 20 that comes into contact with the ticket checking device 30.

[0047] The ticket checking device 30 can be any device installed in a facility where an electronic ticket can be used for admission, and can touch the electronic ticket and send the touching information to the server 10. Such a ticket checking device 30 can be linked to the ticket gate system, and can open the ticket gate when it is determined that the authentication of the electronic ticket is successful, and close the ticket gate when it is determined that the authentication of the electronic ticket fails.

[0048] The electronic ticket checking method described below can be executed by the above-mentioned server 10. To this end, the server 10 can include at least one physical element of application specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs, digital signal processing devices), PLDs (programmable logic devices), field programmable gate arrays (FPGAs, field programmable gate arrays), controllers (controller), micro-controllers (micro-controllers), processors (processor), and microprocessors (microprocessors).

[0049] refer to Figure 2According to an embodiment of the present invention, a method for checking an electronic ticket may include the following steps: receiving first terminal information and a ticket request signal from a user terminal 20 (S10); generating ticket information in response to the ticket request signal (S20); sending an electronic ticket corresponding to the ticket information to the user terminal 20 (S30); receiving the ticket information and the second terminal information from the ticket checking device 30 (S40); identifying the first terminal information corresponding to the received ticket information (S50); and authenticating the electronic ticket based on the identity of the first terminal information and the second terminal information (S60).

[0050] However, Figure 2 The electronic ticket checking method shown is based on an embodiment, and the multiple steps constituting the present invention are not limited to Figure 2 The embodiments shown are described below, and some steps can be added, modified or deleted as needed.

[0051] Below, detailed description Figure 2 The steps shown.

[0052] The server 10 can receive the first terminal information and the ticket issuance request signal from the user terminal 20 (ie, the ticket issuance target terminal 20) (S10).

[0053] For example, the user can access the server 10 through his terminal and send a ticket request signal corresponding to the ticket to be issued to the server 10. On the other hand, the first terminal information can be sent to the server 10 in response to the signal requested by the server 10 without a separate command from the user.

[0054] As an example, refer to Figure 3 , the ticket issuing target terminal 20 can send a ticket issuing request signal to the server 10 (S210). The server 10 that receives the ticket issuing request signal can send a terminal information request signal to the ticket issuing target terminal 20 (S110). According to the terminal information request signal, the ticket issuing target terminal 20 can output an interface for confirming whether to agree to send the terminal information, and when the user inputs an agreement command through the corresponding interface, the ticket issuing target terminal 20 can send the first terminal information to the server 10 (S220).

[0055] On the other hand, the terminal information described in the present invention can include a unique ID that is set differently for each user terminal 20, for example, it can include at least one of a MAC address, an international mobile equipment identity code IMEI (International Mobile Equipment Identity), a device unique identifier UDID (Unique Device Identifier), a universally unique identifier UUID (Universally Unique Identifier), and an advertising identifier ADID (Advertising Identifier). In addition, the terminal information can also include any identification information specific to the user terminal 20.

[0056] In one embodiment, the ticket issuing target terminal 20 can further confirm the first identity information of the user of the ticket issuing target terminal 20 in addition to the first terminal information according to the terminal information request signal and send it to the server 10. The identity information can include the first identity confirmation number (CI, Connection Information) or the first identity authentication information of the mobile certificate based on the user of the ticket issuing target terminal 20. In addition, the identity information can also include any identification information unique to the user.

[0057] Thereafter, the server 10 can generate ticket information corresponding to the ticket issuance request signal ( S20 ).

[0058] The ticket information may include various information required for entering facilities such as musicals, plays, museums, art galleries, performance venues, and stadiums (hereinafter, viewing facilities), such as the ticket usage location, validity period, price, seats, etc. Such ticket information may be generated in the form of data.

[0059] After generating the ticket information, the server 10 can store the corresponding ticket information and the first terminal information received in step S10 in an internal database in a one-to-one correspondence. This storage operation can be performed on all user terminals 20 that send ticket request signals, so that the data stored in the database can have a structure representation of a look-up table (LUT) as shown in Table 1 below.

[0060] Table 1

[0061] No. Ticket Information(t) First terminal information (ID) 1 <![CDATA[t1]]> <![CDATA[ID1]]> 2 <![CDATA[t2]]> <![CDATA[ID2]]> 3 <![CDATA[t3]]> <![CDATA[ID3]]> ... ... ... n <![CDATA[t n ]]> <![CDATA[ID n ]]>

[0062] In one embodiment, after generating the ticket information, the server 10 can store the corresponding ticket information (t), the first terminal information (ID) and the first identity information (UID) in a database in a one-to-one correspondence with a lookup table structure.

[0063] Afterwards, the server 10 can generate an electronic ticket corresponding to the ticket information and send it to the user terminal 20 (ie, the ticket issuing target terminal 20) (S30).

[0064] An electronic ticket is a ticket stored in the ticket issuing target terminal 20 in the form of data, and can include part or all of the above-mentioned ticket information. This electronic ticket can be implemented as a barcode or QR code displayed by the display of the user terminal 20, and can also be implemented as a near field communication NFC (Near Field Communication) ticket or a non-fungible token NFT (Non-Fungible Token) ticket that is not displayed on the display but sent and received through a unique communication protocol. In addition, electronic tickets can also take a variety of forms that can be implemented in related technical fields.

[0065] On the other hand, although not shown in the figure, in the process from step S10 to step S30, a signal for paying for the ticket can be sent and received between the server 10 and the ticket issuing target terminal 20.

[0066] After that, the server 10 can receive the ticket information and the second terminal information from the ticket checking device 30 (S40). At this time, the second terminal information can be the terminal information of the user terminal 20 as the ticket checking target, that is, the ticket checking target terminal 20.

[0067] As described above, after the electronic ticket is transmitted to the user terminal 20, the user can enter in a state of holding the user terminal 20 and tag the electronic ticket to the ticket checking device 30 installed at the entrance of the viewing facility.

[0068] When the electronic ticket is touched, the ticket checking device 30 can read the ticket information contained in the corresponding electronic ticket and simultaneously obtain the second terminal information of the ticket checking target terminal 20 through short-range wireless communication. In other words, the user can make the ticket checking device 30 collect the ticket information and the second terminal information corresponding to the electronic ticket respectively by touching the ticket checking target terminal 20 to the ticket checking device 30.

[0069] In one embodiment, when the electronic ticket is touched, the ticket checking device 30 can obtain the second identity information of the user of the ticket checking target terminal 20 in addition to the ticket information and the second terminal information. In one embodiment, as a prerequisite operation for the ticket checking target terminal 20 to allow the electronic ticket to be touched to the ticket checking device 30, the ticket checking target terminal 20 runs a dedicated application to prepare for the touching of the electronic ticket, and the server 10 can enable the ticket checking target terminal 20 to obtain the second identity authentication information based on the second identity confirmation number (CI) of the user of the ticket checking target terminal 20 or a mobile certificate (for example, Naver / Kakao certificate, etc.) as the second identity identification information. At this time, the server 10 can set the dedicated application to: when the user of the ticket checking target terminal 20 does not perform the authentication process of the identity confirmation number (CI) or does not perform the authentication process using the mobile certificate, the electronic ticket touch information is not sent to the ticket checking device 30.

[0070] The ticket checking device 30 can send the ticket information and the second terminal information collected by the touch operation to the server 10, and the server 10 can identify the first terminal information corresponding to the ticket information received from the ticket checking device 30 (S50). That is, the server 10 can identify which terminal issued the electronic ticket for the ticket information read in the ticket checking device 30.

[0071] Specifically, in the example of Table 1 above, when the ticket information received in the ticket checking device 30 is t2, the server 10 can refer to the database to identify the first terminal information corresponding to t2 as ID2. In other words, the server 10 can confirm that the electronic ticket with the ticket information of t2 is issued from the user terminal 20 with the terminal information of ID2.

[0072] In one embodiment, the server 10 can obtain the second identity identification information from the ticket checking target terminal 20 in the process of obtaining the second identity identification information from the ticket checking device 30 or touching the electronic ticket through a dedicated application.

[0073] After that, the server 10 can authenticate the electronic ticket based on the identity of the first terminal information identified in step S50 and the second terminal information received from the ticket checking device 30 in step S40. That is, the server 10 can authenticate the electronic ticket by comparing the terminal information of the ticket issuing target terminal 20 that sends the electronic ticket and the terminal information of the ticket checking target terminal 20 that touches the electronic ticket.

[0074] Specifically, when the first terminal information of the ticket issuing target terminal 20 identified when issuing an electronic ticket corresponding to specific ticket information is the same as the second terminal information of the ticket checking target terminal 20 identified when checking the electronic ticket, the server 10 can judge that the ticket issuing target terminal 20 and the ticket checking target terminal 20 are the same user terminal 20, and determine that the authentication of the electronic ticket is successful.

[0075] In one embodiment, the server 10 can identify the first identity information corresponding to the ticket information received from the ticket checking device 30, and authenticate the electronic ticket based on the sameness of the first identity information and the second identity information. Specifically, when the first identity information of the ticket issuing target terminal 20 identified when issuing the electronic ticket corresponding to the specific ticket information is the same as the second identity information of the ticket checking target terminal 20 identified when checking the electronic ticket, the server 10 can determine that the ticket issuing target terminal 20 and the ticket checking target terminal 20 are the same user terminal 20, and determine that the authentication of the electronic ticket is successful.

[0076] In one embodiment, the server 10 can determine that the ticket issuing target terminal 20 and the ticket checking target terminal 20 are the same user terminal 20 when the first terminal information and the second terminal information are the same and the first identity identification information and the second identity identification information are the same, and determine that the authentication of the electronic ticket is successful.

[0077] In one embodiment, even if it is determined that the ticket issuing target terminal 20 and the ticket checking target terminal 20 are the same user terminal 20, after determining that the authentication of the electronic ticket is successful, the server 10 can ultimately authenticate the user of the user terminal 20 before entering the place where the electronic ticket is used to obtain a third identity identification information (for example, a third identity confirmation number (CI) or a third identity authentication information). When the first identity identification number, the second identity identification number and the third identity identification number are all the same, admission is allowed through the electronic ticket.

[0078] In the following instructions, get terminal information and determine whether the same operation can also be applied to Figure 2 The operation of obtaining identity identification information and determining whether they are the same.

[0079] In the following, reference Figure 3 Detailed description of an example of determining that authentication of an electronic ticket is successful when the ticket issuing target terminal 20 and the ticket checking target terminal 20 are the same. Figure 3 In each of the steps shown, detailed descriptions of previously described operations will be omitted.

[0080] refer to Figure 3 The ticket issuing target terminal 20 can send a ticket issuing request signal to the server 10 (S210). In response, the server 10 can send a terminal information request signal to the ticket issuing target terminal 20 (S110), and the ticket issuing target terminal 20 can send its first terminal information to the server 10 (S220).

[0081] Afterwards, the server 10 can generate ticket information (S120), and store the ticket information and the first terminal information in a database in a one-to-one correspondence (S130). Furthermore, the server 10 can send the electronic ticket corresponding to the ticket information to the ticket issuing target terminal 20 (S140).

[0082] Afterwards, the ticket inspection target terminal 20 can touch the electronic ticket to the ticket inspection device 30 installed in the viewing facility (S230). Through this touch operation, the ticket inspection device 30 can collect the ticket information corresponding to the electronic ticket and the second terminal information of the ticket inspection target terminal 20, and send it to the server 10 (S310).

[0083] Afterwards, the server 10 can refer to the database to identify the first terminal information corresponding to the ticket information received from the ticket checking device 30 (S150), and compare it with the second terminal information received from the ticket checking device 30 (S160). In this example, the ticket issuing target terminal 20 and the ticket checking target terminal 20 are the same, so the first terminal information and the second terminal information are consistent. In this case, the server 10 can determine that the authentication of the electronic ticket is successful.

[0084] At this time, the server 10 can also send an authentication success signal to the ticket checking device 30 (S170), and the ticket checking device 30 can open the ticket gate according to the authentication success signal.

[0085] On the other hand, when the terminal information is forged or stolen, the first terminal information and the second terminal information may be the same even if the ticket issuing target terminal 20 is different from the ticket checking target terminal 20. In view of this, the server 10 can further use the location information of the user terminal 20 to perform the authentication operation when the first terminal information and the second terminal information are the same.

[0086] For this purpose, the server 10 can receive the terminal position from the user terminal 20 (ie, the ticket inspection target terminal 20 ) that touches the ticket inspection device 30 when the first terminal information and the second terminal information are the same in step S60 .

[0087] Specifically, the server 10 can send a terminal location request signal to the user terminal 20 that touches the ticket checking device 30. According to the terminal location request signal, the user terminal 20 can output an interface for confirming whether to agree to send the terminal information, and when the user inputs an agreement command through the corresponding interface, the user terminal 20 can send the terminal location to the server 10.

[0088] Afterwards, the server 10 can compare the position of the ticket inspection device 30 and the terminal position pre-stored in the database, and if the distance between the two is within the preset distance, it is determined that the electronic ticket is successfully authenticated. That is, the server 10 can determine that the electronic ticket is successfully authenticated only when the terminal information of the ticket issuing target terminal 20 and the ticket inspection target terminal 20 are the same and the distance between the position of the ticket inspection target terminal 20 and the ticket inspection device 30 during ticket inspection is relatively close.

[0089] On the other hand, if the location of the ticket checking device 30 is not pre-stored in the database, the server 10 can determine that the authentication of the electronic ticket is successful when the distance between the terminal location and the location of the viewing facility corresponding to the electronic ticket touched by the ticket checking device 30 is within a preset distance.

[0090] Specifically, the server 10 can identify the viewing facility corresponding to the corresponding electronic ticket through the ticket information of the electronic ticket read by the ticket checking device 30. The server 10 can compare the geographical location of the viewing facility with the location of the terminal previously received, and if the distance between the two is within a preset distance, it is determined that the authentication of the electronic ticket is successful. That is, the server 10 can determine that the authentication of the electronic ticket is successful only when the terminal information of the ticket issuing target terminal 20 is the same as the terminal information of the ticket checking target terminal 20 and the distance between the location of the ticket checking target terminal 20 and the viewing facility during ticket checking.

[0091] In the following, reference Figure 4 Detailed description of an example of determining that authentication of an electronic ticket fails when the ticket issuing target terminal 20 and the ticket checking target terminal 20 are different. Figure 4 In each of the steps shown, detailed descriptions of previously described operations will be omitted.

[0092] refer to Figure 4 The ticket issuing target terminal 20a can send a ticket issuing request signal to the server 10 (S210). In response, the server 10 can send a terminal information request signal to the ticket issuing target terminal 20a (S110), and the ticket issuing target terminal 20a can send its first terminal information to the server 10 (S220).

[0093] Afterwards, the server 10 can generate ticket information (S120), and store the ticket information and the first terminal information in a database in a one-to-one correspondence (S130). Furthermore, the server 10 can send the electronic ticket corresponding to the ticket information to the ticket issuing target terminal 20a (S140).

[0094] Afterwards, the electronic ticket stored in the ticket issuing target terminal 20a can be illegally copied to the ticket checking target terminal 20b (S410), and the ticket checking target terminal 20b can touch the electronic ticket to the ticket checking device 30 installed in the viewing facility (S230). Through this touching operation, the ticket checking device 30 can collect the ticket information corresponding to the electronic ticket and the second terminal information of the ticket checking target terminal 20b, and send it to the server 10 (S310).

[0095] Afterwards, the server 10 can refer to the database to identify the first terminal information corresponding to the ticket information received from the ticket checking device 30 (S150), and compare it with the second terminal information received from the ticket checking device 30 (S160). In this example, the ticket issuing target terminal 20a and the ticket checking target terminal 20b are different terminals, so the first terminal information and the second terminal information are different. In this case, the server 10 can determine that the authentication of the electronic ticket has failed.

[0096] At this time, the server 10 can also send an authentication failure signal to the ticket checking device 30 (S180), and the ticket checking device 30 can close the ticket gate according to the authentication failure signal.

[0097] On the other hand, when the user who has issued the electronic ticket changes the user terminal 20, the ticket issuing target terminal 20 and the ticket checking target terminal 20 are different, and the user who actually purchased the electronic ticket and meets the regulations may not be able to enter the viewing facility. In view of this, the server 10 can update the first terminal information stored in the database according to the re-issue request of the user terminal 20.

[0098] refer to Figure 5 , the first user terminal 20a can send a ticket request signal to the server 10 (S210). In response, the server 10 can send a terminal information request signal to the first user terminal 20a (S110), and the first user terminal 20a can send its first terminal information to the server 10 (S220).

[0099] Afterwards, the server 10 can generate ticket information (S120), and store the ticket information and the first terminal information in a database in a one-to-one correspondence (S130). Furthermore, the server 10 can send an electronic ticket corresponding to the ticket information to the first user terminal 20a (S140).

[0100] Afterwards, the user may replace the first user terminal 20a with the second user terminal 20c. In this case, the server 10 can receive a re-issue request signal for the electronic ticket from the second user terminal 20c (S420). In response to the re-issue request signal, the server 10 can delete the first terminal information corresponding to the ticket information of the electronic ticket stored in the database, that is, the terminal information of the first user terminal 20a (S510).

[0101] Afterwards, the server 10 can re-receive the first terminal information from the second user terminal 20c (S430), and re-store the ticket information of the electronic ticket and the re-received first terminal information in a one-to-one correspondence in the database (S520). Furthermore, the server 10 can send the electronic ticket corresponding to the ticket information to the second user terminal 20c (S530).

[0102] Afterwards, the second user terminal 20c can touch the electronic ticket to the ticket checking device 30 installed in the viewing facility (S230). Through this touch operation, the ticket checking device 30 can collect the ticket information corresponding to the electronic ticket and the second terminal information of the second user terminal 20c, and send it to the server 10 (S310).

[0103] Afterwards, the server 10 can refer to the database to identify the first terminal information corresponding to the ticket information received from the ticket checking device 30 (S150), and compare it with the second terminal information received from the ticket checking device 30 (S160). In this example, the first terminal information stored in the database has been updated from the terminal information of the first user terminal 20a to the terminal information of the second user terminal 20c, so the first terminal information and the second terminal information are consistent. In this case, the server 10 can determine that the authentication of the electronic ticket is successful.

[0104] As described above, the present invention checks the electronic ticket by comparing the user terminal 20 information at the time of ticket issuance and the time of ticket checking, so that only customers who actually purchased the electronic ticket can be selectively allowed to enter the facility without the need for additional personnel to authenticate whether they are qualified users.

[0105] As described above, the present invention has been described with reference to the exemplary drawings, but the present invention is not limited to the embodiments and drawings disclosed herein, and those skilled in the art can make various modifications within the scope of the technical idea of ​​the present invention. In addition, although the effects of the structure according to the present invention are not explicitly described and explained when explaining the embodiments of the present invention above, it should be recognized that the foreseeable effects caused by the structure.

Claims

1. A method for checking an electronic ticket, characterized in that: The steps include: receiving first terminal information and a ticket request signal from a user terminal; Generating ticket information corresponding to the ticket request signal, and sending an electronic ticket corresponding to the ticket information to the user terminal; receiving ticket information and second terminal information from the ticket checking device; Identifying first terminal information corresponding to the received ticket information; and The electronic ticket is authenticated based on the identity of the identified first terminal information and the second terminal information received from the ticket checking device.

2. The electronic ticket checking method according to claim 1, characterized in that: The electronic ticket is a barcode, a QR code, a near-field communication (NFC) ticket or a non-fungible token (NFT) ticket.

3. The electronic ticket checking method according to claim 1, characterized in that: The step of receiving the first terminal information and the ticket issuance request signal comprises the following steps: receiving the ticket request signal from the user terminal; Sending a terminal information request signal to the user terminal; and The first terminal information is received from the user terminal.

4. The electronic ticket checking method according to claim 1, characterized in that: The step of sending the electronic ticket to the user terminal comprises the following steps: Generating ticket information corresponding to the ticket request signal; Storing the generated ticket information and the received first terminal information in a database in a one-to-one correspondence; and An electronic ticket including the generated ticket information is generated and sent to the user terminal.

5. The electronic ticket checking method according to claim 1, characterized in that: The step of receiving the ticket information and the second terminal information comprises the following steps: The ticket information of the electronic ticket touched by the ticket checking device and the second terminal information of the user terminal touched by the ticket checking device are received.

6. The electronic ticket checking method according to claim 1, characterized in that: The first terminal information and the second terminal information include a unique ID that is differently set for each user terminal.

7. The electronic ticket checking method according to claim 6, characterized in that: The first terminal information and the second terminal information include at least one of a MAC address, an international mobile equipment identity code IMEI, a device unique identifier UDID, a universal unique identifier UUID, and an advertising identifier ADID.

8. The electronic ticket checking method according to claim 1, characterized in that: The steps of authenticating the electronic ticket include the following steps: If the first terminal information is the same as the second terminal information, it is determined that the authentication of the electronic ticket is successful.

9. The electronic ticket checking method according to claim 1, characterized in that: The steps of authenticating the electronic ticket include the following steps: When the first terminal information is the same as the second terminal information, receiving a terminal position from a user terminal in contact with the ticket checking device; and If the distance between the terminal position and the ticket checking device position is within a preset distance, it is determined that the authentication of the electronic ticket is successful.

10. The electronic ticket checking method according to claim 1, characterized in that: The steps of authenticating the electronic ticket include the following steps: When the first terminal information is the same as the second terminal information, receiving a terminal position from a user terminal in contact with the ticket checking device; and If the distance between the terminal position and the position of the viewing facility corresponding to the electronic ticket is within a preset distance, it is determined that the authentication of the electronic ticket is successful.

11. The electronic ticket checking method according to claim 1, characterized in that: The following steps are also included: receiving a re-issue request signal of the electronic ticket from a user terminal; In response to the re-ticket request signal, deleting the first terminal information stored corresponding to the ticket information of the electronic ticket from the database; Re-receiving first terminal information from the user terminal; storing the ticket information of the electronic ticket and the re-received first terminal information in the database in a one-to-one correspondence; and The electronic ticket is sent to the user terminal.

12. An electronic ticket checking system, characterized in that: include: server; A ticket checking device, used for sending the touch information to the server; a ticket issuing target terminal, used for receiving an electronic ticket from the server; and The ticket inspection target terminal is used to touch the electronic ticket to the ticket inspection device. The server authenticates the electronic ticket based on the identity of the first terminal information received from the ticket issuing target terminal and the second terminal information collected by touching with the ticket checking device.

13. The electronic ticket checking system according to claim 12, characterized in that: The ticket issuing target terminal sends the first terminal information and the ticket issuing request signal to the server, The server generates ticket information in response to the ticket issuance request signal, and sends an electronic ticket corresponding to the ticket information to the ticket issuance target terminal. The ticket checking device sends the ticket information and the second terminal information collected by touching the ticket checking target terminal to the server, The server identifies first terminal information corresponding to the ticket information received from the ticket checking device, and authenticates the electronic ticket based on the identity of the identified first terminal information and second terminal information received from the ticket checking device.

Images