ACCESS CONTROL SYSTEM FOR PREMISES

Abstract

An access control system for a premises includes a first scanning device for detecting when an individual having an authorized presence in a unique location in the premises has left the premises, the individual having a handheld device; a second scanning device for determining a location of another individual who is not in the premises, the another individual having another handheld device; nd a server computer in communication with the first scanning device, the second scanning device, the handheld device and the another handheld device, the server computer determining from the first scanning device that the individual has left the premises, and upon said determining, further determining whether the another individual is within a predetermined proximity to the premises, and authorizing access to the unique location in the premises to the another individual if the another individual is within said predetermined proximity.

Claims

1. An access control system for a premises, comprising: a first scanning device for detecting when an individual having an authorized presence in a unique location in the premises has left the premises, the individual having a handheld device; a second scanning device for determining a location of another individual who is not in the premises, the another individual having another handheld device; a server computer in communication with the first scanning device, the second scanning device, the handheld device and the another handheld device, the server computer determining from the first scanning device that the individual has left the premises, and upon said determining, further determining whether the another individual is within a predetermined proximity to the premises, and authorizing access to the unique location in the premises to the another individual if the another individual is within said predetermined proximity.

2. The access control system of claim 1, wherein the first scanning device includes one of an NFC, RFID, or optical scanner, and a geolocation system.

3. The access control system of claim 1, wherein the second scanning device includes a geolocation system.

4. The access control system of claim 1, wherein said authorizing access includes transmitting a scannable barcode or QR code image representing a right to occupy the unique location to the another individual.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0034] Various embodiments of the present invention are described below by reference to the following drawings, in which:

[0035] FIG. 1 is a schematic diagram showing the components of the desired system including a mobile application, a web site, the internet, and a back end system including a ticket transaction server and a user database;

[0036] FIG. 2 is a schematic diagram showing a ticket holder and late arriver connected through the software application;

[0037] FIG. 3 is a schematic diagram showing that while inside the venue, the ticket holder has ownership of the ticket information;

[0038] FIG. 4 is a schematic diagram showing that upon or prior to exit of the venue, the ticket holder will provide ticket information to the software application;

[0039] FIG. 5 is a schematic diagram showing that shows that once the ticket holder leaves the venue, the software application will have ownership of the ticket information;

[0040] FIG. 6 is a schematic diagram that shows how the late arrival is able to search for available tickets inside the software application;

[0041] FIG. 7 is a schematic diagram that shows the software application sending a push notification to the late arriver of tickets representing vacated seats or space available for events they may be interested in;

[0042] FIG. 8 is a schematic diagram that shows the late arriver purchasing a ticket for the previously used seat or space from within the software application;

[0043] FIG. 9 is a schematic diagram that shows that at the venue gate, the gate staff verifying the purchase of the ticket;

[0044] FIG. 10 is a schematic diagram that shows that the ticket information will belong to the late arriver;

[0045] FIG. 11A illustrates a screen display with which users create an account via a web site;

[0046] FIG. 11B illustrates a screen display with which users create an account on via a mobile device;

[0047] FIG. 11C illustrates a screen display on a phone or other mobile device showing a potential late arrival being notified of an event that meets her/his preferences;

[0048] FIG. 11D illustrates a screen display on a phone or other mobile device showing a likely early exit being asked to confirm if they did in fact leave;

[0049] FIG. 11E illustrates a screen display on a phone or other mobile device showing events being recommended to a user;

[0050] FIG. 11F illustrates a screen display on a phone or other mobile device showing an alert that an event is coming up that may be of interest to a user;

[0051] FIG. 11G illustrates a screen display on a phone or other mobile device showing an alert to a potential active seller to ask how much they might be induced to sell their ticket for; and

[0052] FIGS. 12(a) through 12(d) are flow charts which illustrates process steps in accordance with embodiments of the present invention.

DETAILED DESCRIPTION

[0053] The process, methods, and systems in accordance with various embodiments of the present invention create a tertiary market for previously occupied seats and space. In accordance with these embodiments, a method is provided for selling tickets for seats and space that have been previously occupied. A ticket is sold when a seller (an early exit) who may intend to leave, or already has left a venue early, so notifies the system, so that a buyer (the later arriver), who is interested in attending the event for the remaining duration of the event, can make a purchase of the right to use the previously occupied seat or space.

