RU2647667C1 - Method of creating universal pass for user access to event - Google Patents

Abstract

FIELD: means of ensuring safety.

SUBSTANCE: invention relates to a method for creating a universal pass for the user access to events. In the method, a mobile developer application is downloaded to a mobile device of the user from the application store, the user's mobile device and bank card are registered in the mobile developer application, the user is assigned with an ID number, to which the user’s medium data is attached: the bank card number or the mobile device number of the user, tickets to the event are generated, the ticket is paid, and then a unique number of the electronic ticket is formed and the client ID is bound to it, herewith this set – the number of the electronic ticket plus the ID – is a universal identification code (UIC), which is a universal pass to the event, and this UIC is formed in the first server of the developer, is transferred to the processing center of the terminal of the second server of the developer, to the terminal for the user's access to the event and to the user through the first development server and the mobile developer application in order to control the passage of the user through the terminal and the user's access to the event, herewith all the information is transmitted through the Internet.

EFFECT: technical result is to automate the user's access to the event.

1 cl, 1 dwg

Description

Technical field

The invention relates to systems that provide user access to the servers of issuers for the sale of tickets and provide access through terminals to control access to events.

State of the art

The well-known "Method and system of redistribution of original tickets", patent of the Russian Federation 2189632.

The invention relates to an automated system for the redistribution of tickets for entertainment events. The technical result is to increase the reliability and efficiency of ticket sales in the secondary market. The system includes devices for performing operations of accepting tickets from individual sellers, devices for transferring tickets to a central database for redistribution, establishing a market price based on demand and / or service fees and distributing tickets among new customers. The system provides sellers with a wider market and allows potential viewers to easily buy tickets for an event at a reasonable price. Individual buyers are not required to deal directly with brokers, speculators or other intermediaries and, thus, they are protected from fakes. The system checks all the data received by the database, and to protect the seller, the buyer's credit card is checked, from which the amount for payment of the seller is withdrawn.

The invention relates to the redistribution of tickets for a spectacular event, in particular to an automated system for mailing tickets for a spectacular event for the subsequent sale of tickets at a nominal price or at a market price based on demand and / or service fees and for distributing tickets among new owners .

The original ticket redistribution system comprises a host computer having a central database and comprising a network interface device, a seller’s server connected to a network interface device, in which the seller’s server is used to receive and store information about a previously sold original ticket of an individual seller and to confirm seller’s information , a ticket server associated with a network interface device in which a ticket server is used to receive, store and limit access rights to the original ticket and to confirm the information on resale tickets and to establish the market price, the customer’s server connected to the network interface device, in which the customer’s server is used to receive and store the customer’s information and to confirm the customer’s information, and the output device connected to the customer’s server, in which the output device is used to transmit and confirm access to print copies of the resale ticket, the seller’s input device for transferring information about the seller’s original ticket to the central database, and the buyer's input device for transmitting the buyer’s information to the central database.

However, this technical solution does not solve the complex issue of buying a ticket and its application, that is, using it to go to the event.

Such a ticket will have to be exchanged at the box office of the corresponding event for a generally accepted paper ticket, after which it can only be used to enter the event.

There are also known methods of ordering tickets through the Ticketland service.

Tickets for all types of events: concerts, theater performances, performances, musicals, festivals, sports matches, etc. can be ordered through the Ticketland online service.

Ticketland.ru is a website representing Ticketland, which is directly related to Moscow Directorate of Theater, Concert and Spectacular Ticket Offices LLC (MDTZK).

To purchase tickets, you must perform the following steps:

1. Choose an event with the possibility of acquiring an electronic ticket.

2. Choose the delivery method "electronic ticket" at checkout.

3. Pay for the order and print the received electronic ticket. Print the purchased electronic ticket, which will be available for download in your account.

An electronic ticket is a digital record in the database of the company “Moscow Directorate of Theater, Concert and Sports and Spectacular Cash Boxes”, confirming the reservation and payment of a ticket for the corresponding entertainment event.

The physical carrier of the electronic ticket is the file of the electronic ticket form, which is sent to the customer’s email address indicated at the time of placing the order, and which must be printed out to attend the event.

