WO2014080405A1

WO2014080405A1 - System and methods for electronic ticketing and gate verification control for events

Info

Publication number: WO2014080405A1
Application number: PCT/IL2013/050965
Authority: WO
Inventors: Lior JORNO; Boaz SHNAPP
Original assignee: Jorno Lior
Priority date: 2012-11-25
Filing date: 2013-11-24
Publication date: 2014-05-30

Abstract

The present disclosure relates generally to tickets to events and, more particularly, a system and methods for issuing and providing tickets to an event, sent to a personal electronic device of a user obtaining the tickets, and authentication the electronic tickets at the entrance gate to the event venue, using the personal electronic device and an electronic device associated with that entrance gate.

Description

SYSTEM AND METHODS FOR ELECTRONIC TICKETING AND GATE VERIFICATION CONTROL FOR EVENTS

FIELD OF THE INVENTION

BACKGROUND OF THE INVENTION

This section is intended to introduce the reader to various aspects of art that may be related to various aspects of the present disclosure, described herein below. This discussion is believed to be helpful in providing the reader with background information to facilitate a better understanding of the various aspects of the present disclosure. Accordingly, it should be understood that these statements are to be read in this light, and not as admissions of prior art.

An event ticket may provide the ticket holder entry to a corresponding event as well as other benefits. However, tangible tickets may be misplaced or lost and may not be easily replaced. Such tickets may not easily be transferred to distant individuals, and may provide a limited range of benefits. Moreover, such tickets may be forged without the ability of the gatekeeper to authenticate the ticket presented at the entrance gate of the event. There is therefore a need and it would be advantageous to have a system and methods for issuing and providing tickets to an event, sent to a personal electronic device of a user obtaining the tickets. It would be further advantageous to have a system and methods that facilitates simple authentication of issued electronic tickets at the entrance gate to the event, using the personal electronic device and an electronic device associated with that entrance gate. DEFINITIONS

The term "event" is referred to herein as an event, taking place at a secured specific location and wherein the admission to the event requires permission. An event may be entrance to a club, a movie, a theater, a party, a wedding, a convention, an exhibition and so on and so forth.

SUMMARY OF THE INVENTION

The present invention introduces a system and methods for electronic ticketing and gate verification control for events. The electronic ticketing system includes an e- ticket server having a processing unit, a data-base (DB) and a managing module. The managing module manages the DB, including the subscribers DB and the clubs DB, facilitates registered subscribers to use the services provided by electronic ticketing system, via a network such as an internet network and/or a cellular network.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to understand the innovation and to see how the same way may be carried in practice, some preferred embodiment will now be described, by way of non- limiting examples only with reference to the accompanying topics and examples, in which: Fig. 1 is a schematic illustration of a system for electronic ticketing and gate verification control for events, according to an embodiment of the present invention.

Fig. 2 is a schematic illustration of an example application as displayed on the screen of a personal mobile device of a user, using the electronic ticketing system shown in Fig. 1.

Fig. 3 is a schematic illustration of an example application as displayed on the screen of an electronic device disposed proximal to an event gate, being part of the electronic ticketing system shown in Fig. 1.

Fig. 4 is a schematic illustration of an event gate verification control system, according to an embodiment of the present invention. Fig. 5 schematically illustrates an example method of registering to become a subscriber of the system shown in Fig. 1, according to an embodiment of the present invention.

Fig. 6 schematically illustrates an example method of submitting an admission request to a hall that provides an event, of the system shown in Fig. 1, according to an embodiment of the present invention.

Fig. 7 schematically illustrates an example method of sorting out admission requests to a particular event by the event provider, according to an embodiment of the present invention.

Fig. 8 schematically illustrates an example method of a subscriber being admitted to an event, using the system shown in Fig. 1, according to an embodiment of the present invention.

Fig. 9 schematically illustrates an example method of a verifying a virtual ticket of a subscriber, being admitted to an event, presented on the personal mobile device of the subscriber, according to an embodiment of the present invention.

