Patent Application
20140195277
1. Field of the Invention
This invention relates to systems and methods for creating seating charts in digital form, and more particularly to systems and methods for user-driven creation and visualization of interactive digital seating charts, particularly for ticketing and reservations systems.
2. Description of the Related Art
Many systems are known for providing electronic tickets to different events. However, each event normally is hosted in one of a variety of different venues. In order to create ticketing solutions, each seating within the venues needs to be assigned a specific number or identifier so that two different patrons aren't sold tickets to the same venue seat. Some systems, such as the website socialtables.com allow one to electronically design layouts of seats for planning an event. However, these systems do not provide a robust and automated way of capturing the format of a particular venue and thereafter providing a ticketing service to handle seat assignments and other ticketing functions.
Systems and methods described herein provide interactive, user-driven generation of a dynamic seating chart. A dynamic seating chart can be used as an interactive interface for users to visually manage a venue's seating inventory for such purposes as a ticketing and reservation system. A user can automatically or manually create a flexible seating map that user can quickly modify to dynamically reflect a seating configuration of an evolving venue. The map can be linked to information about individual seats such as location and pricing information, and further displayed with additional information useful to individuals associated with the venue or events at the venue, and the attendees (of the venue/event).
Various embodiments relate to systems and methods for generating, preferably in a network-based system, an interactive illustration showing where a particular seat is located in an event venue. The system receives visual or dimensional input from a user to generate a digital map that can be displayed as a representative map of the venue; information to create identifiers for each seat in the venue (whether specific or general), and additional information such as pricing, zoning or other characteristic that may be necessary for the user and/or end-user to visually manage reservations, inventory, sales, and other interests.
Visual or textual input is received by the system to generate a visual interactive and informative display of seats, and more importantly, venue inventory. The system can prompt the user to input photos, schematics, drawings or other illustration to automatically, or with the aid of the user, generate a digital overlay representation that displays the seating arrangement of the venue. The system can link the input illustration with the digital overlay. Alternatively, the system can prompt the user for dimensional information about the venue to create a digital representation of the seating arrangement of the venue. The user can quickly modify and manipulate this seating map to accurately reflect the actual seating arrangement of the venue, particularly as a tool to visualize seating inventory and related information for the user, venue and event organizers and to end-users looking to reserve seating.
Information related to each seat is then generated to identify, for example, inventory purposes, the location of each seat, quantity of seats and/or characteristics of seats. Identifiers can be created for each seat or for blocks of seats. Additional information can be further associated with the seat information, for example, section or zoning associations, pricing, end-user reservations, sales, and other information relevant to the user.
The systems and methods disclosed herein provide, in one embodiment, an application for creating and displaying a dynamic seating chart, particularly for a venue such as a stadium, theater or other venue. In one embodiment, a user can create a dynamic seating chart that can be easily managed and changed as the seats and venue evolve. Through such seating charts, a user can visually manage inventory, analyze usage and sales, and visually rearrange seats to accommodate maximum usage. In addition, consumers can be presented information about one or more seats at a venue, and be presented an online interface to purchase electronic tickets and/or a link to view additional information associated with the tickets and/or seat.
In yet another aspect of the invention, a computer program product for generating a dynamic seating chart is embodied on a computer readable medium and when executed by a computer, performs the method comprising generating a digital seating map, generating one or more seat identifiers for each seat in the digital map associated with a database, and thereafter linking the seating map with a seat.
Additional aspects related to the invention will be set forth in part in the description which follows, and in part will be apparent from the description, or may be learned by practice of the invention. Aspects of the invention may be realized and attained by means of the elements and combinations of various elements and aspects particularly pointed out in the following detailed description and the appended claims.
It is to be understood that both the foregoing and the following descriptions are exemplary and explanatory only and are not intended to limit the claimed invention or application thereof in any manner whatsoever.
The accompanying drawings, which are incorporated in and constitute a part of this specification, exemplify the embodiments of the present invention and, together with the description, serve to explain and illustrate principles of the invention. Specifically:
In the following detailed description, reference will be made to the accompanying drawings. The aforementioned accompanying drawings show by way of illustration, and not by way of limitation, specific embodiments and implementations consistent with principles of the present invention.
The systems and methods disclosed herein provide, in one embodiment, an application for creating and displaying a dynamic seating chart, particularly for a venue such as a stadium, theater or other venue. In one embodiment, a user can create a dynamic seating chart that can be easily managed and changed as the seats and venue may evolve. Through such seating charts, a consumer can be presented information about one or more seats at a venue, and be presented an online interface to purchase electronic tickets and/or a link to view additional information associated with the tickets and/or seat.
It is to be understood that while a particular interactive seating chart may be described, the embodiments are not limited to such context. Furthermore, it is to be understood that while a particular interactive seat chart may be described as comprising a certain set of features and functions, an interactive seat map may comprise fewer features and functions, additional features and functions, and/or a combination of various features and functions of different user interfaces in accordance with the described embodiments.
As defined herein, the term “venue” or “venue” refer to any stadium(s), arena(s), theatre(s), movie theatre(s), concert hall(s), museum(s), performance hall(s), indoor stadium(s), indoor arena(s), indoor theatre(s), indoor movie theatre(s), indoor concert hall(s), indoor museum(s), indoor performance hall(s), outdoor stadium(s), outdoor arena(s), outdoor theatre(s), outdoor movie theatre(s), outdoor concert hall(s), outdoor museum(s), outdoor performance hall(s), and/or any other place(s) or location(s) where any of the herein-described and/or herein-defined events can be held, take place, and/or occur.
A venue can include any location of a scheduled event to be viewed by spectators. Non-limiting examples of performance venues include theaters, stadiums, arenas, halls, clubs, rooms and auditoriums. A performance venue includes a plurality of seats and a performance space. A venue can also include non-spectator sites or slots such as campgrounds, restaurants, ballrooms and convention centers, cubicles or other such spaces, where tickets and reservations may be sold or otherwise offered.
As used herein, a “seat” can include any pre-defined viewing location within a performance venue, and does not necessarily require a physical seat. Non-limiting examples of seats include chairs, benches, tables (with and without individual chairs), drive-in theater parking spots, reservations and score desks. As used herein, a “space” can include any location within a venue where the scheduled event to be viewed will primarily occur. Non-limiting examples of performance spaces include stages, fields and courts.
As defined herein, the term “ticket” or “tickets” refer to any tickets, conventional tickets, physical tickets, electronic tickets, digital tickets, mobile tickets, admissions, registrations, reservations, licenses, invitations, and/or any other mode or means, for allowing and/or permitting entry into, attendance at or in, and/or any other presence at or in, an event or venue, a sporting event or venue, a theatrical event or venue, a movie event or venue, an entertainment event or venue, a concert event or venue, and/or any other event or venue for which tickets and reservations, may be sold or otherwise offered.
As defined herein, the terms “event” or “events” refer to any event, sporting event(s), baseball game(s), basketball game(s), football game(s), hockey game(s), tennis event(s), swimming event(s), skiing event(s), athletic event(s), athletic competition event(s), Olympic event(s), and/or any game(s), event(s), tournament, and/or competition(s), theatrical event or performance, movie event or performance, entertainment event or performance, concert event or performance, and/or any other event or performance for tickets or registration may be sold or otherwise offered.
As defined herein, the terms “user”, “individual”, or the plurals of same, refer to any user, individual, venue owner or promoter, ticket seller, ticket broker, ticket brokers, ticket issuer, ticket and/or any other individuals or entities who or which utilize the apparatus and method of the present invention, particularly for generating an interactive seating chart. The user does not necessarily have to be the venue or event representative but can represent any user utilizing the present invention. As defined herein, the terms “end-user”, “consumer” or “buyer” refers to individuals that utilize the system after a seating chart has been created, for example to purchase or acquire a ticket or to view seating arrangements, availability, information, etc.
As defined herein, the phrase combining the term “seat” or “seating” with the term “chart” or “plan” refers to the digital visual representation of a venue (i.e., “map”), particularly to seats and/or sections within a venue that may or may not have additional information associated with each seat/section such as pricing, location, identity, seating details (e.g., section, row, seat, comments), designations (reserved, general, handicapped, etc.), and the like. The visual representation can be in the form of a schematic, outline, drawing or other representation to enable viewers to see the layout of a venue and the components thereof, preferably electronically, such as structures, landmarks (which may be structural landmarks, such as walls, columns, doorways, seats, and/or may be active or passive beacons, such as coded signs (e.g., where each sign has a unique visual code and the signs are strategically placed are columns, walls, etc.), etc.), or such other representation desired by the user creator.
Further aspects and advantages of various embodiments will become more readily appreciated and better understood by the following description of the elements of the communications system 100 illustrated in
It may be advantageous to create a layout overlay that sits on top of a photo, for example one or more digital photos taken from a mobile device or camera. The photo can be input into system, or can reside on the user device. Once a photo is taken, an outline of the venue can be created by superimposing an outline over the photo of the venue. The creation of the digital overlay can be created on the device or on a server connected to the device. If the photo or schematic is used as the background for display to a customer, the system can create tags or marks on both the image and the overlay to ensure that they are consistently and accurately superimposed.
Outlines of the venue can also be generated by wizards and templates that guide the user through generation of an outline. For example, as shown in
Although the process of outlining the boundaries of the venue will assist the user in generating the seating map, it is not necessarily required as the boundaries of the venue can be established by the generation of the sections and seats as shown in
Venues can typically be rearranged between different types of events, such as between sporting events and concert events. For example, a sporting event may call for all seats to be available in the stands and no seats available on the field, while a concert event may fill the floor of the arena with seats and kill or otherwise restrict from sale seats behind a stage. Some sporting events have different seating layouts than others. For example, basketball, which features seats near the ground and close to the action, typically has a different seating arrangement than football, which features seats farther away from the field. Some events, such as soccer and football, may have equal seating arrangements. Likewise, different concerts and entertainment events may have similar or different layouts, depending on the artists involved, types of performance, or types of production. Seating layouts may be predetermined by the promoter, venue, or artist, or the seating layout may be determined in conjunction with pricing.
Preferably, if an image or schematic of a venue with sections is available, such as shown in
As further shown in
Alternatively, the wizard/template can be further used to auto-generate the number of sections. In one embodiment, this step is a single process in combination with the wizard/template for the seating and/or venue. However, this process can be initiated at any point, including for generating the individual seating chart or, in this case, the section generation. The wizard can request specific information be provided by the user to create a section chart, including, for example, the number of floors/tiers/layers, the number of sections in that floor, and other such parameters to create distinct sections. For example, in a stadium with two layers, each layer may have 20 sections that circumnavigate the circumference of the stadium. The user may input the number of layers (2) and input the number of sections in each layer (20), which will be displayed as two oval rings with 20 sectors within each ring. Each sector may not accurately reflect the true size of each section, but can be modified by the user to more accurately reflect the true physical layout of the venue and sections. Each section can be digitally identified with numbers, characters and/or symbols to distinguish each section from other sections.
Preferably, if an image or schematic of a seating chart is available, such as shown in
The overview image can also be linked to numerous digital images, such as digital photographs, of rooms in a structure, exterior views of a structure within a property, and outside spaces and outside structures within the property, using icons placed in the property overview image. The present method is advantageous due to its unique compilation of information. Simultaneous with the outline generation process, various features, amenities, benefits, characteristics, qualities, and materials of a property can be recorded such as viewing obstructions, segmentations or other interruptions, etc.; and graphic images reflecting these features can be drawn and inserted into the overview image. Unlike many conventional floor plans, the present method produces overview images that also can include annotated text information relating to features of a room, outside space, or outside structure displayed in the overview image. Extensive textual annotation describing measurements, landmarks, fixtures, textures, materials, columns or overhangs, ceiling, flooring, and various other features can be included in the overview image.
Alternatively, images or schematics as shown in
As further shown in
Each section can be processed separately to make management of the different seats easier, particularly if there are multiple sections. Or, alternatively, the identification can be generated for the entire venue, or multiple sections at a time. Generation of the identifier for the section of seats can be in conjunction with, separate or in lieu of the generation of the individual seat identifier. Preferably, the system will begin by creating a default identifier for the section, for example theaters have orchestra as the lowest level, followed by the higher levels of ‘loge’, ‘mezzanine’, ‘grand tier’, ‘balcony’ and ‘gallery’, respectively. Stadiums are often numbered with each levels numbered indifferent sequences, e.g., 100s, 200s, etc. Generally, however, section identification will be unique to the user and the venue and may require direct input by the user, as they may distinguish each section, e.g., ‘grand circle’, ‘reserved’, ‘general’, ‘left’, ‘right’, ‘center’, ‘upper’, ‘lower’, ‘field’, ‘box’, ‘club’, or other such distinguishing nomenclature. The names used by the system may be different than the names displayed for easier management of seats.
If individual seat identity is necessary, system may create seat identity(ies) automatically. For example, if the seating information is available in a schematic, text recognition can be applied to identify the identity of the row and of each seat. The schematic in
Seat location within a section is generally identified by its row number, although it can be identified by its table number, box number, section number and the like. As discussed, this information can be manually input by user, automatically prompted by system or something in between. For example in
Similarly, numbering of each seat across each row can also be prompted by the system or input by the user, but preferably defaulted to start from 1 through N (N=the last number of the seats). User can override system to either start with different numbers, letters, codes or other identifier, as well as use coding sequences unique to that venue (e.g., odd or even numbers for different sections of seating).
As shown in
In a further embodiment, system can correlate current seat inventory information with the event database to show existing inventory for a particular event. The inventory information may be uploaded or the system may have a direct connection to an inventory database. This allows the inventory to be displayed visually by status (e.g., available, sold, held, unavailable, reserved, inquiry), by price (e.g., the face value of the ticket for a particular seat, or the going price for a particular seat), and by class (e.g., the type of ticket associated with the seat, the type of package associated with the seat).
As shown in
Designation or characteristic information can also be attributed for each seat which may be temporary or permanent designations such as accessibility by handicapped or disabled individuals, adult or child seating, smoking or non-smoking, box seating, accessibility (e.g., privileged, special or general), amenities available such as food or alcohol and other services, reserved or general seating, VIP, season seats, box or held seats, and other designations provided for particular (types of) seats.
Specific information about the seats, by way of example and not limitation, seat shape and color, seat type (e.g., bench, cushioned, non-cushioned, back rest, no back rest, etc.), seat material (e.g., concrete, wood, plastic, etc.) and/or seat rotation angle may also be included and displayed. Information may be conveyed via a seat icon (or other indicator) using a corresponding interior color, outline color, interior symbol/text/character, color of such symbol, one or more orbiting symbols that are optionally color coded, etc.
More preferably, user can define sectors or zones to identify similar seating areas, particularly for pricing. Sectors or zones can be based on sections, rows, or blocks of individual seats that are similar in location, feature, but more preferably price. Different sectors and zones may be defined for different types of events.
A database connected to or included in the invention system can also include the price or price type for each specific seat. The price may be the specific price, a range of prices or the category of prices. Fixed types of events, e.g., movies, may warrant fixed prices or prices within set ranges. User can set the price through the system for all seats, sections or zones, or for the entire venue. However, it may be advantageous to use aggregate seats/sections based on location and/or designation to account for different types of events which each may attract different prices, for example a stadium which holds both concerts and sporting events will have two different prices for the same seat or same section, or may categorize different seats based on different identifiers.
System can allow the user to assign prices to seats by creating a certain number of ‘price codes’ or price levels that relate to dollar values. The system extracts seat information from a seat chart/map by defining different zones. Zones can be preset by the user or modified based on the input of event organizers, promoters and the like. The user is prompted to assign price codes to each zone, and the dollar value for the price code is associated with each zone. The dollar value of a price code can be changed centrally, and such changes will update the price for every seat identified as being part of that price code. The user can also enable price codes to be defined by third party users such as event organizers, promoters, artists, venue or other interested party that may assign pricing. The user can also set aside seats, make unavailable or create other pools of tickets for a particular. For example, seats with obstructed views can be color-coded or X'ed out so that it is immediately clear to the user that the seats should not be listed for sale. The user may also indicate that certain seats are to be ‘held’ (i.e., hold them from an initial sale period). The user can preview a visual representation of the pricing plan to make sure that the locations by price and the overall financial potential of all tickets (if sold) meet the needs of those involved with the event.
The user can export the price plan's price codes and seat block assignments to be imported into a ticketing system. If the pricing system is directly linked to the ticketing system, then the pricing information can be directly submitted to the ticketing database. The user can create several ‘price plans’ for an event to determine the best plan for each event.
Other differentiators that may affect price include the type of ticket (e.g., processing and other ticketing fees, adult-full price, adult-discounted, child, reserved or general, box seats or other viewing privileges, or alternatively obstructions, amenities such as dining or parking privileges, packaged such as season tickets, etc.) etc.), second market or resale or auction-able tickets, or other factors which may affect price such as excess or unwanted inventory (e.g., an indication as to whether the seating area only has single seats available and not two or more available adjacent seats).
In a particular embodiment, the system may be configured to obtain and/or provide information for active ticket listings and sold ticket listings to enable dynamic pricing for primary or secondary ticket sales. The information may comprise pricing information including active ticket prices (e.g., fixed, auction, and/or declining prices for unsold tickets) and sold ticket prices (e.g., actual prices fans have paid for specific locations) for providing an accurate representation of the current market value of tickets for an event. For each event, the pricing information may comprise data defining active listings (e.g., section, row, quantity, listed price) and sold listings (e.g., section, row, quantity, date, sold price) for each section and for each zone (e.g., aggregated sections) in an event venue.
The pricing information also may include data defining the highest price, the lowest price, and the average price for all active tickets and/or sold tickets within any section or zone. In some implementations, the average price may be calculated as a median price for all active and/or sold tickets within any section or zone by dropping the lowest and highest priced tickets. The pricing information may comprise data defining comparable sections, such as the top ten sections that are closest in price. The pricing information may further comprise the overall average ticket price for an event calculated, for example, by dropping the five lowest and highest priced tickets. The pricing information also may include rising and falling pricing trend information such as price change data (e.g., the percentage change in the average price of sold tickets for an event within the last N number of days), listing rate data (e.g., the percentage change in the amount of active listings within the past week, and/or selling rate data (e.g., the percentage change in the amount of sold tickets within the past week). It can be appreciated that other types of information and/or data may be obtained and/or provided in accordance with the described embodiments.
The system can further be uploaded with or be directly connected to an event database that provides information about each event at the venue. The event database can contain information about dates and times of different events; the main attraction such as the performer, movie, team, activity, organizer, host, guest of honor, or artist; genre; the number of expected attendees; the promoters or the organizers of the event; specific requirements of the event; and other such information related to the event itself. The user can utilize various tools that analyze sales rates of a given event and current and/or past comparable events to determine the likelihood that certain seats/sections/price levels may or may not sell out at the current set price, and to indicate whether price changes may or may not be recommended in order to sell out or to achieve other sales goals and/or whether certain events should be packaged together. This information can be used by create a pricing plan customized for a particular event.
Other information may be stored in the system database and included in or associated with the present invention. Depending on the use of the dynamic seating chart, e.g., ticketing, reservations, etc., additional information can also be accessed and stored, including end-user CRMs that manage identity and activity data for individuals who are or may be potential end-users, social media databases to enhance sales and marketing, public or private databases to extract historical and comparable data and templates to facilitate generation of new dynamic seating charts, and other data stores which may facilitate or enhance the use of the present invention.
Another embodiment of the present invention includes a system and method for correlating current seat inventory information with a dynamic seating chart of a venue. The inventory information may be uploaded or the system may have a direct connection to the inventory database. This allows the inventory to be displayed visually by status (e.g., available, sold, held, killed, inquiry), by price (e.g., the face value of the ticket for a particular seat), and by class (e.g., the type of hold, the type of package associated with the seat). This information from the database can be displayed on a seating map, along with other pertinent information utilized to enhance gross revenues, net revenues, and/or the number of seats filled/tickets sold. For example, the inventory provides a block of data for each section of the event venue or for each section of the event venue that has available tickets for the event, the block of data including section data such as a section identification (such as the section number), a section title (such as “Lower Box”, “Field Club”, or “Arcade”), and a listing of tickets (including the row, quantity, and price for each ticket). Certain embodiments may be utilized to reduce certain types of resale activity (e.g., resale activities that may not be in the public interest, such as, in certain instances, ticket scalping).
The interactive event venue seat chart, see
Controls are provided via which the user can navigate around the map and/or zoom into a certain section of the map. For example, the map is configured to enable a user to click on an area of a map and drag the map to change the displayed map area. In certain embodiments, even when a user clicks or otherwise selects a particular seating area or section, to thereby expand the view of the selected area, the entire venue is still displayed in an area of the map, with the seat statuses indicated (e.g., via color and/or text). The system may further provide user the option to search for different features. For example, if a user enters search criteria (e.g., seats having a ticket price between $50-$100), the user interface will highlight (e.g., via color coding or otherwise) the seats and/or sections that match the search criteria. If the user then selects a given highlighted section, the user interface will zoom in on the selected section, while still displaying an overall view of the venue (which may be reduced in size) in a corner or elsewhere, where the overall view still highlights the seats/sections matching the user's search criteria (e.g., seats between $50-$100). This enables the user to make changes to the dynamic seating chart more readily. The user can upload new price codes or make changes to the pricing of seating individually.
As illustrated in
When the display and visualization capabilities are used for planning or inventory control purposes, the seat status information or a data file can be modified, either manually or through system that allows the user to select seats on a seating chart. New information (e.g., price information) about those seats can be input, thereby updating the data file. This allows promoters, venue owners, or other stakeholders a relatively easy to use tool with which to try out different pricing and seating configurations before finalizing pricing for an event.
Further, the system receives substantially real time ticket sales information for one or more ongoing events, and reports the information to a user (e.g., reports an event ticket sales rate, the number of sold seats, the number of unsold seats, the number of held seats, the percentage of sold seats, a projected sell-out time, event web page visits, event web page conversions to sales, cumulative sales by day as a percent of original net capacity, cumulative audit gross by day, and/or other information discussed herein). The system also has access to, and is configured to provide for display historical information for events that have concluded, including some or all of the types of information provided for ongoing events.
The display and mapping capability can be accessed through desktop software or through a web and mobile-based applications. A web-based and mobile-based application can allow users not linked to the ticket data to visualize ticket information. This may be particularly valuable to concert promoters that wish to know about sales status but are not co-located with the ticket database. A web-based system allows users to log in from a remote location, enter a password, and view data. In the case of a user that has access to ticket data, this data is uploaded and the data from the file can be viewed in a number of displays. For a user who does have access to the ticket inventory database, the embodiment will present the last data that was uploaded by someone with access. It is also possible that the system is connected to the inventory database and information is updated automatically. There can also be different levels of access for different password holders, allowing each user access to a predetermined portion of the data.
The system optionally utilizes the event seating and ticket pricing information as an interface for display to end-users such as ticket purchasers. For example, the user interfaces may display a seating chart color coded, icon coded, and/or text coded to indicate seat availability, prices, seats selected by the user, seats purchased by the user, seats that match user search criteria (e.g., price range, seating section(s), seat type, special offer(s) specified by the user, etc.), other seats that are available, seats that are not available. Other features viewable may be wheelchair accessibility, whether a special code is needed to purchase ticket for a seat, whether the user has already purchased a ticket for the seat for the event, etc. The ticket purchaser user interface may provide a control via which the user can specify filtering criteria (e.g., ticket price, viewing quality, whether a special offer is available, whether the a ticket for the seat is held by a friend of the user, etc.), wherein the user interface will highlight individual seats and/or seating sections that meet the filter criteria. Optionally, the user may select (e.g., by pointing at or clicking on) an individual seat and/or seating section, and the ticket purchaser user interface will access and display additional information regarding the eat (e.g., whether a special password/offer code is required to purchase tickets for the seat, a seat number, a seat row number, a seat section number, face price, ticket related fees, combined face and fee prices, view information, whether alcohol is permitted, whether the seat is in the shade, etc.).
In one implementation, for example, after selecting an event the end-user may be presented with an interactive event venue seat map (see
The event listings may include details such as section, row, quantity, and price and may be sorted by the end-user according to such details. The sections of the interactive event venue seat map for which tickets are available may be displayed in color while sections having no available tickets may be displayed in a different color or shade. For example, red, olive, green, blue, teal, orange, etc., each may be used to indicate different functions, prices, status or designations, e.g., sold available, reserved, etc. Optionally, different brightness, shades or tones of the same color can be used to indicate seats chosen by end-user. Optionally, more muted or pastel colors may be used to indicate relatively low grade/inferior seats, and brighter or primary colors may be used to indicate relatively higher grade/superior seats. Other visual indications may be used as well (e.g., different shapes, flashing seat icons may be used to indicate higher grade/superior seats). Those of skill in the art will know other options available to represent the different functions, status and pricing of seats.
By way of further example, with respect to seat colors, dark blue (or other color) may be used to indicate that the seat is available for purchase and matches the user's selected price range and ticket options. Light blue (or other color) may be used to indicate that the seat is available for purchase, but is outside the user's selected price range and/or ticket options. Gray (or other color) may be used to indicate that the seat is not available for purchase. Orange (or other color) may be used to indicate that the cursor is over that seat or the user has already added the seat to the user's selected seats.
In general, the end-user may be provided the same viewing privileges as the user, but without the ability to make changes. Controls are provided via which the end-user can navigate around the map and/or zoom into a certain section of the map. For example, the map is configured to enable an end-user to click on an area of a map and drag the map to change the displayed map area. In certain embodiments, even when an end-user clicks or otherwise selects a particular seating area or section, to thereby expand the view of the selected area, the entire venue is still displayed in an area of the map, with the seat statuses indicated (e.g., via color and/or text). The system may further provide end-user the option to search for different features. For example, if an end-user enters search criteria (e.g., seats having a ticket price between $50-$100), the user interface will highlight (e.g., via color coding or otherwise) the seats and/or sections that match the search criteria. If the end-user then selects a given highlighted section, the end-user interface will zoom in on the selected section, while still displaying an overall view of the venue (which may be reduced in size) in a corner or elsewhere, where the overall view still highlights the seats/sections matching the end-user's search criteria (e.g., seats between $50-$100).
Optionally, if the end-user hovers a pointer (e.g., a cursor) over a certain seat or seating area, or otherwise indicates a seat or seating section (e.g., by clicking on a specific seat or seating area), additional information is provided (e.g., via a pop-up window or overlay) regarding the corresponding seat or seating section. For example, the additional information may include an indication as to whether an offer code is needed, and if so, from which source, the specific seating information (e.g., section, row number, seat number, the ticket price, the type of ticket (e.g., adult-full price, adult-discounted, child, etc.) etc.), an indication as to whether the seating area only has single seats available (and not two or more available adjacent seats). Other information, such as whether the seat is in a covered area or an exposed area, in the shade or in direct sunlight, the distance of the seat to an exit, bathroom, concessions, parking lot, and/or other destination, how far the seat is from an aisle (e.g., expressed as a number of seats and/or in a unit of length, such as feet, meters, or yards), expected temperature at the seat during the event, whether there is waiter service to the seat, and/or other information may be displayed as well.
As illustrated in
In an embodiment of the present invention, the present system enables users to use devices to input images dynamically or on-the-fly. The image that is input into system can be any picture that evolves with the venue, and can be input using any device such as a camera or mobile phone. Generally the photo can be taken from any angle, but preferably from an angle to get a panoramic view of the seats. Alternatively, a view (and captured image) can be taken from the seat. Accordingly, the seating chart may be configured to provide “view from the seat” images (e.g., movies, photographs, graphic renderings, etc.). For example, a user may select/click-on a seat/section and/or an associated icon (e.g., a camera symbol), and the view from the seat or section may be displayed. The image(s) may include one or more static images, a view from the seat, a view to the seat from the performance area, and/or an immersive virtual reality 360 degree or full sphere view. Each icon can be located in the property overview image at the representative location where a digital image was collected, and can depict the direction and perspective of the represented digital image. The digital images can be displayed alongside textual information relating to the depicted space, and can further contain links to lists of textual information regarding an entire structure or property.
The computer system 2300 is shown comprising hardware elements that can be electrically coupled via a bus 2305 (or may otherwise be in communication, as appropriate). The hardware elements can include one or more processors 2310, including without limitation, one or more general purpose processors and/or one or more special purpose processors (such as digital signal processing chips, graphics acceleration chips, and/or the like); one or more input devices 2315, which can include without limitation a mouse, a keyboard and/or the like; and one or more output devices 2320, which can include without limitation a display device, a printer and/or the like.
The computer system 2300 may further include (and/or be in communication with) one or more storage devices 2325, which can comprise, without limitation, local and/or network accessible storage and/or can include, without limitation, a disk drive, a drive array, an optical storage device, a solid state storage device such as a random access memory (“RAM”) and/or a read-only memory (“ROM”), which can be programmable, flash updateable and/or the like. The computer system 2300 might also include a communications subsystem 2330, which can include without limitation a modem, a network card (wireless or wired), an infrared communication device, a wireless communication device and/or chipset (such as a Bluetooth™ device, an 802.11 device, a WiFi device, a WiMax device, cellular communication facilities, etc.), and/or the like. The communications subsystem 2330 may permit data to be exchanged with a network (such as the network described below, to name one example), and/or any other devices described herein. In many embodiments, the computer system 2300 will further comprise a working memory 2335, which can include a RAM or ROM device, as described above.
The computer system 2300 also can comprise software elements, shown as being currently located within the working memory 2335, including an operating system 2340 and/or other code, such as one or more application programs 2345, which may comprise computer programs of the invention, and/or may be designed to implement methods of the invention and/or configure systems of the invention, as described herein. Merely by way of example, one or more procedures described with respect to the method(s) discussed above might be implemented as code and/or instructions executable by a computer (and/or a processor within a computer). A set of these instructions and/or codes might be stored on a computer-readable storage medium, such as the storage device(s) 2325 described above. In some cases, the storage medium might be incorporated within a computer system, such as the system 2300. In other embodiments, the storage medium might be separate from a computer system (i.e., a removable medium, such as a compact disc, etc.), and is provided in an installation package, such that the storage medium can be used to program a general-purpose computer with the instructions/code stored thereon. These instructions might take the form of executable code, which is executable by the computer system 2300 and/or might take the form of source and/or installable code, which, upon compilation and/or installation on the computer system 2300 (e.g., using any of a variety of generally available compilers, installation programs, compression/decompression utilities, etc.), then takes the form of executable code.
It will be apparent to those skilled in the art that substantial variations may be made in accordance with specific requirements. For example, customized hardware might also be used, and/or particular elements might be implemented in hardware, software (including portable software, such as applets, etc.), or both. Further, connection to other computing devices such as network input/output devices may be employed.
In one aspect, the invention employs a computer system (such as the computer system 2300) to perform methods of the invention. According to a set of embodiments, some or all of the procedures of such methods are performed by the computer system 2300 in response to processor 2310 executing one or more sequences of one or more instructions (which might be incorporated into the operating system 2340 and/or other code, such as an application program 2345) contained in the working memory 2335. Such instructions may be read into the working memory 2335 from another machine-readable medium, such as one or more of the storage device(s) 2325. Merely by way of example, execution of the sequences of instructions contained in the working memory 2335 might cause the processor(s) 2310 to perform one or more procedures of the methods described herein.
The terms “machine-readable medium” and “computer readable medium,” as used herein, refer to any medium that participates in providing data that causes a machine to operate in a specific fashion. In an embodiment implemented using the computer system 2300, various machine-readable media might be involved in providing instructions/code to processor(s) 2310 for execution and/or might be used to store and/or carry such instructions/code (e.g., as signals). In many implementations, a computer-readable medium is a physical and/or tangible storage medium. Such a medium may take many forms, including but not limited to, non-volatile media, volatile media, and transmission media. Non-volatile media includes, for example, optical or magnetic disks, such as the storage device(s) 2325. Volatile media includes, without limitation, dynamic memory, such as the working memory 2335. Transmission media includes coaxial cables, copper wire and fiber optics, including the wires that comprise the bus 2305, as well as the various components of the communications subsystem 2330 (and/or the media by which the communications subsystem 2330 provides communication with other devices). Hence, transmission media can also take the form of waves (including without limitation radio, acoustic and/or light waves, such as those generated during radio wave and infrared data communications).
Common forms of physical and/or tangible computer-readable media include, for example, a floppy disk, a flexible disk, a hard disk, magnetic tape, or any other magnetic medium, a CD-ROM, any other optical medium, punchcards, papertape, any other physical medium with patterns of holes, a RAM, a PROM, an EPROM, a FLASH-EPROM, any other memory chip or cartridge, a carrier wave as described hereinafter, or any other medium from which a computer can read instructions and/or code.
Various forms of machine-readable media may be involved in carrying one or more sequences of one or more instructions to the processor(s) 2310 for execution. Merely by way of example, the instructions may initially be carried on a magnetic disk and/or optical disc of a remote computer. A remote computer might load the instructions into its dynamic memory and send the instructions as signals over a transmission medium to be received and/or executed by the computer system 2300. These signals, which might be in the form of electromagnetic signals, acoustic signals, optical signals and/or the like, are all examples of carrier waves on which instructions can be encoded, in accordance with various embodiments of the invention.
The communications subsystem 2330 (and/or components thereof) generally will receive the signals, and the bus 105 then might carry the signals (and/or the data, instructions, etc., carried by the signals) to the working memory 2335, from which the processor(s) 2310 retrieves and executes the instructions. The instructions received by the working memory 2335 may optionally be stored on a storage device 2325 either before or after execution by the processor(s) 2310.
Merely by way of example,
Certain embodiments of the invention operate in a networked environment, which can include a network 210. The network 210 can be any type of network familiar to those skilled in the art that can support data communications using any of a variety of commercially available protocols, including without limitation TCP/IP, SNA, IPX, AppleTalk, and the like. Merely by way of example, the network 210 can be a local area network (“LAN”), including without limitation an Ethernet network, a Token-Ring network and/or the like; a wide-area network (WAN); a virtual network, including without limitation a virtual private network (“VPN”); the Internet; an intranet; an extranet; a public switched telephone network (“PSTN”); an infrared network; a wireless network, including without limitation a network operating under any of the IEEE 802.11 suite of protocols, the Bluetooth™ protocol known in the art, and/or any other wireless protocol; and/or any combination of these and/or other networks.
Embodiments of the invention can include one or more server computers 215. Each of the server computers 215 may be configured with an operating system, including without limitation any of those discussed above, as well as any commercially (or freely) available server operating systems. Each of the servers 215 may also be running one or more applications, which can be configured to provide services to one or more clients 205 and/or other servers 215.
Merely by way of example, one of the servers 215 may be a web server, which can be used, merely by way of example, to process requests for web pages or other electronic documents from user computers 205. The web server can also run a variety of server applications, including HTTP servers, FTP servers, CGI servers, database servers, Java™ servers, and the like. In some embodiments of the invention, the web server may be configured to serve web pages that can be operated within a web browser on one or more of the user computers 205 to perform methods of the invention.
The server computers 215, in some embodiments, might include one or more application servers, which can include one or more applications accessible by a client running on one or more of the client computers 205 and/or other servers 215. Merely by way of example, the server(s) 215 can be one or more general purpose computers capable of executing programs or scripts in response to the user computers 205 and/or other servers 215, including without limitation web applications (which might, in some cases, be configured to perform methods of the invention). Merely by way of example, a web application can be implemented as one or more scripts or programs written in any suitable programming language, such as Java™, C, C#™ or C++, and/or any scripting language, such as Perl, Python, or TCL, as well as combinations of any programming/scripting languages. The application server(s) can also include database servers, including without limitation those commercially available from Oracle™, Microsoft™, Sybase™, IBM™ and the like, which can process requests from clients (including, depending on the configuration, database clients, API clients, web browsers, etc.) running on a user computer 205 and/or another server 215. In some embodiments, an application server can create web pages dynamically for displaying the information in accordance with embodiments of the invention. Data provided by an application server may be formatted as web pages (comprising HTML, Javascript, etc., for example) and/or may be forwarded to a user computer 205 via a web server (as described above, for example). Similarly, a web server might receive web page requests and/or input data from a user computer 205 and/or forward the web page requests and/or input data to an application server. In some cases a web server may be integrated with an application server.
The seating map can be generated and stored in variety of formats including known and proprietary vector graphics formats such as vector graphics formats and raster graphics formats. Vector graphics (also called geometric modeling or object-oriented graphics) utilize geometrical primitives such as points, lines, curves, and polygons to represent images. Examples of vector graphics formats include the Scalable Vector Graphics (SVG) and Vector Markup Language (VML) formats. The SVG format is defined at W3C, Scalable Vector Graphics (SVG), w3.org/Graphics/SVG/. VML is described in Brian Matthews, et al., Vector Markup Language (VML), w3.org/TR/1998/NOTE-VML-19980513. Alternatively, the images can be converted to or maintained in a raster graphics format, which is a representation of images as a collection of pixels. Examples of raster graphics formats include JPEG, TIFF, RAW, PNG, GIF, and BMP. For example, any number of computer programming languages, such as the Java language, JavaScript, Java Applet technology, C, C++, Perl, Pascal, Smalltalk, FORTRAN, assembly language, HTML (i.e., Hypertext Markup Language), DHTML (i.e., Dynamic Hypertext Markup Language), XML (i.e., eXtensible Markup Language), XLS (i.e., eXtensible Style Language), SVG (i.e., Scalable Vector Graphics), VML (i.e., Vector Markup Language), Macromedia's Flash technology, and the like, may be used to implement aspects of the present invention. Further, various programming approaches such as procedural, object-oriented or artificial intelligence techniques may be employed, depending on the requirements of each particular implementation.
In one embodiment, the present invention uses object recognition techniques to capture the outline of the venue, section and/or each individual seat, as well as text recognition techniques to capture identity information, if any, from any scanned or input image. In an image such as a picture, object recognition can be performed by analyzing the image to identify specific objects such as structural landmarks, such as open spaces, stages, fields, walls, columns, doorways, seats, benches, tables, and the like. In schematics, object recognition can be performed on representative shapes of seats and structural landmarks. Preferably, the object recognition engine will look for seats, bench, or chairs, tables or other seating arrangements within the image which can be generally transformed into representative shapes for seating charts. Object recognition software that can be utilized include those that are developed by Google, Toshiba, or ones that utilize vision computing techniques such as machine learning/pattern recognition to identify specific objects in images. Those of skill in the art will be able to identify suitable techniques for identifying particular objects from images and drawings, particularly for the present invention. It should be noted that various object detection processes can be utilized by the present invention. One example of an object detection process is discussed in U.S. patent application entitled “Object Recognition Using HAAR Features and Histograms of Oriented Gradients”, U.S. application Ser. No. 13/085,985. Another example of an object detection process is discussed in the U.S. patent application entitled “Detection of Objects in Digital Images”, U.S. application Ser. No. 13/086,023. A general review of object recognition can be found in Cyganek, B., Object Detection and Recognition in Digital Images: Theory and Practice. (John Wiley & Sons, Ltd, 2013).
In accordance with further embodiments, one or more servers 215 can function as a file server and/or can include one or more of the files (e.g., application code, data files, etc.) necessary to implement methods of the invention incorporated by an application running on a user computer 205 and/or another server 215. Alternatively, as those skilled in the art will appreciate, a file server can include all necessary files, allowing such an application to be invoked remotely by a user computer 205 and/or server 215. It should be noted that the functions described with respect to various servers herein (e.g., application server, database server, web server, file server, etc.) can be performed by a single server and/or a plurality of specialized servers, depending on implementation-specific needs and parameters.
In certain embodiments, the system can include one or more databases. The location of the database(s) is discretionary. Merely by way of example, a database might reside on a storage medium local to (and/or resident in) a server (and/or a user computer). Alternatively, a database can be remote from any or all of the computers, so long as the database can be in communication (e.g., via the network) with one or more of these. In a particular set of embodiments, a database can reside in a storage-area network (“SAN”) familiar to those skilled in the art. (Likewise, any necessary files for performing the functions attributed to the computers can be stored locally on the respective computer and/or remotely, as appropriate.) In one set of embodiments, the database can be a relational database, such as an Oracle™ database, that is adapted to store, update, and retrieve data in response to SQL-formatted commands. The database might be controlled and/or maintained by a database server, as described above, for example.
The embodiments and implementations described above are presented in sufficient detail to enable those skilled in the art to practice the invention, and it is to be understood that other implementations may be utilized and that structural changes and/or substitutions of various elements may be made without departing from the scope and spirit of present invention. The following detailed description is, therefore, not to be construed in a limited sense. Additionally, the various embodiments of the invention as described may be implemented in the form of software running on a general purpose computer, in the form of a specialized hardware, or combination of software and hardware.
This application claims priority to U.S. Provisional Application No. 61/749,303 filed on Jan. 5, 2013 and entitled “Systems and Methods for Generating Dynamic Seating Charts” which is hereby incorporated by reference in its entirety.
| Number | Date | Country | |
|---|---|---|---|
| 61749303 | Jan 2013 | US |