An electronic ticket is not a strict reporting form. The buyer can exchange an electronic ticket for a ticket formed on a strict reporting form in the manner prescribed by the public offer agreement published on the website www.ticketland.ru.

All controversial issues are resolved only if there is a ticket formed on the strict reporting form of LLC Moscow Directorate of Theater and Concert and Sports and Spectacular Cash Boxes.

Refunds in case of cancellation or replacement of an event are carried out directly by the entertainment institution if there is a ticket formed on the strict reporting form.

Using an electronic ticket, the user agrees to the terms of the public offer agreement published on the website www.ticketland.ru.

In the case of copying electronic ticket forms, access to the event will be open only for the ticket that was presented first.

The buyer has the right at his own discretion to exchange the purchased electronic ticket for a ticket drawn up on a strict reporting form. For this, the buyer needs to print an electronic ticket in advance of the event and come to the call center with him.

Exchange and re-issuance of electronic tickets

When exchanging an electronic ticket for a ticket on a strict reporting form, the electronic ticket is canceled and will not be accepted for passage. Only the ticket on the BSO form will be allowed to pass.

The procedure for exchanging an electronic ticket for a ticket on a strict reporting form is one-time. In case of loss or damage of a ticket issued on a strict reporting form, a reissue of a ticket is not made.

You can pay for the order placed on the website www.ticketland.ru using the following forms of payment: cash at redemption at one of the cash desks or to the courier upon receipt of the delivered order, using Visa, MasterCard and American Express credit cards.

Ordering and delivery of tickets is carried out in a call-center.

http://plusdaminus.ru/gde-kupit-elektronnyj-bilet-v-internete/

The disadvantage of this method is that such a ticket will have to be exchanged at the box office of the corresponding event for a generally accepted paper ticket, after which it can only be used to enter the event.

There is also the Yandex. Tickets service, a service that aggregates sellers data and allows you to buy a movie ticket. Such electronic tickets are not so electronic - they still need to be printed and you still need to go to the cashier.

The following technical solution is also known https://habrahabr.ru/company/yandex/blog/241389/

This technology is called Smartpass, an application that runs on the iPad mini, recognizes QR codes and sends data to the movie theater system. Cinema is enough to install such a scanner at the entrance to each room.

Smartpass uses the ZBar library to recognize QR codes.

After scanning, the data is sent to the UCS-Premiere system, with which most cinemas work. Having printed the ticket, the cashier, before giving it to you, always tears the spine from him. It is called a “strict reporting form” and the cinema must keep it for five years for reporting to inspection bodies. Smartpass is able to print the form remotely at the cashier - the buyer’s participation is not required for this. Now the share of sales of electronic cinema tickets in Russia is 6%, and in the West - up to 40%.

Smartpass scanners are installed on the Formula Kino network.

https://radario.ru/about-tickets

Such an electronic ticket is called “Radario”.

All tickets are agreed with the organizers and give the right to attend relevant events. When buying a ticket, the buyer receives a unique QR code associated with this event. The ticket is sent to the customer’s personal account on Radario - you need to click on your name, then go to the “Purchased tickets” section and the specified e-mail.

An electronic ticket is a complete security document. It does not need to be additionally changed at the checkout for anything else.

A ticket can be presented in several ways:

1. Print the file sent to the buyer's e-mail address or click “Print” on this ticket in your account in “Purchased tickets”.

Upon entering the event, a QR code will be read to verify the authenticity of the ticket. In some cases, instead of reading a QR code, a digital code check may occur.

2. Present a ticket (namely a QR code) from the screen of any mobile device. For example, you can open a ticket sent by mail on a smartphone or tablet.

3. Mobile application for iPhone and Android. The application fully reflects everything that can be done on the site: find an event, buy a ticket and present it, leave a comment and review, subscribe to the organizers or interests.

https://radario.ru/about-tickets

The disadvantages of this system include the high cost of terminals. In addition, the QR code can be copied many times and used by a large number of people to go to events, especially to those mass events where specific places are not indicated.

Disclosure of invention