Fig. 10 schematically illustrates an example method of a subscriber being admitted by a gatekeeper of an event, according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE INVENTION

Before explaining embodiments of the invention in detail, it is to be understood that the invention is not limited in its application to the details of construction and the arrangement of the components set forth in the host description or illustrated in the drawings.

An embodiment is an example or implementation of the inventions. The various appearances of "one embodiment", "an embodiment" or "some embodiments" do not necessarily all refer to the same embodiments. Although various features of the invention may be described in the context of a single embodiment, the features may also be provided separately or in any suitable combination. Conversely, although the invention may be described herein in the context of separate embodiments for clarity, the invention may also be implemented in a single embodiment. Reference in the specification to "one embodiment", "an embodiment", "some embodiments" or "other embodiments" means that a particular feature, structure, or characteristic described in connection with the embodiments is included in at least one embodiments, but not necessarily all embodiments, of the inventions. It is understood that the phraseology and terminology employed herein is not to be construed as limiting and are for descriptive purpose only.

Methods of the present invention may be implemented by performing or completing manually, automatically, or a combination thereof, selected steps or tasks. The term "method" refers to manners, means, techniques and procedures for accomplishing a given task including, but not limited to, those manners, means, techniques and procedures either known to, or readily developed from known manners, means, techniques and procedures by practitioners of the art to which the invention belongs. The descriptions, examples, methods and materials presented in the claims and the specification are not to be construed as limiting but rather as illustrative only.

Meanings of technical and scientific terms used herein are to be commonly understood as to which the invention belongs, unless otherwise defined. The present invention can be implemented in the testing or practice with methods and materials equivalent or similar to those described herein. The present invention will be described in terms of an event taking place, by way of example only, at a club. But the present invention is not limited to managing the admission to a club only, and the event may be any other event into which admission requires a permit.

Reference is made to the drawings. Fig. 1 is a schematic illustration of a system 100 for electronic ticketing and gate verification control for events, according to an embodiment of the present invention. Electronic ticketing system 100 includes an e-ticket server 110 having a processing unit, a data-base (DB) 120 and a managing module 130. Managing module 130 manages DB 120, including subscribers DB 124 and clubs DB 122, facilitates registered subscribers to use the services provided by electronic ticketing system 100, via a network 50 such as an internet network and/or a cellular network. Electronic ticketing system 100 further includes a selector-processing-device 30 such as a tablet PC, a desktop PC, a laptop PC or any other processing unit known in the art adapted to execute selector-application 140. Electronic ticketing system 100 further includes a subscriber-application 160, executed by a computer processor of a personal electronic device 20, such as a smartphone. Electronic ticketing system 100 further includes a gatekeeper-application 150, executed by a computer processor of a gatekeeper-processing-device 35, having a display-unit, the gatekeeper-processing- device 35 being a tablet PC, a desktop PC, a laptop PC or any other processing unit known in the art. Reference is also made to Fig. 2, a schematic illustration of an example subscriber-application 160 as displayed on the screen of a personal mobile device 20 of a subscriber 10, using electronic ticketing system 100. Subscriber 10 is a registered user of the service provided by electronic ticketing system 100, and has obtained a permit 162 that is displayed on the screen of personal mobile device 20 by subscriber- application 160.