[0054] Preferably, but not necessarily, several operating assumptions may include: (i) tickets for previously used seats or space sold through system are not resold for more than the face value of the original ticket; and, (ii) it is expected that some potential buyers may choose to purchase tickets for previously used seats or space for a portion of an event instead of purchasing other tickets available through the primary or secondary resale marketsi.e., some consumers will accept missing a portion of an event rather than paying inflated resale prices for unused tickets.

[0055] Data and analytics about the motivations, timing, and destination of those who leave early may be of value to venues, promoters, and artists. Presently events, venues, and conferences may have difficulty tracking when attendees leave events despite the commercial value of such information.

[0056] In accordance with an embodiment of the present invention, a computerized method is provided for providing a tertiary market for resale of a previously occupied seat or space upon the departure of an original ticket holder from an event while the event is in progress at a venue, as well as a computerized system for implementing this method. The method includes electronically tracking when the original ticket holder has left the event; preferably electronically communicating with the original ticket holder to confirm exit; electronically offering a ticket for the previously occupied seat or space to a third party that is not in the venue; electronically processing the sale of the ticket for the previously occupied seat or space; electronically transmitting to the third party a ticket; and electronically transmitting to the venue a record of the ticket for the use of the previously occupied seat or space. In this regard, the step of electronically tracking may further comprise scanning, at an exit of the venue, the original ticket, with a hand-held device (such as a hand-held scanner held by a gate attendant) or at a scanning kiosk located at the venue exit. The step of electronically tracking may alternatively or further comprise the use of geolocation technologies such as but not limited to GPS, Beacons, ibeacon location and proximity detection technology, and other networked and static systems for identifying location of both the original ticket holder and a third party. The step of electronically offering a ticket for the resale of the right to occupy a previously vacated seat or space may further comprise the original ticket holder offering their occupied seat or space for resale using a hand-held device such as a mobile phone, a watch, or a tablet. The step of electronically processing the resale of the right to occupy a previously vacated seat or space may further comprise receiving, at a server, information from the original ticket holder's handheld device sufficient to indicate the offer for resale, transmitting, from the server, the offer for resale to a plurality of third party users (e.g., to a user's mobile phone); and receiving, from one of the plurality of third party users, information sufficient to process the resale of the right to occupy a previously vacated seat or space.

[0057] Embodiments of the subject matter described herein may be implemented in digital electronic circuitry, or in computer software, firmware, or hardware, or in combinations of one or more of them. Embodiments of the subject matter described herein can be implemented as one or more computer programs, for example, one or more modules of computer program instructions, encoded on computer storage medium for execution by, or to control the operation of, data processing apparatus. A computer storage medium can for example, be, or be included in, a computer-readable storage device, a computer-readable storage substrate, a random or serial access memory array or device, or a combination of one or more of them.

[0058] The process steps and operations described herein can be implemented as operations performed by a data processing apparatus on data stored on one or more computer-readable storage devices or received from other sources. As used herein, data processing apparatus encompasses all kinds of apparatus, devices, and machines for processing data, including by way of example a programmable processor, a computer, a system on a chip, or multiple ones, or combinations thereof. The apparatus can include, or even consist of, special purpose logic circuitry, e.g., an FPGA (field programmable gate array), state machines, sequencers, or an ASIC (application-specific integrated circuit).

[0059] A computer program (for example, a program, software, software application, application, script, or code) can be written in any form of programming language, including compiled or interpreted languages, declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, object, or other unit suitable for use in a computing environment. As used herein, the term app or mobile app is meant broadly to include, for example, an executable binary that is installed and runs on a mobile device, or a web site that the user navigates to within a web browser on the mobile device, or a combination of them. An app may also refer to multiple executable binaries that work in conjunction on a mobile device to perform one or more functions; for example, an Android service and an Android application that communicate with one another.

[0060] The process steps described herein can be performed by one or more programmable processors executing one or more computer programs to perform actions by operating on input data and generating output. The processes can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array), a sequencer, a state machine, or an ASIC (application-specific integrated circuit).