The objective of the present invention is to ensure the convenience of using your own mobile device or bank card user as a universal pass for customers - individuals; and for legal entities of the organizers and owners of events: reducing costs for the implementation of the processes of passage of individuals to the event; increasing the speed of control processes during the passage to an event; automation of the process of admission to the event, the exclusive use of a universal pass by only one user.

This problem is solved due to the fact that a method has been created to create a universal pass for the user’s admission to events, which consists in using the user who needs to purchase a ticket for the event and provide admission to this event from the developer's mobile application located on the first developer server, while the user downloads the developer’s mobile application from the application store to his user’s mobile device, registers his mobile device to the mobile m the developer’s application, as well as the user's bank card, and at the time of registration in the mobile application of the developer, the user is assigned an ID number, then the user independently binds to this ID the data of the medium that he plans to use, that is, for the client’s bank card, this is the card number , for the user's mobile device, this is the number of the user's mobile device, while the ID plus the number of the material carrier has a universal pass to the event, then The agent generates the necessary tickets for the event in the developer's mobile application through the ticket aggregation software kernel located on the first developer's server, using the ticket issuing interface located on the issuer's server, and then carries out the procedure for paying for the selected ticket using the client’s bank card registered in the developer's mobile application , and after the payment procedure for the selected ticket is completed, the user is sent an electronic ticket, one or more, to be processed making a passage to the selected event by means of a CMC message or an e-mail to the e-mail address indicated by the client, and at the time of purchase of a ticket using the developer's mobile application, after payment, the developer's mobile application generates a unique e-ticket number and also binds the client ID to it so that the client has the opportunity to pass with any of the registered universal passes, while this combination - the number of the electronic ticket plus ID - this is the universal The identification code is PEC, and this PEC is generated in the first developer server, transferred to the processing center of the terminal of the second developer server and then transferred to the terminal for admitting the user to the event and the client through the first developer server and the developer’s mobile application to control the user’s passage through the terminal for the user’s admission to the event, at the same time, the terminal for the user’s admission to the event is transmitted the actual information about the bundle - wear ID plus the user, and at the time of going to the event when attaching any of the registered media - the user's mobile device or bank card with his number to the terminal for admitting the user to the event, the terminal for admitting the user to the event checks the following: does this PEC have the right to pass or the right to several passes, if he bought several tickets for one pass, then is this device tied to a user's mobile device or a user's bank card to the user ID and if approved, the user goes to the event, while the universal pass of the client does not contain electronic ticket data, and this information is in the terminal for admitting the user to the event, namely in his PEC database and the developer’s mobile application located in the user's mobile device, moreover, a unique identification code - PEC, which is available in the user's universal pass always contains only information regarding this medium - the number of the mobile device the user’s number or the client’s bank card number, after which the user goes to the event, and then finds his place at the event using the data of the electronic ticket sent previously to the client’s mobile device or to the client’s electronic mailbox, and all information is transmitted via the Internet. In this case, the unique PEC identification code is performed as a unique alphanumeric code, which is an identifier for going to the event and allowing the client to go to the event by checking with the PECs transferred using the developer's mobile application from the first developer server to the processing center of the terminal of the second developer server on a terminal for admitting the user to the event and controlling the passage, while all information is transmitted via the Internet system.

The implementation of the invention

In FIG. 1 shows a diagram of an implementation of a method for creating a universal pass for admitting a user to an event.

Declared "A way to create a universal pass for admitting a user to events."

Universal pass is a way of turning a mobile device or a bank card of a user into a universal access tool for any events and in any places where the incoming flow of visitors is controlled (cinemas, theaters, concerts, sports and other events, as well as offices, etc.) using a universal pass system created by the author of this invention. The universal pass also allows you to save and use all the identification data of the ticket for the event selected by the user to use such data when finding your place (presence zone) at the event.

The developer’s mobile application using which the universal pass system is implemented has a web interface and its version specially adapted for users’ mobile devices. The web interface is a website hosted on the Internet for users to use the developer's mobile application located on the server; the mobile application downloaded by the user to his mobile device has the same functions.

The way to create a universal pass simplifies the process of buying tickets for any events and then simplifies the passage to such events.