Reference is also made to Fig. 3, a schematic illustration of an example gatekeeper-application 150, as displayed on the screen of gatekeeper-processing- device 35 of a particular club, using electronic ticketing system 100. The particular club is a registered member of the service provided by electronic ticketing system 100. When gatekeeper-application 150 is activated, electronic ticketing system 100 sends a new code which code is displayed by gatekeeper-application 150 on the screen of gatekeeper-processing-device 35. The very same code is also displayed on all personal mobile devices 20, on which personal mobile devices 20 subscriber- application 160 is activated. In the example shown in Fig. 3, the current club entry code 154 is composed, by way of example, from a line of a combination different shapes and/or colors, disposed in a particular order. In the example shown in Fig. 3, the other two code lines show the previous codes. As can be seen in Fig. 2, a code line 164 is also shown by subscriber-application 160 on the screen of a personal mobile device 20, wherein current code line 154 is identical to code line 164. Current club entry codes 154 and 164 are kept synchronized by electronic ticketing system 100, wherein electronic ticketing system 100 updates the codes in a preconfigured time interval. For example, electronic ticketing system 100 may update the codes every 10 seconds, 20 seconds, 30 seconds or any other preconfigured time interval.

Reference is also made to Fig. 4, a schematic illustration of an event gate verification control sub system, according to an embodiment of the present invention. On the date of the event, a subscriber 10, who has obtained a permit 162 to a particular club 40, which virtual permit 162 is displayed on the screen of his/her personal mobile device 20, arrives at the gate 42 of club 40. Subscriber 10 shows the permit, displayed on his/her personal mobile device 20, to the gatekeeper 44, who compares the code 164 and 154.

The synchronized codes 154 and 164 authenticate the validity of permit 162, to prevent ticket counterfeiting. Optionally, permit 162 further includes a picture 166 of subscriber 10, to validate that he/she is the owner of permit 162. Optionally, permit 162 further includes personal details of subscriber 10 that may be matched against an ID, to validate that he/she is the owner of permit 162. Reference is now made to Fig. 5, a schematic illustration of an example method 200 of registering to become a subscriber of electronic ticketing system 100, by a user 10, according to an embodiment of the present invention. Method 200 includes the following steps:

Step 201: subscriber 10 activates subscriber-application 160. Subscriber 10 activates subscriber-application 160 on his/her personal mobile device 20.

Step 210: subscriber-application 160 determines if subscriber is a new or existing subscriber.

Subscriber 10 indicates to subscriber-application 160 whether he/she is a new or existing user of electronic ticketing system 100.

If an existing user of electronic ticketing system 100, go to step 230.

Step 220: a user registers to the services provided by electronic ticketing system 100.

A user registers to the services provided by electronic ticketing system 100, to thereby become a subscriber 10. The user enters his/her personal details, selected from the group of personal information including: full name, full address, ID number, password, personal facial picture, birth date, gender, email address, finger print and any other personal data.

Step 222: transmitting the personal data to e-ticket server 110.

The user personal data is transmitted to e-ticket server 110.

Step 224: checking the validity of the submitted personal data.

E-ticket server 110 checks if the submitted personal data is valid.

If the submitted personal data is valid, go to step 260.

Step 230: subscriber 10 logs in to subscriber-application 160.

Subscriber 10 logs in to subscriber-application 160.

Step 240: e-ticket server 110 verifies the identity of subscriber 10.

E-ticket server 110 checks if the submitted personal data is valid.

If identity is valid, go to step 230.

Step 250: checking if subscriber 10 is blocked.

E-ticket server 110 checks if subscriber 10 is blocked.

If so, go to step 230.

Step 260: checking the validity of the submitted personal data.

E-ticket server 110 generates a random code and sends the code to subscriber's personal phone, for example as an SMS (text/numbers message) or an MMS (multimedia message).

Step 270: subscriber 10 returns the received code to e-ticket server 110.

Subscriber 10 returns the received code to e-ticket server 110.

Step 280: checking the validity of the returned code.

E-ticket server 110 checks if the sent code and the returned code match.

If the sent code and the returned code do not match, go to step 260.

Step 290: e-ticket server 110 updates the data base.

E-ticket server 110 updates subscribers DB 124 with the personal data of the new subscriber 10. Reference is now made to Fig. 6, a schematic illustration of an example method 300 of submitting a request for a permit to a specific club, from electronic ticketing system 100, by subscriber user 10, according to an embodiment of the present invention. Method 300 includes the following steps: Step 301: subscriber 10 activates subscriber-application 160 and logs in.