User Experience

[0061] The various embodiments of the present invention can be viewed from the perspective of the late-arrival ticket holder/buyer and from the perspective of the early-leaver ticket holder/seller.

Late Arrival Ticket Holder User Experience

[0062] The late arrival ticket buyer is a fundamental user of the process described herein. The late arrival may introduce new value into the ticket and event ecosystem by 1) buying the unwanted/unused time from the early exit, 2) buying additional concessions or merchandise the early leaver would not have otherwise bought, 3) exposing themselves to advertising impressions, and, 4) paying fees to participate in the ecosystem.

[0063] The late arrival may be a person who: (i) values a ticket or a certain class of tickets in the event highly enough that they choose not to buy tickets available at face value (primary market) or above face value (secondary resale market), instead trading time for seat preference; (ii) is making an impulse purchase based on factors such as proximity (i.e., they are near the arena) and/or interest (e.g., a close game); (iii) wanted to attend an event but, was closed out due to a sold out situation, and/or (iv) is issued an invitation to attend the event based on factors such as proximity and user interest

[0064] In each of these scenarios, the late arrival ticket holder's interest in an event does not end once an event begins and he/she is willing to enter an event after it has started.

[0065] In accordance with various embodiments of the present invention, the late arrival user may indicate his/her interest in an event in a number of ways.

[0066] For example, the late arrival user may indicate interest in various events or classes or types of events as part of their user-profile when they initially register on the system, for example by entering registration data into the system over the internet from a computer, smart phone, tablet or other computing device. The profile can later be updated by the user in the same manner to indicate interest in different or additional events or classes or types of events.

[0067] The late-arrival user may have tried to acquire tickets to an event from the primary ticket source, only to learn that the event was sold out. The user may then be directed to connect with the system of the current invention to register as a person that is interested in that specific event, should seats or space become vacated. The system of the current invention would provide a path for the user to attend an event that has already commenced, as an alternative to having to pay secondary market prices for original tickets, which are often much higher than face value of the original ticket. The system server may also notify the user of vacated seats or space at that event, either through the mobile app or via a text message as illustrated in FIG. 11F.

[0068] The late-arrival user may also or alternatively be notified by the system of an event. For example, a data processing device such as a system server may transmit notifications of events to the late-arrival user via a mobile app on the late-arrival users smart phone, tablet, or other computing device, via text message, or via email. For example, the mobile app could display upcoming events on the display screen of the user's phone as illustrated in FIG. 11E, and the user could respond by clicking (or otherwise entering via the phone interface) interested, and this interest would then be transmitted via the mobile app to the system server. The system server may also notify the user of an individual event prior to the event, either through the mobile app or via a text message as illustrated in in FIG. 11F. In this example, the user can indicate interest, for example by clicking (entering) Yes. The user may also search through a listing of events in geographic proximity to late arrival's current location either via the mobile app or on a website.

[0069] In certain embodiments, prospective late arrivals use a mobile app, system web-site, or other application to select local events that they'd like to attend, optionally coupled with information such as preferred music genres, bands, and sports teams. This preferred event information is stored in a user profile data store with the system and is optionally used as an input to the algorithm used to suggest events. As an example, a system website, for example as illustrated in FIG. 11A, may prompt the user to enter data into data fields such as name, username, password, email, mobile phone number, payment information, preferred music genres, bands, and sports teams. This data can be entered in any conventional manner, such as through key entry, radio boxes, drop down menus, and the like. The user would then submit the registration, for example, by clicking on a submit registration button. The data can also be entered via a mobile app in the same manner as illustrated in FIG. 11B.

[0070] Based on these user preferences, the system, for example via an application(s) on the system server, will propose a list of current and upcoming events that are happening within a user defined radius of his/her current location, and transmit that information to the user via a mobile app, email, and/or text.

[0071] Further, using the notifications functionality of both iOS and Android subsystems, users may also elect to be notified of events that meet their specific criteria (time range, distance, and event type). The application may utilize current and future geolocation technologies including GPS, beacons, etc.