Users of the universal pass system, individuals are able to attach (register) their mobile device or bank card in the developer's mobile application located on the developer's server via the web interface via the Internet and actually turn the selected tool into a “Universal pass”.

The way to create a universal pass for admitting user 1 to event_ consists of the following components: a user’s mobile device 2 containing a developer’s mobile application 3 with a user’s mobile application interface 4, user’s bank card 5, the first developer’s management server 6, ticket aggregation software core 7, and the processing server 8, processing center for processing card transactions 9, “N” servers of issuers 10 with an interface for issuing tickets 11 each, a second development server and 12 with the processing center of terminals 13, “N” terminals for access control 14, containing the PEC 15 database (PEC-universal identification code), universal pass 16, which is the mobile device of user 2, or a bank card of user 5 for admission to the event 16, containing the universal identification code (hereinafter - PEC) generated by the mobile application of the developer 3.

Developer’s mobile application 3, containing the functionality of searching for tickets and linking the bank card of user 5, is downloaded (downloaded) by user 1 (client of the service) to the mobile device of user 2 (phone, tablet, etc.) for subsequent use in order to purchase tickets.

User’s bank card 5, issued by any bank of any payment system, is linked through the interface of the mobile application of user 4 and the mobile application of the developer 3 to the mobile device of user 2, that is, its data is entered: full number, security code CW, CVC, etc. for subsequent payment of selected tickets through electronic acquiring.

The software aggregation engine for tickets 7 of the first server of the developer 6 has a mobile application of the developer 3, and also contains personal accounts of users 1 after they are registered in the mobile application of the developer 3.

The ticket aggregation core 7 of the first developer server 6 allows user 1 to select and buy tickets for event 17 through ticket issuing interfaces 11 located on the servers of issuers 10. Ticket issuing interfaces 11 are a set of providers engaged by the developer to select and purchase tickets by users 1, downloaded the developer’s mobile application 3.

The processing center for processing card transactions 9 on the processing server 8 binds the data on payment and purchase by the user of 1 tickets to the Universal Pass of user 16.

The processing center of terminal 13 carries out transactions on bank cards of client 4, transfers this data to the terminals to allow the user to the event 14

The terminal for user access to event 14 with the software package and the PEC 15 database allows you to identify the owner of Universal Pass 16, who has the right to enter the event

Universal pass 16 - bank card of user 5 or mobile device of user 2, containing identification data for access to event 17 through the terminal for admission of the user to event 14.

Description of the method

User 1, an individual, downloads (downloads) the mobile application of the developer 3 to the mobile device of user 2 from the application store for his model of the mobile device of user 2 (iOS, Google Play, etc.).

User 1 registers (binds) his bank card of user 5 (one or several) in the mobile application of the developer 3 to pay for the purchased tickets. Registration (linking) of a user’s bank card 4 is the entry by user 1 of the bank card of user 5 into the special fields of the mobile application of the developer 3 using the interface of the mobile application of the developer 4. The data entered by user 1 without fail includes: name and surname of user 1, indicated on user’s bank card 5, user’s bank card number 5, its validity period in mm.yy format. Further, during the payment procedure, it is necessary to enter the data of the special secret code of user bank card 5 (CVV / CVC) each time, as well as an additional payment confirmation code, if this is provided for by the issuing bank of the bank card of user 5 (as part of the security protection procedure User’s bank card 5 - Secure code and the like).

User 1 performs registration in the mobile application of the developer 3 by entering: the number of the mobile device of user 2, his name and surname, as well as an email address. To control when registering on the mobile device of user 2, an SMS message is sent with a code to confirm registration. For security reasons, it is not possible to register in the mobile application of the developer 3 without confirmation in the form of entering the code sent to the mobile device of user 2 specified in the registration process.

At the time of registration in the mobile application of the developer 3 (at the beginning of use), user 1 is assigned an identification number (hereinafter - ID). User 1 independently binds to this ID the data of the medium that he plans to use: for the customer’s bank card, 5 is the card number, for the user’s mobile device 2, this is the number of the user’s mobile device 2. User 1 uses the mobile application 4 interface on his user’s mobile device 2. At the same time, he can optionally attach several carriers of one or another type of mobile device or bank card to this ID), as well as replace them while using m stably application developer 3. The set of 'material carrier' '(mobile device 2 a user or customer bank card 5) + entry in a mobile application developer 3 (ID + material carrier number) - this is a universal user 16 skipping 1.