Subscriber 10 activates subscriber-application 160 on his/her personal mobile device 20 and logs into electronic ticketing system 100.

Step 310: presenting subscriber 10 with a list of available clubs 40.

E-ticket server 110 presents subscriber 10 with a list of clubs 40, including existing permissions status, requests status, and allowing subscriber 10 to select a club 40 of his/her choice.

Step 320: selecting a club 40.

Subscriber 10 selects a club 40 of his/her choice and submits "entry request" for that club to e-ticket server 110. Subscriber 10 may also exit subscriber- application 160, at this step.

Step 330: e-ticket server 110 adds the new request to the waiting list of the selected club 40.

E-ticket server 110 adds the new request to the waiting list of the selected club 40

Go to both steps 340 and 350, in parallel.

Step 340: e-ticket server 110 updates the waiting list in selector-application 140.

E-ticket server 110 updates the waiting list in selector-application 140 with the new request submitted by subscriber 10.

Go to step 310. Step 350: delaying for N seconds.

Selector-application 140 waits for N seconds, before querying for the status of his/her request for a permit to enter the chosen club 40.

Step 352: sending a query to e-ticket server 110 regarding the status of the entry request. Subscriber 10 sends to e-ticket server 110, a query to check if the selector of the chosen club 40 has submitted a decision as to whether the "entry request" submitted by subscriber 10, is granted or rejected.

Step 360: checking the response to the "query status" request received from the e- ticket server 110.

Subscriber-application 160 reviews the response to the "request status" query, received from E-ticket server 110.

If no decision was made, go to step 350.

If the request submitted by subscriber 10 was rejected, go to step 380.

Step 370: entry granted is shown for the selected club, in application clubs list.

The request submitted by subscriber 10 is marked the request as granted in the subscriber-application 160.

Subscriber 10 is notified that his/her request was granted. Subscriber 10 may view the granted permit using subscriber-application 160 on his/her personal mobile device 20.

Step 380: entry rejected is shown for the selected club, in application clubs list.

The request submitted by subscriber 10 is marked the request as rejected in the subscriber-application 160.

Step 385: disabling action for the selected club, in subscriber-application 160.

Subscriber-application 160 disables any action from subscriber 10, with regards to the selected club.

Step 390: delaying for minutes.

Subscriber-application 160 waits for M minutes, in which time interval subscriber 10 is blocked from submitting a new "entry request" for that club.

Step 395: Allowing Subscriber 10 to submit a new "entry request" that club 40.

Subscriber 10 is now allowed to submit a new "entry request" to that club 40. Exit.

Reference is also made to Fig. 7, a schematic illustration of an example method 400 of sorting out admission requests to a particular event by the event provider, according to an embodiment of the present invention. Method 400 includes the following steps:

Step 401: the selector of the selected club 40 activates selector-application 140 and logs in.

The selector of the selected club 40 activates selector-application 140 and logs in.

Step 410: E-ticket server 110 presents a list of subscribers' information to the selector.

E-ticket server 110 presents a list of subscribers information, preferably including images, is to the Selector, facilitating approval or rejection of a request.

Step 420: the selector approves or rejects each request.

The selector the club 40 approves or rejects each request. Step 430: sending the decisions to e-ticket server 110.

The selector sends the decisions to e-ticket server 110.

Step 440: checking the response to the request status response received from the selector of the selected club 40.

E-ticket server 110 follows the response to the request status, as received from the selector of the selected club 40.

If the "entry request" has been rejected, go to step 460.

Step 450: Updating the Subscribers request.

The "entry request" was granted. E-ticket server 110 updates subscribes 10 "entry request", in DB 120 with the decision taken, go to step 410

Step 460: Updating the Subscribers request.

The "entry request" was NOT granted. E-ticket server 110 updates subscribes 10 "entry request", in DB 120 with the decision taken, go to step 410