[0072] For example, when a ticket for a vacated seat or space becomes available, a push notification through services including SMS, Email, Instant Message, Direct Message, etc. can be sent to the mobile device of a potential late arrival through the mobile app. Alternatively, such notification could be pushed to a mobile device of a late arriver, without regard for whether a mobile app has been installed on the mobile device. When the push notification is received, the late arriver can purchase the ticket through the mobile app and the ticket is made valid for their entry. Alternatively, the push notification could, for example, include a URL link to a system website which, in turn, will prompt the user to enter information sufficient to purchase the ticket.

[0073] When the late arriver arrives at the venue, they will utilize use their mobile device to enter. Their valid ticket can be captured, for example, through UPC, RFID, or NFC communications through an electronic scanner as they enter. Alternatively, the late arriver may have received a previously unenabled RFID enabled wristband, in which case at the time of purchase, the RFID wristband would be enabled, and the RFID wristband possessed by the original ticket holder would be deactivated.

[0074] The process, methods and system of the present invention may use integration with the venue or promoter or event's access control or ticketing system to ensure the validity of the ticket. In other words, the system may validate the validity of the original ticket through communication with the venue, the issuer of the original ticket, or their agents and partners.

Early Exit Ticket Holder User Experience

[0075] The early exit ticket holder is the source of tickets for the late arrival ticket holder. Ticket inventory available for purchase by late arrivals can be made available through a number of methods.

[0076] As an early exit ticket holder leaves an event in progress, he or she may scan out at an electronic kiosk or via an exit RFID or NFC scanner. The early leaver will scan her/his ticket upon exit at a kiosk or scanner that will enter their ticket into the system. These kiosks may be located outside of the secured area where incoming tickets are scanned. Once the early leaver scans out, the system can immediately make available a ticket to the event in progress.

[0077] The early exit ticket holder can also be identified through any geolocation technology such as Venue or Event's access control system or GPS, beacons, and the like to record the exit. The early leaver may also be asked to confirm their exit, for example, via a mobile app on a mobile device such as a phone or tablet.

[0078] The exit of the early exit ticket holder can also be identified implicitly as ticket exit data scanned through UPC, RFID, or NFC communications.

[0079] The early exit ticket holder can also be identified shortly after an early exit leaves an event. This can be done, for example, via geolocation technology establishing location or early exit and a notification sent via the mobile app asking an early exit if they have left an event.

[0080] The system described herein allows venues to make or use any or all of the above methods of making ticket inventory available for purchase by late arrivals.

[0081] As outlined above, one scenario is for early exits to explicitly indicate their departure through active means when they leave the arena. This approach may minimize the time between departure and the availability of a ticket for sale based on a vacated seat or space. It also provides an opportunity to capture the departure event, as well as, optionally, some information about why and to where the early exits are going.

[0082] The system and process additionally enables passive recapture of seat and space inventory through tracking exits. Passive exits, in some cases based on various venue and market conditions, may not be compensated for subsequent sales of their used tickets. The aggregate preferred embodiments allow early exits to leave the arenai.e., passive exitsthrough means such as NFC (Near Field Communication), RFID ID, and location based services.

[0083] In accordance with certain embodiments of the present invention, the system provides rewards to the early exit ticket holders in order to induce them to make tickets available.

[0084] The early exit ticket holder may have his ticket registered in the system in a number of ways. For example, as part of the ticket purchase process, the user can register with the system or provide their username and password so that the purchased ticket is associated with their email address and/or cell phone number so that they can actively participate in the system and obtain rewards. An early exit ticket holder may be provided with a downstream incentive to encourage registration at the time of purchase, such as increased revenue sharing possibilities, or bonus loyalty rewards. However, it is also possible for a venue to recapture tickets when a ticketholder leaves a venue with a no re-entry policy (either actively, for example, by scanning by a gate agent, or passively, for example via geolocation technologies) and resell the vacated seat or space without the knowledge or participation of the early exit ticket holder.

[0085] Reward options and inducements made possible through the systems and processes may include, but are not limited to: (i) credited event time that may be stored for use towards future events or tickets; (ii) points that can be redeemed towards the purchase of merchandise or exclusive offers (which has the potential to increase revenue for the venue and/or system provider); (iii) cash refund for partial unused time; (iv) special offers from third parties; and (v) donations made to charitable organizations.