At the time of purchase of a ticket using the developer's mobile application 3, after payment, the developer's mobile application 3 generates a unique electronic ticket number and also binds the client ID to it (only ID, not a bunch of ID + media number, so that the client can pass through with any from registered universal passes 16). This set of '' electronic ticket number '' + '' ID '' - this is the universal identification code (hereinafter - PEC). This PEC is generated in the second server of the developer 12, namely in the processing center of the terminal 13, and is transmitted to the terminal for admitting the user to event 14 and to the client through the first server of the developer 6 and the mobile application of the developer 3 to control the passage of user 1 through the terminal for admitting the user to Activity 14 and resolving, if necessary, possible disputes. Also, the terminal for the user’s admission to event 14 receives the latest information about the bundle (ID + media numbers) of user 1.

At the time of going to event 17, when applying any of the registered media with its number (mobile device of user 2 or bank card of user 5) to the terminal for admitting the user to event 14, the terminal for admitting the user to event 14 checks the following:

a) whether this ID has a right of passage (it is possible that user 1 has the right to several passes if he bought several tickets for one pass),

b) whether this device (user’s mobile device 2 or user’s bank card 5) is tied to user ID 1.

If approved, user 1 goes to event 17.

Thus, the universal pass of the client, the mobile device of user 2 or the bank card of user 5 does not contain electronic ticket data. This information (for resolving possible disputes) is in the terminal for the user’s admission to event 14 and the developer’s mobile application 3 located in user’s mobile device 2. The NFC chip, which is available in user’s universal pass 16, always contains only information regarding this medium (user’s mobile device number 2 or client’s bank card number 5).

User 1 becomes a user of the system after completing the registration procedure in the mobile application of the developer 3.

User 1 of the system Universal Pass 16 searches for the event 17 and the ticket for it. The following selection criteria are available for searching events 17 and tickets for them:

- the city where the selected event 17 will take place;

- the site (name and its exact address) where the selected event 17 will take place;

- key parameters for the search (performance, performer, stage director, etc.);

- place, row, zone at event 17, which the client plans to take;

- ticket price;

- and other parameters for the convenience and completeness of the selection of tickets for events 17.

User 1 selects the desired event 17 and a specific ticket for it, and then carries out the procedure for paying for the selected ticket (one or more) in cash from the bank card of user 5 registered in the mobile application of the developer 3.

User 1 is sent an electronic ticket, one or more, for access to the selected event 17 by means of a CMC message or an email to the email address indicated by the client.

After completing the payment procedure for the selected ticket, the mobile application of the developer 3 generates a unique identification code (PEC), individual for each ticket purchased, which through the mobile application of the developer 3 becomes available to user 1 in his personal account of the mobile application of the developer 3, and is also stored on the first server of the developer 6 and transmitted to them through the processing center of the terminal 13 of the second server of the developer 12 to the terminal for admission of the user to the event 14 and stored in the PEC 15 database to enable the passage of user 1 to event 17.

A PEC (unique identification code) is a unique alphanumeric code that represents an identifier for going to event 17 and allows user 1 to go to event 17 by checking with PECs stored in the database of PEC 15 of the terminal to allow the user to go to event 14 using the developer’s mobile application 3 from the first developer’s management server 6 to the second developer’s server 12 and, accordingly, through its processing center of the terminal 13 to the terminal for user 14 access. information is transmitted via the Internet system.

Thus, the PECs generated by the developer’s mobile application 3 of all users 1 who bought tickets for a specific event 17 are sent to the terminal for admitting the user to event 14 located in the venue (s) of event 17 for subsequent monitoring by checking during the passage to event 17 .

User 1 is at the selected event 17 with the mobile device of user 2 containing the mobile application of the developer 3 with the PEC, and performs the verification of the PEC in the mobile device of client 2 with the PEC contained in the database of the PEC 15 of the terminal for admitting the user to the event 14, and when the successful completion of such reconciliation takes place at event 17. After which, if necessary, it finds its place at event 17, using the data of an electronic ticket sent previously to the mobile device of client 2 or electronically client mailbox.