Reference is also made to Fig. 8, a schematic illustration of an example method 500 of a subscriber being admitted to an event, using electronic ticketing system 100, according to an embodiment of the present invention. Method 500 includes the following steps: Step 501: the gatekeeper 44 of the selected club 40 activates gatekeeper-application 150 and logs in.

The gatekeeper 44 of the selected club 40 activates gatekeeper-application 150 and logs in. Step 510: the current club entry code is fetched from server e-ticket server 110.

The current club entry code 154 and optionally, also one or more previous codes, are fetched from e-ticket server 110.

Step 520: displaying the fetched code(s) on gatekeeper-processing-device 35.

Gatekeeper-application 150 displays the fetched code(s) on the screen of gatekeeper-processing-device 35. A sample of displayed codes is shown in Fig

3.

Step 530: delaying for N seconds.

Gatekeeper-application 150 waits for N seconds.

Go to step 510. Reference is now made to Fig. 9, a schematic illustration of an example method 600 of a verifying a virtual ticket 162 of a subscriber 10, being admitted to an event, according to an embodiment of the present invention, wherein virtual ticket 162 is presented on personal mobile device 20 of subscriber 10. Method 600 includes the following steps: Step 601: subscriber 10 reaches the entrance of the selected club.

Subscriber 10 reaches entrance 42 of selected club 40.

Step 610: subscriber 10 starts his subscriber-application 160.

Subscriber 10 starts his subscriber-application 160 and fetches the entry permits 162 from application menu. Step 620: subscriber-application 160 presents a list of valid entry permits for subscriber 10.

Subscriber-application 160 presents a list of valid entry permits for subscriber 10

Step 630: subscriber 10 selects the club entry permit 162 of the selected club 40. Subscriber 10 selects the club entry permit 162 of the selected club 40, from the presented list of permits.

Step 640: subscriber-application 160 downloads the current club entry code 164 from e-ticket server 110.

Subscriber-application 160 inquires e-ticket server 110 as to the status of permit 162 and for the current club entry code 164.

Step 650: checking if permit 162 is valid.

Subscriber-application 160 validates permit 162 status.

If permit 162 is not valid, go to step 620. Step 660: subscriber-application 160 displays the entry permit 162.

The current club entry code 164 and optionally, personal information of subscriber 10, are displayed on the screen his/her personal mobile device 20. Entry permit example is shown in Fig 2.

Step 670: delaying for N seconds. Go to step 640.

Reference is also made to Fig. 10, a schematic illustration of an example method 700 of a subscriber being admitted by a gatekeeper 44 of an event, according to an embodiment of the present invention. Method 700 includes the following steps:

Step 701 subscriber 10 reaches the entrance of the selected club. Subscriber 10 reaches entrance 42 of selected club 40, where a gatekeeper 44 checks the entrance permit of subscriber 10.

Step 710: gatekeeper 44 asks subscriber 10 to present his/her entry permit 162.

Gatekeeper 44 asks subscriber 10 to present his/her entry permit 162.

Step 720: gatekeeper 44 checks the validity of entry permit 162. Gatekeeper 44 checks the validity of entry permit 162 by:

Comparing permit current club entry code 164 with the current club entry code 154, being displayed on gatekeeper-processing-device 35.

Optionally, the image of subscriber 10 with the face of subscriber 10. Step 730: analyzing the comparison results.

Gatekeeper 44 analyzes the comparison results.

If the current club entry codes 164 and 154 are identical and optionally, the displayed image of subscriber 10 and the face of subscriber 10 are similar, subscriber 10 is allowed to enter club 40. If the current club entry codes 164 and 154 are not identical and/or optionally, the displayed image of subscriber 10 and the face of subscriber 10 are not similar, subscriber 10 is disallowed to enter club 40.