[0086] Finally, the system may provide the option for the user to set a desired cash price for sale of their vacated seat or spacethrough the system. For example, a potential early exit ticket holder may indicate through the mobile app that he or she is willing to leave the venue and make the seat or space available for $15.00. The system could then, for example charge a processing fee to the late arrival user (for example $2.00).

System Overview

[0087] In accordance with a preferred embodiment of the present invention, the components of the system include a mobile app, a web site, the internet, a back-end server system in which user information is stored and transaction processing occurs at least in part, and a ticketing system server, which may or may not function, at least in part, as the transaction processing server.

[0088] Following discovery by consumers of the application a new user registers. Registration can be implemented in a number of ways. For example, a user can register on a web site, accessed through a computer or mobile device (FIG. 11A). Alternatively, after downloading the application from locations such as the iTunes store for iOS devices or Google Play for Android devices (FIG. 11B).

[0089] In a preferred embodiment, during registration, users provide some or all of the following information:

[0090] Data to Create an Account:

[0091] a. Email

[0092] b. Password

[0093] c. Users may also be provided with the option to authenticate via OAuth providers accessed by the system via mechanisms such as RESTful APIs and secure HTTP.

[0094] Demographic Data

[0095] a. Name

[0096] b. Street Address

[0097] c. City and State

[0098] d. Zip

[0099] e. Mobile Phone

[0100] Communications Preferences

[0101] a. Opt-inText

[0102] b. Opt-inEmail

[0103] Optional Profile Information

[0104] a. Default Payment Type

[0105] b. Event Type Preferences

[0106] c. Arena Preferences

[0107] d. Favorite Sports and Teams

[0108] e. Music Preferences

[0109] f. Season ticket ownership

[0110] g. Geographic Tolerance Threshold

[0111] Notification Types and Method [Alters, Banner, Email, Text]

[0112] a. Upcoming event

[0113] b. Buy opportunity during event

[0114] c. Sell opportunity during event

[0115] Intended Uses (Users may select both)

[0116] a. Buyer (the user intends to be a late arriver who will buy used tickets)

[0117] b. Seller (the user intends to be an early exit who will sell used ticket)

Pre-Event

[0118] The embodiments allow the system to track interest in both selling and buying tickets for vacated seats or space.

[0119] In a set interval, for example between seven and one day(s), before an event, the system, in its role of market maker, estimates potential buyer (late arrival) and seller (early exit) interest based on explicit interest through the application, and heuristics based on user profile data. This data becomes 1) an input to pricing and 2) is used to prompt sellers and buyer during the event itself with customized notifications.

[0120] As illustrated in FIG. 11E, the same screen may be used to both collect potential buying interest as well as to record those users who already hold tickets, and hence may be potential sellers. This data can be used to estimate potential buyer (late arrival) and seller (early exit) interest using conventional statistical methods.

[0121] The system, in its role of market maker, allows users to register interest of attendance and at what price, prior to the event start.

In-Event

[0122] During an event, registered users who have also identified themselves as ticket holders may be prompted with reminders, through notifications wirelessly transmitted to their wireless devices of the opportunity to leave early and resell their vacated seats or space, including reminders of any venue or third party inducements offered for leaving early exits. Venue inducements are at the discretion of the venue alone. Notifications may also include the announcement of a bid from a Late Arrival seeking entrance to the event.

[0123] In one embodiment, the system proposes a suggested price to ticket holders at which they should consider vacating their seats and posting their seat or space as being available. This is the initial ask price and is set algorithmically based on, or as a function of, one, some or all of the following inputs: [0124] (a) Whether the event is sold out (Higher demand correlates to a higher proposed initial price); [0125] (b) Number of other system users in the venue who have identified themselves as being potential early exits (Less interest in correlates to a higher proposed initial price); [0126] (c) Number of potential late arrivals (More interest correlates to a higher proposed initial price); [0127] (d) Weather at the time of the event; [0128] (e) The score of the event if it is a sporting event; and [0129] (f) Time left in the event (More time remaining) correlates to a higher proposed initial price) [0130] (g) As the event continues, the algorithm to create the suggested selling price may also incorporate as variable the number of transactions for the same event that have closed within the last 5 minutes.