Description of the developer's mobile application 2.

The developer creates a mobile application of the developer 3 with the functionality to create Universal Pass 16, which can be used to access any events 17 and to other places equipped with appropriate terminals for the user to be allowed to the event 14.

Developer’s mobile application 3 has a web interface adapted for user 2’s mobile devices, where any Internet user 1 gets the opportunity to select event 17 (place of visit), pay for a ticket in his or her other name and then using a unique identifier (PEC), go to the selected event 17 (to the selected place) using the mobile device of user 3 or a bank card of user 5, where the identifier (PEC) is transmitted via the developer's mobile application 3. Thus, the mobile application of the developer 3 allows you to use the mobile device of user 2 or a bank card of user 5 as a universal pass 16 to predetermined venues 17.

Description of the functionality of the mobile application developer 3.

Developer’s mobile application 3 contains the following features:

1. The ability to register and create on the first server of the developer 6 a personal account of a user (not shown) that is protected by unique identification data (login, password), including the identification of user 1 by means of a PEC confirmation code sent via SMS to the number of mobile device of user 2, specified by the user during registration and the creation of a personal account.

2. The possibility of linking, actually fixing in a certain section of the developer's mobile application 3, the bank card of user 4 for subsequent payment of selected tickets via the Internet acquiring service provided by the credit organization of the client to the universal pass developer 16.

3. The ability to select events 17 by city, location, dates, time, exact characteristics of the place, given the occupancy of places by other ticket users and other criteria, including a search for event names 17, organizers, etc.

4. The ability to select and fix a specific ticket indicating the name of the event 17, the venue, as well as other characteristics necessary to attend a particular event 17 selected by the user.

5. The ability to instantly pay for the selected ticket (one or more) by making and the necessary confirmation of payment using a user’s bank card 5 of any payment system through the Internet acquiring process provided to the developer by third-party credit organizations.

6. The ability to store a unique identification code (PEC) for subsequent passage through the terminal for admitting the user to event 14, to event 17 selected by user 1.

7. The ability to store data on purchased tickets and their characteristics in the user's mobile device 2.

8. The possibility of transmitting data in the form of a unique identification code (PEC) to the terminals for admitting the user to event 14, installed in the places of ticket control for events 17 and allowing to compare PECs on the mobile device of user 2 with the database of PECs 15 transferred to the terminal for admission user to event 14 from the first developer server 6.

Developer’s mobile application 3 contains the following features:

1. Possibilities of integration, for example, through the API protocol, with systems and programs of developer partners that provide services for selecting and buying tickets for events, including the full functionality of the services of such partners.

2. The ability to provide user 1 with the choice of tickets to events 17, booking and paying for such tickets, as well as storing PECs in a common database and customer orders database as part of his personal account, that is, the developer’s mobile application 3 environment containing user registration data, user card information 5, as well as data on orders made and paid for events 17.

3. The ability to organize the process of paying with a user’s bank card for 5 tickets selected by the user using the Internet acquiring service provided by third-party credit organizations engaged by the developer.

4. The ability to create and store personal accounts of users 1, access to which is carried out using the identification data (login and password) of a specific user 1.

5. The ability to record data, store databases and transfer data to user devices 1.

6. The possibility of generating a unique identification number (PEC) for transferring it to the terminals for the user’s admission to event 14 and taking into account such PEC codes to ensure unauthorized access to events 17.

7. The ability to exchange data via the Internet using various information transfer technologies, such as NFC and similar, with all third-party devices and systems as part of the registration, storage and transmission of data, in order to ensure the processes of selection, ordering and payment of tickets, organization of passage to events 17 and all other interaction processes within the service.

8. The ability to ensure the proper level of security for payments and storage of personal and other data.

The terminal for admitting a user to event 14 contains the following functionality:

1. The ability to interact with the mobile application of the developer 3 via the Internet using various information transfer technologies, such as NFC and similar, for the purpose of receiving, sending and storing unique identification codes (PECs).