Although the present invention has been described with reference to the preferred embodiment and examples thereof, it will be understood that the invention is not limited to the details thereof. Various substitutions and modifications have suggested in the foregoing description, and other will occur to those of ordinary skill in the art. Therefore, all such substitutions and modifications are intended to be embraced within the scope of the invention as defined in the following claims.

Claims

WHAT IS CLAIMED IS:

1. A system for issuing electronic ticketing and gate verification control for events, comprising: an e-ticket server having a processing unit; a data-base (DB); a managing module.

2. A system according to claim 1 where a managing module managing DB, includes subscribers DB and event's venue DB;

3. A system according to claim 2 where the services provided by electronic ticketing system are transferred via network;

4. A system according to claim 3 where the electronic ticketing system includes a selector-processing-device adapted to execute selector-application;

5. A system according to claim 4 where the electronic ticketing system includes a subscriber-application, executed by a computer processor of a personal electronic device;

6. A system according to claim 5 where the electronic ticketing system includes a gatekeeper-application, executed by a computer processor of a gatekeeper- processing-device, having a display-unit;

7. A system according to claim 6 where the gatekeeper-processing-device is any processing unit;

8. A system according to claim 7 where the electronic ticketing system sends a new code to be displayed by gatekeeper-application on the screen of gatekeeper-processing-device, when gatekeeper-application is activated, and the very same code is also displayed on all personal electronic device on which subscriber-application is activated.

9. A system according to claim 8 where event's venue entry codes are kept synchronized by electronic ticketing system, wherein electronic ticketing system updates the codes in a preconfigured time interval.

10. A system according to claim 9 where the synchronized codes authenticate the validity of permit and identity of holder of permit by comparing subscriber's picture and personal details in DB to that of holder of permit.

11. A method of registering to become a subscriber of electronic ticketing system, by a user, comprising the steps of:

• subscriber activates subscriber-application on his personal mobile device;

• subscriber-application determines if subscriber is a new or existing

subscriber to the electronic ticketing system;

• if subscriber is an existing subscriber he logs in to subscriber-application;

• e-ticket server verifies the identity of subscriber;

• e-ticket server checks if subscriber is blocked, if so, he is referred to

subscriber-application ;

• If user is not yet a subscriber, The user enters his personal details, selected from the group of personal information including: full name, full address, ID number, password, personal facial picture, birth date, gender, email address, finger print and any other personal data, and transmits the personal data to e-ticket server;

• e-ticket server checks the validity of submitted personal data;

• e-ticket server generates a random code sending it to subscriber's personal electronic device;

• subscriber returns the received code to e-ticket server;

• the validity of the returned code is been checked by e-ticket server;

• if sent code and the returned code do not match, user is referred to e-ticket server to have the personal data rechecked;

• e-ticket server updates subscribers DB with the personal data of the new subscriber;

12. A method according to claim 11 where a subscriber submits a request to electronic ticketing system for a permit to a specific event-venue, comprising the steps of:

• subscriber activates subscriber-application on his personal mobile device and logs into electronic ticketing system; e-ticket server presents subscriber with a list of event venues, including existing permissions status, requests status, for selecting the desired venue; Subscriber selects a venue and submits "entry request" to e-ticket server, or exits without selection; if venue is selected, e-ticket server adds the new request to the waiting list of the selected venue and updates the waiting list in selector-application; selector-application waits for N seconds, before querying for the status of request for a permit to enter the chosen venue;

subscriber sends to e-ticket server, a query to check if the selector of the chosen venue has granted or rejected "entry request";

if request is rejected, rejection is registered in subscriber-application which disables any further action of subscriber concerning the selected venue for M minutes, thus blocking subscriber from submitting new "entry request" for that venue;

when M minutes have passed, subscriber may submit a new "entry request" to that venue; if request is approved, it is registered as "granted" in the subscriber- application, and subscriber may view the granted permit using subscriber- application on his personal mobile device;

If request is rejected, subscriber is logged out.