[0131] The ticket holder may also be able to override the suggested price and input any price they desire within system and event level parameters.

[0132] The system enables any ticket holder who has left a predetermined geolocation boundary or geofence for a certain amount of time or distance from geofence, to be notified of opportunity to post their tickets. This early exit may be done actively through the RFID wristband scanning at a kiosk or through any venue or event ticketing or access control system.

[0133] Early Exits may be identified and messaged through integration with a venue's ticketing and access control system, and/or through any and all geolocation technology including geofencing, GPS, beacons, etc. that can be utilized to detect a user's entrance and egresses from a venue. Data captured on Early Exits may include Gate location of exit, time of exit, direction of exit and location heading next.

[0134] Concurrently during events, potential buyers (late arrivals) are sent notifications as seats and space are vacated and tickets become available that meet their interests and are in their geographic tolerance threshold.

[0135] In this way, through prompting via notifications to potential sellers and buyers, the system may continuously and iteratively make the market for tertiary tickets. In alternative embodiments, no notifications are required and all activity occurs as a pull by potential sellers and buyers.

[0136] The desired embodiments also enable venues to release unused inventory to the tertiary market after a certain cut off period (e.g., the end of half time in a football or basketball game).

TransactionMatching of Buyers and Sellers

[0137] Referring to FIG. 2, tickets made available through the system belong to the initial ticket holder 101 (the seller or early exit) and will have been redeemed for use at event 201. The method and/or channel through which ticket holder 101 initially obtained the ticket are irrelevant so long as the ticket is valid and can be authenticated inside ticket verification system 305.

[0138] The systems and processes described may enable a number of transaction flow variants. Venues may choose which variant to enable. Common to both variants is that: [0139] (a) Users of the system, both early exits and late arrivals, install the application and register for an account before a transaction occurs; [0140] (b) Prospective Early Exits have registered that they hold tickets to an event; [0141] (c) Prospective Early Exits indicate that they have arrived at an event, or the system identifies they have arrived at an event through an integration with the venue or event's ticket or access control system; [0142] (d) Early Exits are prompted to set a minimum price at which they would be willing to sell a ticket; or they are notified of the amount they will receive or inducement they will receive if they leave the event prior to conclusion if a Late Arrival purchase a ticket for their vacated seat or space; and [0143] (e) Late Arrivals are prompted to set a maximum price at which they would be willing to buy a ticket or to select from a listing of tickets at a certain price point, which may be dynamically changing.

[0144] A first scenario is a direct, synchronous ticket to ticket transfer from early exit to later arrival. In this scenario the license to use a seat or space is passed directly from seller to buyer.

[0145] A second scenario is an asynchronous transfer of the license to use a seat or space at an event whereby the ticket is sold to the late arrival at the same time that the previously issued original ticket is cancelled or deauthorized for entry. In this scenario, the seller and buyer payment processing are asynchronous or close in time.

[0146] In both scenarios the flow of system enabled activities may include the following:

[0147] User has downloaded app;

[0148] User opens app and sees list of events in progress;

[0149] User clicks on an event;

[0150] User registers for an account if they don't already have one; and

[0151] If a ticket is available, [0152] a. The ticket buyer can accept price and complete the transaction, OR [0153] b. They can provide a new bid, OR [0154] c. They can disregard and continue browsing.

[0155] A user can purchase multiple tickets and share these tickets with friends or other Users, including possibly through SMS/Email/IM.

[0156] A user may link to a webpage the renders a new ticket QR code or registers mobile device for RFID or other mobile technology.

[0157] The new entrance ticket code may include branding and sponsor messaging and will preferably have a high error tolerance threshold.

[0158] For the early exit, the flow of system enabled activities may be as follows: [0159] (i) The early exiter is notified of a potential price for the ticket sale; [0160] (ii) The inventory is updated to reflect the availability of vacated seats or space; and [0161] (iii) If the early exiter is leaving, they may scan the ticket at the kiosk, via barcode, QR code, or RFID to confirm departure.