2. The ability to exchange data with the mobile device of user 2 or a bank card of user 5 for the purpose of checking the availability of PECs and verifying the compliance of PECs with the data transmitted by the mobile application of the developer 3, to control the passage to event 17 and to ensure the passage of only those clients whose PECs coincide with those PECs received from the mobile application of the developer 3 for access to a specific event 17.

3. The ability to send signals (audio and text) when passing through the terminals to allow the user to go to event 14 to ensure the transmission of a positive or negative response to the request for PECs (there is such a PEC for passing to this event 17 or in the PEC 15 database of the terminal for user access to event 14 is not).

4. Redemption of PECs (changing the status to “passed, re-entry prohibited”) in the case of passage to event 17 of user 1, who received it, to prevent situations of re-passage of one PEC. Providing follow-up control of canceled PECs for the purpose of providing complete information about the passage through a specific PEC in the event of a dispute.

The sequence of actions and events within the framework of the creation and functioning of the system.

The developer creates a mobile application of the developer 3 and places it on the first server of the developer 6 with the software core of aggregation of tickets 7. The mobile application of the developer 3 has a website located on the Internet and its adapted version for downloading (downloading) to the mobile devices of client 2.

The mobile application of the developer 3, located on the first server of the developer 6, which manages the site, is a complex of software codes and solutions that enable the functioning of the system and its interfaces. When using the system, all operations of all clients and administrators take place within the software on the first server of the developer 6.

The user part of the mobile application of the developer 3 allows users 1 using the interface of the mobile application of user 4 to carry out all operations provided by the system’s functionality. Access to the developer's mobile application 3, located on the first developer's server 6, is provided to users via the Internet through the website using the developer's mobile application 3. Moreover, access to the developer's mobile application 3 is provided to users through official online stores of applications of program and application providers for client 2 mobile devices (AppStore, Google Play and the like).

The mobile application of the developer 3, located on the first server of the developer 6, aggregates all the information about the actions performed by the user, exchanges data with the databases of the servers of the issuers 10 through the interface for issuing tickets 11; with a processing server 7, providing processing of bank cards of client 4; with the server of the terminal 12 and, accordingly, with the processing center of the terminal 13, which provides data processing for passes in the terminal to control the passage 14, as well as with all other systems and databases as part of the system’s functioning.

Developer’s mobile application 2 generates a PEC (unique identification code), which is a unique alphanumeric code, which is an identifier for going to event 17 and allows you to identify the client of the system.

The user of the system gets access to the databases of the servers of the issuers 10 through the mobile application of the developer 3 through the website. Thus, the user 1, downloading (downloading) to the mobile device of the user 2 the mobile application of the developer 3, gets access to the databases of the servers of the issuers 10, as well as to all other functional capabilities of the system.

In the environment of the mobile application of the developer 3, user 1 is given the opportunity to register (link) a bank card of user 5, which, in turn, allows user 1 to pay for the selected tickets and purchase them within the framework of the mobile application of developer 3, located on the first server of the developer 6.

Using the system allows the following sequence of actions of user 1 using the mobile application of the developer 3. The developer creates and places on the website - the first server of the developer 6 _ the mobile application of the developer 3 and its version adapted for use on mobile devices of user 1.

User 1 installs (downloads, downloads) the mobile application of developer 3 on his mobile device of user 2 and registers it in his special section, and also registers his bank card for user 5. The mobile application of developer 3 saves personal data in his database on the first server of developer 6 user 1, his registration data for entering his personal account, registration data of a bank card of user 5 and other data of user 1, forming from them a personal account of a user Spruce 1, where all the information indicated above and the archive of user orders 1 are stored.

At the same time, the environment of user’s personal account 1 is properly protected from third-party users, located and stored on the first server of the developer 6. If you intend to use the system, user 1 must enter the environment of your personal account as part of the developer's mobile application 3 by entering the login and password assigned by the user 1 when registering in the developer's mobile application 3. In the personal account environment, user 1 has the opportunity to select and purchase a ticket, as well as use all other functions national capabilities of the system.

When buying tickets, the mobile application of the developer 3 initiates the procedure for paying for tickets in cash from the account of the bank card of user 5, the data of which was entered by the user in a special section of the personal account of user 1 in the mobile application of the developer 3.