[0162] Both scenarios commence with the original ticket holder (the early exit) leaving the event. Referring to FIG. 4, when the ticket holder 101 decides to leave the event 201 before the event is complete, the ticket is made available through the ticket transaction system 303 on the ticket holder's mobile phone.

[0163] FIG. 5 illustrates a possible procedure for ticket holder 101 to make their vacated seat or space available for resale. Ticket holder 101 will open the software applicationon the ticket holder's mobile device and look up his ticket information 401 through a process that uses ticket verification system 320. Once the ticket information 321 has been located, the ticket holder associates that ticket with his/her account and marks the ticket as available. Ticket holder then leaves event 201 and the vacated seat or space is then available for purchase.

[0164] FIG. 6 illustrates that a late arrival may use the software application to locate vacated seats or space made available for resale. FIG. 7 illustrates that the software application may send a push notification to the late arrival of tickets available for events in which they may have interest.

[0165] The late arriver may purchase tickets (FIG. 8) through the application and will be allowed entry into the event using the remaining time available on the ticket holder's original purchase (FIG. 9).

Revenue Model

[0166] An exemplary revenue model is based on selling this service as an optional add-on or upsell during the initial ticket buying experience. By participating in the service, a ticket buyer can earn back a portion of their purchase price in the event that the depart an event early and a late arriver purchases a ticket for their vacated seat or space. A per ticket or per order fee may be charged as part of the same transaction or a separate, distinct transaction. Any ticket holder who purchases this service is either registered automatically or is provided a notification or link or email to download and register for this service in order to have opportunity to post tickets upon Early Exit.

Exemplary Process Flows

[0167] An exemplary process flow of the system can be illustrated with reference to FIGS. 1 through 10. An exemplary system includes mobile apps 302 executing on phones, tablets or other mobile computing devices, a system website 301 and a backend system which may include a ticket transaction system or server 303 and user database 304. The website 301 and mobile apps 302 communicate with the backend system over the internet as shown. The ticket transaction server 303 may communicate with the database 304 over the internet, or can be connected directly or through a local area network, or otherwise.

[0168] A User can register with the system as described above either through the mobile app 302 or through the website 301.

[0169] The system software applications 301-304 allow a ticket holder 101 at an event at venue 201 to indirectly connect to a prospective late arriver 102 (FIG. 2). While inside the venue 201, the ticket holder 101 has ownership of the ticket information 401 (FIG. 3). Upon or prior to exit of the venue, the ticket holder 101 will provide ticket information 401 to the software application 301-304 (FIG. 4) or authorize the original ticketing entity to provide the information. For example, the ticket holder 101 may indicate, through the mobile app 302, that they are willing to leave the venue for a given incentive. Once the ticket holder 101 leaves the venue 201, the software application 301-304 takes ownership of the ticket information 401 (FIG. 5). This change in ownership can occur actively, for example by scanning the ticket (paper or electronic) at a kiosk or by a gate agent; or can occur passively, for example using geolocation technologies such as but not limited to GPS, Beacons, ibeacon location and proximity detection technology, and other networked and static systems for identifying the locations of both ticket holder and third party. Change in ownership refers to the right of the software application to offer for sale a ticket for the vacated seat or space. In some instances, the original ticket issuer may create a new ticket and the application will merely be presenting that the new ticket for the vacated seat or space is available for purchase.

[0170] A late arriver 102 is able to search for available tickets 401 owned by the software application 301-304 (FIG. 6). Alternatively, or additionally, the software application 301-304 will send a push notification to the late arriver 102 through the mobile app 302 of tickets 401 available for events they're interested in (FIG. 7). Using the mobile app 302, the late arriver 102 can purchase the ticket for the previously occupied seat or space within the software application 301-304. In this regard, the mobile app 302 communicates with the ticketing transaction server 303 to purchase the ticket. When the later arriver 102 arrives at the venue gate, the late arriver 102 will show the electronic receipt 403 on his mobile device to the gate staff 402, and the gate staff 402 will verify that the ticket 401 is valid by communicating with the software 301-304, or an electronic wallet that previously obtained the ticket information from the software, for example, via a computing device (FIG. 9). The electronic receipt, which preferably includes a barcode, serves as a ticket for the resold seat or space. As used herein, a barcode is an optical, machine-readable, representation of data which is sufficient to uniquely identify the ticket to the venue. For example, the barcode could be, for example, linear or matrix barcodes. The gate staff 402 may use a scanner connected to a mobile app to communicate with the ticket transaction server 303 to confirm the validity of the resale ticket.

[0171] Preferably, only once the purchase is confirmed, does ownership of the ticket information pass to the late arriver (FIG. 10). In this regard, the system can set a time limit on the validity of the late arriver ticket. In this instance, ownership refers to the right of the late arriver to use the ticket to access the previously occupied seat or space. Alternatively, ownership of the ticket information can pass to the late arriver upon purchase.

[0172] FIG. 12(a) is a flow chat which illustrates process steps in accordance with an embodiment of the present invention. At step 500, while an event is in progress, the system electronically tracks when a ticket holder has left the event. At step 510, the system electronically offers the ticket for resale to a third party. At step 520, the system electronically processes the resale of the ticket, and at step 530, the system electronically transmits to the third party a resale ticket; and electronically transmits to the venue a record of the resale ticket at step 540. Alternatively, a new ticket may be issued representing a resale of the right to occupy the previously vacated seat or space.

[0173] Referring to FIG. 12(a), step 500 may include scanning, at an exit of the venue, the ticket, with a hand-held scanning device or scanning kiosk, or through geolocation technologies as described above. Further, referring to FIG. 12(b), in embodiments in which the ticket holder is incentivized to leave the venue and resell the ticket, step 500 may further include prompting the ticket holder to resell the ticket (step 501), which may for example, include a push notification message as shown in FIG. 11G. The method may then include receiving authorization to resell the ticket (step 502), which in turn may include selection of a price through the mobile app 302 (FIG. 11G), and then receiving notification that ticket holder has left venue (step 503), which in turn may for example, include scanning, at an exit of the venue, the ticket, with a hand-held scanning device or scanning kiosk, or through geolocation technologies as described above, followed by transmission of this information to the ticket transaction server 303. The account of the ticket holder is thereafter credited for the resale of the ticket in step 504. This crediting preferably occurs after the ticket has been resold to the third party (solid arrow in FIG. 12(b)). However, if the venue or system wishes to provide the incentive independent of any resale to a third party, the ticket holder's account may be credited prior to any resale (dashed arrow in FIG. 12(b)).

[0174] Independent of whether or not the embodiment provides incentives for resale, the system may prompt the ticket holder to confirm that they have left the event and are not returning (FIG. 11D).

[0175] Referring to FIG. 12(c), step 510 may include, in step 511, identifying potential late arrivals from users based on user preferences, user indication (e.g. FIG. 11F) and/or user location, and broadcasting to potential late arrivals that ticket is available (step 512), for example as shown in FIG. 11C or 11E. Further, step 520 may include receiving a request for an available resale ticket (step 521), for example by sending information sufficient to process the resale from the mobile app 302 to the ticket transaction server 303, and then debiting the account of the late arrival ticket holder for the ticket (step 522), for example, through conventional debit or credit card processing techniques.

[0176] Further, referring to FIG. 12(d), when a ticket holder leaves an event in progress, step 500 may further include tracking the ticket holder for a period of time via the GPS function on their mobile device (step 531), transmitting that GPS information to a server (step 532), and then a computer routine on the server determining what businesses or locations that the ticket holder has entered or passed by (step 533). The method may then include transmitting advertisements related to such businesses or locations to the ticket holder's mobile device (step 534), or in addition to, or alternatively, based on data showing that several ticket holders entered or passed by the same businesses or places (step 535), transmitting advertisements to the mobile devices of those still attending the event (step 536), so that those attendees are shown advertisements for businesses or places they are likely to enter or pass by when they leave the event at a later time.

[0177] In the preceding specification, the invention has been described with reference to specific exemplary embodiments and examples thereof. It will, however, be evident that various modifications and changes may be made thereto without departing from the broader spirit and scope of invention as set forth in the claims that follow. The specification and drawings are accordingly to be regarded in an illustrative manner rather than a restrictive sense.