Payment for tickets is made in the mobile application of the developer 3 through the Internet acquiring service within the payment systems provided to the developer by third-party credit organizations.

After the payment procedure is completed, the mobile application of the developer 3 generates PECs for each ticket 1 paid by the user and sends it to the terminal for admitting the user to event 14 for reconciliation during the passage to event 17, and also stores it in its database PEC 15 and in the personal environment user account.

The PECs transmitted by the developer's mobile application 3 are stored in the databases of the second developer's server 13 and in the terminal for admitting the user to the event 14 to ensure reconciliation with the PECs of users as part of the procedure for accessing the events 17.

When going to event 17, user 1 presents his universal pass 16, containing PECs (one or several), for reconciling such PECs with PECs contained in the database of PECs 15 of the terminal to allow a user to take part in event 14 that performs such a check even if PECs match the client and the PEC, transmitted by the mobile application of the developer 3 and stored in the terminal for admitting the user to event 14, gives a signal about the possibility of the passage of user 1 of the system to event 17.

The main advantages of the "Universal Pass" for individual customers:

the convenience of using your own mobile device or bank card as a Universal Pass;

- reduction of time costs for printing, storage and other actions that must be performed with traditional tickets for events;

- ease of use - the client no longer needs to store tickets and monitor their safety.

The main advantages of the Universal Pass for legal entities-organizers and event owners:

- reduction of costs for the implementation of the processes of passage of individuals to the event;

- increase the speed of control processes during the passage to the event;

- Automation of the process of admission to the event.

All of the above confirms the fulfillment of the task and the industrial applicability of this method.

The list of positions:

1. User

2. User’s mobile device

3. Developer mobile application

4. Mobile application user interface

5. User bank card

6. First developer server

7. Ticket aggregation software core

8. Processing server

9. Card processing processing center

10. Issuer's server

11. Ticket Issuing Interface

12. Second developer server

13. Processing center of the terminal

14. Terminal for access control

15. DEC databases

16. Universal pass

17. Event

Claims (1)

A method of creating a universal pass for admitting a user to events consisting in using a mobile application of a developer located on the first server of a developer, in this case a mobile application of a developer is downloaded to a user's mobile device from the application store, a user's mobile device is registered in the mobile application of the developer, and also a bank card user, and at the time of registration in the mobile application of the developer, the user is assigned an identification this ID number, then the user carrier data is tied to the user ID using the device’s mobile application interface: for the client’s bank card, this is the card number, for the user’s mobile device, this is the number of the user's mobile device, the necessary tickets for the event are generated in the developer's mobile application through the software the ticket aggregation core, located on the first developer's server, using the ticketing interface located on the issuer’s server, then the payment procedure for the selected ticket in cash by the client’s bank card registered in the developer's mobile application, and at the time of purchase of the ticket, after payment, they form a unique electronic ticket number using the developer's mobile application and attach the client ID to it, and this combination is the number of the electronic ticket plus ID - this is the universal identification code - PEC, which is a universal pass to the event, while providing the client with the opportunity to pass from the register universal pass, and this PEC is formed in the first developer server, transferred to the processing center of the terminal of the second developer server and then transferred to the terminal for admitting the user to the event, as well as to the user through the first developer server and the developer’s mobile application to control the user’s passage through the terminal and the user’s admission to the event, at the same time, to the user’s admission to the event, they transmit relevant information about the bundle - ID unique number electronic ticket, and at the time of going to the event, when applying the universal pass of the user's mobile device or user’s bank card with its number to the terminal for admitting the user to the event, the terminal checks the PEC stored in the developer's mobile application with the PEC stored in the developer’s mobile application database of the terminal PEC for the user’s admission to the event, and upon successful completion of such verification, the terminal signals the possibility of the user passing through an event, moreover, the NFC chip available in the user's universal pass always contains information regarding this medium — the number of the user's mobile device or the number of the client’s bank card, thus providing the user with access to the event, after which they find the user's place at the event using data an electronic ticket sent earlier to the client’s mobile device or to the client’s electronic mailbox, and all information is transmitted via the Internet.

Images